TWI670957B - Peripheral device integration system for multimedia machines - Google Patents

Abstract

A peripheral device integration system for a multimedia machine includes a cloud server and a plurality of multimedia machines, and the multimedia machine includes an abstract interface defining unit, a component expansion implementation unit, and an application container unit. a device service unit, a communication communication unit, and a host application unit, wherein the host application unit transmits instructions to the device service unit through the device service unit or the communication communication unit according to different application operations, and is loaded by the device service unit Corresponding dynamic expansion configuration file to control the operation of different hardware devices, which will solve the problem of expanding the heterogeneous device and greatly reducing the integration time, and the device service unit can receive the code specification and package it as a monitoring information file. The multimedia machine can transmit the monitoring information file to the cloud server to monitor the operation status of each multimedia machine in real time.

Description

Peripheral device integration system for multimedia machines

The invention relates to a peripheral device integration system for a multimedia machine, in particular to a peripheral device integration system capable of solving heterogeneous device expansion and state monitoring problems.

With the increasing popularity of multimedia kiosks, and based on the familiarity of Internet technology, there are a wide variety of Kiosks on the market, such as self-service ticket vending machines, gateway machines, vending machines, and media channels. The viewing machine and the digital advertising broadcaster reveal an application of the Kiosk multimedia server, which includes: navigation, advertising, inquiry, finance, and life. But no matter which kind of Kiosk is facing the complexity technical problem of peripheral device integration.

Taking the self-service ticket vending machine as an example, there are peripheral devices such as a receipt printer, a ticket printer, a gold flow module hardware (cash or ticket payment), a network hardware routing device, a host, and the like. In addition to the integration of many heterogeneous devices, there are also technical problems with compatibility of different hardware manufacturers on the same hardware device.

Therefore, if a set of architecture can be developed, the system integrator can solve the problem of expansion and status monitoring in a relatively simple and fast way in the process of dealing with many heterogeneous devices, and greatly reduce the burden of integration time. The invention should be an optimal solution.

The invention relates to a peripheral device integration system for a multimedia machine, which comprises a cloud server; a plurality of multimedia machines are connected with the cloud server, and the multimedia machine system comprises an abstract interface defining unit. Obtaining the state of the hardware device in an abstract definition manner, the abstract interface defining unit includes at least one device state obtaining module, and adopting a single interface to obtain the actual state of the hardware device inside the multimedia machine; a code specification storage The module is configured to store at least one defined state code profile according to different hardware devices; a device state translation module is connected to the device state acquisition module and the code specification storage module, Translating the actual state of the hardware device obtained by the device state obtaining module into a defined code specification; a state code returning module is connected to the device state translation module for using the translated code The specification is transmitted; a compiling component generates a module for generating a dynamic expansion element according to the hardware device inside the multimedia machine And a pair of dynamic expansion configuration files that should dynamically expand components; a component expansion implementation unit is capable of setting a customization function for different hardware devices inside the multimedia machine, and calling the corresponding hardware device to execute the set Customizing function; an application container unit for providing different environment execution files of different bits required by different hardware devices; a device service unit, and the application container unit, the abstract interface defining unit, and the component expansion implementation The unit is connected to perform the required environment execution file to load the corresponding dynamic expansion configuration file according to the driving environment required by the different hardware devices, and the device service unit is more capable of receiving the status code return The module transmits the code specification and encapsulates it into a monitoring information file, and the multimedia machine can transmit the monitoring information file to the cloud server; a communication communication unit is connected to the device service unit for different The dynamic expansion configuration file corresponding to the hardware device communicates for message transmission and/or reception; a host application unit is associated with The device service unit is connected to the communication communication unit, and the host application unit is configured to perform an application operation, and transmits an instruction to the device service unit through the device service unit or the communication communication unit according to different application operations, and is served by the device. The unit loads the corresponding dynamic expansion configuration file to control the operation of different hardware devices to complete the application operation performed by the host application unit.

More specifically, the abstract interface definition unit further includes an environment detection module, and the environment detection module is configured to detect whether the hardware device inside the multimedia device can operate normally.

More specifically, the abstract interface definition unit further includes an identification name definition module for defining a unique identification name of the hardware device inside the multimedia machine.

More specifically, the abstract interface definition unit further includes an initialization operation module, which is used to define an operation mode after the hardware device inside the multimedia device is turned on.

More specifically, after the device service unit loads the corresponding dynamic expansion configuration file, the device status acquisition module can obtain the status change notification of the hardware device, and execute the device through the initialization operation module. Initialize the job.

More specifically, the compiled component generation module converts the dynamic expansion component into the dynamic extended configuration file using RSA asymmetric encryption.

Other details, features, and advantages of the present invention will be apparent from the following description of the preferred embodiments.

Please refer to FIG. 1 to FIG. 2B , which are schematic diagrams showing the overall architecture of the peripheral device integration system for the multimedia machine, the architecture diagram of the multimedia machine platform and the architecture of the abstract interface definition unit. The peripheral device integration system of the machine includes a cloud server 1 and at least one multimedia machine 2, wherein the multimedia machine 2 includes an abstract interface defining unit 21, a component expansion implementing unit 22, and an application container unit 23. A device service unit 24, a communication communication unit 25, a host application unit 26, and one or more hardware devices 27.

The abstract interface defining unit 21 obtains the state and state translation of the hardware device 27 in an abstract definition manner, and the hardware device 27 integrates the single device into the monitoring structure of the multimedia machine through the abstract interface defining unit 21 and provides dynamic expansion. And the removal without modifying the main system, and the abstract interface definition unit 21 is an IDevice interface written in an object-oriented language (definition method: public interface IDevice: IObservable<DeviceStatusChangedArgs>, IDisposable), all categories that implement this interface (eg Each of the hardware devices is required to implement a specified abstract definition, including a method for obtaining a state of the hardware device, and the abstract interface defining unit 21 includes at least a device state obtaining module 211, a code specification storage module 212, and a device state. The translation module 213, a status code return module 214, a compilation component generation module 215, an environment detection module 216, an identification name definition module 217, an initialization operation module 218;

The device state obtaining module 211 obtains the actual state of the hardware device 27 inside the multimedia device 2 by using a single interface. Since each device has its own defined communication format to obtain the current state of the device, it must be The service layer can obtain the actual state of the device by a single interface communication without knowing the communication of each protocol, and an example of the instruction for obtaining the state of the hardware device is as follows: object GetStatus(params object[] parameters);

The code specification storage module 212 is configured to store at least one defined status code configuration file according to different hardware devices, where the status code configuration file defines a corresponding manner of each device status when the system is operating, such as whether a log is required to be retained. Whether the record needs to be displayed on the screen, whether it is allowed to continue the operation flow, the corresponding message is displayed, etc., the following example shows the possible settings of the printer (whether the device type/status code/status needs to be recorded/status needs to be displayed to Status column / Receive this message to allow the flow operation / UI display message / API code / actual message / customer service corresponding mode): (1) Thermal, R0001, Y, Y, N, receipt printer error, please inform Field personnel processing, status code: R0001. , ASB_NO_RESPONSE, the receipt printer does not have any response; please inform the counter. ,no. (2) Thermal, R0002, Y, Y, Y, receipt printing machine printing completed. , ASB_PRINT_SUCCESS, the receipt printer print is complete. ,no. (3) Thermal, R0003, Y, Y, N, the receipt printer is abnormal, please inform the customer service staff, status code: R0003. , ASB_OFF_LINE, the receipt printer is in use offline. ,no. (4) Thermal, R0004, Y, Y, N, receipt printer paper is insufficient, please inform the customer service staff to replace the paper roll, status code: R0004. , ASB_JOURNAL_NEAR_END_FIRST, the receipt printer paper is insufficient; please inform the counter to replace the paper roll. ,no. (5) Thermal, R0005, Y, Y, N, receipt printer paper is insufficient, please inform the customer service staff to replace the paper roll, status code: R0005. , ASB_RECEIPT_NEAR_END_FIRST, the receipt printer paper is insufficient; please inform the counter to replace the paper roll. ,no. (6) Thermal, R0006, Y, Y, N, receipt The printer paper roller cover is open, please inform the customer service staff, status code: R0006. , ASB_COVER_OPEN, the receipt printer platen roller cover is open; please inform the counter to close. ,no. (7) Thermal, R0007, Y, Y, N, receipt The printer paper roll is not installed, please inform the customer service staff, status code: R0007. , ASB_PLATEN_OPEN, the receipt printer press roller is open; please inform the counter to close. ,no. (8) Thermal, R0008, Y, N, Y, receipt printer idle. , custom, receipt printer idle. ,no.

The device state translation module 213 is configured to translate the actual state of the hardware device 27 obtained by the device state obtaining module 211 into a defined code specification. Since the state retrieved by the hardware device 27 is not a unified format, The code specification must be defined by re-translation to achieve the content of each device to facilitate the transfer and processing of the state. The instructions for defining the state translation of the hardware device are as follows: string[] ConvertStatusCode(object statusData);

The status code backhaul module 214 is configured to transmit the translated code specification, because the hardware device must return the translated preset normal status code/preset abnormal status code, and the hardware device returns to represent the normal status. An example of a status code/status code representing an exception status is as follows: string GetReadyCode(); string GetFailCode();

The compiling component generating module 215 generates a dynamic expansion component and a dynamic expansion configuration file corresponding to the dynamic expansion component according to the hardware device 27 inside the multimedia device 2, wherein the compiling component generating module 215 Converting the dynamic expansion component to the dynamic expansion configuration file using RSA asymmetric encryption;

The environment detecting module 216 is configured to detect whether the hardware device 27 inside the multimedia machine 2 can operate normally, because each device must be provided in a customized manner to let the device service unit 24 know whether the device is normal or not, and the detecting device Examples of instructions on whether the environment can function properly are as follows: bool CheckEnvironment();

The identification name definition module 217 is used to define a unique identification name of the hardware device inside the multimedia machine. Since the hardware device 27 must return the identification name representing the hardware device type, the instruction device uniquely identifies the name. As follows: string DeviceName();

In addition, after the device service unit 24 loads the corresponding dynamic expansion configuration file, the device status acquisition module 211 can obtain the status change notification of the hardware device 27, and execute the device through the initialization operation module 218. Initializing the operation, since the hardware device 27 is initialized, the normal execution operation can be started, and an example of the instruction for initializing the hardware device entity is as follows: void DeviceInit();

The description of the receipt printer is as follows: (1) Define the method for obtaining the status of the hardware device, mainly by communicating with the receipt device through the OPOS standard specification, and the instruction is as follows: object GetStatus( Params object[] parameters); (2) Define the method of hardware device state translation. The translation examples are as follows (the following is only the actual number of states according to each device definition): (a) 0x00000001 receipt printer does not have any response = > R0001 (b) 0x00000002 Receipt printer system error => R0003 (c) 0x00000010 Receipt printer offline use => R0005 (d) 0x00000080 receipt printer paper feed => R0008 and the command is as follows: string [] ConvertStatusCode(object statusData); (3) Whether the detection device can operate normally in the environment, mainly to check whether the driver is installed in the execution environment, and the instructions are as follows: bool CheckEnvironment();

The description of the ticket card machine is as follows: (1) Define the method of obtaining the state of the hardware device, mainly through the RS232 COM Port for sequence transmission, and analyze the message status according to the card machine specification. The command examples are as follows: Object GetStatus(params object[] parameters); (2) Define the method of hardware device state translation. The translation examples are as follows (the following is only the actual number of states defined by each device): (a) 80008381 card machine network line Exception => 0x80008381 (b) 80003539 device is undefined or not enabled => 0x80003539 (c) 81000913 authorized host connection failure => 0x81000913 (d) 82000104 transaction security module Reset failed => 0x82000104 and the command is as follows: string[] ConvertStatusCode(object statusData); (3) Whether the detection device is working properly in the environment, mainly to check whether the specified dynamic library exists, and the instructions are as follows: bool CheckEnvironment();

The component expansion implementation unit 22 is capable of setting a customization function for different hardware devices 27 inside the multimedia machine 2, and calling the corresponding hardware device 27 to execute the set customization function, except for the abstract definition. In addition, the component expansion unit 22 can perform the expansion of the custom function by means of the COM component calling method. The following is a description of the device parts of the printer and the ticket card machine: (1) Receipt printing table The COM expansion method (a) prints the text, and the command is as follows: (a1) [ComVisible(true)] (a2) public bool PrintText(string text); (b) Print the 2D barcode, and the command is as follows: (b1) [ComVisible(true)] (b2) public bool PrintQRCode(string text, long size, (b3) string alignment); (c) Cut the paper, and the command is as follows: (c1) [ComVisible(true)] ( C2) public bool CutPaper(long percentage); (2) Ticket card machine COM expansion method (a) Get the card basic information, and the command is as follows: (b1) [ComVisible(true)] (b2) public ResultObject GetCardData(); (b) Execution of the transaction (purchasing The cargo deduction/balance is refunded, and the instructions are as follows: (c1) [ComVisible(true)] (c2) public ResultObject DoTransaction(long price, long useAutoLoad); (c) Perform card registration, and the command is as follows: C1) [ComVisible(true)] (c2) public ResultObject SignOn();

The application container unit 23 is configured to provide environment execution files of different bits (x86 or x64 bits) required by different hardware devices, and the device service unit 24 is configured to be driven according to different hardware devices 27. The environment execution file required for execution is loaded to the corresponding dynamic expansion configuration file, so the device service unit 24 is mainly compiled by the dynamic library type, and can specify the operating system bit, such as: x86 Or referenced in an application written in x64 to provide operational use of the system execution phase container;

The photo printer and receipt printer are described as follows. Since the photo printer only provides x64 bit drive, and the receipt printer only provides x86 bit drive, the device service unit 24 has x64 and x86 execution. Different versions of the stage run in the same way, the details are as follows: (1) The dynamic expansion component (DLL) that has been abstracted to define the compiled output, such as: Photo Printer & Receipt Printer, its compiling component The output will be converted to a verified EXT file configuration file by an encryption tool using RSA asymmetric encryption; (2) The device service unit 24 will initially determine whether the current execution stage is x86 or x64. Then dynamically load the corresponding EXT configuration file according to the system settings, and verify the correctness of the configuration file, so as to increase the information security of the system side. The command examples are as follows: (a) DeviceService.dll => device service component (b) IDevice.dll => abstract definition component (c) x86DeviceService.exe => x86 execution phase container (d) CastlesReaderDevice.ext => ticket card machine dynamic expansion Status file (e) PhotoPrinterDevice.ext => Photo printer dynamic expansion configuration file (f) x64DeviceService.exe => x64 execution phase container (3) After loading, it will subscribe to the device status change notification and execute the device Initialize the job.

In addition, the device service unit 24 is further capable of receiving the code specification transmitted by the status code return module 214 and packaging it into a monitoring information file, and the multimedia machine 2 can transmit the monitoring information file to the cloud server 1.

The communication communication unit 25 is configured to communicate to a dynamic extended configuration file corresponding to different hardware devices for message transmission and/or reception, since the communication communication unit 25 is a component responsible for communication between the operating system and the application system. For example, the following functions are used for communication: (1) Send a message to the specified application (waiting for a response). The command is as follows: /// </summary> /// <param name="TargetApplicationName">Target application name </ Param> /// <param name="message">Message sent</param> /// <returns>Messages responded by the target application</returns> public string sendMessage(string TargetApplicationName, string message); (2) Send a message to the specified application (without waiting for a response), the command is as follows: /// </summary> /// <param name="TargetApplicationName">target application name</param> /// <param name= "message">Message sent</param> public void postMessage(string TargetApplicationName, string message) ; (3) Subscribe to the specified application Notifications, examples of instructions are as follows: /// </summary> /// <param name="TargetApplicationName">target application name</param> /// <param name="eventName">event name</param> / // <param name="action">Delegation method for event execution</param> /// <returns>Subscription success</returns> public bool SubscribeEvent(string TargetApplicationName, string eventName, EventHandler<PublishEventArgs> action) ;

The host application unit 26 is configured to perform an application operation, and transmits an instruction to the device service unit through the device service unit or the communication communication unit according to different application operations, and the corresponding service dynamic storage configuration file is loaded by the device service unit. To control the operation of different hardware devices to complete the application operations performed by the host application unit;

Take the implementation details of the Proxy proxy function call as an example to define which execution stage the specified command should be sent to, and return the execution result, as an example: /// <summary> /// Calling the specified device method / // </summary> /// <param name="info"></param> /// <returns></returns> public dynamic InvokeMember(DeviceActionInfo info, int timeout = 0) { info.ActionType = DeviceServiceAction. Action_InvokeMember; var str = API.JSON.JsonHelper.JsonSerializer(info); string result = string.Empty; if (dicDeviceServiceType.ContainsKey(info.DeviceName) == false) { return result; } else { switch (dicDeviceServiceType[info. DeviceName]) { case RuntimeType.x86: result = Windows.KioskWindow.CurrentWindow.Communication.sendMessage(TARGET_APPLICAT ION_NAME_X86, str); break; case RuntimeType.x64: if (timeout == 0) result = Windows.KioskWindow.CurrentWindow.Communication.sendMessage(TARGET_APPLICATION_NAME_X64, str); else result = Windows.KioskWindow.CurrentWindow.Communication.sendMessage(TARGET_APPLICATION_NAME_X64 , str, timeout); break; } return result; } }

Take the COM extension method and use the call of the Proxy proxy function to pass the call command to the corresponding execution stage container execution as an example. The following is an example: (1) Print text /// <summary> /// Print text /// </summary> /// <param name="text">Text Content</param> /// <returns>Execution Results</returns> public static bool PrintText(string text) { var result = Windows. KioskWindow.CurrentWindow.Device.InvokeMember(new DeviceActionInfo() { ActionType = DeviceManager.DeviceServiceAction.Action_InvokeMember, DeviceName = DeviceType.Thermal.ToString(), InvokeName = "PrintText", Parameters = new object[] { text } }); return API.JSON.JsonHelper.JsonDeserialize<bool>(result); } (2) Execute each ticket sign on action /// <summary> /// Execute each ticket sign on action. /// </summary> /// <returns> represents the data structure of the call result and the return value. </returns> public static ResultObject SignOn() { var result = Windows.KioskWindow.CurrentWindow.Device.InvokeMember(new DeviceActionInfo() { ActionType = DeviceManager.DeviceServiceAction.Action_InvokeMember, DeviceName = DeviceType.CastlesReader.ToString(), InvokeName = " SignOn", Parameters = new object[] { } }); return API.JSON.JsonHelper.JsonDeserialize<ResultObject>(result); }

The monitoring of the device service unit 24 will be logically processed according to the current process. The different states are processed as follows: (1) If the system is in the home page, the status inquiry is performed every 5 minutes, if the system has user operation. Entering the process will stop monitoring. (2) The status of the requested device will be recorded in the system. When the next inquiry is made, the difference will be compared. If there is a status change, the data will be returned to the background to save the cost of data transmission. (3) If the system has not changed the status for several hours, it will force a return. (4) Depending on the device, some devices have an active notification function for status change (eg, the cover of the receipt printer is open, paper is insufficient, etc.), and the device based on the architecture can notify the device of the active notification. The Kiosk application layer performs back-throwing, so when the system receives the active notification of the device change, it will judge whether it is currently in the home page, and if it is not in the home page, it will immediately report it.

If the user's operating system enters the service process, the system will get the status of the device that has been inquired within the last 5 minutes, and check according to the status code setting file. If there is an abnormal state, the system will immediately check the status of the device, otherwise it will directly enter Process.

The peripheral device integration system for multimedia machine provided by the present invention has the following advantages when compared with other conventional technologies: (1) The present invention develops a set of architectures, which allows system integration parties to face numerous heterogeneous devices. There is a simpler and faster way to solve the problem of expansion and status monitoring, while greatly reducing the burden of integration time. (2) The present invention can periodically perform status inquiry monitoring. However, if a user operating system enters the service process, the check will be performed before the final step is completed. The purpose of this mechanism is that the status change of the device may be temporary. In this way, the device can be inquired when the process is actually needed, reducing the time cost of the device inquiry (eg, the video device inquiry takes a long time, and the receipt printer status inquiry is relatively fast) . (3) The present invention has been disclosed above by the above embodiments, but it is not intended to limit the present invention. Those skilled in the art can understand the foregoing technical features and embodiments of the present invention without departing from the invention. In the spirit and scope of the present invention, the scope of the invention is to be determined by the appended claims.

1‧‧‧Cloud Server

2‧‧‧Multimedia machine

21‧‧‧Abstract interface definition unit

211‧‧‧Device Status Acquisition Module

212‧‧‧ Code Specification Storage Module

213‧‧‧Device Status Translation Module

214‧‧‧Status code return module

215‧‧‧Compiled component generation module

216‧‧‧Environmental Testing Module

217‧‧‧Recognition name definition module

218‧‧‧Initial operation module

22‧‧‧Component expansion implementation unit

23‧‧‧Application container unit

24‧‧‧Device Service Unit

25‧‧‧Communication communication unit

26‧‧‧Host Application Unit

27‧‧‧ hardware devices

[Fig. 1] is a schematic diagram showing the overall architecture of a peripheral device integration system for a multimedia machine of the present invention. [Fig. 2A] is a schematic structural view of a multimedia machine for the peripheral device integration system of the multimedia machine of the present invention. [Fig. 2B] is a schematic structural diagram of an abstract interface defining unit of the peripheral device integration system for a multimedia machine of the present invention.

Claims (4)

A peripheral device integration system for a multimedia machine includes: a cloud server; a plurality of multimedia machines connected to the cloud server, and the multimedia machine includes: an abstract interface defining unit, Obtaining the state of the hardware device in an abstract definition manner, the abstract interface defining unit includes at least: a device state obtaining module, which is configured to obtain the actual state of the hardware device inside the multimedia device by using a single interface; The specification storage module is configured to store at least one defined status code configuration file according to different hardware devices; a device status translation module is connected to the device status acquisition module and the code specification storage module. The actual state of the hardware device obtained by the device state acquisition module can be translated into a defined code specification; a state code return module is connected to the device state translation module for translation The code specification is transmitted; a compiling component generates a module for generating a dynamic expansion according to the hardware device inside the multimedia machine The component and a pair of dynamic expansion configuration files that should dynamically expand the component; an initialization operation module, which is used to define an operation mode of the hardware device inside the multimedia device after being turned on; The unit is capable of setting a customization function for different hardware devices inside the multimedia machine, and calling the corresponding hardware device to perform the set customization function; an application container unit for providing different hardware devices Environment execution file of different bits; a device service unit is connected to the application container unit, the abstract interface definition unit, and the component expansion implementation unit, and is configured to perform an environment execution file required for execution according to a driving environment required by different hardware devices. Corresponding dynamic expansion configuration file, and the device service unit is further capable of receiving the code specification transmitted by the status code return module and packaging the information as a monitoring information file, and the multimedia machine can transmit the monitoring information file to the a cloud server; wherein the device service unit loads the corresponding dynamic expansion configuration file, and the device state acquisition module capable of obtaining the hardware device through the abstract interface definition module can obtain the status change notification of the hardware device, and Module execution device initialization operation; a communication communication unit is connected to the device service unit for communicating to a dynamic expansion configuration file corresponding to different hardware devices for message transmission and/or reception; An application unit is connected to the device service unit and the communication communication unit, and the host application unit is used for Performing an application operation, and transmitting instructions to the device service unit through the device service unit or the communication communication unit according to different application operations, and loading the corresponding dynamic expansion configuration file by the device service unit to control different hardware device operations To complete the application operation performed by the host application unit. The device of claim 1, wherein the abstract interface defining unit further comprises an environment detecting module, wherein the environment detecting module is configured to detect whether the hardware device inside the multimedia device is It works properly. The peripheral device integration system for a multimedia machine according to claim 1, wherein the abstract interface definition unit further comprises an identification name definition module, wherein the identification name definition module is used to define a hardware inside the multimedia machine. The unique identifying name of the device. The peripheral device integration system for a multimedia machine according to claim 1, wherein the The compiled component generation module converts the dynamic expansion component into the dynamic expansion configuration file using RSA asymmetric encryption.