Data access method, device, equipment and storage mediumTechnical Field
The embodiments of the present disclosure relate to computer software technologies, and in particular, to a data access method, apparatus, device, and storage medium.
Background
When multiple persons are needed to collaboratively and jointly advance project progress, some data are generally required to be shared by the participants of the project, but not all data are visible to all the participants, and only the persons related to work content can share the same data, namely different data are visible to different persons, the visibility between the data and the data is very different, and the range of visible persons is different.
In the prior art, different authorities are generally given to different people by hard codes so that different people can look up data in the authority range according to the authority of the different people, and the mode can only change the range of the data which can be looked up by modifying the authority of a shared person, so that the operation is complex and the flexibility is poor.
Disclosure of Invention
In view of this, embodiments of the present disclosure provide a data access method, an apparatus, a device, and a storage medium, which solve the technical problem of poor flexibility of the data sharing method in the prior art, so as to provide flexibility of data sharing settings.
In a first aspect, an embodiment of the present disclosure provides a data access method, including:
when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event;
and if the sharing relationship exists between the at least one sharer group identifier corresponding to the user identifier to be accessed and the at least one sharer group identifier corresponding to the access user identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed.
In a second aspect, an embodiment of the present disclosure provides a data access apparatus, including:
a data access device, comprising:
the acquisition module is used for acquiring an access user identifier and a user identifier to be accessed, which correspond to a trigger event when the trigger event of the access data is detected;
and the output module is used for allowing the access user corresponding to the access user identifier to access the data corresponding to the to-be-accessed user identifier if a sharing relationship exists between the at least one shared party group identifier corresponding to the to-be-accessed user identifier and the at least one shared party group identifier corresponding to the access user identifier.
In a third aspect, an embodiment of the present disclosure provides a server device, including:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a data access method as in any of the embodiments of the present disclosure.
In a fourth aspect, the embodiments of the present disclosure provide a computer storage medium, on which a computer program is stored, which when executed by a processor, implements a data access method according to any of the embodiments of the present disclosure.
The embodiment of the disclosure provides a data access method, a device and a storage medium, wherein the data access method comprises the following steps: when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event; and if the sharing relationship exists between at least one sharer group identifier corresponding to the user identifier to be accessed and at least one sharer group identifier corresponding to the access user identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed. Because the shared party and the sharing party of the sharing relationship are both group identifications, the sharing relationship cannot be changed due to the change of the personnel of the shared party group and/or the change of the personnel of the sharing party group, so that the user can randomly delete or increase the personnel identification of any group in the sharing relationship according to the actual requirement, the operation is simple, and the realization is easy.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, a brief description will be given below to the drawings required for the embodiments or the technical solutions in the prior art, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flow chart of a data access method provided in an embodiment of the present disclosure;
FIG. 2 is a flow chart of a data access method provided by the second embodiment of the present disclosure;
FIG. 3 is a flow chart of a data access method provided by a third embodiment of the present disclosure;
fig. 4 shows a block diagram of a data access device provided in the fourth embodiment of the present disclosure;
FIG. 5 is a block diagram illustrating a further data access apparatus provided in the fourth embodiment of the present disclosure;
FIG. 6 is a flow chart of a data access method provided by a fifth embodiment of the present disclosure;
fig. 7 shows a hardware structure diagram of a server device according to a sixth embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Example one
Fig. 1 shows a flowchart of a data access method provided by an embodiment of the present disclosure, which may be applied to a situation where a server performs data sharing based on a sharing relationship established by a human relationship, and the method may be implemented by the server, and may be specifically implemented by software and/or hardware in the server.
As shown in fig. 1, a data access method provided by the embodiment of the present disclosure includes the following steps:
s101, when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed corresponding to the trigger event.
When a user queries the shared data of a user to be accessed at a client, the client generates a data access request according to the query operation, and when a server receives the data access request, a trigger event of access data corresponding to the data access data is generated, and an access user identifier corresponding to the user and a user identifier to be accessed corresponding to the user to be accessed are determined according to the trigger event.
S102, if at least one sharer group identification corresponding to the user identification to be accessed and at least one sharer group identification corresponding to the access user identification have sharing relation, allowing the access user corresponding to the access user identification to access the data corresponding to the user identification to be accessed.
It can be understood that the data of the shared party can only be shared to the sharing party by the sharing party and the shared party which satisfy the sharing relationship, and at the moment, the sharing party can only view the data of the shared party. In order to simplify establishment of a sharing relationship, the embodiment of the present disclosure establishes a sharing relationship based on a human relationship, and specifically, optionally, receives a sharing relationship establishment request from a client, where the sharing relationship establishment request includes a sharing party group identifier and a shared party group identifier; and then establishing a sharing relation between the sharing party group identification and the shared party group identification according to the sharing relation establishing request so that the data of the users of the shared party group are shared by the users of the sharing party group. It will be appreciated that the shared party group and the sharing party group may each include one or more group members.
It can be understood that the to-be-accessed user identifier and the access user identifier may correspond to only one sharing relationship or may correspond to a plurality of sharing relationships, and as long as one sharing relationship allows the access user identifier to access the data of the to-be-accessed user identifier, the data corresponding to the to-be-accessed user identifier is output to the client where the current access user identifier is located.
Regarding the number of sharing relationships, if only the shared party group a1 has a sharing relationship with the sharing party group B1 in all the shared party groups where the to-be-accessed user identifier is located and all the sharing party groups where the accessing user identifier is located, the to-be-accessed user identifier and the accessing user identifier only correspond to one sharing relationship at this time; if the shared party group A1 has a sharing relationship with the sharing party group B1, the shared party group A2 has a sharing relationship with the sharing party group B2, and the shared party group An … has a sharing relationship with the sharing party group Bn, the user identifier to be accessed and the user identifier to be accessed have n sharing relationships.
It will be appreciated that the sharing relationships are typically stored in a sharing relationship table, and that the user is typically required to establish a desired sharing relationship via the server and the established sharing relationship is stored in the sharing relationship table by the server before the sharing relationship is used to view the sharing relationship.
The group identifier may be a department identifier, a project identifier, a group identifier, a job identifier, or the like. For example, taking the project identifier as an example, a unit divides the related personnel of the project P into two work groups, namely, a project group P _ a and a project group P _ B, according to the work content, because of the work nature, the personnel of the project group P _ B needs to be able to view the work data of the personnel of the project group P _ a, but the project group P _ a cannot view the work data of the project group P _ B. Therefore, a sharing relationship between two workgroups needs to be configured, and the configuration process includes: the user sets the identification of the project group P _ B as a sharing party on a configuration interface of the client, sets the identification of the project group P _ A as a shared party, simultaneously selects a one-way sharing relationship establishment option, the client sends the configuration contents as a sharing relationship establishment request to the server, and the server establishes a sharing relationship between the two project groups according to the received sharing relationship establishment request, so that the personnel of the project group P _ B can check the working data of the personnel of the project group P _ A, and the personnel of the project group P _ A cannot check the working data of the personnel of the project group P _ B. It is to be understood that the sharing relationship is set to bidirectional if it is required that the person of the project group P _ a can view the work data of the person of the project group P _ B at the same time.
Because the sharing relationship is established based on the shared party group identifier and the sharing party group identifier, the sharing relationship does not change due to the change of the personnel of the shared party group and/or the change of the personnel of the sharing party group, and therefore, the personnel identifier of any group in the sharing relationship can be deleted or increased according to the actual request condition during the actual use.
The technical scheme of the data access method provided by the embodiment of the disclosure comprises the following steps: when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event; and if the sharing relationship exists between at least one sharer group identifier corresponding to the user identifier to be accessed and at least one sharer group identifier corresponding to the access user identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed. Because the shared party and the sharing party of the sharing relationship are both group identifications, the sharing relationship cannot be changed due to the change of the personnel of the shared party group and/or the change of the personnel of the sharing party group, so that the user can randomly delete or increase the personnel identification of any group in the sharing relationship according to the actual requirement, the operation is simple, and the realization is easy.
Example two
The embodiment of the present disclosure further describes the sharing relationship on the basis of the above embodiment, which is the same inventive concept as the data access method proposed in the above embodiment, and the technical details that are not described in detail in the embodiment of the present disclosure may be referred to in the above embodiment.
Optionally, the sharing relationship establishing request further includes a sharing right, where the sharing right includes a shared data identifier and/or a data modification right, and correspondingly, the sharing relationship includes a shared data identifier and/or a data modification right.
Fig. 2 is a flowchart illustrating a data access method when a sharing relationship includes a sharing data identifier, where the data access method includes the following steps:
s201, when a trigger event of the access data is detected, acquiring an access user identifier, a user identifier to be accessed and an access data identifier corresponding to the trigger event.
When detecting a data access request from a user client, a server generates a trigger event of access data corresponding to the data access data, and acquires an access user identifier, a user identifier to be accessed and an access data identifier corresponding to the trigger event after the trigger event is generated.
The access data identifier may be a document name identifier of the access data and/or a source ID of the access data, where the document name identifier may be a department identifier, a position identifier, a group identifier, a project identifier, and the like.
S202, if at least one sharer group identifier corresponding to the user identifier to be accessed and at least one sharer group identifier corresponding to the access user identifier have a sharing relationship, and the sharing data identifier in the sharing relationship comprises an access data identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the access data identifier.
It can be understood that the data of the shared party can only be shared to the sharing party by the sharing party and the shared party which satisfy the sharing relationship, and at the moment, the sharing party can only view the data of the shared party. Considering that different confidential data of one person to be shared may need to be shared with different sharing parties, and considering the confidentiality of the data, each sharing party can only view the data specified by the sharing party. Therefore, the sharing relationship of the embodiment of the present disclosure is further provided with a shared data identifier. And if at least one sharer group identifier corresponding to the user identifier to be accessed has a sharing relationship with at least one sharer group identifier corresponding to the access user identifier, and the shared data identifier in the sharing relationship comprises an access data identifier, allowing the access user corresponding to the access user identifier to look up data corresponding to the access data identifier. Therefore, the shared party distinguishes whether the data is shared or not and to whom the data is shared through the shared data identification, and the privacy and the safety of data sharing are improved.
Compared with the prior art, the sharing method and the sharing device have the advantages that the sharing relation comprises the sharing data identification on the basis of flexibly setting the shared party group and the sharing party group of the sharing relation, so that the shared party can distinguish whether the data is shared and who the data is shared through the sharing data identification, and the privacy and the safety of data sharing are improved.
EXAMPLE III
The embodiment of the present disclosure further describes the sharing relationship on the basis of the above embodiment, which is the same inventive concept as the data access method proposed in the above embodiment, and the technical details that are not described in detail in the embodiment of the present disclosure may be referred to in the above embodiment.
Optionally, the request for establishing the sharing relationship further includes a sharing data identifier and/or a data modification right, and correspondingly, the sharing relationship includes the sharing data identifier and/or the data modification right.
Fig. 3 shows a flowchart of a data access method when a data modification right is included in a sharing relationship, and the data access method comprises the following steps:
s301, when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed corresponding to the trigger event.
S302, if at least one sharer group identifier corresponding to the user identifier to be accessed and at least one sharer group identifier corresponding to the access user identifier have a sharing relationship, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed.
S303, receiving a modification request of data corresponding to the user identifier to be accessed.
It can be understood that if the sharing of the shared data by the sharee to the sharer is only of the informed type, the sharer is not required to modify the shared data; if the shared party shares the shared data to the sharing party and the sharing party is required to review the data, and the review usually includes data modification, it is often required to make the sharing party have the modification right of the shared data. To this end, the sharing relationship of the embodiment of the present disclosure further includes a data modification authority for specifying whether the sharing party has an authority to modify the shared data referred to by the sharing party.
When receiving a modification request of an access user for data corresponding to the identifier of the user to be accessed, the server automatically checks the current sharing relationship to determine whether the access user has data modification permission for the data corresponding to the identifier of the user to be accessed.
S304, if the sharing authority in the current sharing relationship comprises a data modification authority, modifying the data corresponding to the user identification to be accessed based on the modification request.
If the current sharing relationship comprises the data modification permission, the current access user can modify the data corresponding to the identifier of the user to be accessed, so that the data corresponding to the identifier of the user to be accessed is modified based on the modification request.
It can be understood that, if the server detects that the current sharing relationship does not include the data modification permission, that is, the current access user identifier does not have the modification permission for the data corresponding to the current user identifier to be accessed, at this time, it is preferable to output prompt information for prompting that the user corresponding to the access user does not currently have the modification permission for the data.
It is understood that, for the shared party, after the shared data is modified, it is sometimes necessary to confirm the accuracy of the modification of the shared data with the sharing party, and at this time, it is necessary to explicitly modify the sharing party personnel of the shared data. In order to accurately locate the sharing party person who modifies the shared data, the embodiment of the disclosure preferably adds, after the modification of the shared data is finished, a modification user identifier to the modified shared data, where the modification user identifier is used to indicate the sharing party person identifier who has modified the shared data.
With the aforementioned embodiment, a shared person in the shared party group may set the shared data range accessible by each sharing party through the shared data identifier in the sharing relationship, and set whether each sharing party has the right to modify the shared data accessed by each sharing party through the data modification right in the sharing relationship.
Illustratively, to facilitate data sharing, the data of shared person A is identified by items, such as item A and item B. Considering that the data of the item A does not need to be modified, when the sharing relation of the sharing party group of the item A is established, the sharing data identifier of the sharing relation is set to contain the item A, and the data modification authority of the sharing relation is set to be none; considering that the data of the item B can be modified, when the sharing relation of the sharing party group of the item B is established, the sharing data identification of the sharing relation is set to contain the item B, and the data modification permission of the sharing relation is set to be available. The sharing party group corresponding to the project A can only view the shared data of the shared employee A, wherein the shared data comprises a field of the project A; the sharing party group corresponding to the project B can only refer to the shared data of the shared employee A, wherein the shared data comprises the field of the project B, and meanwhile, the sharing party group has modification authority on the shared data comprising the field of the project B.
Compared with the prior art, the embodiment of the disclosure enables the sharing relationship to include the data modification permission on the basis of flexibly setting the shared party group and the sharing party group of the sharing relationship, and can limit the operation permission of the sharing party on the data through the data modification permission, thereby improving the safety and the convenience of data sharing.
Example four
Fig. 4 is a schematic structural diagram of a data access device according to a fourth embodiment of the present disclosure, where the fourth embodiment of the present disclosure is applicable to a case where a server performs data sharing based on a sharing relationship established by a human relationship. The data access device provided by the present disclosure can implement the data access method provided by the above-mentioned embodiment.
As shown in fig. 4, the data access apparatus in the embodiment of the present disclosure includes:
the acquiring module 11 is configured to, when a trigger event of accessing data is detected, acquire an access user identifier and a to-be-accessed user identifier corresponding to the trigger event;
and an output module 12, configured to allow the accessing user corresponding to the accessing user identifier to access the data corresponding to the to-be-accessed user identifier if a sharing relationship exists between the at least one shared party group identifier corresponding to the to-be-accessed user identifier and the at least one shared party group identifier corresponding to the accessing user identifier.
As shown in fig. 5, the apparatus further includes:
a sharing relationship establishment request module 101, configured to receive a sharing relationship establishment request, where the sharing relationship establishment request includes a sharing party group identifier, a user identifier of a sharing party group, a shared party group identifier, and a user identifier of a shared party group;
the sharing relationship establishing module 102 is configured to establish a sharing relationship between the sharing party group identifier and the shared party group identifier according to the sharing relationship establishing request, so that the data of the user of the shared party group is shared by the user of the sharing party group.
The request for establishing the sharing relationship further includes a sharing data identifier and/or a sharing data modification authority, and correspondingly, the sharing relationship includes the sharing data identifier and/or the sharing data modification authority.
Preferably, the obtaining module is further configured to obtain an access data identifier corresponding to the trigger event; the output module is preferably configured to allow the access user corresponding to the access user identifier to access the data corresponding to the access data identifier if a sharing relationship exists between at least one sharer group identifier corresponding to the to-be-accessed user identifier and at least one sharer group identifier corresponding to the access user identifier, and the shared data identifier in the sharing relationship includes the access data identifier.
Preferably, the method further comprises the following steps: a modification request receiving module 131, configured to receive a modification request for data corresponding to the to-be-accessed user identifier; and a modifying module 132, configured to modify, if the current sharing relationship includes a data modification permission, data corresponding to the to-be-accessed user identifier based on the modification request.
Preferably, an identification adding module 14 is further included for adding a modification user identification to the modified data after the data modification is finished.
The technical scheme of the data access method provided by the embodiment of the disclosure comprises the following steps: when a trigger event of the access data is detected through the acquisition module, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event; and allowing the access user corresponding to the access user identifier to access the data corresponding to the to-be-accessed user identifier through the output module if the sharing relationship exists between the at least one sharer group identifier corresponding to the to-be-accessed user identifier and the at least one sharer group identifier corresponding to the access user identifier. Because the shared party and the sharing party of the sharing relationship are both group identifications, the sharing relationship cannot be changed due to the change of the personnel of the shared party group and/or the change of the personnel of the sharing party group, so that the user can randomly delete or increase the personnel identification of any group in the sharing relationship according to the actual requirement, the operation is simple, and the realization is easy.
EXAMPLE five
Fig. 6 shows a flowchart of a data access method provided by the fifth embodiment of the present disclosure, which is applicable to a case where a client performs data sharing based on a sharing relationship established by a human relationship, and the method may be implemented by the client, and may specifically be implemented by software and/or hardware in the client.
S501, when receiving data of a user identifier to be accessed consulted by an accessing user, sending a data access request for accessing the data corresponding to the user identifier to be accessed to a server, so that the server determines whether a sharing relation exists between an accessing user identifier corresponding to the accessing user, a user identifier to be accessed corresponding to the user to be accessed and at least one shared party group identifier corresponding to the accessing user identifier relative to at least one sharing party group identifier corresponding to the user to be accessed.
When an accessing user accesses to-be-accessed user data based on the sharing relationship described in the foregoing disclosure embodiment, generally, a to-be-accessed user identifier needs to be input in a query interface of a client, or the to-be-accessed user identifier and the to-be-accessed shared data identifier need to be input, the client generates a data access request according to the information input by the user, and sends the data access request to a server. And enabling the server to determine whether the access user identification corresponding to the access user, the user identification to be accessed corresponding to the user to be accessed and at least one sharee group identification corresponding to the access user identification have a sharing relationship with respect to at least one sharee group identification corresponding to the user to be accessed according to the data access request.
It can be understood that the data of the shared party can only be shared to the sharing party by the sharing party and the shared party which satisfy the sharing relationship, and at the moment, the sharing party can only view the data of the shared party. In order to simplify the establishment of the sharing relationship, the embodiment of the present disclosure establishes the sharing relationship based on the personnel relationship, and specifically, optionally, the user inputs the shared party group identifier, the sharing party group identifier, and the sharing relationship permission range on the sharing relationship establishment page of the client, and the client generates the sharing relationship establishment request according to the shared party group identifier, the sharing party group identifier, and the sharing relationship permission range, and sends the sharing relationship establishment request to the server. And receiving the sharing relation establishment request, and establishing the sharing relation between the sharing party group identifier and the shared party group identifier according to the sharing relation establishment request so that the data of the users of the shared party group are shared by the users of the sharing party group. It will be appreciated that the shared party group and the sharing party group may each include one or more group members.
And S502, receiving and outputting data corresponding to the user identification to be accessed fed back by the server when the sharing relationship exists.
And if at least one sharer group identifier corresponding to the user identifier to be accessed has a sharing relation with at least one sharer group identifier corresponding to the user identifier to be accessed, the server sends the data corresponding to the user identifier to be accessed to the client corresponding to the user identifier to be accessed.
In the embodiment of the disclosure, since the shared party and the sharing party of the sharing relationship are both group identifiers, the sharing relationship does not change due to the change of the personnel of the shared party group and/or the change of the personnel of the sharing party group, so that the user can randomly delete or increase the personnel identifier of any group in the sharing relationship according to the actual requirement, the operation is simple, and the implementation is easy.
EXAMPLE six
Fig. 7 shows a hardware structure diagram of a server device according to a sixth embodiment of the present disclosure. As shown in fig. 7, the server apparatus 600 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 601, which may perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 602 or a program loaded from a storage device 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
The terminal provided by the embodiment of the present disclosure and the data access method provided by the above embodiment belong to the same inventive concept, and technical details that are not described in detail in the embodiment of the present disclosure may be referred to the above embodiment, and the embodiment of the present disclosure and the above embodiment have the same beneficial effects.
EXAMPLE seven
The seventh embodiment of the present disclosure provides a computer storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the data access method provided by the above embodiments.
It should be noted that the computer storage media described above in this disclosure can be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or FLASH Memory (FLASH), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer storage may be contained in the electronic device; or may exist separately without being assembled into the electronic device.
The computer stores one or more programs that, when executed by the server device, cause the server device to: when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event; and if the sharing relationship exists between at least one sharer group identifier corresponding to the user identifier to be accessed and at least one sharer group identifier corresponding to the access user identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments of the present disclosure, [ example one ] there is provided a data access method comprising:
when a trigger event of accessing data is detected, acquiring an access user identifier and a user identifier to be accessed, which correspond to the trigger event;
and if the sharing relationship exists between the at least one sharer group identifier corresponding to the user identifier to be accessed and the at least one sharer group identifier corresponding to the access user identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the user identifier to be accessed.
According to one or more embodiments of the present disclosure, [ example two ] there is provided a data access method, further comprising:
receiving a sharing relation establishment request, wherein the sharing relation establishment request comprises a sharing party group identifier and a shared party group identifier;
and according to the sharing relation establishment request, establishing a sharing relation between the sharing party group identification and the shared party group identification so that the data of the users of the shared party group are shared by the users of the sharing party group.
According to one or more embodiments of the present disclosure, [ example three ] there is provided a data access method, further comprising:
optionally, the request for establishing the sharing relationship further includes a shared data identifier and/or a shared data modification permission, and correspondingly, the sharing relationship includes the shared data identifier and/or the shared data modification permission.
According to one or more embodiments of the present disclosure, an [ example four ] provides a data access method, where the sharing relationship includes a shared data identifier, and the obtaining of the access user identifier and the to-be-accessed user identifier corresponding to the trigger event at the same time/after further includes:
acquiring an access data identifier corresponding to a trigger event of access data;
correspondingly, if there is a sharing relationship between at least one sharer group identifier corresponding to the to-be-accessed user identifier and at least one sharer group identifier corresponding to the access user identifier, allowing the client corresponding to the access user identifier to access the data corresponding to the to-be-accessed user identifier includes:
and if at least one sharer group identifier corresponding to the user identifier to be accessed has a sharing relationship with at least one sharer group identifier corresponding to the access user identifier, and the shared data identifier in the sharing relationship comprises the access data identifier, allowing the access user corresponding to the access user identifier to access the data corresponding to the access data identifier.
According to one or more embodiments of the present disclosure, [ example five ] there is provided a data access method, further comprising:
optionally, the sharing relationship includes a sharing data modification right, and after the access user corresponding to the access user identifier is allowed to access the data corresponding to the to-be-accessed user identifier, the method further includes:
receiving a modification request for data corresponding to the user identifier to be accessed;
and if the current sharing relation comprises data modification permission, modifying the data corresponding to the user identification to be accessed based on the modification request.
According to one or more embodiments of the present disclosure, [ example six ] there is provided a data access method comprising:
optionally, if the sharing right in the current sharing relationship includes a data modification right, after modifying the data corresponding to the to-be-accessed user identifier based on the modification request, the method further includes:
after the data modification is finished, adding a modification user identification to the modified data.
According to one or more embodiments of the present disclosure, [ example seven ] there is provided a data access apparatus comprising:
the acquisition module is used for acquiring an access user identifier and a user identifier to be accessed, which correspond to a trigger event when the trigger event of the access data is detected;
and the output module is used for allowing the access user corresponding to the access user identifier to access the data corresponding to the to-be-accessed user identifier if a sharing relationship exists between the at least one shared party group identifier corresponding to the to-be-accessed user identifier and the at least one shared party group identifier corresponding to the access user identifier.
According to one or more embodiments of the present disclosure, [ example eight ] there is provided a data access method, further comprising:
a sharing relation establishment request module, configured to receive a sharing relation establishment request, where the sharing relation establishment request includes a sharing party group identifier, a user identifier of the sharing party group, a shared party group identifier, and a user identifier of the shared party group;
a sharing relationship establishing module, configured to establish a sharing relationship between the sharing party group identifier and the shared party group identifier according to the sharing relationship establishing request, so that the data of the user of the shared party group is shared by the user of the sharing party group.
According to one or more embodiments of the present disclosure, [ example nine ] there is provided a server apparatus comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a data access method as in any of the embodiments of the present disclosure.
According to one or more embodiments of the present disclosure, [ example ten ] there is provided a storage medium containing computer-executable instructions, characterized in that the computer-executable instructions, when executed by a computer processor, are for performing a data access method as any one of the embodiments of the present disclosure.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.