WO2014152164A1 - Système d'application client hiérarchique - Google Patents

Système d'application client hiérarchique Download PDF

Info

Publication number
WO2014152164A1
WO2014152164A1 PCT/US2014/027024 US2014027024W WO2014152164A1 WO 2014152164 A1 WO2014152164 A1 WO 2014152164A1 US 2014027024 W US2014027024 W US 2014027024W WO 2014152164 A1 WO2014152164 A1 WO 2014152164A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
layer
native
client
client device
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.)
Ceased
Application number
PCT/US2014/027024
Other languages
English (en)
Inventor
Fabio Chiussi
Parameshwar Hegde
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beeonics Inc
Original Assignee
Beeonics Inc
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
Priority claimed from US13/833,775 external-priority patent/US10320942B2/en
Priority claimed from US13/834,765 external-priority patent/US20140280481A1/en
Priority claimed from US13/833,589 external-priority patent/US10326825B2/en
Priority claimed from US13/833,669 external-priority patent/US10320885B2/en
Priority claimed from US13/833,849 external-priority patent/US10075560B2/en
Application filed by Beeonics Inc filed Critical Beeonics Inc
Publication of WO2014152164A1 publication Critical patent/WO2014152164A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/35—Creation or generation of source code model driven
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services

Definitions

  • the Client Devices are physicai and can be either mobile, such as cellular phones, sraa.rtph.ones, wearable devices, and tablets, or non-mobile, such as laptops, desktops, and In ernet- Enabled TV sets.
  • the Client Devices 1- are coupled to the internet, by wired (a physical interconnect), wireless!y (waves through space), or both wired /wireless networks.
  • the wireless connectivity can be cellular (3G, 4G, etc), Wi-Fi, Bluetooth, WiMax, etc.
  • the Client Device 1-2 runs the Application Client which is the actual application software running on device. [0003]
  • FIG. 1 A also shows an Application Store 1-10 connected to the internet.
  • the Cloud uses the network of the internet to offer services to users by using a combination of hardware and software embedded in the network.
  • An Application Client can be in the Cloud, but in this case the Client Device is a "virtual" Client Device,
  • the "virtual" Client Device has a way to provide access to the Application Client running in the cloud via a physical Client Device.
  • a web browser 1-6 running on the physical Client Device 1-2 and coupled to the client/server 1-7 in the Clout! via the Internet accesses the Application Client running in the Cloud, which performs the actual application software.
  • the Cloud there are two cases; the entire Application Client runs in the Cloud, or a small portion of the Application Client runs on a physical Client Device while most of the logic runs in the Cloud.
  • FIG. 2.4 illustrates a system 2-1 with the hardware 2-16 and software 2-15 of a Client Device 1-2.
  • the Client Device 1-2 is coupled to the internet 1-3 via wireline connection or Radio Frequency (RF) wireless transmission network (xvired xvireless) 2-2 and further coupled to a bank of servers 2-4 via a second interconnection 2-3 that can be wired or wireless.
  • the communication link is a receiver and a transmitter known as a transceiver and is coupled to either a wired connector or an antenna (not illustrated) for the wireline connection or RF wireless transmission network. respectively.
  • these links wired, wireless, cellular, internet, etc. are called the Communication network.
  • the Communication network couples all components together.
  • the server's bank 2-4 comprises server-0 2-11 to server- 2-12.
  • the bank contains at least one server and these servers can be localized, coupled by an intranet, or be physically separated from one another, coupled by the Internet.
  • the Operating System (OS) 2-13 running i the Client Device is closely coupled with the hardware 2-16, especially in case of Mobile Client Devices 1-2,
  • the hardware 2-16 comprises at least one processor 2-5 operating under the Operating System 2-13.
  • the processor 2-5 is coupled to at least one memory 2-7 and at least one communication link 2-9 via at least one bus 2-8.
  • the communicatio link 2-9 couples the Client Device to the outside world throug a wired and/or wireless interconnection via the transceiver.
  • the Client Device offers the user at least one mode of input and one mode of output.
  • One mode of input to the Client Device 1-2 is via the touch based keypad 2-6 or through voice control (not illustrated).
  • the screen 2-10 can be a touch sensitive screen and provide a second mode of input.
  • the screen 2-10 can provide an output response or sound can provide a second mode of output known as voice output (not illustrated).
  • Other hardware components such as MEMS, power supplies, etc, are not mentioned but are well- know by those skilled in the art.
  • a set of applications or Application Clients 2-14 run on the Client Device are coupled to the Operating System 2-13.
  • the Client Device is one of a plurality of Client Devices coupled to the Internet.
  • the Application Store 1-1.0 is coupled to the internet via communication link 2- L
  • FIG. 2B illustrates that when the terra server 2-20 is used, this server is a sub-set representation of a Computer hardware 2-17, which can contain software 2-18, a database 2-1 and the server 2-26 itself. Other components not illustrated are the memory, power supply, etc. One skilled in the art w ould be knowledgeable of the other components contained i n this device and will not be described further. All servers used in this specification are substantially the same as the server 2-20. Furthermore, a plurality of servers and a plurality of databases can be embedded in the Computer hardware 2-17.
  • the term “Client Device” encompasses the device being mobile, non-mobile, or located in the Cloud. However, in some cases, for further distinction within this document the term “Mobile Client Device” will be used for .mobile devices, “ “" Non-Mobile Client Device” will be used tor non- mobile devices and “Cloud Client Device” will be used for the device formed in the Cloud.
  • FIG. 3 A and FIG. 3B present two different types of Application Clients 1-2 and l-2a. This distinction is especially relevant in the case of mobile Clien t Devices, but is also applicable to non- mobile Client Devices.
  • FIG. 3A shows a Native Application Client and how it relates to the layered stacks of the hardware software representation of a Client Device.
  • the Native Application Client 3- 1 is an executable which runs directly on the Operating System 2-1.3 of the Client Device 1-2, which in turn runs o the hardware 2-16 of the Client Device.
  • the Operating System 2-13 provides a set of system libraries 3-5, which the Native Application Client uses 3-2.
  • the Native Application Client is compiled to ran on the Operating System of the Client Device.
  • the Native Application Client needs to be downloaded to the Client Device and installed on the Client Device in order to run on the Client Device.
  • FIG. 3B shows a Non-Naiive Application Client and how it relates to the iayered stacks of the hardware/software representation of a Client Device.
  • the Non-Native Application Client 3-lh does not run directly on the Operating System 2-13h of the Client Device, but instead uses a web browser 3-3 installed on the Client. Device in order to nun.
  • the Non-Native Application Client 3-l h is written in a programming language that is understood by the web browser running on the Client Device. The most common example of such a. language is HTML5, The web browser running on the Client Device contains a.
  • the Operating System 2-!3h runs on the hardware 2-16h [0010]
  • the terra "Application Client” refers to the portion of the application running on. the Client Device.
  • the term “Application Client” encompasses the Application Client running on a mobile Client Device, a non-mobile Client Device or even in the Cloud.
  • the Cloud can ru a portion of the Applicatio Client in the server while the remaining portion of the Application Client c an run on the Client Device, simultaneously.
  • the term “Application Client” is used to refer io both Native and Non-Native Application Client.
  • the term “Mobile Application Client” will e used for both Native and Non-Native Application Clients running on a mobile Client Device, but it also applies to Client Devices that are non-mobile or in the Cloud.
  • the Native Application Client is downloaded to the Client Device, it is installed on the Client Device so it can run on the Operating System of the Client Device.
  • the client now contains a "native" application coupled to the Operating System 2-13 (see FIG. 2A) of the Client Device,
  • the Native Mobile Application Client executable depends on the Operating System (OS) as an iPhone would require a different executable than an Android lM phone.
  • An existing Native Application Client 3-1 cannot manage the update process, but must rely on an external installation manager software or update manager software running on the Operating System of the Client Device to delete the existing ative Application Client, download and re-install the updated Native Application Client 4-7, and complete the update process,
  • the single executable is downloaded and installed on the Client Device, the functionality of the plurality of Native Application Clients is downloaded to the Client Device from an Application Server that is part of the System Solution or is owned by the Business Entity while a first Native Applic tion Client in the Plurality of Native Application Clients is running on the Client Device.
  • a preferred embodiment of the invention is a method to generate a Native Application Client which consists of a common Native Layer which runs directly on the Operating System of the Client Device and is downloaded from the Application Store, and a plurality of Dynamic Layers, which .run on the common Nati ve Layer and can be downloaded from the Application. Store, but can also be downloaded directly f om an application server which is part of the System Solution or owned by the Business Entity while the Native Application Client is running on the Client Device.
  • the functionality provided by the common Native Layer together with a first Dynamic Layer in the plurality of Dynamic Layers provides a first User Experience that the Native Application Client offers to the user on the Client Device.
  • the entire plurality of Dynamic Layers can be downloaded from an application server thai is part of the system solution or is owned by the Business Entity and stored in the Client Device.
  • the entire plurality of User Experiences corresponding to the plurality of Dynamic Layer is stored in the Client Device, and a first User Experience in the plurality of User Experiences is substituted by a second User Experience in the plurality of User Experiences while the Native Application Client is running on the Client Device.
  • the plurality of Dynamic Layers is stored in an application server that is part of the system solution or is owned by the Business Entity and is downloaded to the Client Device only when it is eeded to be displayed to the end user on the
  • the plurality of Dynamic Layers is stored in an application server that is part of the system solution or is owned by the B siness Entity and only the portion of the Dynamic Layer that needs to be displayed to the end user is downloaded to the Client Device, at the time when it is needed to be displayed to the end user.
  • the Native Application Client and the application server optimize the bandwidth utilization of the communication link between the Client Device and server and optimize the storage of the Native Application Client data on the Client Device.
  • a first Dynamic Layer in the plurality of Dynamic Layers is selected to be displayed to the end user while the common Native Layer is running on the Client Device based on a first condition that is evaluated by the common Native Layer while it is running on the Client Device, and a second Dynamic [.aver in. the plurality of Dynamic Layers is selected to be displayed to the end user while the common Native Layer is running on the Client Device based on second condition that is evaluated by the common Native Layer while it is running on the Client Device,
  • Another preferred embodiment of the preferred invention includes the apparatus comprising Computing devices with dedicated servers running the System Solution that, based on the a Service Representation selected by the Business Entity and a Business Entity Data, runs an. Automatic Data Model Generator, This Automatic Data Model Generator places the widely varying and random data positioning from any Business Entity into a. well-defined Data Model which acts as an interface between the Automatic Data Model Generator and an Automatic Application Generator.
  • the Automatic Application Generator uses the data from tire Data Model to automatically generate an Application comprising a plurality of Application Components, including an Application Server., a set of Two-Layer Native Mobile Applicatio Clients supporting a plurality of Dynamic Layers that run on a common Native Layer, a set of Two-Layer Non-Native Non-Mobile Application Clients supporting a plurality of Dynamic Layers that run on a common Native Layer, Non Native Mobile Application Clients, Client server protocol, dashboards and other components.
  • the plurality of Dynamic Layers implements a plurality of User Experiences running on the Native and Non-Native Application Clients.
  • the plurality of Dynamic Layers of the Native Mobile and Non-Mobile Application Clients in the set of generated Two-Layer Native Mobile and Non-Mobile Application Clients can be downloaded to the Client Devices using the generated Application Server and the generated Client server protocol.
  • the generated Dashboards can be used by the Business Entity to modify the Dynamic Layers in the pluralities of Dynamic Layers in the Two-Layer Native Mobile Applicatio Clients and the Two-Layer Native Non-Mobile Application Clients, and to modify the Non-Native Application Clients.
  • the generated Dashboards can be used by the Business Entity to add new Dynamic Layers to the pluralities of Dynamic Layers in the Two-Layer Native Mobile Application Clients and the Two-Layer Native Non-Mobile Application Clients, and to modify the Non-Native Application Clients.
  • Another preferred embodiment of the invention is a method offered to a plurality of Business Entities to generate a. plurality of Native Application Clients which share a common Native Layer which runs directly on the Operating System of the Ciient Device and is downloaded from the Applicatio Store, and a plurality of Dynamic Layers, which run on the shared common Native Layer,
  • the functionality provided by the shared common Native Layer together with a first ' Dynamic Layer in the plurality of Dynamic Layers provides the functionality of a first Native Application Client
  • the functionality provided by the shared common Native Layer together with a second Dynamic Layer in the plurality of Dynamic Layers provides the functionality of a second Native Application Client
  • the functionality of the plurality of Native Application Clients can be downloaded directly from an application server which is part of the System Solution or owned by the Business Entity while a first Native Application Client in the plurality of Native Application Clients is running on the Client Device.
  • the functionality of the entire plurality of Native Applicatio Clients can be downloaded from an application server that is part of the system solution or is owned by the Business Entity and stored in the Client Device.
  • the entire plurality of Native Application Clients is stored in the Client Device, and a first Native Application Client in the plurality of User Experiences is substituted by a second Native Application Client, in the plurality of Native Application Client while the first Native Application Client is running on the Client Device.
  • the functionality of the plurality of Native Application Clients is stored in an application server tha is part of the system solution or is owned by the Business Entity and is downloaded to the Client Device onl when it is needed to be displayed to the end user on the Client Device.
  • the functionality of the plurality of Native Application Clients is stored in an application server that is part of die system solution or is owned by the Business Entity and only the portion of the functionality of the Native Application Clients that needs to be displayed to the end user is downloaded to the Client Device, at the time when it is needed to be displayed to the end user.
  • the Native Application Client and the application server optimize the bandwidth utilization of the communication link between the Client Device and server and optimize the storage of the Native Application Client data on the Client Device.
  • a first Native Application Client in the plurality of Native Application Clients is selected to be run on the Client Device while the shared common Native Layer is running on the Client Device based on a first condition that is evaluated by the common Native Layer while it is running on the Client Device, and a second Nati ve Application Client in the plurality of Native Application Clients is selected to be displayed to the end user while the common Native Layer is running on the Client Device based on a second condition that is evaluated by the common Nati e Layer while it is running on the Client Device.
  • Another preferred embodiment of the invention includes the apparatus comprising Computing devices with dedicated servers running the System Solution that, based on a plurality of Service Representation selected by a plurality of Business Entity and a plurality of Business Entities Data, runs an Automatic Data Model Generator.
  • This Automatic Dat Model Generator places the widely varying and random data positioning from the plurality of Business Entities into a well- defined Data Model which acts as an interface ' between, the A utomat i c Data Model Generator and an. Automatic Application Generator.
  • the Automatic Application Generator uses the data from the plurality of Data Model to automatically generate a plurality of Applications comprising a plurality of Application Components, each Application in the plurality of Applications including an Application Server, a set of Two-Layer Native Mobile Application Clients, a.
  • the Native Application Clients in the sets of generated Native Mobile and Non-Mobile Application Clients for different Applications in the plurality of generated Application share a common Native Layer.
  • the plurality of Dynamic Layers implements a plurality of Native Application Clients running o the shared common Native Layer, For each Application in the plurality of Applications, the Dynamic Layer of the Native Mobile and Non- Mobile Application Clients in the set of generated Two-Layer Native Mobile and Non-Mobile Application Clients can be downloaded to the Client Devices using the generated Application Server and the generated Client server protocol.
  • the generated Dashboards can be used by the Business Entities to modify the Dynamic Layers in the pluralities of Native Application Clients in the Two-Layer Native Mobile Application Clients and the Two-Layer Native Non-Mobile Application Clients, and to modify the Non-Native Application Clients.
  • the generated Dashboards can be used by the Business Entities to add new functionality to the pluralities of Native Application Clients in the Two-Layer Native Mobile Application Clients and the Two-Layer Native Non-Mobtle Application Clients, and to modify the Non-Native Application Clients.
  • Another preferred embodiment of the in vention includes a method to offered to a plurality of Business Entities to generate a plurality of Native Application Clients which share a common Native Layer which runs directly on the Operating System of the Client Device and is downloaded from the Application Store, and a plurality of Dynamic Layers, which can run on the shared common Native Layer at the same time.
  • Another preferred embodiment of the invention is a method offered to a plurality of Business Entities to generate a plurality of Native Application Clients which share a common Native Layer which runs directly on the Operating System of the Client Device and is downloaded from the Application Store, and a plurality of Dynamic Layers.
  • a second Dynamic Layer in the plurality of Dynamic Layers runs on a first Dynamic Layer in the plurality of Dynamic Layers, which in turn runs on the common Native Layer.
  • the functionality provided by the shared common Native Layer together with the first Dynamic Layer in the plurality of Dynamic Layers provides the functionality of a first Nati ve Application Client.
  • the functionality provided by the shared common Native Layer together wit the first and second Dynamic Layer in the plurality of Dynamic Layers provides the functionality of a second Native Application Client.
  • the Dynamic Layers in the plurality of Dynamic Layers can be stored in the Client Device or can be downloaded to the Client Devices only when they are needed to be displayed to the end user, or only the portions of the Dynamic Layers in the plurality of Dynamic Layers that needs to be displayed to the end user is downloaded to the Client Device.
  • the download of the Dynamic Layers may depend on a condition evaluated automatically in the common Native Layer.
  • a System Apparatus comprising a Client Device with a Two-Layer Native Application Client, a first Operating System, a first hardware, and a first screen, the Two-Layer Native Application Client with a Native Layer and a first Dynamic Layer, and a plurality of first Dynamic Layers stored on the Client Device to offer a Business Entity a way to generate a plurality of User Experiences for the Cl ient Device .
  • the System Apparatus further comprising a plurality of conditions associated with each of the plurality of first Dynamic Layers, and the plurality of conditions are also events based on Client Device location, date, time, network connectivity,, and Client Device state.
  • the System Apparatus further comprising a System Solution to automatically generate the Two-Layer Native Application Client that offers a Business Entity a way to generate the plurality of User Experiences.
  • the System Apparatus further comprising a new User Experience from the plurality of User Experiences stored on the Client Device is automatically generated by the Two-Layer Native Application Client based on a new condition from a plurality of conditions.
  • the System Apparatus further comprising a Download manager located in the Native Layer of the Client Device, a plurality of second Dynamic Layers stored on an Application Server to offer the Business Entity a way to generate a second plurality of User Experiences for the Client device, the Two-Layer Native Application Client automatically downloads at least one new Dynamic Layer from tire Application Server to generate at least one new User Experience from the second plurality of User Experiences for the Client Device.
  • the System Apparatus farther comprising a Download manager located in the Native Layer of the Client Device, a plurality of second Dynamic Layers stored on an Appl ication Server to offer the Business Entity a way to generate second plurality of User Experiences for the Client device, the Two-Layer Native Application Client automatically evaluates at least one new condition from a plurality of conditions and based on the evaluated condition downloads at least one new Dynamic Layer from the Application Server to generate at least one new User Experience from the second plurality of User Experiences for the Client Device.
  • the System Apparatus further comprising updated components of Page Surfaces of the at least one new Dynamic Layer are only downloaded to optimize a bandwidth utilization of a communication link between the Client Device and the Application Server.
  • a method of downloading multiple Dynamic Layers comprising the steps of generating a pluralit of Application Clients automatically using a. System Solution with at least one .first server and with at least one Computing device, coupling the plurality of Application Clients to a Client Device where each Application Client in the plurality of Application Clients is a Two-layer native Application Client comprising a Native Layer and a Dynamic Layer, allowing the Native Layer to be a Common Native Layer, and downloading automatically from an Application Server multiple Dynamic Layers corresponding to different Application Clients in the plurality of Application Clients to the Client Device.
  • the method wherein die coupling of the entire plurality of Application Clients is through the coupling of a single Application Client through an Application Store.
  • the method further comprising the steps of allowing a User of the Client Device to select a desired Application and downloading the one desired Dynamic layer of the multiple Dynamic Layers to the Client Device.
  • the method further comprising the steps of using a Download Manager in the Common Native Layer to select the multiple Dynamic layers in the Application Server.
  • the method further comprising the steps of selecting a desired Application based on a plurality of condition at the Client Device, and using a Download Manager in the Common Native Layer to select and download one of the multiple Dynamic layers in the Application Server, and in addition, the method wherei the piuraiity of conditions are also events based on Client Device location, date, time, network connectivity, and Client Device state.
  • the method further comprising the steps of downloading only updated components of Page Surfaces of the multiple Dynamic Layers and optimizing a bandwidth utilization of a communication link between the Client Device and the Application Server.
  • a method of running multiple Dynamic Layers at the same time comprising the steps of generating a plurality of Application Clients automatically using a System Solution with at least one first server and with at least one Computing device, coupling the plurality of Application Clients to a Client Device where each Application Client in the plurality of Application Clients is a Two-layer native Application Client comprising a Native Layer and a plurality of Dynamic Layers, allowing the Native Layer to be a Common Native Layer, downloading automatically from an Application Server at least two or more of a plurality of Dynamic Layers corresponding to different Applications to the Client Device, and running the downloaded the at least two or more of the plurality of Dynamic Layers in a series configuration or a parallel configuration simultaneous ly.
  • the method comprising the steps of running a first of the at least two or more of the plurality of Dynamic Layers on the Common N ative Layer, running at least one of remaining the at least two or more of the piuraiity of Dynamic Layers simultaneously on the Common Native Layer, and forming the parallel configuration, and the method further comprising the steps of achieving multi-tasking between different Applications and allowing a Client Device whic does not support the multi-tasking to support the multi-tasking.
  • ' Hie method wherein a firs portion of the plurality of Dynamic Layers can be stored in the Client Device and the remaining portion of the plurality of Dynamic Layers can he stored in an Application Server.
  • FI * 1A depicts a Client Device coupled to a server and an Application Store and provides some examples of Client Devices.
  • FIG. IB depicts a Client Device coupled to a client/server.
  • FIG. 2A shows a Client Device with a coupling to a bank of servers, an Application Store, and the interna! hardware/software structure- of the Client Device.
  • FIG. 3B illustrates a Non-Native Application Client, and how it relates to the layered stacks of the hardware/software representation of a Client Device.
  • FIG. 4 A shows the flow of how a Native Application Client is approved and downloaded by an Application Store to a Client Device.
  • FIG. 4B illustrates the flow of how a new Updated Native Application Client is approved and downloaded by an Application Store to a Client Device.
  • FIG. 6B presents a Business Entity submitting a Two-Layer Application Client for approval and download to an Application Store for availability to other Device Clients in accordance with the present invention.
  • FIG. 7B illustrates how the Dashboards are used to modify the Dynamic layers in accordance with the present invention.
  • FIG. 8A depicts an Application Client consisting of Pages in accordance with the present invention.
  • FIG. 8B illustrates Page Surface and Page Foundation in accordance with the present invention.
  • FIG. 9A shows an Update Manager continuously checking if there is an. update on the Application Server in accordance with the present invention.
  • FIG. 9B illustrates only the Surface(s) that are updated are downloaded in accordance with the present invention.
  • FIG. 10 depicts the same Application presenting multiple User Experiences dynamically in accordance with the present invention.
  • FIG. J IB depicts the multiple Dynamic Layers being downloaded from the Application Server in accordance with the prese t invention.
  • FIG. IIC illustrates only the updated Page Surface of the multiple Dynamic Layers being downloaded from the Application Server in accordance with the present invention.
  • FIG. ⁇ 2 ⁇ depicts a Client Device can load a given Application User Experience automatically in accordance with the present invention.
  • FIG. 12B shows the Client device selecting the User Experience within the Device in accordance with the present invention.
  • FIG. 12C depicts a Client Device can download a. given Application User Experience automatically front the Application Server in accordance with the present invention.
  • FIG. .13 shows multiple Applications running on the same Native Layer in. accordance with, the present invention.
  • FIG. 14A illustrates one Native laye being downloaded from the Application Store and .multiple Dynamic layers downloaded from the Application Server in accordance with the present invention.
  • FIG. ⁇ 4 ⁇ depicts several Applications stored on ihe Client Device in accordance with the present invention.
  • FIG. 1.4C illustrates severai Applications stored on the Application Server and downloaded as needed in accordance with the present invention.
  • FIG. 14D depicts a Client Device downloading an Application automatically stored on the Application Server and in accordance with the present invention.
  • FIG. 15 illustrates an Umbrella Application which allows the user to select which
  • FIG. 16A depicts Dynamic Layers running on top of each other in the Client Device in accordance with the present invention.
  • FIG. 16B shows DynaiTiic Layers running in parallel with each other in the Client Device in accordance with the present invention.
  • the System Solution offers the ' ownership, control and beneficial use of this inventive idea.
  • the System solution offers the beneficial use to the Business Entity by providing Applications for the Busines Entity.
  • the Applications provided by the System Solutio comprise a plurality of Application Components, and include Native Application Clients that, run on Mobile, Non-Mobile, and Cloud Client Devices. These Native Application Clients can be modified by the Business Entity usina Dashboards and can be downloaded to the Client Devices without the Business Entitv haxdns to submit the modified Native Application Client to the corresponding Application Store.
  • the System Solution is the owner of all Application Components automatically generated by the System Solution.
  • the System Solution creates and hosts Applications for different Business Entities (each Business Entity is a System Solution customer).
  • the System Solution provides a complete environment for the creation, hosting, updating, and management of the Application.
  • the Application Servers generated by the System Solution fo all Business Entities are hosted in a multi- tenant environment in the Cloud, but each Business Entity "feels" like it is provided a dedicated Application Server.
  • the System Solution architecture also applies with minor changes to a scenario where the System Solution Application Server run on dedicated servers owned by the Business Entity, rather than in the C!oud. In this scenario, the System Solution has access to control and offer beneficial use for those servers that are coupled to the Cloud.
  • Each Application includes a family of Application Clients.
  • Each Application Client corresponds to a certain Client Device,
  • the family of Application Clients includes a set of Native Mobile Application Clients, one per mobile platform.
  • the family of Application Clients also includes a set of Native Non-Mobile Application Clients, one per non-mobile platform.
  • the famil of Application Clients also includes Non-Native Mobile and Non-Mobile Application Clients, and Application Clients residing in the Cloud.
  • Some examples of the mobile platforms include the iPhone : , iPad ! ⁇ Android : phones, or tablets while the non-mobile platforms include the Apple Mac Operating System and the Microsoft Windows Operating System.
  • Mobile Application Client or more succinctly Mobile Client to refer to any Mobile Client in the family of Mobile Clients corresponding to an Application generated by the System Solution.
  • a Client Device 1-2 which desires the Two-Layer Native Application Client 5-1 downloads the Two-Layer Native Application Client from the corresponding Application Store 1-1.0. Once the Two-Layer Native Application Client is downloaded to the Client Device, it is installed 6-1 on the Client Device so it can run on the Operating System 2-13 of t e Client Device, The Operating system runs cm the hardware 2-16.
  • the Two-Layer Native Mobile Application Client 5-1 executable depends on the Operating System (OS) as an iPhone would require a different executable than an Android iAl phone. If the Business Entity modifies the Native Layer 5-2, it needs to submit the new version of the Native Layer 5-2 to the Application.
  • OS Operating System
  • the existing version of the Native Layer if running on the Client Device 1-2. must be stopped and deleted from the memory of the Client Device 1-2 in order for the new version of the Native Layer to be installed on the Client Device, The Native Layer cannot be updated "o the fly" while the Two-Layer Nati e Application Client 5- 1 is running on the Client Device 1-2.
  • FIG. 6B illustrates the process of downloading an updated Dynamic Layer 6-3 to the Client Device 1-2
  • the Business Entity 4-1 modifies the functionality of the Dynamic Layer 6-2 and creates an Updated Dynamic Layer 6-3, it can make it available for download directly from an Application Server that is pan of the System Solution or is owned by the Business Entity.
  • the new functionality 6-2 of the Dynamic Layer 5-3 is made available for download to the Client Device by being stored in the Application Server 6-4 without having the Business Entity submit it for approval to the Appiicaiion Store 1-10.
  • the updated Dynamic Layer 6-3 can be downloaded and installed 6-5 in the Client Device 1-2 while the Two-Layer Native Application Client 5-1 is running on the Client Device.
  • the Two-Layer Native Application Client 5-1 can be automatically generated by the Business Entity 4-1 and the generated Dynamic Layer 5-3 of the generated Two-Layer Native Application Client 5-1 can be modified by the Business Entity 4-1 using automatically generated Dashboards 7-14 and made available for download to the Client Device 1-2 on an automatically generated Application Server 7-9 owned by the System Solution or by the Business Entity, without requiring to be re-submitted to the Application Store 1-10 for approval.
  • the generated Client Server Protocols 7-13 can be used to download the modified Dynamic Layers to the Client Device 1-2.
  • FIG. 10 illustrates a Two-Layer Native Application Client I 10-1 which offers to the end user a plurality of Application 1 User Experiences comprising Application 1 User Experience 1 lull to Application 1 User Experience N 10-13.
  • Dynamic Layer i the plurality of available Application 1 Dynamic Layer is downloaded to the Client Device using the Desired Application .1 User Experience i Download 11-3 and the Application 1 Dynamic Layer i 11-4 is run on the Client Device 1-2 so that the Two-Layer Native Application Client 1 10-1 offers the desired Application 1 User Experience i 1.1-5 to the end user.
  • the desired Application 1 Dynamic Layer I 10-4, Layer 2 I0-5, and Layer N 10-6 can be downloaded to the Client Device 1-2 only when it is needed to he displayed to the end user.
  • FIG. 12. shows that the Two-Layer Native Application.
  • Client I 10-1 can Select. Desired Apphcation 1 User Experience 12-2 based on a Condition, Event 12-1.
  • An example of an Event occurring is the Client Device 1-2 changing from being attached to the cellular network to being attached, to the WiFi network (and vice versa).
  • An Application may offer a different User Experiences depending on whether the connectivity is cellular or WiFi.
  • Another example is the Client Device switching to Airplane Mode. In this latter case, the new User Experience corresponding to Airplane Mode must be available on the Client Device before Airplane Mode is turned on (since once in Airplane Mode, there is no connectivity to download it from the Application Server). Time and Date are added as further examples of Conditions or Events.
  • a condition may be of the form IF (date) ⁇ February 14 THEN (select user experience Valentine's Day), or IF (lunch time on a Sunday) THEN (select user experience BRUNCH Application).
  • the Two-Layer Native Application Client 1 10-1 can evaluate a certain condition and, based on the result, select a first Application I Dynamic Layer in the plurality of available Application I Dynamic Layers.
  • the Two-Layer ' Native Application Client 1 10- 1 can identify the occurrence of a certain event and associate the event with the selection of a second Application .1 Dynamic Layer in the plurality of available Application 1 Dynamic Layers.
  • the condition can be the current location of the Client Device.
  • the location can be based on GPS coordinate computed by the client device or other location- determination mechanisms, such as cell-tower or WiFi triangulation.
  • the Two-Layer Native Application Client 1 10- J. computes the current location of the Client Device, if the Client Device location is inside a store, the Two-Layer Native Application Client I 1.0-1 selects a first Application 1 Dynamic Layer 1 10-4; if the Client Device location is not inside a store, the Two-Layer Native Applicatio Client 1 10-1 selects a second Application 1 Dynamic Layer 2 10-5.
  • the Application I Dynamic Layer N 10-6 can be used for a different event. In this way, the Two-Layer Native Application Client 1 offers the end user a User Experience that changes dynamically based on a condition.
  • FIG * 128 shows the selection process depicted in FIG. 12 A when the plurality of Application 1 Dynamic Layers is stored in the Client Device 1-2.
  • Event 12-1 is evaluated, the Select Desired Application I User Experience 12-2 is performed and the desired Application 1 Dynamic Layer 1 10-4 or the desired Application 1 Dynamic Layer N 1.0-6 is loaded via the Selected User Experience load 12-4, replaces the Application Dynamic Layer i 11 -4 and runs in the Two- Layer Native Application Client 1 10-1, This provides the Application 1 User Experience i 1 1-5.
  • FIG. 12C shows the selection process depicted in FIG. 12A when the plurality of Application 1 Dynamic Layers are stored in the Application Server 7-9.
  • the Condition, Event 12-1 is evaluated and the Select Desired Application 1 User Experience 12-2 is performed.
  • the selected desired Application 1 User Experience is communicated to the Download Manager 10-10 in the Native Layer 1 10-7 which uses the Dynamic Download Protocol 11-2 and the List of Desired Page Surfaces 11-9 including Application. 1.
  • FIG. 13 illustrates a plurality of Two-Layer Nati ve Application Clients comprising Two- Layer Native Application Client 1 13-1 to Two-Layer Native Application Client N 13-3.
  • Each Two- Layer Native Application Client in the plurality of Two-Layer Native Application Clients is part of a corresponding Application in a plurality of Applications comprising Application t 13-8 to Application N 13-10.
  • All the Two-Layer Native Application Clients in the plurality of Two-Layer Native Application Clients comprise a Common Native Layer 13-4 and a common Download Manager 10-1.0.
  • a first Two- Layer Native Application Client 1 13-1 corresponds to Application I 13-8 and comprises Application 1 Dynamic Layer 13-5 and Common Native Layer 13-4.
  • Each Application in the plurality of Applications is generated by a Business Entit in a plurality of Business Entities using a method and apparatus such as the one depicted in FIG. 7A.
  • Each Application consists of a plurality of Application Components including a set of Two-Layer Native Application Clients.
  • Each Two-Layer Native Application Client in the set of Two-Layer Native Application Clients corresponding to each Application uses the same Common Native Layer 13-4.
  • Each Two-Layer Native Application Client in the set of Two- Layer Native Application Clients corresponding to a first Application in the plurality of Applications can be modified using corresponding generated Dashboards.
  • the Application I Dynamic Layer of a first Two-Layer Native Application Client 1 corresponding to a first Application 1 can be modified using a .first generated Dashboards and made available for download to the Client Devices using a first generated Application Server and a first generated Client Server Protocols can be used to download the modified Application 1 Dynamic Layer to the Client Device 1-2.
  • FIG. 14A shows that the single Common Native Layer 13-4 needs to be downloaded once from the Application Store 1-10 and installed on the Client Device 1-2 so it can run on the Operating System 2-13 of the Client Device.
  • the Common Native Layer 13-4 executable depends on the Operating System, as an iPhone ! would require a different executable than an Android ! phone. If a Business Entity in the plurality of Business Entities modifies die Common Nati ve Layer 13-4, it needs to submit the new version of the Common Native Layer 13-4 to the Application Store for re-approval in order to make it available for download to the Client Device.
  • the existing version of the Common Native Layer if running on the Client Device 1-2, must be stopped and deleted from the memory of the Client Device 1-2 in order for the new version of the Native Layer 1 to be installed on the Client Device.
  • the Common Nati e Layer 13-4 cannot be updated "on the fly" while a Two- Layer Native Application Client in the plurality of Two-Layer Native Application Clients comprising Two-Layer Native Application Client i 13-1 to Two-Layer Native Application Client N 13-3 is running on the Client Device 1-2,
  • the pl urality of Application Dynamic Layers 13-5 to 13-7 corresponding to die plurality of Applications 13-8 to 13-10 can be downloaded to the Client Device directly from a pluralit of application servers that are pari of the system solution or is owned by the Business Entity.
  • the Business Entit can modify the Application Dynamic Layer of the Application generated b the business solution using the generated Dashboards and make them available for download without having to submit the updated Application Dynamic Layers to the Application Store for approval.
  • FIG. 14B shows a plurality of Applications sharing a Common Native Layer 13-4 where the plurality of Application Dynamic Layers 13-5 to 13-7 for the plurality of Applications is stored on the Client Device 1-2.
  • the plurality of Application Dynamic Layers 13-5 to 13-7 for the plurality of Applications is stored on the Client Device 1-2.
  • different Application in this example Application 1 13-8, in the plurality of Applications is running on the Client Device.
  • FIG. 14C shows a plurality of Applications sharing a Common Native Layer 13-4 where the plurality of Application Dynamic Layers 13-5 to 13-7 for the plurality of Applications is stored on an Application Server 7-9,
  • the Update Manager 10-10 uses a Dynamic Downioad Proioco! 11-2, which is part of the generated Client Server Protocols.
  • the desired Application 1 Dynamic Layer in the plurality of available Application I Dynamic Layers is downloaded to the Client Device using the Desired Application Dynamic Layer Download 14-3.
  • the desired Application Dynamic Layer 1 13-5 can he downloaded to the to the Native Application Client 1 13-1 only when the Application is needed to be displayed to the end user.
  • FIG. 14D shows that the Common Native Layer 13-4 can select to download a certain Application in the plurality of Applications on an Application server 7-9 based on a Condition.
  • Event 12-1 The Condition. Event 12-1 couples to the Select Application 14-4 and informs the Download manager 10-10 to enable the Dynamic Download Protocol 11-2.
  • the Common Native Layer 13-4 can evaluate a certain condition and, based on the result, select a first Application 1 13-8 in the plurality of a vailable Appl ications using the Desired application Dynamic Layer Download 14-3.
  • the Common Native Layer 13-4 can identit the occurrence of a certain event, and. associate the event with the selection of a second Application 2 13-6 in the plurality of available Applications.
  • the condition can be the current location of the Client Device.
  • the Common Native Layer 13-4 computes the current location of the Client Device, if the Client Device location is Inside a first Store A owned by a first Business Entity, the Common Native Layer 13-4 selects and downloads a first Application 1 13-5 generated by the first Business Entity.
  • the Common Native Layer 13-4 selects and downloads a second Application N 13-7 generated by the second Business Entity. In this way, the Client Device 1-2 can automatical ly do wnload and run Appl ications based on a condi tion or on the occ urrence of an event.
  • Application 2 Dynamic Layer 13-6 runs o Application 1 Dynamic Layer 13-5. Using these inventive ideas..
  • Application 2 13-9 uses .functionality provided by Application 1 13-8 as part of its functionality provided to the end. user. The end user can access the functionality provided by Application 1 13-8 using the functionality provided by Application 2 13-9.
  • Both Application 1 Dynamic Layer 13-5 and Application 2 Dynamic Layer 13-6 can be downloaded directly from an Application Server 7-9 owned by the System Solution or by the Business Entities while the Common Native Layer 13-4 is running.
  • a network and a portable system can exchange information wireSessly by using communication techniques such as Time Division Multiple Access fFDMA), Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiplexing (OFDM), Ultra Wide Band (UWB), Wi-Fi, WiGig, Bluetooth, etc.
  • the network can comprise the phone network, IP (Internet protocol) network.
  • LAN Local Area Network
  • ad hoc networks local routers and even other portable systems
  • the term “Mobile Client Device ' " can be used for mobile devices such as cellphone, tablets, etc.
  • Non- Mobile Client Device can be used for non-mobile devices such as desktops.
  • “Cloud Client Device” can be used for the device formed in the Cloud. At other instants the term “Client Device” can imply either the "Mobile Client Device,” “Non-Mobile Client Device” or “Cloud Client Device.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Software Systems (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Game Theory and Decision Science (AREA)
  • Primary Health Care (AREA)
  • Data Mining & Analysis (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)

Abstract

Un système de solution permet à une entité commerciale de générer une pluralité d'expériences utilisateur proposées par une application client native à deux douches, stocke ces expériences dans le dispositif client ou dans un serveur d'applications, et fournit un moyen de télécharger directement, de manière dynamique, des expériences utilisateur tandis que l'application client native à deux couches est exécutée sur le dispositif client. L'application client native à deux couches télécharge automatiquement une première expérience utilisateur sur la base d'une première condition et une deuxième expérience utilisateur dans la pluralité d'expériences utilisateur sur la base d'une seconde condition. Une pluralité d'applications partage une couche native commune et se trouve téléchargée dynamiquement sur le dispositif client. Une première et une seconde application faisant partie de la pluralité d'applications sont exécutées simultanément sur le dispositif client. Le système de solution génère des tableaux de bord utilisés pour modifier dynamiquement les couches dynamiques et des applications faisant partie des pluralités d'applications client natives à deux couches.
PCT/US2014/027024 2013-03-15 2014-03-14 Système d'application client hiérarchique Ceased WO2014152164A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US13/834,765 2013-03-15
US13/833,775 2013-03-15
US13/833,669 2013-03-15
US13/833,775 US10320942B2 (en) 2013-03-15 2013-03-15 Dynamic user interface delivery system
US13/834,765 US20140280481A1 (en) 2013-03-15 2013-03-15 Hierarchical Application Client System
US13/833,589 US10326825B2 (en) 2013-03-15 2013-03-15 Apparatus for single workflow for multi-platform mobile application creation and delivery
US13/833,669 US10320885B2 (en) 2013-03-15 2013-03-15 Method for single workflow for multi-platform mobile application creation and delivery
US13/833,589 2013-03-15
US13/833,849 2013-03-15
US13/833,849 US10075560B2 (en) 2013-03-15 2013-03-15 User interface and content translation system

Publications (1)

Publication Number Publication Date
WO2014152164A1 true WO2014152164A1 (fr) 2014-09-25

Family

ID=51581123

Family Applications (5)

Application Number Title Priority Date Filing Date
PCT/US2014/026981 Ceased WO2014152128A1 (fr) 2013-03-15 2014-03-14 Appareil pour flux de travaux unique destiné à la création et la distribution d'applications mobiles multiplateformes
PCT/US2014/027024 Ceased WO2014152164A1 (fr) 2013-03-15 2014-03-14 Système d'application client hiérarchique
PCT/US2014/026989 Ceased WO2014152136A1 (fr) 2013-03-15 2014-03-14 Appareil pour flux de travaux unique destiné à la création et la distribution d'applications mobiles multiplateformes
PCT/US2014/026995 Ceased WO2014152141A1 (fr) 2013-03-15 2014-03-14 Système de fourniture d'interface utilisateur dynamique
PCT/US2014/027009 Ceased WO2014152149A1 (fr) 2013-03-15 2014-03-14 Interface d'utilisateur et système de translation de contenu

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2014/026981 Ceased WO2014152128A1 (fr) 2013-03-15 2014-03-14 Appareil pour flux de travaux unique destiné à la création et la distribution d'applications mobiles multiplateformes

Family Applications After (3)

Application Number Title Priority Date Filing Date
PCT/US2014/026989 Ceased WO2014152136A1 (fr) 2013-03-15 2014-03-14 Appareil pour flux de travaux unique destiné à la création et la distribution d'applications mobiles multiplateformes
PCT/US2014/026995 Ceased WO2014152141A1 (fr) 2013-03-15 2014-03-14 Système de fourniture d'interface utilisateur dynamique
PCT/US2014/027009 Ceased WO2014152149A1 (fr) 2013-03-15 2014-03-14 Interface d'utilisateur et système de translation de contenu

Country Status (2)

Country Link
EP (2) EP2972814A1 (fr)
WO (5) WO2014152128A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9792014B2 (en) 2013-03-15 2017-10-17 Microsoft Technology Licensing, Llc In-place contextual menu for handling actions for a listing of items
US10949075B2 (en) 2014-11-06 2021-03-16 Microsoft Technology Licensing, Llc Application command control for small screen display
US20160132301A1 (en) 2014-11-06 2016-05-12 Microsoft Technology Licensing, Llc Programmatic user interface generation based on display size
EP3265905A4 (fr) * 2015-03-06 2018-11-21 Cisco Technology, Inc. Systèmes et procédés pour générer des applications de visualisation de données
DE102019201060A1 (de) * 2019-01-29 2020-07-30 Siemens Aktiengesellschaft Verfahren zur rechnergestützten Erzeugung von Betriebssoftware für ein Endgerät und Datenverarbeitungsgerät und Endgerät

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6804718B1 (en) * 1999-03-18 2004-10-12 Kent Ridge Digital Labs Computing system and method for migrating a mobile computing environment
US20060026335A1 (en) * 2004-07-30 2006-02-02 Research In Motion Limited Method and apparatus for provisioning a communications client on a host device
US20100005481A1 (en) * 2004-12-15 2010-01-07 Nokia Corporation Method of Maintaining Applications in a Computing Device
US20110137935A1 (en) * 2000-09-01 2011-06-09 Mark Bobick Server system and method for exporting digital assets in enterprise information systems

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7313782B2 (en) * 2000-05-05 2007-12-25 @Hand Corporation Method for distributing, integrating, and hosting a software platform
US20020078253A1 (en) * 2000-12-20 2002-06-20 Gyorgy Szondy Translation of digital contents based on receiving device capabilities
US7461086B1 (en) * 2006-01-03 2008-12-02 Symantec Corporation Run-time application installation application layered system
US20050044164A1 (en) * 2002-12-23 2005-02-24 O'farrell Robert Mobile data and software update system and method
US20050015361A1 (en) * 2003-07-15 2005-01-20 International Business Machines Corporation Model content provider with reusable components for supporting a plurality of GUI API's
US8006224B2 (en) * 2005-04-15 2011-08-23 Research In Motion Limited System and method for unified visualization of two-tiered applications
SE529490C2 (sv) * 2005-12-19 2007-08-28 Smarttrust Ab Förfarande och system för formatering av provisioneringsinnehåll i ett mobilt apparathanteringssystem
US20070150816A1 (en) * 2005-12-22 2007-06-28 Innopath Software, Inc. User interface authoring utility for changing user interface elements on wireless devices
US8561048B2 (en) * 2005-12-29 2013-10-15 Sap Ag Late and dynamic binding of pattern components
US8904342B2 (en) * 2007-05-25 2014-12-02 Zoot Enterprises, Inc. System and method for rapid development of software applications
US8020144B2 (en) * 2007-06-29 2011-09-13 Microsoft Corporation Metadata-based application deployment
AU2008229743A1 (en) * 2007-10-03 2009-04-23 Britesoft Solutions (M) Sdn Bhd Cutomizable Application System
US20100124939A1 (en) * 2008-11-19 2010-05-20 John Osborne Method and system for graphical scaling and contextual delivery to mobile devices
US9336023B2 (en) * 2009-12-18 2016-05-10 Sybase, Inc. Visual generation of mobile applications based on data models
US8719776B2 (en) * 2009-12-30 2014-05-06 Foneclay, Inc. System for creation and distribution of software applications usable on multiple mobile device platforms
US8692851B2 (en) * 2010-01-06 2014-04-08 Apple Inc. Device, method, and graphical user interface with grid transformations during device rotation
US20120174079A1 (en) * 2010-06-23 2012-07-05 Ansca, Inc. Systems and methods for simulating a mobile device application
CN102647336B (zh) * 2011-02-22 2016-09-07 瑞昱半导体股份有限公司 用于封包内容转换的方法以及网络装置
US8261231B1 (en) * 2011-04-06 2012-09-04 Media Direct, Inc. Systems and methods for a mobile application development and development platform
US8903897B2 (en) * 2011-07-08 2014-12-02 Google Inc. System and method for providing interactive content to non-native application environments

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6804718B1 (en) * 1999-03-18 2004-10-12 Kent Ridge Digital Labs Computing system and method for migrating a mobile computing environment
US20110137935A1 (en) * 2000-09-01 2011-06-09 Mark Bobick Server system and method for exporting digital assets in enterprise information systems
US20060026335A1 (en) * 2004-07-30 2006-02-02 Research In Motion Limited Method and apparatus for provisioning a communications client on a host device
US20100005481A1 (en) * 2004-12-15 2010-01-07 Nokia Corporation Method of Maintaining Applications in a Computing Device

Also Published As

Publication number Publication date
EP2972814A1 (fr) 2016-01-20
WO2014152136A1 (fr) 2014-09-25
WO2014152141A1 (fr) 2014-09-25
EP2972813A1 (fr) 2016-01-20
WO2014152149A1 (fr) 2014-09-25
WO2014152128A1 (fr) 2014-09-25

Similar Documents

Publication Publication Date Title
EP3926468B1 (fr) Application de gestion d'application
US11375045B2 (en) Dynamic user interface delivery system
WO2014152164A1 (fr) Système d'application client hiérarchique
US10243875B2 (en) Cloud service management system
CN109582441A (zh) 用于提供容器服务的系统、方法和装置
CN103370689A (zh) 跨环境应用兼容
US8972592B1 (en) Extending an interface pack to a computer system
CN102770870A (zh) 专用网络文件服务器
JP2014522542A (ja) ユーザー・インターフェース・オブジェクトの自動変換およびコード生成
CN103677860B (zh) 一种用于更新浏览器的方法和设备
US9286054B2 (en) Deployment of mobile enterprise application platform
JP4813331B2 (ja) 移動体電子装置
US11363118B2 (en) User interface and content translation system
CN102752369A (zh) 电视应用服务的提供方法及虚拟化内容服务平台
KR101907837B1 (ko) 애플리케이션 활성화 프레임워크
JP2014518417A (ja) インタプリター型ランタイム・アプリケーションを多数のクライアントに適応させる技法
US20140280481A1 (en) Hierarchical Application Client System
EP2339459B1 (fr) Procédé, système et appareil pour installer un logiciel dans un dispositif électronique mobile via un serveur proxy
US9798586B2 (en) Method and apparatus for providing mashup service of component services
US20160378440A1 (en) Using a version-specific resource catalog for resource management
CN102983985B (zh) 客户端安装方法及系统
CN120826669A (zh) 计算实例的系统选择的可互换可配置属性
JP2007003742A (ja) 地図データ配信システム、方法、携帯端末
GB2503571A (en) Enabling updates of a mobile application

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14770779

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 20/11/2015)

122 Ep: pct application non-entry in european phase

Ref document number: 14770779

Country of ref document: EP

Kind code of ref document: A1