CN108008966B - Resource updating method and system - Google Patents
Resource updating method and system Download PDFInfo
- Publication number
- CN108008966B CN108008966B CN201711257028.3A CN201711257028A CN108008966B CN 108008966 B CN108008966 B CN 108008966B CN 201711257028 A CN201711257028 A CN 201711257028A CN 108008966 B CN108008966 B CN 108008966B
- Authority
- CN
- China
- Prior art keywords
- resource
- current
- coordinate
- target
- module
- 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
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000012216 screening Methods 0.000 claims description 18
- 238000012163 sequencing technique Methods 0.000 claims description 6
- 239000002184 metal Substances 0.000 description 8
- 230000008569 process Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a resource updating method and a system, wherein the system comprises the following steps: the system comprises a publishing module, at least one client and at least one service module; the issuing module receives at least one resource coordinate sent by any one service module, issues and registers the at least one resource coordinate, judges whether the current resource needs to be updated according to the resource coordinate of the current resource and the at least one resource coordinate, determines a target resource coordinate if the current resource needs to be updated, and sends the target resource coordinate to the current service module; each client sends an update request to the current service module when receiving an update trigger of a user for the current resource, wherein the update request comprises: resource coordinates of the current resource; updating the current resource by using the target resource; and each service module determines a target resource according to the target resource coordinate and sends the target resource to the target client. The scheme provided by the invention can update the resources in time.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a resource updating method and system.
Background
With the development of information technology, the amount of resources in the client increases rapidly, and how to update the resources of the client in time becomes a problem to be solved urgently.
In the prior art, a technician issues a resource through an issuing center, and a client downloads the resource through accessing the issuing center.
However, the network between the client and the distribution center is often unstable, resulting in untimely resource update.
Disclosure of Invention
The embodiment of the invention provides a resource updating method and a resource updating system, which can update resources in time.
In a first aspect, an embodiment of the present invention provides a resource updating system, including: the system comprises a publishing module, at least one client and at least one service module;
the issuing module is used for receiving at least one resource coordinate sent by any one of the service modules and issuing and registering the at least one resource coordinate; receiving a resource coordinate of a current resource sent by a target client through a current service module; judging whether the current resource needs to be updated or not according to the resource coordinate of the current resource and the at least one resource coordinate, if so, determining a target resource coordinate, and sending the target resource coordinate to the current service module;
each client is configured to send, when receiving an update trigger for the current resource by a user, an update request to the publishing module through the current service module, where the update request includes: resource coordinates of the current resource; when a target resource is received, updating the current resource by using the target resource;
each business module is used for determining the target resource according to the target resource coordinate when receiving the target resource coordinate and sending the target resource to the target client.
Preferably, the first and second electrodes are formed of a metal,
the update request further comprises: a current identity token;
the release module is further used for storing at least one piece of registered client information; receiving the current identity token sent by the target client through the current service module, analyzing the current identity token, and determining the information of the target client; and judging whether the target client information exists in the at least one piece of registered client information, if so, executing the step of judging whether the current resource needs to be updated according to the current resource coordinate and the at least one resource coordinate.
Preferably, the first and second electrodes are formed of a metal,
the issuing module is further configured to receive issuing time corresponding to each resource coordinate sent by any one of the service modules;
the resource coordinates comprising: business domain, namespace, and version information;
the release module is used for determining at least one released resource coordinate which is the same as the service field and the name space of the current resource and has the release time not later than the current time in the at least one resource coordinate; sequencing the at least one published resource coordinate according to the sequence of the publication time from late to early; and judging whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource, and if not, determining that the published resource coordinate arranged at the first position is the target resource coordinate.
Preferably, the first and second electrodes are formed of a metal,
the issuing module is further configured to receive an issuing range corresponding to each resource coordinate and sent by any one of the service modules, where the issuing range includes: the system comprises a publishing level and at least one object identifier corresponding to the publishing level; receiving at least one target object identifier corresponding to the user and sent by the target client through the current service module; determining the priority of each release level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to the published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of the user as the current release level, and screening the coordinates of the at least one released resource according to the current release level;
s3: updating the current issuing level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current publishing level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening the at least one published resource coordinate according to the updated current publishing level;
the issuing module is used for sequencing the at least one screened issued resource coordinate according to the order of issuing time from late to early; judging whether the version information of the first-ranked screened published resource coordinate is the same as the version information of the current resource, if not, determining the first-ranked screened published resource coordinate as a target resource coordinate;
the update request further comprises: and at least one target object identifier corresponding to the user, wherein each target object identifier corresponds to a different release level.
Preferably, the first and second electrodes are formed of a metal,
the issuing module is further configured to receive a fallback resource coordinate sent by any one of the service modules; judging whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, sending a backspacing instruction to the target client through the current service module, otherwise, executing the resource coordinate according to the current resource and the at least one resource coordinate, and judging whether the current resource needs to be updated;
each client is further used for returning the current resource to the previous version when receiving the return instruction.
In a second aspect, an embodiment of the present invention provides a resource updating method based on the resource updating system in any of the foregoing embodiments, including:
the issuing module receives at least one resource coordinate sent by any one service module and issues and registers the at least one resource coordinate;
when receiving an update trigger of a user for a current resource, each client sends an update request to the publishing module through the current service module, wherein the update request includes: resource coordinates of the current resource;
the issuing module receives the resource coordinate of the current resource sent by the target client through the current service module;
the issuing module judges whether the current resource needs to be updated or not according to the resource coordinate of the current resource and the at least one resource coordinate, if so, determines a target resource coordinate, and sends the target resource coordinate to the current service module;
when each business module receives the target resource coordinate, determining a target resource according to the target resource coordinate, and sending the target resource to the target client;
and each client updates the current resource by using the target resource when receiving the target resource.
Preferably, the first and second electrodes are formed of a metal,
the update request further comprises: a current identity token;
before the issuing module determines whether the current resource needs to be updated according to the resource coordinate of the current resource and the at least one resource coordinate, the method further includes:
the release module stores at least one piece of registered client information in advance;
the issuing module receives the current identity token sent by the target client through the current service module, analyzes the current identity token and determines target client information;
and the issuing module judges whether the target client information exists in the at least one piece of registered client information, and if so, executes the judgment to judge whether the current resource needs to be updated according to the current resource coordinate and the at least one resource coordinate.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
the release module receives release time which is sent by any one of the service modules and corresponds to each resource coordinate;
the resource coordinates comprising: business domain, namespace, and version information;
the issuing module judges whether the current resource needs to be updated according to the resource coordinate of the current resource and the at least one resource coordinate, and if so, determines a target resource coordinate, including:
the release module determines at least one released resource coordinate which is the same as the service field and the name space of the current resource and has the release time not later than the current time in the at least one resource coordinate;
the issuing module is used for sequencing the coordinates of the at least one issued resource according to the order of issuing time from late to early;
and the release module judges whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource, and if not, the published resource coordinate arranged at the first position is determined as the target resource coordinate.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
the issuing module receives an issuing range which is sent by any one of the service modules and corresponds to each resource coordinate, wherein the issuing range comprises: the system comprises a publishing level and at least one object identifier corresponding to the publishing level;
the update request further comprises: at least one target object identifier corresponding to the user, wherein each target object identifier corresponds to a different release level;
the issuing module receives at least one target object identifier which is sent by the target client through the current service module and corresponds to the user;
the issuing module determines the priority of each issuing level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to the published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of the user as the current release level, and screening the coordinates of the at least one released resource according to the current release level;
s3: updating the current issuing level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current publishing level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening the at least one published resource coordinate according to the updated current publishing level;
the issuing module sorts the at least one issued resource coordinate according to the order of issuing time from late to early, and comprises:
the publishing module sorts the at least one published resource coordinate after screening according to the sequence of the publishing time from late to early;
the issuing module judges whether the version information of the issued resource coordinate arranged at the first position is the same as the version information of the current resource, if not, the issued resource coordinate arranged at the first position is determined as a target resource coordinate, and the method comprises the following steps:
and the release module judges whether the version information of the first screened published resource coordinate is the same as the version information of the current resource, and if not, the first screened published resource coordinate is determined to be the target resource coordinate.
Preferably, the first and second electrodes are formed of a metal,
further comprising:
the release module receives a backspacing resource coordinate sent by any one of the service modules;
the issuing module judges whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, a backspacing instruction is sent to the target client through the current service module, otherwise, the issuing module executes the resource coordinate according to the current resource and the at least one resource coordinate to judge whether the current resource needs to be updated;
and each client backs the current resource to the previous version when receiving the backspacing instruction.
The embodiment of the invention provides a resource updating method and a resource updating system, wherein in the system, each resource is divided into different business modules according to the business field, each business module can release the resource through a release module, a user can send an updating request to a current business module to which the current resource belongs through a client aiming at the current resource, the current business module sends the updating request to the release module, the release module judges whether the current resource needs to be updated according to the coordinates of the released and registered resource, and when the current resource needs to be updated, the release module feeds back the determined target resource coordinates to the current business module, so that the current business module determines the target resource according to the target resource coordinates and feeds back the target resource to the client for updating. In an actual application scenario, the resource updating system can be established according to the business requirements of a certain enterprise, the resource can be published and updated by the system, and for the staff of the enterprise, the resource can be updated without an external publishing center, so that the problem of network instability can be avoided, and the resource can be updated in time.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a resource updating system according to an embodiment of the present invention;
FIG. 2 is a flow chart of a resource updating method according to an embodiment of the present invention;
fig. 3 is a flowchart of a resource updating method according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer and more complete, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention, and based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the scope of the present invention.
As shown in fig. 1, an embodiment of the present invention provides a resource updating system, which includes:
a publishing module 101, at least one client 102 and at least one business module 103;
the issuing module 101 is configured to receive at least one resource coordinate sent by any one of the service modules 103, and issue and register the at least one resource coordinate; receiving a resource coordinate of a current resource sent by a target client 102 through a current service module 103; judging whether the current resource needs to be updated or not according to the resource coordinate of the current resource and at least one resource coordinate, if so, determining a target resource coordinate, and sending the target resource coordinate to the current service module 103;
each client 102 is configured to send, through the current service module 103, an update request to the publishing module 101 when receiving an update trigger for a current resource from a user, where the update request includes: resource coordinates of the current resource; when the target resource is received, updating the current resource by using the target resource;
each service module 103 is configured to, when receiving the target resource coordinate, determine a target resource according to the target resource coordinate, and send the target resource to the target client 102.
In the system, each resource is divided into different service modules according to the service field, each service module can issue the resource through an issuing module, a user can send an updating request to a current service module to which the current resource belongs through a client aiming at the current resource, the current service module sends the updating request to the issuing module, the issuing module judges whether the current resource needs to be updated according to the resource coordinate of issued registration, when the current resource needs to be updated, the issuing module feeds back the determined target resource coordinate to the current service module, so that the current service module determines the target resource according to the target resource coordinate and feeds back the target resource to the client for updating. In an actual application scenario, the resource updating system can be established according to the business requirements of a certain enterprise, the resource can be published and updated by the system, and for the staff of the enterprise, the resource can be updated without an external publishing center, so that the problem of network instability can be avoided, and the resource can be updated in time.
In an actual application scenario, a publishing module encapsulates an internal updating mechanism and provides a uniform updating and query interface for resources, publishing and updating services of a business module depend on the publishing module, and a publishable resource can be a picture, a file, a program package of a read Native application, or any other service. And compared with the client, the service module and the release module jointly form a server.
In one embodiment of the invention, to verify the identity of the client, the update request further comprises: a current identity token;
the publishing module 101 is further configured to store at least one piece of registered client information; receiving a current identity token sent by a target client through a current service module, analyzing the current identity token, and determining target client information; and judging whether target client information exists in the at least one piece of registered client information, if so, executing to judge whether the current resource needs to be updated according to the current resource coordinate and the at least one resource coordinate.
Before using the issuing module for updating, the client needs to register in the issuing module through the service module to obtain the identity token. The client needs to transmit detailed information of the client, such as the device Id, the device name, the operating platform information, and the like. The issuing module registers the client and distributes a client identity token, the token is an important certificate for the client to update normally, whether the token takes effect is controlled by the issuing module completely, namely, the issuing module can cancel the expense as required at any time, and the client can not be used any more, so as to achieve the effect of equipment management; the client needs to carry the token every time the client requests for updating, and the issuing module identifies the client according to the token and returns the updating information.
In an embodiment of the present invention, in order to implement the timed distribution of the resource, the distribution module 101 is further configured to receive distribution time corresponding to each resource coordinate sent by any one of the service modules 103;
resource coordinates, including: business domain, namespace, and version information;
the issuing module 101 is configured to determine, in at least one resource coordinate, at least one issued resource coordinate that is the same as a service field and a namespace of a current resource and whose issuing time is not later than a current time; sequencing at least one published resource coordinate according to the sequence of the publication time from late to early; and judging whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource, and if not, determining that the published resource coordinate arranged at the first position is the target resource coordinate.
In the embodiment of the invention, each resource is marked by the resource coordinate. In an actual application scenario, the positioning of the resource by the publishing module is divided into three levels: business domain (domain), namespace (namespace), version information (version). The domain specifies a service module where the resource is located to realize service isolation among the resources, the namespace describes the specific resource in the service field in detail, and the version describes the version information of a certain resource, and finally the specific version information of a certain resource can be completely determined by using { domiain, namespace and version }.
The release time is responsible for controlling the update information to take effect from a certain time of a day, and is suitable for release which is sensitive to time, such as greeting information update in a new year, patch release in a new quarter and the like.
In an embodiment of the present invention, in order to flexibly adjust the publishing range, the publishing module 101 is further configured to receive the publishing range corresponding to each resource coordinate sent by any one of the service modules 103, where the publishing range includes: the system comprises a release level and at least one object identifier corresponding to the release level; receiving at least one target object identifier corresponding to a user, which is sent by a target client 102 through a current service module 103; determining the priority of each release level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of a user as the current release level, and screening at least one released resource coordinate according to the current release level;
s3: updating the current release level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current release level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening at least one published resource coordinate according to the updated current publishing level;
the publishing module 101 is configured to sort the at least one screened published resource coordinate according to a sequence from late to early in publishing time; judging whether the version information of the published resource coordinate ranked at the first position after screening is the same as the version information of the current resource, if not, determining the published resource coordinate ranked at the first position after screening as a target resource coordinate;
the update request further includes: and the target object identifiers correspond to the users, wherein each target object identifier corresponds to a different release level.
The scope of publication may determine which users to publish updates, e.g., in an actual application scenario, publication levels include: enterprise (Enterprise), organizational (Group) and personal (User);
in an embodiment of the present invention, in order to enhance the fault tolerance of the system, the publishing module 101 is further configured to receive a fallback resource coordinate sent by any one of the service modules 103; judging whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, sending a backspacing instruction to the target client 102 through the current service module 103, otherwise, executing to judge whether the current resource needs to be updated according to the resource coordinate of the current resource and at least one resource coordinate;
each client 102 is further configured to roll back the current resource to the previous version when receiving the roll-back instruction.
As shown in fig. 2, an embodiment of the present invention provides a resource updating method based on the resource updating system in any of the above embodiments, including:
step 201: the issuing module receives at least one resource coordinate sent by any one service module and issues and registers the at least one resource coordinate;
step 202: when receiving an update trigger of a user for a current resource, each client sends an update request to a publishing module through a current service module, wherein the update request comprises: resource coordinates of the current resource;
step 203: the issuing module receives the resource coordinate of the current resource sent by the target client through the current service module;
step 204: the issuing module judges whether the current resource needs to be updated according to the resource coordinate of the current resource and at least one resource coordinate, and if so, executes step 205;
step 205: the issuing module determines a target resource coordinate and sends the target resource coordinate to the current service module;
step 206: when each business module receives the target resource coordinate, determining a target resource according to the target resource coordinate, and sending the target resource to a target client;
step 207: and each client updates the current resource by using the target resource when receiving the target resource.
In one embodiment of the invention, the update request further comprises: a current identity token;
before the issuing module judges whether the current resource needs to be updated according to the resource coordinate of the current resource and at least one resource coordinate, the method further includes:
the release module stores at least one registered client information in advance;
the issuing module receives a current identity token sent by a target client through a current service module, analyzes the current identity token and determines target client information;
and the issuing module judges whether target client information exists in the at least one piece of registered client information, and if so, judges whether the current resource needs to be updated according to the current resource coordinate and the at least one resource coordinate.
In one embodiment of the present invention, further comprising:
the issuing module receives issuing time which is sent by any one service module and corresponds to each resource coordinate;
resource coordinates, including: business domain, namespace, and version information;
the issuing module judges whether the current resource needs to be updated according to the resource coordinate of the current resource and at least one resource coordinate, and if so, determines the target resource coordinate, and comprises the following steps:
the method comprises the steps that a release module determines at least one released resource coordinate which is the same as the service field and the name space of a current resource and has the release time not later than the current time in at least one resource coordinate;
the issuing module sorts at least one issued resource coordinate according to the order of issuing time from late to early;
and the release module judges whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource, and if not, the published resource coordinate arranged at the first position is determined as the target resource coordinate.
In one embodiment of the present invention, further comprising:
the issuing module receives issuing ranges which are sent by any one service module and correspond to the resource coordinates, wherein the issuing ranges comprise: the system comprises a release level and at least one object identifier corresponding to the release level;
the update request further includes: at least one target object identifier corresponding to a user, wherein each target object identifier corresponds to a different release level;
the method comprises the steps that a publishing module receives at least one target object identifier which is sent by a target client through a current service module and corresponds to a user;
the issuing module determines the priority of each issuing level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of a user as the current release level, and screening at least one released resource coordinate according to the current release level;
s3: updating the current release level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current release level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening at least one published resource coordinate according to the updated current publishing level;
the issuing module sorts the coordinates of at least one issued resource according to the order of the issuing time from late to early, and comprises the following steps:
the issuing module sorts the at least one screened issued resource coordinate according to the order of issuing time from late to early;
the issuing module judges whether the version information of the issued resource coordinate arranged at the first position is the same as the version information of the current resource, if not, the issued resource coordinate arranged at the first position is determined as a target resource coordinate, and the method comprises the following steps:
and the release module judges whether the version information of the first screened published resource coordinate is the same as the version information of the current resource, and if not, the first screened published resource coordinate is determined as the target resource coordinate.
In one embodiment of the present invention, further comprising:
the release module receives a backspacing resource coordinate sent by any one service module;
the issuing module judges whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, the backspacing instruction is sent to the target client through the current service module, otherwise, the issuing module executes to judge whether the current resource needs to be updated according to the resource coordinate of the current resource and at least one resource coordinate;
and each client backs the current resource to the previous version when receiving the back-off instruction.
As shown in fig. 3, the embodiment of the present invention takes a resource updating system composed of a publishing module, a client, and two service modules as an example to describe in detail a resource updating method, where the method includes:
step 301: the issuing module receives at least one resource coordinate sent by any one service module, issuing time and issuing range corresponding to each resource coordinate, and issues and registers the at least one resource coordinate, wherein the resource coordinate comprises: business domain, namespace, and version information; a distribution scope comprising: a publication level, at least one object identification corresponding to the publication level.
And a plurality of resource coordinates are stored in each business module, and technicians can determine the resource coordinates of the resources to be issued through the business modules and send the resource coordinates to the issuing module so as to enable the issuing module to perform issuing registration.
The resource coordinate is used to distinguish each resource, and in this embodiment, the resource is determined by the service domain, the name space, and the version information, for example, the resource coordinate of the resource 001 is (video, Tencent video, 2.0 version). The parameters in the resource coordinates may include one or more for the purpose of distinguishing between different resources. For example, in an actual application scenario, the resource coordinates include business domain and version information, and the resource coordinates of resource 002 are (holiday picture, 1.0). Therefore, the resource coordinates can be expanded according to business requirements.
The issuing range is used for determining issuing objects, the issuing level is used for grading the issuing objects according to business requirements, and the number of the levels can be determined according to the business requirements. For example, in a practical application scenario, the publication level includes three levels: enterprise level, department level, and personal level.
Taking the financial statement template of a company as an example:
the enterprise level template can see the total business condition of a company in a certain year and the business conditions of various subordinate departments;
the department level template comprises general template contents, can see detailed business conditions of the department, the secondary department and other departments, but cannot see detailed data of other departments;
the personal level template comprises general template contents and department template contents, and confidential information of each department and all individuals of the company can be seen.
The personal level template can be seen only by a plurality of high managers in the company, and the updating of the template is only released to a plurality of users when the template is released; the department level template can be updated only by the staff belonging to a specific department, the updating of the template can be issued only to the staff under the specific department, but not to the staff of the department, and the financial template of the department cannot be obtained; enterprise-level templates are only visible to employees affiliated with the company, and employees of other enterprises should not be able to request updates at the time of the request.
The object identifier is used to identify a published object at a current publication level, for example, where the publication level is an enterprise level, and the object identifier includes: a. b, the resource allows the users of enterprise a and enterprise b to update.
Step 302: when receiving an update trigger of a user for a current resource, a client sends an update request to a publishing module through a current service module, wherein the update request comprises: the resource coordinates of the current resources and at least one target object identifier corresponding to the user, wherein each target object identifier corresponds to different release levels.
For example, the target object identifier corresponding to the user is an enterprise identifier W1, a department identifier W2, and a personal identifier W3.
According to different service requirements, different service modules process different types of resource release and update.
The release time is used to determine the time when the release is effective, for example, the resource coordinate of the resource 001 is (video, update video, version 2.0), and the release time is 9 month 1, so that from 9 month 1, the user can update the update video to the update video version 2.0 through the release module.
Step 303: the issuing module receives the resource coordinates of the current resource and at least one target object identifier corresponding to the user, and determines at least one issued resource coordinate which is the same as the service field and the name space of the current resource and has issuing time not later than the current time in at least one resource coordinate.
For example, if the current resource coordinate is (video, Tencent video, version 1.0) and the current resource coordinate is 9/month/5, the publishing module determines that the published resource coordinate meeting the condition is (video, Tencent video, version 2.0).
Step 304: the issuing module determines the priority of each issuing level, and takes the issuing level with the highest priority as the current issuing level.
Different levels of publication have different priorities, e.g., enterprise, department, and personal priority in the order personal > department > enterprise, depending on business needs.
Taking the above-mentioned financial statement template as an example, steps 304-308 can be summarized as follows:
the issuing module judges which issuing range the financial template updating is applicable to the user according to the information of the user and the priority of personal level, department level and enterprise level, if the issuing history issues the personal level updating to the user, the user is considered to be an important user customized by individuality, and the level of the template updating is set as personal; if the individual level does not exist, searching whether the release history has the update of the organization level, if so, using the organization level, otherwise, using the general level of the enterprise.
Step 305: the issuing module judges whether a target object identifier corresponding to the current issuing level exists in object identifiers corresponding to issued resource coordinates, if so, the step 306 is executed, otherwise, the step 307 is executed;
step 306: the issuing module determines that the issuing level of the user is the current issuing level, screens at least one issued resource coordinate according to the current issuing level, and executes the step 310;
step 307: the issuing module updates the current issuing level according to the sequence of the priority from high to low;
step 308: the issuing module judges whether the updated priority of the current issuing level is the lowest, if so, the step 309 is executed, otherwise, the step 305 is executed;
step 309: the issuing module screens at least one issued resource coordinate according to the updated current issuing level, and executes step 310;
for example, the resource coordinate 002 is (video, Tencent video, version 1.0), the release time is 9 month No. 1, the release range is at the enterprise level, and the enterprise identifier P1;
the resource coordinate 003 is (video, Tencent video, version 1.0), the release time is No. 9 month No. 1, the release range is department level, department identification P2, P3;
the resource coordinate 004 is (video, Tencent video, 2.0 version), the release time is 9 months No. 2, the release range is department level, and the department identifier P2;
if the current resource identification is (video, Tencent video, version 1.0), the current user target object identification is: the affiliated enterprise is marked as P1, the affiliated department is marked as P2, the individual is marked as P3, and the current time is 9 months and 5.
And determining the distributed resource coordinates 002- & 004 according to the distribution time, wherein the distribution for the individual P3 is not performed, but the distribution for the department identification P2 is performed, and screening to obtain the resource coordinates 003- & 004.
Step 310: and the release module sequences the screened at least one published resource coordinate according to the sequence of the release time from late to early, and when the version information of the first-ranked screened published resource coordinate is different from the version information of the current resource, the release module determines the first-ranked screened published resource coordinate as a target resource coordinate and sends the target resource coordinate to the current service module.
The current Tencent video is version 1.0, and the published resource coordinate 004 ranked first after screening is version 2.0 of Tencent video, so the target resource coordinate is (video, Tencent video, version 2.0).
Step 311: and when the current service module receives the target resource coordinate, determining the target resource according to the target resource coordinate, and sending the target resource to the client.
The service module can directly store the resources and also can store the corresponding relation between the resource identification and the resource address. Generally, for the case of a large resource size, the service module generally stores the corresponding relationship between the resource identifier and the resource address, and determines the target resource through the target resource identifier. For example, the service module stores the address of the resource on the network disk.
Step 312: and when the client receives the target resource, updating the current resource by using the target resource.
The embodiment of the invention provides a readable medium, which comprises an execution instruction, and when a processor of a storage controller executes the execution instruction, the storage controller executes the method of any one of the above embodiments.
An embodiment of the present invention provides a storage controller, including: a processor, a memory, and a bus;
the memory is used for storing execution instructions, the processor is connected with the memory through the bus, and when the storage controller runs, the processor executes the execution instructions stored by the memory so as to enable the storage controller to execute the method of any one of the above embodiments.
Because the information interaction, execution process and other contents among the steps in the method are based on the same concept as the system embodiment of the present invention, specific contents can be referred to the description in the system embodiment of the present invention, and are not described herein again.
In summary, the embodiments of the present invention have at least the following effects:
1. in the embodiment of the invention, in the system, each resource is divided into different service modules according to the service field, each service module can issue the resource through an issuing module, a user can send an updating request to a current service module to which the current resource belongs through a client aiming at the current resource, the current service module sends the updating request to the issuing module, the issuing module judges whether the current resource needs to be updated according to the coordinates of the issued and registered resource, and when the current resource needs to be updated, the issuing module feeds back the determined target resource coordinates to the current service module, so that the current service module determines the target resource according to the target resource coordinates and feeds back the target resource to the client for updating. In an actual application scenario, the resource updating system can be established according to the business requirements of a certain enterprise, the resource can be published and updated, for the staff of the enterprise, the resource can be updated without an external publishing center, the external network resources are not occupied, the problem of network instability is avoided, and the resource can be updated in time.
2. In the embodiment of the invention, any client terminal has to provide the detailed information of the equipment to register in the publishing module and obtain the identity token, so that the subsequent steps can be carried out, the detailed information of the equipment is recorded, and a foundation is provided for the management of the equipment.
3. In the embodiment of the invention, the method sufficiently abstracts the release resources, can expand the resource types, and can manage and release any manageable resources such as pictures, patch packages and the like.
4. In the embodiment of the invention, the release range is flexible and changeable, and the update can be released for a specific user or an organization and an enterprise; the updated release time can also be preset, so that the on-site automatic release is realized, and the development cost of operators is reduced.
5. In the embodiment of the invention, the rollback of the released content can be realized, the fault tolerance of the system is enhanced, and good experience is provided for users. The collection of the user update information is convenient for developers and operators to better analyze the use condition of the user, and a data basis is provided for user behavior analysis under big data.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an element" does not exclude the presence of other similar elements in a process, method, article, or apparatus that comprises the element.
Those of ordinary skill in the art will understand that: all or part of the steps for realizing the method embodiments can be completed by hardware related to program instructions, the program can be stored in a computer readable storage medium, and the program executes the steps comprising the method embodiments when executed; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it is to be noted that: the above description is only a preferred embodiment of the present invention, and is only for the purpose of illustrating the technical solutions of the present invention, and not for the purpose of limiting the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (7)
1. A resource update system, comprising: the system comprises a publishing module, at least one client and at least one service module;
the issuing module is used for receiving at least one resource coordinate sent by any one of the service modules and issuing and registering the at least one resource coordinate; receiving a resource coordinate of a current resource sent by a target client through a current service module; judging whether the current resource needs to be updated or not according to the resource coordinate of the current resource and the at least one resource coordinate, if so, determining a target resource coordinate, and sending the target resource coordinate to the current service module;
each client is configured to send, when receiving an update trigger for the current resource by a user, an update request to the publishing module through the current service module, where the update request includes: resource coordinates of the current resource; when a target resource is received, updating the current resource by using the target resource;
each business module is used for determining the target resource according to the target resource coordinate and sending the target resource to the target client when receiving the target resource coordinate;
the update request further comprises: a current identity token;
the release module is further used for storing at least one piece of registered client information; receiving the current identity token sent by the target client through the current service module, analyzing the current identity token, and determining the information of the target client; judging whether the target client information exists in the at least one piece of registered client information or not, if so, executing the step of judging whether the current resource needs to be updated or not according to the current resource coordinate and the at least one resource coordinate;
the issuing module is further configured to receive issuing time corresponding to each resource coordinate sent by any one of the service modules;
the resource coordinates comprising: business domain, namespace, and version information;
the release module is used for determining at least one released resource coordinate which is the same as the service field and the name space of the current resource and has the release time not later than the current time in the at least one resource coordinate; sequencing the at least one published resource coordinate according to the sequence of the publication time from late to early; judging whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource or not, and if not, determining the published resource coordinate arranged at the first position as a target resource coordinate;
the issuing module is further configured to receive an issuing range corresponding to each resource coordinate and sent by any one of the service modules, where the issuing range includes: the system comprises a publishing level and at least one object identifier corresponding to the publishing level; receiving at least one target object identifier corresponding to the user and sent by the target client through the current service module; determining the priority of each release level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to the published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of the user as the current release level, and screening the coordinates of the at least one released resource according to the current release level;
s3: updating the current issuing level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current publishing level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening the at least one published resource coordinate according to the updated current publishing level;
the update request further comprises: and at least one target object identifier corresponding to the user, wherein each target object identifier corresponds to a different release level.
2. The resource update system of claim 1,
the issuing module is further configured to receive a fallback resource coordinate sent by any one of the service modules; judging whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, sending a backspacing instruction to the target client through the current service module, otherwise, executing the resource coordinate according to the current resource and the at least one resource coordinate, and judging whether the current resource needs to be updated;
each client is further used for returning the current resource to the previous version when receiving the return instruction.
3. A resource updating method based on the resource updating system of any one of claims 1-2, comprising:
the issuing module receives at least one resource coordinate sent by any one service module and issues and registers the at least one resource coordinate;
when receiving an update trigger of a user for a current resource, each client sends an update request to the publishing module through the current service module, wherein the update request includes: resource coordinates of the current resource;
the issuing module receives the resource coordinate of the current resource sent by the target client through the current service module;
the issuing module judges whether the current resource needs to be updated or not according to the resource coordinate of the current resource and the at least one resource coordinate, if so, determines a target resource coordinate, and sends the target resource coordinate to the current service module;
when each business module receives the target resource coordinate, determining a target resource according to the target resource coordinate, and sending the target resource to the target client;
and each client updates the current resource by using the target resource when receiving the target resource.
4. The resource updating method according to claim 3,
the update request further comprises: a current identity token;
before the issuing module determines whether the current resource needs to be updated according to the resource coordinate of the current resource and the at least one resource coordinate, the method further includes:
the release module stores at least one piece of registered client information in advance;
the issuing module receives the current identity token sent by the target client through the current service module, analyzes the current identity token and determines target client information;
and the issuing module judges whether the target client information exists in the at least one piece of registered client information, and if so, executes the judgment to judge whether the current resource needs to be updated according to the current resource coordinate and the at least one resource coordinate.
5. The resource updating method according to claim 4, further comprising:
the release module receives release time which is sent by any one of the service modules and corresponds to each resource coordinate;
the resource coordinates comprising: business domain, namespace, and version information;
the issuing module judges whether the current resource needs to be updated according to the resource coordinate of the current resource and the at least one resource coordinate, and if so, determines a target resource coordinate, including:
the release module determines at least one released resource coordinate which is the same as the service field and the name space of the current resource and has the release time not later than the current time in the at least one resource coordinate;
the issuing module is used for sequencing the coordinates of the at least one issued resource according to the order of issuing time from late to early;
and the release module judges whether the version information of the published resource coordinate arranged at the first position is the same as the version information of the current resource, and if not, the published resource coordinate arranged at the first position is determined as the target resource coordinate.
6. The resource updating method according to claim 5, further comprising:
the issuing module receives an issuing range which is sent by any one of the service modules and corresponds to each resource coordinate, wherein the issuing range comprises: the system comprises a publishing level and at least one object identifier corresponding to the publishing level;
the update request further comprises: at least one target object identifier corresponding to the user, wherein each target object identifier corresponds to a different release level;
the issuing module receives at least one target object identifier which is sent by the target client through the current service module and corresponds to the user;
the issuing module determines the priority of each issuing level; performing S1 with the publication level with the highest priority as the current publication level;
s1: judging whether a target object identifier corresponding to the current publishing level exists in object identifiers corresponding to the published resource coordinates, if so, executing S2, otherwise, executing S3;
s2: determining the release level of the user as the current release level, and screening the coordinates of the at least one released resource according to the current release level;
s3: updating the current issuing level according to the sequence of the priority levels from high to low;
s4: judging whether the updated priority of the current publishing level is the lowest, if so, executing S5, otherwise, executing S1;
s5: screening the at least one published resource coordinate according to the updated current publishing level;
the issuing module sorts the at least one issued resource coordinate according to the order of issuing time from late to early, and comprises:
the publishing module sorts the at least one published resource coordinate after screening according to the sequence of the publishing time from late to early;
the issuing module judges whether the version information of the issued resource coordinate arranged at the first position is the same as the version information of the current resource, if not, the issued resource coordinate arranged at the first position is determined as a target resource coordinate, and the method comprises the following steps:
and the release module judges whether the version information of the first screened published resource coordinate is the same as the version information of the current resource, and if not, the first screened published resource coordinate is determined to be the target resource coordinate.
7. The resource updating method according to any one of claim 6, further comprising:
the release module receives a backspacing resource coordinate sent by any one of the service modules;
the issuing module judges whether the resource coordinate of the current resource is the same as the backspacing resource coordinate, if so, a backspacing instruction is sent to the target client through the current service module, otherwise, the issuing module executes the resource coordinate according to the current resource and the at least one resource coordinate to judge whether the current resource needs to be updated;
and each client backs the current resource to the previous version when receiving the backspacing instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711257028.3A CN108008966B (en) | 2017-12-04 | 2017-12-04 | Resource updating method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711257028.3A CN108008966B (en) | 2017-12-04 | 2017-12-04 | Resource updating method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108008966A CN108008966A (en) | 2018-05-08 |
| CN108008966B true CN108008966B (en) | 2020-11-03 |
Family
ID=62056161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711257028.3A Active CN108008966B (en) | 2017-12-04 | 2017-12-04 | Resource updating method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108008966B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103475744A (en) * | 2013-09-30 | 2013-12-25 | 中国农业银行股份有限公司 | Resource downloading method, device and system on basis of Web application |
| WO2014176048A1 (en) * | 2013-04-22 | 2014-10-30 | Alibaba Group Holding Limited | Method and device for updating client |
| CN104778063A (en) * | 2015-04-16 | 2015-07-15 | 小米科技有限责任公司 | Method and device for updating resource |
| CN105138376A (en) * | 2015-09-01 | 2015-12-09 | 北京皮尔布莱尼软件有限公司 | Mixed model application, webpage resource upgrading method thereof, mobile terminal and system |
| CN107026884A (en) * | 2016-02-02 | 2017-08-08 | 阿里巴巴集团控股有限公司 | Acquisition methods, client, server and the system of resource file |
-
2017
- 2017-12-04 CN CN201711257028.3A patent/CN108008966B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014176048A1 (en) * | 2013-04-22 | 2014-10-30 | Alibaba Group Holding Limited | Method and device for updating client |
| CN103475744A (en) * | 2013-09-30 | 2013-12-25 | 中国农业银行股份有限公司 | Resource downloading method, device and system on basis of Web application |
| CN104778063A (en) * | 2015-04-16 | 2015-07-15 | 小米科技有限责任公司 | Method and device for updating resource |
| CN105138376A (en) * | 2015-09-01 | 2015-12-09 | 北京皮尔布莱尼软件有限公司 | Mixed model application, webpage resource upgrading method thereof, mobile terminal and system |
| CN107026884A (en) * | 2016-02-02 | 2017-08-08 | 阿里巴巴集团控股有限公司 | Acquisition methods, client, server and the system of resource file |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108008966A (en) | 2018-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| CN112766907B (en) | Service data processing method, device and server | |
| US6381610B1 (en) | System and method for implementing project procedures | |
| CN110532025B (en) | Data processing method, device and equipment based on micro-service architecture and storage medium | |
| CN108399101A (en) | The methods, devices and systems of scheduling of resource | |
| US20110302212A1 (en) | Systems and methods for analyzing operations in a multi-tenant database system environment | |
| US11182406B2 (en) | Increased data availability during replication | |
| CN101853152A (en) | Method and system for generating graphical user interface | |
| US8428989B2 (en) | Cross functional area service identification | |
| CN113569257B (en) | User authority management method and device in gray level release | |
| US20070124185A1 (en) | State engine for business process execution | |
| CN111198915A (en) | Data distribution system and method based on public information model | |
| CN108008966B (en) | Resource updating method and system | |
| KR20120124931A (en) | User-definable Process-based Management System for Urban Planning and Recording Media for the Same | |
| US20220035946A1 (en) | Data processing systems for identifying and modifying processes that are subject to data subject access requests | |
| CN114721945A (en) | Graph database-based distribution method and device, electronic equipment and storage medium | |
| CN114237634A (en) | Application release risk identification method, device, equipment, medium and program product | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN114240392A (en) | Information processing method, task approval method, and information processing apparatus | |
| Morita | Toward Realization of Service-Oriented Architecture(SOA) | |
| EP2601627B1 (en) | Transaction processing system and method | |
| CN112632169B (en) | Automatic financial data reporting method and device and computer equipment | |
| US11949639B2 (en) | Intelligent management of hero cards that display contextual information and actions for backend systems | |
| CN103634326B (en) | A kind of method and device for processing application system request message | |
| US20220231977A1 (en) | Intelligent management of hero cards that display contextual information and actions for backend systems |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201013 Address after: 250100 Ji'nan high tech Zone, Shandong, No. 1036 wave road Applicant after: INSPUR GENERAL SOFTWARE Co.,Ltd. Address before: 250100, No. 2877, fairway, Sun Town, Ji'nan hi tech Zone, Shandong Applicant before: SHANDONG INSPUR GENESOFT INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |