JP7243064B2 - Information processing device, program, information processing system and information processing method - Google Patents

Description

The present invention relates to an information processing device, a program, an information processing system, and an information processing method.

Equipment manufacturer companies provide external companies with libraries for acquiring various information from equipment such as MFPs (Multifunction Peripherals) and for requesting the equipment to execute various processes. By using the library provided by the manufacturer company, the external company can obtain various information from the device, and without directly implementing the processing to request the device to execute various processes, You can create your own application that performs processing linked to

Further, there is known an image forming apparatus capable of extending the functions of a framework in which at least a part of an interface such as an API (Application Programming Interface) is open to the public while appropriately maintaining security (for example, Patent Document 1).

By using a library provided by a device manufacturer, it is possible to acquire device information such as the IP (Internet Protocol) address of the device and the data format supported by the device.

However, in an application created by an external company, device information acquired from a device may be rewritten. If the device information is rewritten and inconsistency or the like occurs in the device information, the device may perform an unintended operation.

Embodiments of the present invention have been made in view of the above points, and aim to prevent unauthorized rewriting of information acquired from a device.

In order to achieve the above object, an embodiment of the present invention provides an information processing apparatus having a program that provides a predetermined function, wherein the information processing apparatus is connected to the information processing apparatus in response to a first request from the program. an acquisition unit that acquires information including predetermined information from a device that receives the information, and accesses the information acquired by the acquisition unit to a class that belongs to a package different from the program and updates or refers to the predetermined information. a request control unit that restricts the program from requesting update or reference to the predetermined information by making it a class with no modifiers defined; and responding to a second request from the program. a process corresponding to the second request to the device based on the predetermined information, which is the information acquired by the acquisition unit and for which requests from the program are restricted by the request control unit. and a processing request unit that requests execution of

It is possible to prevent unauthorized rewriting of information acquired from a device.

1 is a diagram showing an example of the overall configuration of a printing system according to a first embodiment; FIG. 2 is a diagram illustrating an example of the configuration of a print application; FIG. It is a figure which shows an example of the hardware constitutions of the terminal device which concerns on 1st embodiment. It is a figure which shows an example of the hardware constitutions of the apparatus which concerns on 1st embodiment. It is a figure which shows an example of the functional structure of the terminal device which concerns on 1st embodiment. It is a figure which shows an example of a device information instance. FIG. 10 is a diagram illustrating an example of a print setting information instance; FIG. FIG. 3 is a diagram illustrating an example of a relationship between a vendor development program package and a print library package; It is a figure which shows an example of a device information class. FIG. 4 is a diagram showing an example of a print setting information class; It is a figure which shows an example of a device information acquisition class. FIG. 4 is a diagram showing an example of a print processing class; FIG. 4 is a diagram showing an example of program code of a vendor development program; 4 is a sequence diagram showing an example of print processing according to the first embodiment; FIG. It is a figure which shows an example of a device confirmation screen. FIG. 10 is a diagram showing an example of the overall configuration of a projection system according to a second embodiment; FIG. FIG. 2 is a diagram illustrating an example of the configuration of a projection application; FIG. It is a figure which shows an example of a functional structure of the terminal device which concerns on 2nd embodiment. It is a figure which shows an example of a device information instance. FIG. 10 is a diagram showing an example of a projection setting information instance; FIG. 4 is a diagram illustrating an example of a relationship between a vendor-developed program package and a projection library package; It is a figure which shows an example of a device information class. FIG. 10 is a diagram showing an example of a projection setting information class; FIG. It is a figure which shows an example of a device information acquisition class. FIG. 10 is a diagram showing an example of a projection processing class; FIG. 4 is a diagram showing an example of program code of a vendor development program; FIG. 10 is a sequence diagram showing an example of projection processing according to the second embodiment; FIG. 11 is a diagram showing an example of the functional configuration of a development terminal according to the third embodiment; 10 is a flowchart showing an example of compilation processing according to the third embodiment;

Hereinafter, each embodiment of the present invention will be described in detail with reference to the drawings.

[First embodiment]
<Overall composition>
First, the overall configuration of a printing system 1 according to this embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of the overall configuration of a printing system 1 according to the first embodiment.

As shown in FIG. 1, a printing system 1 according to the present embodiment includes one or more terminal devices 10 and one or more devices 20. As shown in FIG. Also, the terminal device 10 and the device 20 are communicably connected using short-range wireless communication such as Bluetooth (registered trademark), for example. Further, the terminal device 10 and the device 20 are communicably connected using a wireless LAN (Local Area Network) such as Wi-Fi.

The device 20 is an image processing device such as an MFP. The device 20 performs various image processing such as print processing and scan processing in response to a request from the terminal device 10 . In this embodiment, it is assumed that the device 20 is an MFP. Note that the device 20 is not limited to an MFP, and includes, for example, a copier, a printer, a scanner device, a facsimile machine, a digital camera, a projector, an electronic conference terminal, an electronic blackboard device, an audio device, an in-vehicle device (such as a car navigation system), a home appliance It may be a product (for example, a refrigerator, etc.).

The terminal device 10 is an information processing device such as a smart phone. A printing application 100 developed by an external company (hereinafter referred to as a “third vendor”) different from the manufacturer of the device 20 and performing processing in cooperation with the device 20 is installed in the terminal device 10 . A user of the terminal device 10 can use the print application 100 to print on the device 20 .

Note that the terminal device 10 is not limited to a smartphone, and may be, for example, a tablet terminal, a notebook PC (personal computer), a desktop PC, a game device, a digital camera, a wearable device, or the like.

<Configuration of print application 100>
Here, the configuration of the print application 100 developed by a third vendor will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of the configuration of the print application 100. As shown in FIG.

As shown in FIG. 2, the print application 100 includes a vendor development program 110, which is a program developed by a third vendor to provide unique functions, and a print library 120, which is an API group provided by the manufacturer of the device 20. have.

The print library 120 is a program for providing print functions. The print library 120 defines, for example, an API for acquiring device information from the device 20 and an API for requesting the device 20 to print. Therefore, the vendor development program 110 can implement processing in cooperation with the device 20, such as obtaining device information from the device 20 and requesting printing from the device 20, by calling the API defined in the print library 120. can.

At this time, the print library 120 prevents, for example, the vendor development program 110 from rewriting the device information acquired from the device 20 . As a result, it is possible to prevent the device information and the like acquired by the print library 120 from being illegally rewritten by the vendor development program 110 .

Also, for example, when the vendor development program 110 reads the device information acquired from the device 20, the print library 120 prevents at least part of the information from being read. As a result, the vendor development program 110 can be prevented from referring to the device information acquired by the print library 120 unnecessarily, and the security risk of the device 20 can be prevented from being lowered.

In this embodiment, the vendor development program 110 and print library 120 are assumed to be programs developed in the Java (registered trademark) language. Therefore, Java classes are defined in the print library 120 . The vendor development program 110 can implement acquisition of device information from the device 20, a print request to the device 20, and the like by calling a method (API) within the class. However, the vendor development program 110 and print library 120 are not limited to being developed in the Java language. For example, it may be developed in various programming languages such as C language, C++ language, Objective-C language and C# language.

Note that the print library 120 is not limited to being provided by the manufacturer of the device 20 . The print library 120 may be provided, for example, by an affiliated company of the manufacturer of the device 20, or the like. Also, the print library 120 may be provided as part of an SDK (Software Development Kit), for example.

<Hardware configuration>
<<Terminal device 10>>
Next, the hardware configuration of the terminal device 10 according to this embodiment will be described with reference to FIG. FIG. 3 is a diagram showing an example of the hardware configuration of the terminal device 10 according to the first embodiment.

As shown in FIG. 3 , the terminal device 10 according to this embodiment has an input device 11 , a display device 12 , an external I/F 13 and a RAM (Random Access Memory) 14 . The terminal device 10 according to the present embodiment also has a ROM (Read Only Memory) 15 , a CPU (Central Processing Unit) 16 , a communication I/F 17 and an auxiliary storage device 18 . Each of these pieces of hardware are connected by a bus B, respectively.

The input device 11 is, for example, a touch panel or the like, and is used by the user to input various operations. Note that the input device 11 may be, for example, a keyboard, a mouse, or the like.

The display device 12 is a display or the like, and displays the processing result by the terminal device 10 . The external I/F 13 is an interface with an external device. The external device includes a recording medium 13a and the like. The terminal device 10 can read from and write to the recording medium 13 a via the external I/F 13 .

The recording medium 13a includes, for example, a USB memory, an SD memory card, a flexible disk, a CD, a DVD, and the like.

The RAM 14 is a volatile semiconductor memory that temporarily holds programs and data. The ROM 15 is a non-volatile semiconductor memory that can retain programs and data even when power is turned off. The ROM 15 stores, for example, programs and data such as BIOS (Basic Input/Output System), OS (Operating System) settings, and network settings that are executed when the terminal device 10 is started.

The CPU 16 is an arithmetic unit that implements the overall control and functions of the terminal device 10 by reading programs and data from the ROM 15, the auxiliary storage device 18, etc. onto the RAM 14 and executing processing.

The communication I/F 17 is an interface for the terminal device 10 to communicate with the equipment 20 . The communication I/F 17 includes, for example, a Bluetooth module for communicating with the device 20 via Bluetooth and a wireless LAN module for communicating with the device 20 via a wireless LAN such as Wi-Fi.

The auxiliary storage device 18 is, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and is a non-volatile storage device that stores programs and data. The programs and data stored in the auxiliary storage device 18 include an OS, which is basic software for controlling the entire terminal device 10, a print application 100, and applications that provide various other functions. The auxiliary storage device 18 manages stored programs and data by means of a predetermined file system or DB (database).

The terminal device 10 according to the present embodiment has the hardware configuration shown in FIG. 3, and thus can implement various types of processing described later.

<<Equipment 20>>
Next, the hardware configuration when the device 20 according to the present embodiment is an image processing device such as an MFP will be described with reference to FIG. FIG. 4 is a diagram showing an example of the hardware configuration of the device 20 according to the first embodiment.

As shown in FIG. 4, the device 20 according to this embodiment has a controller 21, an operation panel 22, an external I/F 23, a communication I/F 24, a plotter 25, and a scanner . The controller 21 also has a CPU 31 , a RAM 32 , a ROM 33 , an NVRAM 34 and an auxiliary storage device 35 .

The ROM 33 is a non-volatile semiconductor memory that can retain programs and data even when the power is turned off. The RAM 32 is a volatile semiconductor memory that temporarily holds programs and data. The NVRAM 34 is a non-volatile semiconductor memory that stores setting information, for example. Also, the auxiliary storage device 35 is, for example, an HDD, an SSD, or the like, and is a non-volatile storage device that stores programs and data.

The CPU 31 is an arithmetic unit that reads programs, data, setting information, and the like from the ROM 33, the NVRAM 34, the auxiliary storage device 35, and the like onto the RAM 32 and executes processing, thereby realizing control and functions of the device 20 as a whole.

The operation panel 22 is an input/output device that includes an input section for receiving input from a user and a display section for displaying. The external I/F 23 is an interface with an external device. The external device includes a recording medium 23a and the like. The device 20 can read from and write to the recording medium 23 a via the external I/F 23 .

Examples of the recording medium 23a include IC cards, USB memories, SD memory cards, flexible disks, CDs, and DVDs.

The communication I/F 24 is an interface for the device 20 to communicate with the terminal device 10 . The communication I/F 24 includes, for example, a Bluetooth module for communicating with the terminal device 10 via Bluetooth and a wireless LAN module for communicating with the terminal device 10 via a wireless LAN. Note that the communication I/F 24 may include a LAN board or the like for communicating with the terminal device 10 via a wired LAN.

The plotter 25 is a device for printing print data on a print medium. Note that the print medium is not limited to paper. The print medium may be, for example, an OHP sheet, plastic film, copper foil, cloth, or the like. The scanner 26 is a device that reads an original and generates image data.

The device 20 according to the present embodiment has the hardware configuration shown in FIG. 4, and thus can implement various types of processing described later.

<Functional configuration>
Next, the functional configuration of the terminal device 10 according to this embodiment will be described with reference to FIG. FIG. 5 is a diagram showing an example of the functional configuration of the terminal device 10 according to the first embodiment.

As shown in FIG. 5, the terminal device 10 according to the present embodiment includes a device information acquisition request section 111, a display control section 112, a print target data setting section 113, a print setting section 114, and an execution operation reception section 115. and a print execution request unit 116 . These units are realized by processing that the vendor development program 110 causes the CPU 16 to execute.

Further, the terminal device 10 according to this embodiment has a device information acquisition section 121 and a print processing section 122 . These units are implemented by processing that the print library 120 causes the CPU 16 to execute.

The device information acquisition request unit 111 receives device information acquisition operation by the user. Further, upon receiving a device information acquisition operation by the user, the device information acquisition request unit 111 requests the device information acquisition unit 121 to acquire the device information. The device information acquisition request unit 111 requests acquisition of device information by calling a method in a class that implements the device information acquisition unit 121 (this class is hereinafter referred to as a “device information acquisition class 1300”). be able to.

The display control unit 112 displays the device information acquired by the device information acquisition unit 121 on the display device 12 .

The print target data setting unit 113 receives a user's selection operation of print target data. The print target data is content data that the user desires to print. Content data includes, for example, image data such as photographs, document data, and the like. Note that if the device 20 is a projector, an audio device, or the like, the content data may be video data, music data, or the like, for example.

In addition, upon receiving a user's operation of selecting print data, the print data setting unit 113 sets the selected content data as the print data.

The print setting unit 114 accepts an operation of designating print setting information by the user. The print setting information includes, for example, the number of copies, print page range, print color, and the like.

Further, upon receiving a user's operation of designating print setting information, the print setting unit 114 generates a print setting information instance 300 holding each piece of print setting information. The print setting unit 114 then sets the print setting information specified by the user in the print setting information instance 300 . The print setting unit 114 can set print setting information by calling a method in a class that implements the print setting information instance 300 (this class is hereinafter referred to as a “print setting information class 1200”). .

The execution operation reception unit 115 receives a print execution operation by the user. When the print execution operation is received by the execution operation reception unit 115, the print execution request unit 116 requests the print processing unit 122 to execute printing. The print execution request unit 116 can request print execution by calling a method in a class that implements the print processing unit 122 (this class will hereinafter be referred to as a “print processing class 1400”).

The device information acquisition unit 121 acquires device information from the device 20 in response to a request from the device information acquisition request unit 111 . At this time, the device information acquisition unit 121 acquires device information from the device 20 using short-range wireless communication such as Bluetooth. The device information includes, for example, an IP address, model name, supported PDL (Page Description Language), network information, and the like.

Further, when the device information acquisition unit 121 acquires the device information from the device 20, the device information acquisition unit 121 generates the device information instance 200 that holds the acquired device information. Then, the device information acquisition unit 121 sets the acquired device information in the device information instance 200 . The device information acquisition unit 121 can set device information by calling a method in a class that implements the device information instance 200 (this class is hereinafter referred to as “device information class 1100”).

The print processing unit 122 generates print data according to the request from the print execution request unit 116 and then transmits the print request to the device 20 . At this time, the print processing unit 122 transmits a print request to the device 20 using a wireless LAN such as Wi-Fi.

The print processing unit 122 includes a print data generation unit 123 and a print request unit 124 . The print data generator 123 generates print data. The print data is data obtained by converting data to be printed into a data format interpretable by the device 20 (that is, PDL supported by the device 20). The print request unit 124 transmits a print request including the print data generated by the print data generation unit 123 to the device 20 .

Here, the device information instance 200 will be described with reference to FIG. FIG. 6 is a diagram showing an example of the device information instance 200. As shown in FIG.

As shown in FIG. 6, the device information instance 200 includes device information with the field name “IP address”, device information with the field name “model name”, device information with the field name “support PDL”, and device information with the field name “network information” and device information.

The IP address of the device 20 is set as the field value for the device information with the field name “IP address”. Further, the reading range of the device information with the field name "IP address" is "whole area", and the rewriting range is "within the library". This indicates that the device information with the field name "IP address" can be read from a program (vendor development program 110) other than the print library 120, but cannot be rewritten (updated field value). there is

For the device information with the field name “model name”, the model name (for example, model number) of the device 20 is set as the field value. Further, the reading range of the device information with the field name "model name" is "whole area", and the rewriting range is "within the library". This indicates that the device information with the field name "model name" can be read by a program other than the print library 120, but cannot be rewritten.

A data format name interpretable by the device 20 is set as a field value in the device information with the field name “support PDL”. Also, the read range and rewrite range of the device information with the field name "support PDL" are "within the library". This indicates that the device information with the field name “support PDL” cannot be read or rewritten by programs other than the print library 120 .

For the device information with the field name “network information”, the SSID (Service Set Identifier) of the device 20, the encryption method, the password of the access point, etc. are set as field values. Also, the read range and rewrite range of the device information with the field name "network information" are "within the library". This indicates that the device information with the field name “network information” cannot be read or rewritten by programs other than the print library 120 .

As described above, in the device information instance 200, the read range and rewrite range of the device information held by the device information instance 200 are set. As a result, the manufacturer of the device 20 can prevent the vendor development program 110 developed by the third vendor from referencing unnecessary device information or illegally rewriting the device information. Note that the device information held by the device information instance 200 is not limited to the above "IP address", "model name", "support PDL", and "network information". The device information instance 200 may hold various types of device information such as the device number, date of manufacture, and manufacturer company information.

Next, the print setting information instance 300 will be described with reference to FIG. FIG. 7 is a diagram showing an example of the print setting information instance 300. As shown in FIG.

As shown in FIG. 7, the print setting information instance 300 includes print setting information with the field name "number of copies", print setting information with the field name "print page range", and print setting information with the field name "print color". Hold.

The number of print copies specified by the user (or the default number of print copies) is set as the field value in the print setting information with the field name “number of copies”. Also, the read range and rewrite range of the print setting information with the field name "number of copies" are "whole area". This indicates that the print setting information with the field name “number of copies” can be read and rewritten by programs other than the print library 120 .

A print page range specified by the user (or a default print page range) is set as a field value in the print setting information with the field name “print page range”. Also, the read range and rewrite range of the print setting information with the field name "print page range" are "whole area". This indicates that the print setting information with the field name “print page range” can be read and rewritten by programs other than the print library 120 .

The print setting information with the field name “print color” has the print color specified by the user (or the default print color) set as the field value. Also, the read range and rewrite range of the print setting information with the field name "print color" are "whole area". This indicates that the print setting information with the field name “print color” can be read and rewritten by programs other than the print library 120 .

As described above, in the print setting information instance 300, the read range and rewrite range of the print setting information held by the print setting information instance 300 are set. This prevents the vendor development program 110 developed by a third vendor from referring to unnecessary print setting information or from rewriting print setting information to which only default values are applied, for example. can do. Note that the print setting information held by the print setting information instance 300 is not limited to the above-described "number of copies", "print page range", and "print color". The print setting information instance 300 may hold various print setting information such as presence/absence of tint block printing, presence/absence of aggregation, and presence/absence of double-sided printing.

Here, the reading range and rewriting range of the device information instance 200 and the print setting information instance 300 can be realized using a Java language package. For example, as shown in FIG. 8, the package to which each class defined in the vendor development program 110 belongs and the package to which each class defined in the print library 120 belongs are different packages.

As a result, by defining an access level for a method that operates a field (that is, device information) held by the device information instance 200, it is possible to limit the read range and rewrite range of this field. Similarly, by defining an access level for a method that operates a field (that is, print setting information) held by the print setting information instance 300, it is possible to limit the read range and rewrite range of this field. Hereinafter, the package name of the package to which each class defined in the print library 120 belongs is assumed to be "printlibrary".

Although the example shown in FIG. 8 shows the case where each class defined in the vendor development program 110 belongs to the same package, the present invention is not limited to this. Also good.

Here, the device information class 1100 that implements the device information instance 200 will be described with reference to FIG. FIG. 9 is a diagram showing an example of the device information class 1100. As shown in FIG. The device information instance 200 is generated by instantiating the device information class 1100 shown in FIG. 9, for example.

As shown in FIG. 9, device information class 1100 includes package declaration 1101 and class declaration 1102 . The package declaration 1101 defines a package name “printlibrary”. Class declaration 1102 includes method declarations 1103 to 1110 for each device information.

A method declaration 1103 defines a method “getIPAddress” for acquiring (reading) the device information with the field name “IP address”. The method declaration 1103 defines a modifier (hereinafter referred to as an "access modifier") "public" indicating the access level of the method "getIPAddress". Therefore, the method "getIPAddress" can also be called from a class belonging to a package other than the same package (that is, a class defined in a program other than the print library 120). As a result, the reading range “whole area” of the device information with the field name “IP address” is realized, and the device information can be read from the vendor development program 110 as well.

A method declaration 1104 defines a method “setIPAddress” for updating (rewriting) the device information with the field name “IP address”. Also, in the method declaration 1104, no access modifier is defined for this method "setIPAddress". Therefore, the method "setIPAddress" can only be called from classes within the same package (that is, classes defined in the print library 120). As a result, the rewrite range of the device information with the field name “IP address” is realized, and the device information cannot be rewritten from a program other than the print library 120 . Note that if no access modifier is defined for a method, the access level of this method can only be called from within the same package. That is, in this case, the method cannot be called from vendor development programs 110 that are not in the same package.

A method declaration 1105 defines a method “getModelName” for reading device information with a field name “model name”. Also, in the method declaration 1105, the access modifier "public" of this method "getModelName" is defined. As a result, similar to the method "getIPAddress", the reading range "whole area" of the device information with the field name "model name" is realized.

A method declaration 1106 defines a method “setModelName” for rewriting the device information with the field name “model name”. Also, in the method declaration 1106, no access modifier is defined for this method "setModelName". As a result, similar to the method "setIPAddress", the rewriting range "within the library" of the device information with the field name "model name" is realized.

A method declaration 1107 defines a method “getSupportPDL” for reading the device information with the field name “support PDL”. Also, in the method declaration 1107, no access modifier is defined for this method "getSupportPDL". As a result, similarly to the above, the reading range of the device information with the field name "support PDL" is realized as "within the library".

A method declaration 1108 defines a method “setSupportPDL” for rewriting the device information with the field name “support PDL”. Also, in the method declaration 1108, no access modifier is defined for this method "setSupportPDL". As a result, similarly to the above, the rewriting range of the device information with the field name "support PDL" is realized as "within the library".

A method declaration 1109 defines a method “getNetworkInfo” for reading the device information with the field name “network information”. Also, in the method declaration 1109, no access modifier is defined for this method "getNetworkInfo". As a result, similarly to the above, the reading range "within the library" of the device information with the field name "network information" is realized.

A method declaration 1110 defines a method “setNetworkInfo” for rewriting the device information with the field name “network information”. Also, in the method declaration 1108, no access modifier is defined for this method "setNetworkInfo". As a result, similarly to the above, the rewriting range of the device information with the field name "network information" is realized as "within the library".

As described above, in the device information class 1100, by defining the access modifier "public" for methods for manipulating (reading or rewriting) device information, classes belonging to other packages can access device information. You will be able to perform operations on On the other hand, in the device information class 1100, by not defining access modifiers for methods for operating device information, classes belonging to other packages cannot operate device information. can.

Note that the device information for the device information instance 200 may be set, for example, when the device information instance 200 is generated. In this case, the vendor development program 110 must define a method (constructor) that receives parameters for initialization as arguments and initializes the device information. The constructor receives the IP address, model name, support PDL, and network information as arguments, and uses the methods defined in method declarations 1103, 1105, 1107, and 1109 to generate the IP address, model name, support PDL, and network information. should be defined so that each can be obtained. Also, if the device information is not changed after the device information instance 200 is generated, the method declarations 1104, 1106, 1108, and 1110 are unnecessary. Also good.

Next, the print setting information class 1200 that implements the print setting information instance 300 will be described with reference to FIG. FIG. 10 is a diagram showing an example of the print setting information class 1200. As shown in FIG. The print setting information instance 300 is generated by instantiating the print setting information class 1200 shown in FIG. 10, for example.

As shown in FIG. 10, print setting information class 1200 includes package declaration 1201 and class declaration 1202 . A package name “printlibrary” is defined in the package declaration 1201 . Class declaration 1202 includes method declarations 1203 to 1208 for each print setting information.

A method declaration 1203 defines a method “getCopies” for reading the print setting information with the field name “number of copies”. Also, in the method declaration 1203, the access modifier "public" of this method "getCopies" is defined. As a result, as described in the device information class 1100, the reading range "whole area" of the print setting information with the field name "number of copies" is realized.

A method declaration 1204 defines a method “setCopies” for rewriting the print setting information with the field name “number of copies”. Also, in the method declaration 1204, the access modifier "public" of this method "setCopies" is defined. As a result, in the same manner as described for the device information class 1100, the rewrite range "whole area" of the print setting information with the field name "number of copies" is realized.

A method declaration 1205 defines a method “getPrintPage” for reading print setting information with a field name “print page range”. Also, in the method declaration 1205, the access modifier "public" of this method "getPrintPage" is defined. As a result, similarly to the above, the read range "whole area" of the print setting information with the field name "print page range" is realized.

A method declaration 1206 defines a method “setPrintPage” for rewriting print setting information with a field name “print page range”. Also, in the method declaration 1206, the access modifier "public" of this method "setPrintPage" is defined. As a result, in the same manner as described above, the rewrite range "whole area" of the print setting information with the field name "print page range" is realized.

A method declaration 1207 defines a method “getColor” for reading print setting information with a field name “print color”. Also, in the method declaration 1207, the access modifier "public" of this method "getColor" is defined. As a result, similarly to the above, the read range "whole area" of the print setting information with the field name "print color" is realized.

A method declaration 1208 defines a method “setColor” for rewriting print setting information with a field name “print color”. Also, in the method declaration 1208, the access modifier "public" of this method "setColor" is defined. As a result, in the same manner as described above, the rewrite range "whole area" of the print setting information with the field name "print color" is realized.

As described above, in the print setting information class 1200, by defining the access modifier "public" for methods for manipulating (reading or rewriting) print setting information, classes belonging to other packages can It becomes possible to operate the print setting information. On the other hand, the print setting information class 1200 does not define access modifiers for methods for manipulating print setting information, so that classes belonging to other packages cannot manipulate print setting information. can do.

Next, a device information acquisition class 1300 that implements the device information acquisition unit 121 will be described with reference to FIG. FIG. 11 is a diagram showing an example of the device information acquisition class 1300. As shown in FIG. The device information acquisition unit 121 is generated by instantiating the device information acquisition class 1300 shown in FIG. 11, for example.

As shown in FIG. 11, device information acquisition class 1300 includes package declaration 1301 and class declaration 1302 . The package declaration 1301 defines a package name “printlibrary”. Class declaration 1302 includes method declaration 1303 .

A method declaration 1303 defines a method “getMfpInfo” for acquiring device information from the device 20 . Also, in the method declaration 1303, the access modifier "public" of this method "getMfpInfo" is defined. This allows the method "getMfpInfo" to be called from a class belonging to a package other than the same package (that is, a class defined in a program other than the print library 120).

Next, a print processing class 1400 that implements the print processing unit 122 will be described with reference to FIG. FIG. 12 is a diagram showing an example of the print processing class 1400. As shown in FIG. The print processing unit 122 is generated by instantiating the print processing class 1400 shown in FIG. 12, for example.

As shown in FIG. 12, print processing class 1400 includes package declaration 1401 and class declaration 1402 . The package declaration 1401 defines a package name “printlibrary”. Class declaration 1402 includes method declaration 1403 .

A method declaration 1403 defines a method “print” for transmitting a print request to the device 20 . Also, in the method declaration 1403, the access modifier "public" of this method "print" is defined. This allows the method "print" to be called from a class belonging to a package other than the same package (that is, a class defined in a program other than the print library 120).

The method declaration 1403 defines "MfpInfo info", "PrintData data", and "PrintSetting setting" as arguments of the method "print". This indicates that the device information, the data to be printed, and the print setting information are specified as arguments of the method "print".

Next, program code 1500 of vendor development program 110 will be described with reference to FIG. FIG. 13 is a diagram showing an example of program code 1500 of vendor development program 110 . Note that in FIG. 13, as an example, program code 1500 in which codes respectively corresponding to the device information acquisition request section 111, the print target data setting section 113, the print setting section 114, and the print execution request section 116 are defined. explain. Codes corresponding to the display control unit 112, the execution operation receiving unit 115, etc. need to be defined separately.

As shown in FIG. 13, program code 1500 includes package declaration 1501 and class declaration 1502 . A package declaration 1501 defines a package name “printapp”. Therefore, the vendor development program 110 cannot call a method for which the access modifier "public" is not defined among the methods defined in each class belonging to the package name "printlibrary".

Class declaration 1502 includes print execution class 1503 . The print execution class 1503 includes a code definition 1504 defining a code corresponding to the device information acquisition request section 111 and a code definition 1505 defining a code corresponding to the print setting section 114 . The print execution class 1503 also includes a code definition 1506 defining code corresponding to the print target data setting unit 113 and a code definition 1507 defining code corresponding to the print execution request unit 116 .

As shown in the code definition 1507, the vendor development program 110 designates "info" indicating the device information instance 200 as an argument when calling the method "print" of the print processing class 1400 belonging to the package name "printlibrary". As a result, in the processing of the method "print", a method for which the access modifier "public" of the device information instance 200 is not defined can be called, and then a processing request (print request) can be issued to the device 20. can. For example, in the process of the method "print", the method "getSupportPDL" of "info" indicating the device information instance 200 is called to obtain the device information with the field name "support PDL", and then a print request specifying this device information is generated. can be performed on device 20 .

For this reason, the printing application 100 uses information that cannot be operated by the vendor development program 110 for the device 20 (for example, device information with the field name “support PDL” or device information with the field name “network information”). It becomes possible to make a processing request (printing request).

<Print processing>
Next, printing processing of the printing system 1 according to this embodiment will be described. Hereinafter, the processing when the user of the terminal device 10 uses the print application 100 to print on the device 20 will be described with reference to FIG. 14 . FIG. 14 is a sequence diagram showing an example of print processing according to the first embodiment.

14 below, except for the device information class 1100 and the print setting information class 1200, each class defined in the vendor development program 110 and print library 120 is instantiated. Note that each class defined in the vendor development program 110 and the print library 120 may include classes that have not been instantiated. In this case, it may be appropriately instantiated before executing the processing of the functional unit (instance) realized by the class. Also, the device information class 1100 and the print setting information class 1200 may be instantiated in advance.

First, the device information acquisition request unit 111 of the vendor development program 110 accepts a user's device information acquisition operation (step S101). For example, on a predetermined screen displayed by the display control unit 112, the user selects a desired device 20 from a list of devices 20 installed nearby, thereby performing a device information acquisition operation. It can be carried out. Alternatively, for example, a QR code (registered trademark) attached to the housing of the device 20 may be imaged by the camera of the terminal device 10 to perform the device information acquisition operation.

The device information acquisition request unit 111 of the vendor development program 110, upon receiving the device information acquisition operation by the user, requests the device information acquisition unit 121 to acquire the device information (step S102). The device information acquisition request unit 111 can make a device information acquisition request by calling the method “getMfpInfo” defined in the method declaration 1303 of the device information acquisition class 1300 .

Upon receiving the device information acquisition request, the device information acquisition unit 121 of the print library 120 inquires of the device 20 about the device information (step S103). The device information acquisition unit 121 can inquire of the device 20 about device information by short-range wireless communication such as Bluetooth. Note that short-range wireless communication is not limited to Bluetooth, and may be, for example, BLE (Bluetooth Low Energy), Zigbee, or the like. Alternatively, infrared rays, RFID (Radio Frequency Identification), or the like may be used.

Then, the device information acquisition unit 121 receives the device information returned from the device 20 in response to the above inquiry. As a result, the device information acquisition unit 121 can acquire device information such as the IP address, model name, supported PDL, and network information from the device 20 .

In step S103 above, the case where the device information is acquired from the device 20 by short-range wireless communication such as Bluetooth has been described, but the present invention is not limited to this. The device information acquisition unit 121 may acquire the device information embedded in the QR code, for example, by capturing an image of the QR code attached to the housing of the device 20 with a camera. Alternatively, the device information acquisition unit 121 may acquire device information from the device 20 by wireless communication (for example, Wi-Fi, etc.) other than short-range wireless communication. For example, after notifying the device 20 of its own IP address, the terminal device 10 may acquire device information from the device 20 by wireless communication such as Wi-Fi as a response to this notification.

Upon acquiring the device information from the device 20, the device information acquisition unit 121 of the print library 120 generates the device information instance 200 (step S104). A device information instance 200 is generated by instantiating a device information class 1100 .

Next, the device information acquisition unit 121 of the print library 120 sets the device information acquired from the device 20 in the device information instance 200 (step S105).

That is, the device information acquisition unit 121 designates the IP address acquired from the device 20 as an argument and calls the method “setIPAddress” defined in the method declaration 1104 of the device information class 1100 . As a result, the device information with the field name “IP address” is set in the device information instance 200 .

Similarly, the device information acquisition unit 121 calls the method “setModelName” defined in the method declaration 1106 of the device information class 1100 after designating the model name acquired from the device 20 as an argument. As a result, the device information with the field name “model name” is set in the device information instance 200 .

Similarly, the device information acquisition unit 121 designates the support PDL acquired from the device 20 as an argument and calls the method “setSupportPDL” defined in the method declaration 1108 of the device information class 1100 . As a result, the device information with the field name “support PDL” is set in the device information instance 200 .

Similarly, the device information acquisition unit 121 calls the method “setNetworkInfo” defined in the method declaration 1110 of the device information class 1100 after specifying the network information acquired from the device 20 as an argument. As a result, the device information with the field name “network information” is set in the device information instance 200 .

Then, the device information acquisition unit 121 returns to the vendor development program 110 the device information instance 200 in which each device information acquired from the device 20 is set.

The display control unit 112 of the vendor development program 110 acquires device information from the device information instance 200 returned from the device information acquisition unit 121 . Then, the display control unit 112 displays the device information acquired from the device information instance 200 on the display device 12 (step S106).

At this time, the display control unit 112 can acquire the device information whose read range is “whole area” among the device information held in the device information instance 200 . That is, the display control unit 112 can acquire the device information with the field name “IP address” and the device information with the field name “model name” from the device information instance 200 . The display control unit 112 can acquire the device information with the field name “IP address” from the device information instance 200 by calling the method “getIPAddress” defined in the method declaration 1103 of the device information class 1100 . Similarly, the display control unit 112 can acquire the device information with the field name “model name” by calling the method “getModelName” defined in the method declaration 1105 of the device information class 1100 .

Note that the display control unit 112 can use the device information acquired as described above to limit options on the screen for receiving the print setting information designation operation in step S109, which will be described later. For example, the display control unit 112 determines that the device 20 supports only monochrome printing based on the device information with the field name “model name”, and restricts so that “color” cannot be specified as the print setting information. (eg, hide the option for selecting "color").

Further, for example, when the device information of a plurality of devices 20 is acquired, the display control unit 112 uses the device information to generate a device list screen or the like for the user to select the device 20 as the output destination. and may be displayed. By displaying the device list screen, the user can select the output destination device 20 (the device 20 that executes printing) from among the plurality of devices 20 .

On the other hand, the display control unit 112 cannot acquire the device information with the field name “support PDL” and the device information with the field name “network information” from the device information instance 200 .

Therefore, the display control unit 112 displays the IP address and model name of the device 20 on the display device 12 . As a result, it is possible to prevent display of device information that the user does not necessarily need to refer to, such as support PDL and network information.

FIG. 15 shows a device confirmation screen G100 for confirming the device information of the device 20 that executes printing, as an example of the screen displayed on the display device 12 in step S106. FIG. 15 is a diagram showing an example of the device confirmation screen G100.

The device confirmation screen G100 shown in FIG. 15 includes a device information display field G110. In the device information display field G110, device information that can be acquired from the device information instance 200 (that is, device information whose reading range is “whole area”). "model name" device information) is displayed. In this manner, the display control unit 112 displays, among the device information held in the device information instance 200, the device information whose read range is "whole area" in the device information display field G110.

On the other hand, the display control unit 112 cannot display device information that cannot be acquired from the device information instance 200 in the device information display field G110. That is, the display control unit 112 displays the device information whose reading range is “within the library” (specifically, the device information with the field name “support PDL” and the device information with the field name “network information”) in the device information display column. It cannot be displayed on G110.

Next, the print target data setting unit 113 of the vendor development program 110 receives an operation for selecting print target data by the user (step S107). For example, the user can select desired content data from the content data list screen after transitioning from the screen displaying the device information in step S106 to the content data list screen. selection operation can be performed.

The print target data setting unit 113 of the vendor development program 110 receives the print target data selection operation by the user, and sets the selected content data as the print target data (step S108). It should be noted that the processes of steps S107 and S108 do not have to be executed when the data to be printed is set in advance before the process of step S101 is executed.

Next, the print setting unit 114 of the vendor development program 110 accepts an operation of specifying print setting information by the user (step S109). For example, the user can specify the print setting information by specifying the setting value of each print setting information on a predetermined screen displayed after selecting the data to be printed. Note that if the user does not change the print setting information (that is, if default values are used as the setting values of the print setting information), the processing of this step may not be executed.

The print setting unit 114 of the vendor development program 110 generates the print setting information instance 300 (step S110). The print setting information instance 300 is generated by instantiating the print setting information class 1200 .

Next, the print setting unit 114 of the vendor development program 110 sets the print setting information specified by the user in step S109 to the print setting information instance 300 (step S111).

That is, the print setting unit 114 calls the method “setCopies” defined in the method declaration 1204 of the print setting information class 1200 after specifying the number of copies specified by the user as an argument. As a result, the print setting information with the field name “number of copies” is set in the print setting information instance 300 .

Similarly, the print setting unit 114 calls the method “setPrintPage” defined in the method declaration 1206 of the print setting information class 1200 after specifying the print page range specified by the user as an argument. As a result, the print setting information with the field name “print page range” is set in the print setting information instance 300 .

Similarly, the print setting unit 114 calls the method “setColor” defined in the method declaration 1208 of the print setting information class 1200 after specifying the print color specified by the user as an argument. As a result, the print setting information with the field name “print color” is set in the print setting information instance 300 .

Note that if the user specifies only part of the print setting information in step S109 (for example, if only the number of copies is specified), the print setting unit 114 prints only the print setting information specified by the user. It may be set in the setting information instance 300 . Alternatively, if each piece of print setting information held by the print setting information instance 300 is not initialized to a default value, the print setting unit 114 replaces the print setting information that is not specified by the user with this print setting information. A default value may be set in the print setting information instance 300 .

Next, the execution operation receiving unit 115 of the vendor development program 110 receives a print execution operation by the user (step S112). For example, the user can perform a print execution operation by pressing a print execution button on a predetermined screen displayed after designating print setting information.

When the execution operation reception unit 115 receives the print execution operation, the print execution request unit 116 of the vendor development program 110 requests the print processing unit 122 to execute printing (step S113). This print execution request includes the device information instance 200 , the data to be printed, and the print setting information instance 300 . The print execution request unit 116 designates the device information instance 200, the data to be printed, and the print setting information instance 300 as arguments, and then executes the method "print" defined in the method declaration 1403 of the print processing class 1400. By calling it, a print execution request can be issued.

By specifying the device information instance 200 as an argument to the method "print", for example, when a plurality of device information instances 200 exist (that is, for example, when there are a plurality of devices 20 When the device information is obtained from each device 20), it becomes possible to specify which device information instance 200 is to be used. Therefore, it becomes possible to manage a plurality of pieces of information that cannot be operated from the vendor development program 110 .

For example, when a plurality of device information instances 200 exist, device information with the field name “support PDL” exists for each device 20 . In this case, the vendor development program 110 cannot refer to any device information with the field name “support PDL”. For this reason, the vendor development program 110 cannot directly specify one of these pieces of device information, but by specifying the device information instance 200, the vendor development program 110 can determine which device 20's support PDL is to be used. can be specified explicitly.

The print processing unit 122 of the print library 120 uses the print data generation unit 123 to acquire the support PDL from the device information instance 200 included in the print execution request (step S114). That is, the print data generation unit 123 acquires the device information with the field name “support PDL” from among the device information held in the device information instance 200 . The print data generation unit 123 can acquire the device information with the field name “support PDL” by calling the method “getSupportPDL” defined in the method declaration 1107 of the device information class 1100 . Since the print processing class 1400 that implements the print processing unit 122 and the device information class 1100 belong to the same package “printlibrary”, the print data generation unit 123 can call the method “getSupportPDL”.

Next, the print processing unit 122 of the print library 120 uses the print data generation unit 123 to acquire each piece of print setting information from the print setting information instance 300 included in the print execution request (step S115). That is, the print data generator 123 acquires print setting information held in the print setting information instance 300 . The print data generation unit 123 can acquire each piece of print setting information by calling the methods defined in the method declarations 1203 , 1205 and 1207 of the print setting information class 1200 .

Next, the print processing unit 122 of the print library 120 uses the print data generation unit 123 to generate print data (step S116). That is, the print data generation unit 123 generates print data from the print target data using the support PDL acquired in step S114 and the print setting information acquired in step S115. At this time, the print data generation unit 123 generates print data in the data format indicated by the support PDL acquired in step S114.

Next, the print processing unit 122 of the print library 120 uses the print request unit 124 to acquire network information from the device information instance 200 included in the print execution request (step S117). That is, the print request unit 124 acquires the device information with the field name “network information” from among the device information held in the device information instance 200 . The print request unit 124 can acquire the device information with the field name “network information” by calling the method “getNetworkInfo” defined in the method declaration 1109 of the device information class 1100 . Since the print processing class 1400 that implements the print processing unit 122 and the device information class 1100 belong to the same package “printlibrary”, the print request unit 124 can call the method “getNetworkInfo”.

Next, the print processing unit 122 of the print library 120 determines whether or not communication with the device 20 is possible based on the network information acquired in step S117 by the print request unit 124 (step S118). That is, the print request unit 124 compares the SSID included in the network information acquired in step S117 and the SSID of the access point to which the terminal device 10 is connected, for example. 20 is communicable.

Whether or not communication is possible can be determined, for example, by comparing these SSIDs and determining whether or not the terminal device 10 and the device 20 are in the same network. However, the present invention is not limited to this, and for example, the communication method of the terminal device 10 and the communication method of the device 20 may be compared to determine whether or not the terminal device 10 and the device 20 can communicate with each other.

If it is determined in step S118 that communication with the device 20 is possible, the print processing unit 122 of the print library 120 causes the print request unit 124 to acquire the IP address from the device information instance 200 included in the print execution request ( step S119). That is, the print request unit 124 acquires the device information with the field name “IP address” from among the device information held in the device information instance 200 . The print request unit 124 can acquire the device information with the field name “IP address” by calling the method “getIPAddress” defined in the method declaration 1103 of the device information class 1100 .

Next, the print processing unit 122 of the print library 120 uses the print request unit 124 to transmit a print request to the device 20 (step S120). That is, the print request unit 124 transmits a print request to the IP address obtained in step S119 above, via a wireless LAN such as Wi-Fi. The print request includes the print data generated in step S116 above. As a result, the device 20 that has received the print request prints the print data and returns the print result.

On the other hand, if it is determined in step S118 that communication with the device 20 is not possible, the print processing unit 122 of the print library 120 returns an error to the vendor development program 110 via the print request unit 124 . As a result, for example, an error screen indicating that printing cannot be performed is displayed on the display device 12 .

<Summary of the first embodiment>
As described above, in the printing system 1 according to the present embodiment, the vendor development program 110 developed by the third vendor restricts reading and rewriting of various information managed by the printing library 120 provided by the manufacturer of the device 20. can do. As a result, in the printing system 1 according to the present embodiment, various kinds of information managed by the printing library 120 are prevented from being illegally rewritten by the vendor development program 110, or unnecessary information is referred to. can do.

Further, in the printing system 1 according to the present embodiment, by restricting rewriting of information by the vendor development program 110, unintended operations of the device 20 can be prevented.

For example, if the vendor development program 110 rewrites the device information with the field name "supported PDL", print data in a data format not supported by the device 20 may be generated in step S116 of FIG. . Therefore, an unintended error (data format error of print data, etc.) may occur in the device 20 .

Also, for example, if the device information with the field name "IP address" is rewritten, the print request may be sent to an unintended device 20 in step S120 of FIG. Therefore, printing may be performed by an unintended device 20 .

In the present embodiment, the case where printing is performed by the device 20 has been described. However, for example, the same applies to the case where the vendor development program 110 acquires image data (scanned image) generated by scanning with the device 20. be able to. In this case, the print library 120 may define a class (scanned image acquisition class) for acquiring the scanned image from the device 20 . Then, the scanned image acquisition unit implemented by the scanned image acquisition class may acquire the scanned image from the device 20 based on the device information.

[Second embodiment]
Next, a second embodiment will be described. In the first embodiment, the device 20 is an MFP, but in the second embodiment, the device 20 is a projector.

In addition, in the second embodiment, differences from the first embodiment will be mainly described, and the description of the same components as in the first embodiment will be omitted or simplified as appropriate.

<Overall composition>
First, the overall configuration of the projection system 2 according to this embodiment will be described with reference to FIG. FIG. 16 is a diagram showing an example of the overall configuration of the projection system 2 according to the second embodiment.

As shown in FIG. 16 , the projection system 2 according to this embodiment includes one or more terminal devices 10 and one or more devices 20 . Also, the terminal device 10 and the device 20 are communicably connected using short-range wireless communication such as Bluetooth, for example. Furthermore, the terminal device 10 and the device 20 are connected so as to be able to communicate using a wireless LAN such as Wi-Fi.

The device 20 is a projection device such as a projector. The device 20 performs projection processing in response to a request from the terminal device 10 . The hardware configuration of the device 20 may be, for example, the hardware configuration of a general projector.

The terminal device 10 is an information processing device such as a smart phone. A projection application 400 that is developed by a third vendor and performs processing in cooperation with the device 20 is installed in the terminal device 10 . A user of the terminal device 10 can use the projection application 400 to project an image on the device 20 . Note that the hardware configuration of the terminal device 10 is the same as that of the first embodiment.

Note that, as in the first embodiment, the terminal device 10 is not limited to a smartphone, and may be, for example, a tablet terminal, a notebook PC (personal computer), a desktop PC, a game device, a digital camera, a wearable device, or the like. Also good.

<Configuration of Projection Application 400>
Here, the configuration of the projection application 400 developed by a third vendor will be described with reference to FIG. FIG. 17 is a diagram illustrating an example of the configuration of the projection application 400. As shown in FIG.

As shown in FIG. 17, the projection application 400 includes a vendor development program 410, which is a program developed by a third vendor and provides unique functions, and a projection library 420, which is an API group provided by the manufacturer of the device 20. have.

Projection library 420 is a program for providing projection functions. The projection library 420 defines, for example, an API for acquiring device information from the device 20 and an API for requesting projection from the device 20 . Therefore, the vendor development program 410 can implement processing in cooperation with the device 20, such as obtaining device information from the device 20 and requesting projection to the device 20, by calling the API defined in the projection library 420. can.

As in the first embodiment, the vendor development program 410 and projection library 420 are programs developed in Java language.

<Functional configuration>
Next, the functional configuration of the terminal device 10 according to this embodiment will be described with reference to FIG. FIG. 18 is a diagram showing an example of the functional configuration of the terminal device 10 according to the second embodiment.

As shown in FIG. 18, the terminal device 10 according to the present embodiment includes a device information acquisition request unit 411, a display control unit 412, a projection target data setting unit 413, a projection setting unit 414, and an execution operation reception unit 415. , and a projection execution request unit 416 . These units are implemented by processing that the vendor development program 410 causes the CPU 16 to execute.

Further, the terminal device 10 according to this embodiment has a device information acquisition unit 421 and a projection processing unit 422 . These units are implemented by processing that the projection library 420 causes the CPU 16 to execute.

The device information acquisition request unit 411 receives device information acquisition operation by the user. In addition, when the device information acquisition request unit 411 receives the device information acquisition operation by the user, the device information acquisition request unit 411 requests the device information acquisition unit 421 to acquire the device information. The device information acquisition request unit 411 requests acquisition of device information by calling a method in a class that implements the device information acquisition unit 421 (this class is hereinafter referred to as “device information acquisition class 2300”). be able to.

The display control unit 412 displays the device information acquired by the device information acquisition unit 421 on the display device 12 .

The projection target data setting unit 413 receives a selection operation of projection target data by the user. Projection target data is content data that the user desires to project. Content data includes, for example, image data and moving image data. Hereinafter, as an example, it is assumed that content data is image data.

In addition, upon receiving a selection operation of projection target data by the user, the projection target data setting unit 413 sets the selected content data as the projection target data.

The projection setting unit 414 receives an operation of specifying projection setting information by the user. The projection setting information includes, for example, a switching method. The switching method is a display mode at the time of switching when the image to be projected is switched to another image.

Further, upon receiving a user's operation of specifying projection setting information, the projection setting unit 414 generates a projection setting information instance 600 that holds each piece of projection setting information. The projection setting unit 414 then sets the projection setting information specified by the user in the projection setting information instance 600 . The projection setting unit 414 can set the projection setting information by calling a method in a class that implements the projection setting information instance 600 (this class is hereinafter referred to as a “projection setting information class 2200”). .

The execution operation reception unit 415 receives a projection execution operation by the user. When the execution operation receiving unit 415 receives a projection execution operation, the projection execution requesting unit 416 requests the projection processing unit 422 to execute projection. The projection execution request unit 416 can request projection execution by calling a method in a class that implements the projection processing unit 422 (this class will be referred to as a “projection processing class 2400” hereinafter).

The device information acquisition unit 421 acquires device information from the device 20 in response to a request from the device information acquisition request unit 411 . At this time, the device information acquisition unit 421 acquires the device information from the device 20 using short-range wireless communication such as Bluetooth. The device information includes IP address, model name, resolution, network information, and the like, for example.

Further, when the device information acquisition unit 421 acquires the device information from the device 20, the device information acquisition unit 421 generates a device information instance 500 that holds the acquired device information. Then, the device information acquisition unit 421 sets the acquired device information in the device information instance 500 . The device information acquisition unit 421 can set device information by calling a method in a class that implements the device information instance 500 (this class is hereinafter referred to as “device information class 2100”).

The projection processing unit 422 generates projection data in response to a request from the projection execution request unit 416 and then transmits a projection request to the device 20 . At this time, the projection processing unit 422 transmits a projection request to the device 20 using a wireless LAN such as Wi-Fi.

The projection processing section 422 includes a projection data generation section 423 and a projection request section 424 . The projection data generator 423 generates projection data. Projection data is data obtained by converting projection target data into a data format that can be projected by the device 20 (for example, a data format with a resolution that can be projected by the device 20). The projection request unit 424 transmits a projection request including the projection data generated by the projection data generation unit 423 to the device 20 .

Here, the device information instance 500 will be described with reference to FIG. 19 . FIG. 19 is a diagram showing an example of the device information instance 500. As shown in FIG.

As shown in FIG. 19, the device information instance 500 includes device information with the field name “IP address”, device information with the field name “model name”, device information with the field name “resolution”, and field name “network information”. ” device information. Among these pieces of device information, the device information with the field names "IP address", "model name" and "network information" are the same as those in the first embodiment, so description thereof will be omitted.

For the device information with the field name “resolution”, the resolution of image data that can be projected by the device 20 is set as the field value. Also, the read range and rewrite range of the device information with the field name "resolution" are "within the library". This indicates that the device information with the field name “resolution” cannot be read or rewritten by programs other than the projection library 420 . However, the reading range of the device information with the field name "resolution" may be "whole area".

Note that the field value of the field name "resolution" is not limited to the case where a specific resolution value such as "1280×720" is set. For example, resolution standards or classifications such as “XGA (Extended Graphics Array)” and “HD (High Definition video)” may be set.

As described above, in the device information instance 500, the read range and rewrite range of the device information held by the device information instance 500 are set. As a result, the manufacturer of the device 20 can prevent the vendor development program 410 developed by the third vendor from referencing unnecessary device information or illegally rewriting the device information. Note that the device information held by the device information instance 500 is not limited to the above "IP address", "model name", "resolution", and "network information". The device information instance 500 may hold various types of device information such as the device number, date of manufacture, and manufacturer company information.

Next, projection setting information instance 600 will be described with reference to FIG. FIG. 20 is a diagram showing an example of projection setting information instance 600. As shown in FIG.

As shown in FIG. 20, the projection setting information instance 600 holds projection setting information with the field name "switching method".

A switching method set by the user (or a default switching method) is set as a field value in the projection setting information with the field name “switching method”. The switching method is, as described above, the display mode at the time of switching when the image to be projected is switched to another image. Field values of the field name "switching method" include, for example, "none", "fade", and "cut". "None" is, for example, a display mode in which the image to be projected is simply switched to another image. "fade" is, for example, a display mode in which the image to be projected is faded out and the other image is faded in, thereby switching the image to be projected to another image. “Cut” is, for example, a display mode in which an image to be projected is cut out and another image is cut in, thereby switching the image to be projected to another image.

Also, the read range and rewrite range of the projection setting information with the field name "switching method" are "whole area". This indicates that the projection setting information with the field name “switching method” can be read and rewritten by programs other than the projection library 420 .

As described above, in the projection setting information instance 600, the reading range and rewriting range of the projection setting information held by the projection setting information instance 600 are set. This prevents the vendor development program 410 developed by a third vendor from referring to unnecessary projection setting information or from rewriting projection setting information to which only default values are applied, for example. can do. Note that the projection setting information held by the projection setting information instance 600 is not limited to the "switching method" described above.

Here, the reading range and rewriting range of the device information instance 500 and the projection setting information instance 600 can be realized using a Java language package. For example, as shown in FIG. 21, the package to which each class defined in the vendor development program 410 belongs is different from the package to which each class defined in the projection library 420 belongs.

Thus, by defining an access level for a method that operates a field (that is, device information) held by the device information instance 500, it is possible to limit the read range and rewrite range of this field. Similarly, by defining an access level for a method that manipulates a field (that is, projection setting information) held by the projection setting information instance 600, it is possible to limit the read range and rewrite range of this field. Hereinafter, the package name of the package to which each class defined in the projection library 420 belongs is assumed to be "projectionlibrary".

Although the example shown in FIG. 21 shows the case where each class defined in the vendor development program 410 belongs to the same package, the present invention is not limited to this. Also good.

Here, the device information class 2100 that implements the device information instance 500 will be described with reference to FIG. FIG. 22 is a diagram showing an example of the device information class 2100. As shown in FIG. The device information instance 500 is generated by instantiating the device information class 2100 shown in FIG. 22, for example.

As shown in FIG. 22, device information class 2100 includes package declaration 2101 and class declaration 2102 . A package name “projectionlibrary” is defined in the package declaration 2101 . Class declaration 2102 includes method declarations 2103 to 2110 for each device information.

Method declarations 2103 to 2106 and method declarations 2109 to 2110 are the same as the method declarations 1103 to 1106 and method declarations 1109 to 1110 of the device information class 1100 shown in FIG. 9, respectively, so description thereof will be omitted.

A method declaration 2107 defines a method “getResolution” for reading the device information with the field name “resolution”. Also, in the method declaration 2107, no access modifier is defined for this method "getResolution". As a result, the reading range "within the library" of the device information with the field name "resolution" is realized.

A method declaration 2108 defines a method “setResolution” for rewriting the device information with the field name “resolution”. Also, in the method declaration 2108, no access modifier is defined for this method "setResolution". As a result, the rewriting range "within the library" of the device information with the field name "resolution" is realized.

As described above, in the device information class 2100, by defining the access modifier "public" for methods for manipulating (reading or rewriting) device information, classes belonging to other packages can access device information. You will be able to perform operations on On the other hand, in the device information class 2100, by not defining access modifiers for methods for operating device information, classes belonging to other packages cannot operate device information. can.

Next, the projection setting information class 2200 that implements the projection setting information instance 600 will be described with reference to FIG. FIG. 23 is a diagram showing an example of the projection setting information class 2200. As shown in FIG. The projection setting information instance 600 is generated by instantiating the projection setting information class 2200 shown in FIG. 23, for example.

As shown in FIG. 23, projection setting information class 2200 includes package declaration 2201 and class declaration 2202 . A package name “projectionlibrary” is defined in the package declaration 2201 . Class declaration 2202 includes method declarations 2203 and 2204 for each piece of projection setting information.

A method declaration 2203 defines a method “getSwitch” for reading the projection setting information with the field name “switching method”. Also, in the method declaration 2203, the access modifier "public" of this method "getSwitch" is defined. As a result, the reading range “whole area” of the projection setting information with the field name “switching method” is realized.

A method declaration 2204 defines a method “setSwitch” for rewriting projection setting information with a field name “switching method”. Also, in the method declaration 2204, the access modifier "public" of this method "setSwitch" is defined. As a result, the rewrite range "whole area" of the projection setting information with the field name "switching method" is realized.

As described above, in the projection setting information class 2200, by defining the access modifier "public" for the method for manipulating (reading or rewriting) the projection setting information, classes belonging to other packages can access the method. It becomes possible to operate the projection setting information. On the other hand, the projection setting information class 2200 does not define access modifiers for methods for operating projection setting information, so that classes belonging to other packages cannot operate projection setting information. can do.

Next, a device information acquisition class 2300 that implements the device information acquisition unit 421 will be described with reference to FIG. FIG. 24 is a diagram showing an example of the device information acquisition class 2300. As shown in FIG. The device information acquisition part 421 is generated by instantiating the device information acquisition class 2300 shown in FIG. 24, for example.

As shown in FIG. 24, device information acquisition class 2300 includes package declaration 2301 and class declaration 2302 . A package name “projectionlibrary” is defined in the package declaration 2301 . Class declaration 2302 includes method declaration 2303 .

A method declaration 2303 defines a method “getProjectorInfo” for acquiring device information from the device 20 . Also, in the method declaration 2303, the access modifier "public" of this method "getProjectorInfo" is defined. This allows the method "getProjectorInfo" to be called from classes belonging to packages other than the same package (that is, classes defined in programs other than the projection library 420).

Next, a projection processing class 2400 that implements the projection processing unit 422 will be described with reference to FIG. FIG. 25 is a diagram showing an example of the projection processing class 2400. As shown in FIG. The projection processing unit 422 is generated by instantiating the projection processing class 2400 shown in FIG. 25, for example.

As shown in FIG. 25, projection processing class 2400 includes package declaration 2401 and class declaration 2402 . The package declaration 2401 defines a package name “projectionlibrary”. Class declaration 2402 includes method declaration 2403 .

A method declaration 2403 defines a method “project” for transmitting a projection request to the device 20 . Also, in the method declaration 2403, the access modifier "public" of this method "project" is defined. This allows the method "project" to be called from classes belonging to packages other than the same package (that is, classes defined in programs other than the projection library 420).

In the method declaration 2403, "ProjectorInfo info", "ProjectData data", and "ProjectSetting setting" are defined as arguments of the method "project". This indicates that device information, projection target data, and projection setting information are specified as arguments of the method "project".

Next, program code 2500 of vendor development program 410 will be described with reference to FIG. FIG. 26 is a diagram showing an example of program code 2500 of vendor development program 410 . Note that in FIG. 26, as an example, program code 2500 in which codes respectively corresponding to the device information acquisition requesting unit 411, the projection target data setting unit 413, the projection setting unit 414, and the projection execution requesting unit 416 are defined. explain. Codes corresponding to the display control unit 412, the execution operation receiving unit 415, etc. need to be defined separately.

As shown in FIG. 26, program code 2500 includes package declaration 2501 and class declaration 2502 . A package declaration 2501 defines a package name “projectionapp”. Therefore, the vendor development program 410 cannot call a method for which the access modifier "public" is not defined among the methods defined in each class belonging to the package name "projectionlibrary".

Class declaration 2502 includes projection execution class 2503 . The projection execution class 2503 includes a code definition 2504 defining a code corresponding to the device information acquisition requesting section 411 and a code definition 2505 defining a code corresponding to the projection setting section 414 . The projection execution class 2503 also includes a code definition 2506 defining a code corresponding to the projection target data setting unit 413 and a code definition 2507 defining a code corresponding to the projection execution requesting unit 416 .

As shown in the code definition 2507, the vendor development program 410 designates "info" indicating the device information instance 500 as an argument when calling the method "project" of the projection processing class 2400 belonging to the package name "projectionlibrary". As a result, in the process of the method "project", a method for which the access modifier "public" of the device information instance 500 is not defined can be called, and then a processing request (projection request) can be issued to the device 20. can. For example, in the process of the method "project", the method "getResolution" of "info" indicating the device information instance 500 is called to obtain the device information with the field name "resolution", and then a projection request specifying this device information is issued. can be performed on the device 20;

Therefore, the projection application 400 uses information that the vendor development program 410 cannot operate on the device 20 (for example, device information with the field name “resolution” and device information with the field name “network information”). It becomes possible to make a processing request (registration request).

<Projection processing>
Next, projection processing of the projection system 2 according to this embodiment will be described. Hereinafter, the processing when the user of the terminal device 10 uses the projection application 400 to project an image with the device 20 will be described with reference to FIG. 27 . FIG. 27 is a sequence diagram showing an example of projection processing according to the second embodiment.

27 below, except for the device information class 2100 and the projection setting information class 2200, each class defined in the vendor development program 410 and the projection library 420 is instantiated. Note that each class defined in the vendor development program 410 and the projection library 420 may include classes that have not been instantiated. In this case, it may be appropriately instantiated before executing the processing of the functional unit (instance) realized by the class. Also, the device information class 2100 and projection setting information class 2200 may be instantiated in advance.

First, the device information acquisition request unit 411 of the vendor development program 410 receives the device information acquisition operation by the user (step S201), as in step S101 of FIG.

The device information acquisition requesting unit 411 of the vendor development program 410 requests the device information acquisition unit 421 to acquire the device information upon receiving the device information acquisition operation by the user (step S202). The device information acquisition request unit 411 can make a device information acquisition request by calling the method “getProjectorInfo” defined in the method declaration 2303 of the device information acquisition class 2300 .

Upon receiving the device information acquisition request, the device information acquisition unit 421 of the projection library 420 inquires of the device 20 about the device information (step S203), as in step S103 of FIG. Then, the device information acquisition unit 421 receives the device information returned from the device 20 in response to the above inquiry. Accordingly, the device information acquisition unit 421 can acquire device information such as the IP address, model name, resolution, and network information from the device 20 .

Upon acquiring the device information from the device 20, the device information acquisition unit 421 of the projection library 420 generates the device information instance 500 (step S204). A device information instance 500 is generated by instantiating the device information class 2100 .

Next, the device information acquisition unit 421 of the projection library 420 sets the device information acquired from the device 20 in the device information instance 500 (step S205).

That is, the device information acquisition unit 421 calls the method “setIPAddress” defined in the method declaration 2104 of the device information class 2100 after specifying the IP address acquired from the device 20 as an argument. As a result, the device information with the field name “IP address” is set in the device information instance 500 .

Similarly, the device information acquisition unit 421 calls the method “setModelName” defined in the method declaration 2106 of the device information class 2100 after specifying the model name acquired from the device 20 as an argument. As a result, the device information with the field name “model name” is set in the device information instance 500 .

Similarly, the device information acquisition unit 421 calls the method “setResolution” defined in the method declaration 2108 of the device information class 2100 after specifying the resolution acquired from the device 20 as an argument. As a result, the device information with the field name “resolution” is set in the device information instance 500 .

Similarly, the device information acquisition unit 421 calls the method “setNetworkInfo” defined in the method declaration 2110 of the device information class 2100 after specifying the network information acquired from the device 20 as an argument. As a result, the device information with the field name “network information” is set in the device information instance 500 .

Then, the device information acquisition unit 421 returns the device information instance 500 in which each device information acquired from the device 20 is set to the vendor development program 410 .

The display control unit 412 of the vendor development program 410 acquires device information from the device information instance 500 returned from the device information acquisition unit 421 . Then, the display control unit 412 displays the device information acquired from the device information instance 500 on the display device 12 (step S206). At this time, the display control unit 412 can acquire the device information whose read range is "whole area" among the device information held in the device information instance 200, as in step S106 of FIG. . As a result, it is possible to prevent device information that the user does not necessarily need to refer to, such as resolution and network information, from being displayed.

Next, the projection target data setting unit 413 of the vendor development program 410 receives the user's selection operation of the projection target data (step S207). For example, in step S206, the user changes from the screen displaying the device information to the content data list screen, and then selects desired content data from the content data list screen. selection operation can be performed.

The projection target data setting unit 413 of the vendor development program 410 receives the user's selection operation of the projection target data, and sets the selected content data as the projection target data (step S208). Note that if the projection target data is set in advance before the process of step S201 is executed, the processes of steps S207 and S208 do not have to be executed.

Next, the projection setting unit 414 of the vendor development program 410 receives the operation of specifying the projection setting information by the user (step S209). For example, the user can specify projection setting information by specifying a setting value for each piece of projection setting information on a predetermined screen displayed after selecting projection target data. Note that if the user does not change the projection setting information (that is, if the default value is used as the setting value of the projection setting information), the processing of this step may not be executed.

The projection setting unit 414 of the vendor development program 410 generates the projection setting information instance 600 (step S210). A projection setting information instance 600 is generated by instantiating the projection setting information class 2200 .

Next, the projection setting unit 414 of the vendor development program 410 sets the projection setting information specified by the user in step S209 to the projection setting information instance 600 (step S211).

That is, the projection setting unit 414 calls the method “setSwitch” defined in the method declaration 2204 of the projection setting information class 2200 after specifying the switching method specified by the user as an argument. As a result, the projection setting information with the field name “switching method” is set in the projection setting information instance 600 .

Next, the execution operation reception unit 415 of the vendor development program 410 receives a projection execution operation by the user (step S212). For example, the user can perform a projection execution operation by pressing a projection execution button on a predetermined screen displayed after specifying projection setting information.

When the execution operation receiving unit 415 receives the projection execution operation, the projection execution requesting unit 416 of the vendor development program 410 requests the projection processing unit 422 to execute projection (step S213). This projection execution request includes an equipment information instance 500 , projection target data, and a projection setting information instance 600 . The projection execution request unit 416 designates the device information instance 500, the projection target data, and the projection setting information instance 600 as arguments, and then executes the method "project" defined in the method declaration 2403 of the projection processing class 2400. By calling it, a projection execution request can be made.

By specifying the device information instance 500 as an argument to the method "project", for example, when a plurality of device information instances 500 exist (that is, for example, when there are a plurality of devices 20 When the device information is acquired from each device 20), it becomes possible to specify which device information instance 500 is to be used. Therefore, it becomes possible to manage a plurality of pieces of information that cannot be operated from the vendor development program 410 .

For example, when a plurality of device information instances 500 exist, device information with the field name “resolution” exists for each device 20 . In this case, none of the device information with the field name “resolution” can be referenced from the vendor development program 410 . For this reason, the vendor development program 410 cannot directly specify one of these pieces of device information, but by specifying the device information instance 500, the vendor development program 410 can eventually determine the resolution of which device 20 to use. can be specified.

The projection processing unit 422 of the projection library 420 uses the projection data generation unit 423 to acquire the resolution from the device information instance 500 included in the projection execution request (step S214). That is, the projection data generation unit 423 acquires the device information with the field name “resolution” from among the device information held in the device information instance 500 . The projection data generation unit 423 can acquire the device information with the field name “resolution” by calling the method “getResolution” defined in the method declaration 2107 of the device information class 2100 . Since the projection processing class 2400 that implements the projection processing unit 422 and the device information class 2100 belong to the same package “projectionlibrary”, the projection data generation unit 423 can call the method “getResolution”.

Next, the projection processing unit 422 of the projection library 420 acquires the projection setting information from the projection setting information instance 600 included in the projection execution request by the projection data generation unit 423 (step S215). That is, the projection data generator 423 acquires projection setting information held in the projection setting information instance 600 . The projection data generation unit 423 can acquire the projection setting information with the field name “switching method” by calling the method “getSwitch” defined in the method declaration 2203 of the projection setting information class 2200 .

Next, the projection processing unit 422 of the projection library 420 uses the projection data generation unit 423 to generate projection data (step S216). That is, the projection data generation unit 423 generates projection data from the projection target data using the resolution acquired in step S214. At this time, the projection data generation unit 423 generates projection data by, for example, converting the projection target data into the resolution acquired in step S214.

Next, the projection processing unit 422 of the projection library 420 acquires the network information from the device information instance 500 included in the projection execution request by the projection request unit 424, as in step S117 of FIG. 14 (step S217).

Next, the projection processing unit 422 of the projection library 420 determines whether communication with the device 20 is possible based on the network information acquired in step S217 by the projection requesting unit 424, as in step S118 of FIG. (step S218).

In step S218, if it is determined that communication with the device 20 is possible, the projection processing unit 422 of the projection library 420 causes the projection request unit 424 to transmit the device information included in the projection execution request, as in step S119 of FIG. An IP address is obtained from the instance 500 (step S219).

Next, the projection processing unit 422 of the projection library 420 causes the projection request unit 424 to transmit a projection request to the device 20 (step S420). That is, the projection request unit 424 transmits a projection request to the IP address obtained in step S219 above, for example, via a wireless LAN such as Wi-Fi. The projection request includes the projection data generated in step S216 above. As a result, the device 20 that has received the projection request projects the image indicated by the projection data, and returns the projection result.

On the other hand, if it is determined in step S218 that communication with the device 20 is not possible, the projection processing unit 422 of the projection library 420 returns an error to the vendor development program 410 via the projection request unit 424. FIG. As a result, for example, an error screen indicating that projection cannot be performed is displayed on the display device 12 .

<Summary of Second Embodiment>
As described above, in the projection system 2 according to the present embodiment, various information managed by the projection library 420 provided by the manufacturer of the device 20, which is a projector, can be read by the vendor development program 410 developed by the third vendor. Rewriting can be restricted. As a result, in the projection system 2 according to the present embodiment, various kinds of information managed by the projection library 420 are prevented from being illegally rewritten by the vendor development program 410 or unnecessary information is referred to. can do.

Further, in the projection system 2 according to the present embodiment, by restricting rewriting of information by the vendor development program 410, unintended operations of the device 20 can be prevented.

[Third embodiment]
Next, a third embodiment will be described. In the first and second embodiments, an executable application (the printing application 100 or the projection application 400) is installed in the terminal device 10, but the application has defined program code. It is created by compiling the source file. Therefore, in the third embodiment, the development terminal 30, which is, for example, a PC (personal computer, etc.), compiles the source file to create an executable (for example, Java bytecode) application (printing application 100 or projection application). A case of creating an application 400) will be described. Hereinafter, the print application 100 or the projection application 400 will be referred to as an "application 700".

In addition, in the third embodiment, mainly the differences from the first embodiment and the second embodiment are explained, and the same components as the first embodiment and the second embodiment are The description is omitted or simplified as appropriate.

<Functional configuration>
First, the functional configuration of the development terminal 30 according to this embodiment will be described with reference to FIG. FIG. 28 is a diagram showing an example of the functional configuration of the development terminal 30 according to the third embodiment.

As shown in FIG. 28, the development terminal 30 according to this embodiment has a compilation processing section 800 . The functional unit is implemented by processing that one or more programs installed in the development terminal 30 cause the CPU to execute.

Further, the development terminal 30 according to this embodiment has a storage unit 900 . The storage unit can be implemented using, for example, an auxiliary storage device such as an HDD or SSD. Note that the storage unit may be implemented using a storage device or the like connected to the development terminal 30 via a network.

A source file 910 and a library 920 are stored in the storage unit 900 . The source file 910 is a file describing the source code of the vendor development program 110 when the application 700 to be created is the printing application 100, and the vendor development program 410 when the application 700 to be created is the projection application 400. It is a file that describes the source code of The library 920 is the printing library 120 when the application 700 to be created is the printing application 100 , and is the projection library 420 when the application 700 to be created is the projection application 400 .

The library 920 is distributed by the manufacturer of the device 20, for example, together with a manual describing how to use APIs (methods) defined in the library 920 (for example, how to specify arguments).

Compile processing unit 800 receives source file 910 and library 920 and compiles source file 910 (more precisely, compiles source file 910 and library 920) to create executable application 700. do. At this time, the compilation processing unit 800 determines whether or not the access relationship is normally defined between the method to be called and the class that called this method.

That is, the compile processing unit 800 determines whether the class in which the method to be called is defined and the class from which the method is called belong to the same package. Also, when it is determined that these classes do not belong to the same package, the compilation processing unit 800 determines whether an access identifier "public" is defined for the method.

Then, when the compile processing unit 800 determines that the access relationships are normally defined for all the methods of the source file 910 , it compiles the source file 910 to create the executable application 700 . On the other hand, when the compile processing unit 800 determines that the access relationship is not normally defined for at least one method, it displays an error screen, for example.

<Compile processing>
Next, the compilation process executed by the development terminal 30 according to this embodiment will be described. Hereinafter, a process in which a user of the development terminal 30 (for example, an application developer such as a third vendor) compiles the source file 910 to create the executable application 700 will be described with reference to FIG. FIG. 29 is a flowchart showing an example of compilation processing according to the third embodiment. The processing shown in FIG. 29 is started when the source file 910 and the library 920 are input to the compile processing unit 800 in response to an operation by the user of the development terminal 30 (operation to start compiling the source file 910). , is repeatedly executed for each code indicating the method calling process defined in the source file 910 .

First, the compilation processing unit 800 determines whether or not the class of the method to be called defined in the code is in the same package as the caller class (step S301).

If it is determined in step S301 that the class of the method to be called is not in the same package as the class of the caller, the compilation processing unit 800 determines whether the access modifier "public" is defined for the method. is determined (step S302).

If it is determined in step S301 that the class of the method to be called is in the same package as the calling class, or if the access modifier "public" is defined for the method in step S302. When determined, the compilation processing unit 800 determines that the access relationship of the method is normally defined (step S303).

On the other hand, if it is determined in step S302 that the access modifier "public" is not defined for the method, the compilation processing unit 800 determines that the access relationship of the method is not properly defined (error (step S304). In this case, the compilation processing unit 800 displays an error screen indicating that the access relationship of the methods defined in the source file 910 is not normal, and terminates the compilation processing.

On the other hand, if it is determined that the access relationships are normally defined for all the methods in the source file 910, the compile processing unit 800 compiles the source file 910 and the library 920 into an executable format. An application 700 is created (step S305). As a result, an application 700 (printing application 100 or projection application 400) is created in which operations by the vendor development program 110 or the vendor development program 410 are restricted for various information managed by the library 920. FIG. More precisely, the application 700 is created by linking object files created by compiling the source file 910 and the library 920 respectively.

The invention is not limited to the specifically disclosed embodiments above, but various modifications and changes are possible without departing from the scope of the claims.

1 printing system 10 terminal device 20 device 100 print application 110 vendor development program 111 device information acquisition request unit 112 display control unit 113 print target data setting unit 114 print setting unit 115 execution operation reception unit 116 print execution request unit 120 print library 121 device Information acquisition unit 122 print processing unit 123 print data generation unit 124 print request unit 200 device information instance 300 print setting information instance

JP 2013-152743 A

Claims (12)

An information processing device having a program that provides a predetermined function,
an acquisition unit that acquires information including predetermined information from a device connected to the information processing device in response to a first request from the program;
By converting the information acquired by the acquisition unit into a class belonging to a package different from the program and having no defined access modifier for updating or referring to the predetermined information, a request control unit that restricts the program from requesting updates or references to information;
In response to a second request from the program, based on the predetermined information, which is the information acquired by the acquisition unit and the request from the program is restricted by the request control unit, to the device , a processing request unit that requests execution of processing corresponding to the second request;
An information processing device comprising: The program is a program written in Java language,
The request control unit
By setting the information acquired by the acquisition unit to an instance generated from a class in which an access modifier is not defined in a method for updating the predetermined information, the program cannot request update. 2. The information processing apparatus according to claim 1 , wherein the limit is set to . The program is a program written in Java language,
The request control unit
By setting the information acquired by the acquisition unit to an instance generated from a class in which an access modifier is not defined in a method for referring to the predetermined information, the program cannot request a reference. 2. The information processing apparatus according to claim 1 , wherein the limit is set to . a storage control unit that stores a plurality of pieces of information acquired by the acquisition unit in association with one piece of identification information;
The processing request unit is
In response to a second request including the identification information from the program, based on the predetermined information for which the request is restricted by the request control unit, among the plurality of pieces of information associated with the identification information, 2. The information processing apparatus according to claim 1, wherein the device is requested to execute a process corresponding to the second request. the device is an image processing device capable of executing at least print processing;
The processing request unit is
requesting the device to execute the printing process in response to a second request from the program, based on the predetermined information for which requests are restricted by the request control unit. The information processing device according to claim 1 . 2. The information processing apparatus according to claim 1, wherein the information acquired by said acquisition unit includes at least an IP address of said device and network information. 2. The information processing apparatus according to claim 1, wherein said program is a program developed by a third vendor different from a manufacturer of said device. 2. The information processing apparatus according to claim 1, wherein said acquisition unit and said processing request unit are executed by a program different from said program. The request control unit
performing control not to accept a request for the predetermined information from the program;
9. The information processing apparatus according to claim 8 , wherein control is performed to receive a request for said predetermined information from said processing request unit. An information processing device having a program that provides a predetermined function,
an acquisition procedure for acquiring information including predetermined information from a device connected to the information processing device in response to a first request from the program;
By making the information acquired by the acquisition procedure a class belonging to a package different from the program and having no defined access modifier for updating or referring to the prescribed information, a request control procedure for restricting information from being requested to be updated or referenced by the program;
In response to a second request from the program, based on the predetermined information, which is the information acquired by the acquisition procedure and for which requests from the program are restricted, the second request is sent to the device. a process request procedure that requests execution of a process corresponding to the request;
program to run the An information processing system including an information processing device having a program that provides a predetermined function and an image processing device capable of executing predetermined image processing,
an acquisition unit that acquires information including predetermined information from the image processing device in response to a first request from the program;
By converting the information acquired by the acquisition unit into a class belonging to a package different from the program and having no defined access modifier for updating or referring to the predetermined information, a request control unit that restricts the program from requesting updates or references to information;
In response to a second request from the program, based on the predetermined information, which is the information acquired by the acquisition unit and the request from the program is restricted by the request control unit, the image processing apparatus a processing request unit for requesting execution of processing corresponding to the second request;
An information processing system characterized by having: An information processing method executed by an information processing device having a program that provides a predetermined function,
an acquisition procedure for acquiring information including predetermined information from a device connected to the information processing device in response to a first request from the program;
By converting the information acquired by the acquisition procedure into a class belonging to a package different from the program and having no defined access modifier for updating or referring to the prescribed information, a request control procedure that restricts the program from requesting updates or references to the information of
in response to a second request from the program, to the device based on the predetermined information, which is the information acquired by the acquisition procedure and for which requests from the program are restricted by the request control procedure; , a process request procedure for requesting execution of a process corresponding to the second request;
An information processing method characterized by having

Images