Media asset synchronization platform under remote multi-activity architecture and calling method thereof

Abstract

The invention discloses a media asset synchronization platform under a remote multi-activity architecture and a calling method thereof, the media asset synchronization platform comprises a synchronization service and a basic service, the synchronization service comprises a core service, a synchronization basic service and a support service, and the core service comprises a process service, a transmission service and a message service; the calling method comprises the following steps: storing city-county media asset system materials into a city-county data center; city and county users initiate medium resource calling; a city and county data center monitors messages, initiates a synchronization request and sends a synchronization task; the provincial-level data main center and the provincial-level data branch centers transmit materials of the city and county data centers into a database and store the materials; the city-county data center delivers the materials to a provincial-level media asset system; the provincial-level media asset system initiates a new metadata synchronization request, carries out message monitoring, initiates a synchronization request and sends a synchronization task; and transmitting materials of the provincial data main center and updating metadata. The method has the characteristics of realizing efficient utilization of resources and effective control of cost.

Description

Technical Field

[0001] The present invention relates to a media resource calling method, in particular to a media resource synchronization platform under a remote multi-active architecture and a calling method thereof. Background Art

[0002] Media assets, including audio, video, pictures, text and other media materials, are indispensable core resources for media organizations in the process of content production, dissemination and service. In the era of digitalization and informatization, the importance of media assets is becoming increasingly prominent.

[0003] With the continuous development of cloud computing, big data, artificial intelligence and other technologies, the value mining and automated management of media assets have brought many conveniences to users and managers. In the existing integrated media system, the traditional independent domain name and independent server independent construction model is adopted to achieve the integration and optimization of traditional media and new media resources. The integrated media center needs to keep up with the pace of technological development. Independent construction lags behind in technology updates due to the lack of external cooperation and resource sharing, resulting in limited resources, making it difficult to quickly respond to market changes and meet its growing needs; and the independent construction model is usually accompanied by higher initial investment and operation and maintenance costs, especially in terms of hardware facilities, software platforms, and labor costs, and the operation and maintenance costs are high. Summary of the invention

[0004] The purpose of the present invention is to provide a method for calling media asset services in a remote multi-active architecture. The present invention has the characteristics of realizing efficient utilization of resources and effective control of costs.

[0005] The technical solution of the present invention is as follows: a media asset synchronization platform under a multi-site active-active architecture, including synchronization services and basic services, wherein the synchronization services include core services, synchronization basic services and supporting services, wherein the core services include process services, transmission services and message services; the process services are used to uniformly coordinate message processes and transmission processes through process processes to synchronize business data; the transmission services are used to flexibly coordinate transmission migration executors through multi-threaded pooling and high-concurrency technology to complete the business capability of batch data synchronization, realize multi-threaded and high-efficiency data transmission, and achieve real-time synchronization capabilities under stable network environments; the message services are used to utilize the Kafka message platform as the basic support, design a flexible subscription message Topic method, store data information of the business platform, utilize the constructed message process to asynchronously read the accumulated message queue, asynchronously read the accumulated tasks, realize data consistency in each production environment under the multi-active mode, and provide disaster recovery capabilities.

[0006] In the aforementioned media asset synchronization platform under the remote multi-active architecture, the basic synchronization services include user synchronization service, system identification service and message mechanism service; the user synchronization service is used to provide the administrator with basic data configuration, customized process, message configuration, user synchronization task viewing and task redo functions of the synchronization service; the system identification service is a unique identifier of the data center, which is used to identify and confirm the source of data; the message mechanism service is used to build point-to-point synchronization mode and ring synchronization mode to realize the ability of multi-active application synchronization in multiple data centers in different locations.

[0007] In the aforementioned media asset synchronization platform under a multi-site active-active architecture, the supporting services include clock synchronization service, permission management service and migration service; the clock synchronization service is used for clock verification to ensure the reliability of transmission time; the permission management service is used to allocate and verify user permissions to verify whether the user can initiate synchronization or manage synchronization tasks; the migration service is used to migrate transferable files from data center I to data center II.

[0008] In the aforementioned media synchronization platform under the multi-site active-active architecture, the basic services include storage services, database services and cache services; the storage services are used to store files and their metadata information; the database services include distributed relational databases and document databases to adapt to various metadata types; the cache service, on the one hand, serves as a cache buffer for the data interface, responds to frequent query requests with cached hot data, reduces the query pressure of relational and non-relational databases, and provides fast reading functions when users search; on the other hand, it serves as a shared storage area for service session data, ensuring that the service can continue to run in the state before the switch when a service switch occurs.

[0009] A media resource calling method under a remote multi-active architecture adopts the above-mentioned media resource synchronization platform, wherein the remote multi-active architecture includes a city and county data center, a provincial data master center, and a provincial data sub-center. The media resource calling method includes the following steps:

[0010] S1. The materials of the municipal and county media resource systems are stored in the municipal and county data centers, triggering two-way synchronization instructions between the provincial data master center and the provincial data sub-center;

[0011] S2. City and county users initiate media resource calls: City and county users initiate batch or single calls to the provincial data center media resources for materials in the city and county data center, and publish the message to the message mechanism service;

[0012] S3, city and county data center message monitoring;

[0013] S4, the city and county data center initiates a synchronization request;

[0014] S5. The city and county data centers send synchronization tasks to the provincial data main center and provincial data sub-center respectively, and the provincial data main center and provincial data sub-center receive the synchronization tasks;

[0015] S6. The provincial data main center and provincial data sub-center will transfer the materials of the municipal and county data centers into the database and store them;

[0016] S7. Materials from city and county data centers are sent to the provincial media resource system;

[0017] S8. The provincial media asset system initiates a new metadata synchronization request. The provincial data master center updates the metadata to the material of the database service and publishes the message to the message mechanism service.

[0018] S9, provincial data master center message monitoring;

[0019] S10. The provincial data master center initiates a synchronization request;

[0020] S11. The provincial data main center sends synchronization tasks to the provincial data sub-center and the municipal and county data centers respectively, and the provincial data sub-center and the municipal and county data centers receive the synchronization tasks;

[0021] S12. Material transmission and metadata update at the provincial data master center.

[0022] In the above-mentioned media resource calling method under the multi-site active-active architecture, in step S1, when the municipal and county data center accepts the materials of the municipal and county media resource system into the warehouse, the metadata carried by the material itself is stored in the database service of the municipal and county data center. At the same time, the system identification service of the municipal and county data center analyzes the metadata of the material as data at this level, and identifies it as metadata of the municipal and county data center, which triggers the two-way synchronization instructions of the provincial data main center and the data sub-center.

[0023] In the above-mentioned media resource calling method under a remote multi-active architecture, in step S2, before initiation, it is first determined through permission management whether the user has the calling permission. If not, initiation cannot be made; if yes, initiation is successful.

[0024] In the above-mentioned media resource calling method under a multi-site active-active architecture, in step S5 and step S11, before the provincial data main center, the provincial data sub-center, and the municipal and county data centers receive synchronization tasks, they first execute user data synchronization tasks through their respective user synchronization services to ensure the consistency of user data in each data center; then they accept synchronization tasks issued by the message services of data centers at all levels through their respective process services and cache services.

[0025] In the above-mentioned media asset calling method under a multi-site active-active architecture, in step S6, the city and county data center materials are transferred into the library and stored specifically by the provincial data main center and the provincial data sub-center respectively importing the metadata of the city and county data center materials into their respective database services, and respectively transmitting the source files and document data of the city and county media asset system materials to their respective storage services through their respective transmission services, thereby realizing full synchronization of metadata, source files and document data.

[0026] In the above-mentioned media resource calling method under a multi-site active-active architecture, step S12 is specifically as follows: the municipal and county data centers, provincial data sub-centers and provincial data sub-centers first perform clock verification through a clock synchronization service to ensure that the transmission time is consistent; then the provincial data sub-center and the municipal and county data centers use their respective process services to store the metadata of the provincial data main center materials into their respective database services, and use their respective transmission services to transfer the physical files of the provincial data main center materials to their respective storage services, thereby realizing the update of metadata and physical files.

[0027] Compared with the prior art, the present invention has the following beneficial effects:

[0028] The present invention constructs a multi-level regional aggregation and remote media asset system, adopts a synchronous mode to meet the needs of integrated media, ensures the daily business production flow of media assets, provides business data self-organization and flexible scheduling management capabilities, calls provincial data centers in combination with actual needs, and realizes multi-threaded, stable, and efficient data transmission synchronization between multi-level regional data centers, realizes efficient use of resources and low-cost provincial media asset capacity calling, solves the problems of media asset service calling and data synchronization in remote multi-regional data centers, quickly responds to market changes, and has low operating and maintenance costs in terms of hardware facilities, software platforms, and labor costs.

[0029] The present invention also provides full synchronization of metadata, low-code files and manuscript data at the business level, and can perform source file synchronization according to tenant application requirements to meet emergency disaster recovery needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 It is a schematic diagram of the synchronous mode structure of the present invention.

[0031] Figure 2 It is a flowchart of the calling method of the present invention. DETAILED DESCRIPTION

[0032] The present invention will be further described below in conjunction with the embodiments, but they are not intended to limit the present invention.

[0033] Example:

[0034] like Figure 1As shown, a media resource synchronization platform under a remote multi-active architecture includes synchronization services and basic services. The synchronization services include core services, synchronization basic services and supporting services. The core services include process services, transmission services and message services.

[0035] Specifically, the core service uses Microsoft Orleans cloud computing distributed framework to build message service, process service, and transmission service. The three services maintain an independent loosely coupled structure to ensure the stable operation of the overall platform. At the same time, it provides the ability to self-orchestrate task processes and flexibly schedule and manage tasks to achieve efficient data transmission and synchronization.

[0036] The process service is used to coordinate the message process and the transmission process to synchronize business data through the process process.

[0037] The transmission service is used to flexibly deploy the transmission migration executor to complete the business capabilities of batch data synchronization through multi-threaded pooling and high concurrency technology, realize multi-threaded and high-efficiency data transmission, and achieve real-time synchronization capabilities under a stable network environment.

[0038] The message service is used to use the Kafka message platform as the basic support, design a flexible message topic subscription method, store the data information of the business platform, use the constructed message process to asynchronously read the accumulated message queue, asynchronously read the accumulated tasks, achieve data consistency in various production environments under the multi-active mode, and provide disaster recovery capabilities.

[0039] The synchronization basic services include user synchronization services, system identification services and message mechanism services.

[0040] The user synchronization service is used to provide administrator synchronization service with basic data configuration, customized processes, message configuration, user synchronization task viewing and task redo functions.

[0041] The system identification service is a unique identifier of the data center, which is used to identify and confirm the source of data.

[0042] The message mechanism service is used to construct point-to-point synchronization mode and ring synchronization mode to realize the ability to synchronize multi-active applications in multiple data centers in different locations. Among them, the point-to-point synchronization mode is used to design the source system identification and optimize the solution to the ping-pong effect problem of data synchronization. Data Center I and Data Center II collaborate to realize a single point-to-point synchronization of tasks. The ring synchronization mode is used to synchronize data from the main task initiator to one or more receiving ends through the consumption capability of the message queue. The source system identification is carried during the synchronization process, and only a single synchronization is performed to ensure the consistency of data synchronization in multiple data centers in different locations, and realize the collaborative use of multi-active applications among multiple data centers.

[0043] The supporting services include clock synchronization service, rights management service and migration service.

[0044] The clock synchronization service is used for clock verification to ensure the reliability of transmission time.

[0045] The rights management service is used to allocate and verify user rights and verify whether the user can initiate synchronization or manage synchronization tasks.

[0046] The migration service is used to migrate transferable files from data center I to data center II.

[0047] The basic services include storage services, database services and cache services.

[0048] The storage service is used to store files and their metadata information.

[0049] The database service includes a distributed relational database and a document database to adapt to various metadata types. Among them, the distributed relational database mainly stores static configuration information of the system, such as department configuration, column configuration, user permissions, device connection information, etc. The total amount of these data is not large and changes rarely, so a virtual synchronous replication solution is adopted to make a high-availability cluster. The document database associates the object on the object storage with the ObjectID, and manages the files such as materials, programs, manuscripts, logs and related metadata as a whole. When storing data, the document database uses a "tree structure" to save information, and the tree consists of nodes and attributes. A node has only one father (parent node), any number of children (child nodes) and any number of attributes. An attribute has only one father (parent node), no child nodes, and consists of a name and one or more values. Only attributes can be used to store information, and nodes are used to create "paths" inside the tree. The document database can support two levels of control, node and user, and can combine the two to support row-granular access control. During the query process, if the user does not have the authority to view a specific node, even if the node meets the query conditions, the node cannot be seen in the query results. For granular access control, you can do this by planning your data model or by programmatically filtering when filtering query results.

[0050] The cache service, on the one hand, acts as a cache buffer for the data interface, responding to frequent query requests with cached hot data, alleviating the query pressure of relational and non-relational databases, and providing fast reading function when users search; on the other hand, it acts as a shared storage area for service session data, ensuring that the service can continue to run in the state before the switch when service switching occurs.

[0051] A method for calling a media resource system under a remote multi-active architecture adopts the above-mentioned synchronization mode. The remote multi-active architecture is based on the China Blue Cloud platform, including a city and county data center, a provincial data master center, and a provincial data sub-center. The calling method includes the following steps:

[0052] S1. The materials of the city and county media resources system are stored in the city and county data center: City and county users store the materials of the city and county media resources system in the city and county data center.

[0053] Specifically, in this embodiment, when the city and county data center accepts the material from the city and county media asset system, the metadata carried by the material itself is stored in the database service of the city and county data center. At the same time, the city and county data center analyzes the metadata of the material through the system identification service as the data of this level, sets the metadata as the metadata of the city and county data center, and triggers the two-way synchronization instructions of the provincial data main center and the provincial data sub-center. The city and county data center obtains the page display fields through the cache service, and provides a fast reading function when the user searches.

[0054] It should be noted that in the method of this embodiment, only when the system identification service confirms that the source of the metadata of the material belongs to the current data center, will it trigger a two-way synchronization instruction to the provincial data center and the data sub-center to proceed to the next step of the synchronization process. For example, when the city and county data center receives metadata identified as this level, it will trigger a two-way synchronization instruction to the provincial data center and the data sub-center.

[0055] At the same time, it can also be matched with the material metadata according to the preset configuration of the current data center. When the system identification service confirms that the metadata source of the material belongs to the current data center and the metadata of the material meets the preset configuration, it will trigger the two-way synchronization instructions of the provincial data main center and the data sub-center to carry out the subsequent synchronization process.

[0056] By setting up the system identification service, a judgment basis is set for the start of the subsequent synchronization process. With one operation, the automatic flow of media resource synchronization tasks among municipal and county data centers, provincial data main centers, and provincial data sub-centers can be achieved.

[0057] S2. City and county users initiate media resource calls: City and county users initiate media resource calls to the provincial data center in batches or individually for materials in the city and county data center. Specifically, first determine whether the user has the call permission through permission management. If not, the call cannot be initiated; if so, the call is successfully initiated. After the call is successfully initiated, the city and county data center publishes the message to different topics of the Kafka message mechanism service based on the characteristics of the material metadata.

[0058] The present invention can call the media resources of the provincial data main center according to the actual needs of the municipal and county data centers, and can transmit both low-code files and high- and low-code files; or only call certain functions of the media resources of the provincial data main center, support multi-tenant business models, and achieve accurate response to different needs.

[0059] S3. City and county data center message monitoring: The message service of the city and county data center acts as a consumer, monitors the Kafka messages in the message mechanism service and consumes them. Each time a message is consumed, the interface of the process service at this level is called to add a new process task. In one embodiment, in order to control the consumption speed and reduce the network and disk pressure, the message service monitors the process service in real time until the number of process tasks executed in the process service is lower than the threshold.

[0060] By monitoring the message service, consumers can ensure that they will not miss any important messages. Kafka provides message persistence and replication mechanisms. Even if a Broker node fails, consumers can still get messages from other nodes.

[0061] S4. The city and county data center initiates a synchronization request: The message service of the city and county data center initiates a synchronization request to the process service at this level.

[0062] S5. The municipal and county data centers send synchronization tasks: After the process service receives the synchronization request sent by the message service, it sends synchronization tasks to the synchronization services of the provincial data main center and the provincial data sub-center respectively, and the synchronization tasks carry the system identifier.

[0063] The present invention realizes automatic initiation of synchronization tasks through message mechanism services, supports ring synchronization among three data centers, and realizes synchronization of multi-active applications in multiple data centers at different locations.

[0064] Specifically, the provincial data main center and provincial data sub-center first perform user data synchronization tasks through their respective user synchronization services to ensure the consistency of user data in each data center; then, through their respective process services and cache services, they accept synchronization tasks issued by the message services of data centers at all levels, such as business object synchronization tasks, basic data synchronization tasks, etc. According to the actual business situation, the synchronization process is visually constructed in the form of a flowchart. For each step of each process, the name, description, usage protocol, and number of automatic retries of the step can be customized, which further ensures the easy maintenance and high availability of the synchronization process.

[0065] S6. Material transfer into the city and county data center and storage: During the synchronization process, the city and county data center, provincial data sub-center and provincial data sub-center first perform clock verification through the clock synchronization service to ensure consistent transmission time; then the provincial data main center and provincial data sub-center respectively import the metadata of the city and county data center materials into their respective database services through their respective process services, and respectively transfer the high-code files, low-code files, key frame files, manuscripts and other physical files of the city and county media asset system materials to their respective storage services through their respective transmission services, thereby achieving full synchronization of metadata, source files and manuscript data.

[0066] This step uses UDP transmission to transfer the material to the peer storage, which does not occupy the migrator resources and can avoid competing with daily inbound and outbound migration tasks for resources, facilitating independent management and operation and maintenance.

[0067] S7. The materials of the city and county data centers are released to the provincial media asset system: After the provincial data master center receives the materials with the city and county data center logo, the system logo service of the provincial data master center analyzes the metadata of the materials and finds that they are not data of this level, and no longer triggers the synchronization instruction. At the same time, the low-code files of the materials of the city and county data centers are automatically released, and the metadata and low-code files of the materials of the city and county data centers are released to the provincial media asset system through the migration service and process service.

[0068] S8. The provincial media asset system initiates new metadata synchronization: After the provincial media asset system completes intelligent identification, manual cataloging and calibration and other media asset service calls, it forms new metadata, and then initiates a new metadata synchronization request, and publishes the new metadata to the provincial data master center through the process service. After receiving the metadata synchronization request, the provincial data master center confirms that the material already exists in the database service of the provincial data master center based on the material's unique identifier objectID, so it only needs to update the metadata to the material, and no longer migrate the physical file. The material is set as the metadata of the provincial data master center through the system identification service, and the message is published to the message mechanism service at this level.

[0069] This step uses objectID as the judgment basis. Materials with the same objectID are no longer re-entered into the database. Instead, only metadata is updated, which reduces file migration time and avoids the loss of operation records after material deletion.

[0070] S9. Message monitoring at the provincial data master center: As a consumer, the message service at the provincial data master center monitors the Kafka messages in the message mechanism service and consumes them.

[0071] S10. The provincial data master center initiates a synchronization request: The message service of the provincial data master center initiates a synchronization request to the process service at this level.

[0072] S11. The provincial data main center sends synchronization tasks: After the process service of the provincial data main center accepts the synchronization request sent by the message service at this level, it sends synchronization tasks to the synchronization services of the provincial data sub-center and municipal and county data centers respectively.

[0073] Specifically, the provincial data sub-centers and municipal and county data centers first execute user data synchronization tasks through their respective user synchronization services to ensure the consistency of user data in each data center; then they accept synchronization tasks issued by the message services of data centers at all levels through their respective process services and cache services.

[0074] S12. Material transmission and metadata update of the provincial data master center: During the synchronization process, the municipal and county data centers, provincial data sub-centers, and provincial data sub-centers first perform clock verification through the clock synchronization service to ensure that the transmission time is consistent; then the provincial data sub-centers and municipal and county data centers use their own process services to store the metadata of the provincial data master center materials into their own database services, and use their own transmission services to transfer the key frame files, manuscripts, etc. of the provincial data master center materials to their own storage services to update the metadata and physical files. At the same time, the system identification services of the provincial data sub-centers and municipal and county data centers analyze that the metadata of the provincial data master center materials is not data at this level, and no longer trigger synchronization, and the process ends.

[0075] This step fully considers the business characteristics and no longer transmits high- and low-code physical files. It only transmits metadata, key frames, and manuscripts, saving migration time.

[0076] The prerequisite for the above steps is that the municipal and county data centers, provincial data main centers, and provincial data sub-centers configure administrator permissions and the synchronization process of the data centers at this level through user synchronization services.

[0077] It should be understood that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. For those skilled in the art, the technical solutions described in the above embodiments can be modified, or some of the technical features therein can be replaced by equivalents; and all these modifications and replacements should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A media resource synchronization platform under a remote multi-active architecture, characterized by: It includes synchronization services and basic services. The synchronization services include core services, synchronization basic services and supporting services. The core services include process services, transmission services and message services. The process service is used to coordinate the message process and the transmission process to synchronize business data through the process process; The transmission service is used to flexibly deploy the transmission migration executor to complete the business capabilities of batch data synchronization through multi-threaded pooling and high concurrency technology, realize multi-threaded and high-efficiency data transmission, and achieve real-time synchronization capabilities under a stable network environment; the message service is used to use the Kafka message platform as the basic support, design a flexible message subscription topic method, store data information of the business platform, and use the constructed message process to asynchronously read the accumulated message queue and asynchronously read the accumulated tasks to achieve data consistency in each production environment under the multi-active mode and provide disaster recovery capabilities.

2. According to the media resource synchronization platform under the remote multi-active architecture of claim 1, it is characterized by: The basic synchronization services include user synchronization service, system identification service and message mechanism service; the user synchronization service is used to provide the administrator with basic data configuration, customized process, message configuration, user synchronization task viewing and task redo functions of the synchronization service; the system identification service is a unique identifier of the data center, which is used to identify and confirm the source of data; the message mechanism service is used to build point-to-point synchronization mode and ring synchronization mode to realize the ability to synchronize multiple active applications in multiple data centers in different locations.

3. According to the media resource synchronization platform under the remote multi-active architecture of claim 1, it is characterized by: The supporting services include clock synchronization service, rights management service and migration service; the clock synchronization service is used for clock verification to ensure the reliability of transmission time; The permission management service is used to allocate and verify user permissions and verify whether the user can initiate synchronization or manage synchronization tasks; the migration service is used to migrate transferable files from data center I to data center II.

4. According to claim 1, a media resource synchronization platform under a remote multi-active architecture is characterized in that: The basic services include storage services, database services and cache services; the storage services are used to store files and their metadata information; the database services include distributed relational databases and document databases to accommodate various metadata types; The cache service, on the one hand, acts as a cache buffer for the data interface, responding to frequent query requests with cached hot data, alleviating the query pressure of relational and non-relational databases, and providing fast reading function when users search; on the other hand, it acts as a shared storage area for service session data, ensuring that the service can continue to run in the state before the switch when service switching occurs.

5. A method for calling media resources under a remote multi-active architecture, using the media resource synchronization platform described in any one of claims 1 to 4, wherein the remote multi-active architecture includes a city and county data center, a provincial data master center, and a provincial data sub-center, and the media resource calling method includes the following steps: S1. The materials of the municipal and county media resource systems are stored in the municipal and county data centers, triggering two-way synchronization instructions between the provincial data master center and the provincial data sub-center; S2. City and county users initiate media resource calls: City and county users initiate batch or single calls to the provincial data center media resources for materials in the city and county data center, and publish the message to the message mechanism service; S3, city and county data center message monitoring; S4, the city and county data center initiates a synchronization request; S5. The city and county data centers send synchronization tasks to the provincial data main center and provincial data sub-center respectively, and the provincial data main center and provincial data sub-center receive the synchronization tasks; S6. The provincial data main center and provincial data sub-center will transfer the materials of the municipal and county data centers into the database and store them; S7. Materials from city and county data centers are sent to the provincial media resource system; S8. The provincial media asset system initiates a new metadata synchronization request. The provincial data master center updates the metadata to the material of the database service and publishes the message to the message mechanism service. S9, provincial data master center message monitoring; S10. The provincial data master center initiates a synchronization request; S11. The provincial data main center sends synchronization tasks to the provincial data sub-center and the municipal and county data centers respectively, and the provincial data sub-center and the municipal and county data centers receive the synchronization tasks; S12. Material transmission and metadata update at the provincial data master center.

6. The method for calling media resources in a remote multi-active architecture according to claim 5, characterized in that: In step S1, when the city and county data center accepts the materials from the city and county media asset system, the metadata carried by the materials themselves is stored in the database service of the city and county data center. At the same time, the system identification service of the city and county data center analyzes the metadata of the materials as data at this level and identifies them as metadata of the city and county data center, which triggers the two-way synchronization instructions of the provincial data main center and the data sub-center.

7. The method for calling media resources in a remote multi-active architecture according to claim 5, characterized in that: In step S2, before initiating, it is first determined through permission management whether the user has the calling permission. If not, the initiation cannot be made; if so, the initiation is successful.

8. The method for calling media resources in a remote multi-active architecture according to claim 5, characterized in that: In step S5 and step S11, before receiving synchronization tasks, the provincial data main center, provincial data sub-center, and municipal and county data centers first execute user data synchronization tasks through their respective user synchronization services to ensure the consistency of user data in each data center; then they accept synchronization tasks issued by the message services of data centers at all levels through their respective process services and cache services.

9. The method for calling media resources in a remote multi-active architecture according to claim 5, characterized in that: In step S6, the city and county data center materials are transferred into the library and stored specifically in that the provincial data main center and the provincial data sub-center import the metadata of the city and county data center materials into their respective database services, and respectively transfer the source files and manuscript data of the city and county media asset system materials to their respective storage services through their respective transmission services, thereby realizing full synchronization of metadata, source files and manuscript data.

10. The method for calling media resources in a remote multi-active architecture according to claim 5, characterized in that: Specifically, step S12 is that the municipal and county data centers, provincial data sub-centers and provincial data sub-centers first perform clock verification through the clock synchronization service to ensure that the transmission time is consistent; then the provincial data sub-center and the municipal and county data centers use their respective process services to store the metadata of the provincial data main center materials into their respective database services, and use their respective transmission services to transfer the physical files of the provincial data main center materials to their respective storage services to achieve the update of metadata and physical files.

Images