Object sharing request verification method and device, electronic equipment and storage medium
By verifying the permission rules of the target terminal and the user, the problem of uncontrollable resource sharing scope is solved, and the efficiency and security of resource sharing are guaranteed.
Patent Information
- Application Number
- CN202211617057.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-13
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-12-13
AI Technical Summary
Existing technologies cannot control the scope of resource sharing, which makes it impossible to guarantee the efficiency and security of resource sharing.
By defining the permission rules for the target terminal and the target user, and verifying the target terminal type and user type based on the object sharing request, the verification of the object sharing request is achieved.
It improves the efficiency and security of resource sharing and reduces the complexity of the verification process.
Smart Images

Figure CN116186678B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the fields of computer technology and financial technology, and more specifically, to a method and apparatus for verifying object sharing requests, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology
[0002] With the development of computer technology, there is a need to share resources among different users.
[0003] Resources can refer to all software, hardware, and data resources within a network. Sharing can mean that users on the network can use these resources partially or entirely. Resource sharing can mean that multiple users can jointly use resources within a computer system.
[0004] In realizing the concept disclosed herein, the inventors discovered at least the following problems in the related technology: due to the inability to control the scope of resource sharing, the efficiency and security of resource sharing cannot be guaranteed. Summary of the Invention
[0005] In view of this, the present disclosure provides a method and apparatus for verifying object sharing requests, an electronic device, a computer-readable storage medium, and a computer program product.
[0006] According to one aspect of this disclosure, a method for verifying object sharing requests is provided, comprising:
[0007] In response to receiving an object sharing request initiated by a target user using a target terminal, the target terminal permission rules corresponding to the target terminal type of the target terminal are determined according to the object sharing request. The object sharing request includes target object information and object sharing type. The target terminal has the target terminal type and the target user has the target user type.
[0008] If the target object information is determined to meet the target terminal permission rules, the target user permission rules corresponding to the target user type are determined.
[0009] Based on the aforementioned target user permission rules and object sharing types, the aforementioned object sharing request is verified, and the verification result is obtained; and
[0010] If the above verification results indicate that the above object sharing request has been verified, then the execution of the above object sharing request is permitted.
[0011] According to embodiments of this disclosure, the target object information includes source address information, which is used to characterize the Internet Protocol address of the target terminal.
[0012] According to embodiments of this disclosure, the response to receiving an object sharing request initiated by a target user using a target terminal, and the determination of the target terminal permission rules corresponding to the target terminal type based on the object sharing request, includes:
[0013] Based on the preset terminal mapping relationship and the aforementioned source address information, the target terminal type corresponding to the target terminal is determined, wherein the preset terminal mapping relationship includes at least one preset terminal network segment and a preset terminal type corresponding to each of the at least one preset terminal network segment; and
[0014] Based on the preset terminal permission mapping relationship and the target terminal type, the target terminal permission rules are determined, wherein the preset terminal permission mapping relationship includes at least one preset terminal type and preset terminal permission rules corresponding to each of the at least one preset terminal type.
[0015] According to embodiments of this disclosure, the aforementioned preset terminal types include ordinary access terminals, sandbox access terminals, data analysis terminals, and data export terminals.
[0016] According to embodiments of this disclosure, determining the target terminal type corresponding to the target terminal based on the preset terminal mapping relationship and the source address information includes:
[0017] If the source address information is located in the first preset terminal network segment, it is determined that the target terminal type belongs to the ordinary access terminal.
[0018] If the source address information is located in the second preset terminal network segment, it is determined that the target terminal type belongs to the sandbox access terminal.
[0019] If the aforementioned source address information is located in the third preset terminal network segment, it is determined that the aforementioned target terminal type belongs to the aforementioned data analysis terminal; and
[0020] If the source address information is located in the fourth preset terminal network segment, the target terminal type is determined to belong to the data export terminal.
[0021] According to embodiments of this disclosure, the method further includes, before determining the target user permission rule corresponding to the target user type when it is determined that the target object information satisfies the target terminal permission rule:
[0022] The target object information is compared with the target terminal permission rules to obtain the first comparison result;
[0023] If the first comparison result indicates that the target object information and the target terminal permission rules are consistent, then it is determined that the target object information satisfies the target terminal permission rules; and
[0024] If the first comparison result indicates that the target object information and the target terminal permission rules are inconsistent, it is determined that the target object information does not meet the target terminal permission rules.
[0025] According to embodiments of this disclosure, the target object information includes a target user identifier, which is used to represent the identity number of the target user.
[0026] According to embodiments of this disclosure, when it is determined that the target object information satisfies the target terminal permission rules, determining the target user permission rules corresponding to the target user type includes:
[0027] Based on the preset user mapping relationship and the aforementioned target user identifier, a target user type corresponding to the aforementioned target user is determined, wherein the preset user mapping relationship includes at least one preset user identifier and a preset user type corresponding to each of the at least one preset user identifier; and
[0028] Based on the preset user permission mapping relationship and the target user type, the target user permission rules are determined, wherein the preset user permission mapping relationship includes at least one preset user type and the preset user permission rules corresponding to each of the at least one preset user type.
[0029] According to embodiments of this disclosure, determining the target user type corresponding to the target user based on the preset user mapping relationship and the target user identifier includes:
[0030] The target user identifier is matched against each of the at least one preset user identifier to obtain a matching result; and
[0031] If the above matching result indicates a successful match, the preset user type corresponding to the above matching result will be determined as the above target user type.
[0032] According to embodiments of this disclosure, the above-mentioned verification of the object sharing request based on the target user permission rules and the object sharing type yields the following verification results:
[0033] If the target terminal type mentioned above is a data export terminal or a regular access terminal...
[0034] The above target user type, the above object sharing type and the above target user permission rules are compared to obtain the second comparison result;
[0035] If the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are consistent, then the verification result indicating that the object sharing request has been verified is obtained; and
[0036] If the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are inconsistent, the verification result indicating that the object sharing request verification failed is obtained.
[0037] According to embodiments of this disclosure, the above-described object sharing type is used to characterize the type of object sharing operation.
[0038] According to embodiments of this disclosure, the above-mentioned object sharing operation includes at least one of the following: terminal object sharing operation and system object sharing operation, wherein the terminal object sharing operation includes a terminal object upload operation, and the system object sharing operation includes a system object upload operation, an object viewing operation, an object download operation, and an object preview operation.
[0039] According to embodiments of this disclosure, when the target terminal type is a sandbox access terminal or a data analysis terminal, the method further includes:
[0040] If the object sharing operation described above is a terminal object upload operation, then the object sharing request should be rejected; and
[0041] If the object sharing operation described above is a system object upload operation, then the object sharing request is rejected.
[0042] According to another aspect of this disclosure, an apparatus for verifying object sharing requests is provided, comprising:
[0043] The first determining module is used to respond to receiving an object sharing request initiated by a target user using a target terminal, and to determine the target terminal permission rules corresponding to the target terminal type of the target terminal based on the object sharing request. The object sharing request includes target object information and object sharing type, the target terminal corresponds to the target terminal type, and the target user corresponds to the target user type.
[0044] The second determining module is used to determine the target user permission rules corresponding to the target user type when it is determined that the above target object information meets the above target terminal permission rules.
[0045] The verification module is used to verify the object sharing request based on the target user permission rules and the object sharing type, and obtain the verification result; and
[0046] The licensing module is used to grant permission to execute the object sharing request if the above verification results indicate that the object sharing request has been verified successfully.
[0047] According to another aspect of this disclosure, an electronic device is provided, comprising:
[0048] One or more processors;
[0049] Memory, used to store one or more instructions.
[0050] When one or more of the above instructions are executed by one or more processors, the one or more processors cause the one or more processors to implement the method as described in this disclosure.
[0051] According to another aspect of this disclosure, a computer-readable storage medium is provided having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods described in this disclosure.
[0052] According to another aspect of this disclosure, a computer program product is provided, which includes computer-executable instructions that, when executed, are used to perform the methods described in this disclosure.
[0053] According to embodiments of this disclosure, since the target terminal permission rules are determined based on the object sharing request, the target terminal permission rules can correspond to the target terminal type, thereby verifying the object sharing permissions of the target terminal. Based on this, by determining that the target object information satisfies the target terminal permission rules, the target user permission rules are determined, thus the target user permission rules can correspond to the target user type, thereby verifying the object sharing permissions of the target user. By using the target terminal permission rules and the target user permission rules to verify the object sharing request, at least partially overcoming the technical problem in related technologies where the inability to control the scope of resource sharing leads to the inability to guarantee the efficiency and security of resource sharing, reducing the complexity of the object sharing request verification process, and thereby ensuring the efficiency and security of resource sharing. Attached Figure Description
[0054] The above and other objects, features, and advantages of this disclosure will become clearer from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:
[0055] Figure 1 This illustration schematically shows a system architecture for applying an object sharing request verification method according to an embodiment of the present disclosure;
[0056] Figure 2 A flowchart illustrating a method for verifying an object sharing request according to an embodiment of this disclosure is shown schematically.
[0057] Figure 3 This illustration schematically shows a flowchart of a method for determining target terminal permission rules corresponding to the target terminal type of a target terminal based on an object sharing request, according to an embodiment of the present disclosure.
[0058] Figure 4 This illustration shows a flowchart of a method for determining the target terminal type corresponding to a target terminal based on a preset terminal mapping relationship and source address information, according to an embodiment of the present disclosure.
[0059] Figure 5 This illustration schematically shows a flowchart of a method for determining a target user permission rule corresponding to a target user type when the target object information satisfies the target terminal permission rule, according to an embodiment of the present disclosure.
[0060] Figure 6 The illustration shows an example diagram of the verification process for an object sharing request according to an embodiment of the present disclosure;
[0061] Figure 7 A block diagram illustrating a verification apparatus for an object sharing request according to an embodiment of the present disclosure is shown schematically; and
[0062] Figure 8 A block diagram of an electronic device suitable for implementing an object sharing request verification method according to an embodiment of the present disclosure is shown schematically. Detailed Implementation
[0063] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.
[0064] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.
[0065] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.
[0066] When using expressions such as "at least one of A, B, and C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). Similarly, when using expressions such as "at least one of A, B, or C," the expression should generally be interpreted in accordance with the meaning commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having A alone, having B alone, having C alone, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).
[0067] In the technical solution disclosed herein, the acquisition, storage, and application of user personal information comply with the provisions of relevant laws and regulations, necessary confidentiality measures have been taken, and there is no violation of public order and good morals.
[0068] In the technical solution disclosed herein, the user's authorization or consent is obtained before acquiring or collecting the user's personal information.
[0069] Shared resources refer to the ability of other computers on the same computer network to use the computer resources of a particular computer. Shared resources are an important component of a cluster system and can include hardware, software, and data resources, which users in the cluster system can use partially or fully.
[0070] A computer network consists of several computers interconnected through a communication network. Users on each computer can use resources on other computers to share resources. For example, device sharing allows users to use external devices such as printers; data sharing allows users to access shared databases; and file sharing allows users to access file resources on shared servers.
[0071] However, in the process of realizing the present invention, the inventors have discovered at least the following problems in the related technology: due to the inability to control the scope of resource sharing, the efficiency and security of resource sharing cannot be guaranteed.
[0072] To at least partially address the technical problems existing in related technologies, this disclosure provides a method, apparatus, electronic device, and storage medium for verifying object sharing requests, which can be applied to the fields of computer technology and fintech. The object sharing request verification method includes: in response to receiving an object sharing request initiated by a target user using a target terminal; determining, based on the object sharing request, a target terminal permission rule corresponding to the target terminal type of the target terminal; the object sharing request includes target object information and an object sharing type; the target terminal corresponds to a target terminal type, and the target user corresponds to a target user type; if it is determined that the target object information satisfies the target terminal permission rule, determining a target user permission rule corresponding to the target user type; verifying the object sharing request based on the target user permission rule and the object sharing type to obtain a verification result; and if the verification result indicates that the object sharing request has passed verification, permitting the execution of the object sharing request.
[0073] It should be noted that the object sharing request verification method and apparatus provided in this disclosure can be used in the fields of computer technology and fintech, such as in the field of network technology. The object sharing request verification method and apparatus provided in this disclosure can also be used in any field other than computer technology and fintech, such as in the field of information security. The application fields of the object sharing request verification method and apparatus provided in this disclosure are not limited.
[0074] Figure 1 This illustration schematically depicts a system architecture for applying an object sharing request verification method according to embodiments of this disclosure. It should be noted that... Figure 1 The examples shown are merely examples of system architectures that can be applied to the embodiments of this disclosure, in order to help those skilled in the art understand the technical content of this disclosure, but do not mean that the embodiments of this disclosure cannot be used in other devices, systems, environments or scenarios.
[0075] like Figure 1 As shown, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.
[0076] Users can interact with server 105 via network 104 using at least one of the first terminal device 101, second terminal device 102, and third terminal device 103 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, second terminal device 102, and third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).
[0077] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with displays and support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.
[0078] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.
[0079] It should be noted that the object sharing request verification method provided in this embodiment can generally be executed by server 105. Correspondingly, the object sharing request verification device provided in this embodiment can generally be located in server 105. The object sharing request verification method provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105. Correspondingly, the object sharing request verification device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or server 105.
[0080] Alternatively, the object sharing request verification method provided in this embodiment of the present disclosure can also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Correspondingly, the object sharing request verification device provided in this embodiment of the present disclosure can also be located in the first terminal device 101, the second terminal device 102, or the third terminal device 103, or in other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103.
[0081] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.
[0082] It should be noted that the sequence numbers of the operations in the following methods are for descriptive purposes only and should not be considered as indicating the execution order of the operations. Unless explicitly stated otherwise, the method does not need to be executed in the exact order shown.
[0083] Figure 2 A flowchart illustrating a method for verifying an object sharing request according to an embodiment of this disclosure is shown schematically.
[0084] like Figure 2 As shown, the verification method 200 for the object sharing request may include operations S210 to S240.
[0085] In operation S210, in response to receiving an object sharing request initiated by a target user using a target terminal, the target terminal permission rules corresponding to the target terminal type are determined based on the object sharing request. The object sharing request includes target object information and object sharing type; the target terminal has a corresponding target terminal type, and the target user has a corresponding target user type.
[0086] In operation S220, if the target object information is determined to meet the target terminal permission rules, the target user permission rules corresponding to the target user type are determined.
[0087] In operation S230, the object sharing request is verified according to the target user permission rules and the object sharing type, and the verification result is obtained.
[0088] In operation S240, if the verification result indicates that the object sharing request has been verified as successful, the execution of the object sharing request is permitted.
[0089] According to embodiments of this disclosure, code for generating an object sharing request can be pre-written into a script. In response to detecting an object sharing operation performed by a target user using a target terminal, the target terminal can run the script, generate an object sharing request message, and send the object sharing request message to the server so that the server can verify the object sharing request corresponding to the object sharing operation based on the object sharing request message.
[0090] According to embodiments of this disclosure, object sharing operations may include at least one of the following: terminal object sharing operations and system object sharing operations. A terminal object sharing operation may refer to a user operation performed on a target object between terminal A and terminal B. A system object sharing operation may refer to one of the following: a user operation performed on a target object between terminal C and system D, or a user operation performed on a target object between system E and system F.
[0091] According to embodiments of this disclosure, the target object can refer to an electronic file to be shared. The target object may include one of the following: text files, image files, graphic files, video files, audio files, hypermedia link files, program files, and data files. User operations may include at least one of the following: upload operation, view operation, download operation, and preview operation.
[0092] According to embodiments of this disclosure, an object sharing request may include target object information and an object sharing type. The target object information may include source address information and a target user identifier. The source address information may be used to characterize the target terminal's Internet Protocol Address (IP). The target user identifier may be used to characterize the target user's Identity Document (ID).
[0093] According to embodiments of this disclosure, a target terminal may correspond to a target terminal type. The target terminal type can be determined based on source address information. The target terminal type may include one of the following: a normal access terminal, a sandbox access terminal, a data analysis terminal, and a data export terminal. A target user may correspond to a target user type. The target user type may include one of the following: a first user type, a second user type, and a third user type. The target user type can be determined based on a target user identifier.
[0094] According to embodiments of this disclosure, after receiving an object sharing request, a target terminal permission rule corresponding to the target terminal type can be determined based on the object sharing request. For example, the target terminal type can be determined based on the object sharing request. Based on the target terminal type, the target terminal permission rule is determined. The target terminal permission rule may include a mapping rule between the target terminal type, the object sharing type, and the object sharing permissions. After determining the target terminal permission rule, the object sharing request can be verified according to the target terminal permission rule to determine whether the target object information satisfies the target terminal permission rule.
[0095] According to embodiments of this disclosure, when it is determined that the target object information satisfies the target terminal permission rules, target user permission rules corresponding to the target user type can be determined based on the object sharing request. For example, the target user type can be determined based on the object sharing request. Target user permission rules are then determined based on the target user type. The target user permission rules may include mapping rules between the target user type, object sharing type, and object sharing permissions. After determining the target user permission rules, the object sharing request can be verified based on the target user permission rules and the object sharing type to obtain a verification result. The verification result can be used to characterize whether the object sharing request has passed verification.
[0096] According to embodiments of this disclosure, if the verification result indicates that the object sharing request has passed verification, the execution of the object sharing request can be permitted. If the verification result indicates that the object sharing request has failed verification, the execution of the object sharing request can be prohibited.
[0097] According to embodiments of this disclosure, since the target terminal permission rules are determined based on the object sharing request, the target terminal permission rules can correspond to the target terminal type, thereby verifying the object sharing permissions of the target terminal. Based on this, by determining that the target object information satisfies the target terminal permission rules, the target user permission rules are determined, thus the target user permission rules can correspond to the target user type, thereby verifying the object sharing permissions of the target user. By using the target terminal permission rules and the target user permission rules to verify the object sharing request, at least partially overcoming the technical problem in related technologies where the inability to control the scope of resource sharing leads to the inability to guarantee the efficiency and security of resource sharing, reducing the complexity of the object sharing request verification process, and thereby ensuring the efficiency and security of resource sharing.
[0098] The following is for reference. Figures 3-6 The verification method 200 for object sharing requests according to an embodiment of the present invention will be further described.
[0099] According to embodiments of this disclosure, the object sharing type is used to characterize the type of object sharing operation. The object sharing operation includes at least one of the following: a terminal object sharing operation and a system object sharing operation. The terminal object sharing operation includes a terminal object upload operation, and the system object sharing operation includes a system object upload operation, an object viewing operation, an object download operation, and an object preview operation.
[0100] According to embodiments of this disclosure, a terminal object upload operation may refer to a user operation that transmits a target object from a local computer to a remote computer.
[0101] According to embodiments of this disclosure, a system object upload operation can refer to a user operation that transfers a target object from a local computer to a system server. An object viewing operation can refer to a user operation that uses a local computer to request permission from the system server to view a target object. An object download operation can refer to a user operation that copies a target object from the system server to a local computer. An object preview operation can refer to a user operation that uses a local computer to request permission from the system server to view brief information about a target object.
[0102] According to embodiments of this disclosure, operation S210 may include the following operations.
[0103] Based on the preset terminal mapping relationship and source address information, determine the target terminal type corresponding to the target terminal. The preset terminal mapping relationship includes at least one preset terminal network segment and a preset terminal type corresponding to each of the at least one preset terminal network segment. Based on the preset terminal permission mapping relationship and the target terminal type, determine the target terminal permission rules. The preset terminal permission mapping relationship includes at least one preset terminal type and a preset terminal permission rule corresponding to each of the at least one preset terminal type.
[0104] According to embodiments of this disclosure, target object information may include source address information, which may be used to characterize the Internet Protocol address of the target terminal.
[0105] According to embodiments of this disclosure, a preset terminal mapping relationship can be determined based on at least one preset terminal network segment and a preset terminal type corresponding to each of the at least one preset terminal network segment. For example, at least one preset terminal network segment may include preset terminal network segment 1, preset terminal network segment 2, ..., preset terminal network segment n, ..., preset terminal network segment N. N may be an integer greater than or equal to 1, and n∈{1, 2, ..., (N-1), N}. The preset terminal type corresponding to each of the at least one preset terminal network segment may include preset terminal type 1, preset terminal type 2, ..., preset terminal type n, ..., preset terminal type N. In this case, the preset terminal mapping relationship may include the mapping relationship between preset terminal network segment 1 and preset terminal type 1, the mapping relationship between preset terminal network segment 2 and preset terminal type 2, ..., the mapping relationship between preset terminal network segment n and preset terminal type n, ..., the mapping relationship between preset terminal network segment N and preset terminal type N.
[0106] According to embodiments of this disclosure, a preset terminal permission mapping relationship can be determined based on at least one preset terminal type and preset terminal permission rules corresponding to each of the at least one preset terminal type. For example, at least one preset terminal type may include preset terminal type 1, preset terminal type 2, ..., preset terminal type n, ..., preset terminal type N. The preset terminal permission rules corresponding to each of the at least one preset terminal type may include preset terminal permission rule 1, preset terminal permission rule 2, ..., preset terminal permission rule n, ..., preset terminal permission rule N. In this case, the preset terminal permission mapping relationship may include the mapping relationship between preset terminal type 1 and preset terminal permission rule 1, the mapping relationship between preset terminal type 2 and preset terminal permission rule 2, ..., the mapping relationship between preset terminal type n and preset terminal permission rule n, ..., the mapping relationship between preset terminal type N and preset terminal permission rule N.
[0107] According to embodiments of this disclosure, after determining the preset terminal mapping relationship and the preset terminal permission mapping relationship, the preset terminal mapping relationship and the preset terminal permission mapping relationship can be stored in a data source. In response to receiving an object sharing request, the preset terminal mapping relationship and the preset terminal permission mapping relationship can be retrieved from the data source. The data source may include at least one of the following: a local database, a cloud database, and network resources. For example, a data interface can be invoked. The preset terminal mapping relationship and the preset terminal permission mapping relationship are retrieved from the data source using the data interface.
[0108] According to embodiments of this disclosure, after obtaining the preset terminal mapping relationship, the source address information in the target object information of the object sharing request can be matched with the preset terminal network segment 1, preset terminal network segment 2, ..., preset terminal network segment n, ..., preset terminal network segment N in the preset terminal mapping relationship to determine the matching terminal network segment. Based on the preset terminal mapping relationship, the matching terminal type corresponding to the matching terminal network segment is determined. Based on the matching terminal type, the target terminal type is determined.
[0109] According to embodiments of this disclosure, after determining the target terminal type, the target terminal type can be matched with at least one preset terminal type in a preset terminal permission mapping relationship to determine the matching terminal type. Based on the preset terminal permission mapping relationship, a matching terminal permission rule corresponding to the matching terminal type is determined. Based on the matching terminal permission rule, the target terminal permission rule is determined. The target terminal permission rule can be used to characterize whether the target terminal has permissions corresponding to object-shared operations.
[0110] According to embodiments of this disclosure, since the target terminal type is determined based on a preset terminal mapping relationship and source address information, the target terminal type can be automatically determined based on the source address information in the target object information, thereby improving the efficiency and accuracy of target terminal type determination. Furthermore, since the target terminal permission rules are determined based on the target terminal type, the target terminal permission rules can be automatically determined based on the target terminal type, thereby improving the efficiency and accuracy of target terminal permission rule determination, and thus ensuring the efficiency of the object sharing request verification process.
[0111] Figure 3 The flowchart illustrates a method for determining target terminal permission rules corresponding to the target terminal type of a target terminal based on an object sharing request, according to an embodiment of the present disclosure.
[0112] like Figure 3 As shown, in step 300, a preset terminal mapping relationship 303 can be determined based on at least one preset terminal network segment 301 and a preset terminal type 302 corresponding to each of the at least one preset terminal network segment 301. A preset terminal permission mapping relationship 305 can be determined based on at least one preset terminal type 302 and a preset terminal permission rule 304 corresponding to each of the at least one preset terminal type 302.
[0113] In response to receiving an object sharing request 306, the target terminal type 307 can be determined based on the preset terminal mapping relationship 303 and the source address information 3061 in the object sharing request 306. The target terminal permission rule 308 can be determined based on the preset terminal permission mapping relationship 305 and the target terminal type 307.
[0114] According to embodiments of this disclosure, determining the target terminal type corresponding to the target terminal based on a preset terminal mapping relationship and source address information may include the following operations.
[0115] If the source address information is located in the first preset terminal network segment, the target terminal type is determined to be a normal access terminal. If the source address information is located in the second preset terminal network segment, the target terminal type is determined to be a sandbox access terminal. If the source address information is located in the third preset terminal network segment, the target terminal type is determined to be a data analysis terminal. If the source address information is located in the fourth preset terminal network segment, the target terminal type is determined to be a data export terminal.
[0116] According to embodiments of this disclosure, the preset terminal type may include a normal access terminal, a sandbox access terminal, a data analysis terminal, and a data export terminal.
[0117] According to embodiments of this disclosure, terminal network segments can be represented using WXYZ. W, X, Y, Z ∈ [0, 255]. The first preset terminal network segment, the second preset terminal network segment, the third preset terminal network segment, and the fourth preset terminal network segment can be set according to actual service requirements, and are not limited herein.
[0118] For example, the first preset terminal network segment can be set to W∈[0,10], X∈[0,10], ∈[0,10], Z∈[0,255], that is, the first preset terminal network segment can include Internet Protocol addresses in the range of 0.0.0.0 to 10.10.10.255. The second preset terminal network segment can be set to W∈[10,20], X∈[10,20], ∈[10,20], Z∈[0,255], that is, the second preset terminal network segment can include Internet Protocol addresses in the range of 10.10.10.0 to 20.20.20.255. The third preset terminal network segment can be set to W∈[20,30], X∈[20,30], ∈[20,30], Z∈[0,255], that is, the third preset terminal network segment can include Internet Protocol addresses in the range of 20.20.20.0 to 30.30.30.255. The fourth preset terminal network segment can be set to W∈[30,40], X∈[30,40], ∈[30,40], Z∈[0,255], that is, the fourth preset terminal network segment can include Internet Protocol addresses in the range of 30.30.30.0 to 40.40.40.255.
[0119] According to embodiments of this disclosure, since the target terminal type is determined based on a preset terminal mapping relationship and source address information, by dividing different preset terminal network segments, the target terminal type can be automatically determined based on the relationship between the source address information and different preset terminal network segments, thereby improving the efficiency and accuracy of target terminal type determination.
[0120] According to embodiments of this disclosure, when the target terminal type is a sandbox access terminal or a data analysis terminal, the object sharing request verification method 200 may further include the following operations.
[0121] If the object sharing operation is a terminal object upload operation, reject the object sharing request. If the object sharing operation is a system object upload operation, reject the object sharing request.
[0122] According to embodiments of this disclosure, after obtaining the target terminal type, if the target terminal type belongs to a sandbox access terminal or a data analysis terminal, the object sharing request can be rejected for terminal object upload operations and system object upload operations.
[0123] According to embodiments of this disclosure, when the target terminal type is a sandbox access terminal or a data analysis terminal, object sharing requests that are terminal object upload operations or system object upload operations can be rejected, thereby avoiding the upload of sensitive data and ensuring the security of resource sharing.
[0124] Figure 4 The flowchart illustrates a method for determining the target terminal type corresponding to a target terminal based on a preset terminal mapping relationship and source address information, according to an embodiment of the present disclosure.
[0125] like Figure 4 As shown, in step 400, in response to receiving object sharing request 401, the source address information 4011 in object sharing request 401 can be obtained. After obtaining the source address information 4011, operation S410 can be performed.
[0126] In operation S410, if the source address information is located in the first preset terminal network segment i, then the target terminal type is determined to be a normal access terminal 402; otherwise, operation S420 is executed.
[0127] In operation S420, is the source address information located in the second preset terminal network segment? If yes, then determine that the target terminal type belongs to sandbox access terminal 403; otherwise, execute operation S430.
[0128] In operation S430, is the source address information located in the third preset terminal network segment? If yes, then determine that the target terminal type belongs to data analysis terminal 404; otherwise, execute operation S440.
[0129] During operation S430, is the source address information located in the fourth preset terminal network segment? If yes, then determine that the target terminal type belongs to data export terminal 405; otherwise, end the target type determination operation.
[0130] According to embodiments of this disclosure, operation S220 may include the following operations.
[0131] Based on the preset user mapping relationship and the target user identifier, determine the target user type corresponding to the target user. The preset user mapping relationship includes at least one preset user identifier and a preset user type corresponding to each of the at least one preset user identifier. Based on the preset user permission mapping relationship and the target user type, determine the target user permission rules. The preset user permission mapping relationship includes at least one preset user type and a preset user permission rule corresponding to each of the at least one preset user type.
[0132] According to embodiments of this disclosure, the target object information may include a target user identifier, which may be used to represent the identity number of the target user.
[0133] According to embodiments of this disclosure, a preset user mapping relationship can be determined based on at least one preset user identifier and a preset user type corresponding to each of the at least one preset user identifier. For example, at least one preset user identifier may include preset user identifier 1, preset user identifier 2, ..., preset user identifier m, ..., preset user identifier M. M may be an integer greater than or equal to 1, and m ∈ {1, 2, ..., (M-1), M}. The preset user type corresponding to each of the at least one preset user identifier may include preset user type 1, preset user type 2, ..., preset user type m, ..., preset user type M. In this case, the preset user mapping relationship may include the mapping relationship between preset user identifier 1 and preset user type 1, the mapping relationship between preset user identifier 2 and preset user type 2, ..., the mapping relationship between preset user identifier m and preset user type m, ..., the mapping relationship between preset user identifier M and preset user type M.
[0134] According to embodiments of this disclosure, a preset user permission mapping relationship can be determined based on at least one preset user type and preset user permission rules corresponding to each of the at least one preset user type. For example, the at least one preset user type may include preset user type 1, preset user type 2, ..., preset user type m, ..., preset user type M. The preset user permission rules corresponding to each of the at least one preset user type may include preset user permission rule 1, preset user permission rule 2, ..., preset user permission rule m, ..., preset user permission rule M. In this case, the preset user permission mapping relationship may include the mapping relationship between preset user type 1 and preset user permission rule 1, the mapping relationship between preset user type 2 and preset user permission rule 2, ..., the mapping relationship between preset user type m and preset user permission rule m, ..., the mapping relationship between preset user type M and preset user permission rule M.
[0135] According to embodiments of this disclosure, the preset user type may include at least one of the following: audit department contact person and external auditor. External auditor may include at least one of the following: external audit administrator and external audit team member. An audit department contact person may refer to a contact person who cooperates with external audits and provides shared information to external auditors. An external audit administrator may refer to a manager of a specific external audit project. An external audit team member may refer to a participant in a specific external audit project.
[0136] According to embodiments of this disclosure, after determining the preset user mapping relationship and the preset user permission mapping relationship, the preset user mapping relationship and the preset user permission mapping relationship can be stored in a data source. In response to receiving an object sharing request, the preset user mapping relationship and the preset user permission mapping relationship can be retrieved from the data source. The data source may include at least one of the following: a local database, a cloud database, and network resources. For example, a data interface can be invoked. The preset user mapping relationship and the preset user permission mapping relationship are retrieved from the data source using the data interface.
[0137] According to embodiments of this disclosure, since the target user type is determined based on a preset user mapping relationship and a target user identifier, the target user type can be automatically determined based on the target user identifier in the target object information, thereby improving the efficiency and accuracy of target user type determination. Furthermore, since the target user permission rules are determined based on the target user type, the target user permission rules can be automatically determined based on the target user type, thereby improving the efficiency and accuracy of target user permission rule determination, and ultimately ensuring the efficiency of the object sharing request verification process.
[0138] According to embodiments of this disclosure, determining the target user type corresponding to the target user based on a preset user mapping relationship and a target user identifier may include the following operations.
[0139] The target user identifier is matched against each of at least one preset user identifier to obtain a matching result. If the matching result indicates a successful match, the preset user type corresponding to the matching result is determined as the target user type.
[0140] According to embodiments of this disclosure, after obtaining the preset user mapping relationship, the target user identifier in the target object information of the object sharing request can be matched with the preset user identifiers 2, ..., m, ..., M automatically preset through the preset user mapping relationship to determine the matching user identifier. Based on the preset user mapping relationship, the matching user type corresponding to the matching user identifier is determined. Based on the matching user type, the target user type is determined.
[0141] According to embodiments of this disclosure, after determining the target user type, the target user type can be matched with at least one preset user type in a preset user permission mapping relationship to determine the matching user type. Based on the preset user permission mapping relationship, matching user permission rules corresponding to the matching user type are determined. Based on the matching user permission rules, target user permission rules are determined. Target user permission rules can be used to characterize whether the target user has permissions corresponding to object-shared operations.
[0142] According to embodiments of this disclosure, a matching result is obtained by matching the target user identifier with each of at least one preset user identifier. Since the target user type is determined based on the preset user type corresponding to the matching result when the matching result indicates a successful match, the target user type can be automatically determined, thereby improving the efficiency and accuracy of target user type determination.
[0143] Figure 5 The flowchart illustrates a method for determining a target user permission rule corresponding to a target user type when the target object information satisfies the target terminal permission rule, according to an embodiment of the present disclosure.
[0144] like Figure 5 As shown, in step 500, a preset user mapping relationship 503 can be determined based on at least one preset user identifier 501 and a preset user type 502 corresponding to each of the at least one preset user identifier 501. A preset user permission mapping relationship 505 can be determined based on at least one preset user type 502 and a preset user permission rule 504 corresponding to each of the at least one preset user type 502.
[0145] In response to receiving an object sharing request 506, the target user type 507 can be determined based on the preset user mapping relationship 503 and the target user identifier 5061 in the object sharing request 506. The target user permission rule 508 can be determined based on the preset user permission mapping relationship 505 and the target user type 507.
[0146] According to embodiments of this disclosure, the object sharing request verification method 200 may further include the following operations.
[0147] The target object information is compared with the target terminal permission rules to obtain a first comparison result. If the first comparison result indicates that the target object information and the target terminal permission rules are consistent, the target object information is determined to satisfy the target terminal permission rules. If the first comparison result indicates that the target object information and the target terminal permission rules are inconsistent, the target object information is determined to not satisfy the target terminal permission rules.
[0148] According to embodiments of this disclosure, the first comparison result can be used to characterize whether the target object information is consistent with the target terminal permission rules.
[0149] According to embodiments of this disclosure, the target terminal permission rules may include at least one of the following: ordinary access terminal permission rules, sandbox access terminal permission rules, data analysis terminal permission rules, and data export terminal permission rules. Ordinary access terminal permission rules may include at least one of the following: prohibiting terminal object upload operations, allowing system object upload operations, allowing object viewing operations, allowing object download operations, and allowing object preview operations. Sandbox access terminal permission rules may include at least one of the following: prohibiting terminal object upload operations, prohibiting system object upload operations, prohibiting object viewing operations, prohibiting object download operations, and prohibiting object preview operations. Data analysis terminal permission rules may include at least one of the following: prohibiting terminal object upload operations, prohibiting system object upload operations, allowing object viewing operations, allowing object download operations, and allowing object preview operations.
[0150] According to embodiments of this disclosure, since the first comparison result is obtained by comparing the target object information with the target terminal permission rules, if the first comparison result indicates that the target object information and the target terminal permission rules are consistent, it is determined that the target object information satisfies the target terminal permission rules. This reduces the complexity of the terminal permission verification process, thereby reducing the complexity of the object sharing request verification process and ensuring the security of resource sharing.
[0151] According to embodiments of this disclosure, when the target terminal type is a data export terminal or a normal access terminal, operation S230 may include the following operations.
[0152] The target user type, object sharing type, and target user permission rules are compared to obtain a second comparison result. If the second comparison result indicates that the target user type, object sharing type, and target user permission rules are consistent, a verification result indicating that the object sharing request verification has passed is obtained. If the second comparison result indicates that the target user type, object sharing type, and target user permission rules are inconsistent, a verification result indicating that the object sharing request verification has failed is obtained.
[0153] According to embodiments of this disclosure, the second comparison result can be used to characterize whether the target user type, object sharing type, and target user permission rules are consistent.
[0154] According to embodiments of this disclosure, the target user permission rules may include at least one of the following: ordinary access terminal user permission rules, sandbox access terminal user permission rules, data analysis terminal user permission rules, and data export terminal user permission rules. The data export terminal user permission rules may include at least one of the following: audit department contact person permission rules, external audit administrator permission rules, and external audit team member permission rules. The audit department contact person permission rules may include at least one of the following: allowing terminal object upload operations and allowing system object upload operations. The external audit administrator permission rules may include at least one of the following: allowing terminal object upload operations and allowing system object upload operations. The external audit team member permission rules may include at least one of the following: prohibiting terminal object upload operations and prohibiting system object upload operations.
[0155] According to embodiments of this disclosure, since the second comparison result is obtained by comparing the target user type, the object sharing type, and the target user permission rules, and the verification result is obtained based on the second comparison result, if the verification result indicates that the object sharing request has been verified, the execution of the object sharing request is permitted. This reduces the complexity of the user permission verification process, thereby reducing the complexity of the object sharing request verification process and ensuring the security of resource sharing.
[0156] Figure 6 The illustration shows an example diagram of the verification process for an object sharing request according to an embodiment of the present disclosure.
[0157] like Figure 6 As shown in 600, in response to receiving an object sharing request, the target object information 601 and the object sharing type 611 in the object sharing request can be obtained. The target object information 601 may include source address information 6011 and target user identifier 6012.
[0158] After obtaining the source address information 6011, the target terminal type 603 can be determined based on the preset terminal mapping relationship 602 and the source address information 6011. After determining the target terminal type 603, the target terminal permission rules 605 can be determined based on the preset terminal permission mapping relationship 604 and the target terminal type 603.
[0159] After determining the target terminal permission rule 605, the target object information 601 can be compared with the target terminal permission rule 605 to obtain a first comparison result 606. If the first comparison result 606 indicates that the target object information 601 and the target terminal permission rule 605 are consistent, it can be determined that the target object information 601 satisfies the target terminal permission rule 605.
[0160] If the target object information 601 satisfies the target terminal permission rule 605, the target user type 608 can be determined based on the preset user mapping relationship 607 and the target user identifier 6012. After determining the target user type 608, the target user permission rule 610 can be determined based on the preset user permission mapping relationship 609 and the target user type 608.
[0161] After determining the target user permission rule 610, if the target terminal type 603 belongs to a data export terminal or a normal access terminal, the target user type 608, the object sharing type 611 can be compared with the target user permission rule 610 to obtain a second comparison result 612.
[0162] If the second comparison result 612 indicates that the target user type 608, object sharing type 611, and target user permission rule 610 are consistent, a verification result 613 indicating that the object sharing request has passed verification is obtained. If the verification result 613 indicates that the object sharing request has passed verification, the execution of the object sharing request is permitted.
[0163] The above are merely exemplary embodiments, but are not limited thereto. Other object sharing request verification methods known in the art may also be included, as long as they can ensure the efficiency and security of resource sharing.
[0164] Figure 7 A block diagram of an object sharing request verification apparatus according to an embodiment of the present disclosure is shown schematically.
[0165] like Figure 7 As shown, the verification device 700 for object sharing requests may include a first determining module 710, a second determining module 720, a verification module 730, and a licensing module 740.
[0166] The first determining module 710 is used to respond to receiving an object sharing request initiated by a target user using a target terminal, and to determine the target terminal permission rules corresponding to the target terminal type based on the object sharing request. The object sharing request includes target object information and object sharing type; the target terminal corresponds to a target terminal type, and the target user corresponds to a target user type.
[0167] The second determining module 720 is used to determine the target user permission rules corresponding to the target user type when the target object information is determined to meet the target terminal permission rules.
[0168] The verification module 730 is used to verify the object sharing request based on the target user's permission rules and the object sharing type, and obtain the verification result.
[0169] The licensing module 740 is used to license the execution of the object sharing request if the verification result indicates that the object sharing request has passed verification.
[0170] According to embodiments of this disclosure, the target object information includes source address information, which is used to characterize the Internet Protocol address of the target terminal.
[0171] According to embodiments of the present disclosure, the first determining module 710 may include a first determining unit and a second determining unit.
[0172] The first determining unit is used to determine the target terminal type corresponding to the target terminal based on a preset terminal mapping relationship and source address information. The preset terminal mapping relationship includes at least one preset terminal network segment and a preset terminal type corresponding to each of the at least one preset terminal network segment.
[0173] The second determining unit is used to determine the target terminal permission rules based on the preset terminal permission mapping relationship and the target terminal type. The preset terminal permission mapping relationship includes at least one preset terminal type and preset terminal permission rules corresponding to each of the at least one preset terminal type.
[0174] According to embodiments of this disclosure, the preset terminal types include ordinary access terminals, sandbox access terminals, data analysis terminals, and data export terminals.
[0175] According to embodiments of this disclosure, the first determining unit may include a first determining subunit, a second determining subunit, a third determining subunit, and a fourth determining subunit.
[0176] The first determining subunit is used to determine that the target terminal type belongs to a normal access terminal when the source address information is located in the first preset terminal network segment.
[0177] The second determining subunit is used to determine that the target terminal type belongs to the sandbox access terminal when the source address information is located in the second preset terminal network segment.
[0178] The third determining subunit is used to determine that the target terminal type belongs to a data analysis terminal when the source address information is located in the third preset terminal network segment.
[0179] The fourth determining subunit is used to determine that the target terminal type belongs to the data export terminal when the source address information is located in the fourth preset terminal network segment.
[0180] According to embodiments of this disclosure, the verification device 700 for object sharing requests may further include a comparison module, a third determination module, and a fourth determination module.
[0181] The comparison module is used to compare the target object information with the target terminal permission rules to obtain the first comparison result.
[0182] The third determining module is used to determine whether the target object information satisfies the target terminal permission rules when the first comparison result indicates that the target object information and the target terminal permission rules are consistent.
[0183] The fourth determination module is used to determine that the target object information does not meet the target terminal permission rules when the first comparison result indicates that the target object information and the target terminal permission rules are inconsistent.
[0184] According to embodiments of this disclosure, the target object information includes a target user identifier, which is used to represent the identity identification number of the target user.
[0185] According to embodiments of this disclosure, the second determining module 720 may include a third determining unit and a fourth determining unit.
[0186] The third determining unit is used to determine the target user type corresponding to the target user based on the preset user mapping relationship and the target user identifier. The preset user mapping relationship includes at least one preset user identifier and a preset user type corresponding to each of the at least one preset user identifier.
[0187] The fourth determining unit is used to determine the target user permission rules based on the preset user permission mapping relationship and the target user type. The preset user permission mapping relationship includes at least one preset user type and preset user permission rules corresponding to each of the at least one preset user type.
[0188] According to embodiments of this disclosure, the third determining unit may include a matching subunit and a fifth determining subunit.
[0189] The matching subunit is used to match the target user identifier with each of the at least one preset user identifier to obtain the matching result.
[0190] The fifth determining subunit is used to determine the preset user type corresponding to the matching result as the target user type when the matching result indicates a successful match.
[0191] According to embodiments of this disclosure, when the target terminal type is a data export terminal or a normal access terminal, the verification module 730 may include a comparison unit, a first obtaining unit, and a second obtaining unit.
[0192] The comparison unit is used to compare the target user type, object sharing type, and target user permission rules to obtain a second comparison result.
[0193] The first obtaining unit is used to obtain a verification result indicating that the object sharing request has been verified, provided that the second comparison result represents the target user type, the object sharing type, and the target user permission rules are consistent.
[0194] The second obtaining unit is used to obtain a verification result indicating that the object sharing request verification failed when the second comparison result indicates that the target user type, object sharing type and target user permission rules are inconsistent.
[0195] According to embodiments of this disclosure, the object sharing type is used to characterize the type of object sharing operation. The object sharing operation includes at least one of the following: a terminal object sharing operation and a system object sharing operation. The terminal object sharing operation includes a terminal object upload operation, and the system object sharing operation includes a system object upload operation, an object viewing operation, an object download operation, and an object preview operation.
[0196] According to embodiments of this disclosure, when the target terminal type is a sandbox access terminal or a data analysis terminal, the object sharing request verification device 700 may further include a first rejection module and a second rejection module.
[0197] The first rejection module is used to reject object sharing requests when the object sharing operation is a terminal object upload operation.
[0198] The second rejection module is used to reject object sharing requests when the object sharing operation is a system object upload operation.
[0199] Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure, or at least part of the functions of any one or more of them, can be implemented in one module. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be implemented by dividing them into multiple modules. Any one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as hardware circuitry, such as Field Programmable Gate Arrays (FPGAs), Programmable Logic Arrays (PLAs), Systems-on-Chip, Systems-on-Substrate, Systems-on-Package, Application-Specific Integrated Circuits (ASICs), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, one or more of the modules, submodules, units, and subunits according to embodiments of the present disclosure can be at least partially implemented as computer program modules, which, when run, can perform corresponding functions.
[0200] For example, any plurality of the first determining module 710, the second determining module 720, the verification module 730, and the licensing module 740 may be combined into one module / unit / subunit, or any one of these modules / units / subunits may be split into multiple modules / units / subunits. Alternatively, at least part of the functionality of one or more of these modules / units / subunits may be combined with at least part of the functionality of other modules / units / subunits and implemented in one module / unit / subunit. According to embodiments of this disclosure, at least one of the first determining module 710, the second determining module 720, the verification module 730, and the licensing module 740 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging the circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the first determining module 710, the second determining module 720, the verification module 730, and the licensing module 740 may be implemented at least partially as a computer program module that can perform corresponding functions when the computer program module is run.
[0201] It should be noted that the verification device part of the object sharing request in the embodiments of this disclosure corresponds to the verification method part of the object sharing request in the embodiments of this disclosure. For a detailed description of the verification device part of the object sharing request, please refer to the verification method part of the object sharing request, which will not be repeated here.
[0202] Figure 8 A block diagram of an electronic device suitable for implementing an object sharing request verification method according to an embodiment of the present disclosure is shown schematically. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.
[0203] like Figure 8As shown, a computer electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage portion 809 into a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.
[0204] RAM 803 stores various programs and data required for the operation of electronic device 800. Processor 801, ROM 802, and RAM 803 are interconnected via bus 804. Processor 801 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 802 and / or RAM 803. It should be noted that the programs may also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.
[0205] According to embodiments of this disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to a bus 804. The electronic device 800 may also include one or more of the following components connected to the I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 810 as needed so that computer programs read from it can be installed into the storage section 808 as needed.
[0206] According to embodiments of this disclosure, the method flow according to embodiments of this disclosure can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by processor 801, it performs the functions defined in the system of embodiments of this disclosure. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.
[0207] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.
[0208] According to embodiments of this disclosure, the computer-readable storage medium can be a non-volatile computer-readable storage medium. Examples include, but are not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
[0209] For example, according to embodiments of this disclosure, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.
[0210] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods provided in the embodiments of this disclosure. When the computer program product is run on an electronic device, the program code is used to enable the electronic device to implement the object sharing request verification method provided in the embodiments of this disclosure.
[0211] When the computer program is executed by the processor 801, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.
[0212] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and may be downloaded and installed via the communication section 809, and / or installed from a removable medium 811. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.
[0213] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, languages such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0214] The flowcharts and block diagrams in the accompanying drawings 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 a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions. Those skilled in the art will understand that the features recited in the various embodiments and / or claims of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not expressly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure may be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.
[0215] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.
Claims
1. A method for verifying object sharing requests, comprising: In response to receiving an object sharing request initiated by a target user using a target terminal, the system determines target terminal permission rules corresponding to the target terminal type of the target terminal based on the object sharing request. The object sharing request includes target object information and an object sharing type. The target object information includes source address information. The target terminal corresponds to a target terminal type, which is determined based on the source address information. The target terminal type includes ordinary access terminal, sandbox access terminal, data analysis terminal, and data export terminal. The object sharing type characterizes the type of object sharing operation, and the target user corresponds to a target user type. If the target object information is determined to satisfy the target terminal permission rules, then the target user permission rules corresponding to the target user type are determined. If the target terminal type belongs to the data export terminal or the ordinary access terminal, the target user type, the object sharing type, and the target user permission rules are compared to obtain a second comparison result; if the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are consistent, a verification result indicating that the object sharing request verification has passed is obtained; if the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are inconsistent, a verification result indicating that the object sharing request verification has failed is obtained; and If the verification result indicates that the object sharing request has passed verification, the object sharing request is permitted to be executed; If the target terminal type belongs to the sandbox access terminal or the data analysis terminal, and the object sharing operation is a terminal object upload operation, the object sharing request is rejected; and if the object sharing operation is a system object upload operation, the object sharing request is rejected.
2. The method according to claim 1, wherein, The source address information is used to characterize the Internet Protocol address of the target terminal; The step of responding to receiving an object sharing request initiated by a target user using a target terminal, and determining the target terminal permission rules corresponding to the target terminal type based on the object sharing request, includes: Based on a preset terminal mapping relationship and the source address information, the target terminal type corresponding to the target terminal is determined, wherein the preset terminal mapping relationship includes at least one preset terminal network segment and a preset terminal type corresponding to each of the at least one preset terminal network segment; and The target terminal permission rules are determined based on the preset terminal permission mapping relationship and the target terminal type, wherein the preset terminal permission mapping relationship includes at least one preset terminal type and preset terminal permission rules corresponding to each of the at least one preset terminal type.
3. The method according to claim 2, wherein, The preset terminal types include ordinary access terminals, sandbox access terminals, data analysis terminals, and data export terminals; The step of determining the target terminal type corresponding to the target terminal based on the preset terminal mapping relationship and the source address information includes: If the source address information is located in the first preset terminal network segment, it is determined that the target terminal type belongs to the ordinary access terminal. If the source address information is located in the second preset terminal network segment, it is determined that the target terminal type belongs to the sandbox access terminal; If the source address information is located in a third preset terminal network segment, it is determined that the target terminal type belongs to the data analysis terminal; and If the source address information is located in the fourth preset terminal network segment, it is determined that the target terminal type belongs to the data export terminal.
4. The method according to any one of claims 1 to 3, further comprising, before determining the target user permission rule corresponding to the target user type when it is determined that the target object information satisfies the target terminal permission rule: The target object information is compared with the target terminal permission rules to obtain a first comparison result; If the first comparison result indicates that the target object information and the target terminal permission rules are consistent, then the target object information is determined to satisfy the target terminal permission rules. as well as If the first comparison result indicates that the target object information and the target terminal permission rules are inconsistent, it is determined that the target object information does not meet the target terminal permission rules.
5. The method according to claim 1, wherein, The target object information includes a target user identifier, which is used to represent the identity identification number of the target user; Wherein, determining the target user permission rule corresponding to the target user type when it is determined that the target object information satisfies the target terminal permission rule includes: Based on a preset user mapping relationship and the target user identifier, a target user type corresponding to the target user is determined, wherein the preset user mapping relationship includes at least one preset user identifier and a preset user type corresponding to each of the at least one preset user identifier; and The target user permission rules are determined based on the preset user permission mapping relationship and the target user type, wherein the preset user permission mapping relationship includes at least one preset user type and preset user permission rules corresponding to each of the at least one preset user type.
6. The method according to claim 5, wherein, The step of determining the target user type corresponding to the target user based on the preset user mapping relationship and the target user identifier includes: The target user identifier is matched with each of the at least one preset user identifiers to obtain a matching result; and If the matching result indicates a successful match, the preset user type corresponding to the matching result will be determined as the target user type.
7. The method according to claim 1, wherein, The object sharing operations include: terminal object sharing operations and system object sharing operations. The terminal object sharing operations include the terminal object upload operation, and the system object sharing operations include the system object upload operation, object viewing operation, object download operation, and object preview operation.
8. A verification device for an object sharing request, comprising: The first determining module is configured to respond to receiving an object sharing request initiated by a target user using a target terminal, and determine a target terminal permission rule corresponding to the target terminal type of the target terminal based on the object sharing request. The object sharing request includes target object information and an object sharing type. The target object information includes source address information. The target terminal corresponds to the target terminal type, which is determined based on the source address information. The target terminal type includes a normal access terminal, a sandbox access terminal, a data analysis terminal, and a data export terminal. The object sharing type characterizes the type of object sharing operation, and the target user corresponds to a target user type. The second determining module is used to determine the target user permission rule corresponding to the target user type when it is determined that the target object information satisfies the target terminal permission rule; A comparison unit is configured to compare the target user type, the object sharing type, and the target user permission rules to obtain a second comparison result when the target terminal type belongs to the data export terminal or the ordinary access terminal; a first obtaining unit is configured to obtain a verification result indicating that the object sharing request verification has passed when it is determined that the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are consistent; a second obtaining unit is configured to obtain a verification result indicating that the object sharing request verification has failed when it is determined that the second comparison result indicates that the target user type, the object sharing type, and the target user permission rules are inconsistent; and a permission module is configured to permit the execution of the object sharing request when the verification result indicates that the object sharing request verification has passed. The first rejection module is configured to reject the object sharing request if the object sharing operation is a terminal object upload operation when the target terminal type belongs to the sandbox access terminal or the data analysis terminal; and the second rejection module is configured to reject the object sharing request if the object sharing operation is a system object upload operation.
9. An electronic device, comprising: One or more processors; Memory, used to store one or more instructions. When the one or more instructions are executed by the one or more processors, the one or more processors cause the one or more processors to implement the method of any one of claims 1 to 7.
10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 7.
11. A computer program product comprising computer-executable instructions, which, when executed, are used to implement the method of any one of claims 1 to 7.
Citation Information
Patent Citations
Data processing method and system
CN114168994A
Adaptive hierarchical discrimination algorithm in LCS system
CN1658703A
