Hereinafter, the embodiments will be described in detail with reference to the drawings. In order to more clearly describe the features of the embodiments, a detailed description will be omitted with respect to the matters widely known to those skilled in the art to which the following embodiments belong.
In this embodiment, the term " module " is used to mean software, hardware, or a combination of both. For example, the software may be machine language, firmware, embedded code, and application software. Also, for example, the hardware can be a design circuit, a processor, a computer, an integrated circuit, an integrated circuit core, a pressure sensor, an inertial sensor, a microelectromechanical system (MEMS), a passive element,
Referring to Figure 1, a computing system 100 supporting an ecosystem mechanism according to the present embodiment is shown. The computing system 100 includes a first device 102 such as a client device or server, a second device 106 connected to a first device 102, such as a client device or server, and a content device 108.
The content device 108 may communicate with the first device 102, the second device 106, or a combination thereof via a wireless or wired communication path 104. The first device 102 may also communicate with the second device 106 via the communication path 104. The content device 108 may provide a content repository service 110.
The computing system 100 provides an echo system 112 for a first device 102, a second device 106, a content device 108, or a combination thereof. The eco system 112 is a collection of products, businesses, etc., or a combination thereof, that functionally coexist. Eco system 112 includes a common technical platform for these products, businesses, etc., or a collection thereof. Ecosystem 112 provides a common development environment for developers to create solutions for ecosystem 112, rather than specific products. The eco system 112 includes a set of products, which are the first device 102 and the second device 106, as shown. As an example, these products may share the same goals and applications from a software point of view, although they may differ in the resource capabilities of the hardware platform running the product.
The application package 114 is an application structured to operate with the eco system 112. For example, the application package 11 is structured to run on any device in a portion of the ecosystem 112. Details of the application package 114 are described in more detail in FIG.
The content device 108 may be directly or indirectly coupled to the first device 102, the second device 106, or a combination thereof, for communication via the communication path 104, or may be connected directly to a stand- Can be connected and communicated. The first device 102 may be directly or indirectly connected to the second device 106 directly or indirectly or directly to the second device 106 for communicating directly or indirectly via the communication path 104.
An administrator 116 is shown in FIG. The administrator 116 may manage the computing system 100 or ecosystem 112 as a domain to be managed. In addition, manager 116 may represent a manage print service provider (MPS).
For convenience of description of the present embodiment, computing system 100 is depicted as a first device 102, such as a multifunction device, a desktop computer, and a cloud, based on a computing system. Here, the first device 102 may be other kinds of devices. For example, the first device 102 may also be a mobile device as well as a stationary device.
For purposes of describing the present embodiment, computing system 100 is shown with a second device 106, such as a computer tablet, a smartphone, and a notebook computer. Here, the second device 106 may be other types of devices. For example, the second device 106 may also be a mobile device as well as a stationary device.
Although the computing system 100 may provide an echo system 112 of different configurations, for purposes of describing the present embodiment, the computing system 100 may include a portion of the echo system 112 The first device 102 and the second device 106 will be described. For example, the first device 102, the second device 106, or a combination thereof may be external rather than part of the ecosystem 112. Also, for example, some of the illustrated first device 102 and second device 106 may be part of echo system 112, while others may not be part of echo system 112.
The content device 108 may be a centralized or decentralized variety of computing systems. For example, the content device 108 may be a centralized location, a server, a storage system, etc., or a combination thereof, in different locations of the building or in different locations, such as different geometric locations of the building . The content device 108 may also include other types of computing devices such as grid-computing resources, virtualized computer resources, cloud computing resources, routers, switches, peer-to-peer distributed computing devices, . The content device 108 may be embedded within a telecommunications network.
For convenience of description of the present embodiment, the computing system 100 includes a first device 102, a second device 106, and a content device 108 as endpoints of the communication path 104 Respectively. Here, the computing system 100 may partition the first device 102, the second device 106, the content device 108, and the communication path 104 in different ways as well. For example, the first device 102, the second device 106, the content device 108, or a combination thereof may function as part of the communication path 104.
The communication path 104 may be extended to various network types and network topologies or may represent various network types and network topologies. For example, the communication path 104 may include wireless communication, wired communication, optical communication, ultrasound communication, or the like, or a combination thereof. Satellite communication, mobile communication, Bluetooth, Infrared Data Association standard (lrDA), WiFi, and WiMAX (worldwide interoperability for microwave access) are examples of wireless communications that may be included in communication path 104. Ethernet, digital subscriber line (DSL), fiber to the home (FTTH) and plain old telephone service (POTS) are examples of wired communications that may be included in communication path 104. Further, the communication path 104 may traverse many network topologies and distances. For example, the communication path 104 may be a direct connection, a personal area network (PAN), a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN) . ≪ / RTI >
FIG. 2 is a block diagram of computing system 100. FIG. The computing system 100 may include a first device 102, a communication path 104, a second device 106, and a content device 108. The first device 102 may transmit information to the second device 106 via the communication path 104. [ The second device 106 may transmit information to the first device 102 via the communication path 104. [
Although the first device 102 in the computing system 100 is shown as a fixed device for purposes of describing the present embodiment, the first device 102 in the computing system 100 may be another type of device. For example, the first device 102 may be a mobile device.
The second device 106 in the computing system 100 may be another type of device although the second device 106 is shown as a mobile device for purposes of describing the present embodiment. For example, the second device 106 may be a fixed device.
For convenience of description of this embodiment, it is assumed that the first device 102 is a fixed type device and the second device 106 is a mobile device. However, the present embodiment is not limited thereto, and the first device 102 and the second device 106 may correspond to other types of devices.
The first device 102 may include a first control unit 212, a first storage unit 214, a first communication unit 216, and a first user interface 218. The first control unit 212 may include a first control interface 222. The first control unit 212 may execute first software 226 that provides intelligence of the computing system 100.
The first control unit 212 may be implemented in many different ways. For example, the first controller 212 may be a processor, an application specific integrated circuit (ASIC), an embedded processor, a microprocessor, hardware control logic, a hardware finite state machine (FSM) (digital signal processor), or the like, or a combination thereof. The first control interface 222 may be used for communication between the first control unit 212 and other functional components within the first device 102. The first control interface 222 may also be used by the first device 102 to communicate with the outside.
The first control interface 222 may receive information from other functional components or external sources, or may transmit information to other functional components or external destinations. External sources and external destinations refer to sources and destinations external to the first device 102.
The first control interface 222 may be implemented in different ways and may be implemented in different ways depending on the functional or external components that are interfaced with the first control interface 222 . For example, the first control interface 222 may be a pressure sensor, an inertial sensor, a microelectromechanical system (MEMS), an optical circuit, waveguides, wireless circuitry, wireline circuitry, Can be implemented in combination.
The first storage 214 may store the first software 226. The first storage 214 may also store related information, such as data representing an image being received, data representing a previously existing image, a sound file, etc., or a combination thereof.
The first storage 214 may be a volatile memory, a non-volatile memory, an internal memory, an external memory, or the like, or a combination thereof. For example, the first storage 214 may be nonvolatile RAM (NVRAM), flash memory, nonvolatile storage such as disk storage, or volatile storage such as static random access memory (SRAM).
The first storage 214 may include a first storage interface 224. The first storage interface 224 may be used to communicate with other functional components within the first device 102. The first storage interface 224 may also be used to communicate with the outside of the first device 102.
The first storage interface 224 may receive other functional components, information from external sources, or transmit information to other functional components, external destinations. External sources and external destinations refer to sources and destinations external to the first device 102.
The first storage interface 224 may be implemented differently depending on the functional or external components that are interfaced with the first storage 214. The first storage interface 224 may be implemented using techniques similar to those of the manner in which the first control interface 222 is implemented.
The first communication unit 216 may enable communication with the outside of the first device 102. [ For example, the first communication unit 216 may be configured to allow the first device 102 to communicate with an attachment, such as a second device 106, a peripheral device, or a desktop computer, .
The first communication unit 216 may also perform the function of a communication hub such that the first device 102 functions as a part of the communication path 104, . ≪ / RTI > The first communication portion 216 may include active and passive components such as microelectronics or antennas for interacting with the communication path 104.
The first communication unit 216 may include a first communication interface 228. The first communication interface 228 may be used for communication between the first communication 216 and other functional components within the first device 102. The first communication interface 228 may receive information from other functional components or may transmit information to other functional components.
The first communication interface 228 may be implemented in different ways depending on the functional components that are interfaced with the first communication 216. The first communication interface 228 may be implemented using techniques similar to those of the manner in which the first control interface 222 is implemented.
The first user interface 218 allows a user (not shown) to interface and interact with the first device 102. The first user interface 218 may include an input device and an output device. Examples of input devices of the first user interface 218 include a keypad for providing data and receiving user input, a touch pad, a soft key, a keyboard, a microphone, an infrared sensor receiving a remote signal, etc., can do.
The first user interface 218 may include a first display interface 230. The first display interface 230 may include a display, a projector, a video screen, a speaker, etc., or a combination thereof.
The first control unit 212 may operate the first user interface 218 to display information generated by the computing system 100. The first control unit 212 may also execute the first software 226 for other functions of the computing system 100. Furthermore, the first control unit 212 can execute the first software 226 to interact with the communication path 104 through the first communication unit 216. [
The second device 106 may be optimized to implement this embodiment with examples of various devices in conjunction with the first device 102. The second device 106 can provide higher performance throughput compared to the first device 102. [ The second device 106 may include a second control unit 234, a second communication unit 236, and a second user interface 238.
The second user interface 238 allows a user (not shown) to interface with and interact with the second device 106. The second user interface 238 may include an input device and an output device. Examples of input devices of the second user interface 238 include a keypad for providing data and receiving user input, a touch pad, a soft key, a keyboard, a microphone, an infrared sensor receiving a remote signal, etc., can do. Examples of output devices of the second user interface 238 may include a second display interface 240. The second display interface 240 may include a display, a projector, a video screen, a speaker, etc., or a combination thereof.
The second control 234 may execute the second software 242 to provide intelligence of the second device 106 of the computing system 100. The second software 242 may operate in cooperation with the first software 226. [ The second control unit 234 may provide additional performance as compared with the first control unit 212.
The second control unit 234 may operate the second user interface 238 to display the information. The second control unit 234 may also be used for other functions of the computing system 100 including the function of the second communication unit 236 to communicate with the first device 102 via the communication path 104, The second software 242 can be executed.
The second control unit 234 may be implemented in many different ways. For example, the second controller 234 may be a processor, an embedded processor, a microprocessor, hardware control logic, a hardware finite state machine (FSM), a digital signal processor (DSP) Or a combination thereof.
The second control unit 234 may include a second control interface 244. The second control interface 244 may be used for communication between the second control unit 234 and other functional components within the second device 106. The second control interface 244 may also be used to communicate with the outside of the second device 106.
The second control interface 244 may receive information from other functional components or from external sources, or may transmit information to other functional components or external destinations. External sources and external destinations refer to sources and destinations external to the second device 106.
The second control interface 244 may be implemented in different ways and may be implemented in different ways depending on the functional or external components that are interfaced with the second control interface 244 . For example, the second control interface 244 may be implemented as a pressure sensor, an inertial sensor, a MEMS, an optical circuit, a waveguide, a wireless circuit, a wired circuit, or the like, or a combination thereof.
The second storage unit 246 may store the second software 242. The second storage 246 may also store related information, such as data representing the image being received, data representing a previously existing image, sound file, etc., or a combination thereof. The second storage unit 246 may have a size that provides additional storage capacity for supplementing the first storage unit 214.
The second storage unit 246 may be implemented with distributed storage components, but is shown as a single component for convenience of description of the present embodiment. The computing system 100 is shown as a second storage unit 246 as a single hierarchy storage system, but the computing system 100 may have a second storage unit 246 having a different configuration. For example, the second storage unit 246 may include other storage technologies such as a different level of caching, a main memory, a rotating media, or a memory hierarchal system including off- . ≪ / RTI >
The second storage unit 246 may be a volatile memory, a non-volatile memory, an internal memory, an external memory, or the like, or a combination thereof. For example, the second storage unit 246 may be nonvolatile RAM (NVRAM), flash memory, nonvolatile storage such as disk storage, or volatile storage such as static random access memory (SRAM).
The second storage unit 246 may include a second storage interface 248. The second storage interface 248 may be used to communicate with other functional components within the second device 106. The second storage interface 248 may also be used to communicate with the outside of the second device 106.
The second storage interface 248 may receive other functional components, receive information from external sources, or transmit information to other functional components, external destinations. External sources and external destinations refer to sources and destinations external to the second device 106.
The second storage interface 248 may be implemented differently depending on the functional or external components that are interfaced with the second storage 246. The second storage interface 248 may be implemented using techniques similar to those of the manner in which the second control interface 244 is implemented.
And the second communication unit 236 can enable communication with the outside of the second device 106. [ For example, the second communication unit 236 may enable the second device 106 to communicate with the first device 102 via the communication path 104. [
The second communication unit 236 can also perform functions of a communication hub such that the second device 106 functions as a part of the communication path 104, . ≪ / RTI > The second communication portion 236 may include active and passive components such as microelectronics or antennas for interacting with the communication path 104.
The second communication unit 236 may include a second communication interface 250. The second communication interface 250 can be used for communication between the second communication unit 236 and other functional components in the second device 106. [ The second communication interface 250 may receive information from other functional components or may transmit information to other functional components.
The second communication interface 250 may be implemented in different ways depending on the functional components that are to be interfaced with the second communication unit 236. The second communication interface 250 may be implemented using techniques similar to those of the manner in which the second control interface 244 is implemented.
The first communication unit 216 may be connected to the communication path 104 to transmit information to the second device 106. The second device 106 can receive the information of the second communication unit 236 from the communication path 104. [
The second communication unit 236 may be connected to the communication path 104 to transmit information to the first device 102. The first device 102 can receive the information of the first communication unit 216 from the communication path 104. [ The computing system 100 may be operated by a first control unit 212, a second control unit 234, or a combination thereof. The second device 106 may be partitioned to have a second user interface 238, a second storage unit 246, a second control unit 234, and a second communication unit 236, for convenience of description of the present embodiment. ), But the second device 106 may also be differentiated. For example, the second software 242 can differentiate the functions of some or all of the second control unit 234 and the second communication unit 236 from each other. In addition, the second device 106 may also include other functional components not shown in FIG.
The content device 108 may include a content control unit 252, a content storage unit 254, a content communication unit 256, and a content user interface 258. The content control unit 252 may include a content control interface 262. The content control unit 252 may execute the content software 266 to provide the intelligence of the computing system 100 and to provide the content storage service 110.
The content control unit 252 may be implemented in many different ways. For example, the content control unit 252 may include a processor, an application specific integrated circuit (ASIC), an embedded processor, a microprocessor, hardware control logic, a hardware finite state machine (FSM) digital signal processor), or the like, or a combination thereof. The content control interface 262 may be used for communication between the content control unit 252 and other functional components within the content device 108. [ The content control interface 262 may also be used by the content device 108 to communicate with the outside.
The content control interface 262 may receive information from other functional components or external sources, or may transmit information to other functional components or external destinations. External sources and external destinations refer to sources and destinations external to the content device 108.
The content control interface 262 may be implemented in different ways and may be implemented in different ways depending on the functional components or external components that are interfaced with the content control interface 262 . For example, the content control interface 262 may be implemented as a pressure sensor, an inertial sensor, a MEMS, an optical circuit, a waveguide, a wireless circuit, a wired circuit, or the like, or a combination thereof.
The content storage unit 254 may store information for the content software 266 and the content storage service 110. Content store 254 may also store related information, such as data representing an image being received, data representing a previously existing image, sound file, etc., or a combination thereof.
The content storage unit 254 may be a volatile memory, a non-volatile memory, an internal memory, an external memory, or the like, or a combination thereof. For example, the content storage unit 254 may be non-volatile RAM (NVRAM), flash memory, non-volatile storage such as disk storage, or volatile storage such as SRAM.
The content storage unit 254 may include a content storage interface 264. The content storage interface 264 may be used to communicate with other functional components within the content device 108. The content storage interface 264 may also be used to communicate with the outside of the content device 108.
The content storage interface 264 may receive other functional components, receive information from external sources, or transmit information to other functional components, external destinations. External sources and external destinations refer to sources and destinations external to the content device 108.
The content storage interface 264 may be implemented differently depending on the functional or external components that are interfaced with the content storage 254. [ The content storage interface 264 may be implemented using techniques similar to those of the manner in which the content control interface 262 is implemented.
The content communication unit 256 may enable communication with the outside of the content device 108. [ For example, the content communication unit 256 may enable the content device 108 to communicate with the first device 102, the second device 106, the communication path 104, or a combination thereof.
The content communicator 256 can also perform functions of a communication hub such that the content device 108 functions as a part of the communication path 104 and is not limited thereto and may correspond to the endpoint or end of the communication path 104 . The content communicator 256 may include active and passive configurations such as microelectronics or antennas for interacting with the communication path 104.
The content communication unit 256 may include a content communication interface 268. The content communication interface 268 may be used for communication between the content communication unit 256 and other functional components within the content device 108. [ The content communication interface 268 may receive information from other functional components or may transmit information to other functional components.
The content communication interface 268 may be implemented in different ways depending on the functional components that are interfaced with the content communication unit 256. The content communication interface 268 may be implemented using a technique similar to that of the manner in which the content control interface 262 is implemented.
The content user interface 258 allows a user to interface and interact with the content device 108. [ The content user interface 258 may include an input device and an output device. Examples of input devices of the content user interface 258 include a keypad for providing data and receiving user input, a touch pad, a soft key, a keyboard, a microphone, an infrared sensor for receiving a remote signal, etc., can do.
The content user interface 258 may include a content display interface 270. Content display interface 270 may include a display, a projector, a video screen, a speaker, etc., or a combination thereof.
The content control unit 252 may operate the content user interface 258 to display information generated by the computing system 100. [ Content control 252 may also execute content software 266 for other functions of computing system 100. Furthermore, the content control unit 252 can execute the content software 266 so as to interact with the communication path 104 through the content communication unit 256.
For convenience of description of the present embodiment, the computing system 100 is described by the operation of the first device 102, the second device 106, and the content device 108. [ According to the present embodiment, it is assumed that the first device 102, the second device 106, and the content device 108 are capable of performing any function of the computing system 100.
The computing system 100 may include resource constraints 280 for the first device 102, the second device 106, the content device 108, or a combination thereof. The resource constraint 280 is for device restriction when the application package 114 is executed on the devices. The resource constraint 280 may apply the first resource constraint 282 for the first device 102 and the second resource constraint 284 for the second device 106. [
The first resource constraint 282 may include the size or availability of the first storage 214, the performance of the first controller 212, the computation power or bandwidth, or the size or resolution of the first display interface 230 . More specifically, the device limitation of the first display interface 230 may be referred to as a first user interface constraint 286. The first user interface constraint 286 may also include a device restriction of the first control 212 for rendering the user interface from the first application 288 running on the first device 102. [ The first application 288 may be a portion of the application package 114, or another instance of the application package 114. The term of the first application 288 may refer to a pointer to an executable file, or an executable file itself.
The first device 102 may include a first product functionality 294 as part of the resource constraint 280. [ The first product function 294 may provide constraints for the type of functions provided to the first device 102. [ For example, if the first device 102 is a fixed device, the first device 102 may be configured to reduce processor speed for battery operation, or to dynamically adjust brightness for different illumination environments, It may not provide the functions required in the mobile environment.
The second resource constraint 284 may include the size or availability of the second storage 246, the capabilities of the second controller 234, the computing power or bandwidth, or the size or resolution of the second display interface 240 . More specifically, the device restriction of the second display interface 240 may be referred to as a second user interface constraint 290. The second user interface constraint 290 may also include a device restriction of the second control 234 for rendering the user interface from the second application 292 running on the second device 106. The second application 292 may be a portion of the application package 114, or another instance of the application package 114. The term of the second application 292 may refer to a pointer to an executable file, or an executable file itself.
The second device 106 may include a second product function 296 as part of the resource constraint 280. [ The second product function 296 may provide constraints for the type of functions provided to the second device 106. If the second device 106 is an example of a mobile device, then the second device 106 may provide various external port connections, or may perform functions required in a stationary environment, such as many hardware extension options, May not be provided.
In the present embodiment, it is assumed that the first application 288 and the second application 292 operate in the first device 102 and the second device 106, respectively. However, the first application 288 and the second application 292 may be performed in different configurations or environments. For example, the first application 288 may operate on the second device 106, or may operate with the second device 106. In addition, the second application 292 may operate on the first device 102, or may operate with the first device 102. Also, according to this embodiment, a portion of the first application 288 or first application 288 may operate on, or operate on, the first device 102, the second device 106, or a combination thereof . A portion of the second application 292 or the second application 292 may operate on or operate on the first device 102, the second device 106, or a combination thereof. The first application 288 or a portion of the first application 288 may be a pointer or a location identification to an executable file for the first application 288 or a portion of the first application 288. [ This will be described in more detail with reference to FIG.
The first application 288 may correspond to a portion of the first device 102, the second device 106, or a combination thereof implemented in hardware or software. Examples of hardware implementations for the first application 288 are similar to those of the first control 212. [ Also, the first application 288 may correspond to a portion of the first software 226, the second software 242, or a combination thereof.
The second application 292 may correspond to a portion of the first device 102, the second device 106, or a combination thereof implemented in hardware or software. Examples of hardware implementations for the second application 292 are similar to those of the second control 234. Further, the second application 292 may correspond to a portion of the first software 226, the second software 242, or a combination thereof. A portion of the second application 292 or the second application 292 may be a pointer or location identification to an executable file for the second application 292 or a portion of the second application 292. [ This will be described in more detail with reference to FIG.
Referring to FIG. 3, an embodiment of an application package 114 for the computing system 100 of FIG. 1 is shown. 1, the application package 114 may be developed with a structure capable of applying products and solutions that are part of the eco system 112 of FIG. 1, although not all of them. The first device 102 and the second device 106 of Fig. 1 may correspond to examples of such products. The structure of the application package 114 allows the application developer to provide product specific solutions within the application package 114 to handle resource constraints 280 associated with the product.
The structure of the application package 114 allows an application developer to associate with other solutions that are part of the ecosystem 112 for a particular solution.
In order for the application package 114 to support the ecosystem 112 with a variety of different products and platforms with different resource requirements and constraints, the structure of the application package 114 may be used by application developers and tools It is possible to create a package for creating a single application package for products and platforms and furthermore allows the application developers and tools the flexibility to provide platform specific content in the same package. 3 is a structural diagram showing the structure of the application package 114. Fig.
The application package 114 may provide an introduction 302 that may provide a name 304 identifying the application 114 and release or build information of the application 114 And may include a release identifier 306. The preamble 302 may also include a provider identification 308 that may represent a provider or publisher of the application package 114 or a release of the application package 114 or application package 114 And a description 310 that can provide a functional description or information guidance regarding the user.
The application package 114 may also include application echo system information 312 for identifying the eco system 112 and portions of the application package 114 or application package 114, if any, The application ecosystem information 312 may enable the application developer to associate with other applications that increase the usability and functionality of applications on other systems (e.g., mobile devices, televisions, printers, PCs, etc.) do.
3, the computing system 100 may include one or more application packages 114, although the application package 114 is shown as being single in FIG. That is, there may be an application package 114 for the first application 288 and another package for the second application 292. The application package 114 may be a first application 288, a second application 292, or a combination thereof, or may be coupled to a pointer, such as a uniform resource indicator (URI), representing them. The application package 114 may include a first application 288, a second application 292, or a combination thereof, or may include only a portion of each.
The application eco system information 312 may include an application eco system type 314. The application echo system type 314 provides details of the application echo system information 312. The application echo system type 314 may be represented by xml nomenclature for the application package 114. The application echo system type 314 may include associated application information 316. The application package 114 may have one or more associated application information 316. There may be one associated application information 316 for all applications associated with the application in the application package 114. [ Each of the associated application information 316 may be used to link different applications, by associating them with each other, such that when a user of the application uses a device (printer, television, mobile device, etc.) with associated software , So that the device can be automatically updated to increase the user experience. Associated application information 316 may be used to associate or associate the first application 288 of FIG. 2 with the second application 292.
The associated application type 315 provides details for the associated application information 316. The associated application type 315 may be represented by the xml nomenclature for the application package 114. The associated application type 315 may include an associated application identifier 318, a platform filter 320 and a platform target identifier 322. Examples of the associated application type 315 are a network function, a scan function, a fax function, a print function, or a graphic user interface (GUI) function. The associated application identifier 318 provides one or more identifiers for associating each of the associated applications to the exemplary eco system 112 from one or more eco systems. The associated application identifier 318 may simply provide a pointer or location for the application associated with the application in the application package 114 or the application package 114 may actually include the associated application rather than just a pointer.
The associated application identifier 318 may represent a first application 288, a second application 292, or a combination thereof. In addition, there may be one or more associated application identifiers 318 to represent other applications for the first application 288 and the second application 292.
The platform filter 320 provides any constraints required by the application on the installed platform. For example, the platform may be operated on either the first device 102 or the second device 106. [ The platform filter 320 may provide a resource constraint 280, a first user interface constraint 286, a second user interface constraint 290, or a combination thereof.
The platform target identifier 322 provides the destination of the specific platform on which the application can be installed. The platform target identifier 322 may be in a different form depending on the associated application type 315. [
Referring back to the application package 114, the application package 114 may also include platform information 324. The platform information 324 provides details of the platforms over which the application package 114 may operate. The platform information 324 may represent information for the first application 288, the second application 292, or a combination thereof. There may be one platform information 324 for the first application 288 and another one for the second application 292. [
Each of the platform information 324 includes a platform type 326. The platform type 326 provides details for the platform information 324. The platform type 326 may be represented by xml nomenclature for the application package 114. The platform type 326 includes a platform identifier 328 for identifying a particular platform. The platform identifier 328 is used to determine if it matches the platform target identifier 322. The platform information 324 may also include a platform restriction 330 that defines restrictions for when a particular platform entry should be used. The platform limit 330 can be used to match the flamform filter 320 by allowing the application to be executed.
In addition, each of the platform information 324 may include application information 332. [ The application information 332 describes the contents of the application. Application information 332 represents information for a first application 288, a second application 292, or a combination thereof. Application information 332 may include an application type 334. The application type 334 provides details of the application information 332. The application type 334 may be represented by the xml nomenclature for the application package 114. The application type 334 may include an ecosystem identifier 336. The echo system identifier 336 may be used to determine whether it matches the application echo system information 312 in other examples of the application package 114 or may be used to determine whether it matches the application identifier 336 in other instances of the application package 114 .
Application information 332 may include an application name 338 used to identify the location and file name of an application installed on the product or device itself or remotely to execute the application. The application name 338 may be provided in many ways. For example, the application name 338 may be described as a uniform resource indicator (URI) and metafilename. The application name 338 may represent a first application 288, a second application 292, or a combination thereof. There may be an application name 388 for the first application 288 and another for the second application 292, such as platform information 324. [
The application information 332 may include other information, such as license information 340 and certificate information 342, if a license or certificate is required to run on the platform, for example . The license information 340 may correspond to a file name or a pointer to a file for license.
Using the following tables, such as examples of architectural aspects of Figure 1, the manager 116 may be configured to perform an auto push (" push ") operation to a user of a given manage domain software, such as an application package 114 associated with an application )can do. Applications associated with ecosystem identifiers 336 may be received from different providers or all from the same provider. The content device 108 or the content storage service 110 of FIG. 1 may receive the application package 114 for processing. The content communication unit 256 may be used to receive the application package 114. [
The eco system 112 can be managed by the administrators at the managed domain level and automatically reflected on all the devices on which the software is installed. The first device 102 and the second device 106 are examples of such devices.
The following tables provide examples of how an application package 114 may be added to the computing system 100. The administrator 116 may install and manage the CounThru package as the application package 114 at the manage domain level. The CounThru package can define the ecosystem 112 to which it is associated. The eco-system 112 for the CounThru package is automatically managed based on settings at the management domain level and is configured for the settings for the content storage service 110, the content device 108 and the content storage 254 of FIG. 2 And the like.
The eco system 112 can be managed by the administrator 116 at the management domain level and automatically reflected in all devices where the software is installed. The first device 102 and the second device 106 are examples of such devices. The following tables may represent information parsed from the application package 114 by the content storage service 110 of the content device 108. The parsing function may be performed by the content control unit 252.
Table 1 provides information describing where the application can be installed and references to the ecosystem. Table 1 shows an example of platform information 324 from an application package 114.
platformID
applicationID
ecosystemID
platformFilter
appDescriptorID
XOA-E
CounTru
CounThruEcosystem
((minLocalUiSize = 10in) && platformVersion = 1.0.0, *))
One
iOS
iOSCounThru
(platformVersion = 5. *. *, *)
2
Android
AndroidCounThru
(platformVersion = 2.3. *, 3. *. *)
3
The first column of Table 1 represents the platform identifier 328. The first column shows examples of platform identifiers such as extensible open architecture (XOA - TM), iOS (Apple 's operating system), and Android (TM - Google' s operating system). As an example, the platform identifier 328 may represent an operating system requirement for an application to be executed for a particular product.
The second column of Table 1 may represent information from application information 332, application type 334 or application name 338 of the URI. In the second column examples of applications such as CounThru (TM), iOSCounThru and AndriodCounThru are shown.
The third column of Table 1 may represent the ecosystem identifier 336. [ According to the first column of the third column, such a specific platform and application is associated with the eco system 112 along with the eco-system identifier 336 of the CounTruEcosystem. The other columns in the third column are empty to indicate that iOSCounThru and AndriodCounThru are not associated with any ecosystem.
The fourth column of Table 1 represents the platform restriction 33. [ The top column of the fourth column contains a first user interface constraint 286 having a minimum local user interface size of 10 inches and a version of platform identifier 328 such as 1.0.0, Constraint 290, or a combination thereof. The other two columns of the fourth column specify the version of the platform identifier 328, respectively.
The fifth column of Table 1 shows the information of application information 332 or application type 334. The information in the columns of the fifth column represents the application identifier and may represent the first application 288, the second application 292, or a combination thereof.
Table 2 below provides information on the echo system 112 that describes other applications that are part of the application echo system. Table 2 describes an example of the application echo system information 312 from the application package 114.
ecoSystemID
asscoiatedApplicationID
platformID
platformFilter
CounThruEcoSystem
AndroidCounThru
Android
(platformVersion-2.3. *, 3. *. *)
CounThruEcoSystem
iOSCounThru
iOS
(platformVersion5. *. *, *)
The first column of Table 2 shows the information of the application echo system type 314. The first two columns indicate the association to the CounThruEcoSystem.
The second column of Table 2 represents the information of the associated application identification 318. The top column indicates that the associated application identifier 318 is AndroidCounThru, and the bottom column indicates that the associated application identifier 318 is iOSCounThru.
The third column of Table 2 shows the information of the platform target identifier 322. The top column of the third column indicates that the platform target identifier 322 is Android, and the bottom column indicates that the platform target identifier 322 is iOS.
The fourth column of Table 2 shows the information of platform limit 330. Each column provides a restriction on the version of the platform.
Table 3 provides examples of application makeup, or examples of what files make up an application. Table 3 provides information corresponding to a part of the platform information 324. Table 3 describes an example of an application type 334 from an application package 114.
appDescriptorID
Content
One
Bundle1.jar
One
Bundle2.jar
One
Bundle3.jar
2
CounThru.ios
3
CounThru.apk
The first column of Table 3 corresponds to the fifth row of Table 1. The second column of Table 3 represents the contents associated with the corresponding identifiers of the first column of Table 3.
Referring to FIG. 4, an example architecture view of a distributed computing system 100 is shown. 4, computing system 100 includes MFP 402, host platform 404, and host cloud platform 406. In this embodiment, multifunction machine 402 may represent XOA-E devices.
When an application is added to the content storage service 110 together with the content device 108 and the content storage 254 of FIG. 2 through the application package 114 of FIG. 3, the computing system 100 distributes the application .
For example, two types of distribution are possible for installation, manual push, and automated distribution. According to the distribution of the manual push, the application is distributed to the system or the first device 102 or the second device 106 of Fig. 1 running the XOA platform, using examples such as the tables of Fig. The XOA devices request installation files for a given application and provide device metadata such as a platform identifier 328 and a resource constraint 280. [ The content storage service 110 returns installable files for a given application and platform. Examples of such installable files may correspond to a first application 288 and a second application 292 resulting from the application package 114. This distribution process is part of the installation process by the content storage service 110, the content device 108, or a combination thereof.
An automated pull distribution enables the creation of an automated management system for all devices involved in a given management domain (or service level agreement). According to automated full distribution, a device agent is installed on devices where software is deployed. For example, the device agent may be configured to perform an automated full distribution of the application to the first device 102, the second device 106, Device 106 or a combination thereof.
For XOA platforms, these agents will be provided to other devices (mobile, tablet, television, etc.) in addition to the second device 106 of FIG. 1 where the agent needs to be installed. Automated full distribution of applications can also be performed on non-XOA systems as long as the device agent is installed on such devices.
For automated full distribution, the manager 116 queries the content storage service 110 to correct content based on parameters sent by the device agent. The device agent gathers an administrative domain application operator service that can be periodically run on the content device 108 for applications on the device based on the administrative domain or ecosystem 112 to which the device belongs.
The computing system 100 may be any application that has a structure of a single application package for all products / solutions in the ecosystem 112, regardless of the resource constraints 280 of the first device 102 or the second device 106. [ Package 114 is provided. The application package 114 provides the capability to provide product specific functionality within the same package. The structure of the application package 114 allows the application developer to define the products that the ecosystem 112 intends / supports. The structure of the application package 114 allows the ecosystem 112 to provide a custom user interface based on the metadata definitions defined within the application package 114 and products accessing the ecosystem 112. The structure of the application package 114 allows the application to provide default preference settings for the application itself and the ecosystem to provide application configuration tools for application configuration prior to development. The structure of the application package 114 enables the " application ecosystem ", in which different applications are respectively associated, to be generated differently. This is so that if the user of the application uses the device associated with the software (printer, television, mobile device, etc.), it is automatically updated to increase the user experience. The structure of the application package 114 provides the ability to provide " smart " services based on defined metadata. This is particularly useful for automatically updating the client that receives the corrected content automatically based on the identifier. The architecture of the application package 114 provides the ability to provide a user interface for filtering applications based on products / platforms and other constraints.
The computing system 100 may provide a single package structure within the application package 114 for all products in the ecosystem 112, provide product-specific functionality within the same package, support application configuration before and after development, Allow developers to define what products are intended / supported in ecosystem 112. This is of great value for developers, end users and ecosystem 112 to provide the following benefits. For the developers, the application package 114 reduces the complexity of managing the solution as a single package / application to be used for all products that are part of the eco system 112, and provides other solutions that are part of the solution ecosystem Provide a mechanism to associate, and increase the usability and functionality of the solution. For end users or consumers, the application package 114 provides a common feature set between products that are part of the eco system 112 and provides a single common package format for all products And makes it easy for users of the solution to have a device (printer, mobile device, PC, television, etc.) that automatically updates the software in the solution ecosystem. At the point of view of the eco system 112, the application package 114 simplifies application management functions, such as reducing the number of applications and versions that need to be managed by the ecosystem, It enables a smart user interface that simplifies tool creation, filters packages based on the client, and enables automatic updates for solution users and all devices with the solution, just as it is one.
The functions described in this embodiment may correspond to the hardware design or hardware accelerator of the first control unit 212 or the second control unit 234 of FIG. These functions may correspond to a hardware design or a hardware accelerator in the first device 102 or the second device 106, rather than the first control unit 212 or the second control unit 234. [
Referring to FIG. 5, an embodiment of a partition of an application package in computing system 100 is shown. For example, referring to FIG. 5, the CounThru application, used with application information 332 in FIG. 3, includes common functions 502 installed on all platforms, or a set of "common" . However, to maximize the use of user interface constraints associated with a given product or platform, the user interface associated with the binary numbers is separated.
The following product and platform constraints depend on the application providing the product functionality. As a more specific example, the product / platform specific functionality is subject to user interface constraints, resource constraints 280 (memory, speed, etc.), and application programming interface (API) constraints.
For ease of description of this embodiment, product / platform constraints have been described for the computing system 100. In addition, the application package 114 may accommodate other types of constraints. For example, additional resources within an application definition may be shared or unique based on constraints. Some of these resources are, for example, binary numbers, scripts, images, fonts and licenses.
Referring to FIG. 6, there is shown a flowchart of an operation method 600 of the computing system 100 according to the present embodiment. The operating method 600 includes a step 602 (block 602) of receiving an application package operating on the first device and a second device and a step 604 (step 604) of parsing the application package for the ecosystem, the first application and the second application (Step 606) of installing a first application operating with the first device and step 608 (step 608) of installing a second application operating with the first application on the second device.
The above-described embodiments of the present invention can be embodied in a general-purpose digital computer that can be embodied as a program that can be executed by a computer and operates the program using a computer-readable recording medium. In addition, the structure of the data used in the above-described embodiments of the present invention can be recorded on a computer-readable recording medium through various means. The computer-readable recording medium includes a storage medium such as a magnetic storage medium (e.g., ROM, floppy disk, hard disk, etc.), optical reading medium (e.g., CD ROM,
The present invention has been described with reference to the preferred embodiments. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.
