CN112685075A - Gray scale distribution method and device, electronic equipment and computer readable medium - Google Patents
Gray scale distribution method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN112685075A CN112685075A CN202011635569.7A CN202011635569A CN112685075A CN 112685075 A CN112685075 A CN 112685075A CN 202011635569 A CN202011635569 A CN 202011635569A CN 112685075 A CN112685075 A CN 112685075A
- Authority
- CN
- China
- Prior art keywords
- service
- configuration table
- target
- access request
- information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000004044 response Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 238000011835 investigation Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 238000010276 construction Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 239000003795 chemical substances by application Substances 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Abstract
The embodiment of the disclosure discloses a gray scale publishing method, a gray scale publishing device, electronic equipment and a computer readable medium. One embodiment of the method comprises: receiving a service access request of a user; determining a target configuration table corresponding to the access request from a preset service dependency relationship configuration table; and determining a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and executing the target service application. According to the embodiment, the environment of gray scale release is more stable by adding the service dependency relationship configuration table, and the building process of the gray scale environment is simplified.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to a gray scale publishing method, a gray scale publishing device, electronic equipment and a computer readable medium.
Background
Gray scale distribution refers to a distribution method that can smoothly transition between black and white. The gray scale distribution can ensure the stability of the whole system. However, when the gray scale distribution environment is constructed, different application services need to be called, so that the construction and implementation of the gray scale distribution environment have the following problems:
firstly, the process is complex;
second, instability is prone to occur.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Some embodiments of the present disclosure propose a gradation issuance method, an electronic apparatus, an electronic device, and a computer-readable medium to solve the technical problems mentioned in the above background section.
In a first aspect, some embodiments of the present disclosure provide a gray scale publishing method, including: receiving a service access request of a user; determining a target configuration table corresponding to the access request from a preset service dependency relationship configuration table, wherein the service dependency relationship configuration table comprises a calling relationship between a service corresponding to the service access request and a service application and gray release version information of the service application, and the target configuration table comprises target gray release version information of the service application determined through the calling relationship; and determining a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and executing the target service application.
In a second aspect, some embodiments of the present disclosure provide a gray scale issuing apparatus including: a receiving unit configured to receive a service access request of a user; the system comprises a first determining unit, a second determining unit and a third determining unit, wherein the first determining unit is configured to determine a target configuration table corresponding to an access request from a preset service dependency configuration table, the service dependency configuration table comprises a calling relationship between a service corresponding to a service access request and a service application and gray release version information of the service application, and the target configuration table comprises target gray release version information of the service application determined by the calling relationship; and the second determining unit is configured to determine a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and execute the target service application.
In a third aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the gray scale publishing method as in the first aspect.
In a fourth aspect, some embodiments of the disclosure provide a computer readable medium having a computer program stored thereon, wherein the program when executed by a processor implements the greyscale distribution method as in the first aspect.
The above embodiments of the present disclosure have the following beneficial effects: the gray scale publishing method of some embodiments of the disclosure makes the environment of gray scale publishing more stable by adding the service dependency configuration table. Specifically, the reasons for the complex construction process of the gray scale publishing system and the unstable environment operation are as follows: the establishment of the gray scale environment requires the cooperation of each application service, and the calling relationship among the application services is complex, so that the gray scale environment is not only complex in establishment flow, but also easy to generate unstable conditions in the operation process. Based on this, the gray scale publishing method of some embodiments of the present disclosure may be configured by adding a service dependency relationship configuration table, and matching target gray scale publishing version information corresponding to the service application from the service dependency relationship configuration table according to the service access request; then, the target service application can be determined according to the target gray release version information, and finally, the target service application is executed. Therefore, the calling relation among the service applications is simplified through the service dependency relation configuration table, and various combinations of the service applications are realized. When the execution result of the target service application is not good enough, other target service applications can be adjusted in time according to the service dependency configuration table, so that the condition that the operation of the gray scale release environment is unstable is reduced, and the construction flow of the gray scale environment is simplified.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
FIG. 1 is a schematic illustration of one application scenario of a gray scale publishing method according to some embodiments of the present disclosure;
FIG. 2 is a flow diagram of some embodiments of a gray scale publishing method according to the present disclosure;
FIG. 3 is a flow diagram of further embodiments of a gray scale publishing method according to the present disclosure;
FIG. 4 is a flow diagram of still further embodiments of a gray scale publishing method according to the present disclosure;
FIG. 5 is a schematic block diagram of some embodiments of a gray scale publishing device according to the present disclosure;
FIG. 6 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a schematic diagram 100 of one application scenario of a grayscale publishing method according to some embodiments of the present disclosure.
In the application scenario of fig. 1, first, the electronic device 101 may receive a service access request 102 of a user. Determining a target configuration table 103 corresponding to the access request from a preset service dependency configuration table, wherein the service dependency configuration table comprises the calling relationship among a plurality of service applications called by the service corresponding to the service access request 102 and the gray release version information of the service applications; determining a target service application 106 corresponding to the service access request according to the target gray scale release configuration 105 information contained in the target configuration table 103; the target service application 106 is executed through the target call relation 104 contained in the target configuration table 103.
The electronic device 101 may be hardware or software. When the electronic device is hardware, the electronic device may be implemented as a distributed cluster formed by a plurality of servers or terminal devices, or may be implemented as a single server or a single terminal device. When the electronic device is embodied as software, it may be installed in the above-listed hardware devices. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
It should be understood that the number of electronic devices in fig. 1 is merely illustrative. There may be any number of electronic devices, as desired for implementation.
With continued reference to fig. 2, a flow 200 of some embodiments of a gray scale publishing method according to the present disclosure is shown. The gray scale publishing method comprises the following steps:
In some embodiments, the execution subject of the gray scale publishing method (e.g., the electronic device 101 shown in fig. 1) may receive the service access request input by the user through a wired connection manner or a wireless connection manner. The service access request may be a request for viewing a house source or a request for registering a new account. It should be noted that the wireless connection means may include, but is not limited to, a 3G/4G/5G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a uwb (ultra wideband) connection, and other wireless connection means now known or developed in the future.
In some embodiments, the execution subject may determine the target configuration table corresponding to the service access request by matching. The service dependency configuration table may be preset by a technician and stored on the execution agent. The service dependency relationship configuration table may include a call relationship between a service corresponding to the service access request and the service application, and grayscale release version information of the service application. As an example, the service access request may be to view a house source, the service application called by the service corresponding to the service access request may be a face authentication service and a house source database service, and the call relationship may be to first pass the face authentication service, confirm that the user passes the face authentication, and then call the house source database service to view the house source. The gradation issuance configuration information may include: calling the relationship (checking the house source, calling, passing the face authentication service, and then calling the house source database service); and gray release version information of the service application: the version of the face authentication service v.1, the version of the house source database service v.1, the version of the face authentication service v.1, the version of the house source database service v.2, the version of the face authentication service v.2, the version of the house source database service v.1, the version of the face authentication service v.2 and the version of the house source database service v.2 are used. As an example, the target configuration table may be "face authentication service v.1 version; house source database service v.1 version ". That is, the target configuration table may contain target gray release version information of the service application determined according to the call relation.
In some embodiments, the target configuration table may contain target grayscale release version information such as "face authentication service v.1 version" and "house source database service v.1 version", as an example. The execution subject may determine a target service application of a corresponding version according to the target gray release version information and execute the target service application.
According to the information gray scale release method disclosed by some embodiments of the disclosure, a service dependency relationship configuration table is added, so that the gray scale release environment is more stable. Specifically, the reason why the construction process of the gray scale publishing system is complex and the operation environment is unstable is that: the establishment of the gray scale environment requires the cooperation of each application service, and the calling relationship among the application services is complex, so that the gray scale environment is not only complex in establishment flow, but also easy to generate unstable conditions in the operation process. Based on this, the gray scale publishing method of some embodiments of the present disclosure may be configured by adding a service dependency relationship configuration table, and matching target gray scale publishing version information corresponding to the service application from the service dependency relationship configuration table according to the service access request; then, the target service application can be determined according to the target gray release version information, and finally, the target service application is executed. Therefore, the calling relation among the service applications is simplified through the service dependency relation configuration table, and various combinations of the service applications are realized. When the execution result of the target service application is not good enough, other target service applications can be adjusted in time according to the service dependency configuration table, so that the condition that the operation of the gray scale release environment is unstable is reduced, and the construction flow of the gray scale environment is simplified.
With continued reference to fig. 3, a flow 300 of some embodiments of a gray scale publishing method according to the present disclosure is shown. The gray scale publishing method comprises the following steps:
In some embodiments, an executing agent (e.g., electronic device 101 shown in FIG. 1) may determine the service dependencies by querying a lookup table about the business and service applications, as an example.
In some embodiments, as an example, the service dependencies may be: the house source database service relies on a face authentication service. The generated service dependency configuration table may be: calling relationship (the "call" to view house source passes the face authentication service first, and then calls the house source database service), and gray release version information of the service application: "face authentication service v.1 version, house source database service v.1 version".
And 305, determining a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and executing the target service application.
In some embodiments, specific implementation of steps 303, 304, and 305 and technical effects thereof may refer to steps 201, 202, and 203 in the embodiment corresponding to fig. 2, and are not described herein again.
As can be seen from fig. 3, compared with the description of some embodiments corresponding to fig. 2, the flow 300 of the gray scale generation method in some embodiments corresponding to fig. 4 shows how to generate the service dependency configuration table. By determining the service dependency relationship between the service application called by the service and the service application and generating the corresponding service dependency relationship configuration table based on the service dependency relationship, a service dependency relationship configuration table can be ensured to be generated for each service.
With further reference to fig. 4, a flow 400 of further embodiments of a gray scale publishing method is shown. The process 400 of the gray scale publishing method comprises the following steps:
In some embodiments, the service access request includes requesting service information. The request service information is used for characterizing the service accessed by the user.
In some embodiments, the execution subject (e.g., the electronic device 101 shown in fig. 1) may determine whether the request service information belongs to a preset service by querying a database, and the request service information may be a service related to viewing a house source or a service related to changing a password.
In some embodiments, the service dependency configuration table may contain a plurality of service dependency configuration tables. The initial service dependency configuration table may be used to process the request traffic information. The first identification information may be used to identify the request service information. As an example, the request service information may be "view house source", and the first identification information may be "view house source" or "house source".
In some embodiments, the execution principal may randomly select one of the initial service dependency configuration tables as the target configuration table.
In an optional implementation manner of some embodiments, the service access request includes user identity information; and determining a target configuration table corresponding to the access request according to the initial service dependency relationship configuration table, including: determining the type of user identity information; matching the type with second identification information of each initial service dependency relationship configuration table in the initial service dependency relationship configuration table, wherein the second identification information is used for describing the user identity type corresponding to the initial service dependency relationship configuration table; and in response to the matching being successful, determining a target configuration table corresponding to the access request from the initial service dependency configuration table.
As an example, the user identification information may be a user identification number (i.e., a user ID), and the type of the user identification information may be derived from the user identification number. As an example, the type of the user identification information may be determined according to the last digit of the user identification, and the type of the user identification information may be recorded as "1" if the last digit of the user identification is singular, and may be recorded as "0" if the last digit of the user identification is even. As an example, the second identification information is used to describe a user identity type corresponding to the initial service dependency configuration table. As an example, the second identifier may be "1" or "0". As an example, in response to the matching being successful, the execution subject may determine a target configuration table corresponding to the access request from the initial service dependency configuration table according to a preset rule.
In an optional implementation manner of some embodiments, the determining, from the initial service dependency configuration table, a target configuration table corresponding to the access request includes: and responding to a plurality of successfully matched initial service dependency relationship configuration tables, and randomly selecting one from the successfully matched initial service dependency relationship configuration tables as a target configuration table. As an example, there are three initial service dependency configuration tables with the first identification being "View House Source" and the second identification being "1". The execution main body can check which initial service dependency configuration table has the least access times according to the historical access records of the initial service dependency configuration table, and takes the initial service dependency configuration table with the least access times as a target configuration table.
In some embodiments, the specific implementation of step 405 and the technical effect thereof may refer to step 203 in the embodiment corresponding to fig. 2, which is not described herein again.
In an optional implementation of some embodiments, the method further comprises: in response to detecting an access completion signal corresponding to the access request, displaying a trial version investigation interface, wherein the trial version investigation interface comprises a version score of the service application corresponding to the service; and responding to the received selection signal corresponding to the version score, and replacing the target configuration table according to the selection signal to obtain an updated target configuration table. As an example, the service applications corresponding to the "view house source" service included in the version trial investigation interface may be a "face authentication service v.1 version" and a "house source database service v.1 version", and the version trial investigation interface includes score selection buttons respectively corresponding to the "face authentication service v.1 version" and the "house source database service v.1 version".
In an optional implementation of some embodiments, wherein the selection signal comprises a user score for the version of each service application by the user; and in response to receiving the selection signal corresponding to the version score, replacing the target configuration table according to the selection signal to obtain an updated target configuration table, including: obtaining updated gray release configuration information according to the user score; matching the gray release configuration information in the initial service dependency relationship configuration table with the updated gray release configuration information; and responding to the successful matching, and taking the initial service dependency relationship configuration table corresponding to the gray scale release configuration information which is successfully matched as an update target configuration table corresponding to the selection signal. As an example, the options of the score may be 1 score, 2 scores, 3 scores, all the scores are added, and if the total score is less than 3 scores, the gradation issuance configuration information is updated. And the user scores versions of the face authentication service and the house source database service. The score of the 'face authentication service v.1 version' can be 1 score, the score of the 'house source database service v.1 version' can be 1 score, the total score is 2 scores, the score is lower than 3 scores, and gray release configuration information needs to be updated. And checking whether the face authentication service and the house source database service have other versions through the database, if not, updating, and if so, updating to other versions. As an example, the update gray release configuration information may be "face authentication service v.2 version" and "house source database service v.2 version". And matching each gray scale release configuration information in the initial service dependency relationship configuration table with the updated gray scale release configuration information to obtain an updated target configuration table.
In an optional implementation of some embodiments, the method further comprises: and updating the type of the user identity information according to the second identification information corresponding to the updated target configuration table to obtain updated identity information. As an example, the second identification information corresponding to the update target configuration table may be "0", the user identification information may be a user identification number (i.e., a user ID), the type of the user identification information may be determined according to the last digit of the user identification, the type of the user identification information may be "1" if the last digit of the user identification is singular, and the type of the user identification information may be "0" if the last digit of the user identification is even. If the type of the user identification information is "1", the last bit of the user identification number may be added with 1, and then the type of the user identification information is updated to "0".
As can be seen from fig. 4, compared with the description of some embodiments corresponding to fig. 3, the flow 400 of the gray scale publishing method in some embodiments corresponding to fig. 4 shows how to determine the target configuration table. And determining a target configuration table in a mode of matching request service information included in the service access request with the first identifier of the service dependency configuration table.
With further reference to fig. 5, as an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a grayscale issuing device, which correspond to those shown in fig. 3, and which may be applied in various electronic devices in particular.
As shown in fig. 5, the grayscale issuing device 500 of some embodiments includes a receiving unit 501, a first determining unit 502, a second determining unit 503, and an executing unit 504: a receiving unit 501 configured to receive a service access request of a user; a first determining unit 502 configured to determine a target configuration table corresponding to the access request from a preset service dependency configuration table, where the service dependency configuration table includes a call relationship between a service corresponding to the service access request and a service application and gray release version information of the service application, and the target configuration table includes target gray release version information of the service application determined by the call relationship; a second determining unit 503, configured to determine a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and execute the target service application.
In an alternative implementation of some embodiments, the apparatus 500 further comprises a query unit (not shown in the figures) configured to: inquiring service applications called by the service, and determining service dependency relationship among the service applications; a generating unit (not shown in the figure) configured to: and generating a corresponding service dependency configuration table based on the service dependency.
In an optional implementation of some embodiments, the service access request includes request service information; and, the first determining unit 502 is further configured to: determining whether the request service information belongs to a preset service; responding to the preset service, and determining an initial service dependency relationship configuration table corresponding to the request service information according to the first identification information of each service dependency relationship configuration table in the service dependency relationship configuration tables, wherein the first identification information is used for identifying the service information; and determining a target configuration table according to the initial service dependency relationship configuration table.
In an optional implementation manner of some embodiments, the service access request includes user identity information; and, the first determining unit 502 is further configured to: determining the type of user identity information; the type is matched with second identification information of an initial service dependency relationship configuration table in the initial service dependency relationship configuration table, and the second identification information is used for describing the user identity type corresponding to the initial service dependency relationship configuration table; and in response to the matching being successful, determining a target configuration table corresponding to the access request from the initial service dependency configuration table.
In an optional implementation of some embodiments, the first determining unit 502 is further configured to: and responding to a plurality of successfully matched initial service dependency relationship configuration tables, and randomly selecting one from the successfully matched initial service dependency relationship configuration tables as a target configuration table.
In an alternative implementation of some embodiments, the apparatus 500 further comprises a presentation unit (not shown in the figures) configured to: in response to detecting an access completion signal corresponding to the access request, displaying a trial version investigation interface, wherein the trial version investigation interface comprises a version score of the service application corresponding to the service; the replacement unit (not shown in the figure) is configured to: and responding to the received selection signal corresponding to the version score, and replacing the target configuration table according to the selection signal to obtain an updated target configuration table.
In an optional implementation of some embodiments, wherein the selection signal comprises a user score for the version of each service application by the user; and the replacement unit (not shown in the figures) is further configured to: obtaining updated gray release configuration information according to the user score; matching the gray release configuration information in the initial service dependency relationship configuration table with the updated gray release configuration information; and responding to the successful matching, and taking the initial service dependency relationship configuration table corresponding to the gray scale release configuration information which is successfully matched as an update target configuration table corresponding to the selection signal.
In an optional implementation of some embodiments, the apparatus 500 further comprises an updating unit (not shown in the figures) further configured to: and updating the type of the user identity information according to the second identification information corresponding to the updated target configuration table to obtain updated identity information.
It will be appreciated that the storage elements described in the apparatus 500 correspond to the various steps in the method described with reference to fig. 3. Thus, the operations, features and resulting advantages described above with respect to the method are also applicable to the apparatus 500 and the units included therein, and are not described herein again.
Referring now to fig. 6, a schematic diagram of an electronic device (e.g., the server or terminal device of fig. 1) 600 suitable for use in implementing some embodiments of the present disclosure is shown. The electronic device in some embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle-mounted terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, electronic device 600 may include a processing means (e.g., central processing unit, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 6 may represent one device or may represent multiple devices as desired.
In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of some embodiments of the present disclosure.
It should be noted that the computer readable medium described in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a service access request of a user; determining a target configuration table corresponding to the access request from a preset service dependency relationship configuration table, wherein the service dependency relationship configuration table comprises a calling relationship between a service corresponding to the service access request and a service application and gray release version information of the service application, and the target configuration table comprises target gray release version information of the service application determined through the calling relationship; and determining a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and executing the target service application.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in some embodiments of the present disclosure may be implemented by software, and may also be implemented by hardware. The described units may also be provided in a processor, and may be described as: a processor includes a pre-receiving unit, a first determining unit, and a second determining unit. Where the names of these elements do not in some cases constitute a limitation of the element itself, for example, a receiving element may also be described as an "element receiving a service access request of a user".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.
Claims (11)
1. A gray scale publishing method, comprising:
receiving a service access request of a user;
determining a target configuration table corresponding to the access request from a preset service dependency relationship configuration table, wherein the service dependency relationship configuration table comprises a calling relationship between a service corresponding to the service access request and a service application and gray release version information of the service application, and the target configuration table comprises target gray release version information of the service application determined through the calling relationship;
and determining a target service application corresponding to the service access request according to the target gray release version information contained in the target configuration table, and executing the target service application.
2. The method of claim 1, wherein the method further comprises:
inquiring service applications called by the service, and determining service dependency relationship among the service applications;
and generating a corresponding service dependency configuration table based on the service dependency.
3. The method of claim 1, wherein the service access request comprises a request for service information; and
the determining a target configuration table corresponding to the access request from a preset service dependency configuration table includes:
determining whether the request service information belongs to a preset service;
responding to the preset service, and determining an initial service dependency relationship configuration table corresponding to the request service information according to first identification information of each service dependency relationship configuration table in the service dependency relationship configuration tables, wherein the first identification information is used for identifying service information;
and determining the target configuration table according to the initial service dependency relationship configuration table.
4. The method of claim 3, wherein the service access request includes user identity information; and
the determining the target configuration table corresponding to the access request according to the initial service dependency configuration table includes:
determining the type of the user identity information;
matching the type with second identification information of an initial service dependency relationship configuration table in the initial service dependency relationship configuration table, wherein the second identification information is used for describing the user identity type corresponding to the initial service dependency relationship configuration table;
and in response to successful matching, determining the target configuration table corresponding to the access request from the initial service dependency configuration table.
5. The method of claim 4, wherein the determining a target configuration table corresponding to the access request from the initial service dependency configuration table comprises:
and responding to a plurality of successfully matched initial service dependency relationship configuration tables, and randomly selecting one from the successfully matched initial service dependency relationship configuration tables as a target configuration table.
6. The method of claim 5, wherein the method further comprises:
in response to detecting an access completion signal corresponding to the access request, displaying a version trial investigation interface, wherein the version trial investigation interface comprises a version score of a service application corresponding to the service;
and responding to the received selection signal corresponding to the version score, and replacing the target configuration table according to the selection signal to obtain an updated target configuration table.
7. The method of claim 6, wherein the selection signal comprises a user score for a version of each service application by a user; and
the updating the target configuration table according to the received selection signal corresponding to the version score to obtain an updated target configuration table comprises:
obtaining the updated gray release configuration information according to the user score;
matching the gray scale release configuration information in the initial service dependency relationship configuration table with the updated gray scale release configuration information;
and in response to the successful matching, taking an initial service dependency relationship configuration table corresponding to the gray scale release configuration information which is successfully matched as the update target configuration table corresponding to the selection signal.
8. The method of claim 7, wherein the method further comprises:
and updating the type of the user identity information according to the second identification information corresponding to the updated target configuration table to obtain updated identity information.
9. A gradation issuance apparatus comprising:
a receiving unit configured to receive a service access request of a user;
a first determining unit, configured to determine a target configuration table corresponding to the access request from a preset service dependency configuration table, where the service dependency configuration table includes a call relationship between a service corresponding to the service access request and a service application and gray release version information of the service application, and the target configuration table includes target gray release version information of the service application determined by the call relationship;
and the second determining unit is configured to determine a target service application corresponding to the service access request according to the target gray scale release version information contained in the target configuration table, and execute the target service application.
10. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-8.
11. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011635569.7A CN112685075A (en) | 2020-12-31 | 2020-12-31 | Gray scale distribution method and device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011635569.7A CN112685075A (en) | 2020-12-31 | 2020-12-31 | Gray scale distribution method and device, electronic equipment and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112685075A true CN112685075A (en) | 2021-04-20 |
Family
ID=75456324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011635569.7A Pending CN112685075A (en) | 2020-12-31 | 2020-12-31 | Gray scale distribution method and device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112685075A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114401187A (en) * | 2022-01-17 | 2022-04-26 | 中国工商银行股份有限公司 | Gray scale distribution method and device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130145028A1 (en) * | 2011-12-05 | 2013-06-06 | Google Inc. | Access Control List |
| CN108881030A (en) * | 2018-06-07 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Gray scale issues the method for routing and device under scene |
| CN110941839A (en) * | 2019-11-18 | 2020-03-31 | 中国经济信息社有限公司 | User authority management method and system, equipment and storage medium |
| CN111443941A (en) * | 2020-03-27 | 2020-07-24 | 中国平安财产保险股份有限公司 | Method and device for gray scale publishing |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
-
2020
- 2020-12-31 CN CN202011635569.7A patent/CN112685075A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130145028A1 (en) * | 2011-12-05 | 2013-06-06 | Google Inc. | Access Control List |
| CN108881030A (en) * | 2018-06-07 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Gray scale issues the method for routing and device under scene |
| CN110941839A (en) * | 2019-11-18 | 2020-03-31 | 中国经济信息社有限公司 | User authority management method and system, equipment and storage medium |
| CN111443941A (en) * | 2020-03-27 | 2020-07-24 | 中国平安财产保险股份有限公司 | Method and device for gray scale publishing |
| CN112000348A (en) * | 2020-07-28 | 2020-11-27 | 金蝶医疗软件科技有限公司 | Control method and device for service gray release and computer equipment |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114401187A (en) * | 2022-01-17 | 2022-04-26 | 中国工商银行股份有限公司 | Gray scale distribution method and device, computer equipment and storage medium |
| CN114401187B (en) * | 2022-01-17 | 2024-02-23 | 中国工商银行股份有限公司 | Gray scale issuing method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110781373B (en) | List updating method and device, readable medium and electronic equipment | |
| CN111800513B (en) | Method and device for pushing information and computer readable medium of electronic equipment | |
| CN110569057A (en) | gray scale distribution method and device, electronic equipment and computer readable medium | |
| CN110300165B (en) | Method, device and equipment for calling functional program and storage medium | |
| CN111209306A (en) | Business logic judgment method and device, electronic equipment and storage medium | |
| CN111596991A (en) | Interactive operation execution method and device and electronic equipment | |
| CN111432001A (en) | Method, apparatus, electronic device, and computer-readable medium for jumping scenes | |
| CN111782329A (en) | Node dragging method, device, equipment and computer readable medium | |
| CN111694629A (en) | Information display method and device and electronic equipment | |
| CN111273830A (en) | Data display method and device, electronic equipment and computer readable medium | |
| CN111596992B (en) | Navigation bar display method and device and electronic equipment | |
| CN110619101B (en) | Method and apparatus for processing information | |
| CN112685075A (en) | Gray scale distribution method and device, electronic equipment and computer readable medium | |
| CN112732302A (en) | Configuration updating method and device of application program and electronic equipment | |
| CN110827037A (en) | Data interaction method and device based on block chain | |
| CN111787041A (en) | Method and apparatus for processing data | |
| CN112507676B (en) | Method and device for generating energy report, electronic equipment and computer readable medium | |
| CN111626802A (en) | Method and apparatus for processing information | |
| CN115292635A (en) | Page floor data display method, device, equipment and computer readable medium | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN111338621B (en) | Method, apparatus, electronic device and computer readable medium for displaying data | |
| CN114428925A (en) | Page rendering method and device, electronic equipment and computer readable medium | |
| CN114089891A (en) | Display control method and device and electronic equipment | |
| CN112100205A (en) | Data processing method, device, equipment and computer readable medium | |
| CN111580890A (en) | Method, apparatus, electronic device, and computer-readable medium for processing features |
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 |