JP2024018390A - Communication device and computer program for communication device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a communication device that can appropriately execute processing in consideration of character codes.

SOLUTION: A communication device may include: a memory that stores, for each of a plurality of OIDs of an MIB, management information in which the OID is associated with a setting value; a setting command receiving unit that receives a setting command in accordance with TCP of the transport layer of the OSI reference model from a terminal device, in which the setting command includes a first OID and a first value written in UTF; a first conversion unit that converts the first value included in the setting command into a second value written in non-UTF when the setting command is received from the terminal device; and a writing unit that writes the converted second value into the management information in association with the first OID included in the setting command.

SELECTED DRAWING: Figure 3

COPYRIGHT: (C)2024,JPO&INPIT

Description

This specification discloses a technology related to a communication device that stores management information in which an OID (abbreviation for Object ID) and a setting value are associated.

Patent Document 1 describes that a PC can acquire device information corresponding to OID (abbreviation of Object ID) of MIB (abbreviation of Management Information Base) from office equipment according to HTTP (abbreviation of Hyper Test Transfer Protocol). Disclosed.

Japanese Patent Application Publication No. 2004-264995

The above techniques do not take character codes into consideration at all. This specification discloses a communication device that can appropriately execute processing in consideration of character codes.

The communication device disclosed in this specification stores, for each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base), management information in which the OID is associated with a setting value. A configuration command receiving unit that receives a configuration command in accordance with TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a memory and a terminal device, the configuration command comprising: , a first OID, and a first value written in UTF (Unicode Transformation Format); when the configuration command is received from the terminal device; a first conversion unit that converts the first value included in the configuration command into a second value written in non-UTF; and a first conversion unit that converts the first value included in the configuration command into a second value written in non-UTF; The information processing apparatus may further include a writing unit that writes a second value to the management information.

According to the above configuration, the communication device converts the first value written in UTF to the second value written in non-UTF, associates the second value with the first OID, and stores the second value in the management information. write to. Therefore, the communication device can appropriately execute the write process in consideration of the character code.

The communication device disclosed in this specification stores, for each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base), management information in which the OID is associated with a setting value. An acquisition command receiving unit that receives an acquisition command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a memory and a terminal device, wherein the acquisition command is , the acquisition command receiving unit including the second OID, and when the acquisition command is received from the terminal device, the acquisition command receiving unit includes the second OID included in the acquisition command from the management information in the memory. an acquisition unit that acquires an associated third value that is written in non-UTF (abbreviation for Unicode Transformation Format); and a response command transmitter that transmits a response command including the converted fourth value to the terminal device.

According to the above configuration, the communication device converts the third value written in non-UTF to the fourth value written in UTF, and sends a response command including the fourth value to the terminal device. . Therefore, the communication device can appropriately execute response processing in consideration of the character code.

A computer program for implementing the above-described communication device and a computer-readable storage medium that stores the computer program are also new and useful. Also, the method performed by the communication device described above is novel and useful.

The configuration of the communication system is shown. A flowchart of command processing is shown. A flowchart of POST processing is shown. A flowchart of GET processing is shown. A sequence diagram of a case in which a POST command is communicated is shown. An example of a POST command and a response command is shown. A sequence diagram of a case in which a GET command is communicated is shown. An example of a GET command and a response command is shown.

(First example)
(Configuration of communication system 2; Figure 1)
As shown in FIG. 1, the communication system 2 includes a printer 10 and a terminal device 100. Each device 10, 100 is connected to a LAN (abbreviation for Local Area Network) 6 and can communicate with each other via the LAN 6. The LAN 6 may be a wired LAN or a wireless LAN. The terminal device 100 is a user terminal such as a desktop PC, a notebook PC, a tablet PC, or a mobile phone (for example, a smartphone). In this embodiment, the printer 10 writes or transmits setting values in response to a request command (that is, a POST command or a GET command, which will be described later) from the terminal device 100.

(Configuration of printer 10)
The printer 10 is a peripheral device (for example, a peripheral device of the terminal device 100) that can execute a printing function. In a modified example, the printer 10 may be a multi-function device that can perform a scanning function, a FAX function, etc. in addition to the printing function. The printer 10 includes an operation section 12, a display section 14, a LAN interface 16, a print execution section 18, and a control section 30. Each part 12 to 30 is connected to a bus line (numerals omitted).

The operation unit 12 includes a plurality of keys. A user can input various instructions to the printer 10 by operating the operation unit 12. The display unit 14 is a display that displays various information. The display unit 14 also functions as a so-called touch panel (that is, an operation unit that accepts user operations). LAN interface 16 is connected to LAN 6. The printing execution unit 18 includes a printing mechanism such as an inkjet type or a laser type.

The control unit 30 includes a CPU 32, a nonvolatile memory 34A, and a volatile memory 34B. The CPU 32 executes various processes according to the program 36 stored in the nonvolatile memory 34A. The nonvolatile memory 34A is a memory whose stored information is not erased even if the printer 10 is powered off. In addition to the program 36, the nonvolatile memory 34A stores a management table 38, a judgment list 40, a language setting 42, a language table 44, and a plurality of code tables 46. The volatile memory 34B is a memory whose stored information is erased when the power of the printer 10 is turned off. The volatile memory 34B temporarily stores information necessary for the CPU 32 to execute processing.

The management table 38 is a table for storing various information about the printer 10. The information includes, for example, the remaining amount of consumables of the printer 10, the MAC address, the name (ie, user name), the IP address, and the like. Information not illustrated in FIG. 1 includes, for example, the installation location of the printer 10, access destination, error history, status (printing in progress, standby, etc.), print settings (for example, default print resolution), and the like. The management table 38 stores the various information described above using a tree structure (that is, a hierarchical structure). This collection of various information having a tree structure is called "MIB" (abbreviation for Management Information Base).

Specifically, the management table 38 stores content, OID (abbreviation for Object ID), type, and MIB value in association with each other. The content is a character string that indicates the meaning of the information. OID is an identifier that identifies information. Type indicates the type of MIB value. The MIB value indicates a specific value of information (ie, a set value).

In the management table 38, many MIB values are described using UTF-8 character codes. UTF-8 is an abbreviation for Unicode Transformation Format-8 in Unicode, and is an abbreviation for UCS Transformation Format 8 in ISO/IEC10646. In the following, UTF-8 will be simply referred to as "UTF." If the MIB value type is integer or hex string, the MIB value is written in UTF. For example, the MIB value "80" corresponding to the remaining amount of consumables is written as "38 30" in UTF. If the MIB value type is string, the MIB value may be written in UTF or in a character code different from UTF (hereinafter simply referred to as "non-UTF"). Sometimes it is written.

As described above, in the management table 38, some MIB values are written in non-UTF. This is based on the viewpoint of maintaining compatibility of various conventional printers. In the example of FIG. 1, the MIB value corresponding to the name means a string of three letters in Portuguese. The three characters include a "C" with a cedilla, an "E" with a grave accent, and an "E" with an acute accent. The MIB value indicating such a Portuguese character string is described by ISO8859-1, which is a non-UTF character code corresponding to Portuguese. For example, the above three characters are written as "C7 C8 C9" in ISO8859-1.

Non-UTF is not limited to ISO8859-1, but also includes ISO8859-2, ISO8859-3, and ISO8859-5. That is, in this embodiment, the non-UTF is an ISO8859 character code, or in other words, an 8-bit character code. The non-UTF in which the MIB values in the management table 38 are written depends on the language setting 42 of the printer 10.

The determination list 40 is a list for determining whether the MIB value in the management table 38 is written in UTF or non-UTF. The information in decision list 40 is predetermined by the vendor of printer 10. The judgment list 40 includes a plurality of OIDs. Each of these OIDs corresponds to a MIB value written in non-UTF. That is, the judgment list 40 does not include OIDs corresponding to MIB values written in UTF. Therefore, it is possible to suppress the capacity of the judgment list 40 from increasing.

The language setting 42 is the language setting of the printer 10, and is usually specified by the user when the printer 10 is started up for the first time. In this embodiment, one of various languages such as English, Portuguese, Czech, and Japanese is specified as the language setting 42.

Language table 44 shows the non-UTF corresponding to each of the various languages. For example, the non-UTF corresponding to English, German, Portuguese, etc. is ISO8859-1, and the non-UTF corresponding to Czech, Hungarian, etc. is ISO8859-2. Although not shown in FIG. 1, the non-UTF corresponding to Turkish and other languages is ISO8859-3, and the non-UTF corresponding to Russian and other languages is ISO8859-5. Note that in this embodiment, Japanese, Chinese, and Korean are written in UTF. Therefore, the language table 44 does not include Japanese or the like.

The code table 46 includes a UTF code table and a non-UTF code table. Non-UTF code tables include code tables such as ISO8859-1, ISO8859-2, and ISO8859-3.

(Communication protocol between printer 10 and terminal device 100)
As a communication protocol for communicating MIB values between the printer 10 and the terminal device 100, a protocol according to UDP (abbreviation for User Datagram Protocol) of the transport layer of the OSI (abbreviation for Open Systems Interconnection) reference model is used. widely known. Specifically, SNMP (abbreviation for Simple Network Management Protocol) is known. The present inventors created the use of a communication protocol in accordance with TCP (abbreviation for Transmission Control Protocol) of the transport layer of the OSI reference model, instead of UDP, as a communication protocol for communicating MIB values. . Specifically, we created the use of HTTPS (abbreviation for Hyper Text Transfer Protocol Secure). This is because HTTPS has higher security than SNMP because it employs user authentication and data encryption. Thereby, it is possible to prevent the MIB value of the printer 10 from being illegally written or illegally acquired by a third party.

The terminal device 100 can write MIB values to the printer 10 using an HTTPS POST command, and can also acquire MIB values from the printer 10 using an HTTPS GET command. Usually, the HTTPS command and its response command adopt a general-purpose format such as JSON (abbreviation for Java Script Object Notation) or XML (abbreviation for Extensible Markup Language). In these general-purpose formats, information is written in UTF-8. Therefore, in this embodiment, communication between the printer 10 and the terminal device 100 is performed using HTTPS commands and their response commands in the JSON format in which information is written in UTF-8. Note that in a modified example, an XML format may be adopted instead of the JSON format. Even in this case, communication of the HTTPS command and its response command whose information is written in UTF-8 is executed.

As described above, in view of maintaining compatibility, the management table 38 of the printer 10 may store MIB values written in ISO8859-based non-UTF. Therefore, in this embodiment, the printer 10 converts MIB values between UTF and non-UTF, stores the MIB values in the management table 38, and communicates HTTPS commands with the terminal device 100. , execute. In order to achieve this, the printer 10 executes each process shown in FIG. 2 and thereafter.

(Command processing of printer 10: Figure 2)
With reference to FIG. 2, command processing executed by the CPU 32 of the printer 10 will be described. The process shown in FIG. 2 is executed when the power of the printer 10 is turned on as a trigger.

In S10, the CPU 32 monitors reception of an HTTPS command from the terminal device 100. When receiving an HTTPS command from the terminal device 100, the CPU 32 determines YES in S10 and proceeds to S12.

In S12, the CPU 32 determines whether the user authentication was successful. Specifically, in response to the HTTPS command received in S10, the CPU 32 transmits to the terminal device 100 a response command indicating that user authentication has not yet been successful (that is, Unauthorized). Then, the CPU 32 receives an HTTPS command including authentication information (for example, a user password) from the terminal device 100, and determines whether the authentication information included in the HTTPS command matches the authentication information stored in the printer 10. to judge. If these pieces of authentication information match, the CPU 32 transmits a response command indicating successful authentication to the terminal device 100, determines YES in S12, and proceeds to S14. In this way, the MIB value is written and transmitted on the condition that the user authentication is successful, so the security of the printer 10 can be enhanced. On the other hand, if these pieces of authentication information do not match, the CPU 32 determines NO in S12 and ends the process of FIG.

In S14, the CPU 32 exchanges encryption keys with the terminal device 100. As a result, information in the HTTPS command and response command is encrypted in subsequent communications between the printer 10 and the terminal device 100 (for example, S20, S150 in FIG. 3, and S250 in FIG. 4). In this way, since the information in the command is encrypted, the security of the printer 10 can be increased.

In S20, the CPU 32 monitors reception of an HTTPS command from the terminal device 100. The information in the HTTP command is encrypted (see S14). When receiving an HTTPS command from the terminal device 100, the CPU 32 determines YES in S20 and proceeds to S22.

In S22, the CPU 32 determines whether the HTTPS command received in S20 is a POST command or a GET command. The CPU 32 proceeds to S30 when the HTTPS command is a POST command, and proceeds to S40 when the HTTPS command is a GET command. The POST command is a command that follows the HTTP POST method. The GET command may be a command according to the HTTP GET method, or a command according to the HTTP POST method in which "X-HTTP-Method-Override "GET"" is written in the header. .

The CPU 32 executes the POST process (see FIG. 3) in S30, and executes the GET process (see FIG. 4) in S40. When the POST process or the GET process ends, the CPU 32 ends the process in FIG. .

(POST processing: Figure 3)
Next, with reference to FIG. 3, the contents of the POST process in S30 of FIG. 2 will be explained. In S100, CPU 32 identifies one item in the POST command received in S20. One item specified here includes an OID, type, and MIB value. The type is information indicating the type of MIB value, such as string or integer. In the following, each piece of information included in one item identified in S100 will be referred to as "target OID,""targettype," and "target MIB value."

In S110, the CPU 32 determines whether the target type is string. If the target type is string, the CPU 32 determines YES in S110 and proceeds to S112. On the other hand, if the target type is not string, for example, if the target type is integer, hex string, etc., the CPU 32 determines NO in S110 and proceeds to S130. In this way, the printer 10 can switch whether or not to convert the target MIB value depending on the target type.

In S112, the CPU 32 determines whether the target MIB value is a conversion target. Specifically, the CPU 32 determines whether the target OID is included in the determination list 40 or not. If the target OID is included in the determination list 40, the CPU 32 determines YES in S112 and proceeds to S114. On the other hand, if the target OID is not included in the determination list 40, the CPU 32 determines NO in S112 and proceeds to S130. In this manner, the printer 10 can switch whether or not to convert the target MIB value depending on whether the target OID is included in the determination list 40 or not.

In S114, the CPU 32 determines whether the language setting 42 is Japanese, Chinese, or Korean. That is, the CPU 32 determines whether the language setting 42 indicates a language written in UTF or a language written in non-UTF. Japanese, Chinese, and Korean are not described in the language table 44. Therefore, the process of S114 is equivalent to the process of determining whether the language setting indicates a language that is not described in the language table 44. If the language setting 42 is Japanese or the like, the CPU 32 determines YES in S114 and proceeds to S130. If the language setting 42 is not Japanese, for example, if the language setting 42 is English, Portuguese, etc., the CPU 32 determines NO in S114 and proceeds to S120. In this way, the printer 10 can switch whether or not to convert the target MIB value according to the language setting 42.

In S120, the CPU 32 uses the language table 44 to identify the ISO character code (ie, non-UTF) corresponding to the language setting 42. For example, if the language setting 42 is Portuguese, the CPU 32 specifies ISO8859-1. In the following, the non-UTF specified here will be referred to as a "target character code." In this manner, the printer 10 specifies the target character code corresponding to the language setting 42, so that it can convert to an appropriate character code according to the language setting 42.

In S122, the CPU 32 identifies a UTF code table and a target character code code table from the code table 46, and uses these code tables to convert the target MIB value from UTF to the target character code.

In S130, the CPU 32 writes the MIB value into the management table 38. In S130 after S122, the CPU 32 writes the MIB value converted in S122 (that is, the MIB value written in the target character code) into the management table 38. In S130 after NO in S110, NO in S112, or YES in S114, the CPU 32 writes the target MIB value (that is, the MIB value written in UTF) into the management table 38.

In S140, the CPU 32 determines whether the next item in the POST command exists. If the next item exists, the CPU 32 determines YES in S140, specifies the next item in S100, and executes the processes from S110 onwards again. If the next item does not exist, the CPU 32 determines NO in S140 and proceeds to S150.

In S150, CPU 32 transmits a response command to terminal device 100. The response command includes the OID in each item identified in S100 and status information indicating that writing of the MIB value has been completed. The information in the response command is encrypted (see S14 in FIG. 2). When S150 ends, the POST process in FIG. 3 ends.

(GET processing: Figure 4)
Next, with reference to FIG. 4, the contents of the GET process in S40 of FIG. 2 will be explained. In S200, the CPU 32 identifies one item in the GET command received in S20. One item specified here includes an OID. Hereinafter, the OID included in one item identified in S200 will be referred to as a "target OID."

In S202, the CPU 32 reads the type and MIB value associated with the target OID from the management table 38. In the following, the type and MIB value read here will be referred to as "target type" and "target MIB value", respectively.

S210 to S220 are similar to S110 to S120 in FIG. 3. In this way, the printer 10 determines whether the target OID is included in the determination list 40 depending on the target type (i.e., depending on the determination in S210), and whether the target OID is included in the determination list 40 (i.e., in response to the determination in S212). Depending on the language setting 42 (that is, depending on the determination in S214), it is possible to switch whether or not to convert the target MIB value. Furthermore, since the printer 10 specifies the target character code corresponding to the language setting 42 (that is, executes S220), it can convert to an appropriate character code according to the language setting 42.

In S222, the CPU 32 identifies the UTF code table and the target character code code table from the code table 46, and uses these code tables to convert the target MIB value from the target character code to UTF.

In S230, the CPU 32 writes the MIB value to the response command. In S230 after S222, the CPU 32 writes the MIB value converted in S222 (that is, the MIB value written in UTF) to the response command. In S230 after NO in S210, NO in S212, or YES in S214, the CPU 32 writes the target MIB value (that is, the MIB value written in UTF) to the response command.

In S240, the CPU 32 determines whether the next item in the GET command exists. If the next item exists, the CPU 32 determines YES in S240, specifies the next item in S200, and executes the processes from S202 onwards again. If the next item does not exist, the CPU 32 determines NO in S240 and proceeds to S250.

In S250, CPU 32 transmits a response command to terminal device 100. The response command includes the OID in each item specified in S200, each MIB value written in S230, and status information indicating that writing of the MIB value is completed. The information in the response command is encrypted (see S14 in FIG. 2). When S250 ends, the GET process in FIG. 4 ends.

(Specific case)
Next, specific cases realized by the processes shown in FIGS. 2 to 4 will be described with reference to FIGS. 5 to 8. FIG. 5 shows a case where a POST command is sent from the terminal device 100 to the printer 10. FIG. 7 shows a case where a GET command is sent from the terminal device 100 to the printer 10. In each case of FIGS. 5 and 7, the language setting 42 of the printer 10 is Portuguese, and each MIB value shown in FIG. 1 is written in the management table 38.

(POST command case: Figure 5)
The terminal device 100 receives a write operation from the user at T10. The write operation includes an operation of specifying two pieces of information to be written, a "name" and an "IP address," and an operation of specifying a changed character string for each of the two pieces of information. In this case, the terminal device 100 transmits an HTTPS command to the printer 10 at T12.

When the printer 10 receives the HTTPS command from the terminal device 100 at T12 (YES at S10 in FIG. 2), the printer 10 transmits a response command indicating Unauthorized to the terminal device 100 at T14 (S12).

When the terminal device 100 receives the response command from the printer 10 at T14, it displays a screen for inputting authentication information (not shown), and receives an operation from the user to input authentication information at T20. In this case, the terminal device 100 transmits an HTTPS command including authentication information to the printer 10 at T22.

Upon receiving the HTTPS command from the terminal device 100 at T22, the printer 10 transmits a response command indicating successful authentication to the terminal device 100 at T24 (YES at S12). Then, at T30, the printer 10 exchanges the encryption key with the terminal device 100 (S14).

After the terminal device 100 exchanges the encryption key with the printer 10 at T30, the terminal device 100 transmits the POST command 200 corresponding to the write operation at T10 to the printer 10 at T32. Specifically, similar to the management table 38 of the printer 10, the terminal device 100 stores information contents, OIDs, and types in association with each other. Therefore, the terminal device 100 can identify the last 4 OID and the type "string" from the information "name" specified in the write operation of T10, and write these information to the POST command 200. . Similarly, the terminal device 100 can identify the OID at the end of 5 and the type "string" from the information "IP address" specified in the write operation of T10, and write these information to the POST command 200. can.

As shown in FIG. 6, the POST command 200 is written in JSON format and includes a header section and a body section. The body portion includes two items 202 and 204. Item 202 includes the OID with the last 4 corresponding to the information "name", the type "string", and the MIB value "C3,8D C3,93" written in UTF. Item 204 includes the OID with the last 5 corresponding to the information "IP address", the type "string", and the MIB value "31 37 32..." written in UTF.

When the printer 10 receives the POST command 200 from the terminal device 100 at T32 (YES at S20, POST at S22), it sequentially processes each of the two items 202 and 204.

The printer 10 determines that the type of the item 202 is string (YES in S110 of FIG. 3). Since the last 4 OIDs are included in the determination list 40, the printer 10 determines that the MIB value is to be converted (YES in S112). The printer 10 determines that the language setting 42 is Portuguese (NO in S114), and specifies a non-UTF (ie, ISO8859-1) corresponding to Portuguese from the language table 44 (S120). At T40, the printer 10 converts the MIB value "C3,8D C3,93" written in UTF to the MIB value "CD D3" written in ISO8859-1 (S122). Then, the printer 10 writes the MIB value "CD D3" described in ISO8859-1 in the management table 38 in association with the OID with the last 4 (S130).

The printer 10 determines that the type of the item 204 is string (YES in S110). Since the last 5 OIDs are not included in the determination list 40, the printer 10 determines that the MIB value is not a conversion target (NO in S112). Therefore, the printer 10 does not convert the MIB values "31 37 32..." written in UTF. At T42, the printer 10 writes the MIB value "31 37 32..." written in UTF into the management table 38 in association with the OID with the last 5 (S130).

When the printer 10 executes the processing on the two items 202 and 204 (NO at S140), it transmits the response command 210 to the terminal device 100 at T44 (S150). As shown in FIG. 6, the response command 210 is written in JSON format and includes a header section and a body section. The body portion includes two items 212 and 214. Item 212 includes the same OID as the last 4 OIDs in item 202 of POST command 200, and status information "success". Item 214 includes the same OID as the last 5 OID in item 204 of POST command 200, and status information "success".

When the terminal device 100 receives the response command 210 from the printer 10 at T44, it displays a message indicating that the write process has been appropriately completed (not shown). This allows the user to know that the write process has been properly completed.

As shown in the case of FIG. 5, the printer 10 converts the MIB value "C3,8D C3,93" written in UTF to the MIB value "CD D3" written in non-UTF, The MIB value "CD D3" is written in the management table 38 in association with the OID "4" (T40). Therefore, the printer 10 can appropriately execute the write process in response to the POST command according to HTTPS, taking into account the character code.

(GET command case: Figure 7)
The terminal device 100 receives an acquisition operation from the user at T50. The acquisition operation includes an operation of specifying each of the three pieces of information to be acquired: "remaining amount of consumables,""name," and "IP address." In this case, the terminal device 100 transmits an HTTPS command to the printer 10 at T52. T52 to T80 are similar to T12 to T30 in FIG.

After the terminal device 100 exchanges the encryption key with the printer 10 at T80, the terminal device 100 transmits a GET command 220 corresponding to the acquisition operation at T50 to the printer 10 at T82. The terminal device 100 can identify the second OID at the end from the information “remaining amount of consumables” specified in the acquisition operation of T50, and write that information in the GET command 220. Similarly, the terminal device 100 specifies the OID with the last 4 and the OID with the last 5 from the information "name" and "IP address" specified in the acquisition operation of T50, respectively, and sends these information using the GET command 220. can be written to.

As shown in FIG. 8, the GET command 220 is written in JSON format and includes a header part and a body part. The body portion includes three items 222, 224, 226. Item 222 includes the last OID 2 corresponding to the information "remaining amount of consumables". Item 224 includes the last 4 OIDs corresponding to the information "name". Item 226 includes the last 5 OIDs corresponding to the information "IP address".

When the printer 10 receives the GET command 220 from the terminal device 100 at T82 (YES at S20, GET at S22), it processes each of the three items 222, 224, and 226 in order.

The printer 10 reads the type "integer" and the MIB value "38 30" associated with the last OID 2 from the management table 38 for the item 222 (S202 in FIG. 4). The printer 10 determines that the type is integer (NO in S210). Therefore, the printer 10 does not convert the MIB value "38 30" written in UTF. At T90, the printer 10 writes the last OID 2, the type "integer", and the MIB value "38 30" written in UTF into the response command (S230, the item in the response command 230 in FIG. 8 232).

The printer 10 reads the type "string" and the MIB value "C7 C8 C9" associated with the last 4 OIDs from the management table 38 for the item 224 (S202). The printer 10 determines that the type is string (YES in S210). Since the last 4 OIDs are included in the determination list 40, the printer 10 determines that the MIB value is to be converted (YES in S212). The printer 10 determines that the language setting 42 is Portuguese (NO in S214), and specifies a non-UTF (ie, ISO8859-1) corresponding to Portuguese from the language table 44 (S220). At T92, the printer 10 converts the MIB values "C7 C8 C9" described in ISO8859-1 to the MIB values "C3,87 C3,88 C3,89" described in UTF (S222). Then, the printer 10 writes the last 4 OID, the type "string", and the MIB value "C3,87 C3,88 C3,89" written in UTF into the response command (S230, shown in FIG. 8). (See item 234 in response command 230).

The printer 10 reads the type "string" and the MIB value "31 39 32..." associated with the last OID 5 from the management table 38 for the item 226 (S202). The printer 10 determines that the type is string (YES in S210). Since the last 5 OIDs are not included in the determination list 40, the printer 10 determines that the MIB value is not a conversion target (NO in S212). Therefore, the printer 10 does not convert the MIB values "31 39 32..." written in UTF. In T94, the printer 10 writes the OID ending in 5, the type "string", and the MIB value "31 39 32..." written in UTF to the response command (S230, the response command in FIG. 8 (See item 236 within 230).

When the printer 10 executes the processing on the three items 222, 224, and 226 (NO at S240), it transmits the response command 230 to the terminal device 100 at T96 (S250). As shown in FIG. 8, the response command 230 is written in JSON format and includes a header section and a body section. The body portion includes three items 232, 234, 236.

Upon receiving the response command 230 from the printer 10 at T96, the terminal device 100 displays information in the response command 230 (not shown). Specifically, the terminal device 100 inputs the character string “remaining amount of consumables” specified from the last 2 OID in the item 232 and the character string “80” specified from the MIB value “38 30” in the item 232. ” and are displayed in association with each other. Similarly, the terminal device 100 displays the character string "Name" in association with the character string specified from the MIB value "C3,87 C3,88 C3,89", and also displays the character string "IP address". and the character string "192..." specified from the MIB values "31 39 32..." are displayed in association with each other. This allows the user to know each setting value within the printer 10.

As shown in the case of FIG. 7, the printer 10 converts the MIB value "C7 C8 C9" written in non-UTF to the MIB value "C3,87 C3,88 C3,89" written in UTF. Then, a response command 230 including the converted MIB value is transmitted to the terminal device 100 (T96). Therefore, the printer 10 can appropriately execute response processing in response to an HTTPS GET command, taking into account the character code.

(correspondence)
The management table 38 is an example of "management information". A POST command and a GET command are examples of a "setting command" and an "obtaining command", respectively. The judgment list 40 is an example of "specific information". Japanese, Chinese, and Korean are examples of "predetermined language settings." The type "string" and the type "integer" are examples of the "first data type" and "second data type", respectively. The OID in item 202 and the OID in item 204 of the POST command 200 in FIG. 6 are examples of the "first OID." The MIB value in item 202 and the converted MIB value are examples of a "first value" and a "second value," respectively. The OID in item 224 and the OID in item 226 of the GET command 220 in FIG. 8 are examples of the "second OID." The MIB value before conversion and the converted MIB value associated with the OID in item 224 are examples of the "third value" and the "fourth value", respectively.

S20 in FIG. 2 and T32 in FIG. 5 are examples of processing executed by the "setting command receiving section." S122 in FIG. 3 and T40 in FIG. 5 are examples of processing executed by the "first converter". S130 in FIG. 3 and T40 and T42 in FIG. 5 are examples of processing executed by the "writing unit". S20 in FIG. 3 and T82 in FIG. 7 are examples of processing executed by the "acquisition command receiving section." S202 in FIG. 4 is an example of a process executed by the "acquisition unit". S222 in FIG. 4 and T92 in FIG. 7 are examples of processing executed by the "second conversion unit." S250 in FIG. 4 and T96 in FIG. 7 are examples of processing executed by the "response command transmitter".

Although specific examples of the present invention have been described in detail above, these are merely illustrative and do not limit the scope of the claims. The techniques described in the claims include various modifications and changes to the specific examples illustrated above. Modifications of the above embodiment are listed below.

(Modification 1) The judgment list 40, S112 in FIG. 3, and S212 in FIG. 4 may be omitted. That is, "specific information" can be omitted. In addition, the "first (or second) conversion unit" converts the first value (or the third value) regardless of whether the first OID (or the second OID) is a related OID. may be converted into a second value (or a fourth value).

(Modification 2) S114 in FIG. 3 and S214 in FIG. 4 may be omitted. In this case, in S220, for Japanese, Shift-JIS, for example, may be specified. Furthermore, for Chinese, for example, GB2312-1980 may be specified. That is, the "first (or second) conversion unit" converts the first value (or third value) into the second value, regardless of whether the language setting of the communication device is the predetermined language setting or not. value (or a fourth value).

(Variation 3) For example, if the printer 10 supports only English (that is, the printer 10 in which the user cannot specify the language setting 42), the language table 44 is not necessary. In this example, the code table 46 only needs to have ISO8859-1 character codes and UTF character codes. That is, the "first (or second) conversion unit" does not need to specify the non-UTF character code corresponding to the language setting.

(Modification 4) S110 in FIG. 3 and S210 in FIG. 4 may be omitted. In other words, the "first (or second) conversion unit" converts the first value (or third value) into the second value (or fourth value) regardless of the type information. good.

(Modification 5) UTF is not limited to UTF-8, and may be UTF-16, UTF-32, or the like. Non-UTF is not limited to ISO8859-based character codes, but may also be Shift-JIS, GB2312-1980, or the like.

(Variation 6) The "communication device" is not limited to a printer, but may be another device such as a scanner, facsimile, PC, or server.

(Modification 7) In the above embodiment, the CPU 32 executes the program 36 to realize the processes shown in FIGS. 2 to 5 and 7. Alternatively, any of the processes may be realized by hardware such as a logic circuit.

Further, the technical elements described in this specification or the drawings exhibit technical usefulness singly or in various combinations, and are not limited to the combinations described in the claims as filed. Furthermore, the techniques illustrated in this specification or the drawings simultaneously achieve multiple objectives, and achieving one of the objectives has technical utility in itself.

Even if each claim is dependent on only some of the claims in the scope of claims as of the filing of this patent application, each claim can be dependent on only some of the claims. Not limited. To the extent not technically inconsistent, each claim may be dependent on other claims to which it was not dependent as filed. That is, the techniques of each claim can be combined in various ways as follows.
(Item 1)
A communication device,
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
A configuration command receiving unit that receives a configuration command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the configuration command being a first and a first value written in UTF (Unicode Transformation Format);
a first conversion unit that converts the first value included in the configuration command into a second value written in non-UTF when the configuration command is received from the terminal device;
a writing unit that writes the converted second value in the management information in association with the first OID included in the setting command;
A communication device comprising:
(Item 2)
The memory further stores specific information for specifying a related OID that is an OID associated with a setting value to be converted,
When the first OID included in the setting command is identified as the related OID based on the specific information,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
When the first OID included in the setting command is identified as not the related OID based on the specific information,
The first conversion unit does not convert the first value to the second value,
The communication device according to item 1, wherein the writing unit writes the first value into the management information in association with the first OID.
(Item 3)
If the language setting of the communication device is not a predetermined language setting,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
when the language setting of the communication device is the predetermined language setting,
The first conversion unit does not convert the first value to the second value,
The communication device according to item 1 or 2, wherein the writing unit writes the first value into the management information in association with the first OID.
(Item 4)
The first conversion unit specifies the non-UTF character code corresponding to the language setting of the communication device, and converts the first value into the second value written in the specified character code. The communication device according to any one of items 1 to 3.
(Item 5)
The setting command further includes type information indicating a data type of the first value,
When the type information included in the configuration command indicates a first data type,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
When the type information included in the configuration command indicates a second data type different from the first data type,
The first conversion unit does not convert the first value to the second value,
The communication device according to any one of items 1 to 4, wherein the writing unit writes the first value to the management information in association with the first OID.
(Item 6)
The communication device further includes:
an acquisition command receiving unit that receives an acquisition command according to the TCP from the terminal device, the acquisition command including a second OID;
When the acquisition command is received from the terminal device, a third value associated with the second OID included in the acquisition command is determined from the management information in the memory, the non-UTF an acquisition unit that acquires the third value described by;
a second conversion unit that converts the acquired third value into a fourth value written in UTF;
a response command transmitter that transmits a response command including the converted fourth value to the terminal device;
The communication device according to any one of items 1 to 5, comprising:
(Item 7)
A communication device,
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
An acquisition command receiving unit that receives an acquisition command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the acquisition command being a second The acquisition command receiving unit includes an OID of
When the acquisition command is received from the terminal device, a third value associated with the second OID included in the acquisition command is determined from the management information in the memory, and is a non-UTF ( an acquisition unit that acquires the third value described in Unicode Transformation Format (abbreviation for Unicode Transformation Format);
a second conversion unit that converts the acquired third value into a fourth value written in UTF;
a response command transmitter that transmits a response command including the converted fourth value to the terminal device;
A communication device comprising:
(Item 8)
The memory further stores specific information for specifying a related OID that is an OID associated with a setting value to be converted,
When the second OID included in the acquisition command is identified as the related OID based on the specific information,
The second conversion unit converts the third value into the fourth value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
When the second OID included in the acquisition command is identified as not the related OID based on the specific information,
The second conversion unit does not convert the third value to the fourth value,
The communication device according to item 7, wherein the response command transmitting unit transmits the response command including the third value to the terminal device.
(Item 9)
If the language setting of the communication device is not a predetermined language setting,
The second conversion unit converts the first value into the second value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
when the language setting of the communication device is the predetermined language setting,
The second conversion unit does not convert the third value to the fourth value,
9. The communication device according to item 7 or 8, wherein the response command transmitting unit transmits the response command including the third value to the terminal device.
(Item 10)
The second conversion unit specifies the non-UTF character code corresponding to the language setting of the communication device, and converts the third value written in the specified character code to the fourth value. The communication device according to any one of items 7 to 9.
(Item 11)
when the data type of the third value associated with the second OID included in the acquisition command is the first data type;
The second conversion unit converts the third value into the fourth value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
when the data type of the third value associated with the second OID included in the acquisition command is a second data type different from the first data type;
The second conversion unit does not convert the third value to the fourth value,
The communication device according to any one of items 7 to 10, wherein the response command transmitting unit transmits the response command including the third value to the terminal device.
(Item 12)
The UTF is UTF-8,
The communication device according to any one of items 1 to 11, wherein the non-UTF is an ISO8859-based character code.

2: Communication system, 6: LAN, 10: Printer, 12: Operation unit, 14: Display unit, 16: LAN interface, 18: Print execution unit, 30: Control unit, 32: CPU, 34A: Non-volatile memory, 34B : volatile memory, 36: program, 38: management table, 40: judgment list, 42: language setting, 44: language table, 46: code table, 100: terminal device

Claims (14)

A communication device,
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
A configuration command receiving unit that receives a configuration command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the configuration command being a first and a first value written in UTF (Unicode Transformation Format);
a first conversion unit that converts the first value included in the configuration command into a second value written in non-UTF when the configuration command is received from the terminal device;
a writing unit that writes the converted second value in the management information in association with the first OID included in the setting command;
A communication device comprising: The memory further stores specific information for specifying a related OID that is an OID associated with a setting value to be converted,
When the first OID included in the setting command is identified as the related OID based on the specific information,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
When the first OID included in the setting command is identified as not the related OID based on the specific information,
The first conversion unit does not convert the first value to the second value,
The communication device according to claim 1, wherein the writing unit writes the first value into the management information in association with the first OID. If the language setting of the communication device is not a predetermined language setting,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
when the language setting of the communication device is the predetermined language setting,
The first conversion unit does not convert the first value to the second value,
The communication device according to claim 1, wherein the writing unit writes the first value into the management information in association with the first OID. The first conversion unit specifies the non-UTF character code corresponding to the language setting of the communication device, and converts the first value into the second value written in the specified character code. The communication device according to claim 1. The setting command further includes type information indicating a data type of the first value,
When the type information included in the configuration command indicates a first data type,
The first conversion unit converts the first value into the second value,
The writing unit writes the second value in the management information in association with the first OID,
When the type information included in the configuration command indicates a second data type different from the first data type,
The first conversion unit does not convert the first value to the second value,
The communication device according to claim 1, wherein the writing unit writes the first value into the management information in association with the first OID. The communication device further includes:
an acquisition command receiving unit that receives an acquisition command according to the TCP from the terminal device, the acquisition command including a second OID;
When the acquisition command is received from the terminal device, a third value associated with the second OID included in the acquisition command is determined from the management information in the memory, the non-UTF an acquisition unit that acquires the third value described by;
a second conversion unit that converts the acquired third value into a fourth value written in UTF;
a response command transmitter that transmits a response command including the converted fourth value to the terminal device;
The communication device according to claim 1, comprising: A communication device,
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
An acquisition command receiving unit that receives an acquisition command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the acquisition command being a second The acquisition command receiving unit includes an OID of
When the acquisition command is received from the terminal device, a third value associated with the second OID included in the acquisition command is determined from the management information in the memory, and is a non-UTF ( an acquisition unit that acquires the third value described in Unicode Transformation Format (abbreviation for Unicode Transformation Format);
a second conversion unit that converts the acquired third value into a fourth value written in UTF;
a response command transmitter that transmits a response command including the converted fourth value to the terminal device;
A communication device comprising: The memory further stores specific information for specifying a related OID that is an OID associated with a setting value to be converted,
When the second OID included in the acquisition command is identified as the related OID based on the specific information,
The second conversion unit converts the third value into the fourth value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
When the second OID included in the acquisition command is identified as not the related OID based on the specific information,
The second conversion unit does not convert the third value to the fourth value,
The communication device according to claim 7, wherein the response command transmitter transmits the response command including the third value to the terminal device. If the language setting of the communication device is not a predetermined language setting,
The second conversion unit converts the third value into the fourth value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
when the language setting of the communication device is the predetermined language setting,
The second conversion unit does not convert the third value to the fourth value,
The communication device according to claim 7, wherein the response command transmitter transmits the response command including the third value to the terminal device. The second conversion unit specifies the non-UTF character code corresponding to the language setting of the communication device, and converts the third value written in the specified character code to the fourth value. The communication device according to claim 7. when the data type of the third value associated with the second OID included in the acquisition command is the first data type;
The second conversion unit converts the third value into the fourth value,
The response command transmitting unit transmits the response command including the fourth value to the terminal device,
when the data type of the third value associated with the second OID included in the acquisition command is a second data type different from the first data type;
The second conversion unit does not convert the third value to the fourth value,
The communication device according to claim 7, wherein the response command transmitter transmits the response command including the third value to the terminal device. The UTF is UTF-8,
12. The communication device according to claim 1, wherein the non-UTF is an ISO8859-based character code. A computer program for a communication device, the computer program comprising:
The communication device includes:
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
comprising a computer;
The computer program causes the computer to run the following parts:
A configuration command receiving unit that receives a configuration command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the configuration command being a first and a first value written in UTF (Unicode Transformation Format);
a first conversion unit that converts the first value included in the configuration command into a second value written in non-UTF when the configuration command is received from the terminal device;
a writing unit that writes the converted second value in the management information in association with the first OID included in the setting command;
A computer program that functions as A computer program for a communication device, the computer program comprising:
The communication device includes:
a memory that stores management information in which the OID and setting value are associated with each of a plurality of OIDs (abbreviation of Object ID) of MIB (abbreviation of Management Information Base);
comprising a computer;
The computer program causes the computer to run the following parts:
An acquisition command receiving unit that receives an acquisition command according to TCP (Transmission Control Protocol) of a transport layer of an OSI (Open Systems Interconnection) reference model from a terminal device, the acquisition command being a second The acquisition command receiving unit includes an OID of
When the acquisition command is received from the terminal device, a third value associated with the second OID included in the acquisition command is determined from the management information in the memory, and is a non-UTF ( an acquisition unit that acquires the third value described in Unicode Transformation Format (abbreviation for Unicode Transformation Format);
a second conversion unit that converts the acquired third value into a fourth value written in UTF;
a response command transmitter that transmits a response command including the converted fourth value to the terminal device;
A computer program that functions as

Images