Intelligent battery data simulation transmission method and device, electronic equipment and storage medium

Abstract

The invention provides an intelligent battery data simulation transmission method and device, electronic equipment and a storage medium, relates to the technical field of battery data transmission, and is applied to a terminal, the terminal carries a Lunix system, the Lunix system carries an intelligent power management system, and the intelligent power management system comprises intelligent battery service and intelligent battery management. The voltameter uploads monitored battery state data by using an I2C bus simulated by a non-standard interface, and the intelligent battery service takes over the battery state data monitored by the voltameter by using a Power Supply interface; and the intelligent battery management uses an I2C bus simulated by a non-standard interface to read the battery state data monitored by the voltameter. In the Lunix system, the software capability of the intelligent battery management system is utilized, so that the I2C bus based on non-standard interface simulation is realized, the compatibility and flexibility of the system are improved, and the complexity and cost of system design are reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of transformer fault detection, and in particular to an intelligent battery data simulation transmission method and device, electronic equipment and a storage medium. BACKGROUND

[0002] With the popularity of mobile devices, the performance and management of the battery as its core power supply component become crucial. Traditional battery management systems usually use standard communication interfaces such as I2C, SMBus, etc. to interact with the host chip. However, in some specific hardware design or system integration, the battery power meter may use a non-standard interface for data transmission. This non-standard interface design makes it difficult for traditional battery management systems to directly compatible and efficiently process battery state data, thereby limiting the flexibility and data processing capability of the system.

[0003] In addition, the existing battery management system often needs additional hardware switching or complex software protocol conversion when processing non-standard interface data, which not only increases the hardware cost and system complexity, but also may introduce data transmission delay and instability. Therefore, how to design a method that can directly and efficiently process battery data transmitted by a non-standard interface and seamlessly integrate it into the existing intelligent power management system has become a technical problem to be solved. SUMMARY

[0004] Therefore, the purpose of the present application is to provide an intelligent battery data simulation transmission method, device, electronic equipment and storage medium to solve the above problems.

[0005] In a first aspect, the present application provides an intelligent battery data simulation transmission method, applied to a terminal, the terminal is equipped with a Lunix system, the Lunix system is equipped with an intelligent power management system, the intelligent power management system includes: an intelligent battery service and an intelligent battery management. The power meter is equipped with a non-standard interface, and the power meter is used to monitor the state data of the battery, and the method comprises: The power meter uploads the monitored battery state data to the I2C bus simulated by the non-standard interface; The intelligent battery service takes over the battery state data monitored by the power meter through the Power Supply interface; The intelligent battery management reads the battery state data monitored by the power meter through the I2C bus simulated by the non-standard interface.

[0006] The application realizes I2C bus simulation based on non-standard interface by using the software capability of the intelligent battery management system in the Lunix system, so that the system can process data of the non-standard interface like processing the standard I2C interface, improves the compatibility and flexibility of the system, and enables the terminal device to conveniently integrate various battery power meters using non-standard interfaces without hardware modification or additional hardware conversion chips, thereby reducing the complexity and cost of system design.

[0007] In a possible manner, the non-standard interface comprises one of a GPIO interface, a UR interface, a SPA interface or a CAN bus interface.

[0008] In a possible manner, the intelligent battery service is provided with a register sys node. The step of the intelligent battery service receiving the battery state data monitored by the power meter by using the I2C bus and the Power Supply comprises: The intelligent battery service writes the battery state data into the register sys node. The intelligent battery management calls the register sys node to read the battery state data monitored by the power meter by using the I2C bus simulated by the non-standard interface.

[0009] In a possible manner, the method further comprises: The intelligent battery service calls the register sys node to monitor the charging mode of the battery and whether the charging alarm information is generated. In response to the charging alarm information, it is determined whether the battery state data monitored by the power meter is accurate. If the battery state data monitored by the power meter is accurate, the charging alarm information is reported.

[0010] In a possible manner, the intelligent battery service is further used to convert the battery state data monitored by the power meter.

[0011] In a possible manner, the battery state data comprises at least one of battery power data, battery output voltage, battery output current and battery temperature.

[0012] In a possible manner, the charging alarm information is generated when the battery temperature exceeds a first threshold range or or the battery output voltage exceeds a second threshold range.

[0013] In a second aspect, the embodiments of the present application provide an intelligent battery data simulation transmission device, applied to a terminal, wherein the terminal is loaded with a Lunix system, the Lunix system is loaded with an intelligent power management system, and the intelligent power management system comprises an intelligent battery service and an intelligent battery management. The power gauge is loaded with a non-standard interface, the power gauge is used for monitoring state data of a battery, and the device comprises: An uploading module, configured to upload the monitored battery state data by the power gauge through the I2C bus simulated by the non-standard interface; A takeover module, configured to take over the battery state data monitored by the power gauge by the intelligent battery service through the Power Supply interface; A reading module, configured to read the battery state data monitored by the power gauge by the intelligent battery management through the I2C bus simulated by the non-standard interface.

[0014] In a third aspect, the embodiments of the present application provide an electronic device, comprising: at least one processor; and at least one memory in communication with the processor, wherein: the memory stores program instructions executable by the processor, and the processor invoking the program instructions can execute the method according to the first aspect.

[0015] In a fourth aspect, the embodiments of the present application provide a computer readable storage medium, which stores computer instructions, and the computer instructions make the computer execute the method according to the first aspect.

[0016] Other features and advantages of the present application will be described in the following description and, in part, will become apparent from the description or will be learned by practice of the present application. The objects and other advantages of the present application will be realized and achieved by the structure particularly pointed out in the description, claims and drawings.

[0017] In order to make the above objectives, characteristics and advantages of the present application more apparent and easy to understand, the following preferred embodiments are specifically described below, and the accompanying drawings are described in detail as follows. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to be used in the specific embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0019] Fig. 1A flow chart of an intelligent battery data simulation transmission method provided by an embodiment of the present application is shown in FIG. 1. Fig. 2 A structural diagram of an intelligent battery data simulation transmission device provided by an embodiment of the present application is shown in FIG. 2. Fig. 3 An electronic device structure provided by an embodiment of the present application is shown in FIG. 3. DETAILED DESCRIPTION

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be described below in detail with reference to the accompanying drawings. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of the present application.

[0021] With the popularity of mobile devices, the performance and management of the battery as the core power supply component become crucial. Traditional battery management systems usually use standard communication interfaces, such as I2C, SMBus, etc., to interact with the master chip for data. However, in some specific hardware designs or system integration, the battery power meter may use a non-standard interface for data transmission. This non-standard interface design makes it difficult for traditional battery management systems to directly compatible and efficiently process battery status data, thereby limiting the flexibility and data processing capability of the system.

[0022] In addition, existing battery management systems often require additional hardware switching or complex software protocol conversion when processing non-standard interface data, which not only increases hardware costs and system complexity, but also may introduce data transmission delay and instability. Therefore, how to design a method that can directly and efficiently process non-standard interface transmission of battery data and seamlessly integrate it into the existing intelligent power management system has become a technical problem to be solved.

[0023] To solve the above problems, the embodiments of the present application provide an intelligent battery data simulation transmission method, device, electronic device and storage medium, in order to solve the above problems.

[0024] First, the intelligent battery data simulation transmission method provided by the embodiments of the present application is described.

[0025] In the embodiments provided by the present application, the intelligent battery data simulation transmission method is applied to a terminal, which is equipped with a Lunix system, the Lunix system is equipped with an intelligent power management system, and the intelligent power management system includes an intelligent battery service and an intelligent battery management.

[0026] The Lunix system integrates an intelligent power management system, and the fuel gauge is used to monitor various battery status data in real time, such as voltage, current, temperature, and remaining charge. The fuel gauge uses a non-standard physical interface and cannot be directly recognized by the Lunix system.

[0027] In this application, S10 is executed first: the fuel gauge uploads the monitored battery status data using an I2C bus simulated by a non-standard interface.

[0028] Specifically, at the hardware level, in this application, the fuel gauge still uses its non-standard interface to connect to the main control chip, but at the software level, through programming, the signal output, timing control and data format of this non-standard interface are made to fully comply with the I2C bus communication protocol.

[0029] In this embodiment, the terminal's central processing unit (CPU) simulates the I2C master terminal.

[0030] Then, execute S20: The Smart Battery Service uses the Power Supply interface to take over the battery status data monitored by the fuel gauge.

[0031] It should be noted that the Smart Battery Service is a module within the Smart Power Management System, specifically responsible for processing data streams related to battery power supply. This module receives battery status data uploaded by the fuel gauge via the Power Supply interface. The Power Supply interface is a standard interface designed for power management in Linux systems. The Smart Battery Service uses this interface to parse simulated I2C bus data to ensure that the parsed data meets the format requirements for charging the terminal battery.

[0032] Finally, S30 is executed: Intelligent Battery Management uses a non-standard interface to simulate an I2C bus to read battery status data monitored by the fuel gauge.

[0033] In this terminal, the CPU is simulated as an I2C slave, so that the CPU responds passively.

[0034] Intelligent battery management is another module of the intelligent power management system. It is responsible for analyzing and managing battery status data, such as calculating remaining battery life, controlling charging, and providing overcharge and over-discharge protection. Intelligent battery management reads data already managed by the intelligent battery service via an I2C bus simulated using a non-standard interface. This reading process is also simulated in software, ensuring that intelligent battery management can process data from these non-standard interfaces as efficiently as it processes data from a standard I2C bus.

[0035] The application realizes I2C bus simulation based on a non-standard interface by using the software capability of the intelligent battery management system in the Lunix system, so that the system can process data of the non-standard interface as processing the standard I2C interface, improves the compatibility and flexibility of the system, and enables the terminal device to conveniently integrate various battery power meters using the non-standard interface without hardware modification or additional hardware conversion chips, thereby reducing the complexity and cost of system design.

[0036] In the present application, the non-standard interface includes one of a GPIO interface and a UR interface, an SPA interface, or a CAN bus interface.

[0037] In the present application, in order to realize battery state data, the intelligent battery service is provided with a register sys node, which is a virtual file system node for storing and managing device information in the Lunix operating system. In the present application, this node is used as a buffer and data exchange interface for battery state data.

[0038] The intelligent battery service first writes the battery state data into the register sys node, and then the intelligent battery management calls the register sys node to read the battery state data monitored by the power meter through the I2C bus simulated by the non-standard interface.

[0039] The present application separates the data writing and reading process by introducing the register sys node as a unified data interface, so that the intelligent battery service and the intelligent battery management module can independently and efficiently obtain battery data without directly interacting with the power meter, simplifying the software design and improving the stability and maintainability of the system.

[0040] As a preferred embodiment, the intelligent battery service calls the register sys node to monitor the charging mode of the battery and whether the charging alarm information is generated, and determines whether the battery state data monitored by the power meter is accurate in response to the charging alarm information.

[0041] Specifically, at this time, it is determined whether the battery state data monitored by the power meter has a jump, redundancy, etc., and if the battery state data monitored by the power meter is accurate, the charging alarm information is reported, at this time, the intelligent battery management can perform corresponding operation to eliminate the charging alarm information.

[0042] In an embodiment, at this time, the terminal interface displays the charging alarm information, at this time, the user performs corresponding operation to eliminate the charging alarm information.

[0043] For example, the charging alarm information is that the battery temperature is too high, at this time, the terminal interface informs the user to remove the charging socket to eliminate the charging alarm information.

[0044] or when the battery output voltage exceeds a second threshold range.

[0045] It should be noted that the first threshold range specifically refers to the threshold range of the battery temperature, and the second threshold range specifically refers to the threshold range of the battery output voltage, which can be set by the person skilled in the art according to the actual situation.

[0046] In some embodiments, the intelligent battery service is also used to convert the battery state data monitored on the power gauge to meet the data reading format requirements of intelligent battery management.

[0047] Specifically, since the battery state data reported by different power gauges may have inconsistent units (such as voltage units of volts or millivolts) or different formats (such as containing manufacturer-defined data fields or structures), the intelligent battery service is also used to convert and standardize these data, and adjust them to a unified data reading format that meets the regulations of intelligent battery management. This processing is based on pre-set conversion rules, such as unit conversion or mapping of custom format to standard format Here, the battery state data includes at least one of battery power data, battery output voltage, battery output current, and battery temperature.

[0048] On the basis of the foregoing embodiments, the embodiments of the present application provide an intelligent battery data simulation transmission device, the terminal, the terminal is equipped with Lunix system, the Lunix system is equipped with intelligent power management system, the intelligent power management system includes: intelligent battery service and intelligent battery management; The power gauge is equipped with a non-standard interface, and the power gauge is used to monitor the state data of the battery, and the device comprises: The uploading module is used for the power gauge to upload the monitored battery state data through the I2C bus simulated by the non-standard interface. The takeover module is used for the intelligent battery service to take over the battery state data monitored by the power gauge through the Power Supply interface. The reading module is used for the intelligent battery management to read the battery state data monitored by the power gauge through the I2C bus simulated by the non-standard interface.

[0049] The device provided by the embodiments of the present application has the same implementation principle and technical effects as the foregoing method embodiments. For brevity, the part of the device embodiment not mentioned in the foregoing method embodiments can be referred to the corresponding content in the foregoing method embodiments.

[0050] The computer program product of the second aspect can include a computer readable storage medium. The computer readable storage medium can include instructions. The instructions can include those that would cause a computer to implement a method according to the first aspect. The computer readable storage medium can be a volatile memory, a non-volatile memory, a solid-state memory, a magnetic memory, or an optical memory.

[0051] Fig. 3 A block diagram of an example electronic device suitable for use in implementing embodiments of the present application is shown. Fig. 3 The electronic device shown is merely one example. It should be understood, however, that the functionality of the embodiments of the present application is not limited to the electronic device shown.

[0052] As shown in Fig. 3 The electronic device is in the form of a general purpose computing device. Components of the electronic device can include, but are not limited to, one or more processors 410, a memory 430, and a communication bus 440 that couples various system components including the memory 430 and the processor 410.

[0053] The communication bus 440 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics bus (e.g., AGP or Accelerated Graphics Port bus), and a local bus using any of a variety of bus architectures (e.g., 6 9 9 Industry Standard Architecture (ISA), Micro Channel Architecture (MCA), Enhanced ISA (EISA), Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus).

[0054] Electronic devices typically include a variety of computer system readable media. These media can be any available media that is located either internally or externally to an electronic device, including volatile and non-volatile media, removable and non-removable media.

[0055] Memory 430 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) and / or cache memory. Electronic device can further include other removable / non-removable, volatile / non-volatile computer system storage media. Memory 430 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the application.

[0056] Program / utility, having a set (at least one) of program modules, can be stored in memory 430, for example, include an operating system, one or more application programs, other program modules, and program data, each or some combination thereof, can include implementation of a network environment. Program modules are generally carried in the memory of electronic device and implement the functions described in embodiments of the application.

[0057] Processor 410, through the operating system, executes various components of the application, and particularly component for performing the functions described in embodiments of the application. Figs. 1-3 The method provided by the embodiments shown.

[0058] The embodiments of the application provide a non-transitory computer readable storage medium, the non-transitory computer readable storage medium stores computer instructions, the computer instructions make the computer execute the method provided by the embodiments shown. Figs. 1-3 The method provided by the embodiments shown.

[0059] The computer readable storage medium can be implemented in any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium can be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0060] A computer readable signal medium can include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal can take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium can be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0061] Program code embodied on a computer readable medium can be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0062] Computer program code for carrying out operations of embodiments of the present application can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0063] The above description of specific embodiments of the present application has been presented for the purpose of illustration. Other embodiments are within the scope of the following claims. In some instances, the acts or steps recited in the claims can occur in a different order and still accomplish the desired results. Additionally, the process depicted in the accompanying figures does not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0064] In the description of embodiments of the present application reference has been made to descriptive terms, such as "one embodiment", "some embodiments", "an example", "a specific example" or "some examples" etc. which are intended to convey that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. The appearances of the phrases "in one embodiment", "in some embodiments", "an example", "a specific example" or "some examples" in various places in the specification are not necessarily referring to the same embodiment or example of the present application, and that they do not necessarily refer to any one embodiment or example. Furthermore, the particular features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples. Moreover, the different embodiments or examples described in the present application are not mutually exclusive, and combinations of features of different embodiments or examples can be made without departing from the scope of the present application.

[0065] Furthermore, the terms "first", "second", etc. are used herein only to describe different instances of an element, and do not imply or suggest relative importance or a number of instances of the elements. Thus, the features defined with "first", "second", etc. can include at least one of the features explicitly or implicitly. In the description of embodiments of the present application, the meaning of "a plurality" is at least two, such as two, three, etc., unless otherwise specifically limited.

[0066] Any processes or methods described in the flowcharts or elsewhere herein can be understood as representing one or more modules, segments, or portions of code that include executable instructions for performing specific logical functions or steps in the processes, and the various embodiments of the present application can include additional implementations in which additional, fewer, or none of the functions are performed, in different orders or in different manners, and that these claims should not be limited to the actions illustrated and described.

[0067] The word "if" can be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [a stated condition or event] is detected" can be interpreted to mean "upon determining" or "in response to determining" or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]," depending on the context.

[0068] It should be noted that the terminal involved in the embodiments of the present application can include, but is not limited to, a personal computer (PC), a personal digital assistant (PDA), a wireless handheld device, a tablet computer, a mobile phone, an MP3 player, an MP4 player, and the like.

[0069] In several embodiments provided by the embodiments of the present application, it should be understood that the disclosed system, device, and method can be implemented in other manners. For example, the embodiments of the device described above are merely schematic; for example, the division of the units is only a logical function division, and there can be another division manner in actual implementation; for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices, or units, and can be electrical, mechanical, or in other forms.

[0070] In addition, each function unit in the various embodiments of the embodiments of the present application can be integrated into one processor, or each unit can exist physically, or two or more units can be integrated into one unit. The integrated unit can be implemented in the form of hardware, or in the form of hardware plus software function units.

[0071] The integrated unit in the form of the software function unit can be stored in a computer readable storage medium. The software function unit is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute part of steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various storage medium capable of storing program codes.

[0072] The above merely describes preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for simulating data transmission from a smart battery, characterized in that, The device is applied to a terminal equipped with a Linux system, which in turn is equipped with an intelligent power management system, which includes intelligent battery service and intelligent battery management. The fuel gauge is equipped with a non-standard interface and is used to monitor battery status data. The method includes: The fuel gauge uses a non-standard interface to simulate an I2C bus to upload monitored battery status data. The intelligent battery service uses the Power Supply interface to take over the battery status data monitored by the fuel gauge; The intelligent battery management system uses a non-standard interface to simulate an I2C bus to read battery status data monitored by the fuel gauge.

2. The method according to claim 1, characterized in that, The non-standard interfaces include: GPIO interface and UR interface, SPA interface or CAN bus interface.

3. The method according to claim 2, characterized in that, The intelligent battery service is equipped with a register sys node; The steps of the intelligent battery service using the I2C bus to receive battery status data monitored by the fuel gauge from the power supply include: The intelligent battery service writes the battery status data to the register sys node; The intelligent battery management system calls the sys register node and uses a non-standard interface to simulate an I2C bus to read the battery status data monitored by the fuel gauge.

4. The method according to claim 3, characterized in that, The method further includes: The intelligent battery service calls the sys register node to monitor the battery's charging mode and whether charging alarm information is generated; In response to the charging alarm information, determine whether the battery status data monitored by the fuel gauge is accurate; If the battery status data monitored by the fuel gauge is accurate, it will be reported to the charging alarm information.

5. The method according to claim 4, characterized in that, The intelligent battery service is also used to convert the battery status data uploaded and monitored by the fuel gauge.

6. The method according to claim 4, characterized in that, The battery status data includes at least one of the following: battery power data, battery output voltage, battery output current, and battery temperature.

7. The method according to claim 4, characterized in that, The charging alarm information is generated when the battery temperature exceeds a first threshold range. or This is generated when the battery output voltage exceeds the second threshold range.

8. A smart battery data simulation transmission device, characterized in that, The device is applied to a terminal equipped with a Linux system, which in turn is equipped with an intelligent power management system, which includes intelligent battery service and intelligent battery management. The fuel gauge is equipped with a non-standard interface and is used to monitor battery status data. The device includes: Upload module: used by the fuel gauge to upload monitored battery status data via an I2C bus simulated using a non-standard interface; Takeover module: Used by the smart battery service to take over the battery status data monitored by the fuel gauge via the Power Supply interface; Reading module: Used for intelligent battery management, it reads battery status data monitored by the fuel gauge using a non-standard interface-simulated I2C bus.

9. An electronic device, characterized in that, include: At least one processor; as well as At least one memory communicatively connected to the processor, wherein: The memory stores program instructions that can be executed by the processor, which can invoke the program instructions to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause the computer to perform the method as described in any one of claims 1 to 7.

Images