CN110933184B - Resource publishing platform and resource publishing method - Google Patents
Resource publishing platform and resource publishing method Download PDFInfo
- Publication number
- CN110933184B CN110933184B CN201911302584.7A CN201911302584A CN110933184B CN 110933184 B CN110933184 B CN 110933184B CN 201911302584 A CN201911302584 A CN 201911302584A CN 110933184 B CN110933184 B CN 110933184B
- Authority
- CN
- China
- Prior art keywords
- resource
- cdn
- machine
- publishing
- released
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- 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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a resource publishing platform and a resource publishing method. Wherein, this resource issuing platform includes: the system comprises a resource front end, a service machine, at least one Content Delivery Network (CDN) source machine and a CDN front end machine cluster which is configured corresponding to the CDN source machine; the service machine screens the resources to be released from the uploaded resources according to a resource releasing request initiated by a resource front end and synchronizes the resources to be released to the CDN source machine; and the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released, and releases the optimized resource to be released to a CDN front-end machine cluster which is correspondingly configured. According to the technical scheme provided by the embodiment of the invention, the two processes of resource uploading and resource publishing are separated, so that the safety of resource publishing is ensured, other users can conveniently obtain the resource to be published in the most matched external access format in the CDN front-end computer cluster, the convenience of subsequent external access is improved, and the process of resource publishing is simplified.
Description
Technical Field
The embodiment of the invention relates to the field of online management of internet resources, in particular to a resource publishing platform and a resource publishing method.
Background
With the rapid development of internet technology, the application of Content Delivery Networks (CDNs) is becoming more and more widespread.
At present, an existing CDN network mainly supports resource interaction between a user terminal and a closest CDN front-end node in the CDN network, so when the CDN network is used to perform online delivery of internet resources, a developer generally directly uploads the resources to the closest CDN front-end node in the CDN network to the user terminal where the developer is located, or uploads the resources to the closest CDN front-end node after uniformly packaging the resources and front-end service codes, and then the CDN front-end node spreads and delivers the uploaded resources throughout the CDN network.
The risk of manually operating resource delivery by research personnel is high, so that resource delivery errors are easily caused, meanwhile, the resource delivery errors are required to be compiled and then delivered when the resource delivery errors are uniformly packed with front-end service codes, so that the delivery process is complicated, and the CDN front-end node is used as user-oriented resource providing equipment in a CDN (content delivery network) and is mainly used for realizing edge propagation and storage of resources, so that the delivered resources cannot be actively maintained when the resources are abnormal.
Disclosure of Invention
The embodiment of the invention provides a resource publishing platform and a resource publishing method, which can simplify the resource publishing process and improve the security of resource publishing.
In a first aspect, an embodiment of the present invention provides a resource publishing platform, where the platform includes: the system comprises a resource front end, a service machine, at least one CDN source machine and a CDN front end machine cluster which is configured corresponding to the CDN source machine; wherein the content of the first and second substances,
the service machine synchronizes the resource to be released to the CDN source machine according to the resource releasing request initiated by the resource front end;
and the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released, and releases the optimized resource to be released to a CDN front-end machine cluster which is correspondingly configured.
In a second aspect, an embodiment of the present invention provides a resource publishing method, which is applied to the resource publishing platform in the first aspect, and the method includes:
the resource front end generates a corresponding resource publishing request according to the triggering operation acted on a resource publishing inlet of the resource to be published by a publishing user;
the service machine synchronizes the resource to be released to the CDN source machine according to the resource releasing request;
the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released, releases the optimized resource to be released to a CDN front-end machine cluster which is correspondingly configured, and simultaneously issues a corresponding cache clearing instruction to the CDN front-end machine cluster;
and the CDN front-end machine cluster eliminates cached resources which are the same as the resource identifiers of the resources to be released according to the cache elimination instruction.
The embodiment of the invention provides a resource delivery platform and a resource delivery method, wherein a corresponding service machine is additionally arranged between a resource front end and a CDN source machine, the service machine is used for storing all resources which are uploaded by the resource front end before, at the moment, the resource front end initiates a resource delivery request aiming at a certain to-be-delivered resource in the uploaded resources, the to-be-delivered resource is synchronized to the CDN source machine through the service machine, the resource front end does not need to directly perform resource interaction with a CDN network, two processes of resource uploading and resource delivery are separated, the safety of resource delivery is ensured, meanwhile, the CDN source machine optimizes the external access format of the to-be-delivered resource according to the attribute information of the to-be-delivered resource, and delivers the optimized to-be-delivered resource to the CDN front end machine cluster which is correspondingly arranged, so that other users can conveniently obtain the to-be-delivered resource in the most matched external access format in the CDN front end machine cluster, the convenience of subsequent external access is improved, and the subsequent external access is not required to be uniformly packaged and compiled with the front-end service code and then distributed, so that the resource distribution process is simplified.
Drawings
Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments thereof, made with reference to the following drawings:
fig. 1A is a schematic architecture diagram of a resource publishing platform according to an embodiment of the present invention;
fig. 1B is a schematic architecture diagram of another resource publishing platform according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a resource publishing platform according to a second embodiment of the present invention;
fig. 3 is a flowchart of a resource issuing method according to a third embodiment of the present invention;
fig. 4 is a flowchart of a resource issuing method according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.
Example one
Fig. 1A is a schematic architecture diagram of a resource publishing platform according to an embodiment of the present invention. The embodiment can be applied to any situation of online publishing of internet resources. Specifically, referring to fig. 1A, the resource publishing platform 10 may include: the CDN resource server comprises a resource front end 110, a server machine 120, at least one CDN origin machine 130, and a CDN front end machine cluster 140 configured to correspond to the CDN origin machine 130.
The service machine 120 screens out resources to be delivered from the uploaded resources according to a resource delivery request initiated by the resource front end 110, and synchronizes the resources to the CDN source machine 130; the CDN source machine 130 optimizes an external access format of the resource to be delivered according to the attribute information of the resource to be delivered, and delivers the optimized resource to be delivered to the CDN front-end machine cluster 140 configured correspondingly.
Specifically, in this embodiment, for the resource publishing platform 10, a front-end display interface of the resource publishing platform 10 for the publishing user may be designed by analyzing various operation functions existing in the resource publishing process, at this time, the resource front end 110 may refer to a user terminal where each type of publishing user is located, and the user terminal is configured with an application program corresponding to the resource publishing platform 10 in advance; the resource front end 110 is configured to display, in the platform interface, each resource operation entry for opening the right to the publishing user according to the login identifier of the publishing user, and generate a corresponding service request according to a trigger operation of the publishing user at the resource operation entry.
For example, when detecting that an issuing user accesses the resource issuing platform 10, the resource front end 110 needs to log in the resource issuing platform 10 through a platform account of the issuing user, at this time, it is first determined in a local cache whether an identity authentication identifier (for example, a token identifier) returned after the issuing user has logged in the resource issuing platform 10 can be found, and if yes, it is determined that the issuing user has logged in, and the resource front end directly enters a platform interface under the resource issuing platform 10; if not, jumping to an Office Automation (OA) login system corresponding to the resource publishing platform 10, inputting a platform account number of the publishing user for login, receiving a returned identity authentication identifier (such as a token identifier) after the login is successful, and entering a platform interface of the resource publishing platform 10; meanwhile, after entering the corresponding platform interface, the resource front end 110 determines, according to the identity authentication identifier of the publishing user, a resource operation entry that the resource publishing platform 10 opens the right to the publishing user, where the resource operation entry may be a resource uploading entry, a resource publishing entry, a resource rollback entry, and the like, and at this time, the publishing user in this embodiment may be any user with a publishing right, such as a scientific research worker or a non-scientific research worker in a resource background, for example, the resource publishing platform 10 only supports a visitor user to access the published resource, and cannot upload or publish a new resource, but supports a worker in a background scientific research department to upload and publish a certain resource; at this time, the publisher may execute the corresponding trigger operation on each resource operation entry of the right opened in the platform interface displayed by the resource front end 110, so that the resource front end 110 generates a matching service request according to the trigger operation of the publisher on the corresponding resource operation entry, for example, generates a corresponding resource upload request according to the trigger operation acting on the resource upload entry or generates a corresponding resource publishing request according to the trigger operation acting on the resource publishing entry.
In addition, in this embodiment, when the resource front end 110 initiates a corresponding resource publishing request to a certain resource to be published according to a triggering operation of a publishing user acting on a resource publishing entry in a platform interface, the resource to be published is determined as a resource that the resource publishing platform 10 has successfully uploaded, otherwise, the resource cannot be published; at this time, a corresponding service machine 120 is additionally arranged between the resource front end 110 and the CDN source machine 130, all resources that have been successfully uploaded by the resource front end 110 before are stored by the service machine 120, when resource delivery is performed, a resource to be delivered may be directly selected from the uploaded resources for delivery, and it is not necessary to perform the resource uploading and delivery processes at the same time, so that the resource uploading process is isolated from the resource delivery process, security and independence of resource delivery are ensured, a preview function of the resource to be delivered in the resource front end 110 is also implemented, and uniform delivery of multiple resources to be delivered in the uploaded resources is also implemented, and high availability of resource delivery is improved.
Further, when receiving a resource delivery request initiated by a certain resource to be delivered from an uploaded resource displayed in the platform interface by the resource front end 110, the service machine 120 firstly screens out the resource to be delivered specified in the current delivery from the pre-stored uploaded resource according to a resource identifier of the resource to be delivered carried in the resource delivery request, and synchronously sends the resource to be delivered to CDN source machines in each pre-configured CDN network, and the CDN source machine delivers the resource to be delivered to a CDN front end cluster configured corresponding to the CDN source machine for external user access, thereby implementing online delivery of the resource to be delivered and facilitating external access of other users to the resource to be delivered.
In this embodiment, in order to ensure that resources are delivered in a global scope, a corresponding architecture is performed on a globally set location of the CDN origin machine 130 and the CDN front-end cluster 140 configured correspondingly in the CDN network, as shown in fig. 1B, because a delivery user who has a demand for online delivering of resources is usually a worker of a certain resource development project, the resource front end 110 where such a delivery user is located is generally uniformly located in a certain fixed area, for example, an area where a certain scientific research company that has a resource development project and needs to online deliver resources is located; at this time, in order to ensure efficient resource interaction between the resource front end 110 and the CDN origin 130 through the service machine 120, in this embodiment, first, a location area of the resource front end 110 where a large number of delivering users are located is determined, and a region is selected nearby based on the location area of the resource front end 110, a plurality of CDN origin machines 130 are respectively set at different locations in the region, at this time, a CDN network where each CDN origin machine 130 is located may face external users in different regions around the world, at this time, according to a global region where the CDN network where each CDN origin machine 130 is located faces a user in a european region, a CDN front end cluster 140 including a corresponding number of CDN origin machines may be respectively configured for each CDN origin machine 130 in a corresponding region around the world, for example, a CDN network where the first CDN origin machine 130 is located faces a user in a european region, a CDN front end cluster 140 corresponding to the first CDN origin machine 130 is set in a european region, if the CDN network where the second CDN origin machine 130 is located faces a user in an asian area, a CDN front-end machine cluster 140 corresponding to the second CDN origin machine 130 is set in the asian area; at this time, because the set distance between the CDN origin machine 130 and the CDN front-end cluster 140 configured correspondingly is long, in order to ensure the security of resource interaction between the CDN origin machine 130 and the CDN front-end cluster 140 configured correspondingly and avoid resource omission caused by remote interaction, in this embodiment, a series of load algorithm strategies, global machine node deployment, transparent routing and other measures are adopted between the CDN origin machine 130 and the CDN front-end cluster 140, so that the efficiency of resource interaction between the CDN origin machine 130 and the CDN front-end cluster 140 is improved.
At this time, after receiving the resource to be delivered synchronized by the service machine 120, the CDN source machine 130 firstly analyzes the attribute information of the resource to be delivered, determines the type of the resource to be delivered, and further optimizes the external access format of the resource to be delivered according to the attribute information, for example, if the resource to be delivered is a picture resource in png or ipg format, the picture resource may be converted into a webp format, or the picture resource may be converted into pictures in different definition sizes and stored by using different resource access paths; the subsequent CDN source machine 130 uniformly delivers the optimized resources to be delivered in different external access formats to the CDN front-end machine cluster 140 configured corresponding to the CDN source machine 130, so as to implement global delivery of the resources to be delivered, which is convenient for a global user to select a delivered resource to download by logging in the resource delivery platform 10, and at this time, each resource that has been successfully delivered in a corresponding external access format can be accessed in a CDN front-end machine configured closest according to the network conditions of the global user, for example, a regional user with a poor network environment can access a picture with lower definition, and a regional user with a better network environment can access a picture with higher definition, thereby ensuring access diversity when other external users access the corresponding resources.
In addition, since some errors may exist in a resource to be delivered after a certain resource to be delivered is successfully delivered, at this time, an accurate resource to be delivered needs to be delivered again, and in order not to change an access path of the same resource to be delivered, the CDN origin machine 130 in this embodiment may be further configured to, when delivering the optimized resource to be delivered to the CDN front-end cluster 140 configured correspondingly: issuing a corresponding cache removal instruction to the CDN front-end cluster 140; the CDN front-end cluster 140 removes the cached resource that is the same as the resource identifier of the resource to be delivered according to the cache removal instruction.
Specifically, when the CDN origin machine 130 delivers the resource to be delivered to the CDN front-end machine cluster 140 configured correspondingly, it first needs to determine whether the resource to be delivered is cached in the CDN front-end machine cluster 140, and at this time, a corresponding cache removal instruction is issued to the CDN front-end machine cluster 140, so as to remove the resource to be delivered cached before in the cached resource; the CDN front-end cluster 140 screens out and clears the cached resource that is the same as the resource identifier of the resource to be delivered from all cached resources according to the cache clearing instruction, and then locally caches the resource to be delivered that is delivered this time, so as to ensure the uniqueness of the resource to be delivered cached in the CDN front-end cluster 140, and therefore when the CDN source 130 delivers the same resource to be delivered multiple times, it is not necessary to change the resource identifier of the resource to be delivered in the CDN front-end cluster 140 in order to distinguish caches, and at the same time, ensure the consistency of access paths of the re-delivered resource to be delivered in the CDN front-end cluster 140.
In the technical solution provided in this embodiment, a corresponding service machine is additionally configured between a resource front end and a CDN source machine, where the service machine is used to store all resources that have been uploaded by the resource front end before, and at this time, the resource front end initiates a resource delivery request for a certain resource to be delivered in the uploaded resources, synchronizes the resource to be delivered to the CDN source machine through the service machine, and does not need to directly perform resource interaction between the resource front end and the CDN network, so that two processes of resource uploading and resource delivery are isolated, and the security of resource delivery is ensured, and at the same time, the source machine optimizes an external access format of the resource to be delivered according to attribute information of the resource to be delivered, and delivers the optimized resource to the CDN front end cluster configured correspondingly, so that other users can obtain the resource to be delivered in a best-matched external access format in the CDN front end cluster, and improve convenience of subsequent external access, the resource is not required to be uniformly packaged and compiled with a front-end service code and then distributed, so that the resource distribution flow is simplified.
Example two
Fig. 2 is a schematic structural diagram of a resource publishing platform according to a second embodiment of the present invention. The embodiment is optimized on the basis of the technical scheme provided by the embodiment. Referring to fig. 2, the resource delivery platform 20 may include a resource front end 210, a service machine 220, at least one CDN origin machine 230, and a CDN front end machine cluster 240 configured to correspond to the CDN origin machine 230.
Specifically, when the resource front end 210 selects the resource to be published, it selects from the uploaded resources stored in the service machine 220, and at this time, it is first required to ensure that the resource to be published is uploaded to the service machine 220 for each resource to be published, so the resource publishing platform 20 in this embodiment supports the resource publishing operation and the resource uploading operation, at this time, after the publishing user successfully logs in the resource publishing platform 20, the resource front end 210 may display a platform interface that opens a corresponding uploading right to the publishing user, and the publishing user may execute the uploading operation of a certain resource by triggering a corresponding resource uploading entry on the platform interface. At this time, the embodiment may implement uploading of the resource in a manner of transmitting a binary stream by using a preset egg-multicast + Formdata format, so that the resource to be uploaded may be any type of resource, the type of the resource to be uploaded is not limited in the embodiment, and subsequently, online publishing of any type of resource may also be implemented.
At this time, when detecting the trigger operation of the publishing user on the resource uploading entry on the platform interface, the resource front end 210 first needs to verify whether the publishing user has the authority to upload the resource type, and generates a corresponding resource uploading request after the authority verification, where the resource uploading request carries the resource to be uploaded; thus, the service machine 220 can also be used to: according to a resource uploading request initiated by the resource front end 210, storing the resource to be uploaded into a preset CDN mapping area, updating the resource identifier of the resource copy to be uploaded according to the uploading timestamp of the resource to be uploaded, and storing the updated resource copy to be uploaded into a preset history recording area.
Specifically, after receiving the resource to be uploaded in the resource uploading request initiated by the resource front end 210, the service machine 220 correspondingly stores the resource to be uploaded in a preset CDN mapping area for subsequent resource delivery in the CDN network; meanwhile, in order to enable the publishing user to preview the upload record of each resource in the resource front end 210, and after a certain uploaded resource is successfully published, a history record area for storing the history upload record of each resource may be additionally set in this embodiment, at this time, after receiving the resource to be uploaded in the resource upload request initiated by the resource front end 210, the service machine 220 generates a copy of the resource to be uploaded with completely consistent content for the resource to be uploaded, at this time, stores the resource to be uploaded in a preset CDN mapping area, and at the same time, modifies the resource identifier of the copy of the resource to be uploaded according to the upload timestamp of the resource to be uploaded, for example, renames the copy of the resource to be uploaded by adding an upload timestamp in the original resource name, and stores the renamed copy of the resource to be uploaded in the preset history record area, subsequent publishers may look up different upload records for an uploaded resource named by different upload timestamps in the history zone by performing a preview operation on the resource front end 210 for that uploaded resource.
Further, in this embodiment, the service machine 220 may include a service host 221 and a service standby machine 222, where the service host 221 and the service standby machine 222 cooperate to execute each service request initiated by the resource front end 210, at this time, the resource front end 210 will report the initiated resource upload request to the service host 221, the service host 221 stores the resource to be uploaded in a preset CDN mapping region according to the resource upload request, stores a corresponding copy of the resource to be uploaded in a preset history recording region, and synchronizes the resource to be uploaded and the copy of the resource to be uploaded to the service standby machine 222 for storage, so as to ensure consistency between the service host 221 and the service standby machine 222, so that when the service host 221 fails, the service standby machine 222 can timely replace the service host 221 to execute a corresponding resource publishing operation, thereby avoiding a failure in a resource publishing process.
Meanwhile, the CDN mapping area and the history recording area preset in this embodiment may be commonly disposed on the service host 221 and the service standby 222, that is, the service host 221 and the service standby 222 are both simultaneously disposed with the CDN mapping area and the history recording area, and directly store the resource to be uploaded and the copy of the resource to be uploaded on the physical machine; or, because the physical machine has the problems of limited memory, large probability of error deletion due to coexistence of multiple services, and high read-write cost, in this embodiment, in order to avoid many limitations of the physical machine storage, the CDN mapping area and the history recording area may be commonly disposed in the cloud system, and the cloud system stores the resource to be uploaded and the copy of the resource to be uploaded, which are uploaded by the resource front end 210, so that when the service machine 220 fails or needs to be migrated or expanded to another service machine, the copy operation of the uploaded resource does not need to be performed on the service machine 220, thereby timely and easily achieving alternate replacement of the service machine 220.
In addition, in order to ensure load balancing and high availability of the service host 221 and the service standby 222, the resource distribution platform 20 of this embodiment may further include: a proxy server 250 communicatively coupled to the resource front-end 210 and the server 220, respectively; at this time, the proxy server 250 is provided with a hot update process and a smooth upgrade process, the resource front end 210 first sends any service request initiated by the publishing user on the platform interface to the proxy server 250, and the proxy server 250 detects the respective current service operation loads of the two physical machines under the service machine 220, so as to determine the service host 221 and the service standby machine 222 with balanced loads from the two physical machines.
Further, in an actual resource issuing service, there may be multiple uploading operations for the same resource, if the version currently issued by the resource has a problem, the resource needs to be rolled back to the latest historical version, at this time, the resource front end 210 may generate a corresponding resource rolling back request according to a triggering operation of a resource rolling back entry acted on the platform interface by the issuing user, and send the corresponding resource rolling back request to the service machine 220, where the resource rolling back request carries a corresponding resource to be rolled back, at this time, the service machine 220 may find out the resource to be rolled back specified by the resource rolling back request from the history recording area, and use the resource to be rolled back as a new resource to be issued, and execute the same resource issuing operation in the CDN source machine 230 and the CDN front end cluster 240 configured correspondingly.
It should be noted that, before the resource front end 210 generates the resource rollback request, the publishing user may determine in advance that the published target resource needs to be rolled back due to an error, at this time, the publishing user may preview the historical upload record of the target resource by triggering the resource preview entry of the target resource on the platform interface, at this time, when the resource front end 210 detects that the publishing user performs a preview operation on the target resource, the historical upload record of the target resource may be found from the historical upload record area according to the resource identifier of the target resource and according to the upload time stamp, and is displayed in the platform interface, the publishing user selects the resource to be rolled back to which the target resource needs to be rolled back from the historical upload record, and executes a corresponding rollback operation, thereby implementing the rollback of the target resource and maintaining the published resource.
According to the technical scheme provided by the embodiment, the resources to be uploaded and the copies of the resources to be uploaded are respectively stored through the CDN mapping area and the history recording area in the service machine, the resources to be released are selected from the uploaded resources through the service machine subsequently and released to the CDN source machine and the CDN front-end machine cluster configured correspondingly, so that the two processes of resource uploading and resource releasing are separated, the problems that the resources are directly covered or replaced by the resource releasing operation and are directly accessed to the resources externally are avoided, the manageability of resource uploading and the safety of external access are effectively improved, meanwhile, the corresponding resource rollback operation can be executed through the copies of the resources to be uploaded stored in the history recording area, and the accuracy of resource releasing and the safety of external access are guaranteed.
EXAMPLE III
Fig. 3 is a flowchart of a resource issuing method according to a third embodiment of the present invention. The present embodiment can be applied to the resource publishing platform provided in any of the above embodiments, and mainly describes a resource publishing process of any resource in uploaded resources. Referring to fig. 3, the present embodiment may mainly include the following steps:
and S310, the resource front end generates a corresponding resource publishing request according to the triggering operation of the publishing user acting on the resource publishing entrance of the resource to be published.
Specifically, the resource front end may display, in the platform interface, each resource operation entry opening the authority to the publishing user according to the login identifier of the publishing user, and generate a corresponding service request according to a trigger operation of the publishing user at the resource operation entry; at this time, when the resource front end initiates a corresponding resource delivery request to a certain resource to be delivered according to a triggering operation of a delivery user acting on a resource delivery inlet in a platform interface, the resource to be delivered is determined as a resource which has been successfully uploaded by the resource delivery platform, and the resource delivery request is sent to the service machine, and the service machine screens out the resource to be delivered to deliver in the CDN source machine and the CDN front end machine cluster configured correspondingly.
And S320, the resource front end sends the resource issuing request to the service machine.
And S330, the service machine screens the resources to be issued from the uploaded resources according to the resource issuing request.
Specifically, all resources that have been successfully uploaded by the resource front end before are stored in the service machine, at this time, after a resource delivery request initiated by the resource front end is received, a resource to be delivered specified by the resource delivery request can be screened from the stored uploaded resources, and subsequent CDN source machines and a cluster of CDN front end machines configured correspondingly perform delivery.
S340, the service machine synchronizes the resource to be released to the CDN source machine.
And S350, the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released.
In this embodiment, after receiving the resource to be delivered synchronized by the service machine, the CDN source machine first analyzes the attribute information of the resource to be delivered, determines the type of the resource to be delivered, and then optimizes the external access format of the resource to be delivered according to the attribute information, for example, if the resource to be delivered is a png or ipg-formatted picture resource, the picture resource may be converted into a webp format, or the picture resource may be converted into pictures with different definition sizes and stored by using different resource access paths, so that the subsequent CDN source machine uniformly delivers the optimized resource to be delivered in different external access formats to a CDN front-end machine cluster configured corresponding to the CDN source machine, thereby implementing global delivery of the resource to be delivered.
And S360, the CDN source machine issues the optimized resources to be issued to the CDN front-end machine cluster configured correspondingly, and simultaneously issues a corresponding cache clearing instruction to the CDN front-end machine cluster.
Optionally, the CDN source machine uniformly delivers the optimized resources to be delivered in different external access formats to a CDN front-end cluster configured corresponding to the CDN source machine, so that a global user can select a delivered resource to download by logging in the resource delivery platform 10, and at this time, each resource that has been successfully delivered in a corresponding external access format can be accessed in a CDN front-end configured closest to the global user according to the network condition of the global user, for example, a regional user with a poor network environment can access a picture with low definition, and a regional user with a better network environment can access a picture with high definition, thereby ensuring access diversity when other external users access the corresponding resource.
However, after a certain resource to be delivered is successfully delivered, it may be found that some errors exist in the resource to be delivered, at this time, an accurate resource to be delivered needs to be delivered again, and in order to not change an access path of the same resource to be delivered, the CDN source machine in this embodiment may issue a corresponding cache clearing instruction to the CDN front-end cluster while delivering the optimized resource to be delivered to the CDN front-end cluster configured correspondingly, so as to determine whether the resource to be delivered is cached before the CDN front-end cluster, so that the CDN front-end cluster clears the resource to be delivered cached before in the cached resource according to the cache clearing instruction.
S370, the CDN front-end cluster removes, according to the cache removal instruction, the cached resource that is the same as the resource identifier of the resource to be delivered.
Specifically, when receiving a to-be-delivered resource and a cache clearing instruction sent by a CDN source, a CDN front-end cluster screens, according to the cache clearing instruction, cached resources that are the same as a resource identifier of the to-be-delivered resource from all cached resources and clears the cached resources, and then locally caches the to-be-delivered resource that is delivered this time, so that the uniqueness of the to-be-delivered resource cached in the CDN front-end cluster is ensured, and therefore, when the CDN source delivers the same to-be-delivered resource multiple times, it is not necessary to change the resource identifier of the to-be-delivered resource in the CDN front-end cluster in order to distinguish caches, and meanwhile, ensure the consistency of access paths of the to-be-delivered resource in the CDN front-end cluster.
In the technical solution provided in this embodiment, a corresponding service machine is additionally configured between a resource front end and a CDN source machine, where the service machine is used to store all resources that have been uploaded by the resource front end before, and at this time, the resource front end initiates a resource delivery request for a certain resource to be delivered in the uploaded resources, synchronizes the resource to be delivered to the CDN source machine through the service machine, and does not need to directly perform resource interaction between the resource front end and the CDN network, so that two processes of resource uploading and resource delivery are isolated, and the security of resource delivery is ensured, and at the same time, the source machine optimizes an external access format of the resource to be delivered according to attribute information of the resource to be delivered, and delivers the optimized resource to the CDN front end cluster configured correspondingly, so that other users can obtain the resource to be delivered in a best-matched external access format in the CDN front end cluster, and improve convenience of subsequent external access, the resource is not required to be uniformly packaged and compiled with a front-end service code and then distributed, so that the resource distribution flow is simplified.
Example four
Fig. 4 is a flowchart of a resource issuing method according to a fourth embodiment of the present invention. The present embodiment can be applied to the resource publishing platform provided in any of the above embodiments, and mainly describes a resource uploading and publishing process of any resource in uploaded resources. Referring to fig. 4, the present embodiment may mainly include the following steps:
s401, the resource front end logs in the resource publishing platform according to the identity of the publishing user, and displays a corresponding platform interface after the login is successful.
And each resource operation entry for opening the authority to the publishing user is displayed in a platform interface at the front end of the resource. Specifically, when detecting that a publishing user accesses the resource publishing platform, the resource front end needs to log in the resource publishing platform through a platform account of the publishing user, at this time, it is first determined in a local cache whether an identity authentication identifier (for example, a token identifier) returned after the publishing user logs in the resource publishing platform can be found, and if yes, it is determined that the publishing user logs in, and the resource front end directly enters a platform interface under the resource publishing platform; if the identity authentication identifier does not exist, jumping to an OA login system corresponding to the resource publishing platform, inputting a platform account number of the publishing user for login, receiving a returned identity authentication identifier (such as a token identifier) after login is successful, and entering a platform interface of the resource publishing platform.
S402, the resource front end generates a resource uploading request of the resource to be issued according to the triggering operation of the issuing user at the resource uploading entrance.
Optionally, after entering a corresponding platform interface, the resource front end determines, according to the identity authentication identifier of the publishing user, a resource operation entry for opening the right to the publishing user by the resource publishing platform, where the resource operation entry may be a resource uploading entry, a resource publishing entry, a resource rollback entry, and the like, and at this time, the publishing user in this embodiment may be any user with the publishing right, such as a scientific research worker or a non-scientific research worker in a resource background, for example, the resource publishing platform only supports a visitor user to access the published resource, and cannot upload or publish a new resource, and supports a worker in a background scientific research department to upload and publish a certain resource; at this time, the publisher may execute the corresponding trigger operation on each resource operation entry of the authority opened in the platform interface displayed at the resource front end, so that the resource front end generates a matched service request according to the trigger operation of the publisher on the corresponding resource operation entry.
At this time, when the resource front end selects the resource to be published, the resource front end selects from uploaded resources stored on the service machine, and at this time, it is first required to ensure that each resource to be published is uploaded to the service machine, so the resource publishing platform in this embodiment supports the resource uploading operation in addition to the resource publishing operation, and at this time, after the publishing user successfully logs in the resource publishing platform, the resource front end can display a platform interface which opens a corresponding uploading right to the publishing user, and the publishing user can execute the uploading operation of the resource to be published by triggering a corresponding resource uploading entry on the platform interface; when detecting the triggering operation of the publishing user on the resource uploading entry on the platform interface, the resource front end firstly needs to verify whether the publishing user has the authority to upload the resource type, generates a corresponding resource uploading request after the authority verification, and sends the resource uploading request to the service host in the service machine.
And S403, the resource front end sends the resource uploading request to the service machine.
S404, the service host in the service machine stores the resource to be released into a preset CDN mapping area according to the resource uploading request, updates the resource identifier of the resource copy to be released according to the uploading timestamp of the resource to be released, and stores the updated resource copy to be released into a preset history recording area.
Specifically, in order to enable a publishing user to preview an upload record of each resource in a resource front end, and to execute a corresponding maintenance operation according to the upload record of the uploaded resource after a certain uploaded resource is successfully published, in this embodiment, a history record area for storing the history upload record of each resource may be additionally set outside a CDN mapping area, at this time, a service host in a service machine, after receiving the resource to be published in a resource upload request initiated by the resource front end, generates a copy of the resource to be published with completely consistent content for the resource to be published, at this time, stores the resource to be published into a preset CDN mapping area, and modifies a resource identifier of the copy of the resource to be published according to an upload timestamp of the resource to be published, for example, renames the copy of the resource to be published by adding an upload timestamp to an original resource name, and stores the renamed copy of the resource to be published into a preset history record area, the subsequent publisher can search the history area for different uploading records of the uploaded resource named by different uploading timestamps by performing a preview operation on the front end of the resource.
S405, the service host synchronizes the resource to be issued and the updated copy of the resource to be issued to the service standby machine.
In this embodiment, the service host and the service standby machine cooperate to execute each service request initiated by the resource front end, at this time, the resource front end will report the initiated resource upload request to the service host, the service host stores the resource to be published in the preset CDN mapping region according to the resource upload request, and stores the corresponding resource copy to be published in the preset history region, and synchronizes the resource to be published and the resource copy to be published to the service standby machine for storage, so as to ensure consistency between the service host and the service standby machine, so that when the service host fails, the service standby machine can timely replace the service host to execute the corresponding resource publishing operation, thereby avoiding a failure in the resource publishing process.
S406, the resource front end generates a corresponding resource publishing request according to the triggering operation of the publishing user on the resource publishing entry of the resource to be published.
S407, the resource front end sends the resource issuing request to the service host.
S408, the service host in the service machine screens out the resources to be published from the uploaded resources according to the resource publishing request.
And S409, the service host synchronizes the resource to be released to the CDN source machine.
And S410, the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released.
And S411, the CDN source machine issues the optimized resource to be issued to a CDN front-end machine cluster configured correspondingly, and simultaneously issues a corresponding cache clearing instruction to the CDN front-end machine cluster.
S412, the CDN front-end cluster clears the cached resource that is the same as the resource identifier of the resource to be delivered according to the cache clearing instruction.
And S413, the front end of the resource searches and displays the historical uploading record of the target resource from the historical record area according to the preview operation of the issued target resource, and determines the corresponding resource to be rolled back from the historical uploading record.
Optionally, in an actual resource publishing service, there may be multiple uploading operations for the same resource, if a currently published version of the resource has a problem, the resource needs to be rolled back to a recent historical version, at this time, a publishing user may predetermine a target resource that has been published and needs to be rolled back due to an error, at this time, the publishing user may preview a historical uploading record of the target resource by triggering a resource preview entry of the target resource on a platform interface, at this time, when a resource front end detects that the publishing user performs a preview operation on the target resource, a historical uploading record of the target resource is found from a historical recording area according to an uploading timestamp according to a resource identifier of the target resource and is displayed in the platform interface, the publishing user selects a resource to be rolled back to which the target resource needs to be rolled back from the historical uploading record and performs a corresponding rolling back operation, and then the rollback of the target resource is realized, and the published resource is maintained.
And S414, the resource front end sends the resource rollback request initiated by the resource to be rolled back to the service host.
And S415, the service host takes the resource to be rolled back as the resource to be released according to the resource roll-back request, and executes the resource release operation in the CDN source machine and the CDN front-end machine cluster configured correspondingly.
Optionally, the resource front end may generate a corresponding resource rollback request according to a trigger operation of the publishing user on a resource rollback entry on the platform interface, and send the resource rollback request to the service machine, where the resource rollback request carries a corresponding resource to be rolled back, and at this time, the service host may find out a resource to be rolled back specified by the resource rollback request from the history recording area, and use the resource to be rolled back as a new resource to be published, where the same resource publishing operation is executed in the CDN source machine and the CDN front end cluster configured correspondingly.
According to the technical scheme provided by the embodiment, the resources to be uploaded and the copies of the resources to be uploaded are respectively stored through the CDN mapping area and the history recording area in the service machine, the resources to be released are selected from the uploaded resources through the service machine subsequently and released to the CDN source machine and the CDN front-end machine cluster configured correspondingly, so that the two processes of resource uploading and resource releasing are separated, the problems that the resources are directly covered or replaced by the resource releasing operation and are directly accessed to the resources externally are avoided, the manageability of resource uploading and the safety of external access are effectively improved, meanwhile, the corresponding resource rollback operation can be executed through the copies of the resources to be uploaded stored in the history recording area, and the accuracy of resource releasing and the safety of external access are guaranteed.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (12)
1. A resource publishing platform, comprising: the system comprises a resource front end, a service machine, at least one Content Delivery Network (CDN) source machine and a CDN front end machine cluster which is configured corresponding to the CDN source machine; wherein the content of the first and second substances,
the service machine screens the resources to be released from the uploaded resources according to the resource identifiers of the resources to be released and synchronizes the resources to be released to the CDN source machine;
the CDN source machine optimizes the external access format of the resource to be released according to the attribute information of the resource to be released, and releases the optimized resource to be released to a CDN front-end machine cluster which is correspondingly configured;
issuing a corresponding cache clearing instruction to the CDN front-end machine cluster;
and the CDN front-end machine cluster clears the cached resources with the same resource identifiers as the resources to be released according to the cache clearing instruction, and caches the resources to be released locally.
2. The resource publishing platform of claim 1, wherein the resource front end is configured to display, in a platform interface, each resource operation entry that opens the right to the publishing user according to the login identifier of the publishing user, and generate a corresponding service request according to a trigger operation of the publishing user at the resource operation entry.
3. The resource publishing platform of claim 1, wherein the service machine is further configured to: and storing the resources to be uploaded into a preset CDN mapping area according to the resource uploading request initiated by the resource front end, updating the resource identification of the copy of the resources to be uploaded according to the uploading timestamp of the resources to be uploaded, and storing the updated copy of the resources to be uploaded into a preset history recording area.
4. The resource distribution platform according to claim 3, wherein the service machine includes a service host and a service standby machine, and the service host stores the resource to be uploaded according to the resource uploading request and synchronizes the resource to be uploaded to the service standby machine.
5. The resource delivery platform of claim 4, wherein the CDN mapping area and the history area are co-located on the service host and the service standby, or co-located in a cloud system.
6. The resource publishing platform of claim 4, further comprising: and the proxy server is respectively in communication connection with the resource front end and the service machine, and determines the service host and the service standby machine with balanced load according to a service request initiated by the resource front end.
7. The resource publishing platform of claim 3, wherein the business machine is further configured to: and taking the resource to be rolled back specified by the resource roll-back request initiated by the resource front end as the resource to be released, and executing resource releasing operation in the CDN source machine and the CDN front end machine cluster correspondingly configured.
8. The resource publishing platform of claim 7, wherein the resource front end is further configured to: and if the preview operation of the issued target resource is detected, searching and displaying a history uploading record of the target resource from the history recording area, and determining the corresponding resource to be rolled back from the history uploading record.
9. A resource publishing method applied to the resource publishing platform of any one of claims 1-8, comprising:
the resource front end generates a corresponding resource publishing request according to the triggering operation acted on a resource publishing inlet of the resource to be published by a publishing user;
the service machine screens out the resources to be released from the uploaded resources according to the resource releasing request and synchronizes the resources to the CDN source machine;
the CDN source machine optimizes an external access format of the resource to be released according to the attribute information of the resource to be released, releases the optimized resource to be released to a CDN front-end machine cluster which is correspondingly configured, and simultaneously issues a corresponding cache clearing instruction to the CDN front-end machine cluster;
and the CDN front-end machine cluster clears the cached resources with the same resource identifiers as the resources to be released according to the cache clearing instruction.
10. The method according to claim 9, wherein before the resource front end generates the corresponding resource publishing request according to the triggering operation of the publishing user acting on the resource publishing entry of the resource to be published, the method further comprises:
the resource front end generates a resource uploading request of the resource to be issued according to the triggering operation of the issuing user at the resource uploading entrance;
a service host in the service machine stores the resource to be released into a preset CDN mapping area according to the resource uploading request, updates a resource identifier of a resource copy to be released according to an uploading timestamp of the resource to be released, stores the updated resource copy to be released into a preset history recording area, and synchronizes the resource to be released and the updated resource copy to be released into a service standby machine;
correspondingly, the step of screening out the resource to be delivered from the uploaded resources according to the resource delivery request and synchronizing the resource to be delivered to the CDN source machine by the service machine includes:
and the service host in the service machine screens the resources to be released from the uploaded resources according to the resource releasing request and synchronizes the resources to be released to the CDN source machine.
11. The method according to claim 10, before the resource front end generates the resource upload request of the resource to be published according to the trigger operation of the publishing user at the resource upload entry, further comprising:
the resource front end logs in the resource publishing platform according to the identity of the publishing user, displays a corresponding platform interface after the login is successful, and displays each resource operation entry for opening the authority to the publishing user in the platform interface.
12. The method of claim 10, further comprising:
the resource front end searches and displays a historical uploading record of the target resource from the historical record area according to the preview operation of the issued target resource, and determines a corresponding resource to be rolled back from the historical uploading record;
and the service host takes the resource to be rolled back as the resource to be released according to a resource roll-back request initiated by the resource front end to the resource to be rolled back, and executes resource releasing operation in the CDN source machine and the CDN front end machine cluster correspondingly configured.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911302584.7A CN110933184B (en) | 2019-12-17 | 2019-12-17 | Resource publishing platform and resource publishing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911302584.7A CN110933184B (en) | 2019-12-17 | 2019-12-17 | Resource publishing platform and resource publishing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110933184A CN110933184A (en) | 2020-03-27 |
| CN110933184B true CN110933184B (en) | 2022-08-23 |
Family
ID=69864045
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911302584.7A Active CN110933184B (en) | 2019-12-17 | 2019-12-17 | Resource publishing platform and resource publishing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110933184B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113037888A (en) * | 2021-03-12 | 2021-06-25 | 北京金山云网络技术有限公司 | Method and device for accelerating configuration of domain name, storage medium and electronic equipment |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012152824A1 (en) * | 2011-05-12 | 2012-11-15 | Telefonica, S.A | Method for managing the infrastructure of a content distribution network service in an isp network and such an infrastructure |
| CN110493350A (en) * | 2019-08-27 | 2019-11-22 | 北京百度网讯科技有限公司 | File uploading method and device, electronic equipment and computer-readable medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8589992B2 (en) * | 2010-05-27 | 2013-11-19 | Istreamplanet Co. | Video workflow automation platform for publishing a video feed in multiple formats |
| ES2402037B1 (en) * | 2011-10-13 | 2014-04-30 | Telefónica, S.A. | METHOD AND SYSTEM FOR CARRYING OUT A DISTRIBUTED CONTENT ACQUISITION PROCESS FOR A CONTENT DISTRIBUTION NETWORK |
-
2019
- 2019-12-17 CN CN201911302584.7A patent/CN110933184B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012152824A1 (en) * | 2011-05-12 | 2012-11-15 | Telefonica, S.A | Method for managing the infrastructure of a content distribution network service in an isp network and such an infrastructure |
| CN110493350A (en) * | 2019-08-27 | 2019-11-22 | 北京百度网讯科技有限公司 | File uploading method and device, electronic equipment and computer-readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110933184A (en) | 2020-03-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3382534B1 (en) | Page jumping method and apparatus | |
| US9009277B2 (en) | Configuration management repository for a distributed platform | |
| KR20210057149A (en) | Smart contract-based data processing method, device and storage medium | |
| CN108683668B (en) | Resource checking method, device, storage medium and equipment in content distribution network | |
| US10635473B2 (en) | Setting support program, setting support method, and setting support device | |
| US9864791B2 (en) | Flow for multi-master replication in distributed storage | |
| US10333788B2 (en) | System and method for acquiring, processing and updating global information | |
| CN107992537B (en) | Service attribute transmission method, device, computer equipment and storage medium | |
| US8825750B2 (en) | Application server management system, application server management method, management apparatus, application server and computer program | |
| JPWO2009098909A1 (en) | Virtual appliance deployment system | |
| CN106790131B (en) | Parameter modification method and device and distributed platform | |
| CN110597673B (en) | Disaster recovery method, device and equipment of storage system and computer readable storage medium | |
| US20220157043A1 (en) | Distributed retrieval method, apparatus, and system, computer device, and storage medium | |
| CN110619226A (en) | Platform-based data processing method, system, equipment and storage medium | |
| EP4050850A1 (en) | Service upgrading method, device and system | |
| CN109542894B (en) | User data centralized storage method, device, medium and computer equipment | |
| US10474696B2 (en) | Replication groups for content libraries | |
| CN111464603B (en) | Server capacity expansion method and system | |
| CN113315754A (en) | Intelligent linkage method, device, equipment and medium for firewall of container visit | |
| CN110933184B (en) | Resource publishing platform and resource publishing method | |
| CN106325909A (en) | Method and system for updating multiple images in private cloud system | |
| CN107291575B (en) | Processing method and equipment for data center fault | |
| JP2018173741A (en) | Container registration program, container registration device and container registration method | |
| JP3802977B2 (en) | Information contradiction judgment, correction apparatus and method, and information contradiction judgment and correction program in storage exchange type electronic conference system | |
| KR20190015817A (en) | Method, Apparatus and System for Monitoring Using Middleware |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231008 Address after: 31a, 15 / F, building 30, maple mall, bangrang Road, Brazil, Singapore Patentee after: Baiguoyuan Technology (Singapore) Co.,Ltd. Address before: 511400 floor 5-13, West Tower, building C, 274 Xingtai Road, Shiqiao street, Panyu District, Guangzhou City, Guangdong Province Patentee before: GUANGZHOU BAIGUOYUAN INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |