CN103973691B - Resource access method and resource access device - Google Patents
Resource access method and resource access device Download PDFInfo
- Publication number
- CN103973691B CN103973691B CN201410196889.5A CN201410196889A CN103973691B CN 103973691 B CN103973691 B CN 103973691B CN 201410196889 A CN201410196889 A CN 201410196889A CN 103973691 B CN103973691 B CN 103973691B
- Authority
- CN
- China
- Prior art keywords
- queue
- shared resource
- access
- requesting party
- 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.)
- Active
Links
Landscapes
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a kind of resource access method and resource access device, is related to shared resource technical field.Methods described includes：In response to accessing shared resource failure, the first authentication information of the shared resource is obtained；According at least one access request to the shared resource received, according to the second authentication information of the preset strategy transmission shared resource.The method and device of the embodiment of the present invention being capable of effectively managing shared resource, and administrative mechanism is simple by accessing requesting parties' transmission authentication information of shared resources to other according to preset strategy from each user for accessing failure and the authentication information for getting shared resource.
Description
Technical field
The application is related to shared resource management domain, more particularly to a kind of resource access method and resource access device.
Background technology
In the work and life of reality, there are the application scenarios that multiple users access same shared resource often, for example, it is more
Individual user logs in search engine using shared account and obtains service.However, because some resources are restricted to the number of users of access,
Often because occurring accessing user without effective resource access scheme beyond congestion caused by defined quantity, or access
Conflict causes logged-in user to be forced the phenomenon published.
The content of the invention
The purpose of the application is：There is provided it is a kind of can realize shared resource access effective management resource access method and
Resource access device.
In a first aspect, the embodiments of the invention provide a kind of resource access method, methods described includes：
In response to accessing shared resource failure, the first authentication information of the shared resource is obtained；
According at least one access request to the shared resource received, sent according to preset strategy described shared
Second authentication information of resource.
It is described in response to accessing shared resource failure with reference in a first aspect, in the first possible implementation, obtain
First authentication information of the shared resource includes：
In response to accessing shared resource failure, the access request to the shared resource is sent；
Receive first authentication information.
With reference to the possible implementation of the first of first aspect or first aspect, in second of possible implementation
In, the preset strategy is：
Destination request side in wait access queue to the shared resource sends second authentication information.
With reference to second of possible implementation of first aspect, in the third possible implementation, the basis
At least one access request to the shared resource received, the second mirror of the shared resource is sent according to preset strategy
Power information includes：
Determine the wait access queue.
With reference to the third possible implementation of first aspect, in the 4th kind of possible implementation, the basis
At least one access request to the shared resource received, the second mirror of the shared resource is sent according to preset strategy
Power information includes：
Determine the destination request side.
With reference to the 4th kind of possible implementation of first aspect, in the 5th kind of possible implementation, the determination
In the wait access queue：
Time sequencing according at least one access request determines the wait access queue；
It is described to determine in the destination request side：
The destination request side is determined sequentially in time.
With reference to the 5th kind of possible implementation of first aspect, in the 6th kind of possible implementation, the determination
In the wait access queue：
According to the time of at least one access request after arriving first, requesting party is arranged in order from head of the queue to tail of the queue.
With reference to the 4th kind of possible implementation of first aspect, in the 7th kind of possible implementation, the determination
In the wait access queue：
Priority according to requesting party determines the wait access queue；
It is described to determine in the destination request side：
Priority according to the requesting party determines the destination request side.
With reference to the 7th kind of possible implementation of first aspect, in the 8th kind of possible implementation, the determination
In the wait access queue：
According to requesting party's priority from high to low, requesting party is arranged in order from head of the queue to tail of the queue.
With reference to the 4th kind of possible implementation of first aspect, in the 9th kind of possible implementation, the determination
In the wait access queue：
The team to be visited such as described is determined according to the time sequencing of at least one access request and the priority of requesting party
Row；
It is described to determine in the destination request side：
The destination request side is determined according to the time sequencing of at least one access request and the priority of requesting party.
With reference to the 9th kind of possible implementation of first aspect, in the tenth kind of possible implementation, the determination
In the wait access queue：
According to the time of at least one access request after arriving first, requesting party is arranged in order from head of the queue to tail of the queue, together
The height of requesting party according to priority in one period arranges from front to back.
It is described true in a kind of the tenth possible implementation with reference to the 9th kind of possible implementation of first aspect
In the fixed wait access queue：
According to requesting party's priority from high to low, requesting party, the request of same priority are arranged in order from head of the queue to tail of the queue
Side arranges from front to back according to the time order and function of access request.
A kind of any of the 5th to the tenth possible implementation with reference to first aspect, it is possible at the 12nd kind
It is described to determine in the destination request side in implementation：
It is determined that the requesting party for waiting access queue head of the queue is the destination request side.
Any of the 4th to the 12nd kind of possible implementation with reference to first aspect, it is possible at the 13rd kind
In implementation, at least one access request to the shared resource received, send according to preset strategy described in
In second authentication information：
In response to determining that the destination request side sends second authentication information.
Any of the 3rd to the 13rd kind of possible implementation with reference to first aspect, it is possible at the 14th kind
In implementation, methods described also includes：
Update the wait access queue.
It is described in the 15th kind of possible implementation with reference to the 14th kind of possible implementation of first aspect
Update in the wait access queue：
The wait access queue is updated in response to receiving access request.
It is described in the 16th kind of possible implementation with reference to the 15th kind of possible implementation of first aspect
Method also includes：
Receive the message cancelled and waited.
It is described in the 17th kind of possible implementation with reference to the 16th kind of possible implementation of first aspect
Update in the wait access queue：
In response to receiving to cancel access queue is waited described in the information updating waited.
Any of second to the 17th kind of possible implementation with reference to first aspect, it is possible at the 18th kind
In implementation, methods described also includes：
The wait access queue is broadcasted in renewal in response to the wait access queue.
Any of second to the 17th kind of possible implementation with reference to first aspect, it is possible at the 19th kind
In implementation, methods described also includes：
Access queue is waited described in periodic broadcast.
With reference to first aspect or any of the above-described kind of possible implementation of first aspect, in the 20th kind of possible realization
In mode, methods described also includes：
Determine second authentication information.
With reference to the 20th kind of possible implementation of first aspect, in a kind of the 20th possible implementation, institute
It is identical with first authentication information to state the second authentication information.
With reference to the 20th kind of possible implementation of first aspect, in the 22nd kind of possible implementation, institute
The priority for stating the second authentication information is less than the priority of first authentication information.
Second aspect, the embodiments of the invention provide a kind of resource access device, described device includes：
One acquisition module, in response to accessing shared resource failure, obtaining the first authentication information of the shared resource；
One management module, at least one access request to the shared resource received for basis, according to default
Strategy sends the second authentication information of the shared resource.
With reference to second aspect, in the first possible implementation, the acquisition module includes：：
One transmitting element, in response to accessing shared resource failure, sending the access request to the shared resource；
One receiving unit, for receiving first authentication information.
With reference to the possible implementation of the first of second aspect or second aspect, in second of possible implementation
In, the management module includes：
One first determining unit, for determining the wait access queue of the shared resource.
With reference to second of possible implementation of second aspect, in the third possible implementation, the management
Module includes：
One second determining unit, for determining destination request side.
With reference to the third possible implementation of second aspect, in the 4th kind of possible implementation, described first
Determining unit determines the wait access queue according to the time sequencing of at least one access request；
Second determining unit determines the destination request side sequentially in time.
With reference to the 4th kind of possible implementation of second aspect, in the 5th kind of possible implementation, described first
Determining unit after arriving first, is arranged in order requesting party according to the time of at least one access request from head of the queue to tail of the queue.
With reference to the third possible implementation of second aspect, in the 6th kind of possible implementation, described first
Determining unit determines the wait access queue according to the priority of requesting party；
Second determining unit determines the destination request side according to the priority of the requesting party.
With reference to the 6th kind of possible implementation of second aspect, in the 7th kind of possible implementation, described first
Determining unit from high to low, is arranged in order requesting party according to requesting party's priority from head of the queue to tail of the queue.
With reference to the third possible implementation of second aspect, in the 8th kind of possible implementation, described first
Determining unit determines the team to be visited such as described according to the time sequencing of at least one access request and the priority of requesting party
Row；
Second determining unit is true according to the time sequencing of at least one access request and the priority of requesting party
The fixed destination request side.
With reference to the 8th kind of possible implementation of second aspect, in the 9th kind of possible implementation, described first
Determining unit after arriving first, is arranged in order requesting party, together according to the time of at least one access request from head of the queue to tail of the queue
The height of requesting party according to priority in one period arranges from front to back.
With reference to the 8th kind of possible implementation of second aspect, in the tenth kind of possible implementation, described first
Determining unit from high to low, is arranged in order requesting party, the request of same priority according to requesting party's priority from head of the queue to tail of the queue
Side arranges from front to back according to the time order and function of access request.
Any of the 4th to the tenth kind of possible implementation with reference to second aspect, in a kind of the tenth possible reality
In existing mode, second determining unit determines that it is the destination request side to wait the requesting party of access queue head of the queue.
A kind of any of the 3rd to the tenth possible implementation with reference to second aspect, it is possible at the 12nd kind
In implementation, the management module is in response to determining that the destination request side sends second authentication information.
Any of second to the 12nd kind of possible implementation with reference to second aspect, it is possible at the 13rd kind
In implementation, described device also includes：
One update module, for updating the wait access queue.
It is described in the 14th kind of possible implementation with reference to the 13rd kind of possible implementation of second aspect
Update module updates the wait access queue in response to receiving access request.
It is described in the 15th kind of possible implementation with reference to the 14th kind of possible implementation of second aspect
Device also includes：
One receiving module, cancel the message waited for receiving.
It is described in the 16th kind of possible implementation with reference to the 14th kind of possible implementation of second aspect
Update module response receives and waits access queue described in the information updating cancelled and waited.
Any of first to the 16th kind of possible implementation with reference to second aspect, it is possible at the 17th kind
In implementation, described device also includes：
One first broadcast module, for broadcasting the wait access queue in response to the renewal of the wait access queue.
Any of first to the 16th kind of possible implementation with reference to second aspect, it is possible at the 18th kind
In implementation, described device also includes：
One second broadcast module, for waiting access queue described in periodic broadcast.
With reference to second aspect or any of the above-described kind of possible implementation of second aspect, in the 19th kind of possible realization
In mode, described device also includes：
One determining module, for determining second authentication information.
The method and device of the embodiment of the present invention by each access by failing and getting the authentication information of shared resource
User according to preset strategy to other access shared resources requesting parties send authentication information can effectively manage shared money
Source, and administrative mechanism is simple.
Brief description of the drawings
Fig. 1 is a kind of flow chart of resource access method of the embodiment of the present invention；
Fig. 2 is a kind of structured flowchart of resource access device of present aspect embodiment；
Fig. 3 is a kind of a kind of structured flowchart of possible implementation of resource access device of present aspect embodiment；
Fig. 4 is a kind of structured flowchart of the alternatively possible implementation of resource access device of present aspect embodiment；
Fig. 5 is a kind of structured flowchart of the third possible implementation of resource access device of present aspect embodiment；
Fig. 6 is a kind of structured flowchart of the 4th kind of possible implementation of resource access device of present aspect embodiment；
Fig. 7 is a kind of structured flowchart of the 5th kind of possible implementation of resource access device of present aspect embodiment.
Embodiment
(identical label represents identical element in some accompanying drawings) and embodiment below in conjunction with the accompanying drawings, to the tool of the application
Body embodiment is described in further detail.Following examples are used to illustrate the application, but are not limited to scope of the present application.
It will be understood by those skilled in the art that the term such as " first ", " second " in the application be only used for distinguishing it is asynchronous
Suddenly, equipment or module etc., any particular technology implication is neither represented, does not also indicate that the inevitable logical order between them.
In addition, " shared resource " in various embodiments of the present invention, which refers to, can be based on network by more than one task access (use)
Resource, for example, database, application program, website, file, memory space etc., preferably limit the concurrent of such shared resource
Visit capacity.The resource access method of the embodiment of the present invention can be by that can access appointing for shared resource by the mode such as wired or wireless
Equipment of anticipating operation, for example, mobile phone, notebook computer, palm PC etc..User can directly or indirectly be accessed by the equipment
Shared resource.
As shown in figure 1, the resource access method of an embodiment of the present invention includes：
S110. in response to accessing shared resource failure, the first authentication information of the shared resource is obtained.
In the method for the embodiment of the present invention, when user desires access to shared resource, it can believe directly or using default authentication
Cease (for example, password) and access the shared resource, if accessing the shared resource failure, send the visit to the shared resource
The mode of request is asked, and receives the first authentication information.The access request can be sent by the form of broadcast, also can be directed to send
To the management equipment of the shared resource, for example, server apparatus, the equipment etc. for currently taking the shared resource.In this hair
In each embodiment, " authentication information " is used to access the shared resource, including but not limited to accesses password, password etc. and arbitrarily can
The information of authentication-access authority.And the first authentication information is on a preset condition based with the authentication for accessing the shared resource authority
Information, the preparatory condition are that the shared resource is unoccupied.
S120. after getting the first authentication information of the shared resource, according to receiving to the shared resource
At least one access request, the second authentication information of the shared resource is sent according to preset strategy.
In the method for the embodiment of the present invention, access shared resource and fail and get the authentication information of the shared resource
User turn into the current management user of the shared resource, its used equipment is referred to as in the method for the embodiment of the present invention
Management equipment, management user can be the authentication information of shared resource setting second by the management equipment, or from for example common
Enjoy Resource Server or currently take and second authentication information is obtained at the equipment of the shared resource.
Manage requesting party's transmission second mirror that user accesses the shared resource according to preset strategy to other requests
Weigh information so that the requesting party for receiving second authentication information obtains the authority for accessing the shared resource.It is described default
Strategy can be formulated or preset by managing user, make every effort to effectively ensureing the user's that currently takes the shared resource
While access, other requesting parties for liberally treating the shared resource are taken into account.So as to avoid the concurrent of the shared resource
Management user caused by congestion, or malicious user preempting resources caused by visit capacity exceeds defined quantity is forced to publish.
To sum up, the method for the embodiment of the present invention passes through by each authentication information for accessing failure and getting shared resource
User according to requesting parties of preset strategy to other access shared resources send authentication information can effectively managing shared resource,
And administrative mechanism is simple.
The method of the embodiment of the present invention also includes：
S130. second authentication information is determined.
Wherein, second authentication information can be identical with first authentication information, also can be different.In order to preferably manage
Access to the shared resource, in a kind of possible implementation, the priority of second authentication information can be set
Less than the priority of first authentication information, so as to prevent from receiving the requesting party of second authentication information in management user
Accessed before management user accesses the shared resource when accessing the shared resource or using second authentication information
The shared resource, cause management user can not access or be forced to publish.In various embodiments of the present invention, authentication information is not
Same priority can embody in the following manner：The authentication information of each priority is effective only in respective special time period, higher
Within the period earlier effectively, the authentication information of lower priority has the authentication information of priority in later time section
Effect；Or one user access the shared resource using the authentication information of higher priority during, other users will be unable to use
The authentication information of lower priority accesses the shared resource.
In a kind of possible implementation, the preset strategy is：In wait access queue to the shared resource
Destination request side send second authentication information.It is described to wait access queue to be asked according to the access to the shared resource
Ask what is established, wherein the information of the requesting party of the shared resource to be visited such as containing, for example, the mark letter of requesting party
Breath, ask time of access etc..Correspondingly, step S120 can further comprise：
S121. the wait access queue is determined.
In the method for the embodiment of the present invention, it is determined that waiting access queue to may include to manage outside of the user from management equipment
(such as managing the server of the shared resource) obtains the situation for the wait access queue established and/or updated, in addition to
The situation of wait access queue is locally created and/or updates in management equipment.
S122. at least one destination request side is determined.
After determining the wait access queue, management user determines that target please from the queue according to certain rule
The side of asking.
In the method for the embodiment of the present invention, determine it is described wait access queue rule may include it is a variety of：
Time according at least one access request determines the wait access queue.For example, according to it is described at least
The time of one access request after arriving first, is arranged in order requesting party from head of the queue to tail of the queue, that is, often receiving a new access
Request, corresponding requesting party is come to the tail of the queue of the wait access queue.Now, it is true sequentially in time in step S122
Fixed at least one destination request side.
Priority according to requesting party determines the wait access queue.For example, according to requesting party's priority from high to low,
Requesting party is arranged in order from head of the queue to tail of the queue, that is, the minimum requesting party of priority to be come to the team of the wait access queue
Tail.The priority of requesting party can be determined by managing user, or pre-set, and may determine that according to the identification information of requesting party
The priority of requesting party, or corresponding precedence information is directly contained in access request.Now, in step S122 according to
The priority of requesting party determines the destination request side.
The team to be visited such as described is determined according to the time sequencing of at least one access request and the priority of requesting party
Row.For example, requesting party is arranged in order from head of the queue to tail of the queue, together after arriving first according to the time of at least one access request
The height of requesting party according to priority in one period arranges from front to back.Or according to requesting party's priority from high to low, from
Head of the queue is arranged in order requesting party 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
Row.Now, consider the time sequencing of at least one access request in step S122 and the priority of requesting party determines
The destination request side, while the second authentication information is sent to the higher requesting party of priority, it may be notified that it please to accessing
The access request of first requesting party is asked to respond.
In the method for the embodiment of the present invention, it is a variety of that step S122 determines that the rule of the destination request side can also have.Example
Such as, according to it is described wait access queue head of the queue (tail of the queue) arrive tail of the queue (head of the queue) order, choose request time at first (rear) and/
Or a requesting party of highest priority (low) is destination request side.Further for example, being chosen at request in special time period accesses institute
A requesting party for stating shared resource is destination request side；Or choose a requesting party with certain priority and asked for target
The side of asking.
User response is managed in the arrival at default time span/default time point, is accessed according to the whole received
Request determines the destination request side.It may also be responsive in the access request for receiving some specific requesting party, it is determined that or again true
The fixed destination request side.For example, after receiving the access request of the requesting party with higher priority, redefine it is described compared with
The requesting party of high priority is destination request side.
In addition, in a kind of possible implementation, after determining the destination request side, may be in response to management user can
To access the shared resource using the first authentication information, second authentication information is sent, receives the second authentication letter
The requesting party of breath turns into management user.In alternatively possible implementation, it may be in response to determine destination request side's hair
Send second authentication information.For example, after determining the destination request side, second authentication information is sent to institute immediately
Destination request side is stated, now, user is managed and receives the requesting party of second authentication information and continue waiting for being able to access that
The shared resource, receiving the requesting party of the second authentication information turns into management user, and the two, which feels to wait, currently takes institute
The user for stating shared resource stops using the shared resource to access the shared resource successively again afterwards；Or because of authentication information
The limitation of priority, before the shared resource is not released, the two can not be accessed.
For specific requesting party, (the specific requesting party may have the higher or highest for accessing the shared resource
Priority), regardless of whether having determined that the destination request side, management user may be in response to receive the specific request
The access request of side sends the authentication information of limit priority to the specific requesting party immediately so that the specific request
Side can access the shared resource at once.
In addition, within the period for not determining destination request side, the message that management user needs response to receive safeguards institute
State wait access list.Correspondingly, the method for the embodiment of the present invention also includes：
S130. the wait access queue is updated.
In the method for the embodiment of the present invention, request accesses the user of the shared resource by sending the side of access request
Formula is added to the wait access queue；User in the wait access queue can also be sent by active cancels what is waited
To inform management user, it cancels the behavior waited to message.Management user response in receive access request, cancel wait
Message etc. updates the wait access queue.Correspondingly, the method for the embodiment of the present invention can include at least one described in reception respectively
The step of message that individual access request and cancellation wait.
In order to provide relatively good Consumer's Experience to user (user for being especially to wait for accessing), the embodiment of the present invention
Method also includes：
S140. access queue is waited described in periodic broadcast.And/or
S140 ' broadcast the wait access queue in response to the renewal of the wait access queue.
By broadcasting the wait access queue, the user for wanting or waiting the shared resource to be visited can be allowed to understand institute
State the occupancy situation of shared resource and wait situation, so as to provide the reference further selected for each user.
It will be understood by those skilled in the art that in the above method of the application embodiment, the sequence number of each step
Size is not meant to the priority of execution sequence, and the execution sequence of each step should be determined with its function and internal logic, without answering
Any restriction is formed to the implementation process of the application embodiment.
The embodiment of the present invention additionally provides a kind of resource access device.Described device is that can pass through wired or wireless grade side
Formula accesses the arbitrary equipment of shared resource, for example, mobile phone, notebook computer, palm PC etc..User can pass through the equipment
Directly or indirectly access shared resource.As shown in Fig. 2 the resource access device 200 of the embodiment of the present invention includes:
Acquisition module 210, in response to accessing shared resource failure, obtaining the first authentication letter of the shared resource
Breath.
When user desires access to shared resource, it can be accessed directly or using default authentication information (for example, password) described common
Resource is enjoyed, using the device of the embodiment of the present invention, if accessing the shared resource failure, passes through the transmission of acquisition module 210
Unit 211 sends the mode of the access request to the shared resource, and receives the first authentication information by receiving unit 212.Hair
Send unit 211 to send the access request by the form of broadcast, also can be directed to transmission to the management of the shared resource and set
It is standby, for example, server apparatus, the equipment etc. for currently taking the shared resource.
Management module 220, for after the first authentication information of the shared resource is got, according to acquisition module 210
At least one access request to the shared resource received, the second mirror of the shared resource is sent according to preset strategy
Weigh information.
In the device of the embodiment of the present invention, access shared resource and fail and get the authentication information of the shared resource
User turn into the current management user of the shared resource, it is right using the device (being referred to as management equipment) of the embodiment of the present invention
The shared resource is managed, and management user can be the authentication information of shared resource setting second by described device 200,
Or described the is obtained at external equipment from such as shared resource server or currently take as the equipment of the shared resource
Two authentication informations.Correspondingly, the device 200 of the embodiment of the present invention also includes to realize that management module 220 is led to external equipment
The functional module of letter.
The requesting party that management module 220 accesses the shared resource according to preset strategy to other requests sends described second
Authentication information so that the requesting party for receiving second authentication information obtains the authority for accessing the shared resource.It is described pre-
If strategy can be formulated or preset by managing user, make every effort to effectively ensureing the user that currently takes the shared resource
Access while, take into account other requesting parties for liberally treating the shared resource.So as to avoid the shared resource and
Management user caused by congestion, or malicious user preempting resources caused by visit capacity exceeds defined quantity is sent out to be forced to step on
Go out.
To sum up, the device of the embodiment of the present invention passes through by each authentication information for accessing failure and getting shared resource
User according to requesting parties of preset strategy to other access shared resources send authentication information can effectively managing shared resource,
And administrative mechanism is simple.
As shown in figure 3, the device 200 of the embodiment of the present invention also includes：
Determining module 230, for determining second authentication information.
Wherein, second authentication information can be identical with first authentication information, also can be different.In order to preferably manage
Access to the shared resource, in a kind of possible implementation, the priority of second authentication information can be set
Less than the priority of first authentication information, so as to prevent from receiving the requesting party of second authentication information in management user
Visited during accessing the shared resource or before management user accesses the shared resource using second authentication information
The shared resource is asked, causes management user to be forced to publish or can not access.
In a kind of possible implementation, the preset strategy is：In wait access queue to the shared resource
Destination request side send second authentication information.It is described to wait access queue to be asked according to the access to the shared resource
Ask what is established, wherein the information of the requesting party of the shared resource to be visited such as containing, for example, the mark letter of requesting party
Breath, ask time of access etc..Correspondingly, as shown in figure 4, management module 220 can further comprise：
First determining unit 221, for determining the wait access queue.
In the device of the embodiment of the present invention, it is determined that waiting access queue to may include (such as to manage from the outside of management equipment
Manage the server of the shared resource) situation of wait access queue established and/or updated is obtained, it is additionally included in management and sets
It is standby to be locally created and/or update the situation for waiting access queue.
Second determining unit 222, for determining at least one destination request side.
Determine it is described wait access queue after, management user by the second determining unit 222 from the queue according to
Certain rule determines destination request side.
In the device of the embodiment of the present invention, the second determining unit 222 determines that the rule of the wait access queue can wrap
Include a variety of：
Time according at least one access request determines the wait access queue.For example, according to it is described at least
The time of one access request after arriving first, is arranged in order requesting party from head of the queue to tail of the queue, that is, often receiving a new access
Request, corresponding requesting party is come to the tail of the queue of the wait access queue.Now, the second determining unit 222 is suitable according to the time
Sequence determines at least one destination request side.
Priority according to requesting party determines the wait access queue.For example, according to requesting party's priority from high to low,
Requesting party is arranged in order from head of the queue to tail of the queue, that is, the minimum requesting party of priority to be come to the team of the wait access queue
Tail.The priority of requesting party can be determined by managing user, or pre-set, and may determine that according to the identification information of requesting party
The priority of requesting party, or corresponding precedence information is directly contained in access request.Now, the second determining unit 222
Priority according to requesting party determines the destination request side.
The team to be visited such as described is determined according to the time sequencing of at least one access request and the priority of requesting party
Row.For example, requesting party is arranged in order from head of the queue to tail of the queue, together after arriving first according to the time of at least one access request
The height of requesting party according to priority in one period arranges from front to back.Or according to requesting party's priority from high to low, from
Head of the queue is arranged in order requesting party 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
Row.Now, the second determining unit 222 considers the time sequencing of at least one access request and the priority of requesting party
Determine the destination request side.Management module 220, can while the second authentication information is sent to the higher requesting party of priority
Inform that the access request of its requesting party first to access request responds
In the device of the embodiment of the present invention, the second determining unit 222 determines that the rule of the destination request side can also have
It is a variety of.For example, arriving the order of tail of the queue (head of the queue) according to the head of the queue (tail of the queue) of the wait access queue, request time is chosen at first
One requesting party of (rear) and/or highest priority (low) is destination request side.Asked further for example, being chosen in special time period
A requesting party for accessing the shared resource is destination request side；Or choose a requesting party with certain priority and be
Destination request side.
In response to the arrival at default time span/default time point, the second determining unit 222 is complete according to what is received
Portion's access request determines the destination request side.It may also be responsive in the access request for receiving some specific requesting party, it is determined that or
Redefine the destination request side.For example, after receiving the access request of the requesting party with higher priority, redefine
The requesting party of the higher priority is destination request side.
In addition, in a kind of possible implementation, can after the second determining unit 222 determines the destination request side
In response to the first authentication information can be used to access the shared resource, second authentication information is sent, receives described the
The requesting party of two authentication informations turns into management user.In alternatively possible implementation, it may be in response to determine the target
Requesting party sends second authentication information.For example, after determining the destination request side, immediately by second authentication information
The destination request side is sent to, now, user is managed and receives the requesting party of second authentication information and continue waiting for
The shared resource is able to access that, receiving the requesting party of the second authentication information turns into management user, and the two, which feels to wait, works as
The preceding user for taking the shared resource accesses the shared resource successively again after stopping using the shared resource；Or because of mirror
The limitation of the priority of information is weighed, before the shared resource is not released, the two can not be accessed.
For specific requesting party, (the specific requesting party may have the higher or highest for accessing the shared resource
Priority), regardless of whether have determined that the destination request side, management module 220 may be in response to receive described specific
The access request of requesting party sends the authentication information of limit priority to the specific requesting party immediately so that described specific
Requesting party can access the shared resource at once.
In addition, within the period for not determining destination request side, the message that management user needs response to receive safeguards institute
State wait access list.Correspondingly, as shown in figure 5, the device 200 of the embodiment of the present invention also includes：
Update module 240, for updating the wait access queue.
In the device of the embodiment of the present invention, request accesses the user of the shared resource by sending the side of access request
Formula is added to the wait access queue；User in the wait access queue can also be sent by active cancels what is waited
To inform management user, it cancels the behavior waited to message.Update module 240 in response to receive access request, cancel wait
The renewal such as the message wait access queue.Correspondingly, the device of the embodiment of the present invention can include described in reception at least respectively
One access request and the receiving module 250 for cancelling the message waited.
In order to provide relatively good Consumer's Experience to user (user for being especially to wait for accessing), as shown in fig. 6, this hair
The device of bright embodiment also includes：
First broadcast module 260, access queue is waited described in periodic broadcast.And/or
Second broadcast module 260 ', for broadcasting the team to be visited such as described in response to the renewal of the wait access queue
Row.
By broadcasting the wait access queue, the user for wanting or waiting the shared resource to be visited can be allowed to understand institute
State the occupancy situation of shared resource and wait situation, so as to provide the reference further selected for each user.
It should be noted that above-mentioned each functional module that sending function is performed in the device of the embodiment of the present invention can be same
Individual module, the above-mentioned functional module for performing receive capabilities is alternatively same module, herein not as to the embodiment of the present invention
The limitation of device.
The method and device of various embodiments of the present invention is further illustrated below by instantiation.
Example one
User's first is failed using shared account access target database by default password, uses the embodiment of the present invention
Method and device, user's first broadcast access request simultaneously receive first password, turn into the management user of the shared account.User
Access failure will be told in second when logging in the shared account using default password.Now, user's first will receive user's second
Access request, established in response to the access request received and wait access queue, user's second is added to described by user's first
In access queue and the second password is sent to, the priority of the second password is less than first password, and now, user's second turns into described
The management user of shared account.User's first is used after the message of current accessed user stopping access being received using first password
The shared account.Other management users are by that analogy.
Example two
User's first is failed using shared account access target database by default password, uses the embodiment of the present invention
Method and device, user's first broadcast access request simultaneously receive first password, turn into the management user of the shared account.User
Access failure will be told in second when logging in the shared account using default password.Now, user's first will receive user's second
Access request, established in response to the access request received and wait access queue.In the first-class data to be visited of user
During storehouse, it receives user third, Yong Huding, the access request of user penta successively, and according to the priority successively by user
Fourth, Yong Hubing, user penta are added to the tail of the queue for waiting access queue.User's first often updates wait access queue, i.e. broadcast renewal
Wait access queue afterwards, Yong Huyi, Yong Hubing, Yong Huding, user penta can know the occupancy situation of the shared account.With
Family second is actively cancelled for some reason to be waited, and in response to this, user's first updates the access waiting list and broadcasts the team after renewal again
Row.After a period of time of the database to be visited is waited, the user's fourth for determining the wait access queue head of the queue is user's first
Destination request side, the second password is sent to user's fourth and informs that request of user's fourth to user third responds, user's fourth into
For the current management user of the account, and can preferred user third send the target of " the second password " for it.Current accessed user
When stopping accessing the database, first password can be used to access the database for user's first, and other management users are by that analogy.
Example three
In the situation of example one, user's first turns into the management user of the shared account and it is determined that user's second is
After destination request side, the second password is sent to user's second immediately.Received during the first-class database to be visited of user
The access request of specific user's second, user's second use user for the limit priority of the shared account, and now, user's first determines
User's second is destination request side, and is sent to the password of limit priority, and user's second turns into the current pipe of the shared account
Manage user.User's first can notify or not notify this variation of user's second.
Fig. 7 is the structural representation for another resource access device 700 that present aspect embodiment provides, and the application is specifically real
Specific implementation of the example not to resource access device 700 is applied to limit.As shown in fig. 7, the resource access device 700 can wrap
Include：
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 being communicated with the network element of such as client etc..
Processor 710, for configuration processor 732, it can specifically perform the correlation step in above method embodiment.
Specifically, program 732 can include program code, and described program code includes computer-managed instruction.
Processor 710 is probably a central processor CPU, or specific integrated circuit ASIC (Application
Specific Integrated Circuit), or it is arranged to implement the integrated electricity of one or more of the embodiment of the present application
Road.
Memory 730, for depositing program 732.Memory 730 may include high-speed RAM memory, it is also possible to also include
Nonvolatile memory (non-volatile memory), for example, at least a magnetic disk storage.Program 732 can specifically be used
Following steps are performed in causing the resource access device 700：
In response to accessing shared resource failure, the first authentication information of the shared resource is obtained；
According at least one access request to the shared resource received, sent according to preset strategy described shared
Second authentication information of resource.
Corresponding to the specific implementation of each step may refer in corresponding steps and the unit in above-described embodiment in program 732
Description, will not be described here.It is apparent to those skilled in the art that for convenience and simplicity of description, it is above-mentioned to retouch
The equipment and the specific work process of module stated, the corresponding process description in preceding method embodiment is may be referred to, herein no longer
Repeat.
Those of ordinary skill in the art are it is to be appreciated that the list of each example described with reference to the embodiments described herein
Member and method and step, it can be realized with the combination of electronic hardware or computer software and electronic hardware.These functions are actually
Performed with hardware or software mode, application-specific and design constraint depending on technical scheme.Professional and technical personnel
Described function can be realized using distinct methods to each specific application, but this realization is it is not considered that exceed
Scope of the present application.
If the function is realized in the form of SFU software functional unit and is used as independent production marketing or in use, can be with
It is stored in a computer read/write memory medium.Based on such understanding, the technical scheme of the application is substantially in other words
The part to be contributed to prior art or the part of the technical scheme can be embodied in the form of software product, institute
State computer software product to be stored in a storage medium, including some instructions are causing a computer equipment (can be with
It is personal computer, server, or network equipment etc.) perform all or part of step of each embodiment methods described of the application
Suddenly.And foregoing storage medium includes：USB flash disk, mobile hard disk, read-only storage (ROM, Read-Only Memory), deposit at random
Access to memory (RAM, Random Access Memory), magnetic disc or CD etc. are various can be with the medium of store program codes.
Embodiment of above is merely to illustrate the application, and is not the limitation to the application, about the common of technical field
Technical staff, in the case where not departing from spirit and scope, it can also make a variety of changes and modification, thus it is all
Equivalent technical scheme falls within the category of the application, and the scope of patent protection of the application should be defined by the claims.
Claims (43)
1. a kind of resource access method, it is characterised in that applied to first terminal, methods described includes：
The first terminal from shared resource server or takes the shared resource in response to accessing shared resource failure
Terminal, obtain the first authentication information of the shared resource；
At least one access request to the shared resource that the first terminal is sent according to the second terminal received, is pressed
The second authentication information of the shared resource is sent to second terminal according to preset strategy.
2. according to the method for claim 1, it is characterised in that it is described in response to accessing shared resource failure, from shared money
Source server or the terminal for taking the shared resource, the first authentication information of the shared resource is obtained, including：
In response to accessing shared resource failure, to shared resource server or the terminal of the occupancy shared resource, transmission pair
The access request of the shared resource；
Receive the shared resource server or take the first authentication information that the terminal of the shared resource is sent.
3. according to the method for claim 1, it is characterised in that the preset strategy is：
Destination request side in wait access queue to the shared resource sends second authentication information.
4. according to the method for claim 3, it is characterised in that second terminal that the basis receives send to described
At least one access request of shared resource, the second authentication for sending the shared resource to second terminal according to preset strategy are believed
Breath, including：
Determine the wait access queue.
5. according to the method for claim 4, it is characterised in that second terminal that the basis receives send to described
At least one access request of shared resource, the second authentication for sending the shared resource to second terminal according to preset strategy are believed
Breath, including：
Determine the destination request side.
6. according to the method for claim 5, it is characterised in that described to determine in the wait access queue：
Time sequencing according at least one access request determines the wait access queue；
It is described to determine in the destination request side：
The destination request side is determined sequentially in time.
7. according to the method for claim 6, it is characterised in that described to determine in the wait access queue：
According to the time of at least one access request after arriving first, requesting party is arranged in order from head of the queue to tail of the queue.
8. according to the method for claim 5, it is characterised in that described to determine in the wait access queue：
Priority according to requesting party determines the wait access queue；
It is described to determine in the destination request side：
Priority according to the requesting party determines the destination request side.
9. according to the method for claim 8, it is characterised in that described to determine in the wait access queue：
According to requesting party's priority from high to low, requesting party is arranged in order from head of the queue to tail of the queue.
10. according to the method for claim 5, it is characterised in that described to determine in the wait access queue：
The wait access queue is determined according to the time sequencing of at least one access request and the priority of requesting party；
It is described to determine in the destination request side：
The destination request side is determined according to the time sequencing of at least one access request and the priority of requesting party.
11. according to the method for claim 10, it is characterised in that described to determine in the wait access queue：
According to the time of at least one access request after arriving first, requesting party is arranged in order from head of the queue to tail of the queue, with for the moment
Between the height of requesting party according to priority in section arrange from front to back.
12. according to the method for claim 10, it is characterised in that described to determine in the wait access queue：
According to requesting party's priority from high to low, requesting party is arranged in order from head of the queue to tail of the queue, the requesting party of same priority presses
Arranged from front to back according to the time order and function of access request.
13. the method according to any one of claim 6 to 12, it is characterised in that described to determine the destination request side
In：
It is determined that the requesting party for waiting access queue head of the queue is the destination request side.
14. the method according to any one of claim 5 to 12, it is characterised in that the second end that the basis receives
At least one access request to the shared resource sent is held, the shared money is sent to second terminal according to preset strategy
In second authentication information in source：
In response to determining that the destination request side sends second authentication information.
15. the method according to any one of claim 4 to 12, it is characterised in that methods described also includes：
Update the wait access queue.
16. according to the method for claim 15, it is characterised in that in the renewal wait access queue：
The wait access queue is updated in response to receiving access request.
17. according to the method for claim 16, it is characterised in that methods described also includes：
Receive the message cancelled and waited.
18. according to the method for claim 17, it is characterised in that in the renewal wait access queue：
In response to receiving to cancel access queue is waited described in the information updating waited.
19. the method according to any one of claim 3 to 12, it is characterised in that methods described also includes：
The wait access queue is broadcasted in renewal in response to the wait access queue.
20. the method according to any one of claim 3 to 12, it is characterised in that methods described also includes：
Access queue is waited described in periodic broadcast.
21. the method according to any one of claim 1 to 12, it is characterised in that methods described also includes：
Determine second authentication information.
22. according to the method for claim 21, it is characterised in that second authentication information and first authentication information
It is identical.
23. according to the method for claim 21, it is characterised in that the priority of second authentication information is less than described the
The priority of one authentication information.
24. a kind of resource access device, it is characterised in that applied to first terminal, described device includes：
One acquisition module, for the first terminal in response to accessing shared resource failure, from shared resource server or account for
With the terminal of the shared resource, the first authentication information of the shared resource is obtained；
One management module, for the first terminal according to the second terminal that receives send to the shared resource at least
One access request, the second authentication information of the shared resource is sent to second terminal according to preset strategy.
25. device according to claim 24, it is characterised in that the acquisition module includes：
One transmitting element, in response to accessing shared resource failure, sending the access request to the shared resource；
One receiving unit, for receiving first authentication information.
26. device according to claim 24, it is characterised in that the management module includes：
One first determining unit, for determining the wait access queue of the shared resource.
27. device according to claim 26, it is characterised in that the management module includes：
One second determining unit, for determining destination request side.
28. device according to claim 27, it is characterised in that first determining unit is according at least one visit
Ask that the time sequencing of request determines the wait access queue；
Second determining unit determines the destination request side sequentially in time.
29. device according to claim 28, it is characterised in that first determining unit is according at least one visit
Ask that the time of request after arriving first, is arranged in order requesting party from head of the queue to tail of the queue.
30. device according to claim 27, it is characterised in that first determining unit according to requesting party priority
Determine the wait access queue；
Second determining unit determines the destination request side according to the priority of the requesting party.
31. device according to claim 30, it is characterised in that first determining unit according to requesting party's priority from
It is high to Low, requesting party is arranged in order from head of the queue to tail of the queue.
32. device according to claim 27, it is characterised in that first determining unit is according at least one visit
Ask that the time sequencing of request and the priority of requesting party determine the wait access queue；
Second determining unit determines institute according to the time sequencing of at least one access request and the priority of requesting party
State destination request side.
33. device according to claim 32, it is characterised in that first determining unit is according at least one visit
The time of request is asked after arriving first, requesting party is arranged in order from head of the queue to tail of the queue, the requesting party in the same period is according to priority
Height arrange from front to back.
34. device according to claim 32, it is characterised in that first determining unit according to requesting party's priority from
It is 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 according to access request time order and function from
Front to back arranges.
35. the device according to any one of claim 28 to 34, it is characterised in that described second determining unit determination etc.
The requesting party of queue head of the queue to be visited is the destination request side.
36. the device according to any one of claim 27 to 34, it is characterised in that the management module is in response to determining
The destination request side sends second authentication information.
37. the device according to any one of claim 26 to 34, it is characterised in that described device also includes：
One update module, for updating the wait access queue.
38. the device according to claim 37, it is characterised in that the update module is in response to receiving access request more
The new wait access queue.
39. the device according to claim 38, it is characterised in that described device also includes：
One receiving module, cancel the message waited for receiving.
40. the device according to claim 39, it is characterised in that the update module cancels what is waited in response to receiving
Access queue is waited described in information updating.
41. the device according to any one of claim 26 to 34, it is characterised in that described device also includes：
One first broadcast module, for broadcasting the wait access queue in response to the renewal of the wait access queue.
42. the device according to any one of claim 26 to 34, it is characterised in that described device also includes：
One second broadcast module, for waiting access queue described in periodic broadcast.
43. the device according to any one of claim 24 to 34, it is characterised in that described device also includes：
One determining module, for determining 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 CN103973691A (en) | 2014-08-06 |
| CN103973691B true 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) |
Families Citing this family (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 |
| CN106851123B (en) | 2017-03-09 | 2020-12-22 | Oppo广东移动通信有限公司 | Exposure control method, exposure control device and electronic device |
| CN109391588B (en) * | 2017-08-04 | 2021-03-12 | 北京国双科技有限公司 | Request processing method and device |
| CN109587183B (en) * | 2017-09-28 | 2021-06-29 | 北京国双科技有限公司 | Request processing method and device |
Citations (4)
| 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 |
| 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 |
Family Cites Families (1)
| 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 |
-
2014
- 2014-05-09 CN CN201410196889.5A patent/CN103973691B/en active Active
Patent Citations (4)
| 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 |
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103973691A (en) | 2014-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103973691B (en) | Resource access method and resource access device | |
| US9853906B2 (en) | Network prioritization based on node-level attributes | |
| US9264369B2 (en) | Technique for managing traffic at a router | |
| CN112039942A (en) | Subscription and publishing method and server | |
| CN108173938A (en) | Server load shunt method and device | |
| CN110365752A (en) | Processing method, device, electronic equipment and the storage medium of business datum | |
| CN104158818B (en) | A kind of single-point logging method and system | |
| WO2013159750A1 (en) | Cloud-storage-based file processing method and system | |
| CN109510878B (en) | Long connection session keeping method and device | |
| CN105095130B (en) | Information processing equipment, system and information processing method | |
| CN103973690B (en) | Resource access method and resource access device | |
| CN101163117A (en) | Packet management method, packet resource sharing method and instant communication equipment | |
| CN109150745A (en) | A kind of message processing method and device | |
| CN110460978A (en) | A kind of method and apparatus of resource access | |
| CN108027802A (en) | Data exchange is write twice in the network architecture of dead point | |
| CN107659573A (en) | Control method and device of vehicle-mounted system | |
| CN110191131A (en) | A kind of file sharing method, device, system, server and storage medium | |
| CN103491193A (en) | Method and device for sharing file | |
| CN105049463B (en) | Disperse database, data sharing method, the device for disperseing database | |
| US8949344B2 (en) | Asynchronous queued messaging for web applications | |
| CN105519055A (en) | Dynamic equilibrium method and apparatus for QoS of I/O channel | |
| KR101042244B1 (en) | Method and System for Managing Quality of Experience of Service in Wired and Wireless Communication Network | |
| CN110381537A (en) | A kind of bandwidth speed limiting method, apparatus, equipment and storage medium based on QoE | |
| CN110247808A (en) | Method for sending information, device, equipment and readable storage medium storing program for executing | |
| CN106550492B (en) | The method and mobile terminal of data transfer between a kind of mobile terminal |
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 |