Information writing method, device, storage medium, and information storage server

Abstract

The present disclosure provides an information writing method, device, storage medium and information storage server. The method comprises: generating corresponding permission information according to a service processing request, wherein the permission information comprises a permission subject user identifier, and the permission subject user identifier is used to indicate a user having a first control right over the permission information according to law; generating a corresponding permission information writing request based on the permission information and a deployment unit identifier of a first current deployment unit; and sending the generated permission information writing request to a corresponding to-be-written deployment unit. The corresponding to-be-written deployment unit is determined based on the permission subject user identifier in the permission information of each permission information writing request. Thus, the to-be-written deployment unit can be selected within the range allowed by laws and regulations and the range approved by the permission subject user, the safety of the permission information processing can be ensured, and the information interaction performance can be taken into account.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of information interaction, and in particular, to an information writing method and device, a storage medium, and an information storage server. BACKGROUND

[0002] An information interaction application is a terminal service in which two or more people use a network to exchange text information, files, images, voice, and video. The information interaction application has become a communication tool used by most netizens.

[0003] Information interaction between different users often involves some permission settings, and the interaction between users needs to follow these permission settings. Therefore, the communication between users needs to be authenticated to ensure communication security. How the permission information is stored often affects the related information interaction process and, in turn, affects the information interaction performance. How to ensure communication security and provide better information interaction performance is one of the technical problems to be solved. SUMMARY

[0004] Embodiments of the present disclosure provide an information writing method and device, a storage medium, and an information storage server.

[0005] In a first aspect, embodiments of the present disclosure provide an information writing method, which includes: generating at least one piece of permission information according to a service processing request, wherein the permission information includes a permission subject user identifier, and the permission subject user identifier is used to indicate a user who has a first control right over the permission information according to law; generating a corresponding permission information writing request based on the permission information and a first current deployment unit identifier, wherein the first current deployment unit includes a deployment unit used to execute the generation of the corresponding permission information writing request; and sending each generated permission information writing request to a corresponding to-be-written deployment unit to instruct the corresponding to-be-written deployment unit to perform a writing process based on the received permission information writing request, wherein the corresponding to-be-written deployment unit is determined based on the permission subject user identifier in the permission information of each permission information writing request.

[0006] In a second aspect, embodiments of the present disclosure provide an information writing method, which includes: in response to receiving a permission information writing request, parsing the received permission information writing request to obtain a target permission subject user identifier and a source deployment unit identifier; determining whether the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit; in response to a determination that the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit, determining to-be-written permission information based on the received permission information writing request, and writing the to-be-written permission information into a permission information set in a fourth current deployment unit, wherein the to-be-written permission information includes a permission subject user identifier, and the fourth current deployment unit includes a deployment unit determined based on the permission subject user identifier included in the to-be-written permission information.

[0007] In a third aspect, embodiments of the present disclosure provide an information writing device, the device comprising: a permission information generation unit configured to generate at least one piece of permission information according to a service processing request, wherein the permission information comprises a permission subject user identifier, and the permission subject user identifier is used to indicate a user having a first control right over the permission information according to law; a writing request generation unit configured to generate a corresponding permission information writing request based on the permission information and a first current deployment unit identifier, the first current deployment unit comprising a deployment unit used to execute the generated corresponding permission information writing request; and a writing request sending unit configured to send each generated permission information writing request to a corresponding to-be-written deployment unit to instruct the corresponding to-be-written deployment unit to perform a writing process based on the received permission information writing request, wherein the permission subject user identifier in the permission information of each permission information writing request has an association relationship with the corresponding to-be-written deployment unit.

[0008] In a fourth aspect, embodiments of the present disclosure provide an information writing device, comprising: a first analysis unit configured to analyze a received permission information writing request to obtain a target permission subject user identifier and a source deployment unit identifier in response to receiving the permission information writing request; a first determination unit configured to determine whether the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit; and a first writing unit configured to determine to-be-written permission information based on the received permission information writing request and write the to-be-written permission information into a permission information set in a fourth current deployment unit in response to a determination that the to-be-written permission information comprises a permission subject user identifier, and the fourth current deployment unit comprises a deployment unit determined based on the permission subject user identifier comprised in the to-be-written permission information.

[0009] In a fifth aspect, embodiments of the present disclosure provide a computer readable storage medium having a computer program stored thereon, wherein the computer program is executed by one or more processors to implement the method described in any implementation manner of the first aspect and / or the second aspect.

[0010] In a sixth aspect, embodiments of the present disclosure provide an information storage server, comprising: one or more processors; and a storage device having one or more programs stored thereon, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method described in any implementation manner of the first aspect and / or the second aspect.

[0011] The embodiment of the information writing method, device, storage medium and information storage server provided by the embodiment of the present disclosure, by generating corresponding permission information according to the business processing request, the permission information includes the permission subject user identifier for indicating the user having the first control right to the permission information according to the law, generating a corresponding permission information writing request based on the permission information and the deployment unit identifier of the first current deployment unit, and sending the generated permission information writing request to the corresponding to-be-written deployment unit, wherein the corresponding to-be-written deployment unit is determined based on the permission subject user identifier in the permission information of each permission information writing request. Since the permission subject user identifier is set in the permission information, and the to-be-written deployment unit is determined based on the permission subject user identifier when the permission information writing request is sent to the to-be-written deployment unit for permission information writing processing, the to-be-written deployment unit has the permission of the permission subject user before processing the permission information writing request, so that the to-be-written deployment unit can be selected within the range allowed by laws and regulations and the range approved by the permission subject user, the safety of the permission information processing can be ensured, and the information interaction performance can be considered. BRIEF DESCRIPTION OF DRAWINGS

[0012] Other features, objects, and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments made with reference to the accompanying drawings. The drawings are for purposes of illustrating the specific embodiments only and are not to be construed as limiting the application. In the drawings:

[0013] Figure 1 is an exemplary system architecture diagram in which one embodiment of the information writing method according to the present disclosure can be applied;

[0014] Figure 2 is a flowchart of one embodiment of the information writing method according to the present disclosure;

[0015] Figure 3 is a flowchart of one embodiment of another information writing method according to the present disclosure;

[0016] Figure 4 is a structural schematic diagram of one embodiment of the information writing device according to the present disclosure;

[0017] Figure 5 is a structural schematic diagram of one embodiment of another information writing device according to the present disclosure;

[0018] Figure 6 is a structural schematic diagram of a computer system suitable for implementing the information storage server of the present disclosure. DETAILED DESCRIPTION

[0019] The present disclosure will be further described below in conjunction with the drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the related application, and not to limit the application. In addition, it should be noted that, for the sake of description, only the parts related to the application are shown in the drawings.

[0020] It should be noted that the embodiments in the present disclosure and the features in the embodiments can be combined with each other without conflict. The present disclosure will be described in detail below with reference to the drawings and in conjunction with the embodiments.

[0021] Figure 1 An exemplary system architecture 100 of one embodiment to which the information writing method and device of the present disclosure can be applied is shown.

[0022] As shown in Figure 1 , the system 100 can include deployment units 101, 102, 103, 104, 105 and a network 106. The network 106 is used to provide a communication link medium between the deployment units 101, 102, 103, 104, 105. The network 106 can include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0023] A user can use a client (not shown in the Figure 1 ) to interact with any of the deployment units 101, 102, 103, 104, 105 to receive or send information, etc. Various communication client applications can be installed on the client (not shown in the Figure 1 ), such as audio and video conference applications, instant messaging tools, voice recognition applications, web browser applications, shopping applications, search applications, email clients, social platform software, etc.

[0024] The deployment units 101, 102, 103, 104, 105 can be deployment units that provide information interaction related services. The deployment units 101, 102, 103, 104, 105 can analyze and process the received information interaction service related business processing requests and other data, and can also feed back the processing results to the client.

[0025] It should be noted that the deployment units 101, 102, 103, 104, 105 can be hardware or software. When the deployment units 101, 102, 103, 104, 105 are hardware, they can be implemented as a distributed deployment unit composed of multiple servers, or as a single server. The deployment units 101, 102, 103, 104, 105 can each be a server cluster composed of servers located in the same machine room or region, or a server cluster composed of servers in different machine rooms or regions.

[0026] It should be noted that the information writing method provided by the present disclosure is generally executed by the deployment units 101, 102, 103, 104, 105, and correspondingly, the information writing device is generally arranged in the deployment units 101, 102, 103, 104, 105.

[0027] It should be understood that Figure 1 The number of deployment units and networks in the above-mentioned embodiments is only illustrative. According to the implementation needs, there can be any number of deployment units and networks.

[0028] With reference to Figure 2 , a flow 200 of one embodiment of the information writing method according to the present disclosure is shown. The information writing method, which can be applied to a deployment unit, includes the following steps:

[0029] Step 201, generating at least one piece of permission information according to a service processing request.

[0030] In the present embodiment, the execution subject of the information writing method (for example, the deployment units 101, 102, 103, 104, 105 shown in Figure 1 The deployment units 101, 102, 103, 104, 105 shown in the above-mentioned embodiments can generate at least one piece of permission information according to a specific service processing request received in the case of detecting a service processing request, for example, a service processing request received from a client network connected to the deployment unit. For another example, it can also be a service processing request received from other logical processing function modules in the deployment unit.

[0031] In some optional embodiments, the service processing request can include service operation information. The service operation information is used to represent a specific operation to be executed. The above-mentioned service operation information can include operation subject user identifier, specific action (Action) to be executed, and in some cases, operation object identifier (may also not include operation object identifier). In addition, the service operation information can also correspond to the corresponding permission.

[0032] The execution subject can generate at least one piece of permission information according to the specific business processing request in various implementation manners. Here, the permission information can include a permission subject user identifier. The permission subject user identifier is used to indicate a user who has a first control right over the permission information according to law. The first control right includes, for example, storage, authentication, and the like. The first control right can also include a modification right of the permission information, or the first control right can not include the modification right of the permission information. Generally, the permission subject user indicated by the permission subject user identifier in the permission information is generally the permission control party in the corresponding permission information, that is, the permission subject user has the control right. The permission information can also include a permission identifier, which is used to indicate a specific permission that the permission subject user requests to have with respect to the permission information. The permission subject user identifier is determined based on a relevant legal regulation and at least one of the following: an operation subject user identifier, a specific action, and an operation object user identifier. The operation subject user and the operation object user can also be referred to as a sender and a receiver.

[0033] For example, user A allows user B to establish a first communication relationship with user A, and user A can have a control right of whether to allow the establishment of the first communication relationship. The permission subject user can be user A. Alternatively, user A and user B can pre-negotiate to determine a permission subject within the scope allowed by laws and regulations. The permission subject has a first control right, for example, a storage right, with respect to the permission information related to the first communication relationship.

[0034] In some optional embodiments, the permission information can also include a permission object user identifier. The permission object user identifier is used to indicate a permission object user. The permission information including the permission object user identifier is used to represent that the permission subject user has a control right indicated by a corresponding permission identifier with respect to the permission object user, for example, whether to allow the permission object user to establish a first communication relationship with the permission subject user.

[0035] As an example, the business operation information can be used to represent that user A requests to establish a first preset communication relationship with user B, that is, user A allows user B to communicate with user A based on the first preset communication relationship. Then, user B can subsequently send information to user A based on the first preset communication relationship. In this way, the permission subject user can be user A, the specific permission content can be to establish the first preset communication relationship, the permission object user can be user B, the permission subject user identifier in the permission information generated according to the business processing request is the user identifier "A" of user A, the permission identifier is used to represent the establishment of the first preset communication relationship, and the permission object user identifier is the user identifier "B" of user B.

[0036] For example, the business operation information is used to represent that user A requests to shield user B, i.e., user A hopes that user B cannot send information to user A based on the first preset communication relationship subsequently. In this way, the authority subject user is user A, the specific authority content is to refuse to establish the first preset communication relationship, and the authority object user is user B. Therefore, in the authority information generated according to the business processing request, the authority subject user identifier is the user identifier "A" of user A, the authority identifier is used to represent the refusal to establish the first preset communication relationship, and the authority object user identifier is the user identifier "B" of user B.

[0037] For another example, the business operation information is used to represent whether user A requests to allow any other user who has not established the first preset communication relationship with the user A to interact with the user A based on the first preset communication relationship. That is, user A hopes that any other user who has not established the first preset communication relationship with user A can interact with user A based on the first preset communication relationship subsequently. In this way, the authority subject user is user A, the specific authority content includes allowing the other user to interact with the user A based on the first preset communication relationship or not allowing the other user to interact with the user A based on the first preset communication relationship. Therefore, in the authority information generated according to the business processing request, the authority subject user identifier is the user identifier "A" of user A, and the authority identifier is used to represent the control of allowing the other user to interact with the user A based on the first preset communication relationship or not allowing the other user to interact with the user A based on the first preset communication relationship.

[0038] In some optional embodiments, the deployment unit can be composed of at least one server in a machine room. Optionally, the at least one machine room can be a machine room whose actual physical entity is located in the same designated area.

[0039] In some optional embodiments, step 201 can be performed as follows:

[0040] Based on the pre-stored association relationship between the business processing request type and the authority information type, at least one piece of authority information corresponding to the business processing request is generated. That is, for different business processing request types, corresponding authority information types can be pre-set, and corresponding authority information generation rules can be pre-set, and the corresponding authority information is generated according to the authority information generation rule corresponding to the authority information type, so as to realize automatic generation of authority information and improve information generation efficiency.

[0041] Optionally, one business processing request type in the pre-stored association relationship between the business processing request type and the authority information type can be associated with at least one authority information type. That is, according to one business processing request, at least one piece of authority information can be generated.

[0042] In some optional embodiments, the number of pieces of permission information generated in step 201, and / or the permission subject user identifier in the generated permission information, are related to at least one of the following of the service processing request: the sender, the receiver, the requested service processing operation. For example, if user A requests to establish a first communication relationship with user B, the data flow of the service processing request can be from the deployment unit to which user A belongs to the deployment unit to which user B belongs, and one piece of permission information can be generated, in which the permission subject user identifier can be "A".

[0043] In some optional embodiments, step 201 can also be performed as follows:

[0044] First, service authentication is performed on the service processing request.

[0045] Here, the execution subject can perform service authentication on the service processing request according to the service operation represented by the service operation information in the specific service processing request upon receiving the service processing request, which is not specifically limited in the present disclosure. For example, the service authentication can be to determine whether the user identity triggering the service processing request is verified.

[0046] Second, at least one piece of permission information is generated according to the service processing request in response to the service authentication passing.

[0047] Here, the execution subject can generate at least one piece of permission information according to the service processing request upon the service authentication passing on the service processing request.

[0048] With this optional embodiment, since at least one piece of permission information corresponding to the service processing request is generated only upon the service authentication passing on the service processing request, the security can be improved.

[0049] In some optional embodiments, step 201 can be performed as follows: at least one piece of permission information corresponding to the service processing request is generated based on a pre-stored association relationship between service processing request types and permission information types. For example, for a Y1 type service processing request, a Q1 type permission information can be generated, where the so-called Q1 type can be, for example, permission information with a specified permission identifier.

[0050] Step 202: generating a corresponding permission information write request based on the permission information and the first current deployment unit identifier.

[0051] In the present embodiment, the execution subject can generate a corresponding permission information write request based on each or part of the permission information generated in step 201 and the first current deployment unit identifier.

[0052] Here, the first current deployment unit includes a deployment unit for generating a corresponding permission information write request. The first current deployment unit is identified by the first current deployment unit.

[0053] At step 203, the generated permission information write request is sent to the corresponding to-be-written deployment unit.

[0054] In the present embodiment, the execution subject can send the generated permission information write request at step 202 to the corresponding to-be-written deployment unit, so as to instruct the to-be-written deployment unit to perform write processing based on the received permission information write request. Here, the to-be-written deployment unit can be at least one deployment unit.

[0055] Here, the permission subject user identifier in the permission information of each permission information write request has an association relationship with the corresponding to-be-written deployment unit.

[0056] In some optional embodiments, the to-be-written deployment unit corresponding to the permission subject user identifier can be specified in the business processing request.

[0057] In some optional embodiments, the specific to-be-written deployment unit determination rule corresponding to different types of permission information (for example, which can be classified according to the permission identifier in the permission information) can be specified in the business processing request, and the corresponding to-be-written deployment unit can be determined according to the generated permission information and the permission subject user identifier according to the corresponding rule.

[0058] In some optional embodiments, the to-be-written deployment unit corresponding to the permission information write request is determined based on the permission subject user identifier in the permission information of each permission information write request, and specifically can include: the to-be-written deployment unit corresponding to the permission information write request is determined based on the permission subject user identifier in the permission information of each permission information write request and the permission range of the permission subject identifier.

[0059] In some optional embodiments, the to-be-written deployment unit corresponding to the permission information write request can include at least one of the following first and second:

[0060] First, the deployment unit to which the permission subject user corresponding to the permission information write request belongs.

[0061] Here, it should be noted that each user identifier can be uniquely attributed to a deployment unit, which can be a deployment unit filled or selected by the user when registering. Sending the permission information writing request to the deployment unit to which the corresponding permission subject user belongs can instruct the deployment unit to which the permission subject user belongs to perform writing processing based on the received permission information writing request, so that in the future the permission information corresponding to the permission subject user can be obtained in the deployment unit to which the permission subject user belongs.

[0062] Second, the authorized private deployment unit and / or public deployment unit corresponding to the permission subject user corresponding to the permission information writing request.

[0063] Here, sending the permission information writing request to the authorized private deployment unit and / or public deployment unit corresponding to the permission subject user corresponding to the permission information writing request can instruct the authorized private deployment unit and / or public deployment unit corresponding to the permission subject user corresponding to the permission information writing request to perform writing processing based on the received permission information writing request, so that in the future the processing result based on the permission information corresponding to the permission subject user can be obtained in the authorized private deployment unit and / or public deployment unit corresponding to the permission subject user corresponding to the permission information writing request. Since the deployment unit to be written is pre-authorized by the permission subject user under the premise of meeting laws and regulations, the security of the permission information acquisition can also be improved.

[0064] Based on the above optional implementation, optionally, the above information writing method can further include the following steps 204 and 205:

[0065] Step 204, in response to detecting the permission information reading request, determining whether the target deployment unit to which the permission subject user corresponding to the permission information reading request belongs satisfies at least one of the following: the target deployment unit is a second current deployment unit; and the second current deployment unit is an authorized private deployment unit and / or public deployment unit corresponding to the target deployment unit.

[0066] Here, the above execution subject can determine whether the target deployment unit to which the permission subject user corresponding to the permission information reading request belongs satisfies at least one of the following in the case of detecting the permission information reading request:

[0067] First, the target deployment unit is a second current deployment unit.

[0068] Here, the second current deployment unit includes a deployment unit that detects the permission information reading request. That is, if the target deployment unit to which the permission subject user corresponding to the permission information reading request belongs is the deployment unit that detects the permission information reading request, it indicates that the deployment unit that detects the permission information reading request stores and has the permission to provide the processing result based on the permission information corresponding to the permission information reading request, and thus the subsequent step 205 can be continued.

[0069] Second, the second current deployment unit is an authorized private deployment unit and / or a public deployment unit corresponding to the target deployment unit.

[0070] Here, if the second current deployment unit is an authorized private deployment unit and / or a public deployment unit corresponding to the target deployment unit, it indicates that the second deployment unit has been authorized by the permission subject user corresponding to the permission information reading request, and the second current deployment unit can also store and have the permission to provide the processing result based on the permission information corresponding to the permission information reading request, and thus the subsequent step 205 can be continued.

[0071] Step 205: Based on the determination result being yes, the processing result based on the permission information corresponding to the permission information reading request in the permission information set in the second current deployment unit is returned.

[0072] Here, the above execution subject can return the processing result based on the permission information corresponding to the permission information reading request in the permission information set in the second current deployment unit based on the determination result being yes in step 204 in various implementation manners. For example, the processing result based on the permission information corresponding to the permission information reading request in the permission information set in the second current deployment unit can be returned in the case where the determination result is yes in step 204, or in the case where the determination result is yes in step 204 and other preset conditions are yes. The processing result may, for example, be an authentication result based on the permission information.

[0073] Steps 204 and 205 can be implemented to provide permission information in the second current deployment unit to achieve the integrity of the information interaction service.

[0074] In some optional embodiments, step 203 can be performed as follows:

[0075] For each generated permission information writing request, in response to passing the parameter verification of the permission information writing request, the permission information writing request is sent to the corresponding to-be-written deployment unit. Here, the parameter verification of the permission information writing request can be performed by using the same parameter verification method, or different parameter verification methods can be set according to different specific permission identifiers in the permission information writing request. For example, the parameter verification can be to verify whether the required parameters are empty.

[0076] With the optional implementation, since the permission information write request is sent to the corresponding to-be-written deployment unit only when the parameter check of the permission information write request is passed, it can be avoided that the parameter write request with parameters not meeting the requirements is sent to the corresponding to-be-written deployment unit, unnecessary calculation resource consumption of the corresponding to-be-written deployment unit is reduced, and system execution efficiency is improved.

[0077] In some optional implementations, the above information write method can further include the following steps 206, 207 and 208:

[0078] Step 206, in response to receiving the permission information write request, the received permission information write request is parsed to obtain the target permission subject user identifier and the source deployment unit identifier.

[0079] Here, the above execution subject can parse the received permission information write request to obtain the to-be-written permission information and the source deployment unit identifier according to the preset format of the permission information write request in the case of receiving the permission write request sent by the deployment unit or other deployment unit where the execution subject is located, wherein the source deployment unit identifier is used to indicate the deployment unit from which the permission information write request originates. The to-be-written permission information can include the target permission subject user identifier. The target permission subject user identifier is used to indicate the user to which the to-be-written permission information belongs.

[0080] Step 207, determine whether the received permission information write request is from the source deployment unit and the target permission subject user belongs to the source deployment unit.

[0081] Here, the source deployment unit identifier parsed in step 207 can be obtained first, and then it is determined whether the permission information write request is from the deployment unit indicated by the source deployment unit identifier, so as to determine whether the received permission information write request is from the source deployment unit. If it is determined to be yes, it indicates that the permission information write request indeed comes from the deployment unit claimed by the permission information write request.

[0082] In addition, since each user belongs to a unique deployment unit, the deployment unit identifier of the deployment unit to which the target permission subject user belongs can be obtained first, and then it is determined whether the obtained deployment unit identifier is consistent with the target deployment unit identifier, so as to determine whether the target permission subject user belongs to the source deployment unit.

[0083] If the above two aspects are determined to be yes, it indicates that the target permission subject user corresponding to the permission information parsed in step 206 belongs to the deployment unit from which the permission information write request comes.

[0084] If the above two determinations are yes, the above execution subject can proceed to step 208 for further execution.

[0085] In step 208, in response to the determination being yes, the to-be-written permission information is determined based on the received permission information write request, and the to-be-written permission information is written into the permission information set in the third current deployment unit.

[0086] Here, the above-mentioned execution subject can indicate that the permission information write request passes the verification, determine the to-be-written permission information based on the received permission information write request, and write the to-be-written permission information into the permission information set in the third current deployment unit in the case of the determination being yes in step 206, thereby realizing the processing of the permission information write request.

[0087] Here, the to-be-written permission information can be obtained based on the analysis of the permission information write request in step 206. The to-be-written permission information can include a permission subject user identifier, which is used to indicate a user who has a first control right over the permission information according to law. The first control right can include storage, authentication, etc., and can also include a modification right of the permission information, or can not include the modification right of the permission information. Alternatively, the to-be-written permission information can further include a permission identifier, which is used to indicate a specific permission claimed by the corresponding permission subject user. Alternatively, the to-be-written permission information can further include a permission object user identifier, which is used to indicate a permission object user. The permission information including the permission object user identifier is used to represent that the permission subject user has a control right indicated by the permission identifier, for example, whether to allow the permission object user to establish a first communication relationship with the permission subject user.

[0088] Here, the third current deployment unit includes a deployment unit determined based on the permission subject user identifier in the to-be-written permission information determined in step 208.

[0089] Through the above-mentioned steps 206 to 208, in the case that the permission information write request is received by the third current deployment unit, the permission subject user and whether the permission information write request comes from the deployment unit claimed by the permission subject user are first verified, and the corresponding write operation is performed in the case of passing the verification, thereby realizing the write operation of the permission information, providing a data basis for subsequent permission information read requests. Moreover, since the write operation is performed in the case of passing the verification, the permission defined by the permission information written into the third current deployment unit is safe, and in the process of providing the information interaction service, the corresponding permission verification can be performed based on the above-mentioned permission information, thereby improving the security of the mutual process between the deployment units.

[0090] In some optional embodiments, the writing of the to-be-written permission information into the permission information set in the third current deployment unit in step 208 can be performed as follows:

[0091] In response to determining that the principal user identifier in the to-be-written permission information is the same as the target principal user identifier, the to-be-written permission information is written into the permission information set in the third current deployment unit. That is, it is further needed to confirm whether the principal user identifier in the permission information to be written into the third current deployment unit is consistent with the target principal user identifier obtained by parsing the received permission write request, so as to prevent the permission information written into the third current deployment unit from being incorrect, and further improve the permission information write security. In some embodiments, the target principal user identifier in the permission write request is often written in a specific format, and when the to-be-written permission information is determined based on the received permission write request in step 208, specific processing such as deserialization needs to be performed to generate the to-be-written permission information. However, errors may occur in the specific processing such as deserialization. In order to avoid the above errors, the above further verification operation is needed to be performed to improve the permission information write security.

[0092] The method provided by the above embodiments of the present disclosure generates corresponding permission information according to a business processing request, and the permission information includes a principal user identifier for indicating a user subject to which the permission information belongs. Then, the corresponding permission information write request is generated based on the permission information and the deployment unit identifier of the first current deployment unit. Next, the generated permission information write request is sent to the corresponding to-be-written deployment unit. The corresponding to-be-written deployment unit is determined based on the principal user identifier in the permission information of each permission information write request. Furthermore, since the principal user identifier is set in the permission information, and the permission information write request is sent to the to-be-written deployment unit, the to-be-written deployment unit can perform permission information write processing according to the received permission information write request. Since the to-be-written deployment unit is determined based on the principal user identifier, the processing of the permission information write request by the to-be-written deployment unit is equivalent to the pre-approval of the principal user, so that the security of the permission information processing can be ensured. Since the above to-be-written deployment unit is not limited to the sender and the receiver of the business processing request, the selection range of the to-be-written deployment unit is more flexible, and the to-be-written deployment unit can be selected within the range allowed by laws and regulations and the range approved by the principal user, so that the information interaction performance can be considered.

[0093] With reference to Figure 3 which shows a flow 300 of one embodiment of the information write method according to the present disclosure. The information write method can be applied to a deployment unit, and includes the following steps:

[0094] In step 301, in response to receiving a permission information write request, the received permission information write request is parsed to obtain a target principal user identifier and a source deployment unit identifier.

[0095] In this embodiment, the execution subject of the information writing method can parse the received permission information writing request to obtain the to-be-written permission information and the source deployment unit identifier in a preset format of the permission information writing request in a case where the permission information writing request is received, wherein the source deployment unit identifier is used to indicate the deployment unit from which the permission information writing request originates. The to-be-written permission information can include a target permission subject user identifier. The target permission subject user identifier is used to indicate the user to which the to-be-written permission information belongs.

[0096] Step 302, determining whether the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit.

[0097] Here, the above execution subject can first obtain the source deployment unit identifier parsed in step 301, and then determine whether the permission information writing request is from the deployment unit indicated by the source deployment unit identifier, so as to determine whether the received permission information writing request is from the source deployment unit. If it is determined that yes, it indicates that the permission information writing request is indeed from the deployment unit claimed by the permission information writing request.

[0098] In addition, since each user belongs to a unique deployment unit, the deployment unit identifier of the deployment unit to which the target permission subject user belongs can be obtained first, and then it is determined whether the obtained deployment unit identifier is consistent with the target deployment unit identifier, so as to determine whether the target permission subject user belongs to the source deployment unit.

[0099] If both of the above two aspects are determined to be yes, it indicates that the target permission subject user corresponding to the permission information parsed in step 301 belongs to the deployment unit from which the permission information writing request originates, and thus the verification operation of the permission information writing request is completed.

[0100] Step 303, in response to determining yes, determining the to-be-written permission information based on the received permission information writing request, and writing the to-be-written permission information into the permission information set in the fourth current deployment unit.

[0101] Here, the above execution subject can determine yes in step 302, which indicates that the permission information writing request passes the verification, and the to-be-written permission information can be determined based on the received permission information writing request, and the to-be-written permission information is written into the permission information set in the fourth current deployment unit, so as to realize the processing of the permission information writing request.

[0102] The to-be-written permission information can be obtained based on the analysis of the permission information write request in step 301. The to-be-written permission information can include a permission subject user identifier, which is used to indicate a user who has a first control right over the permission information according to law. The first control right can include storage, authentication, and the like, and can also include a modification right over the permission information, or can not include the modification right over the permission information. Alternatively, the to-be-written permission information can further include a permission identifier, which is used to indicate a specific permission claimed by the corresponding permission subject user. Alternatively, the to-be-written permission information can further include a permission object user identifier, which is used to indicate a permission object user. The permission information including the permission object user identifier is used to represent that the permission subject user has a control right indicated by the permission identifier, for example, whether to allow the permission object user to establish a first communication relationship with the permission subject user.

[0103] Here, the fourth current deployment unit includes a deployment unit determined based on the permission subject user identifier included in the to-be-written permission information.

[0104] Through steps 301 to 303, in the case that the fourth current deployment unit receives the permission information write request, the permission subject user and the request source deployment unit are first verified based on the permission information write request, and the corresponding write operation is performed in the case that the verification is passed, so that the write operation of the permission information is realized. Moreover, since the write operation is performed in the case that the verification is passed, the permission defined by the permission information written into the fourth current deployment unit is safe, and in the subsequent process of providing the information interaction service, the corresponding permission verification can be performed based on the above-mentioned permission information, thereby improving the security of the mutual process between the deployment units.

[0105] In some optional embodiments, the writing of the to-be-written permission information into the permission information set in the fourth current deployment unit in step 303 can include:

[0106] In response to determining that the permission subject user identifier in the to-be-written permission information is the same as the permission subject user identifier in the permission information write request, the to-be-written permission information is written into the permission information set in the fourth current deployment unit.

[0107] That is, in the case that it is further determined that the permission subject user identifier in the to-be-written permission information determined in step 303 is consistent with the permission subject user identifier in the permission information write request received in step 301, the determined to-be-written permission information is written into the permission information set in the fourth current deployment unit, further improving the security of the permission information write.

[0108] Further reference is made to Figure 4As an implementation of the methods shown in the above figures, this disclosure provides an embodiment of an information writing device, which is similar to... Figure 2 Corresponding to the method embodiments shown, the device can be specifically applied to various deployment units.

[0109] like Figure 4 As shown, the information writing device 400 of this embodiment includes: a permission information generation unit 401, configured to generate at least one permission information according to a business processing request, wherein the permission information includes a permission subject user identifier, which is used to indicate a user who has a first control right over the permission information according to law; a write request generation unit 402, configured to generate a corresponding permission information write request based on the above permission information and a first current deployment unit identifier, wherein the first current deployment unit includes a deployment unit for executing the generation of the corresponding permission information write request; and a write request sending unit 403, configured to send each generated permission information write request to a corresponding deployment unit to be written, so as to instruct the corresponding deployment unit to be written to perform write processing based on the received permission information write request, wherein the permission subject user identifier in the permission information of each permission information write request is associated with the corresponding deployment unit to be written, or in other words, the corresponding deployment unit to be written is determined based on the permission subject user identifier in the permission information of each permission information write request.

[0110] In this embodiment, the specific processing of the permission information generation unit 401, the write request generation unit 402, and the write request sending unit 403 of the information writing device 400, and the resulting technical effects, can be referred to respectively. Figure 2 The relevant descriptions of steps 201, 202 and 203 in the corresponding embodiments will not be repeated here.

[0111] In some optional implementations, the permission information generation unit 401 may be further configured to generate at least one permission information corresponding to the business processing request based on the pre-stored association between the business processing request type and the permission information type.

[0112] In some optional implementations, the pre-stored service processing request type can be associated with at least one permission information type in the association relationship between service processing request type and permission information type.

[0113] In some optional implementations, the number of generated permission information entries and / or the permission subject user identifier in the generated permission information may be related to at least one of the following in the business processing request: the sender, the receiver, and the requested business processing operation.

[0114] In some optional implementations, the deployment unit to be written corresponding to the permission information write request may include at least one of the following:

[0115] The permission information is written to the deployment unit to which the permission subject user corresponding to the request belongs;

[0116] The permission information is written to the authorized private deployment unit and / or public deployment unit corresponding to the permission subject user of the request.

[0117] In some alternative embodiments, the device 400 may further include: a second determining unit ( Figure 4 (Not shown in the image), configured to, in response to detecting a permission information read request, determine whether the target deployment unit to which the permission subject user corresponding to the permission information read request belongs satisfies at least one of the following: the target deployment unit is a second current deployment unit, wherein the second current deployment unit includes the deployment unit that executed the detected permission information read request; the second current deployment unit is an authorized private deployment unit and / or a public deployment unit corresponding to the target deployment unit; permission information return unit ( Figure 4 (not shown in the image), is configured to return the processing result of the permission information corresponding to the permission information read request in the permission information set in the second current deployment unit based on the determined result being yes.

[0118] In some alternative embodiments, the above-described apparatus 400 may further include: a second parsing unit ( Figure 4 (not shown in the image), configured to, in response to receiving a permission information write request, parse the received permission information write request to obtain the target permission subject user identifier and the source deployment unit identifier; the third determining unit ( Figure 4 (Not shown in the image), configured to determine whether the received permission information write request originates from the source deployment unit and whether the target permission subject user belongs to the source deployment unit, wherein each user belongs to a unique deployment unit; the second write unit ( Figure 5 (not shown in the image), configured to, in response to a determination, determine the permission information to be written based on the received permission information write request, and write the permission information to be written into the permission information set in the third current deployment unit, wherein the permission information to be written includes a permission subject user identifier, and the third current deployment unit includes a deployment unit determined based on the permission subject user identifier.

[0119] In some optional embodiments, the writing of the to-be-written permission information into the set of permission information in the third current deployment unit can include: in response to determining that the permission subject user identifier in the to-be-written permission information is the same as the target permission subject user identifier, writing the to-be-written permission information into the set of permission information in the third current deployment unit.

[0120] It should be noted that the implementation details and technical effects of the units in the information writing apparatus provided by the embodiments of the present disclosure can refer to the descriptions of other embodiments of the present disclosure, which will not be repeated here.

[0121] Further reference Figure 3 , as an implementation of the method shown in the above figures, the present disclosure provides an embodiment of an information writing apparatus, which corresponds to the method embodiment shown in Figure 5 , and the apparatus can be specifically applied to various deployment units.

[0122] As shown in Figure 3 , the information writing apparatus 500 of the present embodiment includes: a first parsing unit 501 configured to, in response to receiving a permission information writing request, parse the received permission information writing request to obtain a target permission subject user identifier and a source deployment unit identifier; a first determination unit 502 configured to determine whether the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit, wherein each user belongs to a unique deployment unit; and a first writing unit 503 configured to, in response to a determination that the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit, determine to-be-written permission information based on the received permission information writing request, and write the to-be-written permission information into a set of permission information in a fourth current deployment unit, the to-be-written permission information including a permission subject user identifier, and the fourth current deployment unit including a deployment unit determined based on the permission subject user identifier included in the to-be-written permission information.

[0123] In the present embodiment, the specific processing of the first parsing unit 501, the first determination unit 502, and the first writing unit 503 of the information writing apparatus 500 and the technical effects brought by the same can refer to the related descriptions of step 301, step 302, and step 303 in the corresponding embodiments, which will not be repeated here. Figure 6

[0124] In some optional embodiments, the writing of the to-be-written permission information into the set of permission information in the fourth current deployment unit can include: in response to determining that the permission subject user identifier in the to-be-written permission information is the same as the permission subject user identifier in the permission information writing request, writing the to-be-written permission information into the set of permission information in the fourth current deployment unit.

[0125] ​It should be noted that the implementation details and technical effects of the units in the information writing device provided by the embodiments of the present disclosure can refer to the descriptions of other embodiments of the present disclosure, and will not be described here.

[0126] Reference is made below Figure 6 to a block diagram showing the structure of a computer system 600 suitable for implementing the information storage server of the embodiments of the present disclosure. Figure 6 The computer system 600 shown is merely one example. It should not be understood in any way as limiting the scope of functionality of the embodiments of the present disclosure.

[0127] As Figure 6 shown, the computer system 600 can include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601 that can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or programs loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the information storage server are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0128] Generally, the following devices can be connected to the I / O interface 605: input devices 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, etc.; output devices 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 608 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 609. The communication devices 609 can allow the computer system 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 2 The computer system 600 is shown with various devices, but it should be understood that not all of the shown devices are required to be implemented or present. More or fewer devices can alternatively be implemented or present.

[0129] In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, the embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication devices 609, or installed from the storage devices 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the methods of the embodiments of the present disclosure are performed.

[0130] It should be noted that the computer-readable medium in the above disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of computer-readable storage media can 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present disclosure, the computer-readable signal medium can include a data signal carried in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to a wire, a cable, an RF (radio frequency) or the like, or any suitable combination of the above.

[0131] The computer-readable medium described above can be contained in the electronic device described above; or can exist separately and not be assembled into the electronic device.

[0132] The computer-readable medium described above carries one or more programs, which, when executed by the electronic device, cause the electronic device to implement the information writing method as shown in the embodiments and optional implementation modes thereof. Figure 3 and / or ​ The information writing method shown in the embodiments and optional implementation modes thereof.

[0133] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can 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 latter scenario, the remote computer can 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 can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0134] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations 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 flow diagrams or block diagrams can represent a module, a segment, or a 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 blocks can 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

[0135] The units described in the embodiments of the present disclosure can be implemented by software, or by hardware. In some cases, the name of the unit does not constitute a limitation on the unit itself. For example, the permission information generation unit can also be described as a unit that generates at least one piece of permission information according to a service processing request.

[0136] The above description is merely that of preferred embodiments of the present disclosure and of the principles thereof. It is understood that the scope of the disclosure disclosed herein is not limited to the specific combinations of technical features described above, and also covers other technical solutions formed by any combination of the above technical features or equivalent features, without departing from the above disclosed concept. For example, the above technical features can be replaced with technical features disclosed in the present disclosure (but not limited to) having similar functions to form technical solutions.

Claims

1. An information writing method, the method being performed by a deployment unit of a plurality of deployment units in a system, comprising: generating at least one piece of authority information according to a service processing request, wherein the authority information comprises an authority subject user identifier, and the authority subject user identifier is used to indicate a user having a first control right over the authority information according to law; generating a corresponding authority information writing request based on the authority information and a first current deployment unit identifier, the first current deployment unit comprising the deployment unit used to perform the generating of the corresponding authority information writing request; sending each generated authority information writing request to a corresponding to-be-written deployment unit to instruct the corresponding to-be-written deployment unit to perform a writing process based on the received authority information writing request, wherein the corresponding to-be-written deployment unit is determined based on the authority subject user identifier in the authority information of each authority information writing request.

2. The method of claim 1, wherein, The generating of the at least one piece of authority information according to the service processing request comprises: generating at least one piece of authority information corresponding to the service processing request based on a pre-stored association relationship between a service processing request type and an authority information type.

3. The method of claim 2, wherein, One service processing request type in the pre-stored association relationship between the service processing request type and the authority information type is associated with at least one authority information type.

4. The method of claim 1, wherein, The number of generated pieces of authority information and / or the authority subject user identifier in the generated authority information is related to at least one of the following of the service processing request: a sender, a receiver, and a requested service processing operation.

5. The method of claim 4, wherein, The number of generated pieces of authority information is positively correlated with the number of data flow directions involved in the service processing request.

6. The method of claim 4, wherein the corresponding to-be-written deployment unit is determined based on the authority subject user identifier in the authority information of each authority information writing request, comprising: the corresponding to-be-written deployment unit is determined based on the authority subject user identifier in the authority information of each authority information writing request and the authority scope of the authority subject identifier.

7. The method of claim 1, wherein, The to-be-written deployment unit corresponding to the authority information writing request comprises at least one of: a deployment unit to which a corresponding authority subject user of the authority information writing request belongs; an authorized private deployment unit and / or a public deployment unit corresponding to the corresponding authority subject user of the authority information writing request.

8. The method of claim 1, wherein, The method further comprises: in response to detecting an authority information reading request, determining whether a target deployment unit to which a corresponding authority subject user of the authority information reading request belongs satisfies at least one of the following: the target deployment unit is a second current deployment unit, wherein the second current deployment unit comprises a deployment unit used to perform the detecting of the authority information reading request; and the second current deployment unit is an authorized private deployment unit and / or a public deployment unit corresponding to the target deployment unit; based on a result of the determination being yes, returning a processing result based on authority information corresponding to the authority information reading request in a set of authority information in the second current deployment unit.

9. The method of claim 1, wherein, The method further comprises: In response to receiving the permission information write request, the received permission information write request is parsed to obtain a target permission subject user identifier and a source deployment unit identifier; It is determined whether the received permission information write request is from the source deployment unit and the target permission subject user belongs to the source deployment unit; and In response to a determination that yes, the to-be-written permission information is determined based on the received permission information write request, and the to-be-written permission information is written into a permission information set in a third current deployment unit, the to-be-written permission information includes a permission subject user identifier, and the third current deployment unit includes a deployment unit determined based on the permission subject user identifier.

10. The method of claim 9, wherein, The to-be-written permission information is written into the permission information set in the third current deployment unit, including: In response to a determination that the permission subject user identifier in the to-be-written permission information is the same as the target permission subject user identifier, the to-be-written permission information is written into the permission information set in the third current deployment unit.

11. An information write method, the method being performed by a deployment unit in a plurality of deployment units in a system, comprising: In response to receiving the permission information write request, the received permission information write request is parsed to obtain a target permission subject user identifier and a source deployment unit identifier; It is determined whether the received permission information write request is from the source deployment unit and the target permission subject user belongs to the source deployment unit; and In response to a determination that yes, the to-be-written permission information is determined based on the received permission information write request, and the to-be-written permission information is written into a permission information set in a fourth current deployment unit, the to-be-written permission information includes a permission subject user identifier, and the fourth current deployment unit includes a deployment unit determined based on the permission subject user identifier included in the to-be-written permission information.

12. The method of claim 11, wherein, The to-be-written permission information is written into the permission information set in the fourth current deployment unit, including: In response to a determination that the permission subject user identifier in the to-be-written permission information is the same as the permission subject user identifier in the permission information write request, the to-be-written permission information is written into the permission information set in the fourth current deployment unit.

13. An information write apparatus, comprising: A permission information generation unit configured to generate at least one piece of permission information according to a business processing request, wherein the permission information includes a permission subject user identifier, and the permission subject user identifier is used to indicate a user having a first control right over the permission information according to law; A write request generation unit configured to generate a corresponding permission information write request based on the permission information and a first current deployment unit identifier, the first current deployment unit including a deployment unit used to perform the generation of the corresponding permission information write request; A write request sending unit configured to send each generated permission information write request to a corresponding to-be-written deployment unit to instruct the corresponding to-be-written deployment unit to perform a write process based on the received permission information write request, wherein the permission subject user identifier in the permission information of each permission information write request has an association relationship with the corresponding to-be-written deployment unit. 14.An information writing device, comprising: a first parsing unit configured to, in response to receiving a permission information writing request, parse the received permission information writing request to obtain a target permission subject user identifier and a source deployment unit identifier; a first determining unit configured to determine whether the permission information writing request is from the source deployment unit and the target permission subject user belongs to the source deployment unit; a first writing unit configured to, in response to a positive determination, determine to-be-written permission information based on the received permission information writing request, and write the to-be-written permission information into a permission information set in a fourth current deployment unit, the to-be-written permission information comprising a permission subject user identifier, the fourth current deployment unit comprising a deployment unit determined based on the permission subject user identifier comprised in the to-be-written permission information. 15.A computer-readable storage medium having stored thereon a computer program, wherein: the computer program, when executed by one or more processors, realizes the method of any one of claims 1-10 and / or claims 11-12. 16.An information storage server, comprising: one or more processors; a storage device having stored thereon one or more programs, the one or more programs, when executed by the one or more processors, cause the one or more processors to realize the method of any one of claims 1-10 and / or claims 11-12.

Images