CN103973691A - Resource access method and resource access device - Google Patents
Resource access method and resource access device Download PDFInfo
- Publication number
- CN103973691A CN103973691A CN201410196889.5A CN201410196889A CN103973691A CN 103973691 A CN103973691 A CN 103973691A CN 201410196889 A CN201410196889 A CN 201410196889A CN 103973691 A CN103973691 A CN 103973691A
- Authority
- CN
- China
- Prior art keywords
- queue
- requesting party
- access
- shared resource
- authentication information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
The embodiment of the invention relates to the technical field of shared resources and discloses a resource access method and a resource access device. The method comprises the following steps that response to access to the shared resources fails, and first authentication information for acquiring the shared resources is acquired; second the authentication information of the shared resources is sent according to the preset strategy and at least one received access request to the shared resources. According to the resource access method and the resource access device, each user failed in access and acquiring the authentication information of the shared resources sends the authentication information to other request parties having access to the shared resources according to the preset strategy so that the shared resources can be effectively managed. In addition, a management mechanism is simple.
Description
Technical field
The application relates to shared resource management domain, relates in particular to a kind of resource access method and resource access device.
Background technology
In actual work and life, often there are a plurality of users to access the application scenarios of same shared resource, such as using shared account to log in search engine, a plurality of users obtain service.Yet, because some resource is restricted to the number of users of access, often because there is no effective resource access scheme, occur that calling party exceeds blocking up that the quantity of regulation causes, or the access conflict phenomenon that causes logged-in user to be forced to publish.
Summary of the invention
The application's object is: a kind of resource access method and the resource access device that can realize effective management of shared resource access is provided.
First aspect, the embodiment of the present invention provides a kind of resource access method, and described method comprises:
In response to the failure of access shared resource, obtain the first authentication information of described shared resource;
According at least one access request to described shared resource receiving, according to preset strategy, send the second authentication information of described shared resource.
In conjunction with first aspect, in the possible implementation of the first, described in response to the failure of access shared resource, the first authentication information that obtains described shared resource comprises:
In response to the failure of access shared resource, send the access request to described shared resource;
Receive described the first authentication information.
In conjunction with the possible implementation of the first of first aspect or first aspect, in the possible implementation of the second, described preset strategy is:
Target requesting party in the wait access queue of described shared resource sends described the second authentication information.
In conjunction with the possible implementation of the second of first aspect, in the third possible implementation, at least one access request to described shared resource that described basis receives, the second authentication information that sends described shared resource according to preset strategy comprises:
Determine described wait access queue.
In conjunction with the third possible implementation of first aspect, in the 4th kind of possible implementation, at least one access request to described shared resource that described basis receives, the second authentication information that sends described shared resource according to preset strategy comprises:
Determine described target requesting party.
In conjunction with the 4th kind of possible implementation of first aspect, in the 5th kind of possible implementation, in described definite described wait access queue:
According to the time sequencing of described at least one access request, determine described wait access queue;
In described definite described target requesting party:
According to time sequencing, determine described target requesting party.
In conjunction with the 5th kind of possible implementation of first aspect, in the 6th kind of possible implementation, in described definite described wait access queue:
According to the time of described at least one access request, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party.
In conjunction with the 4th kind of possible implementation of first aspect, in the 7th kind of possible implementation, in described definite described wait access queue:
According to requesting party's priority, determine described wait access queue;
In described definite described target requesting party:
According to the priority of described request side, determine described target requesting party.
In conjunction with the 7th kind of possible implementation of first aspect, in the 8th kind of possible implementation, in described definite described wait access queue:
According to requesting party's priority from high to low, from head of the queue to tail of the queue, be arranged in order requesting party.
In conjunction with the 4th kind of possible implementation of first aspect, in the 9th kind of possible implementation, in described definite described wait access queue:
According to the time sequencing of described at least one access request and requesting party's priority, determine described wait access queue;
In described definite described target requesting party:
According to the time sequencing of described at least one access request and requesting party's priority, determine described target requesting party.
In conjunction with the 9th kind of possible implementation of first aspect, in the tenth kind of possible implementation, in described definite described wait access queue:
According to the time of described at least one access request, from arriving first, be arranged in order requesting party from head of the queue to tail of the queue, the height according to priority of the requesting party in the same time period is arranged from front to back.
In conjunction with the 9th kind of possible implementation of first aspect, in the 11 kind of possible implementation, in described definite described wait access queue:
According to requesting party's priority from high to low, be arranged in order requesting party from head of the queue to tail of the queue, the requesting party of same priority arranges from front to back according to the time order and function of access request.
In conjunction with any in the 5th to the 11 kind of possible implementation of first aspect, in the 12 kind of possible implementation, describedly determine in described target requesting party:
Determine and wait for that the requesting party of access queue head of the queue is described target requesting party.
In conjunction with any in the 4th to the 12 kind of possible implementation of first aspect, in the 13 kind of possible implementation, described at least one access request to described shared resource receiving, sends in described the second authentication information according to preset strategy:
In response to definite described target requesting party, send described the second authentication information.
In conjunction with any in the 3rd to the 13 kind of possible implementation of first aspect, in the 14 kind of possible implementation, described method also comprises:
Upgrade described wait access queue.
In conjunction with the 14 kind of possible implementation of first aspect, in the 15 kind of possible implementation, in the described wait access queue of described renewal:
In response to receiving access request, upgrade described wait access queue.
In conjunction with the 15 kind of possible implementation of first aspect, in the 16 kind of possible implementation, described method also comprises:
Receive and cancel the message of waiting for.
In conjunction with the 16 kind of possible implementation of first aspect, in the 17 kind of possible implementation, in the described wait access queue of described renewal:
In response to receiving described in the information updating of cancel waiting for, wait for access queue.
In conjunction with any in second to the 17 kind of possible implementation of first aspect, in the 18 kind of possible implementation, described method also comprises:
In response to the renewal of described wait access queue, broadcast described wait access queue.
In conjunction with any in second to the 17 kind of possible implementation of first aspect, in the 19 kind of possible implementation, described method also comprises:
Described in periodic broadcast, wait for access queue.
In conjunction with above-mentioned any possible implementation of first aspect or first aspect, in the 20 kind of possible implementation, described method also comprises:
Determine described the second authentication information.
In conjunction with the 20 kind of possible implementation of first aspect, in the 21 kind of possible implementation, described the second authentication information is identical with described the first authentication information.
In conjunction with the 20 kind of possible implementation of first aspect, in the 22 kind of possible implementation, the priority of described the second authentication information is lower than the priority of described the first authentication information.
Second aspect, the embodiment of the present invention provides a kind of resource access device, and described device comprises:
One acquisition module, in response to the failure of access shared resource, obtains the first authentication information of described shared resource;
One administration module, for according at least one access request to described shared resource receiving, sends the second authentication information of described shared resource according to preset strategy.
In conjunction with second aspect, in the possible implementation of the first, described acquisition module comprises:
One transmitting element, in response to the failure of access shared resource, sends the access request to described shared resource;
One receiving element, for receiving described the first authentication information.
In conjunction with the possible implementation of the first of second aspect or second aspect, in the possible implementation of the second, described administration module comprises:
One first determining unit, for determining the wait access queue of described shared resource.
In conjunction with the possible implementation of the second of second aspect, in the third possible implementation, described administration module comprises:
One second determining unit, for determining target requesting party.
In conjunction with the third possible implementation of second aspect, in the 4th kind of possible implementation, described the first determining unit is determined described wait access queue according to the time sequencing of described at least one access request;
Described the second determining unit is determined described target requesting party according to time sequencing.
In conjunction with the 4th kind of possible implementation of second aspect, in the 5th kind of possible implementation, described the first determining unit from arriving first, is arranged in order requesting party according to the time of described at least one access request from head of the queue to tail of the queue.
In conjunction with the third possible implementation of second aspect, in the 6th kind of possible implementation, described the first determining unit is determined described wait access queue according to requesting party's priority;
Described the second determining unit is determined described target requesting party according to the priority of described request side.
In conjunction with the 6th kind of possible implementation of second aspect, in the 7th kind of possible implementation, described the first determining unit according to requesting party's priority from high to low, is arranged in order requesting party from head of the queue to tail of the queue.
In conjunction with the third possible implementation of second aspect, in the 8th kind of possible implementation, described the first determining unit is determined described wait access queue according to the time sequencing of described at least one access request and requesting party's priority;
Described the second determining unit is determined described target requesting party according to the time sequencing of described at least one access request and requesting party's priority.
The 8th kind of possible implementation in conjunction with second aspect, in the 9th kind of possible implementation, described the first determining unit according to the time of described at least one access request from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party, the height according to priority of the requesting party in the same time period is arranged from front to back.
The 8th kind of possible implementation in conjunction with second aspect, in the tenth kind of possible implementation, described the first determining unit according to requesting party's priority from high to low, from head of the queue to tail of the queue, be arranged in order requesting party, the requesting party of same priority arranges from front to back according to the time order and function of access request.
In conjunction with any in the 4th to the tenth kind of possible implementation of second aspect, in the 11 kind of possible implementation, described the second determining unit is determined and is waited for that the requesting party of access queue head of the queue is described target requesting party.
In conjunction with any in the 3rd to the 11 kind of possible implementation of second aspect, in the 12 kind of possible implementation, described administration module sends described the second authentication information in response to definite described target requesting party.
In conjunction with any in second to the 12 kind of possible implementation of second aspect, in the 13 kind of possible implementation, described device also comprises:
One update module, for upgrading described wait access queue.
In conjunction with the 13 kind of possible implementation of second aspect, in the 14 kind of possible implementation, described update module is upgraded described wait access queue in response to receiving access request.
In conjunction with the 14 kind of possible implementation of second aspect, in the 15 kind of possible implementation, described device also comprises:
One receiver module, cancels for receiving the message of waiting for.
In conjunction with the 14 kind of possible implementation of second aspect, in the 16 kind of possible implementation, the response of described update module receives to cancel described in the information updating of waiting for waits for access queue.
In conjunction with any in first to the 16 kind of possible implementation of second aspect, in the 17 kind of possible implementation, described device also comprises:
One first broadcast module, for broadcasting described wait access queue in response to the renewal of described wait access queue.
In conjunction with any in first to the 16 kind of possible implementation of second aspect, in the 18 kind of possible implementation, described device also comprises:
One second broadcast module, waits for access queue for described in periodic broadcast.
In conjunction with above-mentioned any possible implementation of second aspect or second aspect, in the 19 kind of possible implementation, described device also comprises:
One determination module, for determining described the second authentication information.
The method of the embodiment of the present invention and device are by sending authentication information effectively managing shared resource according to preset strategy to the requesting party of other access shared resources by each access failure and the user that gets the authentication information of shared resource, and administrative mechanism is simple.
Accompanying drawing explanation
Fig. 1 is the flow chart of a kind of resource access method of the embodiment of the present invention;
Fig. 2 is the structured flowchart of a kind of resource access device of this aspect embodiment;
Fig. 3 is the structured flowchart of a kind of possible implementation of a kind of resource access device of this aspect embodiment;
Fig. 4 is the structured flowchart of the possible implementation of a kind of another kind of resource access device of this aspect embodiment;
Fig. 5 is the structured flowchart of the third possible implementation of a kind of resource access device of this aspect embodiment;
Fig. 6 is the structured flowchart of the 4th kind of possible implementation of a kind of resource access device of this aspect embodiment;
Fig. 7 is the structured flowchart of the 5th kind of possible implementation of a kind of resource access device of this aspect embodiment.
Embodiment
Below in conjunction with accompanying drawing (in some accompanying drawings, identical label represents identical element) and embodiment, the application's embodiment is described in further detail.Following examples are used for illustrating the application, but are not used for limiting the application's scope.
It will be understood by those skilled in the art that the terms such as " first " in the application, " second ", only for distinguishing different step, equipment or module etc., neither represent any particular technology implication, also do not represent the inevitable logical order between them.
In addition, " shared resource " in various embodiments of the present invention refers to can be Network Based by the resource of an above task access (use), for example, database, application program, website, file, memory space etc., preferably limit the Concurrency Access amount of this type of shared resource.The resource access method of the embodiment of the present invention can be moved by the arbitrary equipment that can access shared resource by the mode such as wired or wireless, for example, and mobile phone, notebook computer, palmtop PC etc.User can directly or indirectly access shared resource by described equipment.
As shown in Figure 1, the resource access method of an embodiment of the present invention comprises:
S110. in response to the failure of access shared resource, obtain the first authentication information of described shared resource.
In the method for the embodiment of the present invention, when user wants to access shared resource, can (for example directly or use default authentication information, password) access described shared resource, if access described shared resource failure, send the mode to the access request of described shared resource, and receive the first authentication information.Described access request can send by the form of broadcast, the also orientable management equipment that is sent to described shared resource, for example, server apparatus, the current equipment that takies described shared resource etc.In this each embodiment, " authentication information " for accessing described shared resource, includes but not limited to the information that access code, password etc. arbitrarily can authentication-access authorities.And the first authentication information is for having the authentication information of the described shared resource authority of access under pre-conditioned, described pre-conditioned be that described shared resource is unoccupied.
S120. get after the first authentication information of described shared resource, according at least one access request to described shared resource receiving, according to preset strategy, send the second authentication information of described shared resource.
In the method for the embodiment of the present invention, access shared resource failure the user who gets the authentication information of described shared resource become the current leading subscriber of described shared resource, its equipment using is called management equipment in the method for the embodiment of the present invention, leading subscriber can be described shared resource setting the second authentication information by described management equipment, or obtains described the second authentication information from for example shared resource server or the current equipment that takies described shared resource.
Leading subscriber sends described the second authentication information according to preset strategy to the requesting party of shared resource described in other request access, and the requesting party who makes to receive described the second authentication information obtains the authority of the described shared resource of access.Described preset strategy can be formulated or be preset by leading subscriber, makes every effort to, when effectively ensureing the current user's who takies described shared resource access, take into account other requesting parties that treat liberally described shared resource.Thereby the Concurrency Access amount of avoiding described shared resource exceeds blocking up that the quantity of regulation causes, or the leading subscriber that malicious user preempting resources causes is forced to publish.
To sum up, the method of the embodiment of the present invention is by sending authentication information effectively managing shared resource according to preset strategy to the requesting party of other access shared resources by each access failure and the user that gets the authentication information of shared resource, and administrative mechanism is simple.
The method of the embodiment of the present invention also comprises:
S130. determine described the second authentication information.
Wherein, described the second authentication information can be identical with described the first authentication information, also can be different.For the better access of management to described shared resource, in a kind of possible implementation, can be by the priority setting of described the second authentication information the priority lower than described the first authentication information, thereby prevent that the requesting party who receives described the second authentication information from using described the second authentication information to access described shared resource when leading subscriber is accessed described shared resource or before leading subscriber is accessed described shared resource, causes leading subscriber cannot access or be forced to and publish.In various embodiments of the present invention, the different priorities of authentication information can embody in the following manner: the authentication information of each priority is only effective in special time period separately, within the time period early effectively, the authentication information of lower priority is effective within the more late time period for the authentication information of higher priority; Or during a user uses the authentication information of higher priority to access described shared resource, other users cannot use the authentication information of lower priority to access described shared resource.
In a kind of possible implementation, described preset strategy is: the target requesting party in the wait access queue of described shared resource sends described the second authentication information.Described wait access queue is for according to setting up the access request of described shared resource, the requesting party's of the described shared resource to be visited information such as wherein comprised, for example, and requesting party's identification information, time of request access etc.Correspondingly, step S120 can further comprise:
S121. determine described wait access queue.
In the method for the embodiment of the present invention, determine and wait for that access queue can comprise that leading subscriber for example, obtains the situation of the wait access queue of setting up and/or upgrading from the outside (managing the server of described shared resource) of management equipment, be also included in the local foundation of management equipment and/or upgrade the situation of waiting for access queue.
S122. determine described at least one target requesting party.
After determining described wait access queue, leading subscriber is determined target requesting party according to certain rule from described queue.
In the method for the embodiment of the present invention, determine that the rule of described wait access queue can comprise multiple:
Determine described wait access queue according to the time of described at least one access request.For example, according to the time of described at least one access request, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party, also, often receive a new access request, corresponding requesting party is come to the tail of the queue of described wait access queue.Now, in step S122, according to time sequencing, determine described at least one target requesting party.
According to requesting party's priority, determine described wait access queue.For example, according to requesting party's priority from high to low, from head of the queue to tail of the queue, be arranged in order requesting party, also, the minimum requesting party of priority come to the tail of the queue of described wait access queue.Requesting party's priority can determine by leading subscriber, or sets in advance, and can judge requesting party's priority, or directly comprised corresponding precedence information in access request according to requesting party's identification information.Now, in step S122, according to requesting party's priority, determine described target requesting party.
According to the time sequencing of described at least one access request and requesting party's priority, determine described wait access queue.For example, according to the time of described at least one access request, from arriving first, be arranged in order requesting party from head of the queue to tail of the queue, the height according to priority of the requesting party in the same time period is arranged from front to back.Or, according to requesting party's priority from high to low, from head of the queue to tail of the queue, being arranged in order requesting party, the requesting party of same priority arranges from front to back according to the time order and function of access request.Now, at step S122, consider the described time sequencing of at least one access request and requesting party's priority is determined described target requesting party, when the requesting party higher to priority sends the second authentication information, can inform that its access request to access request requesting party formerly responds.
In the method for the embodiment of the present invention, step S122 determines that described target requesting party's rule also can have multiple.For example, according to the head of the queue of described wait access queue (tail of the queue) to the order of tail of the queue (head of the queue), choose request time at first a requesting party of (afterwards) and/or priority the highest (low) be target requesting party.Also for example, being chosen in special time period a requesting party of shared resource described in request access is target requesting party; Or choosing a requesting party with certain priority is target requesting party.
Leading subscriber, in response to the arrival of the time point of default time span/default, is determined described target requesting party according to the whole access request that receive.Also can be in response to the access request that receives certain specific requesting party, determine or redefine described target requesting party.For example, receive after the access request of the requesting party with higher priority, the requesting party who redefines described higher priority is target requesting party.
In addition, in a kind of possible implementation, after determining described target requesting party, can use the first authentication information to access described shared resource in response to leading subscriber, send described the second authentication information, the requesting party who receives described the second authentication information becomes leading subscriber.In the possible implementation of another kind, can send described the second authentication information in response to definite described target requesting party.For example, after determining described target requesting party, immediately described the second authentication information is sent to described target requesting party, now, leading subscriber and the requesting party who receives described the second authentication information all continue to wait for and can access described shared resource, the requesting party who receives the second authentication information becomes leading subscriber, the two all the current user who takies described shared resource of conscious wait stop using and access successively more described shared resource after described shared resource; Or because of the restriction of the priority of authentication information, before described shared resource is not released, the two all cannot be accessed.
For specific requesting party (described specific requesting party may have the higher or limit priority of the described shared resource of access), no matter whether determined described target requesting party, leading subscriber can send the authentication information of limit priority immediately in response to the access request that receives described specific requesting party to described specific requesting party, make described specific requesting party can at once access described shared resource.
In addition, do not determining that in target requesting party's time period, leading subscriber need to respond the message receiving and safeguard described wait access list.Correspondingly, the method for the embodiment of the present invention also comprises:
S130. upgrade described wait access queue.
In the method for the embodiment of the present invention, the user of shared resource joins described wait access queue by sending the mode of access request described in request access; User in described wait access queue also can be sent and be cancelled the behavior that the message of waiting for informs that its cancellation of leading subscriber is waited for by active.The message that leading subscriber is waited in response to the access request receiving, cancellation etc. is upgraded described wait access queue.Correspondingly, the method for the embodiment of the present invention can comprise respectively the step that receives described at least one access request and cancel the message of waiting for.
In order to provide relatively good user to experience to user (especially etc. user to be visited), the method for the embodiment of the present invention also comprises:
S140. described in periodic broadcast, wait for access queue.And/or
S140 '. in response to the renewal of described wait access queue, broadcast described wait access queue.
By broadcast described wait access queue, can allow want or etc. the user of described shared resource to be visited understand the situation that takies and the wait situation of described shared resource, thereby provide the reference of further selection for each user.
It will be appreciated by those skilled in the art that, in the said method of the application's embodiment, the sequence number size of each step does not also mean that the priority of execution sequence, the execution sequence of each step should be definite with its function and internal logic, and should not form any restriction to the implementation process of the application's embodiment.
The embodiment of the present invention also provides a kind of resource access device.Described device be for accessing the arbitrary equipment of shared resource by the mode such as wired or wireless, for example, and mobile phone, notebook computer, palmtop PC etc.User can directly or indirectly access shared resource by described equipment.As shown in Figure 2, the resource access device 200 of the embodiment of the present invention comprises:
Acquisition module 210, in response to the failure of access shared resource, obtains the first authentication information of described shared resource.
When user wants to access shared resource, can (for example directly or use default authentication information, password) access described shared resource, use the device of the embodiment of the present invention, if access described shared resource failure, by the mode of transmitting element 211 transmissions to the access request of described shared resource of acquisition module 210, and by receiving element 212 reception the first authentication informations.Transmitting element 211 can send described access request by the form of broadcast, the also orientable management equipment that is sent to described shared resource, for example, server apparatus, the current equipment that takies described shared resource etc.
Administration module 220, for after getting the first authentication information of described shared resource, at least one access request to described shared resource receiving according to acquisition module 210, sends the second authentication information of described shared resource according to preset strategy.
In the device of the embodiment of the present invention, access shared resource failure the user who gets the authentication information of described shared resource become the current leading subscriber of described shared resource, it uses the device (being called management equipment) of the embodiment of the present invention to manage described shared resource, leading subscriber can be described shared resource setting the second authentication information by described device 200, or obtains described the second authentication information from for example shared resource server or the current such external equipment of equipment that takies described shared resource.Correspondingly, the device 200 of the embodiment of the present invention also comprises the functional module that can realize administration module 220 and external device communication.
Administration module 220 sends described the second authentication information according to preset strategy to the requesting party of shared resource described in other request access, and the requesting party who makes to receive described the second authentication information obtains the authority of the described shared resource of access.Described preset strategy can be formulated or be preset by leading subscriber, makes every effort to, when effectively ensureing the current user's who takies described shared resource access, take into account other requesting parties that treat liberally described shared resource.Thereby the Concurrency Access amount of avoiding described shared resource exceeds blocking up that the quantity of regulation causes, or the leading subscriber that malicious user preempting resources causes is forced to publish.
To sum up, the device of the embodiment of the present invention is by sending authentication information effectively managing shared resource according to preset strategy to the requesting party of other access shared resources by each access failure and the user that gets the authentication information of shared resource, and administrative mechanism is simple.
As shown in Figure 3, the device 200 of the embodiment of the present invention also comprises:
Determination module 230, for determining described the second authentication information.
Wherein, described the second authentication information can be identical with described the first authentication information, also can be different.For the better access of management to described shared resource, in a kind of possible implementation, can be by the priority setting of described the second authentication information the priority lower than described the first authentication information, thereby prevent that the requesting party who receives described the second authentication information from using described the second authentication information to access described shared resource during leading subscriber is accessed described shared resource or before leading subscriber is accessed described shared resource, causes leading subscriber to be forced to publish maybe and cannot access.
In a kind of possible implementation, described preset strategy is: the target requesting party in the wait access queue of described shared resource sends described the second authentication information.Described wait access queue is for according to setting up the access request of described shared resource, the requesting party's of the described shared resource to be visited information such as wherein comprised, for example, and requesting party's identification information, time of request access etc.Correspondingly, as shown in Figure 4, administration module 220 can further comprise:
The first determining unit 221, for determining described wait access queue.
In the device of the embodiment of the present invention, determine and wait for that access queue can comprise that the outside (for example managing the server of described shared resource) from management equipment obtains the situation of the wait access queue of setting up and/or upgrading, be also included in the local foundation of management equipment and/or upgrade the situation of waiting for access queue.
The second determining unit 222, for determining described at least one target requesting party.
After determining described wait access queue, leading subscriber is determined target requesting party according to certain rule by the second determining unit 222 from described queue.
In the device of the embodiment of the present invention, the second determining unit 222 determines that the rule of described wait access queue can comprise multiple:
Determine described wait access queue according to the time of described at least one access request.For example, according to the time of described at least one access request, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party, also, often receive a new access request, corresponding requesting party is come to the tail of the queue of described wait access queue.Now, the second determining unit 222 is determined described at least one target requesting party according to time sequencing.
According to requesting party's priority, determine described wait access queue.For example, according to requesting party's priority from high to low, from head of the queue to tail of the queue, be arranged in order requesting party, also, the minimum requesting party of priority come to the tail of the queue of described wait access queue.Requesting party's priority can determine by leading subscriber, or sets in advance, and can judge requesting party's priority, or directly comprised corresponding precedence information in access request according to requesting party's identification information.Now, the second determining unit 222 is determined described target requesting party according to requesting party's priority.
According to the time sequencing of described at least one access request and requesting party's priority, determine described wait access queue.For example, according to the time of described at least one access request, from arriving first, be arranged in order requesting party from head of the queue to tail of the queue, the height according to priority of the requesting party in the same time period is arranged from front to back.Or, according to requesting party's priority from high to low, from head of the queue to tail of the queue, being arranged in order requesting party, the requesting party of same priority arranges from front to back according to the time order and function of access request.Now, the second determining unit 222 considers the described time sequencing of at least one access request and requesting party's priority is determined described target requesting party.Administration module 220, when the requesting party higher to priority sends the second authentication information, can inform that its access request to access request requesting party formerly responds
In the device of the embodiment of the present invention, the second determining unit 222 determines that described target requesting party's rule also can have multiple.For example, according to the head of the queue of described wait access queue (tail of the queue) to the order of tail of the queue (head of the queue), choose request time at first a requesting party of (afterwards) and/or priority the highest (low) be target requesting party.Also for example, being chosen in special time period a requesting party of shared resource described in request access is target requesting party; Or choosing a requesting party with certain priority is target requesting party.
In response to the arrival of the time point of default time span/default, the second determining unit 222 is determined described target requesting party according to the whole access request that receive.Also can be in response to the access request that receives certain specific requesting party, determine or redefine described target requesting party.For example, receive after the access request of the requesting party with higher priority, the requesting party who redefines described higher priority is target requesting party.
In addition, in a kind of possible implementation, after the second determining unit 222 is determined described target requesting party, can be in response to using the first authentication information to access described shared resource, send described the second authentication information, the requesting party who receives described the second authentication information becomes leading subscriber.In the possible implementation of another kind, can send described the second authentication information in response to definite described target requesting party.For example, after determining described target requesting party, immediately described the second authentication information is sent to described target requesting party, now, leading subscriber and the requesting party who receives described the second authentication information all continue to wait for and can access described shared resource, the requesting party who receives the second authentication information becomes leading subscriber, the two all the current user who takies described shared resource of conscious wait stop using and access successively more described shared resource after described shared resource; Or because of the restriction of the priority of authentication information, before described shared resource is not released, the two all cannot be accessed.
For specific requesting party (described specific requesting party may have the higher or limit priority of the described shared resource of access), no matter whether determined described target requesting party, administration module 220 can send the authentication information of limit priority immediately in response to the access request that receives described specific requesting party to described specific requesting party, make described specific requesting party can at once access described shared resource.
In addition, do not determining that in target requesting party's time period, leading subscriber need to respond the message receiving and safeguard described wait access list.Correspondingly, as shown in Figure 5, the device 200 of the embodiment of the present invention also comprises:
Update module 240, for upgrading described wait access queue.
In the device of the embodiment of the present invention, the user of shared resource joins described wait access queue by sending the mode of access request described in request access; User in described wait access queue also can be sent and be cancelled the behavior that the message of waiting for informs that its cancellation of leading subscriber is waited for by active.The message that update module 240 is waited in response to the access request receiving, cancellation etc. is upgraded described wait access queue.Correspondingly, the device of the embodiment of the present invention can comprise respectively the receiver module 250 that receives described at least one access request and cancel the message of waiting for.
In order to provide relatively good user to experience to user (especially etc. user to be visited), as shown in Figure 6, the device of the embodiment of the present invention also comprises:
The first broadcast module 260, waits for access queue described in periodic broadcast.And/or
The second broadcast module 260 ', for broadcasting described wait access queue in response to the renewal of described wait access queue.
By broadcast described wait access queue, can allow want or etc. the user of described shared resource to be visited understand the situation that takies and the wait situation of described shared resource, thereby provide the reference of further selection for each user.
It should be noted that, above-mentioned each functional module of carrying out sending function in the device of the embodiment of the present invention can be same module, and the above-mentioned functions module of carrying out receiving function also can be same module, in this not restriction of conduct to the device of the embodiment of the present invention.
Below by instantiation, further illustrate method and the device of various embodiments of the present invention.
Example one
User's first is successfully used shared account access destination database unsuccessful by default password, uses method and the device of the embodiment of the present invention, and user's first broadcast access request also receives first password, becomes the leading subscriber of described shared account.When user's second is used the described shared account of default password login, will be apprised of and access unsuccessfully.Now, user's first will receive the access request of user's second, in response to the described access request receiving, set up and wait for access queue, user's first joins user's second in described access queue and to it and sends the second password, the priority of the second password is lower than first password, now, user's second becomes the leading subscriber of described shared account.User's first is used first password to use described shared account after receiving current accessed user and stop the message of access.Other leading subscribers by that analogy.
Example two
User's first is used shared account access destination database unsuccessful by default password, uses method and the device of the embodiment of the present invention, and user's first broadcast access request also receives first password, becomes the leading subscriber of described shared account.When user's second is used the described shared account of default password login, will be apprised of and access unsuccessfully.Now, user's first will receive the access request of user's second, in response to the described access request receiving, sets up and waits for access queue.During the first-class described database to be visited of user, it receives user third, user's fourth, user's penta access request successively,
And successively user's fourth, user third, user penta are added according to the priority to the tail of the queue of waiting for access queue.Access queue is waited in the every renewal of user's first, i.e. wait access queue after broadcast is upgraded, and user's second, user third, user's fourth, user penta all can be known the situation that takies of described shared account.User's second is initiatively cancelled and being waited for for some reason, and in response to this, user's first is again upgraded described access waiting list and broadcasted the queue after upgrading.User's first is after waiting a period of time of described database to be visited, user's fourth of determining described wait access queue head of the queue is target requesting party, the second password is sent to user's fourth and inform that user's fourth responds to user third request, user's fourth becomes the current leading subscriber of described account, and can first-selected user third send the target of " the second password " for it.When current accessed user stops accessing described database, user's first can be used first password to access described database, and other leading subscribers by that analogy.
Example three
In the situation of example one, user's first becomes the leading subscriber of described shared account and after definite described user's second is target requesting party, immediately the second password is sent to user's second.During the first-class described database to be visited of user, receive oneself access request of specific user, oneself is the limit priority user of described shared account for user, now, user's first is determined user, and oneself is target requesting party, and the password that sends limit priority to it, oneself becomes the current leading subscriber of described shared account user.User's first can notify or not notify user's second this change.
The structural representation of another resource access device 700 that Fig. 7 provides for this aspect embodiment, the application's specific embodiment does not limit the specific implementation of resource access 700.As shown in Figure 7, described resource access device 700 can comprise:
Processor (processor) 710, communication interface (Communications Interface) 720, memory (memory) 730 and communication bus 740.Wherein:
Processor 710, communication interface 720 and memory 730 complete mutual communication by communication bus 740.
Communication interface 720, for the net element communication with such as client etc.
Processor 710, for executive program 732, specifically can carry out the correlation step in said method embodiment.
Particularly, program 732 can comprise program code, and described program code comprises computer-managed instruction.
Processor 710 may be a central processor CPU, or specific integrated circuit ASIC (Application Specific Integrated Circuit), or is configured to implement one or more integrated circuits of the embodiment of the present application.
Memory 730, for depositing program 732.Memory 730 may comprise high-speed RAM memory, also may also comprise nonvolatile memory (non-volatile memory), for example at least one magnetic disc store.Program 732 specifically can be for making described display control unit 700 carry out following steps:
In response to the failure of access shared resource, obtain the first authentication information of described shared resource;
According at least one access request to described shared resource receiving, according to preset strategy, send the second authentication information of described shared resource.
In program 732, the specific implementation of each step can, referring to description corresponding in the corresponding steps in above-described embodiment and unit, be not repeated herein.Those skilled in the art can be well understood to, and for convenience and simplicity of description, the specific works process of the equipment of foregoing description and module, can describe with reference to the corresponding process in preceding method embodiment, does not repeat them here.
Those of ordinary skills can recognize, unit and the method step of each example of describing in conjunction with embodiment disclosed herein, can realize with the combination of electronic hardware or computer software and electronic hardware.These functions are carried out with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Professional and technical personnel can specifically should be used for realizing described function with distinct methods to each, but this realization should not thought and exceeds the application's scope.
If described function usings that the form of SFU software functional unit realizes and during as production marketing independently or use, can be stored in a computer read/write memory medium.Understanding based on such, the part that the application's technical scheme contributes to prior art in essence in other words or the part of described technical scheme can embody with the form of software product, described computer software product is stored in a storage medium, comprise that some instructions are with so that a computer equipment (can be personal computer, server, or the network equipment etc.) carry out all or part of step of method described in each embodiment of the application.And aforesaid storage medium comprises: USB flash disk, portable hard drive, read-only memory (ROM, Read-Only Memory), the various media that can be program code stored such as random access memory (RAM, Random Access Memory), magnetic disc or CD.
Above execution mode is only for illustrating the application; and the not restriction to the application; the those of ordinary skill in relevant technologies field; in the situation that do not depart from the application's spirit and scope; can also make a variety of changes and modification; therefore all technical schemes that are equal to also belong to the application's category, and the application's scope of patent protection should be defined by the claims.
Claims (43)
1. a resource access method, is characterized in that, described method comprises:
In response to the failure of access shared resource, obtain the first authentication information of described shared resource;
According at least one access request to described shared resource receiving, according to preset strategy, send the second authentication information of described shared resource.
2. method according to claim 1, is characterized in that, described in response to the failure of access shared resource, the first authentication information that obtains described shared resource comprises:
In response to the failure of access shared resource, send the access request to described shared resource;
Receive described the first authentication information.
3. method according to claim 1 and 2, is characterized in that, described preset strategy is:
Target requesting party in the wait access queue of described shared resource sends described the second authentication information.
4. method according to claim 3, is characterized in that, at least one access request to described shared resource that described basis receives, and the second authentication information that sends described shared resource according to preset strategy comprises:
Determine described wait access queue.
5. method according to claim 4, is characterized in that, at least one access request to described shared resource that described basis receives, and the second authentication information that sends described shared resource according to preset strategy comprises:
Determine described target requesting party.
6. method according to claim 5, is characterized in that, in described definite described wait access queue:
According to the time sequencing of described at least one access request, determine described wait access queue;
In described definite described target requesting party:
According to time sequencing, determine described target requesting party.
7. method according to claim 6, is characterized in that, in described definite described wait access queue:
According to the time of described at least one access request, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party.
8. method according to claim 5, is characterized in that, in described definite described wait access queue:
According to requesting party's priority, determine described wait access queue;
In described definite described target requesting party:
According to the priority of described request side, determine described target requesting party.
9. method according to claim 8, is characterized in that, in described definite described wait access queue:
According to requesting party's priority from high to low, from head of the queue to tail of the queue, be arranged in order requesting party.
10. method according to claim 5, is characterized in that, in described definite described wait access queue:
According to the time sequencing of described at least one access request and requesting party's priority, determine described wait access queue;
In described definite described target requesting party:
According to the time sequencing of described at least one access request and requesting party's priority, determine described target requesting party.
11. methods according to claim 10, is characterized in that, in described definite described wait access queue:
According to the time of described at least one access request, from arriving first, be arranged in order requesting party from head of the queue to tail of the queue, the height according to priority of the requesting party in the same time period is arranged from front to back.
12. methods according to claim 10, is characterized in that, in described definite described wait access queue:
According to requesting party's priority from high to low, be arranged in order requesting party from head of the queue to tail of the queue, the requesting party of same priority arranges from front to back according to the time order and function of access request.
13. according to the method described in any one in claim 6 to 12, it is characterized in that, in described definite described target requesting party:
Determine and wait for that the requesting party of access queue head of the queue is described target requesting party.
14. according to the method described in any one in claim 5 to 13, it is characterized in that, described at least one access request to described shared resource of receiving, according to preset strategy, send in described the second authentication information:
In response to definite described target requesting party, send described the second authentication information.
15. according to the method described in any one in claim 4 to 14, it is characterized in that, described method also comprises:
Upgrade described wait access queue.
16. methods according to claim 15, is characterized in that, in the described wait access queue of described renewal:
In response to receiving access request, upgrade described wait access queue.
17. methods according to claim 16, is characterized in that, described method also comprises:
Receive and cancel the message of waiting for.
18. methods according to claim 17, is characterized in that, in the described wait access queue of described renewal:
In response to receiving described in the information updating of cancel waiting for, wait for access queue.
19. according to the method described in any one in claim 3 to 18, it is characterized in that, described method also comprises:
In response to the renewal of described wait access queue, broadcast described wait access queue.
20. according to the method described in any one in claim 3 to 18, it is characterized in that, described method also comprises:
Described in periodic broadcast, wait for access queue.
21. according to the method described in any one in claim 1 to 20, it is characterized in that, described method also comprises:
Determine described the second authentication information.
22. methods according to claim 21, is characterized in that, described the second authentication information is identical with described the first authentication information.
23. methods according to claim 21, is characterized in that, the priority of described the second authentication information is lower than the priority of described the first authentication information.
24. 1 kinds of resource access devices, is characterized in that, described device comprises:
One acquisition module, in response to the failure of access shared resource, obtains the first authentication information of described shared resource;
One administration module, for according at least one access request to described shared resource receiving, sends the second authentication information of described shared resource according to preset strategy.
25. devices according to claim 24, is characterized in that, described acquisition module comprises:
One transmitting element, in response to the failure of access shared resource, sends the access request to described shared resource;
One receiving element, for receiving described the first authentication information.
26. according to the device described in claim 24 or 25, it is characterized in that, described administration module comprises:
One first determining unit, for determining the wait access queue of described shared resource.
27. devices according to claim 26, is characterized in that, described administration module comprises:
One second determining unit, for determining target requesting party.
28. devices according to claim 27, is characterized in that, described the first determining unit is determined described wait access queue according to the time sequencing of described at least one access request;
Described the second determining unit is determined described target requesting party according to time sequencing.
29. devices according to claim 28, is characterized in that, described the first determining unit from arriving first, is arranged in order requesting party according to the time of described at least one access request from head of the queue to tail of the queue.
30. devices according to claim 27, is characterized in that, described the first determining unit is determined described wait access queue according to requesting party's priority;
Described the second determining unit is determined described target requesting party according to the priority of described request side.
31. devices according to claim 30, is characterized in that, described the first determining unit according to requesting party's priority from high to low, is arranged in order requesting party from head of the queue to tail of the queue.
32. devices according to claim 27, is characterized in that, described the first determining unit is determined described wait access queue according to the time sequencing of described at least one access request and requesting party's priority;
Described the second determining unit is determined described target requesting party according to the time sequencing of described at least one access request and requesting party's priority.
33. devices according to claim 32, it is characterized in that, described the first determining unit from arriving first, is arranged in order requesting party according to the time of described at least one access request from head of the queue to tail of the queue, and the height according to priority of the requesting party in the same time period is arranged from front to back.
34. devices according to claim 32, it is characterized in that, described the first determining unit according to requesting party's priority from high to low, is arranged in order requesting party from head of the queue to tail of the queue, and the requesting party of same priority arranges from front to back according to the time order and function of access request.
35. according to the device described in any one in claim 28 to 34, it is characterized in that, described the second determining unit determines that the requesting party of wait access queue head of the queue is described target requesting party.
36. according to the device described in any one in claim 27 to 35, it is characterized in that, described administration module sends described the second authentication information in response to definite described target requesting party.
37. according to the device described in any one in claim 26 to 36, it is characterized in that, described device also comprises:
One update module, for upgrading described wait access queue.
38. according to the device described in claim 37, it is characterized in that, described update module is upgraded described wait access queue in response to receiving access request.
39. according to the device described in claim 38, it is characterized in that, described device also comprises:
One receiver module, cancels for receiving the message of waiting for.
40. according to the device described in claim 38, it is characterized in that, the response of described update module receives to cancel described in the information updating of waiting for waits for access queue.
41. according to the device described in any one in claim 25 to 40, it is characterized in that, described device also comprises:
One first broadcast module, for broadcasting described wait access queue in response to the renewal of described wait access queue.
42. according to the device described in any one in claim 25 to 40, it is characterized in that, described device also comprises:
One second broadcast module, waits for access queue for described in periodic broadcast.
43. according to the device described in any one in claim 24 to 42, it is characterized in that, described device also comprises:
One determination module, for determining described the second authentication information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410196889.5A CN103973691B (en) | 2014-05-09 | 2014-05-09 | Resource access method and resource access device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410196889.5A CN103973691B (en) | 2014-05-09 | 2014-05-09 | Resource access method and resource access device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103973691A true CN103973691A (en) | 2014-08-06 |
| CN103973691B CN103973691B (en) | 2018-02-02 |
Family
ID=51242737
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410196889.5A Active CN103973691B (en) | 2014-05-09 | 2014-05-09 | Resource access method and resource access device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103973691B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105204928A (en) * | 2015-10-30 | 2015-12-30 | 上海斐讯数据通信技术有限公司 | Shared resource access method and system |
| CN105471881A (en) * | 2015-12-07 | 2016-04-06 | 北京奇虎科技有限公司 | Method, device and system for locking and unlocking requests |
| CN107066324A (en) * | 2017-03-08 | 2017-08-18 | 广东欧珀移动通信有限公司 | A kind of control method and equipment of finger prints processing resource |
| CN109391588A (en) * | 2017-08-04 | 2019-02-26 | 北京国双科技有限公司 | Request processing method and device |
| CN109587183A (en) * | 2017-09-28 | 2019-04-05 | 北京国双科技有限公司 | Request processing method and device |
| US11206360B2 (en) | 2017-03-09 | 2021-12-21 | Shenzhen Heytap Technology Corp., Ltd. | Exposure control method for obtaining HDR image, related exposure control device and electronic device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101247338A (en) * | 2008-03-18 | 2008-08-20 | 宇龙计算机通信科技(深圳)有限公司 | Authorization method and system for mutual accesses to shared data between mobile terminals |
| US20100319068A1 (en) * | 2007-08-27 | 2010-12-16 | Nec Europe Ltd | Method and system for performing delegation of resources |
| CN102546534A (en) * | 2010-12-15 | 2012-07-04 | 上海杉达学院 | Auto-distributive system for access permissions |
| CN102611686A (en) * | 2011-12-19 | 2012-07-25 | 无锡华御信息技术有限公司 | Shared file authority control method |
| CN102986190A (en) * | 2010-07-08 | 2013-03-20 | 国际商业机器公司 | Resource access management |
-
2014
- 2014-05-09 CN CN201410196889.5A patent/CN103973691B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100319068A1 (en) * | 2007-08-27 | 2010-12-16 | Nec Europe Ltd | Method and system for performing delegation of resources |
| CN101247338A (en) * | 2008-03-18 | 2008-08-20 | 宇龙计算机通信科技(深圳)有限公司 | Authorization method and system for mutual accesses to shared data between mobile terminals |
| CN102986190A (en) * | 2010-07-08 | 2013-03-20 | 国际商业机器公司 | Resource access management |
| CN102546534A (en) * | 2010-12-15 | 2012-07-04 | 上海杉达学院 | Auto-distributive system for access permissions |
| CN102611686A (en) * | 2011-12-19 | 2012-07-25 | 无锡华御信息技术有限公司 | Shared file authority control method |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105204928A (en) * | 2015-10-30 | 2015-12-30 | 上海斐讯数据通信技术有限公司 | Shared resource access method and system |
| CN105471881A (en) * | 2015-12-07 | 2016-04-06 | 北京奇虎科技有限公司 | Method, device and system for locking and unlocking requests |
| CN107066324A (en) * | 2017-03-08 | 2017-08-18 | 广东欧珀移动通信有限公司 | A kind of control method and equipment of finger prints processing resource |
| WO2018161543A1 (en) * | 2017-03-08 | 2018-09-13 | 广东欧珀移动通信有限公司 | Method and device for controlling fingerprint processing resources |
| US10963308B2 (en) | 2017-03-08 | 2021-03-30 | Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Method for controlling fingerprint processing resources, terminal, and computer-readable storage medium |
| US11206360B2 (en) | 2017-03-09 | 2021-12-21 | Shenzhen Heytap Technology Corp., Ltd. | Exposure control method for obtaining HDR image, related exposure control device and electronic device |
| CN109391588A (en) * | 2017-08-04 | 2019-02-26 | 北京国双科技有限公司 | Request processing method and device |
| CN109391588B (en) * | 2017-08-04 | 2021-03-12 | 北京国双科技有限公司 | Request processing method and device |
| CN109587183A (en) * | 2017-09-28 | 2019-04-05 | 北京国双科技有限公司 | Request processing method and device |
| CN109587183B (en) * | 2017-09-28 | 2021-06-29 | 北京国双科技有限公司 | Request processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103973691B (en) | 2018-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10638345B2 (en) | Visual privacy systems for enterprise mobility management | |
| CN103973691A (en) | Resource access method and resource access device | |
| JP5937103B2 (en) | Flexible policy-based network decision making | |
| US8656016B1 (en) | Managing application execution and data access on a device | |
| US20160019486A1 (en) | Resource Releasing Method, Apparatus, and System | |
| WO2017128728A1 (en) | Service network processing method, apparatus, and system | |
| JP2011526012A (en) | Wireless communication device with deterministic control of foreground access of user interface | |
| WO2015191964A1 (en) | Enforcing policies based on information received from external systems | |
| KR20130126601A (en) | Unified policy over heterogenous device types | |
| US10425475B2 (en) | Distributed data management | |
| US11592953B2 (en) | Enterprise workspace notifications service | |
| CA2829805C (en) | Managing application execution and data access on a device | |
| US9588983B2 (en) | Data classification for adaptive synchronization | |
| CN105453072A (en) | User centric data maintenance | |
| CN103973690A (en) | Resource access method and resource access device | |
| EP3011528B1 (en) | Wireless network and mac address device detection system and methods | |
| US10819842B2 (en) | Providing on-demand access to a restricted resource of a user device | |
| CN111078398A (en) | GPU (graphics processing Unit) distribution method, equipment and storage medium | |
| CN110677838A (en) | Service distribution method and device | |
| JP6289879B2 (en) | Communication terminal, communication method and program | |
| WO2013166306A1 (en) | Client based congestion management | |
| US9577967B2 (en) | Method and system for managing an informational site using a social networking application | |
| US20210124463A1 (en) | Enterprise workspace notifications service | |
| US20200235935A1 (en) | Data access control for edge devices using a cryptographic hash | |
| US11700261B1 (en) | Tool for management of a pool of authorizations to use software |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |