Web services device profile on a multi-service device: device and facility manager
First Claim
1. A computer-implemented method for processing requests to process data on multi-functional peripherals (MFPs), the method comprising:
- sending, to a client application, location data of an MFP in a network, wherein;
a plurality of applications execute on the MFP, andeach application of the plurality of applications provides a service among a plurality of services;
receiving, from the client application, at a device facility manager (DFM) that executes on the MFP, a metadata request for metadata associated with the MFP;
sending, from the DFM to the client application, device metadata that indicates the plurality of services;
receiving, from the client application, at a first application of the plurality of applications, a request for service metadata that indicates how the client application is to interact with the first application, on the MFP, that provides a first service of the plurality of services;
receiving, from the first application, at the DFM, a service metadata request that corresponds to the request;
in response to receiving the service metadata request, the DFM;
retrieving the service metadata that corresponds to the first application, andsending the service metadata to the first application;
the first application sending the service metadata to the client application;
receiving, from the client application, at the first application, a first particular request for the first service;
receiving, from a second client application, at second application of the plurality of applications that is different than the first application, a second request for second service metadata that indicates how the second client application is to interact with the second application that provides a second service of the plurality of services that is different than the first service;
receiving, from the second application, at the DFM, a second service metadata request that corresponds to the second request;
in response to receiving the second service metadata request, the DFM;
retrieving the second service metadata that corresponds to the second application, andsending the second service metadata to the second application;
the second application sending the second service metadata to the second client application; and
receiving, from the second client application, at the second application, a second particular request for the second service;
wherein an application from the plurality of applications (a) retrieves, through an abstract application programming interface (API), information pertaining to the MFP, and (b) invokes, through the abstract API, one or more functions on a platform corresponding to the MFP;
wherein the abstract API defines an interface by which the application invokes one or more functions on the MFP and receives data from the MFP.
1 Assignment
0 Petitions
Accused Products
Abstract
A technique is provided for implementing multiple Web services on a multi-functional device (MFP) executing multiple service applications. A Device Facility Manager (DFM) executing on the MFP represents the MFP by responding to discovery, metadata, and logging requests with device location, metadata and logging information. When a client application discovers the services provided by the MFP, the client application may communicate directly with a service application executing on the MFP. The client application requests the service metadata of the service application and then transmits SOAP requests, which the service application processes. The implementation of one or more Web Service specifications may be packaged into one common module so that the complexity of the Web Services is hidden from developers. New services may be added to the MFP and existing services may be updated through communication with the DFM.
-
Citations
36 Claims
-
1. A computer-implemented method for processing requests to process data on multi-functional peripherals (MFPs), the method comprising:
-
sending, to a client application, location data of an MFP in a network, wherein; a plurality of applications execute on the MFP, and each application of the plurality of applications provides a service among a plurality of services; receiving, from the client application, at a device facility manager (DFM) that executes on the MFP, a metadata request for metadata associated with the MFP; sending, from the DFM to the client application, device metadata that indicates the plurality of services; receiving, from the client application, at a first application of the plurality of applications, a request for service metadata that indicates how the client application is to interact with the first application, on the MFP, that provides a first service of the plurality of services; receiving, from the first application, at the DFM, a service metadata request that corresponds to the request; in response to receiving the service metadata request, the DFM; retrieving the service metadata that corresponds to the first application, and sending the service metadata to the first application; the first application sending the service metadata to the client application; receiving, from the client application, at the first application, a first particular request for the first service; receiving, from a second client application, at second application of the plurality of applications that is different than the first application, a second request for second service metadata that indicates how the second client application is to interact with the second application that provides a second service of the plurality of services that is different than the first service; receiving, from the second application, at the DFM, a second service metadata request that corresponds to the second request; in response to receiving the second service metadata request, the DFM; retrieving the second service metadata that corresponds to the second application, and sending the second service metadata to the second application; the second application sending the second service metadata to the second client application; and receiving, from the second client application, at the second application, a second particular request for the second service; wherein an application from the plurality of applications (a) retrieves, through an abstract application programming interface (API), information pertaining to the MFP, and (b) invokes, through the abstract API, one or more functions on a platform corresponding to the MFP; wherein the abstract API defines an interface by which the application invokes one or more functions on the MFP and receives data from the MFP. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A machine-readable storage medium for processing requests to process data on multi-functional peripherals (MFPs), the machine-readable medium storing instructions which, when processed by one or more processors, causes:
-
sending, to a client application, location data of an MFP in a network, wherein; a plurality of applications execute on the MFP, and each application of the plurality of applications provides a service among a plurality of services; receiving, from the client application, at a device facility manager (DFM) that executes on the MFP, a metadata request for metadata associated with the MFP; and sending, from the DFM to the client application, device metadata that indicates the plurality of services; receiving, from the client application, at a first application of the plurality of applications, a request for service metadata that indicates how the client application is to interact with the first application, on the MFP, that provides a first service of the plurality of services; receiving, from the first application, at the DFM, a service metadata request that corresponds to the request; in response to receiving the service metadata request, the DFM; retrieving the service metadata that corresponds to the first application, and sending the service metadata to the first application; the first application sending the service metadata to the client application; receiving, from the client application, at the first application, a first particular request for the first service; receiving, from a second client application, at second application of the plurality of applications that is different than the first application, a second request for second service metadata that indicates how the second client application is to interact with the second application that provides a second service of the plurality of services that is different than the first service; receiving, from the second application, at the DFM, a second service metadata request that corresponds to the second request; in response to receiving the second service metadata request, the DFM; retrieving the second service metadata that corresponds to the second application, and sending the second service metadata to the second application; the second application sending the second service metadata to the second client application; and receiving, from the second client application, at the second application, a second particular request for the second service; wherein an application from the plurality of applications (a) retrieves, through an abstract application programming interface (API), information pertaining to the MFP, and (b) invokes, through the abstract API, one or more functions on a platform corresponding to the MFP; wherein the abstract API defines an interface by which the application invokes one or more functions on the MFP and receives data from the MFP. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A multi-functional peripheral (MFP) for processing requests to process data, the MFP being configured to:
-
send, to a client application, location data of the MFP in a network, wherein; a plurality of applications execute on the MFP, and each application of the plurality of applications provides a service among a plurality of services; receive, from the client application, at a device facility manager (DFM) that executes on the MFP, a metadata request for metadata associated with the MFP; and send, from the DFM to the client application, device metadata that indicates the plurality of services; receive, from the client application, at a first application of the plurality of applications, a SOAP request for service metadata that indicates how the client application is to interact with the first application, on the MFP, that provides a first service of the plurality of services; receive, from the first application, at the DFM, a service metadata request that corresponds to the SOAP request; in response to receiving the service metadata request, the DFM; retrieves the service metadata that corresponds to the first application, and sends the service metadata to the first application; send, from the first application, the service metadata to the client application; receive, from the client application, at the first application, a first particular request for the first service; receive, from a second client application, at second application of the plurality of applications that is different than the first application, a second request for second service metadata that indicates how the second client application is to interact with the second application that provides a second service of the plurality of services that is different than the first service; receive, from the second application, at the DFM, a second service metadata request that corresponds to the second request; in response to receiving the second service metadata request, the DFM; retrieves the second service metadata that corresponds to the second application, and sends the second service metadata to the second application; send, by the second application, the second service metadata to the second client application; and receive, from the second client application, at the second application, a second particular request for the second service; wherein an application from the plurality of applications (a) retrieves, through an abstract application programming interface (API), information pertaining to the MFP, and (b) invokes, through the abstract API, one or more functions on a platform corresponding to the MFP; wherein the abstract API defines an interface by which the application invokes one or more functions on the MFP and receives data from the MFP. - View Dependent Claims (26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36)
-
Specification