CN111491188A - Authority management method, routing device and system - Google Patents
Authority management method, routing device and system Download PDFInfo
- Publication number
- CN111491188A CN111491188A CN202010155788.9A CN202010155788A CN111491188A CN 111491188 A CN111491188 A CN 111491188A CN 202010155788 A CN202010155788 A CN 202010155788A CN 111491188 A CN111491188 A CN 111491188A
- Authority
- CN
- China
- Prior art keywords
- identifier
- preset list
- receiving
- equipment
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/254—Management at additional data server, e.g. shopping server, rights management server
- H04N21/2541—Rights Management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
- H04N21/25866—Management of end-user data
- H04N21/25875—Management of end-user data involving end-user authentication
Abstract
The present disclosure provides a rights management method, a routing device and a system, which relate to the technical field of computers, and the method is applied to the routing device and comprises the following steps: receiving an acquisition request from a receiving end, wherein the acquisition request carries an equipment identifier and a request data source identifier; inquiring the authority level corresponding to the equipment identifier in a first preset list, wherein the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal; judging whether the permission level corresponding to the equipment identifier meets a preset condition or not; if the request is met, the acquisition request is sent to the acquisition end, so that the acquisition end finds the corresponding target source according to the request data source identifier and sends the target source to the routing device; and sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier. The method and the device can solve the problem of realizing authority management on the receiving end on the routing device.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method, a routing device, and a system for managing permissions.
Background
The wireless image transmission system comprises a collection end (S end), a receiving end (R end) and an image Router (VGR) arranged between the S end and the R end. The S-terminal is used for acquiring an image source, which may be a video and a picture stored in the S-terminal, or a video and a picture acquired by the S-terminal through some channels, such as a live video and a picture acquired through a camera. The S end can send the collected image source to the R end, and the R end displays the image source to a user through the display.
With the personalized requirements of users, how to realize the distribution management function of the R terminal on the premise of keeping the lightweight of the S terminal and the R terminal is a problem to be solved.
Disclosure of Invention
The embodiment of the disclosure provides a permission management method, a routing device and a system, which can solve the problem that the conventional equipment can realize permission management on a receiving end on the routing device. The technical scheme is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a rights management method applied to a routing device, the method including:
receiving an acquisition request from a receiving end, wherein the acquisition request carries an equipment identifier and a request data source identifier;
inquiring the authority level corresponding to the equipment identifier in a first preset list, wherein the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
judging whether the permission level corresponding to the equipment identifier meets a preset condition or not;
if the request is met, the acquisition request is sent to the acquisition end, so that the acquisition end finds the corresponding target source according to the request data source identifier and sends the target source to the routing device;
and sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier.
In one embodiment, before receiving the acquisition request from the receiving end, the method further comprises:
acquiring an access request of a receiving end, wherein the access request carries an equipment identifier;
judging whether the equipment identification exists in a second preset list or not, wherein the second preset list stores the equipment identification of the receiving terminal equipment which is allowed to be accessed;
if the device identification is present in the second predetermined list, a step of receiving an acquisition request from the receiving end is performed.
In one embodiment, the first preset list further stores a corresponding relationship between the device identifier and the validity period;
before querying the permission level corresponding to the device identifier in the first preset list, the method further includes:
acquiring the receiving time of receiving an acquisition request from a receiving end;
judging whether the receiving time is within the valid period or not based on the first preset list;
and if the receiving time is not within the valid period, the step of inquiring the authority level corresponding to the equipment identification in the first preset list is executed.
In one embodiment, the determining whether the permission level corresponding to the device identifier satisfies the preset condition includes:
if the authority level corresponding to the equipment identifier is the first level, judging that the authority level corresponding to the equipment identifier meets a preset condition; or
If the permission level corresponding to the device identifier is the second level, judging whether the permission level corresponding to the device identifier meets the preset condition or not comprises the following steps:
inquiring whether a target data source identifier corresponding to the corresponding authority level contains a request data source identifier or not in a third preset list, wherein the third preset list stores the corresponding relation between the authority level and the target data source identifier, and the target data source identifier corresponds to a target data source of the acquisition end;
if yes, judging that the permission level corresponding to the equipment identifier meets a preset condition; or
And if the permission level corresponding to the equipment identifier is the third level, judging that the permission level corresponding to the equipment identifier does not meet the preset condition.
In one embodiment, the method further comprises:
if not, returning a message of acquisition failure to the receiving end.
The method further comprises the following steps: modifying the first preset list and/or the second preset list;
modifying the first preset list and/or the second preset list comprises at least one of:
when an acquisition request of a receiving end corresponding to the equipment identifier is not received within first preset time, deleting the corresponding relation between the equipment identifier and the authority level from the first preset list;
acquiring current time, and deleting the corresponding relation between the equipment identifier and the authority level from the first preset list when the valid period in the first preset list is earlier than the current time;
when the access request of the receiving end corresponding to the equipment identifier is not received within second preset time, deleting the equipment identifier from the second preset list;
and acquiring a deletion request sent by a receiving end, wherein the deletion request carries an equipment identifier, deleting the corresponding relation between the equipment identifier and the authority level from the first preset list, and deleting the equipment identifier from the second preset list.
The authority management method provided by the embodiment of the disclosure realizes the distribution management function of the routing device end to the R end on the premise of keeping the lightweight of the S end and the R end.
According to a second aspect of the embodiments of the present disclosure, there is provided a routing apparatus, including:
the receiving module is used for receiving an acquisition request from a receiving end, wherein the acquisition request carries an equipment identifier and a request data source identifier;
the inquiry module is used for inquiring the authority level corresponding to the equipment identifier in a first preset list, the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
the judging module is used for judging whether the permission level corresponding to the equipment identifier meets a preset condition or not;
the first sending module is used for sending the acquisition request to the acquisition end if the acquisition request is met, so that the acquisition end finds the corresponding target source according to the request data source identifier and sends the target source to the routing device;
and the second sending module is used for sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier.
In one embodiment, the apparatus further comprises:
the device comprises a preprocessing module, a receiving end and a processing module, wherein the preprocessing module is used for acquiring an access request of the receiving end before receiving the acquisition request from the receiving end, and the access request carries a device identifier;
judging whether the equipment identification exists in a second preset list or not, wherein the second preset list stores the equipment identification of the receiving terminal equipment which is allowed to be accessed;
if the device identifier exists in the second preset list, the step of receiving the acquisition request from the receiving end by the receiving module is executed.
The routing device provided by the embodiment of the disclosure realizes the distribution management function of the routing device to the R end on the premise of keeping the S end and the R end lightweight.
According to a third aspect of the embodiments of the present disclosure, there is provided a routing apparatus, including: the storage is used for storing a first preset list and a second preset list, and the processor is used for executing the authority management method of the first aspect.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a rights management system, which includes a collecting end, at least one receiving end, and the routing device of the second aspect or the third aspect.
In the invention, the VGR can distribute the image source of the S end to a plurality of R ends, and the VGT realizes the management function of the R end, specifically comprising judging the authority of the R end for accessing the VGR, acquiring the authority of the image source of the S end and the like, wherein the VGR can be arranged between the S end and the R end.
Therefore, the individual requirements of users can be met through the management of the VGR to the R end, and the functions are put on the VRG, so that the workload of the S-end equipment and the R-end equipment can be prevented from being increased, and the light weight of the S-end equipment and the R-end equipment is ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flowchart of a rights management method provided by an embodiment of the disclosure;
FIG. 2 is a flowchart of a rights management method provided by an embodiment of the disclosure;
FIG. 3 is a diagram of a rights management system according to an embodiment of the present disclosure;
FIG. 4 is a flowchart of a rights management method provided by an embodiment of the disclosure;
fig. 5 is a structural diagram of a routing device according to an embodiment of the present disclosure;
fig. 6 is a structural diagram of a routing device according to an embodiment of the present disclosure;
fig. 7 is a structural diagram of a routing device according to an embodiment of the present disclosure;
fig. 8 is a structural diagram of a routing device according to an embodiment of the present disclosure;
fig. 9 is a structural diagram of a routing device according to an embodiment of the present disclosure;
fig. 10 is a structural diagram of a routing device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a rights management method provided by an embodiment of the present disclosure, where the rights management method is applied to a routing device, and the rights management method includes the following steps:
103, inquiring an authority level corresponding to the equipment identifier in a first preset list, wherein the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
and step 109, sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier.
Fig. 2 is a right management method provided by an embodiment of the present disclosure, where the right management method is applied to a routing device, and the right management method includes the following steps:
the second preset list stores the device identification of the receiving terminal device allowed to be accessed;
if the device identifier exists in the second preset list, step 101 is executed, and if the device identifier does not exist in the second preset list, the process ends.
in one embodiment, the first preset list further stores a corresponding relationship between the device identifier and the validity period;
if the reception time is within the valid period, the step of step 103 is performed, and if the reception time is not within the valid period, the flow ends.
103, inquiring an authority level corresponding to the equipment identifier in a first preset list, wherein the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
illustratively, the authority level can be set to three levels, the first level is identified by 2, the receiving end corresponding to the identification is a VIP user and can receive all image sources from the acquisition end; the second level is marked by 1, a receiving end corresponding to the mark is a common user, and can receive part of image sources from the acquisition end, specifically which part of the image sources have authority to be received and need to be set in a third preset list; and the third level is marked by 0, and the receiving end corresponding to the mark is a limited user and cannot receive the image source from the acquisition end. The specific classification may also have more levels or select some of the levels, which is not limited in this embodiment.
if yes, step 107 is executed, and if not, a message of acquisition failure is returned to the receiving end, and the process is ended.
Optionally, the determining whether the permission level corresponding to the device identifier meets the preset condition includes:
if the authority level corresponding to the equipment identifier is the first level, judging that the authority level corresponding to the equipment identifier meets a preset condition; or
If the permission level corresponding to the device identifier is the second level, judging whether the permission level corresponding to the device identifier meets the preset condition or not comprises the following steps:
inquiring whether a target data source identifier corresponding to the corresponding authority level contains a request data source identifier or not in a third preset list, wherein the third preset list stores the corresponding relation between the authority level and the target data source identifier, and the target data source identifier corresponds to a target data source of the acquisition end;
if yes, judging that the permission level corresponding to the equipment identifier meets a preset condition; or
And if the permission level corresponding to the equipment identifier is the third level, judging that the permission level corresponding to the equipment identifier does not meet the preset condition.
and step 109, sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier.
In the embodiment described in fig. 1 and 2, the first preset list and the second preset list may be modified, for example:
when an acquisition request of a receiving end corresponding to the equipment identifier is not received within first preset time, deleting the corresponding relation between the equipment identifier and the authority level from the first preset list;
acquiring current time, and deleting the corresponding relation between the equipment identifier and the authority level from the first preset list when the valid period in the first preset list is earlier than the current time;
when the access request of the receiving end corresponding to the equipment identifier is not received within second preset time, deleting the equipment identifier from the second preset list;
and acquiring a deletion request sent by a receiving end, wherein the deletion request carries an equipment identifier, deleting the corresponding relation between the equipment identifier and the authority level from the first preset list, and deleting the equipment identifier from the second preset list.
Fig. 3 is a schematic diagram of a rights management system where a routing device is located according to the present disclosure, where the system includes: the system comprises a collecting end S end, a receiving end R end and an image router VGR arranged between the S end and the R end. The S-terminal is used for acquiring an image source, which may be a video and a picture stored in the S-terminal, or a video and a picture acquired by the S-terminal through some channels, such as a live video and a picture acquired through a camera. One S end corresponds to at least one R end, and the S end distributes the image source to a plurality of R ends through VGR. The VGR can also be arranged at the S end, but the S end equipment is large in size and inconvenient to use and is not attractive, so that the VGR and the S end equipment can be separately arranged, for example, the VGR can be arranged in a machine room. The VGR includes a processing module and a storage module, the processing module may be a CPU, and the storage module may be a hard disk.
Fig. 4 is a flowchart of a rights management method provided in an embodiment of the present disclosure, which is based on the system shown in fig. 3, and specifically includes the following steps:
illustratively, the first list is a right management list for identifying the right of each receiving end to receive the image source of the collecting end. As shown in table 1, the first list includes R-terminal identifiers and privilege levels. The R-end identifier can uniquely represent one R end, and the permission levels comprise 0, 1, 2 and 3 …, and are used for identifying the permission of each R receiving S-end image source.
| R-terminal identifier | Permission level |
| R1 | 0 (restricted users) |
| R2 | 1 (common user) |
| R3 | 2 (senior user) |
TABLE 1
Illustratively, as shown in Table 2, the first list includes an R-terminal identifier, a validity period, and a permission level. The R end identifier can uniquely represent one R end, the validity period refers to the time limit that the R end can obtain images from S ends, and the authority levels comprise 0, 1, 2 and 3 … and are used for identifying the authority of each R for receiving the images from the S ends.
Specifically, the image source corresponding to the R end of each authority level may be preset in the VGR according to actual requirements.
| R-terminal identifier | Period of validity | Permission level |
| R1 | 2019.5.30 | 0 (restricted users) |
| R2 | 2020.5.1 | 1 (common user) |
| R3 | 2019.12.31 | 2 (senior user) |
TABLE 2
The second list is an access list, and the access list comprises an R end identifier; that is, only the R terminal stored in the VGR allows the image source at the S terminal to be acquired.
The management list and the admission list are stored in a storage module of the VGR.
Specifically, the user may set the management list and the admission list on the VGR through the S-side, or may make the management list on the VGR empty.
if yes, go to step 403, otherwise, terminate the process and return a response message of access failure to the R-side.
Wherein the access request comprises an R-terminal identifier, a validity period and an authority level.
In practical application, the admission list may also be an effective IP address field, and the inherent attributes of the R terminals, such as the geographic region where the R is located, and the R terminals may be distinguished according to the inherent attributes to screen out the R terminals meeting the conditions.
Specifically, the R-side identifier, the validity period, and the permission level carried by the access request may be respectively filled in the management list.
Of course, the upper limit of the sequence number of the management list may also be set, and when the accessed R-side exceeds the upper limit of the sequence number, the R-side is denied access.
if yes, sending an acquisition request to the S end, otherwise, not sending the acquisition request to the S end, and returning a message of acquisition failure to the R end.
It should be noted that, the R end and the S end both preset the corresponding relationship between the serial number and the image source.
For example, an image source code included in the acquisition request sent by the R1 end is a, the corresponding image source is an english class video of the first grade of primary school, the validity period of the R1 end is 2020.5.1, the authority level is 1 (common user), and the image source corresponding to the R end with the preset authority level of 1 (common user) in the VGR includes the image source coded as a, then, the VGR can determine that the R1 can acquire the image source with the number of a by comparing the validity period with the current time and viewing the range of the image source corresponding to the R end with the level of 1, so that the VGR can send the acquisition request to the S end, where the acquisition request includes the code a of the image source.
For another example, the image source code included in the acquisition request sent by the R2 end is B, the corresponding image source is an adult self-examination course video, the validity period of the R2 end is 2019.5.30, but the permission level of the R2 end is 0 (limited user), the image source corresponding to the R end with the permission level of 0 (limited user) preset in the VGR does not include the image source coded as B, the VGR returns the acquisition failure message to the R1 end, and does not send the acquisition request to the S end.
In addition, the VGR can also maintain the management list; for example, when a certain R-side in the admission list cannot send an acquisition request again within a period of time, the R-side may also be deleted from the management list. Or, when the validity period of some R terminals in the management list expires, the R terminals may also be deleted from the management list. Of course, the R-side may also delete itself from the management list by sending a delete request to the VGR.
Fig. 5 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: a receiving module 501, a query module 502, a judgment module 503, a first sending module 504 and a second sending module 505;
a receiving module 501, configured to receive an acquisition request from a receiving end, where the acquisition request carries an equipment identifier and a request data source identifier;
a query module 502, configured to query, in a first preset list, an authority level corresponding to the device identifier, where the first preset list stores a correspondence between the device identifier and the authority level, and the device identifier corresponds to the receiving terminal;
a determining module 503, configured to determine whether the permission level corresponding to the device identifier meets a preset condition;
a first sending module 504, configured to send the acquisition request to the acquisition end if the request is met, so that the acquisition end finds a corresponding target source according to the request data source identifier and sends the target source to the routing device;
and a second sending module 505, configured to send the found corresponding target source to the corresponding receiving end according to the device identifier.
Fig. 6 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: a receiving module 501, a query module 502, a judgment module 503, a first sending module 504, a second sending module 505 and a preprocessing module 500,
a preprocessing module 500, configured to obtain an access request from a receiving end before receiving the obtaining request from the receiving end, where the access request carries an equipment identifier;
judging whether the equipment identification exists in a second preset list or not, wherein the second preset list stores the equipment identification of the receiving terminal equipment which is allowed to be accessed;
if the device identifier exists in the second preset list, the step of receiving the acquisition request from the receiving end by the receiving module is executed.
In all embodiments, the determining module 503 is specifically configured to: if the authority level corresponding to the equipment identifier is the first level, judging that the authority level corresponding to the equipment identifier meets a preset condition; and if the permission level corresponding to the equipment identifier is a third level, judging that the permission level corresponding to the equipment identifier does not meet a preset condition.
Fig. 7 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: a receiving module 501, a querying module 502, a determining module 503, a first sending module 504, and a second sending module 505, where if the permission level corresponding to the device identifier is a second level, the determining module 503 includes:
the query submodule 5031 is configured to query whether the target data source identifier corresponding to the corresponding permission level includes the request data source identifier in a third preset list, where a correspondence between the permission level and the target data source identifier is stored in the third preset list, and the target data source identifier corresponds to the target data source of the acquisition end;
the determining sub-module 5032 is configured to determine that the permission level corresponding to the device identifier meets a preset condition if the permission level exists.
In all embodiments, the first preset list further stores a corresponding relationship between the device identifier and the validity period;
the determining module 503 is further configured to: before querying the authority level corresponding to the device identification in the first preset list,
acquiring the receiving time of receiving an acquisition request from a receiving end;
judging whether the receiving time is within the valid period or not based on the first preset list;
and if the receiving time is not within the valid period, the step of inquiring the authority level corresponding to the equipment identification in a first preset list is executed.
Fig. 8 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: the receiving module 501, the querying module 502, the judging module 503, the first sending module 504, the second sending module 505, and the feedback module 506 are configured to return a message of acquisition failure to the receiving end if the receiving end fails to acquire the message.
Fig. 9 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: a receiving module 501, a query module 502, a judging module 503, a first sending module 504, a second sending module 505 and a modifying module 507, configured to modify the first preset list and/or the second preset list;
the modification module is specifically configured to at least one of:
when an acquisition request of a receiving end corresponding to the equipment identification is not received within first preset time, deleting the corresponding relation between the equipment identification and the authority level from a first preset list;
acquiring current time, and deleting the corresponding relation between the equipment identifier and the authority level from the first preset list when the validity period in the first preset list is earlier than the current time;
when the access request of the receiving end corresponding to the equipment identification is not received within second preset time, deleting the equipment identification from a second preset list;
the method comprises the steps of obtaining a deleting request sent by a receiving end, deleting a corresponding relation between an equipment identifier and an authority level from a first preset list, and deleting the equipment identifier from a second preset list, wherein the deleting request carries the equipment identifier. Fig. 10 is a routing apparatus provided in an embodiment of the present disclosure, where the routing apparatus includes: a processor 1001 and a memory 1002, wherein,
the routing device may include one or more processors 1001 and a memory 1002, wherein the memory 1002 is used for storing programs, the processors 1001 are communicatively connected with the memory 1002 through a bus 1003, and the processors 1001 call the programs stored in the memory 1002 to execute the above method embodiments.
It should be noted that Processor 1001 may include one or more Processing cores (e.g., a single-core Processor or a multi-core Processor), by way of example only, a Processor may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Set Processor (ASIP), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable logic Device (Programmable L), a P L D), a controller, a microcontroller Unit, a Reduced Instruction Set computer (Reduced Instruction Set computer, Device), a microprocessor, or any combination thereof.
The memory 1002 may include: including mass storage, removable storage, volatile Read-and-write Memory, or Read-Only Memory (ROM), among others, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state drives, and the like; removable memory may include flash drives, floppy disks, optical disks, memory cards, zip disks, tapes, and the like; volatile read-write Memory may include Random Access Memory (RAM); the RAM may include Dynamic RAM (DRAM), Double data Rate Synchronous Dynamic RAM (DDR SDRAM); static RAM (SRAM), Thyristor-Based Random Access Memory (T-RAM), Zero-capacitor RAM (Zero-RAM), and the like. By way of example, ROMs may include Mask Read-Only memories (MROMs), Programmable ROMs (PROMs), erasable Programmable ROMs (PERROMs), Electrically Erasable Programmable ROMs (EEPROMs), compact disk ROMs (CD-ROMs), digital versatile disks (ROMs), and the like.
For ease of illustration, only one processor 1001 is depicted in the routing device. It should be noted, however, that the routing device in the present application may also include multiple processors 1001, and thus, the steps performed by one processor described in the present application may also be performed by multiple processors in combination or individually. For example, if the processor 1001 of the routing device executes step a and step B, it should be understood that step a and step B may also be executed by two different processors together or separately in one processor. For example, a first processor performs step a and a second processor performs step B, or the first processor and the second processor perform steps a and B together.
Fig. 3 is a structural diagram of a rights management system according to an embodiment of the disclosure, where the rights management system shown in fig. 3 includes a collection end, any one of the routing devices in the foregoing embodiments, and at least one receiving end.
The authority management method provided by the embodiment of the disclosure realizes the distribution management function of the routing device end to the R end on the premise of keeping the lightweight of the S end and the R end.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (10)
1. A method for managing authority is applied to a routing device, and is characterized in that the method comprises the following steps:
receiving an acquisition request from a receiving end, wherein the acquisition request carries an equipment identifier and a request data source identifier;
inquiring the authority level corresponding to the equipment identifier in a first preset list, wherein the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
judging whether the permission level corresponding to the equipment identifier meets a preset condition or not;
if the request is met, the acquisition request is sent to an acquisition end, so that the acquisition end finds a corresponding target source according to the request data source identifier and sends the target source to the routing device;
and sending the searched corresponding target source to a corresponding receiving end according to the equipment identification.
2. The rights management method of claim 1, wherein prior to receiving the acquisition request from the receiver, the method further comprises:
acquiring an access request of a receiving end, wherein the access request carries an equipment identifier;
judging whether the equipment identification exists in a second preset list or not, wherein the second preset list stores the equipment identification of the receiving terminal equipment which is allowed to be accessed;
and if the equipment identification exists in the second preset list, executing the step of receiving an acquisition request from a receiving end.
3. The rights management method according to claim 1, wherein the first preset list further stores a correspondence between a device identifier and a validity period;
before querying the permission level corresponding to the device identifier in the first preset list, the method further includes:
acquiring the receiving time of receiving an acquisition request from a receiving end;
judging whether the receiving time is within the valid period or not based on the first preset list;
and if the receiving time is not within the valid period, the step of inquiring the authority level corresponding to the equipment identification in a first preset list is executed.
4. The rights management method of claim 1, wherein the determining whether the level of rights corresponding to the device identifier satisfies a preset condition comprises:
if the authority level corresponding to the equipment identifier is the first level, judging that the authority level corresponding to the equipment identifier meets a preset condition; or
If the permission level corresponding to the device identifier is a second level, judging whether the permission level corresponding to the device identifier meets a preset condition comprises the following steps:
inquiring whether the target data source identification corresponding to the corresponding authority level contains the request data source identification or not in a third preset list, wherein the third preset list stores the corresponding relation between the authority level and the target data source identification, and the target data source identification corresponds to the target data source of the acquisition end;
if so, judging that the permission level corresponding to the equipment identifier meets a preset condition; or
And if the permission level corresponding to the equipment identifier is a third level, judging that the permission level corresponding to the equipment identifier does not meet a preset condition.
5. The rights management method of claim 1, further comprising:
if not, returning a message of acquisition failure to the receiving end.
6. The rights management method according to any one of claims 1-5, characterized in that the method further comprises: modifying the first preset list and/or the second preset list;
modifying the first preset list and/or the second preset list comprises at least one of:
when an acquisition request of a receiving end corresponding to the equipment identification is not received within first preset time, deleting the corresponding relation between the equipment identification and the authority level from a first preset list;
acquiring current time, and deleting the corresponding relation between the equipment identifier and the authority level from the first preset list when the validity period in the first preset list is earlier than the current time;
when the access request of the receiving end corresponding to the equipment identification is not received within second preset time, deleting the equipment identification from a second preset list;
the method comprises the steps of obtaining a deleting request sent by a receiving end, deleting a corresponding relation between an equipment identifier and an authority level from a first preset list, and deleting the equipment identifier from a second preset list, wherein the deleting request carries the equipment identifier.
7. A routing apparatus, characterized in that the routing apparatus comprises:
the receiving module is used for receiving an acquisition request from a receiving end, wherein the acquisition request carries an equipment identifier and a request data source identifier;
the inquiry module is used for inquiring the authority level corresponding to the equipment identifier in a first preset list, the first preset list stores the corresponding relation between the equipment identifier and the authority level, and the equipment identifier corresponds to the receiving terminal;
the judging module is used for judging whether the permission level corresponding to the equipment identifier meets a preset condition or not;
the first sending module is used for sending the acquisition request to the acquisition end if the acquisition request is met, so that the acquisition end finds the corresponding target source according to the request data source identifier and sends the target source to the routing device;
and the second sending module is used for sending the searched corresponding target source to the corresponding receiving end according to the equipment identifier.
8. The routing device of claim 7, wherein the device further comprises:
the device comprises a preprocessing module, a receiving end and a processing module, wherein the preprocessing module is used for acquiring an access request of the receiving end before receiving the acquisition request from the receiving end, and the access request carries a device identifier;
judging whether the equipment identification exists in a second preset list or not, wherein the second preset list stores the equipment identification of the receiving terminal equipment which is allowed to be accessed;
and if the equipment identification exists in the second preset list, executing a step that a receiving module receives an acquisition request from a receiving end.
9. A routing device, comprising a memory configured to store a first preset list and a second preset list, and a processor configured to perform the rights management method of any of claims 1-5.
10. A rights management system comprising an acquisition end, at least one receiving end and a routing means according to any of claims 7-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010155788.9A CN111491188A (en) | 2020-03-09 | 2020-03-09 | Authority management method, routing device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010155788.9A CN111491188A (en) | 2020-03-09 | 2020-03-09 | Authority management method, routing device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111491188A true CN111491188A (en) | 2020-08-04 |
Family
ID=71811607
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010155788.9A Pending CN111491188A (en) | 2020-03-09 | 2020-03-09 | Authority management method, routing device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111491188A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105100708A (en) * | 2015-06-26 | 2015-11-25 | 小米科技有限责任公司 | Request processing method and device |
| CN105429933A (en) * | 2014-09-19 | 2016-03-23 | 中国电信股份有限公司 | Access method of network equipment in local area network, access equipment and system |
| CN105787342A (en) * | 2016-02-26 | 2016-07-20 | 北京小米移动软件有限公司 | Method and device for executing target function |
| KR20190007125A (en) * | 2017-07-11 | 2019-01-22 | 주식회사 아이앤나 | Method for Providing Observation Camera Image |
| CN109815731A (en) * | 2018-12-29 | 2019-05-28 | 深圳云天励飞技术有限公司 | Permission processing method and relevant device |
| CN110233982A (en) * | 2018-03-06 | 2019-09-13 | 北京视联动力国际信息技术有限公司 | A kind of monitoring method and device based on view networking |
-
2020
- 2020-03-09 CN CN202010155788.9A patent/CN111491188A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105429933A (en) * | 2014-09-19 | 2016-03-23 | 中国电信股份有限公司 | Access method of network equipment in local area network, access equipment and system |
| CN105100708A (en) * | 2015-06-26 | 2015-11-25 | 小米科技有限责任公司 | Request processing method and device |
| CN105787342A (en) * | 2016-02-26 | 2016-07-20 | 北京小米移动软件有限公司 | Method and device for executing target function |
| KR20190007125A (en) * | 2017-07-11 | 2019-01-22 | 주식회사 아이앤나 | Method for Providing Observation Camera Image |
| CN110233982A (en) * | 2018-03-06 | 2019-09-13 | 北京视联动力国际信息技术有限公司 | A kind of monitoring method and device based on view networking |
| CN109815731A (en) * | 2018-12-29 | 2019-05-28 | 深圳云天励飞技术有限公司 | Permission processing method and relevant device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5144556A (en) | Method and system for retaining access to deleted documents in a data processing system | |
| CN108768948B (en) | Access right management method, server and computer readable storage medium | |
| CN108809775A (en) | The method and apparatus that smart machine is controlled | |
| US9645928B2 (en) | Distributed directory service for in-memory compression unit home location | |
| CN110555015B (en) | Database entity management method and device, electronic equipment and storage medium | |
| RU2146077C1 (en) | System for controlling source position register and method for controlling database for mobile communication network | |
| CN105512279A (en) | Metadata access method, related equipment and system | |
| CN110909373A (en) | Access control method, device, system and storage medium | |
| EP3355549B1 (en) | Data storage method, nonvolatile computer storage medium, electronic equipment, open capability entity, and base station | |
| US20200359220A1 (en) | Network Access Control Method, Apparatus, and Device | |
| CN111984949B (en) | Authentication method, device, electronic equipment and storage medium | |
| CN108154024B (en) | Data retrieval method and device and electronic equipment | |
| CN111491188A (en) | Authority management method, routing device and system | |
| CN112328549A (en) | Small file storage method, electronic device and storage medium | |
| US10327133B2 (en) | Making subscriber data addressable as a device in a mobile data network | |
| CN106407470A (en) | Fingerprint sharing method, terminal and server | |
| CN105743922A (en) | Method, device and system for inter-domain communication | |
| CN112784161B (en) | Information processing method, device, medium and electronic device | |
| CN111475535B (en) | Data storage and access method and device | |
| CN115473895A (en) | Digital object warehouse node consensus group division method and device under ubiquitous environment | |
| CN114201496A (en) | Data updating method and device, electronic equipment, system and storage medium | |
| CN113905252A (en) | Data storage method and device for live broadcast room, electronic equipment and storage medium | |
| US11343253B2 (en) | Access control for private channels in a channel-based discussion system | |
| US6298346B1 (en) | Method and apparatus for supporting cooperative activity | |
| CN113032745A (en) | Authority management apparatus, authority management method and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200804 |