Remote call monitoring method and device

Abstract

The invention discloses a method and a device for remotely calling monitoring, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: acquiring a preset interception strategy in a monitoring component; determining whether the interception strategy meets a framework calling rule of a remote calling system or not; if yes, calling a monitoring component to intercept the request information and / or response information corresponding to the request information by using an interception strategy; and when abnormal information exists in the intercepted request information and / or response information, prompting information is sent to a user by using a monitoring component. According to the embodiment, the monitoring component is used for acquiring the request information and / or the response information of each time in real time, when the request information and / or the response information are / is abnormal, the prompt information can be sent to the user in time, delayed troubleshooting does not need to be carried out according to the subsequently generated log information, and the abnormality troubleshooting efficiency is improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for remotely invoking monitoring. Background Technology

[0002] In existing remote procedure calls (RPCs), different services are typically invoked sequentially through various interfaces within a gateway to achieve a complete operational flow. For example, during a user order placement process, the system first needs to retrieve the item's inventory, then the order system generates the order, and subsequently, multiple systems such as the sorting, routing, and delivery systems are invoked to complete the item's delivery. When an anomaly occurs in a remote procedure call, current technologies typically rely on monitoring anomaly logs to identify the problematic step, the interface and system involved, and then manually investigate the anomaly. This approach suffers from high latency, lacks real-time alerts, and has low anomaly investigation efficiency. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a method and apparatus for remote call monitoring, which utilizes a monitoring component to obtain request information and / or response information in real time. When abnormalities occur in the request information and / or response information, prompt information can be sent to the user in a timely manner without the need for delayed investigation based on subsequently generated log information, thereby improving the efficiency of anomaly investigation.

[0004] To achieve the above objectives, according to one aspect of the present invention, a method for remotely invoking monitoring is provided.

[0005] A method for monitoring remote calls according to an embodiment of the present invention includes: obtaining a preset interception policy in a monitoring component; determining whether the interception policy satisfies the framework call rules of the remote call system; if so, invoking the monitoring component to intercept request information and / or response information corresponding to the request information using the interception policy; and when abnormal information exists in the intercepted request information and / or response information, sending a prompt message to the user using the monitoring component.

[0006] Optionally, invoking the monitoring component includes: determining the target invocation interface according to the interception policy; determining the target service required to invoke the monitoring component according to a pre-created directory file; and invoking the target service using the target invocation interface.

[0007] Optionally, after invoking the target service using the target invocation interface, the method further includes: adding at least two annotations to the target service and loading the target service using the annotations.

[0008] Optionally, the interception strategy includes intercepting based on a preset call duration; the step of calling the monitoring component to intercept request information and / or response information corresponding to the request information using the interception strategy includes: using reflection to call instance methods to obtain the first call time of the request information and the second call time of the response information respectively; and intercepting the request information and / or response information based on whether the difference between the first call time and the second call time is greater than the preset call duration.

[0009] Optionally, the interception strategy indicates the interception scenario and the corresponding target user; the step of sending a prompt message to the user using the monitoring component includes: sending a prompt message to the target user using the monitoring component according to the interception scenario.

[0010] Optionally, the remote invocation system is a page presentation technology framework; the target invocation interface is a filter extension point interface.

[0011] Optionally, obtaining the preset interception strategy in the monitoring component includes: obtaining the monitoring component using project management software or a static library.

[0012] To achieve the above objectives, according to another aspect of the present invention, a device for remotely invoking monitoring is provided.

[0013] An embodiment of the present invention provides a remote call monitoring device comprising: an acquisition module for acquiring a preset interception strategy in a monitoring component; a determination module for determining whether the interception strategy satisfies the framework call rules of the remote call system; an interception module for, if the interception strategy satisfies the framework call rules of the remote call system, invoking the monitoring component to intercept request information and / or response information corresponding to the request information using the interception strategy; and a prompting module for, when abnormal information exists in the intercepted request information and / or response information, sending a prompting message to the user using the monitoring component.

[0014] To achieve the above objectives, according to another aspect of the present invention, an electronic device for remotely invoking monitoring is provided.

[0015] An electronic device for remote call monitoring according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement a remote call monitoring method according to an embodiment of the present invention.

[0016] To achieve the above objectives, according to another aspect of the present invention, a computer-readable storage medium is provided.

[0017] An embodiment of the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein the program, when executed by a processor, implements a remote call monitoring method according to an embodiment of the present invention.

[0018] One embodiment of the above invention has the following advantages or beneficial effects: by using a monitoring component to obtain each request and / or response information in real time, when the request and / or response information is abnormal, a prompt message can be sent to the user in a timely manner, without the need for delayed investigation based on subsequently generated log information, thus improving the efficiency of anomaly investigation.

[0019] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0020] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0021] Figure 1 This is a schematic diagram of the main flow of the remote call monitoring method according to an embodiment of the present invention;

[0022] Figure 2 This is a schematic diagram of the main process of invoking the target service according to an embodiment of the present invention;

[0023] Figure 3 This is a flowchart illustrating a specific embodiment of the remote call monitoring method according to an embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of the process of calling the monitoring component to intercept according to an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the main modules of a remote monitoring device according to an embodiment of the present invention;

[0026] Figure 6 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0027] Figure 7 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0028] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0029] It should be noted that, unless otherwise specified, the embodiments of the present invention and the technical features thereof can be combined with each other.

[0030] It should be noted that the collection, gathering, updating, analysis, processing, use, transmission, and storage of user personal information involved in this disclosed technical solution all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0031] Figure 1 This is a schematic diagram of the main steps of a remote call monitoring method according to an embodiment of the present invention.

[0032] like Figure 1 As shown, the remote call monitoring method of this invention mainly includes the following steps:

[0033] Step S101: Obtain the preset interception policy in the monitoring component;

[0034] Step S102: Determine whether the interception strategy meets the framework invocation rules of the remote invocation system;

[0035] If yes, then proceed to steps S103 and S104; if no, then proceed to step S105.

[0036] Step S103: Invoke the monitoring component to intercept the request information and / or the response information corresponding to the request information using the interception strategy;

[0037] Step S104: When abnormal information is found in the intercepted request information and / or response information, a prompt message is sent to the user using the monitoring component;

[0038] Step S105: End the process.

[0039] The configuration information for the monitoring component is pre-configured through a configuration file, which can include various aspects such as interception strategies, API call strategies, and monitoring method call strategies. As a plugin, during user application, simply installing and loading the monitoring component allows access to its pre-configured configuration file and its corresponding functions. In an optional embodiment, step S101 obtains the monitoring component using project management software (e.g., Maven project object model) or a static library (e.g., LIB file format). The monitoring component introduced by this invention enables non-intrusive monitoring of anomalies, requiring no changes to the coding logic of the remote call system; simply referencing the compressed package of the monitoring component reduces coding and maintenance costs.

[0040] For step S102, the executable files and component types used by remote invocation systems of different frameworks may differ. Therefore, to ensure that the monitoring component can run smoothly in the remote invocation system, it is necessary to ensure that the interception strategy can meet the framework invocation rules of the remote invocation system. In an optional embodiment, the remote invocation system provided by this invention is a page presentation technology framework (i.e., JSF framework, JavaServer Faces framework). For remote invocation systems of different frameworks, the interception strategy in the monitoring component can be adaptively modified according to the framework invocation rules to ensure the smooth operation of the monitoring component.

[0041] For the calling procedure in step S103, in one optional embodiment, it can be as follows: Figure 2 As shown, it specifically includes:

[0042] Step S201: Determine the target API call based on the interception strategy;

[0043] Step S202: Determine the target service required to invoke the monitoring component based on the pre-created directory file;

[0044] Step S203: Use the target call interface to call the target service.

[0045] The directory file indicates the storage location and files of the target service; calling the directory file allows the target service to be invoked. Regarding the target invocation interface, remote invocation systems typically have multiple interfaces to correspond to different application scenarios; for example, interface 1 might be used to invoke application A, and interface 2 might be used to invoke application B. Therefore, when using external plugins for monitoring, it is preferable to use a specific interface to invoke the target service corresponding to the monitoring plugin, thus decoupling it from other business functions of the remote invocation system. For the JSF framework, there are reserved filter extension point interfaces; therefore, in an optional embodiment, the target invocation interface in this invention can be a filter extension point interface.

[0046] In a further optional embodiment, after invoking the target service, it is also necessary to load the target service. That is, after step S203, the method further includes: adding at least two annotations to the target service and loading the target service using the annotations. Specifically, for the JSF framework, in order to ensure successful loading, the annotations that need to be added are the AutoActive annotation and the Extensible annotation from Spring annotations. If these two annotations are not added, loading will fail.

[0047] The following is a specific embodiment illustrating the method for remote call monitoring, such as... Figure 3 As shown, it includes:

[0048] Step S301: Obtain the preset interception policy in the monitoring component;

[0049] Step S302: Execute the invoke method to determine whether the interception strategy meets the framework invocation rules of the remote invocation system;

[0050] If successful, it means that the interception strategy can meet the framework call rules of the remote call system, and continue to execute subsequent steps S303 to S308; otherwise, execute step S309: end the process;

[0051] Step S303: Determine the target call interface from the filter extension point interface according to the interception strategy;

[0052] Step S304: Determine the target service required to invoke the monitoring component based on the pre-created directory file;

[0053] For example, the file corresponding to the target service is called in a pre-created directory named services (which stores the target service).

[0054] Step S305: Invoke the target service using the target invocation interface;

[0055] Step S306: Add two annotations to the target service and load the target service using the annotations;

[0056] For example, the annotations are the AutoActive annotation and the Extensible annotation in Spring annotations.

[0057] Step S307: Using the target service, intercept the request information and / or the response information corresponding to the request information;

[0058] The request information includes the input parameters, interface name, interface method, and interface alias for each request; the response information includes the response values ​​returned by the external system for each request, including parameters returned normally or responses that are abnormal.

[0059] Step S308: When abnormal information is found in the intercepted request information and / or response information, a prompt message is sent to the user using the monitoring component.

[0060] Through the above process, the monitoring component can be used to obtain the request information and / or response information in real time. When the request information and / or response information is abnormal, the user can be promptly notified without delaying the investigation based on the subsequently generated log information, thus improving the efficiency of anomaly investigation.

[0061] Furthermore, the preset interception strategy in the monitoring component can include various interception information. In one optional embodiment, the interception strategy includes interception based on a preset call duration; that is, the process of calling the monitoring component in step S103 is as follows: Figure 4 As shown, it includes:

[0062] Step S401: Use reflection to call instance methods to obtain the first call time of the request information and the second call time of the response information respectively;

[0063] Step S402: Based on whether the difference between the first call time and the second call time is greater than the preset call duration, intercept the request information and / or response information.

[0064] For example, reflection-invoking instance methods can include the `beforeInvoke` and `afterInvoke` methods. The `beforeInvoke` method executes during the initialization process before program startup, taking the request information and a custom context as input parameters. The `afterInvoke` method executes after program startup, taking the response information, the custom context, and an action interface as input parameters. The action interface can be understood as the interface for the specific notification method to be sent to the user, such as email notification, WeChat notification, or phone notification. The `beforeInvoke` and `afterInvoke` methods can be used to obtain the first invocation time of the request information and the second invocation time of the response information, respectively, thereby determining the difference between the first and second invocation times.

[0065] In one optional embodiment, the aforementioned interception strategy can be stored in the `rule` directory of the target service file. It is understood that when other interception strategies need to be added as needed, the corresponding interception strategy files can also be stored in the same directory, with the file names adjusted appropriately.

[0066] In another optional embodiment, the interception strategy can also indicate the interception scenario and the corresponding target user. That is, under different interception scenarios, corresponding prompt information is sent to the specified target user. That is, the process of sending prompt information to the user using the monitoring component in step S104 includes: sending prompt information to the target user using the monitoring component according to the interception scenario.

[0067] According to the remote call monitoring method of the present invention, the monitoring component acquires the request information and / or response information of each request in real time. When the request information and / or response information is abnormal, the system can promptly send a prompt to the user without delaying the investigation based on the subsequently generated log information, thereby improving the efficiency of anomaly investigation.

[0068] Figure 5 This is a schematic diagram of the main modules of a remote monitoring device according to an embodiment of the present invention.

[0069] like Figure 5 As shown, the remote monitoring device 500 of this embodiment includes:

[0070] The acquisition module 501 is used to acquire the preset interception policies in the monitoring component;

[0071] The determining module 502 is used to determine whether the interception strategy meets the framework invocation rules of the remote invocation system;

[0072] The interception module 503 is used to call the monitoring component if the interception strategy meets the framework call rules of the remote call system, so as to use the interception strategy to intercept the request information and / or the response information corresponding to the request information.

[0073] The prompting module 504 is used to send a prompting message to the user when there is abnormal information in the intercepted request information and / or response information using the monitoring component.

[0074] In an optional embodiment of the present invention, the interception module 503 is further configured to: determine the target call interface according to the interception strategy; determine the target service required to call the monitoring component according to a pre-created directory file; and call the target service using the target call interface.

[0075] In an optional embodiment of the present invention, the interception module 503 is further configured to add at least two annotations to the target service after the target service is invoked using the target call interface, and load the target service using the annotations.

[0076] In an optional embodiment of the present invention, the interception strategy includes interception based on a preset call duration; the interception module 503 is further configured to obtain the first call time of the request information and the second call time of the response information respectively using a reflection call instance method; and to intercept the request information and / or response information based on whether the difference between the first call time and the second call time is greater than the preset call duration.

[0077] In an optional embodiment of the present invention, the interception strategy indicates the interception scenario and the corresponding target user; the prompting module 504 is further configured to send a prompt message to the target user using the monitoring component according to the interception scenario.

[0078] In an optional embodiment of the present invention, the remote invocation system is a page representation technology framework; the target invocation interface is a filter extension point interface.

[0079] In an optional embodiment of the present invention, the acquisition module 501 is further configured to acquire the monitoring component using project management software or a static library.

[0080] The remote call monitoring device according to embodiments of the present invention utilizes a monitoring component to acquire request information and / or response information in real time. When abnormalities occur in the request information and / or response information, it can promptly send a prompt message to the user without needing to perform delayed investigation based on subsequently generated log information, thereby improving the efficiency of anomaly investigation.

[0081] Figure 6 An exemplary system architecture 600 is shown, in which the remote call monitoring method or apparatus of embodiments of the present invention can be applied.

[0082] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing communication links between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0083] Users can use terminal devices 601, 602, and 603 to interact with server 605 via network 604 to receive or send data. Various communication client applications can be installed on terminal devices 601, 602, and 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, and social media platforms.

[0084] Terminal devices 601, 602, and 603 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0085] Server 605 can be a server that provides various services, such as a background management server that monitors remote call requests initiated by users using terminal devices 601, 602, and 603. The background management server can analyze and process data such as request information and / or response information, and feed back the processing results (such as prompt information) to the terminal devices.

[0086] It should be noted that the remote call monitoring method provided in this embodiment of the invention is generally executed by server 605, and correspondingly, the remote call monitoring device is generally set in server 605.

[0087] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0088] The following is for reference. Figure 7 It shows a schematic diagram of the structure of a computer system 700 suitable for implementing a terminal device of the present invention. Figure 7 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0089] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 702 or programs loaded from storage section 708 into random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the system 700. The CPU 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) first interface 705 is also connected to the bus 704.

[0090] The following components are connected to the I / O first interface 705: an input section 706 including a keyboard, mouse, etc.; an output section 707 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network first interface card such as a LAN card, modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O first interface 705 as needed. A removable medium 711, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 710 as needed so that computer programs read from it can be installed into the storage section 708 as needed.

[0091] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 709, and / or installed from removable medium 711. When the computer program is executed by central processing unit (CPU) 701, it performs the functions defined above in the system of this invention.

[0092] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0093] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0094] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including an acquisition module, a determination module, an interception module, and a notification module. The names of these modules do not necessarily limit the module itself; for example, the acquisition module can also be described as "a module for acquiring preset interception strategies in a monitoring component."

[0095] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to: acquire a preset interception policy in a monitoring component; determine whether the interception policy satisfies the framework invocation rules of the remote invocation system; if so, invoke the monitoring component to intercept request information and / or response information corresponding to the request information using the interception policy; and, when abnormal information exists in the intercepted request information and / or response information, send a prompt message to the user using the monitoring component.

[0096] According to the technical solution of the present invention, the monitoring component is used to obtain the request information and / or response information of each request in real time. When the request information and / or response information is abnormal, the prompt information can be sent to the user in a timely manner without the need for delayed investigation based on the subsequently generated log information, thereby improving the efficiency of anomaly investigation.

[0097] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for remotely invoking monitoring, characterized in that, Applications include remote invocation systems, including: Retrieve the preset interception policies in the monitoring component; Determine whether the interception strategy meets the framework invocation rules of the remote invocation system; If so, the monitoring component is invoked to intercept the request information and / or the response information corresponding to the request information using the interception strategy; If any abnormal information is found in the intercepted request and / or response information, the monitoring component will be used to send a notification to the user.

2. The method according to claim 1, characterized in that, The invocation of the monitoring component includes: The target calling interface is determined according to the interception strategy; The target service required to invoke the monitoring component is determined based on the pre-created directory file; The target service is invoked using the target invocation interface.

3. The method according to claim 2, characterized in that, After invoking the target service using the target invocation interface, the method further includes: Add at least two annotations to the target service, and load the target service using the annotations.

4. The method according to claim 1, characterized in that, The interception strategy includes interception based on a preset call duration; The invocation of the monitoring component to intercept request information and / or corresponding response information using the interception strategy includes: Use reflection to invoke instance methods to obtain the first invocation time of the request information and the second invocation time of the response information, respectively. Based on whether the difference between the first call time and the second call time is greater than the preset call duration, the request information and / or response information are intercepted.

5. The method according to claim 1, characterized in that, The interception strategy specifies the interception scenario and the corresponding target user; the step of sending a notification message to the user using the monitoring component includes: Based on the interception scenario, the monitoring component is used to send a notification message to the target user.

6. The method according to claim 1, characterized in that, The remote invocation system is a page presentation technology framework; the target invocation interface is a filter extension point interface.

7. The method according to claim 1, characterized in that, The preset interception strategy in the monitoring component includes: The monitoring components can be obtained using project management software or static libraries.

8. A device for remotely invoking monitoring, characterized in that, include: The acquisition module is used to acquire the preset interception policies in the monitoring components; The determination module is used to determine whether the interception strategy meets the framework invocation rules of the remote invocation system; An interception module is used to invoke the monitoring component if the interception strategy meets the framework invocation rules of the remote invocation system, so as to use the interception strategy to intercept the request information and / or the response information corresponding to the request information. The alert module is used to send alert information to the user when abnormal information is found in the intercepted request information and / or response information, using the monitoring component.

9. An electronic device for remotely invoking monitoring, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-7.

10. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-7.

Images