CN103973690A

CN103973690A - Resource access method and resource access device

Info

Publication number: CN103973690A
Application number: CN201410196498.3A
Authority: CN
Inventors: 刘嘉
Original assignee: Beijing Zhigu Ruituo Technology Services Co Ltd
Current assignee: Beijing Zhigu Ruituo Technology Services Co Ltd
Priority date: 2014-05-09
Filing date: 2014-05-09
Publication date: 2014-08-06
Anticipated expiration: 2034-05-09
Also published as: CN103973690B

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: having access to the shared resources; determining at least one piece of authentication information of the shared resources; sending at least one piece of authentication information according to a preset strategy and at least one received access request to the shared resource. According to the resource access method and the resource access device, first a user successfully having access to the shared resources sends the authentication information to other requesting parties having access to the shared resources according to the preset strategy so that the shared resources can be effectively managed.

Description

Resource access method and resource access device

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 multiple users to access the application scenarios of same shared resource, such as using shared account to log in search engine, multiple users obtain service.But, because some resource is restricted to the number of users of access, often occur because there is no effective resource access scheme that calling party exceeds blocking up that the quantity of regulation causes, or the access conflict phenomenon that causes logged-in user to be published by pressure.

Summary of the invention

The application's object is: resource access method and resource access device that a kind of effective management that can realize shared resource access is provided.

First aspect, the embodiment of the present invention provides a kind of resource access method, and described method comprises:

Access shared resource;

Determine at least one authentication information of described shared resource;

According at least one access request to described shared resource receiving, send described at least one authentication information according to preset strategy.

In conjunction with first aspect, in the possible implementation of the first, described access shared resource comprises:

Use the first authentication information to access described shared resource, the priority of described at least one authentication information is lower than the priority of 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 at least one authentication information of determining described shared resource comprises:

Described at least one authentication information is set.

In conjunction with the possible implementation of the first of first aspect or first aspect, in the third possible implementation, described at least one authentication information of determining described shared resource comprises:

Obtain described at least one authentication information.

In conjunction with above-mentioned any possible implementation of first aspect or first aspect, in the 4th kind of possible implementation, described preset strategy is:

At least one target requesting party in the wait access queue of described shared resource sends described at least one authentication information.

In conjunction with the 4th kind of possible implementation of first aspect, in the 5th kind of possible implementation, at least one access request that described basis receives, sends described at least one authentication information according to preset strategy and comprises:

Determine described wait access queue.

In conjunction with the 5th kind of possible implementation of first aspect, in the 6th kind of possible implementation, at least one access request that described basis receives, sends described at least one authentication information according to preset strategy and comprises:

Determine described at least one target requesting party.

In conjunction with the 6th kind of possible implementation of first aspect, in the 7th kind of possible implementation, in described definite described wait access queue:

Determine described wait access queue according to the time sequencing of described at least one access request;

In described definite described at least one target requesting party:

Determine described at least one target requesting party according to time sequencing.

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:

From arriving first, from head of the queue to tail of the queue, be arranged in order requesting party according to the time of described at least one access request.

In conjunction with the 6th kind of possible implementation of first aspect, in the 9th kind of possible implementation, in described definite described wait access queue:

Determine described wait access queue according to requesting party's priority;

In described definite described at least one target requesting party:

Determine described at least one target requesting party according to the priority of described request side.

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 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 6th kind of possible implementation of first aspect, in the 11 kind of possible implementation, in described definite described wait access queue:

Determine described wait access queue according to the time sequencing of described at least one access request and requesting party's priority;

In described definite described at least one target requesting party:

Determine described at least one target requesting party according to the time sequencing of described at least one access request and requesting party's priority.

In conjunction with the 11 kind of possible implementation of first aspect, in the 12 kind of possible implementation, in described definite described wait access queue:

From arriving first, be 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, the height according to priority of the requesting party in the same time period is arranged from front to back.

In conjunction with the 11 kind of possible implementation of first aspect, in the 13 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 7th to the 13 kind of possible implementation of first aspect, in the 14 kind of possible implementation, describedly determine in described at least one target requesting party:

Determine described at least one target requesting party according to the head of the queue of described wait access queue to the order of tail of the queue.

In conjunction with any in the 6th to the 14 kind of possible implementation of first aspect, in the 15 kind of possible implementation, at least one access request that described basis receives, sends in described at least one authentication information according to preset strategy:

In response to stopping accessing described shared resource, send described at least one authentication information.

In conjunction with any in the 6th to the 14 kind of possible implementation of first aspect, in the 16 kind of possible implementation, at least one access request that described basis receives, sends in described at least one authentication information according to preset strategy:

In response to determining that described at least one target requesting party sends described at least one authentication information.

In conjunction with any in the 5th to the 16 kind of possible implementation of first aspect, in the 17 kind of possible implementation, described method also comprises:

Upgrade described wait access queue.

In conjunction with the 17 kind of possible implementation of first aspect, in the 18 kind of possible implementation, in the described wait access queue of described renewal:

Upgrade described wait access queue in response to receiving access request.

In conjunction with the 18 kind of possible implementation of first aspect, in the 19 kind of possible implementation, described method also comprises:

Receive and cancel the message of waiting for.

In conjunction with the 19 kind of possible implementation of first aspect, in the 20 kind of possible implementation, in the described wait access queue of described renewal:

In response to receive cancel wait for information updating described in wait for access queue.

In conjunction with any in the 4th to the 20 kind of possible implementation of first aspect, in the 21 kind of possible implementation, described method also comprises:

Broadcast described wait access queue in response to the renewal of described wait access queue.

In conjunction with any in the 4th to the 20 kind of possible implementation of first aspect, in the 22 kind of possible implementation, described method also comprises:

Described in periodic broadcast, wait for access queue.

In conjunction with any in the 4th to the 22 kind of possible implementation of first aspect, in the 23 kind of possible implementation, described method also comprises:

Transmission stops accessing the message of described shared resource.

In conjunction with the 23 kind of possible implementation of first aspect, in the 24 kind of possible implementation, described transmission stops accessing in the message of described shared resource:

Described in broadcast, stop accessing the message of described shared resource.

In conjunction with the 23 kind of possible implementation of first aspect, in the 25 kind of possible implementation, described transmission stops accessing in the message of described shared resource:

Described in sending to described at least one target requesting method, stop accessing the message of described shared resource.

In conjunction with above-mentioned any possible implementation of first aspect or first aspect, in the 26 kind of possible implementation, according at least one access request receiving, send in described at least one authentication information according to preset strategy:

Send at least two authentication informations, described at least two authentication informations have at least two kinds of priority.

Second aspect, the embodiment of the present invention provides a kind of resource access device, and described device comprises:

One access modules, for accessing shared resource;

One determination module, for determining at least one authentication information of described shared resource;

One administration module, for according at least one access request to described shared resource receiving, sends described at least one authentication information according to preset strategy.

In conjunction with second aspect, in the possible implementation of the first, described access modules comprises:

One addressed location, for using the first authentication information to access described shared resource, the priority of described at least one authentication information is lower than the priority of 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 determination module comprises:

One setting unit, for arranging described at least one authentication information.

In conjunction with the possible implementation of the first of second aspect or second aspect, in the third possible implementation, described determination module comprises:

One acquiring unit, for obtaining described at least one authentication information.

In conjunction with above-mentioned any possible implementation of second aspect or second aspect, in the 4th kind of possible implementation, described administration module comprises:

One first determining unit, for determining the wait access queue of described shared resource.

In conjunction with the 4th kind of possible implementation of second aspect, in the 5th kind of possible implementation, described administration module comprises:

One second determining unit, for determining at least one target requesting party of described shared resource.

In conjunction with the 5th kind of 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 the time sequencing of described at least one access request;

Described the second determining unit is determined described at least one target requesting party according to time sequencing.

In conjunction with the 6th kind of possible implementation of second aspect, in the 7th 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 5th kind of 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 requesting party's priority;

Described the second determining unit is determined described at least one target requesting party according to the priority of described request side.

In conjunction with the 8th kind of possible implementation of second aspect, in the 9th 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 5th kind of possible implementation of second aspect, in the tenth 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 at least one target requesting party according to the time sequencing of described at least one access request and requesting party's priority.

In conjunction with the tenth kind of possible implementation of second aspect, in the 11 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.

In conjunction with the tenth kind of possible implementation of second aspect, in the 12 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 6th to the 12 kind of possible implementation of second aspect, in the 13 kind of possible implementation, described the second determining unit is determined described at least one target requesting party according to the head of the queue of described wait access queue to the order of tail of the queue.

In conjunction with any in the 5th to the 13 kind of possible implementation of second aspect, in the 14 kind of possible implementation, described administration module, in response to stopping accessing described shared resource, sends described at least one authentication information.

In conjunction with any in the 5th to the 13 kind of possible implementation of second aspect, in the 15 kind of possible implementation, it is characterized in that, described administration module is in response to determining that described at least one target requesting party sends described at least one authentication information.

In conjunction with any in the 4th to the 15 kind of possible implementation of second aspect, in the 16 kind of possible implementation, described device also comprises:

One update module, for upgrading described wait access queue.

In conjunction with the 16 kind of possible implementation of second aspect, in the 17 kind of possible implementation, described update module is upgraded described wait access queue in response to receiving access request.

In conjunction with the 17 kind of possible implementation of second aspect, in the 18 kind of possible implementation, described device also comprises:

One receiver module, cancels for receiving the message of waiting for.

In conjunction with the 18 kind of possible implementation of second aspect, in the 19 kind of possible implementation, described update module in response to receive cancel wait for information updating described in wait for access queue.

In conjunction with any in the 4th to the 19 kind of possible implementation of second aspect, in the 20 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 the 4th to the 19 kind of possible implementation of second aspect, in the 21 kind of possible implementation, described device also comprises:

One second broadcast module, waits for access queue for described in periodic broadcast.

In conjunction with any in the 3rd to the 21 kind of possible implementation of second aspect, in the 22 kind of possible implementation, described device also comprises:

One sending module, for sending the message that stops accessing described shared resource.

In conjunction with the 22 kind of possible implementation of second aspect, in the 23 kind of possible implementation, stop accessing the message of described shared resource described in the broadcast of described sending module.

In conjunction with the 22 kind of possible implementation of second aspect, in the 24 kind of possible implementation, described in sending to described at least one target requesting method, described sending module stops accessing the message of described shared resource.

In conjunction with above-mentioned any possible implementation of second aspect or second aspect, in the 25 kind of possible implementation, described administration module sends at least two authentication informations, and described at least two authentication informations have at least two kinds of priority

The method of the embodiment of the present invention and device are by sending authentication information managing shared resource effectively by the requesting party that first user of successful access shared resource accesses shared resources according to preset strategy to other.

Brief description of the drawings

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;

Fig. 8 is the structured flowchart of the 6th 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 term such as " first ", " second " in the application, only for distinguishing different step, equipment or module etc., neither represents 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 more than one 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. access shared resource.

When user wants to access shared resource, can directly or use default authentication information (for example, password) to access described shared resource.In this sends out embodiment each, " authentication information " for accessing described shared resource, includes but not limited to the information that access code, password etc. arbitrarily can authentication-access authorities.

S120. determine at least one authentication information of described shared resource.

In the method for the embodiment of the present invention, the user of successful access shared resource becomes 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 at least one authentication information of described shared resource setting by described management equipment, or obtains described at least one authentication information from this equipment that can manage described shared resource of for example shared resource server.

S130. according at least one access request receiving, send described at least one authentication information according to preset strategy.

Leading subscriber sends described at least one authentication information according to preset strategy at least one requesting party of shared resource described in other request access, makes the requesting party who receives described at least one authentication information obtain the authority of accessing described shared resource.Described preset strategy can be formulated or be preset by leading subscriber, makes every effort in effectively ensureing the current accessed of leading subscriber, takes 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 for the embodiment of the present invention is by sending authentication information managing shared resource effectively by the requesting party that first user of successful access shared resource accesses shared resources according to preset strategy to other.

In a kind of possible implementation, for the better access of management to described shared resource, except described at least one authentication information, leading subscriber also can use management equipment to obtain or arrange one first authentication information, and the current rights of using of described shared resource are revised as and use the first authentication information.The priority of described at least one authentication information is lower than described the first authentication information, thereby prevent that the requesting party who receives described at least one authentication information from using described at least one authentication information to access described shared resource during leading subscriber is accessed described shared resource, causes leading subscriber to be forced to 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 the possible implementation of another kind, described preset strategy is: at least one the target requesting party in the wait access queue of described shared resource sends described at least one 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 S130 can further comprise:

S131. 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 manages the equipment such as server of described shared resource) from the outside of management equipment and obtain the situation of the wait access queue of setting up and/or upgrade, be also included in that management equipment is local to be set up and/or upgrade the situation of waiting for access queue.

S132. 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, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party according to the time of described at least one access request, 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 S132, determine described at least one target requesting party according to time sequencing.

Determine described wait access queue according to requesting party's priority.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, requesting party minimum 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 S132, determine described at least one target requesting party according to requesting party's priority.

Determine described wait access queue according to the time sequencing of described at least one access request and requesting party's priority.For example, from arriving first, be 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, 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, consider the described time sequencing of at least one access request and definite described at least one the target requesting party of requesting party's priority at step S132.

In the method for the embodiment of the present invention, step S132 determines that described at least one 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 one or more requesting parties of (afterwards) and/or priority the highest (low) be target requesting party.Also for example, being chosen in special time period one or more requesting parties of shared resource described in request access is target requesting party; Or choosing one or more requesting parties 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 at least one 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 at least one 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.Determine after target recipient, can determine when described at least one authentication information is sent to determined target recipient according to active user's access needs and/or target requesting party's priority.

In a kind of possible implementation, after determining described at least one target requesting party, can be in response to stopping accessing described shared resource, send described at least one authentication information.Also described at least one authentication information is sent to determined described at least one target requesting party after leading subscriber stops accessing described shared resource.In this case, described at least one target requesting party can just can use shared resource described in corresponding authentication information successful access receiving after described at least one authentication information.

In another possible implementation, can be in response to determining that described at least one target requesting party sends described at least one authentication information.For example, after determining described at least one target requesting party, immediately described at least one authentication information is sent to described at least one target requesting party, now, leading subscriber can continue to access described shared resource, and the conscious wait leading subscriber of described at least one target requesting party visits again described shared resource after stopping using described shared resource; Or because of the restriction of the priority of authentication information, described at least one target requesting party does not stop access line at described leading subscriber and cannot use described at least one authentication information to access described shared resource before being.

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 determine described at least one target requesting party, leading subscriber can send immediately in response to the access request that receives described specific requesting party the authentication information of limit priority to described specific requesting party, and stop current access behavior, make described specific requesting party can at once access described shared resource.

In addition, not determining that in time period of target requesting party, 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:

S140. 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 the mode that sends 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:

S150. described in periodic broadcast, wait for access queue.And/or

S150 '. broadcast 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.

In addition, after described at least one target requesting party receives described at least one authentication information, do not stop to attempt access, the method for the embodiment of the present invention also can comprise:

S160. send the message that stops accessing described shared resource.

Leading subscriber initiatively sends the message that stops accessing described shared resource after stopping accessing described shared resource, to inform that described at least one target requesting party can use described at least one authentication information to access described shared resource.And in step S160, described in to stop access message can be broadcast transmission, can be also directly to send to described at least one target requesting party.

It should be noted that, in the method for the embodiment of the present invention, leading subscriber can be determined one or more target requesting parties, and in response to the situation of having determined multiple target requesting parties, leading subscriber can have respectively the authentication information of different priorities to its transmission.

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 is the arbitrary equipment that can access by the mode such as wired or wireless shared resource, 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:

Access modules 210, for accessing shared resource.

For example, when user wants to access shared resource, by access modules 210 directly or use default authentication information (, password) to access described shared resource.

Determination module 220, for determining at least one authentication information of described shared resource.

In the device 200 of the embodiment of the present invention, the user of successful access shared resource becomes the current leading subscriber of described shared resource, the resource access device 200 of its embodiment of the present invention using is called management equipment, leading subscriber can be at least one authentication information of described shared resource setting by determination module 220, or obtains described at least one authentication information from this equipment that can manage described shared resource of for example shared resource server.Correspondingly, the device 200 of the embodiment of the present invention also comprises the functional module that can realize determination module 220 and external device communication.

Administration module 230, for according at least one access request to described shared resource receiving, sends described at least one authentication information according to preset strategy.

Administration module 230 sends described at least one authentication information according to preset strategy at least one requesting party of shared resource described in other request access, makes the requesting party who receives described at least one authentication information obtain the authority of accessing described shared resource.Described preset strategy can be formulated or be preset by leading subscriber, makes every effort in effectively ensureing the current accessed of leading subscriber, takes 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 managing shared resource effectively by the requesting party that first user of successful access shared resource accesses shared resources according to preset strategy to other.

For the better access of management to described shared resource, except described at least one authentication information, leading subscriber also can use management equipment to obtain or arrange one first authentication information, and the current rights of using of described shared resource are revised as and use the first authentication information.As shown in Figure 3, in a kind of possible implementation, described access modules 210 comprises addressed location 211, be used for using described the first authentication information to access described shared resource, the priority of described at least one authentication information is lower than the priority of described the first authentication information, thereby prevent that the requesting party who receives described at least one authentication information from using described at least one authentication information to access described shared resource during leading subscriber is accessed described shared resource, causes leading subscriber to be forced to publish.Described determination module 220 can further comprise:

Setting unit 221, for arranging described at least one authentication information.

Maybe can comprise:

Acquiring unit 222, for obtaining described at least one authentication information.

In the possible implementation of another kind, described preset strategy is: at least one the target requesting party in the wait access queue of described shared resource sends described at least one 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, described administration module 230 comprises:

The first determining unit 231, for determining the wait access queue of described shared resource.

In the device of the embodiment of the present invention, the first determining unit 231 determines and waits for that access queue can comprise that outside from management equipment (for example managing the equipment such as server of described shared resource) obtains the situation of the wait access queue of setting up and/or upgrade, and is also included in that management equipment is local to be set up and/or upgrade the situation of waiting for access queue.

The second determining unit 232 for after the first determining unit 231 is determined described wait access queue, is determined described at least one target requesting party from described queue according to certain rule.

In the device of the embodiment of the present invention, the first determining unit 231 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, from arriving first, from head of the queue to tail of the queue, be arranged in order requesting party according to the time of described at least one access request, 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 232 is determined described at least one target requesting party according to time sequencing.

Determine described wait access queue according to requesting party's priority.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, requesting party minimum 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 232 is determined described at least one target requesting party according to requesting party's priority.

Determine described wait access queue according to the time sequencing of described at least one access request and requesting party's priority.For example, from arriving first, be 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, 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 232 considers the described time sequencing of at least one access request and definite described at least one the target requesting party of requesting party's priority.

In the device of the embodiment of the present invention, the second determining unit 232 determines that described at least one 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 one or more requesting parties of (afterwards) and/or priority the highest (low) be target requesting party.Also for example, being chosen in special time period one or more requesting parties of shared resource described in request access is target requesting party; Or choosing one or more requesting parties with certain priority is target requesting party.

The second determining unit 232, in response to the arrival of the time point of default time span/default, is determined described at least one 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 at least one target requesting party, for example, receive after the access request of the requesting party with higher priority, the requesting party that the second determining unit 232 redefines described higher priority is target requesting party.Determine after target recipient, determined when described at least one authentication information is sent to determined target recipient according to active user's access needs and/or target requesting party's priority.

In a kind of possible implementation, after the second determining unit 232 is determined described at least one target requesting party, can be in response to stopping accessing described shared resource, send described at least one authentication information.Also described at least one authentication information is sent to determined described at least one target requesting party after leading subscriber stops accessing described shared resource.In this case, described at least one target requesting party can just can use shared resource described in corresponding authentication information successful access receiving after described at least one authentication information.

In another possible implementation, administration module 230 can determine that described at least one target requesting party sends described at least one authentication information in response to the second determining unit 232.For example, administration module 230 is after the second determining unit 232 is determined described at least one target requesting party, immediately described at least one authentication information is sent to described at least one target requesting party, now, leading subscriber can continue to access described shared resource, and the conscious wait leading subscriber of described at least one target requesting party visits again described shared resource after stopping using described shared resource; Or because of the restriction of the priority of authentication information, described at least one target requesting party does not stop access line at described leading subscriber and cannot use described at least one authentication information to access described shared resource before being.

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 the second determining unit 232 has determined described at least one target requesting party, administration module 230 can send immediately in response to the access request that receives described specific requesting party the authentication information of limit priority to described specific requesting party, and stop current access behavior, make described specific requesting party can at once access described shared resource.

In addition, not determining that in time period of target requesting party, 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 the mode that sends access request described in request access; User in described wait access queue also can by active send wait for cancel message inform leading subscriber its cancel wait for behavior.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 the functional module that receives described at least one access request and cancel the message of waiting for.As shown in Figure 6, comprising:

Receiver module 250, cancels for receiving the message of waiting for.Described at least one access request also can be received by receiver module 250, or the module that can carry out receiving function by other receives.

As shown in Figure 7, in order to provide relatively good user to experience to user (especially etc. user to be visited), the device 200 of the embodiment of the present invention also comprises:

The first broadcast module 260, for broadcasting described wait access queue in response to the renewal of described wait access queue.And/or

The second broadcast module 260 ', waits for access queue for described in periodic broadcast.

In addition, after described at least one target requesting party receives described at least one authentication information, do not stop to attempt access, as shown in Figure 8, the device 200 of the embodiment of the present invention also can comprise:

Sending module 270, for sending the message that stops accessing described shared resource.

Leading subscriber initiatively sends by sending module 270 message that stops accessing described shared resource after stopping accessing described shared resource, to inform that described at least one target requesting party can use described at least one authentication information to access described shared resource.Sending module 270 can be to stop access message described in broadcast transmission, can be also directly to send to described at least one target requesting party.

It should be noted that, in the device of the embodiment of the present invention, administration module 230 can be determined one or more target requesting parties, and in response to the situation of having determined multiple target requesting parties, administration module 230 can have respectively the authentication information of different priorities to its transmission.

In addition, the function that the device of the embodiment of the present invention is carried out described at least one authentication information of transmission also can be completed by described sending module, or is completed by other functional module, in this not restriction of the device of conduct to the embodiment of the present invention.

Further illustrate method and the device of various embodiments of the present invention below by instantiation.

Example one

User's first is successfully used and is shared account access destination database by default password.When not using the method for the embodiment of the present invention and installing, other users use described shared account accessing database will cause user's first to be forced to publish.Use after the method and device of the embodiment of the present invention, user's first becomes the leading subscriber of described shared account, and the password of described shared account is set to first password.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, sets up and waits for access queue, and user's second is joined in described access queue in response to the described access request receiving.During user's first is accessed described database, it receives user third, Yong Huding, user's penta access request successively, and successively user third, Yong Huding, user penta is added to the tail of the queue of waiting for access queue according to the time order and function of access request.Access queue is waited in the every renewal of user's first, i.e. wait access queue after broadcast is upgraded, and Yong Huyi, Yong Hubing, Yong Huding, 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, after a period of time of the described database of access, is determined that the user third of described wait access queue head of the queue is target requesting party, and first password is sent to user third.In the time that user's first stops accessing described database, send to described user third message that stops access, user third can use first password to access described database at once, and becomes the current leading subscriber of described account.

Example two

In the situation of example one, user's first becomes after the leading subscriber of described shared account, and first password and second password of described shared account is set, and wherein, the priority of first password is higher than the second password.User's first is used first password to continue the described database of access, and after definite described user third is target requesting party, immediately the second password is sent to user the third, and now, user third cannot be by sharing account described in the second password login.User's first stops accessing after described database user third just can use database described in the second cryptographic acess.User's first is stopping sending to described user third message that stops access after access.User third uses described in the second password successful access becomes the current leading subscriber of described account after database.

Example three

In the situation of example one, user's first becomes after the leading subscriber of described shared account, and first password and second password of described shared account is set, and wherein, the priority of first password is higher than the second password.User's first is used first password to continue the described database of access, and after definite described user third is target requesting party, immediately the second password is sent to user third.User's first stops receiving before accessing described database 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, stop using described shared account and to user oneself send first password, oneself becomes the current leading subscriber of described shared account user.User can be notified or do not notified to user's first third this variation, and user third continues to wait for stopping using of first password.

Example four

User's first is successfully used and is shared account access destination database by default password.When not using the method for the embodiment of the present invention and installing, other users use described shared account accessing database will cause user's first to be forced to publish.Use after the method and device of the embodiment of the present invention, user's first becomes the leading subscriber of described shared account, and the password of described shared account is set to first password.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, sets up and waits for access queue in response to the described access request receiving, and user's second is joined in described access queue and to it and sends the second password.During user's first is accessed described database, receive successively user third, Yong Huding, user's penta access request, successively user third, Yong Huding, user penta are added to the tail of the queue of waiting for access queue according to the time order and function of access request, and sending the 3rd password, the 4th password and the 5th password to user third, Yong Huding, user penta respectively according to time order and function order, the priority of the second password, the 3rd password, the 4th password and the 5th password reduces successively.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.Now, the second password lost efficacy, and the priority of the 3rd password, the 4th password and the 5th password still reduces successively.In the time that user's first stops accessing described database, send the message that stops access to user third, user third can use database described in the 3rd cryptographic acess at once, and becomes the current leading subscriber of described shared account.During user third is by database described in the 3rd cryptographic acess, for asking subsequently the user who uses described shared account to access described database to send the 6th password having lower than the priority of described the 5th password, and the rest may be inferred.

The structural representation of another resource access device 800 that Fig. 8 provides for this aspect embodiment, the application's specific embodiment does not limit the specific implementation of resource access 800.As shown in Figure 8, described resource access device 800 can comprise:

Processor (processor) 810, communication interface (Communications Interface) 820, memory (memory) 830 and communication bus 840.Wherein:

Processor 810, communication interface 820 and memory 830 complete mutual communication by communication bus 840.

Communication interface 820, for net element communication such as client etc.

Processor 810, for executive program 832, specifically can carry out the correlation step in said method embodiment.

Particularly, program 832 can comprise program code, and described program code comprises computer-managed instruction.

Processor 810 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 830, for depositing program 832.Memory 830 may comprise high-speed RAM memory, also may also comprise nonvolatile memory (non-volatile memory), for example at least one magnetic disc store.Program 832 specifically can be for making described display control unit 800 carry out following steps:

Access shared resource;

Determine at least one authentication information of described shared resource;

In program 832, 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 skill in the art 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 realize described function with distinct methods to each specifically should being used for, but this realization should not thought and exceeds the application's scope.

If described function realizes and during as production marketing independently or use, can be stored in a computer read/write memory medium using the form of SFU software functional unit.Based on such understanding, 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 (can be personal computers in order to make a computer equipment, 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 case of not departing 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

1. a resource access method, is characterized in that, described method comprises:

Access shared resource;

Determine at least one authentication information of described shared resource;

2. method according to claim 1, is characterized in that, described access shared resource comprises:

3. method according to claim 1 and 2, is characterized in that, described at least one authentication information of determining described shared resource comprises:

Described at least one authentication information is set.

4. method according to claim 1 and 2, is characterized in that, described at least one authentication information of determining described shared resource comprises:

Obtain described at least one authentication information.

5. according to the method described in any one in claim 1 to 4, it is characterized in that, described preset strategy is:

6. method according to claim 5, is characterized in that, at least one access request that described basis receives sends described at least one authentication information according to preset strategy and comprises:

Determine described wait access queue.

7. method according to claim 6, is characterized in that, at least one access request that described basis receives sends described at least one authentication information according to preset strategy and comprises:

Determine described at least one target requesting party.

8. method according to claim 7, is characterized in that, in described definite described wait access queue:

In described definite described at least one target requesting party:

9. method according to claim 8, is characterized in that, in described definite described wait access queue:

10. method according to claim 7, is characterized in that, in described definite described wait access queue:

Determine described wait access queue according to requesting party's priority;

In described definite described at least one target requesting party:

11. methods according to claim 10, is characterized in that, in described definite described wait access queue:

12. methods according to claim 7, is characterized in that, in described definite described wait access queue:

In described definite described at least one target requesting party:

13. methods according to claim 12, is characterized in that, in described definite described wait access queue:

14. methods according to claim 12, is characterized in that, in described definite described wait access queue:

Method in 15. according to Claim 8 to 14 described in any one, is characterized in that, in described definite described at least one target requesting party:

16. according to the method described in any one in claim 7 to 15, it is characterized in that at least one access request that described basis receives sends in described at least one authentication information according to preset strategy:

17. according to the method described in any one in claim 7 to 15, it is characterized in that at least one access request that described basis receives sends in described at least one authentication information according to preset strategy:

18. according to the method described in any one in claim 6 to 17, it is characterized in that, described method also comprises:

Upgrade described wait access queue.

19. methods according to claim 18, is characterized in that, in the described wait access queue of described renewal:

Upgrade described wait access queue in response to receiving access request.

20. methods according to claim 19, is characterized in that, described method also comprises:

Receive and cancel the message of waiting for.

21. methods according to claim 20, is characterized in that, in the described wait access queue of described renewal:

22. according to the method described in any one in claim 5 to 21, it is characterized in that, described method also comprises:

23. according to the method described in any one in claim 5 to 21, it is characterized in that, described method also comprises:

Described in periodic broadcast, wait for access queue.

24. according to the method described in any one in claim 5 to 23, it is characterized in that, described method also comprises:

Transmission stops accessing the message of described shared resource.

25. methods according to claim 24, is characterized in that, described transmission stops accessing in the message of described shared resource:

26. methods according to claim 24, is characterized in that, described transmission stops accessing in the message of described shared resource:

27. according to the method described in any one in claim 1 to 26, it is characterized in that, according at least one access request receiving, sends in described at least one authentication information according to preset strategy:

28. 1 kinds of resource access devices, is characterized in that, described device comprises:

One access modules, for accessing shared resource;

29. devices according to claim 28, is characterized in that, described access modules comprises:

30. according to the device described in claim 28 or 29, it is characterized in that, described determination module comprises:

31. according to the device described in claim 28 or 29, it is characterized in that, described determination module comprises:

32. according to the device described in any one in claim 28 to 31, it is characterized in that, described administration module comprises:

33. devices according to claim 32, is characterized in that, described administration module comprises:

34. devices according to claim 33, 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;

35. devices according to claim 34, 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.

36. devices according to claim 33, is characterized in that, described the first determining unit is determined described wait access queue according to requesting party's priority;

37. devices according to claim 36, 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.

38. devices according to claim 33, 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;

39. according to the device described in claim 38, 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.

40. according to the device described in claim 38, 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.

41. according to the device described in any one in claim 34 to 40, it is characterized in that, described the second determining unit is determined described at least one target requesting party according to the head of the queue of described wait access queue to the order of tail of the queue.

42. according to the device described in any one in claim 33 to 41, it is characterized in that, described administration module, in response to stopping accessing described shared resource, sends described at least one authentication information.

43. according to the device described in any one in claim 33 to 41, it is characterized in that, described administration module is in response to determining that described at least one target requesting party sends described at least one authentication information.

44. according to the device described in any one in claim 32 to 43, it is characterized in that, described device also comprises:

One update module, for upgrading described wait access queue.

45. according to the device described in claim 44, it is characterized in that, described update module is upgraded described wait access queue in response to receiving access request.

46. according to the device described in claim 45, it is characterized in that, described device also comprises:

One receiver module, cancels for receiving the message of waiting for.

47. according to the device described in claim 46, it is characterized in that, described update module in response to receive cancel wait for information updating described in wait for access queue.

48. according to the device described in any one in claim 32 to 47, it is characterized in that, described device also comprises:

49. according to the device described in any one in claim 32 to 47, it is characterized in that, described device also comprises:

50. according to the device described in any one in claim 31 to 49, it is characterized in that, described device also comprises:

51. according to the device described in claim 50, it is characterized in that, stops accessing the message of described shared resource described in the broadcast of described sending module.

52. according to the device described in claim 50, it is characterized in that, stops accessing the message of described shared resource described in described sending module sends to described at least one target requesting method.

53. according to the device described in any one in claim 28 to 52, it is characterized in that, described administration module sends at least two authentication informations, and described at least two authentication informations have at least two kinds of priority.