CN113792014A

Movatterモバイル変換

Info

Publication number: CN113792014A
Application number: CN202110897037.9A
Authority: CN
Inventors: 郭炳杰; 阳立; 刘文可; 柯婧; 刘晖
Original assignee: China General Nuclear Power Corp; CGN Power Co Ltd; Daya Bay Nuclear Power Operations and Management Co Ltd; Lingdong Nuclear Power Co Ltd; Guangdong Nuclear Power Joint Venture Co Ltd; Lingao Nuclear Power Co Ltd
Current assignee: China General Nuclear Power Corp; CGN Power Co Ltd; Daya Bay Nuclear Power Operations and Management Co Ltd; Lingdong Nuclear Power Co Ltd; Guangdong Nuclear Power Joint Venture Co Ltd; Lingao Nuclear Power Co Ltd
Priority date: 2021-08-05
Filing date: 2021-08-05
Publication date: 2021-12-14
Anticipated expiration: 2041-08-05
Also published as: CN113792014B

Abstract

Translated fromChinese

本申请适用于核电站信息化建设技术领域，提供了一种核电站文件管理方法、装置、终端设备及存储介质。本申请实施例中获取点击指令，根据所述点击指令确定目标文件的文件类型；当所述文件类型为第一预设类型时，将所述目标文件的目标文件信息发送至SAP系统，以使所述SAP系统根据所述目标文件信息中的第一文件地址确定所述目标文件是否存储于预设文件服务器；若所述目标文件存储于所述文件服务器中，则接收所述目标文件在所述文件服务器中的第二文件地址，并根据所述第二文件地址向所述文件服务器发送请求信息；接收所述文件服务器根据所述请求信息发送的所述目标文件，从而提高了核电站的文件管理效率。

The present application is applicable to the technical field of nuclear power plant information construction, and provides a nuclear power plant file management method, device, terminal equipment and storage medium. In the embodiment of the present application, a click instruction is obtained, and the file type of the target file is determined according to the click instruction; when the file type is the first preset type, the target file information of the target file is sent to the SAP system, so that the The SAP system determines whether the target file is stored in the preset file server according to the first file address in the target file information; if the target file is stored in the file server, the target file is received in the the second file address in the file server, and send request information to the file server according to the second file address; management efficiency.

Description

Nuclear power station file management method and device, terminal equipment and storage medium

Technical Field

The application belongs to the technical field of nuclear power station informatization construction, and particularly relates to a nuclear power station file management method and device, terminal equipment and a storage medium.

Background

With the development of enterprise informatization, the requirements of people on the operation interface and the operation experience of the system are gradually improved, and the SAP GUI interface is designed based on the adoption of a traditional client interface, and the process design and the function design are integrated with the enterprise management experience of all countries and all industries around the world, so that the SAP system plays an increasingly important role in the aspect of service management of the nuclear power station.

However, since the SAP system stores a large amount of files, people need to perform file migration with a large workload when interacting with the SAP system by using the WEB server to perform corresponding management work. And the SAP system and the WEB server are mutually independent, so that the management efficiency is low when the file management related to the nuclear power station is carried out.

Disclosure of Invention

The embodiment of the application provides a nuclear power station file management method and device, terminal equipment and a storage medium, and can solve the problem of low file management efficiency of a nuclear power station.

In a first aspect, an embodiment of the present application provides a nuclear power plant file management method, which is applied to a WEB server, and includes:

acquiring a click instruction, and determining the file type of a target file according to the click instruction;

when the file type is a first preset type, sending target file information of the target file to an SAP (system application protocol) system so that the SAP system determines whether the target file is stored in a preset file server or not according to a first file address in the target file information;

if the target file is stored in the file server, receiving a second file address of the target file in the file server, and sending request information to the file server according to the second file address;

and receiving the target file sent by the file server according to the request information.

In one embodiment, after determining the file type of the target file according to the click command, the method includes:

when the file type is a second preset type, sending a second file address of the target file to the file server;

and receiving the target file sent by the file server according to the second file address.

In an embodiment, the determining the file type of the target file according to the click command includes:

and determining the file type of the target file in a preset notice according to the click command.

In one embodiment, before obtaining the click command, the method includes:

acquiring a file to be stored, and storing the file to be stored in the file server;

receiving a second file address of the file to be stored, which is sent by the file server;

and saving the second file address of the file to be stored into the notice, and sending the notice to the SAP system.

In one embodiment, request file information of a request file sent by the SAP system is received; determining whether the request file is stored in the file server according to a second file address in the request file information; and if the request file is not stored in the file server, uploading the request file to the file server so that the file server sends the request file to the SAP system.

In a second aspect, an embodiment of the present application provides a nuclear power plant file management method, which is applied to an SAP system, and includes:

when the file type is a second preset type, sending target file information of the target file to a WEB service end so that the WEB service end determines whether the target file is stored in a preset file server according to a second file address in the target file information;

and if the target file is stored in the file server, receiving the target file sent by the file server according to the second file address.

In one embodiment, request file information of a request file sent by the WEB service terminal is received; determining whether the request file is stored in the file server according to a first file address in the request file information; and if the request file is not stored in the file server, uploading the request file to the file server so that the file server sends the request file to the WEB server.

In a third aspect, an embodiment of the present application provides a nuclear power plant file management apparatus, including:

the acquisition module is used for acquiring a click command and determining the file type of the target file according to the click command;

the type determining module is used for sending the target file information of the target file to an SAP system when the file type is a first preset type so that the SAP system can determine whether the target file is stored in a preset file server according to a first file address in the target file information;

an address receiving module, configured to receive a second file address of the target file in the file server if the target file is stored in the file server, and send request information to the file server according to the second file address;

and the file receiving module is used for receiving the target file sent by the file server according to the request information.

In a fourth aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements any of the steps of the nuclear power plant file management method when executing the computer program.

In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the steps of any one of the nuclear power plant file management methods.

In a sixth aspect, an embodiment of the present application provides a computer program product, which, when running on a terminal device, causes the terminal device to execute any one of the nuclear power plant file management methods in the first aspect.

In the embodiment of the application, a click instruction is obtained, and a file type of a target file is determined according to the click instruction, so that which end the target file required by a current user is stored at is determined, and when the file type is a first preset type, the target file is stored in an SAP system, so that target file information of the target file is sent to the SAP system, and the SAP system determines whether the target file is stored in a preset file server according to a first file address in the target file information, so that the target file is sent to a WEB service end through the file server. And if the target file is stored in the file server, receiving a second file address of the target file in the file server, sending request information to the file server according to the second file address so that the file server feeds back the target file, and further receiving the target file sent by the file server according to the request information, so that file interaction between a WEB server and an SAP system is realized through the file server, and the file management efficiency of the nuclear power station is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

Fig. 1 is a first flowchart of a file management method for a nuclear power plant according to an embodiment of the present application;

FIG. 2 is a second flowchart of a nuclear power plant file management method according to an embodiment of the present disclosure;

FIG. 3 is a third flowchart illustrating a nuclear power plant file management method according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of a first structure of a nuclear power plant file management apparatus according to an embodiment of the present application;

FIG. 5 is a second schematic structural diagram of a file management apparatus of a nuclear power plant according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Example one

Fig. 1 is a schematic flowchart of a nuclear power plant file management method in an embodiment of the present application, where an execution subject of the method may be a terminal device, for example, a WEB server, and as shown in fig. 1, the nuclear power plant file management method may include the following steps:

step S101, obtaining a click command, and determining the file type of the target file according to the click command.

In this embodiment, a WEB service obtains a click instruction generated by a user clicking a target file required by the user on a display interface of the WEB service, and the WEB service determines a file type of the target file in a preset notice according to the click instruction, and determines a storage location of the target file according to the obtained file type of the target file because file types corresponding to different storage paths of the file are different, thereby triggering different file obtaining mechanisms, that is, obtaining the target file from the corresponding storage location, so as to meet a document query requirement of the user on the premise of not performing all document migration. In this embodiment, the target file is a file that is required when a user operates a WEB server.

Exemplarily, if the target file is a file stored by a WEB server, the file type of the target file is a URL type, and corresponds to a URL address of the target file; and if the target file is a file stored by the SAP system, the file type of the target file is a KEY type and corresponds to the KEY information of the target file.

In one embodiment, before obtaining the click command, the method may include: the method comprises the steps that a WEB server acquires a current file to be stored, stores the file to be stored in a file server, and accordingly receives a URL (uniform resource locator) address (second file address) of the file to be stored sent by the file server, namely a storage address of the file to be stored in the file server. And the WEB service end saves the second file address of the file to be stored into the notice, so that when the user operates the target file required by the user at the WEB service end, the storage address of the target file can be determined according to the notice. And the WEB server side simultaneously sends the notice to the SAP system, so that when a user operates a target file required by the user at the SAP system, the storage address of the target file can be determined according to the notice. The file server may adopt an FTP document server.

Step S102, when the file type is a first preset type, sending the target file information of the target file to an SAP system, so that the SAP system determines whether the target file is stored in a preset file server according to a first file address in the target file information.

In this embodiment, if the file type is a first preset type, which indicates that the target file is a file stored by an SAP system, the WEB server sends target file information of the target file including KEY information (a first file address) to the SAP system, so that the SAP system determines whether the target file is stored in a preset file server according to the first file address, and if the target file is not stored in the file server, the target file in the SAP system is uploaded to the file server through a webserver technology, and a corresponding URL address (a second file address) is generated, so that the WEB server obtains the target file required by the user from the file server according to the generated second file address, and thus, the file required by the user is gradually uploaded to the file server, so as to improve the document management efficiency.

Step S103, if the target file is stored in the file server, receiving a second file address of the target file in the file server, and sending request information to the file server according to the second file address.

In this embodiment, if the SAP system determines that the target file is stored in the file server, the second file address corresponding to the target file is sent to the WEB server, so that the WEB server analyzes the second file address by using the JS technology, identifies the target file as a file stored by the WEB server, changes the file type to the URL type, and sends request information to the file server according to the second file address of the target file, so that the file server downloads the target file corresponding to the request information to the WEB server according to the request information.

Step S104, receiving the target file sent by the file server according to the request information.

In one embodiment, after step S101, the method includes: when the file type is a second preset type, the target file is a file stored by the WEB server and is uploaded to the file server, the WEB server sends a second file address of the target file to the file server, and the target file corresponding to the second file address is downloaded to the WEB server by calling the file server, so that the WEB server receives the target file sent by the file server.

In an embodiment, as shown in fig. 2, if a current user operates the SAP system and a file required by the user is stored in a WEB server, the nuclear power plant file management method may further include:

step S201, receiving the request file information of the request file sent by the SAP system.

Step S202, determining whether the requested file is stored in the file server according to the second file address in the requested file information.

Step S203, if the request file is not stored in the file server, uploading the request file to the file server, so that the file server sends the request file to the SAP system.

In this embodiment, when the WEB server receives the request file information of the request file sent by the user operating the SAP system, it indicates that the request file required by the user is a file stored by the WEB server, so the WEB server needs to determine that the request file is stored in the file server according to a URL address (a second file address) corresponding to the request file, and send the request file to the SAP system through the file server. In this embodiment, the request file is a file that is required when a user operates the SAP system.

Example two

Fig. 3 is a schematic flowchart of a nuclear power plant file management method in an embodiment of the present application, where an execution subject of the method may be an SAP system, and as shown in fig. 3, the nuclear power plant file management method may include the following steps:

step S301, obtaining a click command, and determining the file type of the target file according to the click command.

In this embodiment, the SAP system obtains a click instruction generated by a user clicking a target file required by the user on a display interface of the SAP system, determines a file type of the target file in a preset notice according to the click instruction, and determines a storage location of the target file according to the obtained file type of the target file because the file types corresponding to different storage paths of the file are different, thereby obtaining the target file. In this embodiment, the target file is a file required by a user when operating the SAP system.

Step S302, when the file type is a second preset type, sending the target file information of the target file to a WEB service end, so that the WEB service end determines whether the target file is stored in a preset file server according to a second file address in the target file information.

In this embodiment, if the file type is a second preset type, which indicates that the target file is a file stored by the WEB server, the SAP system sends target file information of the target file including a URL address (a second file address) to the WEB server, so that the WEB server determines whether the target file is stored in a preset file server according to the second file address, and if the target file is not stored in the file server, uploads the target file in the WEB server to the file server, so that the SAP system obtains the target file required by the user from the file server according to the second file address.

Step S303, if the target file is stored in the file server, receiving the target file sent by the file server according to the second file address.

In this embodiment, if the WEB server determines that the target file is stored in the file server, the WEB server sends request information to the file server according to a second file address of the target file, so that the file server downloads the target file corresponding to the request information to the SAP system according to the request information.

In an embodiment, if a current user operates a WEB service and a file required by the user is stored in the SAP system, the nuclear power plant file management method may further include: the SAP system receives request file information of a request file sent by a user operating the WEB server, and indicates that the request file required by the user is a file stored by the SAP system, so the SAP system needs to determine whether the request file is stored in the file server according to KEY information (a first file address) corresponding to the request file, and if the request file is not stored in the file server, the SAP system uploads the request file to the file server so that the file server sends the request file to the WEB server. In this embodiment, the request file is a file that is required when a user operates a WEB server.

In the embodiment of the application, a click instruction is obtained, a file type of a target file is determined according to the click instruction, so that which end the target file required by a current user is stored at is determined, and when the file type is a second preset type, the target file is stored in a WEB server, so that target file information of the target file is sent to the WEB server, so that the WEB server determines whether the target file is stored in a preset file server according to a second file address in the target file information, and the target file is sent to an SAP system through the file server. And if the target file is stored in the file server, receiving the target file sent by the file server according to the second file address, so that file interaction between the WEB server and the SAP system is realized through the file server, and the file management efficiency of the nuclear power station is improved.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

EXAMPLE III

Corresponding to the first nuclear power plant file management method in the foregoing embodiment, fig. 4 is a schematic structural diagram of a nuclear power plant file management apparatus in the embodiment of the present application, and as shown in fig. 4, the nuclear power plant file management apparatus may include:

the obtainingmodule 401 is configured to obtain a click instruction, and determine a file type of the target file according to the click instruction.

Atype determining module 402, configured to send, when the file type is a first preset type, target file information of the target file to an SAP system, so that the SAP system determines, according to a first file address in the target file information, whether the target file is stored in a preset file server.

Anaddress receiving module 403, configured to receive a second file address of the target file in the file server if the target file is stored in the file server, and send request information to the file server according to the second file address.

Afile receiving module 404, configured to receive the target file sent by the file server according to the request message.

In an embodiment, the nuclear power plant file management apparatus may further include:

and the address sending module is used for sending the second file address of the target file to the file server when the file type is a second preset type.

And the first receiving module is used for receiving the target file sent by the file server according to the second file address.

In one embodiment, the obtaining module may include:

and the type determining unit is used for determining the file type of the target file in a preset notice according to the click command.

the first storage module is used for acquiring a file to be stored and storing the file to be stored in the file server.

And the second receiving module is used for receiving a second file address of the file to be stored, which is sent by the file server.

And the notice sending module is used for saving the second file address of the file to be stored into the notice and sending the notice to the SAP system.

and the information receiving module is used for receiving the request file information of the request file sent by the SAP system.

And the second storage module is used for determining whether the request file is stored in the file server according to a second file address in the request file information.

A first file uploading module, configured to upload the request file to the file server if the request file is not stored in the file server, so that the file server sends the request file to the SAP system.

Example four

Corresponding to the second embodiment of the file management method for a nuclear power plant, fig. 5 is a schematic structural diagram of a file management apparatus for a nuclear power plant in the embodiment of the present application, and as shown in fig. 5, the file management apparatus for a nuclear power plant may include:

thefile determining module 501 is configured to obtain a click instruction, and determine a file type of the target file according to the click instruction.

Thefile storage module 502 is configured to, when the file type is a second preset type, send target file information of the target file to a WEB server, so that the WEB server determines whether the target file is stored in a preset file server according to a second file address in the target file information.

An objectfile receiving module 503, configured to receive the object file sent by the file server according to the second file address if the object file is stored in the file server.

and the third receiving module is used for receiving the request file information of the request file sent by the WEB service end.

And the third storage module is used for determining whether the request file is stored in the file server according to the first file address in the request file information.

And the second file uploading module is used for uploading the request file to the file server if the request file is not stored in the file server, so that the file server sends the request file to the WEB server.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the apparatus and the module described above may refer to corresponding processes in the foregoing system embodiments and method embodiments, and are not described herein again.

EXAMPLE five

Fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present application. For convenience of explanation, only portions related to the embodiments of the present application are shown.

As shown in fig. 6, theterminal device 6 of this embodiment includes: at least one processor 600 (only one shown in fig. 6), a memory 601 connected to theprocessor 600, and acomputer program 602, such as a nuclear power plant file management program, stored in the memory 601 and operable on the at least oneprocessor 600. Theprocessor 600 executes thecomputer program 602 to implement the steps in the above embodiments of the nuclear power plant file management method, such as the steps S101 to S104 shown in fig. 1. Alternatively, theprocessor 600 executes thecomputer program 602 to implement the functions of the modules in the device embodiments, such as themodules 401 to 404 shown in fig. 4.

Illustratively, thecomputer program 602 may be divided into one or more modules, and the one or more modules are stored in the memory 601 and executed by theprocessor 600 to complete the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of thecomputer program 602 in theterminal device 6. For example, thecomputer program 602 may be divided into the obtainingmodule 401, thetype determining module 402, theaddress receiving module 403, and thefile receiving module 404, and the specific functions of the modules are as follows:

an obtainingmodule 401, configured to obtain a click instruction, and determine a file type of a target file according to the click instruction;

atype determining module 402, configured to send target file information of the target file to an SAP system when the file type is a first preset type, so that the SAP system determines whether the target file is stored in a preset file server according to a first file address in the target file information;

anaddress receiving module 403, configured to receive a second file address of the target file in the file server if the target file is stored in the file server, and send request information to the file server according to the second file address;

Theterminal device 6 may include, but is not limited to, aprocessor 600 and a memory 601. Those skilled in the art will appreciate that fig. 6 is merely an example of theterminal device 6, and does not constitute a limitation to theterminal device 6, and may include more or less components than those shown, or combine some components, or different components, such as an input-output device, a network access device, a bus, etc.

TheProcessor 600 may be a Central Processing Unit (CPU), and theProcessor 600 may be other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, a discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The storage 601 may be an internal storage unit of theterminal device 6, such as a hard disk or a memory of theterminal device 6 in some embodiments. In other embodiments, the memory 601 may also be an external storage device of theterminal device 6, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on theterminal device 6. Further, the memory 601 may include both an internal storage unit and an external storage device of theterminal device 6. The memory 601 is used for storing an operating system, an application program, a Boot Loader (Boot Loader), data, and other programs, such as program codes of the computer programs. The memory 601 described above may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the above modules or units is only one logical function division, and there may be other division manners in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. The computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file or some intermediate form. The computer-readable medium may include at least: any entity or device capable of carrying computer program code to a photographing apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.