WO2019091023A1 - 影像文件上传方法、服务器及可读存储介质 - Google Patents

影像文件上传方法、服务器及可读存储介质 Download PDF

Info

Publication number
WO2019091023A1
WO2019091023A1 PCT/CN2018/077621 CN2018077621W WO2019091023A1 WO 2019091023 A1 WO2019091023 A1 WO 2019091023A1 CN 2018077621 W CN2018077621 W CN 2018077621W WO 2019091023 A1 WO2019091023 A1 WO 2019091023A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
database
image file
service system
writing
Prior art date
Application number
PCT/CN2018/077621
Other languages
English (en)
French (fr)
Inventor
罗国强
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019091023A1 publication Critical patent/WO2019091023A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/50—Information retrieval; Database structures therefor; File system structures therefor of still image data
    • G06F16/51—Indexing; Data structures therefor; Storage structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101—Access control lists [ACL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • the present application relates to the field of computer technologies, and in particular, to an image file uploading method, a server, and a readable storage medium.
  • the purpose of the application is to provide an image file uploading method, a server and a readable storage medium, aiming at reducing the concurrent pressure and improving the system availability.
  • the first aspect of the present application provides an image file uploading server, where the image file uploading server includes a memory and a processor, and the memory stores an image file uploading system executable on the processor.
  • the image file uploading system is executed by the processor, the following steps are implemented:
  • the database read/write module determines whether the user of the service system has access rights according to the user access right information pre-stored in the memory;
  • the database read/write module determines the database and the hard disk corresponding to the user of the service system according to the correspondence between the user pre-stored in the memory and the database and the hard disk, and determines the determined The hard disk is notified to the file reading and writing module;
  • the file reading and writing module writes an image file of the user of the business system into the hard disk notified by the database read/write module;
  • the database reading and writing module After the file reading and writing module is successfully written, the database reading and writing module writes the current uploading information into a database corresponding to the user of the service system.
  • the second aspect of the present application further provides an image file uploading method, which is applied to an image file uploading server, and the method includes:
  • the database read/write module determines whether the user of the service system has access rights according to the user access right information pre-stored in the memory;
  • the database read/write module determines the database and the hard disk corresponding to the user of the service system according to the correspondence between the user pre-stored in the memory and the database and the hard disk, and determines the determined The hard disk is notified to the file reading and writing module;
  • the file reading and writing module writes an image file of the user of the business system into the hard disk notified by the database read/write module;
  • the database reading and writing module After the file reading and writing module is successfully written, the database reading and writing module writes the current uploading information into a database corresponding to the user of the service system.
  • a third aspect of the present application further provides a computer readable storage medium storing an image file uploading system, where the image file uploading system is executable by at least one processor So that the at least one processor performs the steps of the image file uploading method as described above.
  • the image file uploading method, system and readable storage medium proposed by the present application separate the database access from the file reading and writing service in the image file uploading server, and receive the image file uploading request sent by the user of the service system when the database file is read.
  • the writing module determines, according to the user access right information pre-stored in the memory, whether the user of the business system has access rights, and when the user of the business system has the access right, the database reading and writing module is based on the user and the database and the hard disk pre-stored in the memory.
  • determining a database and a hard disk corresponding to the user of the service system determining a database and a hard disk corresponding to the user of the service system, and notifying the determined hard disk to the file reading and writing module, wherein the file reading and writing module writes the image file of the user of the service system
  • the hard disk is notified by the database reading and writing module; after the file reading and writing module is successfully written, the database reading and writing module writes the current uploading information into a database corresponding to the user of the service system, thereby avoiding Frequently initiated query requests to the primary database, reducing the pressure on concurrency Improve system availability.
  • the number of databases and hard drives can be flexibly expanded as needed.
  • FIG. 1 is a schematic diagram of an operating environment of a preferred embodiment of an image file uploading system 10 of the present application;
  • FIG. 2 is a schematic diagram of an application environment of a plurality of service systems in an embodiment of the image file uploading system 10 of the present application;
  • FIG. 3 is a schematic flowchart of an embodiment of an image file uploading method of the present application.
  • FIG. 1 is a schematic diagram of an operating environment of a preferred embodiment of the image file uploading system 10 of the present application.
  • the image file uploading system 10 is installed and runs in the image file uploading server 1.
  • the image file upload server 1 may include, but is not limited to, the memory 11, the processor 12, and the display 13.
  • Figure 1 shows only server 1 with components 11-13, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the memory 11 is at least one type of readable computer storage medium, which in some embodiments may be an internal storage unit of the server 1, such as the hard disk or memory of the server 1.
  • the memory 11 may also be an external storage device of the server 1 in other embodiments, such as a plug-in hard disk equipped on the server 1, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) cards, flash cards, etc. Further, the memory 11 may also include both an internal storage unit of the server 1 and an external storage device.
  • the memory 11 is configured to store application software and various types of data installed in the server 1, such as program code of the image file uploading system 10. The memory 11 can also be used to temporarily store data that has been output or is about to be output.
  • the processor 12 in some embodiments, may be a central processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 11, for example
  • CPU central processing unit
  • microprocessor or other data processing chip for running program code or processing data stored in the memory 11, for example
  • the image file uploading system 10 and the like are executed.
  • the display 13 in some embodiments may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch sensor, or the like.
  • the display 13 is used to display information processed in the server 1 and a user interface for displaying visualizations, such as user access rights information, write success prompt information, and the like.
  • the components 11-13 of the server 1 communicate with one another via a system bus.
  • the image file upload system 10 includes at least one computer readable instruction stored in the memory 11, the at least one computer readable instruction being executable by the processor 12 to implement various embodiments of the present application.
  • step S1 when receiving the image file uploading request sent by the user of the service system, the database reading and writing module determines whether the user of the business system has the access right according to the user access right information pre-stored in the memory.
  • the image file uploading system 10 receives an image file uploading request sent by a user, for example, receiving an image file uploading request sent by a user through a mobile phone, a tablet computer, a self-service terminal device, and the like, such as receiving a user on a mobile phone or a tablet computer.
  • An image file upload request sent by a pre-installed client in a terminal such as a self-service terminal device, or an image file upload request sent by a user on a browser system in a terminal such as a mobile phone, a tablet computer, or a self-service terminal device.
  • FIG. 2 is a schematic diagram of an application environment of a plurality of service systems in an embodiment of the image file uploading system 10 of the present application.
  • Each image file uploading server can serve multiple business systems, and each business system user can send an image file upload request to the image file uploading server.
  • User access rights information is pre-stored in the memory of the image file upload server.
  • the user access right information may be identification information of each business system user having access rights.
  • an identification information table may be pre-stored, and the identifier of all business system users having access rights is stored in the table.
  • the user access right information may also be a correspondence between a business system user and a database and a hard disk that are authorized to access.
  • the user access right information may be a correspondence table between the business system user, the database, and the hard disk, and each business system user in the table has the access right, and the business system of the upload request may be known through the query form. Whether the user has access rights, you can also know the database and hard disk accessible to each business system user.
  • step S2 when the user of the service system has the access right, the database read/write module determines the database and the hard disk corresponding to the user of the service system according to the correspondence between the user pre-stored in the memory and the database and the hard disk, and Notifying the determined hard disk to the file reading and writing module.
  • the correspondence between the user and the database and the hard disk pre-stored in the memory is the correspondence between the user of the service system and the database and the hard disk that are authorized to access. For example, by querying the correspondence table, the database and the hard disk that the business system user who sent the upload request has permission to access can be known.
  • the database read/write module can notify the file reading and writing module of the identification or number of the hard disk.
  • step S3 the file reading and writing module writes the image file of the user of the service system into the hard disk notified by the database read/write module.
  • Step S4 After the file reading and writing module is successfully written, the database reading and writing module writes the current uploading information into a database corresponding to the user of the business system.
  • the database read/write module may also write the current upload information into the primary database.
  • the database access is separated from the file read/write service in the image file uploading server.
  • the database read/write module determines the location according to the user access permission information prestored in the memory. Whether the user of the service system has the access authority, and the database read/write module determines that the user of the service system corresponds to the service system user according to the correspondence between the user and the database and the hard disk prestored in the memory.
  • the file reading and writing module writes the image file of the business system user to the hard disk notified by the database reading and writing module;
  • the database reading and writing module writes the current uploading information into the database corresponding to the user of the service system, thereby avoiding frequently initiating query requests to the primary database and reducing the concurrent pressure. , improved system availability.
  • the number of databases and hard drives can be flexibly expanded as needed.
  • the method may further include the following steps:
  • the database read/write module reads user access rights information in the primary database and correspondence information between the user and the database and the hard disk into the memory.
  • the data related to the query operation stored in the primary database may be read into the memory when the database read/write module is started.
  • the data related to the query operation may include the above-mentioned user authority access information, database configuration information, hard disk information, and the like.
  • User access rights information includes which databases and hard disks are accessible to different users of each business system.
  • the database configuration information includes the number of databases currently configured by the database system (for example, 30), the number of each database, and the service system of the service.
  • the hard disk information includes the number of hard disks configured by the current storage system, the number of each hard disk, the storage capacity, and the service system of the service.
  • the image file uploading server can automatically obtain the user access right information, and the correspondence relationship between the user and the database and the hard disk, and cache the data of the query operation of the primary database on the server side, thereby avoiding frequently initiating a query to the primary database. request.
  • the manual database may be manually User access rights information, and correspondence information between the user and the database and the hard disk are stored in the memory, or the user access authority module in the main database is activated by manually issuing an instruction, and the user and the database are And correspondence information between the hard disks is read into the memory.
  • the method may further include the following steps:
  • the database reading and writing module After the file reading and writing module writes successfully, the database reading and writing module is notified.
  • the file reading and writing module may send the indication information to the database reading and writing module, and the indication information may carry the identification information of the user of the service system, so that the database reading and writing module may determine, according to the indication information, which service system user writes successfully, and further The current upload information of the service system user can be correspondingly written into the database corresponding to the user of the service system.
  • the image file uploading system 10 may further include the following steps:
  • the database read/write module notifies the user of the service system that the writing is successful. For example, the database read/write module can send an indication of successful writing to the service system user, so that the user can know in time whether the uploaded image file is successfully written.
  • FIG. 3 is a schematic flowchart of an image file uploading method according to an embodiment of the present invention.
  • the image file uploading method includes the following steps:
  • Step S10 Upon receiving the image file upload request sent by the user of the service system, the database read/write module determines whether the user of the service system has the access right according to the user access right information pre-stored in the memory.
  • the image file uploading system 10 receives an image file uploading request sent by a user, for example, receiving an image file uploading request sent by a user through a mobile phone, a tablet computer, a self-service terminal device, and the like, such as receiving a user on a mobile phone or a tablet computer.
  • An image file upload request sent by a pre-installed client in a terminal such as a self-service terminal device, or an image file upload request sent by a user on a browser system in a terminal such as a mobile phone, a tablet computer, or a self-service terminal device.
  • FIG. 2 is a schematic diagram of an application environment of a plurality of service systems in an embodiment of the image file uploading system 10 of the present application.
  • Each image file uploading server can serve multiple business systems, and each business system user can send an image file upload request to the image file uploading server.
  • User access rights information is pre-stored in the memory of the image file upload server.
  • the user access right information may be identification information of each business system user having access rights.
  • an identification information table may be pre-stored, and the identifier of all business system users having access rights is stored in the table.
  • the user access right information may also be a correspondence between a business system user and a database and a hard disk that are authorized to access.
  • the user access right information may be a correspondence table between the business system user, the database, and the hard disk, and each business system user in the table has the access right, and the business system of the upload request may be known through the query form. Whether the user has access rights, you can also know the database and hard disk accessible to each business system user.
  • step S20 when the user of the service system has the access right, the database read/write module determines the database and the hard disk corresponding to the user of the service system according to the correspondence between the user pre-stored in the memory and the database and the hard disk, and Notifying the determined hard disk to the file reading and writing module.
  • the correspondence between the pre-stored user and the database and the hard disk in the memory is the correspondence between the user of the service system and the database and the hard disk that are authorized to access. For example, by querying the correspondence table, the database and the hard disk that the business system user who sent the upload request has permission to access can be known.
  • the database read/write module can notify the file reading and writing module of the identification or number of the hard disk.
  • Step S30 the file reading and writing module writes the image file of the user of the business system into the hard disk notified by the database read/write module.
  • Step S40 After the file reading and writing module is successfully written, the database reading and writing module writes the current uploading information into a database corresponding to the user of the business system.
  • the database read/write module may also write the current upload information into the primary database.
  • the database access is separated from the file read/write service in the image file uploading server.
  • the database read/write module determines the location according to the user access permission information prestored in the memory. Whether the user of the service system has the access authority, and the database read/write module determines that the user of the service system corresponds to the service system user according to the correspondence between the user and the database and the hard disk prestored in the memory.
  • the file reading and writing module writes the image file of the business system user to the hard disk notified by the database reading and writing module;
  • the database reading and writing module writes the current uploading information into the database corresponding to the user of the service system, thereby avoiding frequently initiating query requests to the primary database and reducing the concurrent pressure. , improved system availability.
  • the number of databases and hard drives can be flexibly expanded as needed.
  • the method may further include the following steps:
  • the database read/write module reads user access rights information in the primary database and correspondence information between the user and the database and the hard disk into the memory.
  • the data related to the query operation stored in the primary database may be read into the memory when the database read/write module is started.
  • the data related to the query operation may include the above-mentioned user authority access information, database configuration information, hard disk information, and the like.
  • User access rights information includes which databases and hard disks are accessible to different users of each business system.
  • the database configuration information includes the number of databases currently configured by the database system (for example, 30), the number of each database, and the service system of the service.
  • the hard disk information includes the number of hard disks configured by the current storage system, the number of each hard disk, the storage capacity, and the service system of the service.
  • the image file uploading server can automatically obtain the user access right information, and the correspondence relationship between the user and the database and the hard disk, and cache the data of the query operation of the primary database on the server side, thereby avoiding frequently initiating a query to the primary database. request.
  • the manual database may be manually User access rights information, and correspondence information between the user and the database and the hard disk are stored in the memory, or the user access authority module in the main database is activated by manually issuing an instruction, and the user and the database are And correspondence information between the hard disks is read into the memory.
  • the method may further include the following steps:
  • the database reading and writing module After the file reading and writing module writes successfully, the database reading and writing module is notified.
  • the file reading and writing module may send the indication information to the database reading and writing module, where the indication information may carry the identification information of the user of the service system, so that the database reading and writing module may determine, according to the indication information, which service system user writes successfully, and further The current upload information of the service system user can be correspondingly written into the database corresponding to the user of the service system.
  • the method may further include the following steps:
  • the database read/write module notifies the user of the service system that the writing is successful. For example, the database read/write module can send an indication of successful writing to the service system user, so that the user can know in time whether the uploaded image file is successfully written.
  • the present application also provides a computer readable storage medium storing an image file uploading system, the image file uploading system being executable by at least one processor to cause the at least one processor.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and can also be implemented by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Storage Device Security (AREA)

Abstract

本申请涉及一种影像文件上传方法、服务器及可读存储介质，该方法包括：在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定业务系统用户是否具有访问权限；在业务系统用户具有访问权限时，数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。本申请降低了并发压力，提高了系统可用性。

Description

影像文件上传方法、服务器及可读存储介质
优先权申明
本申请基于巴黎公约申明享有2017年11月10日递交的申请号为CN 201711107655.9、名称为“影像文件上传方法、服务器及可读存储介质”中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种影像文件上传方法、服务器及可读存储介质。
背景技术
通常，企业内部有众多的业务系统，各业务系统向影像系统上传文件时，影像系统每次接收到请求，就需要访问一次数据库和硬盘，当接收到大量并发请求时，频繁的访问对数据库和磁盘造成的压力非常大，业务系统的请求不能得到及时响应，造成各方系统的可用性都降低。
发明内容
本申请的目的在于提供一种影像文件上传方法、服务器及可读存储介质，旨在降低并发压力，提高系统可用性。
为实现上述目的，本申请第一方面提供一种影像文件上传服务器，所述影像文件上传服务器包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的影像文件上传系统，所述影像文件上传系统被所述处理器执行时实现如下步骤：
在接收到业务系统用户发送的影像文件上传请求时，数据库读写 模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限；
在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；
所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；
在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
此外，为实现上述目的，本申请第二方面还提供一种影像文件上传方法，应用于影像文件上传服务器，所述方法包括：
在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限；
在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；
所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；
在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
进一步地，为实现上述目的，本申请第三方面还提供一种计算机 可读存储介质，所述计算机可读存储介质存储有影像文件上传系统，所述影像文件上传系统可被至少一个处理器执行，以使所述至少一个处理器执行如上述的影像文件上传方法的步骤。
本申请提出的影像文件上传方法、系统及可读存储介质，通过在影像文件上传服务器中将数据库访问与文件读写服务进行分离，在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限，在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块，所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中，从而避免了频繁对主数据库发起查询请求，降低了并发压力，提高了系统可用性。此外，数据库和硬盘的数量还可以根据需求灵活扩展。
附图说明
图1为本申请影像文件上传系统10较佳实施例的运行环境示意图；
图2为本申请影像文件上传系统10一实施例中与多个业务系统的应用环境示意图；
图3为本申请影像文件上传方法一实施例的流程示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
需要说明的是，在本申请中涉及“第一”、“第二”等的描述仅用于描述目的，而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外，各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本申请要求的保护范围之内。
本申请提供一种影像文件上传系统。请参阅图1，是本申请影像文件上传系统10较佳实施例的运行环境示意图。
在本实施例中，所述的影像文件上传系统10安装并运行于影像文件上传服务器1中。该影像文件上传服务器1可包括，但不仅限于，存储器11、处理器12及显示器13。图1仅示出了具有组件11-13的服务器1，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
所述存储器11为至少一种类型的可读计算机存储介质，所述存储器11在一些实施例中可以是所述服务器1的内部存储单元，例如该服务器1的硬盘或内存。所述存储器11在另一些实施例中也可以是所述服务器1的外部存储设备，例如所述服务器1上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital, SD)卡，闪存卡(Flash Card)等。进一步地，所述存储器11还可以既包括所述服务器1的内部存储单元也包括外部存储设备。所述存储器11用于存储安装于所述服务器1的应用软件及各类数据，例如所述影像文件上传系统10的程序代码等。所述存储器11还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)，微处理器或其他数据处理芯片，用于运行所述存储器11中存储的程序代码或处理数据，例如执行所述影像文件上传系统10等。
所述显示器13在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。所述显示器13用于显示在所述服务器1中处理的信息以及用于显示可视化的用户界面，例如用户访问权限信息、写入成功提示信息等。所述服务器1的部件11-13通过系统总线相互通信。
影像文件上传系统10包括至少一个存储在所述存储器11中的计算机可读指令，该至少一个计算机可读指令可被所述处理器12执行，以实现本申请各实施例。
其中，上述影像文件上传系统10被所述处理器12执行时实现如下步骤：
步骤S1，在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限。
本实施例中，影像文件上传系统10接收用户发出的影像文件上 传请求，例如，接收用户通过手机、平板电脑、自助终端设备等终端发送的影像文件上传请求，如接收用户在手机、平板电脑、自助终端设备等终端中预先安装的客户端上发送来的影像文件上传请求，或接收用户在手机、平板电脑、自助终端设备等终端中的浏览器系统上发送来的影像文件上传请求。
本实施例中，如图2所示，图2为本申请影像文件上传系统10一实施例中与多个业务系统的应用环境示意图。每一影像文件上传服务器可以服务于多个业务系统，各个业务系统用户均可以向影像文件上传服务器发送影像文件上传请求。
该影像文件上传服务器的存储器中预存有用户访问权限信息。该用户访问权限信息可以为具有访问权限的各个业务系统用户的标识信息，例如，可以预存一标识信息表，该表格中存储有所有具有访问权限的业务系统用户的标识。或者，所述用户访问权限信息还可以为业务系统用户与有权限访问的数据库和硬盘之间的对应关系。例如，用户访问权限信息可以为业务系统用户、数据库和硬盘之间的对应关系表，该表格中的每一业务系统用户均具有访问权限，通过查询表格，既可以获知所述上传请求的业务系统用户是否具有访问权限，还可以获知每一业务系统用户可访问的数据库和硬盘。
步骤S2，在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块。
可以理解的是，所述存储器中预存的用户与数据库以及硬盘之间的对应关系，即为上述业务系统用户与有权限访问的数据库和硬盘之 间的对应关系。例如，通过查询该对应关系表格，即可获知发送所述上传请求的业务系统用户有权限访问的数据库和硬盘。
数据库读写模块可以将硬盘的标识或编号等信息通知给文件读写模块。
步骤S3，所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中。
步骤S4，在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
在本实施例中，除了将上传信息写入与业务系统用户对应的数据库中之外，数据库读写模块还可以将本次上传信息写入主数据库中。
本实施例通过在影像文件上传服务器中将数据库访问与文件读写服务进行分离，在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限，在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块，所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中，从而避免了频繁对主数据库发起查询请求，降低了并发压力，提高了系统可用性。此外，数据库和硬盘的数量还可以根据需求灵活扩展。
进一步地，在一可选的实施例中，在上述实施例的基础上，所述影像文件上传系统10被所述处理器12执行实现所述步骤S1之前，还可以包括如下步骤：
所述数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
在本实施例中，可以在数据库读写模块启动时，将主数据库存储的与查询操作相关的数据读取到存储器中。该与查询操作相关的数据可以包括上述用户权限访问信息、数据库配置信息、硬盘信息等。用户访问权限信息包括各业务系统的不同用户对哪些数据库及硬盘有访问权限。数据库配置信息包括数据库系统当前配置的数据库数量(例如30个)，各数据库的编号、服务的业务系统等。硬盘信息包括当前存储系统配置的硬盘数量，各硬盘的编号、存储容量，服务的业务系统等。从而该影像文件上传服务器可以自动获取到用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息等，通过在服务器端缓存主数据库的查询操作的数据、避免了频繁对主数据库发起查询请求。
此外，除了通过数据库读写模块自动将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中之外，还可以手动的将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息存储到所述存储器中，或者，通过人为发出指令来启动数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
进一步地，在一可选的实施例中，在上述实施例的基础上，所述影像文件上传系统10被所述处理器12执行实现所述步骤S4之前，还可以包括如下步骤：
所述文件读写模块写入成功后，通知所述数据库读写模块。例如，文件读写模块可以向数据库读写模块发送指示信息，该指示信息可以携带业务系统用户的标识信息，从而该数据库读写模块可以根据指示信息确定是哪一个业务系统用户写入成功，进而能够将该业务系统用户的本次上传信息对应写入到该业务系统用户对应的数据库中。
进一步地，在一可选的实施例中，在上述实施例的基础上，所述影像文件上传系统10被所述处理器12执行实现所述步骤S4之后，还可以包括如下步骤：
所述数据库读写模块通知所述业务系统用户写入成功。例如，数据库读写模块可以向业务系统用户发送写入成功的指示信息，使得用户能够及时获知其上传的影像文件是否成功写入。
如图3所示，图3为本申请影像文件上传方法一实施例的流程示意图，该影像文件上传方法包括以下步骤：
步骤S10，在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限。
本实施例中，影像文件上传系统10接收用户发出的影像文件上传请求，例如，接收用户通过手机、平板电脑、自助终端设备等终端发送的影像文件上传请求，如接收用户在手机、平板电脑、自助终端 设备等终端中预先安装的客户端上发送来的影像文件上传请求，或接收用户在手机、平板电脑、自助终端设备等终端中的浏览器系统上发送来的影像文件上传请求。
本实施例中，如图2所示，图2为本申请影像文件上传系统10一实施例中与多个业务系统的应用环境示意图。每一影像文件上传服务器可以服务于多个业务系统，各个业务系统用户均可以向影像文件上传服务器发送影像文件上传请求。
该影像文件上传服务器的存储器中预存有用户访问权限信息。该用户访问权限信息可以为具有访问权限的各个业务系统用户的标识信息，例如，可以预存一标识信息表，该表格中存储有所有具有访问权限的业务系统用户的标识。或者，所述用户访问权限信息还可以为业务系统用户与有权限访问的数据库和硬盘之间的对应关系。例如，用户访问权限信息可以为业务系统用户、数据库和硬盘之间的对应关系表，该表格中的每一业务系统用户均具有访问权限，通过查询表格，既可以获知所述上传请求的业务系统用户是否具有访问权限，还可以获知每一业务系统用户可访问的数据库和硬盘。
步骤S20，在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块。
可以理解的是，所述存储器中预存的用户与数据库以及硬盘之间的对应关系，即为上述业务系统用户与有权限访问的数据库和硬盘之间的对应关系。例如，通过查询该对应关系表格，即可获知发送所述上传请求的业务系统用户有权限访问的数据库和硬盘。
数据库读写模块可以将硬盘的标识或编号等信息通知给文件读写模块。
步骤S30，所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中。
步骤S40，在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
在本实施例中，除了将上传信息写入与业务系统用户对应的数据库中之外，数据库读写模块还可以将本次上传信息写入主数据库中。
本实施例通过在影像文件上传服务器中将数据库访问与文件读写服务进行分离，在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限，在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块，所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中，从而避免了频繁对主数据库发起查询请求，降低了并发压力，提高了系统可用性。此外，数据库和硬盘的数量还可以根据需求灵活扩展。
进一步地，在一可选的实施例中，在上述实施例的基础上，在所述步骤S10之前，该方法还可以包括如下步骤：
所述数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
在本实施例中，可以在数据库读写模块启动时，将主数据库存储的与查询操作相关的数据读取到存储器中。该与查询操作相关的数据可以包括上述用户权限访问信息、数据库配置信息、硬盘信息等。用户访问权限信息包括各业务系统的不同用户对哪些数据库及硬盘有访问权限。数据库配置信息包括数据库系统当前配置的数据库数量(例如30个)，各数据库的编号、服务的业务系统等。硬盘信息包括当前存储系统配置的硬盘数量，各硬盘的编号、存储容量，服务的业务系统等。从而该影像文件上传服务器可以自动获取到用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息等，通过在服务器端缓存主数据库的查询操作的数据、避免了频繁对主数据库发起查询请求。
此外，除了通过数据库读写模块自动将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中之外，还可以手动的将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息存储到所述存储器中，或者，通过人为发出指令来启动数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
进一步地，在一可选的实施例中，在上述实施例的基础上，在所述步骤S40之前，该方法还可以包括如下步骤：
所述文件读写模块写入成功后，通知所述数据库读写模块。例如， 文件读写模块可以向数据库读写模块发送指示信息，该指示信息可以携带业务系统用户的标识信息，从而该数据库读写模块可以根据指示信息确定是哪一个业务系统用户写入成功，进而能够将该业务系统用户的本次上传信息对应写入到该业务系统用户对应的数据库中。
进一步地，在一可选的实施例中，在上述实施例的基础上，在所述步骤S40之后，该方法还可以包括如下步骤：
所述数据库读写模块通知所述业务系统用户写入成功。例如，数据库读写模块可以向业务系统用户发送写入成功的指示信息，使得用户能够及时获知其上传的影像文件是否成功写入。
此外，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有影像文件上传系统，所述影像文件上传系统可被至少一个处理器执行，以使所述至少一个处理器执行如上述实施例中的影像文件上传方法的步骤，该影像文件上传方法的步骤S10、S20、S30等具体实施过程如上文所述，在此不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件来实现，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
以上参照附图说明了本申请的优选实施例，并非因此局限本申请的权利范围。上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。另外，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本领域技术人员不脱离本申请的范围和实质，可以有多种变型方案实现本申请，比如作为一个实施例的特征可用于另一实施例而得到又一实施例。凡在运用本申请的技术构思之内所作的任何修改、等同替换和改进，均应在本申请的权利范围之内。

Claims (20)

  1. 一种影像文件上传服务器，其特征在于，所述影像文件上传服务器包括存储器、处理器，所述存储器上存储有可在所述处理器上运行的影像文件上传系统，所述影像文件上传系统被所述处理器执行时实现如下步骤：
    在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限；
    在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；
    所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；
    在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
  2. 如权利要求1所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
  3. 如权利要求2所述的影像文件上传服务器，其特征在于，所述用户访问权限信息包括业务系统用户与有权限访问的数据库和硬 盘之间的对应关系。
  4. 如权利要求1所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述文件读写模块写入成功后，通知所述数据读写模块。
  5. 如权利要求2所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述文件读写模块写入成功后，通知所述数据读写模块。
  6. 如权利要求3所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述文件读写模块写入成功后，通知所述数据读写模块。
  7. 如权利要求1所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述数据库读写模块通知所述业务系统用户写入成功。
  8. 如权利要求2所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述数据库读写模块通知所述业务系统用户写入成功。
  9. 如权利要求3所述的影像文件上传服务器，其特征在于，所述处理器还用于执行所述影像文件上传系统，以实现以下步骤：
    所述数据库读写模块通知所述业务系统用户写入成功。
  10. 一种影像文件上传方法，应用于影像文件上传服务器，其特征在于，所述方法包括：
    在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限；
    在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；
    所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；
    在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
  11. 如权利要求10所述的影像文件上传方法，其特征在于，在所述数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限的步骤之前，该方法还包括：
    所述数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
  12. 如权利要求11所述的影像文件上传方法，其特征在于，所述用户访问权限信息包括业务系统用户与有权限访问的数据库和硬 盘之间的对应关系。
  13. 如权利要求10所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中的步骤之前，该方法还包括：所述文件读写模块写入成功后，通知所述数据读写模块。
  14. 如权利要求11所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中的步骤之前，该方法还包括：所述文件读写模块写入成功后，通知所述数据读写模块。
  15. 如权利要求12所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中的步骤之前，该方法还包括：所述文件读写模块写入成功后，通知所述数据读写模块。
  16. 如权利要求10所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中的步骤之后，该方法还包括：所述数据库读写模块通知所述业务系统用户写入成功。
  17. 如权利要求11所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的 数据库中的步骤之后，该方法还包括：所述数据库读写模块通知所述业务系统用户写入成功。
  18. 如权利要求12所述的影像文件上传方法，其特征在于，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中的步骤之后，该方法还包括：所述数据库读写模块通知所述业务系统用户写入成功。
  19. 一种计算机可读存储介质，所述计算机可读存储介质存储有影像文件上传系统，所述影像文件上传系统可被至少一个处理器执行，以使所述至少一个处理器执行如下步骤：
    在接收到业务系统用户发送的影像文件上传请求时，数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限；
    在所述业务系统用户具有访问权限时，所述数据库读写模块根据存储器中预存的用户与数据库以及硬盘之间的对应关系，确定与所述业务系统用户对应的数据库和硬盘，并将确定的所述硬盘通知给文件读写模块；
    所述文件读写模块将所述业务系统用户的影像文件写入所述数据库读写模块通知的所述硬盘中；
    在所述文件读写模块写入成功后，所述数据库读写模块将本次上传信息写入与所述业务系统用户对应的数据库中。
  20. 如权利要求19所述的计算机可读存储介质，其特征在于， 在所述数据库读写模块根据存储器中预存的用户访问权限信息确定所述业务系统用户是否具有访问权限的步骤之前，还包括：
    所述数据库读写模块将主数据库中的用户访问权限信息，以及用户与数据库以及硬盘之间的对应关系信息读取到所述存储器中。
PCT/CN2018/077621 2017-11-10 2018-02-28 影像文件上传方法、服务器及可读存储介质 WO2019091023A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711107655.9 2017-11-10
CN201711107655.9A CN107967305B (zh) 2017-11-10 2017-11-10 影像文件上传方法、服务器及可读存储介质

Publications (1)

Publication Number Publication Date
WO2019091023A1 true WO2019091023A1 (zh) 2019-05-16

Family

ID=62000935

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077621 WO2019091023A1 (zh) 2017-11-10 2018-02-28 影像文件上传方法、服务器及可读存储介质

Country Status (2)

Country Link
CN (1) CN107967305B (zh)
WO (1) WO2019091023A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114090521A (zh) * 2021-11-19 2022-02-25 中国银行股份有限公司 影像上传方法及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108846300B (zh) * 2018-06-22 2022-06-28 联想(北京)有限公司 一种信息处理方法及第一电子设备
CN110912953A (zh) * 2018-09-17 2020-03-24 深圳市优必选科技有限公司 一种文件存储系统及方法
CN111444532A (zh) * 2020-02-20 2020-07-24 山东浪潮通软信息科技有限公司 一种可灵活配置的租赁业务专用影像展示方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103020550A (zh) * 2012-12-03 2013-04-03 记忆科技(深圳)有限公司 一种固态硬盘及其安全访问方法、固态硬盘系统
CN104202626A (zh) * 2014-08-29 2014-12-10 青岛海信宽带多媒体技术有限公司 电视相册系统及管理和访问电视相册的方法
CN105956063A (zh) * 2016-04-27 2016-09-21 华自科技股份有限公司 多采测点的数据存储方法与系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8239443B2 (en) * 2009-09-01 2012-08-07 Rovi Technologies Corporation Method and system for tunable distribution of content
CN102104494B (zh) * 2009-12-18 2013-11-06 华为技术有限公司 元数据服务器、带外网络文件系统及其处理方法
CN103246483A (zh) * 2013-04-24 2013-08-14 Tcl集团股份有限公司 文件扫描方法、系统及智能终端
US10805273B2 (en) * 2016-04-01 2020-10-13 Egnyte, Inc. Systems for improving performance and security in a cloud computing system
CN106612330B (zh) * 2017-01-05 2020-04-21 广州慧睿思通信息科技有限公司 支持分布式多文件导入的系统及方法
CN107180102B (zh) * 2017-05-25 2019-12-31 北京环境特性研究所 一种目标特性数据的存储方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103020550A (zh) * 2012-12-03 2013-04-03 记忆科技(深圳)有限公司 一种固态硬盘及其安全访问方法、固态硬盘系统
CN104202626A (zh) * 2014-08-29 2014-12-10 青岛海信宽带多媒体技术有限公司 电视相册系统及管理和访问电视相册的方法
CN105956063A (zh) * 2016-04-27 2016-09-21 华自科技股份有限公司 多采测点的数据存储方法与系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114090521A (zh) * 2021-11-19 2022-02-25 中国银行股份有限公司 影像上传方法及装置

Also Published As

Publication number Publication date
CN107967305A (zh) 2018-04-27
CN107967305B (zh) 2022-02-01

Similar Documents

Publication Publication Date Title
WO2019153592A1 (zh) 用户权限数据管理装置、方法及计算机可读存储介质
WO2019091023A1 (zh) 影像文件上传方法、服务器及可读存储介质
WO2019140828A1 (zh) 电子装置、分布式系统日志查询方法及存储介质
US8335890B1 (en) Associating an identifier with a content unit
KR101643022B1 (ko) 카탈로그-기반 소프트웨어 컴포넌트 관리
US20130152085A1 (en) Optimizing Storage Allocation in a Virtual Desktop Environment
US8695104B2 (en) System and method for creating conditional immutable objects in a storage device
CN111400308B (zh) 缓存数据的处理方法、电子装置及可读存储介质
US9760725B2 (en) Content transfer control
US12007849B2 (en) System and method for securing instant access of data in file based backups in a backup storage system using metadata files
US10572506B2 (en) Synchronizing data stores for different size data objects
CN108475201B (zh) 一种虚拟机启动过程中的数据获取方法和云计算系统
TW200825924A (en) Virtual deletion in merged registry keys
WO2019136812A1 (zh) 电子装置、数据调用日志生成及查询方法及存储介质
WO2019071898A1 (zh) 电子装置、数据库查询脚本生成方法及存储介质
CN109597707B (zh) 克隆卷数据拷贝方法、装置及计算机可读存储介质
WO2019169763A1 (zh) 电子装置、业务系统风险控制方法及存储介质
WO2019071968A1 (zh) 薪资计算方法、应用服务器及计算机可读存储介质
WO2019169771A1 (zh) 电子装置、访问指令信息获取方法及存储介质
WO2019140829A1 (zh) 电子装置、应用升级版本发布的方法及存储介质
CN107886008B (zh) 文件管理方法、系统、装置和计算机可读存储介质
US20180276213A1 (en) Methods and system for database request management
CN107918915B (zh) 核保信息处理的装置、方法及计算机可读存储介质
US20200104046A1 (en) Opportunistic data content discovery scans of a data repository
CN112685078A (zh) 接口文档生成与查询方法、装置及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18876356

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22.09.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18876356

Country of ref document: EP

Kind code of ref document: A1