Embedded machine and display system
By setting up a web server in an embedded machine and using a virtual server to distinguish communication types, the communication load and security differences between the built-in browser and external browser are solved, and more efficient processing and security management are achieved.
Patent Information
- Application Number
- CN202280094328.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-11
- Publication Date
- 2024-11-12
AI Technical Summary
When the built-in browser and external browser of existing embedded machines display the same web documents, there are differences in communication load and security, resulting in unbalanced processing load and it is difficult to effectively reduce the communication load between built-in browsers.
By setting up a web server in an embedded machine, the stored web documents are sent to the built-in browser in an unencrypted manner and sent to the external browser in an encrypted manner. The virtual server distinguishes communication types and realizes that different browsers are used to realize the communication types between different browsers. security differences.
It effectively reduces the communication processing load between built-in browsers, improves the performance of embedded machines, and switches user authentication methods based on the connection source, improving operability and security.
Smart Images

Figure CN118947086A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to an embedded machine and a display system. Background Art
[0002] An embedded device equipped with a display unit for displaying a screen is known. In addition, as the embedded device is network-enabled, the embedded device can also be controlled from an external terminal. For example, Patent Document 1 discloses an image processing device that can display different operation screens when accessed via a built-in Web browser and when accessed from a Web browser of an external device.
[0003] Prior art literature
[0004] Patent Document 1: Japanese Patent Application Publication No. 2011-197968 Summary of the invention
[0005] In a system that displays screens in both a built-in browser of an embedded device and an external browser installed in an external terminal, it is required to reduce the man-hours required for screen development by generating screens displayed in the built-in browser and the external browser based on the same Web document.
[0006] On the other hand, there is a difference in the required security between the built-in browser and the external browser. Specifically, when displaying a screen in an external browser, since communication is performed via an external network, enhanced security countermeasures are required. In contrast, when displaying a screen in a built-in browser of an embedded machine, since it becomes internal communication of the embedded machine, enhanced security countermeasures are not required compared to communication with an external browser. It is required to take into account such a difference in required security to reduce the processing load in communication with the built-in browser.
[0007] The present disclosure is made to solve the above-mentioned problems, and its purpose is to provide an embedded machine etc. that can reduce the processing load in communication with a built-in browser in an embedded machine that displays a screen based on the same Web document on the built-in browser and an external browser.
[0008] In order to achieve the above-mentioned object, the embedded machine involved in the present disclosure is an embedded machine that is communicatively connected to an external terminal having an external browser, and has:
[0009] Storage department, storing Web documents;
[0010] Built-in browser; and
[0011] The web server sends the web document stored in the storage unit to the built-in browser via unencrypted communication, so that a first screen based on the web document is displayed on the built-in browser, and sends the web document stored in the storage unit to the external browser via encrypted communication, so that a second screen based on the web document is displayed on the external browser.
[0012] In the present disclosure, the Web server sends the Web document stored in the storage unit to the built-in browser via unencrypted communication, so that a first screen based on the Web document is displayed on the built-in browser, and sends the Web document stored in the storage unit to the external browser via encrypted communication, so that a second screen based on the Web document is displayed on the external browser. Therefore, according to the present disclosure, in an embedded machine that displays screens based on the same Web document on the built-in browser and the external browser, the processing load in the communication with the built-in browser can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1 FIG. 1 is a first diagram showing a configuration of a display system according to Embodiment 1. FIG.
[0014] Figure 2 FIG. 2 is a second diagram showing the configuration of the display system according to the first embodiment.
[0015] Figure 3 This is a diagram showing the configuration of a Web server according to the first embodiment.
[0016] Figure 4 This is a diagram showing an example of a user authentication input screen displayed by the external browser according to the first embodiment.
[0017] Figure 5 This is a diagram showing an example of a user authentication completion screen displayed by the built-in browser and the external browser according to the first embodiment.
[0018] Figure 6 This is a diagram showing an example of an operation screen displayed by the built-in browser and the external browser according to the first embodiment.
[0019] Figure 7 This is a flowchart showing the flow of user authentication processing executed by the embedded device according to the first embodiment.
[0020] Figure 8 This is a flowchart showing the flow of operation screen display processing executed by the embedded device according to the first embodiment.
[0021] Fig. 9This is a diagram showing a configuration related to user authentication of an authentication device in an embedded device according to the second embodiment.
[0022] Fig.10 This is a diagram showing an example of a screen displayed by the built-in browser according to the second embodiment, urging the user to operate the authentication device.
[0023] Fig.11 This is a diagram showing a system configuration of a virtual machine in an embedded machine according to the third embodiment.
[0024] Fig.12 This is a diagram showing a system configuration based on container virtualization in an embedded device according to a fourth embodiment. DETAILED DESCRIPTION
[0025] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. In addition, the same reference numerals are given to the same or corresponding parts in the drawings.
[0026] (Implementation Method 1)
[0027] Figure 1 The configuration of a display system 1 according to Embodiment 1 is shown. The display system 1 includes an embedded device 10 and an external terminal 30. The embedded device 10 is equipped with a screen display function, and a user can operate the embedded device 10 by directly touching the embedded device 10 while viewing the screen.
[0028] The embedded machine 10 and the external terminal 30 are connected to each other in a communicative manner via an external network shown by a dotted line. The external network is a communication network, specifically, an information communication network such as a LAN (Local Area Network) or the Internet. By using the external network, the user can operate the embedded machine 10 from the browser of the external terminal 30 without directly contacting the embedded machine 10.
[0029] The embedded device 10 is an electronic device controlled by embedded software, specifically, an electronic device for a specific purpose such as an air conditioner, a water heater, an automatic rice cooker, a washing machine, a refrigerator, a television, etc. Hereinafter, as the embedded device 10, an air conditioner controller for operating an air conditioner is described as an example.
[0030] The embedded device 10 includes a control unit 11, a storage unit 12, an operation unit 13, a display unit 14, and a communication unit 15. These may be respectively referred to as a device-side control unit, a device-side storage unit, a device-side operation unit, a device-side display unit, and a device-side communication unit.
[0031] The control unit 11 includes a CPU (Central Processing Unit). The CPU is also called a central processing unit, a central computing unit, a processor, a microprocessor, a microcomputer, etc., and functions as a processing unit that performs processing and calculations related to the control of the embedded machine 10. In the control unit 11, the CPU reads out the program and data stored in the storage unit 12 and performs operations to control the embedded machine 10 as a whole.
[0032] The storage unit 12 includes a ROM (Read Only Memory), a RAM (Random Access Memory), a flash memory, etc. The storage unit 12 stores programs and data used for various processes performed by the control unit 11. In addition, the storage unit 12 stores data generated or acquired by the control unit 11 performing various processes.
[0033] Specifically, the storage unit 12 stores a Web document 121. The Web document 121 is a data file that determines an image displayed on the display unit 14. In the Web document 121, data of a screen displayed on the display unit 14, such as a user authentication screen and an operation screen of the embedded device 10, is determined according to a predetermined rule. For example, the Web document 121 includes HTML (Hyper Text Markup Language) or CSS (Cascading Style Sheets) that specifies the screen layout, and JavaScript that describes the content of the screen.
[0034] The operation unit 13 includes input devices such as a touch panel, a touch pad, a keyboard, a mouse, and physical buttons, and accepts operation input from the user. The user can input various instructions to the embedded device 10 by operating the operation unit 13. When the operation unit 13 accepts the instruction input by the user, it outputs the accepted instruction to the built-in browser 111.
[0035] The display unit 14 includes a display device such as a liquid crystal panel, an organic EL (Electro-Luminescence) panel, etc. The display unit 14 is driven by a display driving circuit and displays various images output from the built-in browser 111 .
[0036] The communication unit 15 includes a communication interface for communicating with a device external to the embedded device 10. For example, the communication unit 15 communicates with the external device including the external terminal 30 in accordance with a known communication standard such as LAN or USB (Universal Serial Bus).
[0037] Specifically, the communication unit 15 performs encrypted communication with the external terminal 30 via the external network. In response to a request from the external terminal 30, the communication unit 15 transmits the web document 121 stored in the storage unit 12 to the external terminal 30.
[0038] The external terminal 30 is a terminal device outside the embedded machine 10, and functions as a Web client. Specifically, the external terminal 30 is an operation terminal operated by a user, such as a personal computer, a smart phone, a tablet terminal, etc. The external terminal 30 is connected to the embedded machine 10 via an external network, and can operate the embedded machine 10, monitor the status, etc.
[0039] The external terminal 30 includes a control unit 31, a storage unit 32, an operation unit 33, a display unit 34, and a communication unit 35. These may be respectively referred to as a terminal-side control unit, a terminal-side storage unit, a terminal-side operation unit, a terminal-side display unit, and a terminal-side communication unit.
[0040] The control unit 31 includes a CPU. The CPU is also called a central processing unit, a central computing unit, a processor, a microprocessor, a microcomputer, etc., and functions as a processing unit that performs processing and calculations related to the control of the external terminal 30. In the control unit 31, the CPU reads out programs and data stored in the storage unit 32 and operates, thereby controlling the external terminal 30 as a whole.
[0041] The storage unit 32 includes a ROM, a RAM, a flash memory, etc. The storage unit 32 stores programs and data used for the control unit 31 to perform various processes. In addition, the storage unit 32 stores data generated or acquired by the control unit 31 performing various processes.
[0042] The operation unit 33 includes input devices such as buttons, a touch pad, and a touch panel, and receives operation input from the user. The user can input various instructions to the external terminal 30 by operating the operation unit 33. When receiving an instruction input by the user, the operation unit 33 outputs the received instruction to the external browser 311.
[0043] The display unit 34 includes a display device such as an LCD panel or an organic EL panel. The display unit 34 is driven by a display driving circuit and displays various images output from the external browser 311 .
[0044] The communication unit 35 includes a communication interface for communicating with an external device of the external terminal 30. For example, the communication unit 35 communicates with the external device including the embedded device 10 in accordance with a known communication standard such as LAN or USB.
[0045] Specifically, the communication unit 35 performs encrypted communication with the embedded device 10 via the external network. Thus, the communication unit 35 acquires the Web document 121 transmitted from the embedded device 10.
[0046] In the embedded device 10, the control unit 11 functionally includes a built-in browser 111, a web server 112, and an application server 113. In the external terminal 30, the control unit 31 functionally includes an external browser 311.
[0047] These components are implemented by software, firmware, or a combination of software and firmware. Software and firmware are described as programs and stored in ROM or storage unit 12, 32. The functions of each component are implemented by the CPU executing the program stored in ROM or storage unit 12, 32.
[0048] Next, refer to Figure 2 , describing the functions of each component included in the control units 11 and 31.
[0049] In the embedded device 10, the built-in browser 111 is a Web browser built into the embedded device 10, and displays a display screen on the display unit 14. The built-in browser 111 also obtains an operation instruction input by the user of the embedded device 10 by operating the operation unit 13 from the operation unit 13.
[0050] The built-in browser 111 can be connected to the Web server 112 via internal communication of the embedded machine 10. The built-in browser 111 obtains the Web document 121 stored in the storage unit 12 from the Web server 112 via internal communication, and outputs a display screen based on the Web document 121 to the display unit 14. In addition, the built-in browser 111 sends the user's operation instruction obtained from the operation unit 13 to the Web server 112 via internal communication.
[0051] More specifically, the built-in browser 111 is connected to the Web server 112 via loopback communication as internal communication. In loopback communication, the source browser and the destination server are both addressed as "127.0.0.1" in the case of IPv4 (Internet Protocol version 4), and as "::1" in the case of IPv6 (Internet Protocol version 6). By assigning such addresses, loopback communication can be distinguished from communication from an external network.
[0052] In the external terminal 30, the external browser 311 is a web browser installed in the external terminal 30, and displays a display screen on the display unit 34. In addition, the external browser 311 obtains an operation instruction input by the user of the external terminal 30 by operating the operation unit 33 from the operation unit 33.
[0053] The external browser 311 can be connected to the Web server 112 of the embedded machine 10 via an external network. The external browser 311 obtains the Web document 121 stored in the storage unit 12 from the Web server 112 via the external network, and outputs a display screen based on the Web document 121 to the display unit 34. In addition, the external browser 311 sends the user's operation instruction obtained from the operation unit 33 to the Web server 112 via the external network.
[0054] In the embedded machine 10, the web server 112 has a function of causing the built-in browser 111 and the external browser 311, which are web browsers, to execute screen display. In addition, the web server 112 also has a reverse proxy function that relays communications accessed from the built-in browser 111 and the external browser 311. The web server 112 is constructed, for example, by Nginx (registered trademark in Japan).
[0055] The web server 112 distributes the web document 121 to the built-in browser 111 and the external browser 311, and displays a display screen based on the web document 121 on the display units 14 and 34. Specifically, the web server 112 distributes the web document 121 stored in the storage unit 12 to both the built-in browser 111 and the external browser 311. In this way, since the common web document 121 is distributed to both the built-in browser 111 and the external browser 311, and the display screen is displayed based on the distributed web document 121, the development cost of the web document 121 can be reduced.
[0056] In this way, when the Web screen is made common in the built-in browser 111 and the external browser 311, the same security measures are not necessarily required in the display processing in the built-in browser 111 and the display processing in the external browser 311. Specifically, when the external terminal 30 is connected to the embedded machine 10 via an external network, security measures must be taken to prevent unauthorized access to the embedded machine 10.
[0057] Specifically, the security measures include (1) encryption of communication between the external terminal 30 and the embedded machine 10, (2) user authentication, and (3) authentication of the WebAPI (Application Programming Interface) for operating the embedded machine 10 via an external network. In the first embodiment, different security measures are implemented in the display processing in the built-in browser 111 and the display processing in the external browser 311 for these (1) to (3), respectively.
[0058] (1) Communication encryption
[0059] First, the encryption of communication is described. The communication between the built-in browser 111 and the Web server 112 is a loopback communication, and the communication content will not be leaked to the outside, so there is no need to encrypt the communication. In addition, the CPU installed in the embedded machine 10 has lower performance than the CPU of a general personal computer, so when performing unnecessary encrypted communication, the CPU load becomes a problem.
[0060] Therefore, the Web server 112 performs unencrypted communication with the built-in browser 111, and performs encrypted communication with the external browser 311. Here, an example of unencrypted communication is HTTP (Hypertext Transfer Protocol) communication, and an example of encrypted communication is HTTPS (Hypertext Transfer Protocol Secure) communication.
[0061] In order to realize the function of changing the presence or absence of encryption according to the connection destination, the Web server 112 has a function called a virtual server. A virtual server is a technology that can achieve the same effect as when operating multiple servers by operating only one software.
[0062] Specifically, Figure 3 As shown, the web server 112 has the functions of an internal virtual server 141 and an external virtual server 142. The web server 112 performs unencrypted communication with the built-in browser 111 using the internal virtual server 141 and performs encrypted communication with the external browser 311 using the external virtual server 142.
[0063] When receiving communication from the built-in browser 111 or the external browser 311, the web server 112 determines whether the connection destination of the communication is the built-in browser 111 or the external browser 311. As described above, the built-in browser 111 communicates with the web server 112 through loopback communication, and the external browser 311 communicates with the web server 112 through the external network.
[0064] Therefore, when the address of the connection destination matches the loopback address, the web server 112 determines that the connection is accepted from the built-in browser 111, and when the address of the connection destination matches an address other than the loopback address, the web server 112 determines that the connection is accepted from the external browser 311. The loopback address is "127.0.0.1" in the case of IPv4 and "::1" in the case of IPv6.
[0065] When it is determined that the connection is accepted from the built-in browser 111, the internal virtual server 141 accepts the connection. On the other hand, when it is determined that the connection is accepted from the external browser 311, the external virtual server 142 accepts the connection. In the internal virtual server 141, only HTTP communication, which is unencrypted communication, is enabled, and in the external virtual server 142, only HTTPS communication, which is encrypted communication, is enabled.
[0066] Thus, when the screen operation is performed from the built-in browser 111, unencrypted communication is performed, so the CPU load of the embedded machine 10 is reduced. On the other hand, for example, when a connection is made from an external network through HTTP communication, since the address of the connection destination is not a loopback address, the connection is not made to the internal virtual server 141. On the other hand, since the external virtual server 142 does not support HTTP communication, the connection is not made to the external virtual server 142 either. Therefore, unencrypted communication is rejected to the external network, so the security of the machine is ensured.
[0067] The web server 112 sends the web document 121 stored in the storage unit 12 to the built-in browser 111 via unencrypted HTTP communication, so that the first screen based on the web document 121 is displayed on the built-in browser 111. On the other hand, the web server 112 sends the web document 121 stored in the storage unit 12 to the external browser 311 via encrypted HTTPS communication, so that the second screen based on the web document 121 is displayed on the external browser 311.
[0068] Here, the first screen and the second screen are user authentication screens described later or operation screens of the embedded device 10. The first screen and the second screen are generated based on the same Web document 121, so they are the same except for the difference caused by the display settings determined separately in the embedded device 10 and the external terminal 30. The display settings are, for example, the frame rate of the animation included in the screen, the frequency of throttling of events when the screen is enlarged, reduced or scrolled, etc., and are determined based on cookies.
[0069] (2) User Authentication
[0070] Second, user authentication is described. User authentication is a process executed at the timing when the user starts using the embedded device 10 in order to identify the proper user.
[0071] When the embedded machine 10 is operated from the external terminal 30 via the external network, enhanced user authentication needs to be implemented as a security measure. On the other hand, there is a case where security measures are implemented at the place where the embedded machine 10 is installed. In this case, user authentication is not required when the user directly contacts the embedded machine 10 to operate.
[0072] Thus, when the user operates the embedded machine 10 by direct contact, and when the user operates the embedded machine 10 via an external network, the requested user authentication is different. Therefore, the display system 1 generates the user authentication screens in both cases using the same Web document 121, and switches the user authentication according to the Web browser of the connection source.
[0073] First, when receiving a user authentication request from the external browser 311 via HTTPS communication, the Web server 112 displays the user authentication input screen as the second screen on the external browser 311. Specifically, when the user of the external terminal 30 operates the operation unit 33 to use the embedded machine 10, the external browser 311 sends the HTML document of the user authentication request to the embedded machine 10 via HTTPS communication. The user authentication request is a request for accessing the URL (Uniform Resource Locator) of the user authentication input screen in the Web document 121.
[0074] When a user authentication request is sent from the external browser 311, the Web server 112 receives the user authentication request using the external virtual server 142. The user authentication request is encrypted through HTTPS communication, so the external virtual server 142 decrypts the received request. Then, the external virtual server 142 sends the Web document 121 for generating the input screen for user authentication as a response to the request back to the external browser 311 through HTTPS communication.
[0075] Here, the web document 121 stored in the storage unit 12 includes a description for generating a user authentication screen. The user authentication screen includes an input screen for user authentication and a completion screen for user authentication.
[0076] When the Web document 121 is sent back, the external browser 311 analyzes the sent back Web document 121 to generate a screen and displays it on the display unit 34. The external browser 311 displays, for example, Figure 4 The user authentication input screen shown is displayed on the display unit 34. The user of the external terminal 30 operates the operation unit 33 on the user authentication input screen to input a user name and a password, thereby performing user authentication.
[0077] The external browser 311 sends the input user name and password to the Web server 112 via HTTPS communication. The external virtual server 142 determines whether the user authentication is successful or failed based on whether the user name and password sent from the external browser 311 are appropriate. Then, the external virtual server 142 sends back the Web document 121 for generating the completion screen of the user authentication to the external browser 311 via HTTPS communication.
[0078] When user authentication succeeds due to the operation accepted by the operation unit 33, the external browser 311 displays, for example, Figure 5 The screen indicating successful user authentication as shown is displayed on the display unit 34. On the other hand, when user authentication fails due to the operation accepted by the operation unit 33, the external browser 311 displays a screen indicating failed user authentication on the display unit 34 as a user authentication completion screen, although not shown.
[0079] On the other hand, when receiving a user authentication request from the built-in browser 111 via HTTP communication, the Web server 112 does not display the user authentication input screen on the built-in browser 111, but displays the user authentication completion screen as the first screen on the built-in browser 111. Specifically, when the user of the embedded machine 10 operates the operation unit 13 to use the embedded machine 10, the built-in browser 111 sends an HTML document of the user authentication request to the embedded machine 10 via HTTP communication. The user authentication request is a request for accessing the URL of the user authentication input screen in the Web document 121.
[0080] When a user authentication request is sent from the built-in browser 111, the Web server 112 receives the user authentication request using the internal virtual server 141. At this time, the user authentication request is not encrypted, so the internal virtual server 141 does not decrypt the received request.
[0081] It is assumed that when a user authentication request is received from the built-in browser 111, high security is ensured when the user operates from the built-in browser 111. Therefore, the internal virtual server 141 skips the process of displaying the input screen of the user authentication and displays the completion screen of the user authentication on the built-in browser 111.
[0082] Specifically, when receiving a user authentication request from the built-in browser 111, the internal virtual server 141 changes the connection destination of the request from the user authentication input screen to the user authentication completion screen by redirection or URL rewriting. Here, redirection means a mechanism of transferring to a different URL when accessing a specific URL.
[0083] In the case of redirection, the internal virtual server 141 forwards the request received with the URL of the user authentication input screen as the connection destination to the URL of the user authentication completion screen. Alternatively, in the case of URL rewriting, the internal virtual server 141 changes the URL of the connection destination of the received request from the URL of the user authentication input screen to the URL of the user authentication completion screen.
[0084] By such redirection or URL rewriting, the internal virtual server 141 does not display the user authentication input screen, but guides to the user authentication completion screen. As a result, the internal virtual server 141 sends the Web document 121 for generating the user authentication completion screen instead of the user authentication input screen as a response to the request to the built-in browser 111 through HTTP communication.
[0085] When the web document 121 is sent back, the built-in browser 111 analyzes the sent back web document 121 to generate a screen and displays it on the display unit 14. Specifically, the built-in browser 111 displays, for example, Figure 5 The screen indicating that the user authentication is successful as shown is displayed on the display unit 14 as a user authentication completion screen.
[0086] In this way, the Web server 112 does not execute the process of displaying the input screen for user authentication when receiving the user authentication request from the built-in browser 111. This can reduce the load of the user authentication process in the embedded device 10.
[0087] (3) WebAPI authentication
[0088] Third, the authentication of WebAPI is described. The application server 113 executes processing based on the application software installed in the embedded machine 10. The embedded machine 10 is equipped with application software prepared by the development source supplier and application software for machine operation developed by a third party other than the development source supplier. The application software calls WebAPI to operate the embedded machine 10.
[0089] WebAPI means the following mechanism: using a document in HTML format to send an operation request for operating the embedded machine 10, and after the embedded machine 10 performs an operation in accordance with the operation request, a response document of the operation result is returned. In order to prevent illegal operation of the embedded machine 10, it is necessary to prepare a mechanism for authentication of whether to accept the operation request from the external network in accordance with the Web standard.
[0090] like Figure 2 As shown, the application server 113 has the functions of an authentication control unit 131 and a Web API server 132. The authentication control unit 131 performs authentication processing for using application software. The Web API server 132 performs application processing, which is processing based on the application software.
[0091] When operating the embedded machine 10 through WebAPI, the built-in browser 111 or the external browser 311 sends an HTML document of an operation request of the embedded machine 10 to a specified URL in the embedded machine 10. Direct access to the application server 113 from the built-in browser 111 or the external browser 311 is not permitted, but is accessed via a reverse proxy.
[0092] When the web server 112 receives an HTML document of an operation request with a URL for WebAPI as a connection destination from the built-in browser 111 via HTTP communication, the web server 112 acts as an internal reverse proxy and forwards the received HTML document to the application server 113. On the other hand, when the web server 112 receives an HTML document of an operation request with a URL for WebAPI as a connection destination from the external browser 311 via HTTPS communication, the web server 112 acts as an external reverse proxy and forwards the received HTML document to the application server 113 after decryption. Since the web server 112 decrypts, the application server 113 does not need to correspond to encrypted HTTPS communication.
[0093] In the application server 113, the authentication control unit 131 performs authentication processing of the operation request before the WebAPI server 132 actually performs the WebAPI operation. The authentication processing of the authentication control unit 131 is different from the user authentication for the user to access the embedded device 10 itself, and is used to protect the WebAPI.
[0094] Specifically, the authentication control unit 131 determines whether the HTML document of the operation request contains correct authentication information. If the HTML document of the operation request does not contain correct authentication information, the authentication control unit 131 rejects the operation request and does not forward it to the WebAPI server 132.
[0095] Here, in Figure 4 When the user authentication in the user authentication screen shown is successful, the authentication information is given to the HTML document of the operation request through the Web browser. Therefore, when the user operates from the external browser 311, the correct authentication information is given to the HTML document of the operation request. On the other hand, when the user operates from the built-in browser 111, the user authentication in the user authentication screen is skipped, so the correct authentication information is not given to the HTML document of the operation request.
[0096] When an HTML document for an operation request is sent from built-in browser 111, authentication control unit 131 does not perform authentication processing but allows the HTML document for an operation request to pass through WebAPI server 132 unconditionally. This prevents authentication control unit 131 from rejecting an operation request sent from built-in browser 111.
[0097] The authentication control unit 131 determines whether the transmission source of the operation request forwarded from the Web server 112 to the application server 113 is the built-in browser 111 or the external browser 311. Here, since the operation request is forwarded from the Web server 112 functioning as a reverse proxy, the direct transmission source for the application server 113 is the reverse proxy regardless of whether the operation request is transmitted from the built-in browser 111 or the external browser 311. Therefore, the address of the transmission source viewed from the application server 113 is the loopback address in either case.
[0098] In order to enable the application server 113 to distinguish whether the source of the operation request is the built-in browser 111 or the external browser 311, Figure 3 As shown, the Web server 112 further includes functions of address assigning units 143 and 144 .
[0099] When the web server 112 receives an operation request sent from the built-in browser 111 using the internal virtual server 141, the web server 112 assigns the loopback address as the address of the sending source to the received operation request through the function of the address assigning unit 143. In addition, when the web server 112 receives an operation request sent from the external browser 311 using the external virtual server 142, the web server 112 assigns the address of the external browser 311 as the address of the sending source to the received operation request through the function of the address assigning unit 144.
[0100] More specifically, when receiving an operation request from the built-in browser 111 or the external browser 311 , the Web server 112 adds the address of the transmission source to the header or query parameter of the operation request, thereby giving the address of the transmission source to the operation request.
[0101] As the first address assignment method, the Web server 112 acting as a reverse proxy adds the address of the sending source to the header of the operation request. The header of the operation request is specifically equivalent to the header of the HTML document of the operation request, that is, the HTML header. The HTML document includes a header and a body based on the HTML specification. When the HTML document is used in the WebAPI, the operation request is recorded in the body of the HTML document.
[0102] In the HTML header, in addition to the standard header name determined by the official standard, non-standard header names can also be used. There is no standard header name for assigning the address of the sending source. However, as a de facto standard, there are many cases where the address of the sending source is assigned to HTML header names such as X-Forwarded-For or X-Real-IP. Therefore, the Web server 112 adds the address of the sending source to X-Forwarded-For or X-Real-IP.
[0103] In this case, the authentication control unit 131 determines whether X-Forwarded-For or X-Real-IP exists in the HTML header of the HTML document. If the content of X-Forwarded-For or X-Real-IP is a loopback address, the authentication control unit 131 skips the authentication process and allows the HTML document to pass through the WebAPI server 132.
[0104] Alternatively, as a second address assignment method, the Web server 112 acting as a reverse proxy may also add the address of the sending source to the query parameter of the operation request. The query parameter means information assigned to the end of the URL. When the query parameter is used, the Web server 112 adds the address of the sending source to the query parameter of the URL of the WebAPI that is the connection destination of the operation request.
[0105] In this case, the authentication control unit 131 obtains the URL of the HTML document. Furthermore, if the address of the transmission source of the query parameter of the URL is a loopback address, the authentication control unit 131 skips the authentication process and passes the HTML document through the Web API server 132 .
[0106] In addition, both the first address assignment method and the second address assignment method require rewriting based on a reverse proxy. In particular, the first address assignment method requires updating the content of the HTML document. In encrypted HTTPS communication, the content of the communication cannot be referenced or tampered with during the communication path. Therefore, before rewriting based on a reverse proxy, the operation request sent from the external browser 311 needs to be decrypted by the HTTPS server. On the other hand, as described above, the Web server 112 having the function of distributing the Web document 121 functions as an HTTPS server. Therefore, in Implementation 1, the Web server 112 and the reverse proxy are not separated as independent components, and the Web server 112 acts as a reverse proxy.
[0107] When the source address is thus assigned to the operation request, the Web server 112 transfers the operation request to the application server 113. In the application server 113, the authentication control unit 131 determines whether the source of the operation request is the built-in browser 111 or the external browser 311 based on the source address assigned to the operation request.
[0108] When it is determined that the transmission source is the external browser 311, the authentication control unit 131 performs authentication processing based on the user authentication information included in the operation request. When the authentication is successful, the authentication control unit 131 forwards the operation request to the WebAPI server 132. On the other hand, when it is determined that the transmission source is the built-in browser 111, the authentication control unit 131 does not perform authentication processing, but forwards the operation request to the WebAPI server 132 as it is.
[0109] Thus, the authentication control unit 131 uses the authenticated result in the user authentication screen when an operation request is sent from the external browser 311, and skips the authentication process when an operation request is sent from the built-in browser 111. Therefore, the user authentication of the embedded device 10 itself and the authentication of the WebAPI are not required twice, so the burden on the user can be reduced.
[0110] In particular, when WebAPI is protected by authentication, it is necessary to disclose the authentication specifications of WebAPI to the development source of APP and develop application software in accordance with the specifications. On the other hand, when application software developed by a third party is installed on the embedded machine 10, if only the recognized application software is installed on the embedded machine 10, there is no need to worry about the WebAPI being used illegally, and the embedded machine 10 will not be illegally operated. Therefore, if WebAPI can be used from application software without authentication, there is no need to disclose the authentication specifications of the embedded machine 10 to a third party, and the burden on the user of the embedded machine 10 can be reduced.
[0111] When an operation request is transferred from the authentication control unit 131, the WebAPI server 132 executes application processing based on the application software according to the transferred operation request. The application processing is, for example, processing related to air conditioning control when the embedded device 10 is an air conditioning controller. When executing the application processing, the WebAPI server 132 instructs the Web server 112 to display an operation screen for executing the application processing on the built-in browser 111 or the external browser 311.
[0112] Specifically, when receiving an operation request from the built-in browser 111 via HTTP communication, the Web server 112 displays the operation screen as the first screen on the built-in browser 111. In this case, the Web server 112 operates as an internal virtual server 141, and as a response to the operation request, sends a Web document 121 for generating the operation screen of the embedded device 10 to the built-in browser 111 via HTTP communication. Here, the Web document 121 stored in the storage unit 12 includes a description for generating the operation screen.
[0113] When the web document 121 is sent, the built-in browser 111 analyzes the web document 121 to generate an operation screen, and displays it on the display unit 14. As an example, when the embedded device 10 is an air conditioner controller, the built-in browser 111 Figure 6 The operation screen shown is displayed on the display unit 14. The user can input on / off of the air conditioner, switching of the operation mode, setting of the set temperature and the air volume, and the like while viewing the operation screen.
[0114] On the other hand, when an operation request is received from the external browser 311 via HTTPS communication, after the authentication control unit 131 performs authentication processing as described above, the Web server 112 displays the operation screen as the second screen on the external browser 311. In this case, the Web server 112 operates as the external virtual server 142, and as a response to the operation request, sends the Web document 121 for generating the operation screen of the embedded device 10 back to the external browser 311 via HTTPS communication.
[0115] When the Web document 121 is sent, the external browser 311 analyzes the Web document 121 and generates an operation screen. Figure 6 The same operation screen is displayed on the display unit 34. The operation screen displayed on the built-in browser 111 and the operation screen displayed on the external browser 311 are the same except for the difference due to the display setting.
[0116] The built-in browser 111 and the external browser 311 receive operation information input by the user on such an operation screen, and transmit the information to the Web server 112 and the WebAPI server 132. The WebAPI server 132 executes application processing according to the transmitted operation information.
[0117] Next, refer to Figure 7 as well as Figure 8 , describing the flow of processing performed by display system 1.
[0118] No. 1, reference Figure 7, which explains the user authentication process performed by the embedded machine 10. When the user wishes to operate the operation unit 13 of the embedded machine 10 or the operation unit 33 of the external terminal 30 to start using the embedded machine 10, the following is performed: Figure 7 User authentication processing shown.
[0119] After the user authentication process starts, the Web server 112 of the embedded machine 10 receives a request for user authentication (step S101). Specifically, when the user operates the operation unit 13 of the embedded machine 10, the built-in browser 111 sends an HTML document requesting user authentication to the Web server 112 via the internal communication of the embedded machine 10. On the other hand, when the user operates the operation unit 33 of the external terminal 30, the external browser 311 sends an HTML document requesting user authentication to the Web server 112 via the external network. The Web server 112 receives the HTML document requesting user authentication sent from the built-in browser 111 or the external browser 311.
[0120] When receiving the request for user authentication, the web server 112 determines the source of the received request (step S102). Specifically, the web server 112 determines whether the address of the source is a loopback address. Furthermore, the web server 112 determines that the source is the built-in browser 111 when the address of the source is a loopback address, and determines that the source is the external browser 311 when the address of the source is an address other than the loopback address.
[0121] When the source of the request is the external browser 311 (step S102; external browser), the Web server 112 accepts the connection using the external virtual server 142 (step S103). The external virtual server 142 decrypts the received request.
[0122] When the connection is accepted, the external virtual server 142 sends the Web document 121 describing the input screen for user authentication to the external browser 311, so that, for example, Figure 4 The user authentication input screen shown is displayed on the display unit 34 (step S104).
[0123] When the user authentication input screen is displayed, the external virtual server 142 receives the user name and password input on the user authentication input screen from the external browser 311, and determines whether the user authentication is successful (step S105).
[0124] When the authentication fails (step S105 ; No), the external virtual server 142 sends the Web document 121 describing the authentication failure screen to the external browser 311 , and displays the authentication failure screen on the display unit 34 (step S106 ).
[0125] On the other hand, if the authentication is successful (step S105; "Yes"), the external virtual server 142 sends the Web document 121 describing the authentication success screen to the external browser 311, so that, for example, Figure 5 The authentication success screen shown is displayed on the display unit 34 (step S107).
[0126] On the other hand, in step S102 , when the source of the user authentication request is the built-in browser 111 (step S102 ; built-in browser), the Web server 112 accepts the connection using the internal virtual server 141 (step S108 ).
[0127] When the connection is accepted, the internal virtual server 141 guides the received request to the URL of the authentication success screen by redirection or URL rewriting (step S109). Then, the internal virtual server 141 sends the Web document 121 describing the authentication success screen to the built-in browser 111, so that, for example, Figure 5 The authentication success screen shown is displayed on the display unit 14 (step S110). Figure 7 The user authentication process shown ends.
[0128] No. 2, reference Figure 8 , which explains the operation screen display processing performed by the embedded machine 10. Figure 7 After the user authentication process shown in the figure succeeds, execute Figure 8 The operation screen shown is displayed.
[0129] After the operation screen display process is started, the Web server 112 receives an operation request from the embedded machine 10 (step S201). Specifically, when the user operates the operation unit 13 of the embedded machine 10, the built-in browser 111 sends an HTML document of the operation request to the Web server 112 via the internal communication of the embedded machine 10. On the other hand, when the user operates the operation unit 33 of the external terminal 30, the external browser 311 sends an HTML document of the operation request to the Web server 112 via the external network. The Web server 112 receives the HTML document of the operation request sent from the built-in browser 111 or the external browser 311.
[0130] When receiving the operation request, the web server 112 determines the source of the received operation request (step S202). Specifically, the web server 112 determines whether the address of the source is a loopback address. Furthermore, the web server 112 determines that the source is the built-in browser 111 when the address of the source is a loopback address, and determines that the source is the external browser 311 when the address of the source is an address other than the loopback address.
[0131] When the source of the operation request is the external browser 311 (step S202; external browser), the Web server 112 accepts the connection using the external virtual server 142 (step S203). The external virtual server 142 decrypts the received operation request.
[0132] When the connection is accepted, the address assigning unit 144 assigns the address of the transmission source to the operation request (step S204). Specifically, the address assigning unit 144 adds the address of the external browser 311 as the transmission source address to the header or query parameter of the received operation request.
[0133] After assigning the address of the transmission source, the address assigning unit 144 transfers the operation request to the application server 113 (step S205).
[0134] On the other hand, in step S202 , when the source of the operation request is the built-in browser 111 (step S202 ; built-in browser), the Web server 112 accepts the connection using the internal virtual server 141 (step S206 ).
[0135] When the connection is accepted, the address assigning unit 143 assigns the address of the transmission source to the operation request (step S207). Specifically, the address assigning unit 144 adds the loopback address as the address of the transmission source to the header or query parameter of the received operation request.
[0136] After assigning the address of the transmission source, the address assigning unit 144 transfers the operation request to the application server 113 (step S208).
[0137] When an operation request is forwarded from the Web server 112, the authentication control unit 131 in the application server 113 determines the source of the forwarded operation request (step S209). Specifically, the authentication control unit 131 determines whether the source of the operation request is the external browser 311 or the built-in browser 111 based on the address given to the operation request.
[0138] When the transmission source is the external browser 311 (step S209; external browser), the authentication control unit 131 performs authentication processing (step S210). Specifically, the authentication control unit 131 determines whether the correct authentication information assigned by the external browser 311 during user authentication is included in the forwarded operation request. When the operation request contains the correct authentication information, the authentication control unit 131 determines that the authentication is successful and allows the operation request to pass through the WebAPI server 132. In contrast, when the operation request does not contain the correct authentication information, the authentication control unit 131 determines that the authentication has failed and does not allow the operation request to pass through the WebAPI server 132.
[0139] On the other hand, when the transmission source is the built-in browser 111 (step S209 ; built-in browser), the authentication control unit 131 skips the authentication process of step S210 and allows the transferred operation request to pass through the WebAPI server 132 unconditionally.
[0140] When the operation request is transferred from the authentication control unit 131, the WebAPI server 132 displays the operation screen on the built-in browser 111 or the external browser 311 via the Web server 112. Then, the WebAPI server 132 executes application processing based on the transferred operation request (step S211).
[0141] Specifically, the WebAPI server 132 instructs the Web server 112 to display an operation screen. The Web server 112 sends a Web document 121 describing the operation screen to the Web browser that is the source of the operation request in the built-in browser 111 and the external browser 311, so that, for example, Figure 6 The operation screen shown is displayed on the display unit 14 or the display unit 34. The WebAPI server 132 executes application processing according to the operation information input from the user to the operation screen. Figure 8 The operation screen shown shows that the processing is completed.
[0142] As described above, in the embedded machine 10 involved in the first embodiment, the Web server 112 sends the Web document 121 stored in the storage unit 12 to the built-in browser 111 via unencrypted communication, so that the first screen based on the Web document 121 is displayed on the built-in browser 111. On the other hand, the Web server 112 sends the Web document 121 stored in the storage unit 12 to the external browser 311 via encrypted communication, so that the second screen based on the Web document 121 is displayed on the external browser 311.
[0143] In this way, in the embedded machine 10 that displays a screen based on the same Web document 121 on the built-in browser 111 and the external browser 311, since different security is applied to the built-in browser 111 and the external browser 311, the processing load in the communication with the built-in browser 111 can be reduced. As a result, the performance of the embedded machine 10 can be improved.
[0144] In addition, the embedded machine 10 according to the first embodiment displays the input screen of the user authentication on the external browser 311 when receiving the request of the user authentication from the external browser 311, and displays the completion screen of the user authentication on the built-in browser 111 instead of displaying the input screen of the user authentication on the built-in browser 111 when receiving the request of the user authentication from the built-in browser 111. In this way, the method of user authentication can be switched in consideration of the difference in security between the case of connecting from the built-in browser 111 and the case of connecting from the external browser 311. As a result, the operability of the user can be improved.
[0145] In the embedded machine 10 according to the first embodiment, the Web server 112 that distributes the Web document 121 also serves as a reverse proxy for the WebAPI, thereby operating a virtual server. Thus, one Web server 112 can also serve as a server having four different functions: an external Web server, an external reverse proxy, an internal Web server, and an internal reverse proxy. As a result, the resources of the embedded machine 10 can be saved.
[0146] In addition, in the embedded machine 10 involved in the first embodiment, when the web server 112 receives a request for user authentication from the built-in browser 111, it changes the connection destination of the request for user authentication from the input screen of the user authentication to the completion screen by redirection or URL rewriting. The process of switching screens between the connection from the built-in browser 111 and the connection from the external browser 311 can also be implemented by describing it in the JavaScript of the web document 121. However, the source code of the JavaScript of the web document 121 can be referenced from the web browser. Therefore, when describing the internal processing in JavaScript, leakage of the internal processing is involved. In the first embodiment, since redirection or URL rewriting is used, only the processing that is not a problem with leakage can be described in the source code of the JavaScript in the web document 121, and leakage of the internal processing can be prevented.
[0147] (Implementation Method 2)
[0148] Next, Embodiment 2 will be described. The description of the same configuration and function as that of Embodiment 1 will be appropriately omitted.
[0149] In the first embodiment, the web server 112 rewrites or redirects the URL of the user authentication screen, thereby omitting user authentication when connecting to the web server 112 from the built-in browser 111. In contrast, in the second embodiment, when connecting to the web server 112 from the built-in browser 111, the web server 112 guides to a screen for performing user authentication using the authentication device 400 mounted on the embedded machine 10.
[0150] The user who operates the external browser 311 is usually in a place physically far away from the embedded machine 10, so it is difficult to operate the hardware device installed in the embedded machine 10. However, in a structure where the application server 113 that can operate the hardware device operates on the embedded machine 10, the user who operates the built-in browser 111 can operate the hardware device. Taking advantage of this, in the second embodiment, the authentication device 400 is installed in the embedded machine 10 as a hardware device, and the user who operates the embedded machine 10 is authenticated using the authentication device 400.
[0151] Reference Fig. 9 Next, a configuration related to user authentication in Embodiment 2 will be described. The embedded device 10 according to Embodiment 2 further includes an authentication device 400. The authentication device 400 is a device for authenticating a user who operates the embedded device 10.
[0152] As an example, the authentication device 400 is a biometric authentication device that performs biometric authentication of a user such as fingerprint authentication, facial authentication, vein authentication, iris authentication, etc. Alternatively, the authentication device 400 may be a reading device that reads an ID (Identification) card owned by a user such as a contact IC (Integrated Circuit) card reader or an NFC (Near Field Communication) reader.
[0153] Thus, the authentication device 400 is a device that the user can operate at hand while viewing the built-in browser 111. In order to perform user authentication using the authentication device 400, the user needs to physically access the authentication device 400.
[0154] When receiving a user authentication request from the built-in browser 111 via unencrypted HTTP communication, the Web server 112 uses the function of the internal virtual server 141 to display a screen prompting the user to operate the authentication device 400 as the first screen on the built-in browser 111 .
[0155] Specifically, the Web server 112 changes the connection destination of the user authentication request from Figure 4 The user authentication input screen shown is changed to a screen urging the user to operate the authentication device 400. Then, the web server 112 sends the web document 121 for generating the screen urging the user to operate the authentication device 400 to the built-in browser 111 via HTTP communication. In the second embodiment, the web document 121 includes a description for generating the screen urging the user to operate the authentication device 400.
[0156] The built-in browser 111 will, for example, Fig.10 The screen instructing the user to perform user authentication using the authentication device 400 is displayed on the display unit 14 as a first image based on the web document 121 transmitted from the web server 112. When the user sees such a screen, he or she physically accesses the authentication device 400 and performs biometric authentication or card reading authentication.
[0157] At this time, the web server 112 assigns the loopback address as the address of the transmission source to the request for user authentication sent from the built-in browser 111 by the address assigning unit 143, and forwards the request for user authentication to the application server 113. As a result, the web server 112 calls the WebAPI for controlling the authentication device 400, and starts the operation of the authentication device 400. The request for user authentication is not subject to the authentication process of the authentication control unit 131, but is forwarded to the WebAPI server 132, similarly to the operation request sent from the built-in browser 111 described in the first embodiment.
[0158] After that, the WebAPI server 132 monitors the authentication device 400 to determine whether the user authentication of the authentication device 400 is successful. Then, the WebAPI server 132 notifies the built-in browser 111 of the result of the user authentication via the Web server 112. For example, if the user authentication is successful, the WebAPI server 132 sends a Figure 5 The screen indicating that the user authentication is successful is displayed on the built-in browser 111. If the user authentication fails, the WebAPI server 132 causes the built-in browser 111 to display a screen indicating that the user authentication has failed via the Web server 112.
[0159] The notification from the WebAPI server 132 to the built-in browser 111 needs to comply with the Web specification. As one method, a method can be cited in which the JavaScript operating on the built-in browser 111 periodically inquires about the result of user authentication in a polling manner. Alternatively, as another method, the following method can be cited: when the operation of the authentication device 400 starts, the built-in browser 111 connects to the WebAPI server 132 through the WebSocket technology, and the WebAPI server 132 uses the WebSocket to notify the built-in browser 111 that the user authentication is successful.
[0160] When receiving a user authentication request from the external browser 311 via encrypted HTTPS communication, the Web server 112 uses the function of the external virtual server 142 to perform the same processing as in Embodiment 1. Specifically, the Web server 112 sends the Web document 121 stored in the storage unit 12 to the external browser 311 via HTTPS communication. Then, the Web server 112 sends, for example, Figure 4 The input screen for user authentication without using the authentication device 400 as shown is displayed on the external browser 311 as the second screen.
[0161] In addition, the authentication device 400 may be pre-installed in the embedded machine 10 when shipped from the factory. Alternatively, the authentication device 400 may be attached to the embedded machine 10 by connecting to a slot, a USB connector, etc. provided in the embedded machine 10. As described above, in the application server 113, application software may be attached. Therefore, it is also possible to attach user authentication implemented by the authentication device 400 as user authentication by installing a Web API that operates the authentication device 400 as application software.
[0162] The authentication device 400 is not limited to a biometric authentication device or a reader. For example, the authentication device 400 may also be a device that performs user authentication based on a PIN (Personal Identification Number) code. When a PIN code is used, a user name and a password are recorded in a local storage area of the embedded machine 10. In addition, the 4-digit PIN code is used as an access key to the local storage area. Even when a PIN code is used, hardware access to the local storage area is required, so a method similar to the case where the authentication device 400 is a biometric authentication device or a reader can be used.
[0163] (Implementation 3)
[0164] Next, Embodiment 3 will be described. The description of the same configuration and function as those of Embodiments 1 and 2 will be appropriately omitted.
[0165] In the first embodiment, the Web server 112 has the function of the internal virtual server 141 and the function of the external virtual server 142. In contrast, in the third embodiment, the Web server 112 does not have the function of the virtual server.
[0166] As a method for setting a difference in security between the connection from the built-in browser 111 and the connection from the external browser 311 without using the function of the virtual server, there is a method of operating both the HTTP server and the HTTPS server in one server. Specifically, one Web server 112 can operate as both the HTTP server and the HTTPS server.
[0167] In this case, when the Web server 112 receives a connection from the built-in browser 111 via internal communication, the Web server 112 receives the connection through the HTTP server. On the other hand, when the Web server 112 receives a connection from the external browser 311 on the external terminal 30 via the external network, the Web server 112 receives the connection through the HTTPS server. At this time, the Web server 112 controls by the function of the firewall so that the built-in browser 111 can be connected to the HTTP server but the external network cannot be connected to the HTTP server. Thus, the problem of the difference in security settings between the connection from the built-in browser 111 and the connection from the external browser 311 can be solved.
[0168] However, when both the HTTP server and the HTTPS server are operated by one server, the HTTP server and the HTTPS server are not separated, so it is impossible to perform redirection and URL rewriting depending on whether the connection source is the built-in browser 111 or the external browser 311.
[0169] As a method for performing redirection and URL rewriting without using the function of a virtual server, there is a method in which, utilizing the characteristic that the port numbers used in the HTTP server and the HTTPS server are different, two identical Web servers 112 are prepared. Specifically, one of the two Web servers 112 is started in the setting for HTTP, and the other is started in the setting for HTTPS.
[0170] In this case, the HTTP setting and the HTTPS setting are separated, so it is possible to handle redirection and URL rewriting depending on whether the connection source is the built-in browser 111 or the external browser 311. However, when two Web servers 112 are started, there is a problem that the resources used in the embedded machine 10 increase.
[0171] Therefore, in the third embodiment, the virtualization of the Web server 112 is adopted. Here, the virtualization of the Web server 112 means starting one Web server application and operating multiple different Web servers in the Web server application. In other words, the virtualization of the Web server 112 means the functions that can be realized only by the Web server software and that the Web server software has. For example, the Web server software refers to Nginx (registered trademark in Japan).
[0172] As one method for virtualizing the Web server 112, a virtual machine technology is used in Embodiment 3. In order to use the virtual machine technology, virtual machine software is required in addition to the Web server software. The virtual machine software is, for example, Linux (registered trademark in Japan) KVM, VirtualBox, or VMWare (registered trademark in Japan).
[0173] When the virtual machine technology is used, a plurality of virtual machines are operated on the embedded machine 10. In addition, a plurality of virtual Web servers are operated on the plurality of virtual machines as the Web server 112. The Web server 112 performs unencrypted communication with the built-in browser 111 through the first virtual machine, and performs encrypted communication with the external browser 311 through the second virtual machine.
[0174] Specifically, if Fig.11 As shown, the embedded machine 10 involved in Implementation 3 has the functions of multiple virtual machines 1 to 3. Each virtual machine 1 to 3 operates on the host OS (Operating System) 550 of the embedded machine 10. Virtual machines 1 to 3 operate based on libraries 512, 522, and 532, respectively. On the first virtual machine 1, OS513 and HTTP server 511 operate. On the second virtual machine 2, OS523 and HTTPS server 521 operate. On the third virtual machine 3, OS533 and application server 531 operate. In this way, different OSs operate independently on each virtual machine 1 to 3, and the server operates independently on each OS.
[0175] When connecting from the built-in browser 111 to the Web server 112, the HTTP server 511 operating on the first virtual machine 1 accepts the connection. On the other hand, when connecting from the external browser 311 to the Web server 112, the HTTPS server 521 operating on the second virtual machine 2 accepts the connection. In addition, the same processing as the internal virtual server 141 described in the first embodiment is performed on the first virtual machine 1, the same processing as the external virtual server 142 described in the first embodiment is performed on the second virtual machine 2, and the same processing as the application server 113 described in the first embodiment is performed on the third virtual machine 3. At this time, by sharing the network file between different virtual machines, the first virtual machine 1 and the second virtual machine 2 use a common Web document 121.
[0176] Thus, in the third embodiment, the Web server 112 operates the plurality of virtual machines 1 to 3 on the embedded machine 10 without using the virtual server function. Furthermore, the Web server 112 operates the HTTP server 511 on the first virtual machine 1 and operates the HTTPS server 521 on the second virtual machine 2. Access from the external network is limited to the second virtual machine 2, so that security can be improved.
[0177] also, Fig.11 The system configuration shown shows an example of using a virtual machine called a host type among several types of virtual machines. However, even when using other types of virtual machines, there is no change in the point that multiple virtual machines are operated on the same embedded machine 10, so other types of virtual machines can also be used.
[0178] (Implementation 4)
[0179] Next, Embodiment 4 will be described. The description of the same configuration and function as those of Embodiments 1 to 3 will be appropriately omitted.
[0180] In the third embodiment, multiple virtual machines are operated on the embedded machine 10. However, the hardware resources such as the CPU and memory of the embedded machine 10 are smaller than those of a general personal computer, so it is sometimes difficult to operate multiple virtual machines. Therefore, in the fourth embodiment, as another method for virtualizing the Web server 112, container virtualization technology is used.
[0181] Container virtualization technology is a simple virtualization software that can be implemented using fewer hardware resources than virtual machines. In order to use container virtualization technology, container virtualization software is required in addition to Web server software. Container virtualization software refers to Docker (registered trademark in Japan), for example.
[0182] In container virtualization, the Web server 112 and the setting files required for its operation are concentrated in one package called a container, and the operation is performed in units of containers. In other words, multiple containers are generated on the embedded machine 10. And, as the Web server 112, multiple virtual Web servers operate on multiple containers. Container virtualization is similar to the method of starting multiple identical Web servers 112, but in container virtualization, the file system is separated for each container in operation.
[0183] In the structure using virtual machines described in Implementation 3, the machine itself is virtualized, and an independent OS is operated for each virtual machine. In contrast, in container virtualization, the operating OS is only one OS of the embedded machine 10, so in principle, the hardware resources used are less than those of the structure using virtual machines.
[0184] The web server 112 performs unencrypted communication with the built-in browser 111 using a first container generated by the container virtualization technology, and performs encrypted communication with the external browser 311 using a second container generated by the container virtualization technology.
[0185] Specifically, if Fig.12 As shown, the embedded machine 10 involved in Implementation 4 has the functions of multiple containers 1 to 3 and a container management unit 640. Each container 1 to 3 is managed by the container management unit 640 and operates on the OS 650 of the embedded machine 10. The containers 1 to 3 operate based on the libraries 612, 622, and 632, respectively. On the first container 1, the HTTP server 611 operates. On the second container 2, the HTTPS server 621 operates. On the third container 3, the application server 631 operates. In this way, different OSs operate independently on each virtual machine, and the server operates independently on each OS.
[0186] When connecting from the built-in browser 111 to the Web server 112, the HTTP server 611 operating on the first container 1 accepts the connection. On the other hand, when connecting from the external browser 311 to the Web server 112, the HTTPS server 621 operating on the second container 2 accepts the connection. In addition, the same processing as the internal virtual server 141 described in the first embodiment is performed on the first container 1, the same processing as the external virtual server 142 described in the first embodiment is performed on the second container 2, and the same processing as the application server 113 described in the first embodiment is performed on the third container 3.
[0187] Redirection and URL rewriting of the Web server 112 are set in the first container 1. In order to allow access to the file system of the embedded machine 10 itself from each container 1 to 3, a Web document 121 for making the screen common may be arranged in the file system of the embedded machine 10 side.
[0188] Thus, in the fourth embodiment, the web server 112 generates a plurality of containers 1 to 3 on the embedded machine 10. Furthermore, the web server 112 operates the HTTP server 611 on the first container 1 and operates the HTTPS server 621 on the second container 2. Since the file system is separated for each container, the screen dedicated to the built-in browser 111 is included only in the first container 1, so that the screen dedicated to the built-in browser 111 cannot be accessed from the external network.
[0189] (Variation Example)
[0190] Although the embodiments have been described above, the embodiments may be combined or the embodiments may be appropriately modified or omitted.
[0191] For example, in the above-described embodiment, the embedded machine 10 implements different security measures for (1) encryption of communication, (2) user authentication, and (3) authentication of WebAPI in the display process in the built-in browser 111 and the display process in the external browser 311, respectively. However, the embedded machine 10 is not limited to implementing different security measures for all of (1) to (3), and may implement different security measures for at least one of (1) to (3).
[0192] In addition, the user authentication screen for the built-in browser 111 may be changed according to the setting input by the user. For example, when the web server 112 receives a request for user authentication from the built-in browser 111, the same user authentication input screen as when the request for user authentication is received from the external browser 311 is displayed in the built-in browser 111 by default. Furthermore, when the web server 112 receives a request for user authentication from the built-in browser 111, it may switch whether to display the default input screen in the built-in browser 111 or to display the completion screen of user authentication without displaying the input screen according to the setting input by the user via the operation unit 13. Furthermore, an option of displaying the screen urging the operation authentication device 400 as described in Embodiment 2 may be added. The web server 112 may switch the screen when the request for user authentication is received from the built-in browser 111 by redirection or URL rewriting according to the setting input by the user.
[0193] In the above embodiment, the embedded device 10 is described as an air conditioner controller, but the embedded device 10 is not limited thereto and may be electronic devices such as a water heater, an automatic rice cooker, a washing machine, a refrigerator, a television, or a controller for operating them.
[0194] In the above embodiment, the communication based on HTTP and the communication based on HTTPS are described as examples of unencrypted communication and encrypted communication, respectively. However, communication in a method other than HTTP and HTTPS may also be used.
[0195] In the above-mentioned embodiment, in the control unit 11, by executing the program stored in the storage unit 12 by the CPU, the built-in browser 111, the web server 112 and the application server 113 are functioned. In addition, in the control unit 31, by executing the program stored in the storage unit 32 by the CPU, the external browser 311 is functioned. However, the control units 11 and 31 may also be dedicated hardware. Dedicated hardware is, for example, a single circuit, a composite circuit, a programmed processor, an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a combination thereof. In the case where the control units 11 and 31 are dedicated hardware, the functions of each unit may be respectively implemented by separate hardware, or the functions of each unit may be implemented collectively by a single hardware.
[0196] In addition, part of the functions of each unit may be implemented by dedicated hardware, and the other part may be implemented by software or firmware. In this way, the control units 11 and 31 can implement the above-mentioned functions by hardware, software, firmware, or a combination thereof.
[0197] It is also possible to apply a program that defines the operations of the embedded device 10 and the external terminal 30 to an existing computer such as a personal computer or an information terminal device, thereby causing the computer to function as the embedded device 10 and the external terminal 30 .
[0198] In addition, the distribution method of such a program is arbitrary. For example, it can be stored in a computer-readable recording medium such as a CD-ROM (Compact Disk ROM), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), a memory card, etc., or it can be distributed via a communication network such as the Internet.
[0199] The present disclosure can realize various embodiments and variations without departing from the broad spirit and scope of the present disclosure. In addition, the above-mentioned embodiments are used to illustrate the embodiments of the present disclosure and do not limit the scope of the present disclosure. That is, the scope of the present disclosure is not shown by the embodiments but by the claims. In addition, various variations implemented within the scope of the claims and the equivalent disclosed meanings are considered to be within the scope of the present disclosure.
[0200] Explanation of symbols
[0201] 1: Display system; 10: Embedded machine; 11, 31: Control unit; 12, 32: Storage unit; 13, 33: Operation unit; 14, 34: Display unit; 15, 35: Communication unit; 30: External terminal; 111: Built-in browser; 112: Web server; 113, 531, 631: Application server; 121: Web document; 131: Authentication control unit; 132: WebAPI server; 141: Internal virtual server; 142: External virtual server; 143, 144: Address assignment unit; 311: External browser; 400: Authentication device; 511, 611: HTTP server; 521, 621: HTTPS server; 512, 522, 532, 612, 622, 632: Library; 513, 523, 533, 550, 650: OS; 640: Container management unit.
Claims
1. An embedded machine communicatively connected to an external terminal having an external browser, in, The embedded machine has: Storage department, storing Web documents; Built-in browser; as well as The web server sends the web document stored in the storage unit to the built-in browser via unencrypted communication, so that a first screen based on the web document is displayed on the built-in browser, and sends the web document stored in the storage unit to the external browser via encrypted communication, so that a second screen based on the web document is displayed on the external browser.
2. The embedded machine according to claim 1, in, The Web server uses an internal virtual server to perform the unencrypted communication with the built-in browser. The Web server performs the encrypted communication with the external browser using an external virtual server.
3. The embedded machine according to claim 1 or 2, in, When the Web server receives a user authentication request from the built-in browser via the unencrypted communication, the Web server does not display an input screen for the user authentication on the built-in browser, but displays a completion screen for the user authentication as the first screen on the built-in browser, When receiving the user authentication request from the external browser via the encrypted communication, the Web server causes the external browser to display the input screen as the second screen.
4. The embedded machine according to claim 3, in, When receiving the user authentication request from the built-in browser, the Web server changes the connection destination of the received request from the input screen to the completion screen by redirection or URL rewriting.
5. The embedded machine according to claim 3 or 4, in, When the Web server receives the user authentication request from the built-in browser or the external browser, it determines whether the source of the received request is the built-in browser or the external browser based on whether the address of the source of the received request matches the loopback address.
6. The embedded machine according to any one of claims 3 to 5, in, When the Web server receives the user authentication request from the built-in browser, it switches according to the setting input by the user whether to display the input screen as the first screen in the built-in browser or not display the input screen and display the completion screen as the first screen in the built-in browser.
7. The embedded machine according to any one of claims 1 to 6, in, When the Web server receives an operation request from the built-in browser via the unencrypted communication, the Web server displays the operation screen of the embedded device as the first screen on the built-in browser, When receiving the operation request from the external browser via the encrypted communication, the Web server causes the external browser to display the operation screen as the second screen.
8. The embedded machine according to any one of claims 1 to 7, in, The embedded machine further includes an application server that performs authentication processing for using application software and application processing based on the application software. the application server executes the application process without executing the authentication process when the Web server receives an operation request from the built-in browser via the unencrypted communication, The application server executes the application process after executing the authentication process, when the Web server receives the operation request from the external browser via the encrypted communication.
9. The embedded machine according to claim 8, in, When the Web server receives the operation request from the built-in browser or the external browser, the Web server assigns the address of the source of the received operation request to the operation request. The application server determines whether the transmission source is the built-in browser or the external browser based on the address of the transmission source assigned to the operation request.
10. The embedded machine according to claim 9, in, When the Web server receives the operation request from the built-in browser or the external browser, the Web server adds the address of the sending source to a header or a query parameter of the received operation request, thereby assigning the address of the sending source to the operation request.
11. The embedded machine according to claim 1 or 2, in, The embedded machine is further provided with an authentication device, which authenticates a user operating the embedded machine. When the Web server receives a user authentication request from the built-in browser via the unencrypted communication, the Web server displays a screen prompting the user to operate the authentication device as the first screen on the built-in browser, When receiving the user authentication request from the external browser via the encrypted communication, the Web server displays an input screen for user authentication without using the authentication device as the second screen on the external browser.
12. The embedded machine according to any one of claims 1 to 11, in, The Web server uses the first virtual machine running on the embedded machine to perform the unencrypted communication with the built-in browser. The Web server performs the encrypted communication with the external browser using the second virtual machine running on the embedded machine.
13. The embedded machine according to any one of claims 1 to 12, in, The Web server uses the first container generated by container virtualization technology to perform the unencrypted communication with the built-in browser. The Web server performs the encrypted communication with the external browser using the second container generated by the container virtualization technology.
14. A display system comprising: The embedded machine according to any one of claims 1 to 13; and The external terminal.
