CN101090389B - Method and system for implementing permission protocol between equipment - Google Patents
Method and system for implementing permission protocol between equipment Download PDFInfo
- Publication number
- CN101090389B CN101090389B CN2006100839587A CN200610083958A CN101090389B CN 101090389 B CN101090389 B CN 101090389B CN 2006100839587 A CN2006100839587 A CN 2006100839587A CN 200610083958 A CN200610083958 A CN 200610083958A CN 101090389 B CN101090389 B CN 101090389B
- Authority
- CN
- China
- Prior art keywords
- permission
- source device
- equipment
- candidate
- requesting service
- 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
Images
Abstract
This invention discloses a method for realizing permission negotiation among equipment, in which, a request device getting permission obtains formal permission from a source device issuing permission and stores the negotiation information and is registered as a proxy device of permitted negotiations, the succeeded request devices select a proxy device from the registered ones to negotiate and informs the negotiation result to the source device, which issues permission to the request device. This invention also discloses a permission management system.
Description
Technical field
The present invention relates to the digital copyright management field, particularly relate to the method and system of between equipment, realizing permission protocol.
Background technology
Along with becoming stronger day by day of terminal capability, increasing people begins oneself to make and share digital content with other people.These digital contents need copyright management, and for example the somebody may wish to obtain certain expense there or wish that own works are shared and watch in a period of time from other people that watch own works.It is that it provides permission that the individual can authorize the service provider; for example the service provider safeguards a website; individual subscriber is uploaded the works of oneself; the user who downloads certain content selects and downloads suitable permission by this website; like this, but by the digital content that provides of individual in the digital copyright management protecting network.
Digital copyright management is a copyright protection technology at digital content, thereby prevents effectively by network and computer bootlegging, copy, transmission digital content.The publisher of digital content uploads to network after with encrypt digital content, and the user is if use digital content, must and obtain the permission of this digital content to the rights issuer request, comprises relevant key in the permission, can be used for deciphering to obtain digital content; Comprise use right and service condition to content simultaneously in the permission, terminal can only satisfy under the situation of service condition according to using right to use digital content.
Consult permission mutually by website or agreement between equipment and the server, for example the user selects an existing permission or select relevant parameters on webpage by webpage, customizes a special permission.
In these cases, in the service provider grasped, the individual can only depend on the trust to the service provider fully for information that permission is provided and control, and can't oneself control the distribution of permission.Along with the rise of P2P technology, the content on the shared own equipment that the individual can be convenient.Same, the individual also needs to make by equipment and oneself also can provide permission, thus the quantity and the type of can own control permitting.
At present, each equipment that asks for permission all needs and provides the source device of permitting and carry out permission protocol, along with the individual can cause the load pressure of source device more and more heavier, thereby influence service quality by equipment granting permission, even causes the source device collapse.In addition, in negotiations process,, cause between the equipment interaction times too much, bring excessive load pressure to source device if consult to lead to divergence then can only restart negotiations process.
Summary of the invention
The invention provides a kind of method and system of between equipment, realizing permission protocol, too much cause the source device load pressure excessive and influence the problem of service quality to solve to ask for permission in the prior art.
Further solve and have when leading to divergence in the negotiations process that interaction times too much causes the excessive problem of source device load pressure between the equipment.
Side of the present invention provides following technical scheme,
A kind of method that realizes permission protocol between equipment comprises the steps:
The requesting service that need secure permission obtains to preserve negotiation information after the formal license from the source device that is used to provide permission, and is registered as the agent equipment of permission protocol;
Follow-up requesting service selects an agent equipment to carry out permission protocol from registered agent equipment, and negotiation result is notified described source device after consulting successfully;
Described source device is permitted to described follow-up requesting service granting according to described negotiation result.
According to said method:
The requesting service that obtains formal license with the separate service equipment of described source device on be registered as agent equipment, follow-up requesting service selects agent equipment to carry out permission protocol from this service equipment; Perhaps
The requesting service that obtains formal license is registered as agent equipment on described source device, follow-up requesting service selects agent equipment to carry out permission protocol from this source device.
Further with candidate's notification of permit source device of consulting, source device determines that this candidate's permission meets the requirements the back to follow-up requesting service granting formal license after consulting successfully.
Described candidate's permission is provided by follow-up requesting service, and proxied device is accepted in negotiations process; Perhaps, described candidate's permission is provided by agent equipment, and is accepted by follow-up requesting service in negotiations process.
Source device determines that described candidate permits when undesirable, further sends candidate's permission that this source device provides to follow-up requesting service, indicates it to consult again.
Carry the type information of permission in permission, equipment determines that according to the type information permission is formal license or is candidate's permission in negotiations process.
A kind of license management system comprises:
Source device is used for carrying out permission protocol with other equipment, and is responsible for providing permission;
Service equipment, the device registration that is used for obtaining formal license is to act on behalf of the agent equipment that source device carries out permission protocol;
Agent equipment is used to replace described source device to finish permission protocol, and this agent equipment obtains formal license from described source device;
Requesting service be used for selecting agent equipment to carry out permission protocol from described service equipment, and the back secures permission from described source device consulting successfully.
The separate setting of described source device and service equipment; Perhaps, described source device and service equipment are set to one.
Beneficial effect of the present invention is as follows:
Carry out registering apparatus as agent equipment by the present invention's handle to server, the equipment that other requests are secured permission need not be held consultation with the equipment of providing permission, just can carry out permission protocol by agent equipment, so just reduce request equipment that secures permission and the interaction times of providing permitted device, alleviated the pressure of providing the equipment of permission.If difference takes place when consulting, needn't redefine a cover metadata expression method and permission create-rule between requesting party and the recipient by in candidate's licence list, revising the content of permission, making, simplified negotiation step.
Description of drawings
Fig. 1 is a networking schematic diagram of realizing the permission protocol system in the embodiment of the invention between the equipment;
Fig. 2 is a permission protocol basic flow sheet in the embodiment of the invention;
Fig. 3 A, Fig. 3 B, Fig. 3 C are the equipment that secures permission of request and the equipment of the providing permission flow chart of holding consultation in the embodiment of the invention;
Fig. 4 A, Fig. 4 B, Fig. 4 C be in the embodiment of the invention equipment that secures permission of request by the agent equipment flow chart of holding consultation;
Fig. 5 is a device processes license request flow chart of providing permission in the embodiment of the invention;
Fig. 6 permits flow chart for the device processes candidate that request in the embodiment of the invention secures permission;
The device processes formal license flow chart that Fig. 7 secures permission for request in the embodiment of the invention;
Fig. 8 realizes the permission protocol flow chart between the equipment in the embodiment of the invention.
Embodiment
At at present in digital copyright management, the requesting service that request secures permission is too frequent with the interaction times of the source device of providing permission, cause the source device problems such as over-burden of providing permission, the present invention obtains to be registered as agent equipment after the formal license from source device at requesting service, the requesting service that other follow-up needs secure permission selects these agent equipments to carry out permission protocol, and provides formal license by source device after consulting successfully.Described permission protocol is meant the right that comprised of permission and the negotiation of restriction, can plays how many times such as content, the number etc. of at every turn paying.When the recipient disagrees with the other side's permission, can in permission, add the information of consulting.
Referring to shown in Figure 1, the license management system in the present embodiment comprises source device, server, agent equipment and requesting service.Source device is used for carrying out permission protocol with requesting service, and provides permission to consulting successful request; The device registration that server is used for obtaining formal license is to act on behalf of the agent equipment that source device carries out permission protocol; Agent equipment is used to replace source device to finish permission protocol; Requesting service selects agent equipment to carry out permission protocol from the tabulation of the agent equipment of described server, consults successfully that the back obtains formal license from the equipment of providing permission, thus the digital content of use correspondence.Described server can be one or more independently network entities, also can be born the function of enrollment proxy equipment by source device.At least include the address of each equipment in the agent equipment tabulation, also can comprise other relevant informations; Agent equipment in the described tabulation can comprise source device.
Consult shown in Figure 2ly, requesting service obtains formal license and carries out the main flow process of permission protocol as agent equipment as follows from source device in the present embodiment:
Step 200, the requesting service A that need secure permission and source device carry out permission protocol.
Step 210, consult successfully after, source device is provided formal license to requesting service A, the information when requesting service A preserves and carries out permission protocol with source device.
Step 220, requesting service A be to server registers, by server requesting service A recorded in the address list of agent equipment (to call device A in the following text).
Step 230, requesting service B are to the address list of server requests agent equipment.
Step 240, server are tabulated to requesting service B return address.
Step 250, equipment B select to select device A from address list, information and equipment B when the device A basis is held consultation with source device are carried out permission protocol.
After step 260, the permission protocol success, source device is provided formal license to equipment B.
Under initial condition, except source device has formal license, other equipment also do not obtain formal license, and this moment, requesting service can only be by carrying out permission protocol obtaining formal license with source device, and Fig. 3 A has shown the process that the requesting service A that need get a license and source device are held consultation:
Step 300, requesting service A send the message that asks for permission to source device, comprise candidate's permission that requesting service generates in this permission request message.
If requesting service A can not generate candidate's permission or not provide the candidate to permit, then the content of candidate's permission is empty.
After step 301, source device are received request message, judge that according to consulting tactical not accepting the candidate permits, and generate one or more candidates' permissions, join in candidate's licence list according to consulting tactical.
If the candidate's licensed content in the request message is empty, the one or more candidate's permissions that then will give tacit consent to join in candidate's licence list the equipment that the request of sending to secures permission.
Step 302, requesting service A do not accept candidate's permission that source device provides, and then revise candidate's licensed content according to consulting tactical and generate new candidate's permission to send to source device, duplicate negotiation loops process.
Step 310, requesting service A and source device carry out repeatedly mutual after, send the message that asks for permission to source device once more.
Step 311, source device are permitted according to the candidate that consulting tactical has received requesting service A, provide a formal license to requesting service A.
It is consistent that step 312, requesting service A check that the candidate of formal license and acceptance permits, installation license also sends acknowledge message to source device.If confirm inconsistently, then abandon permission, consult again or interrupt negotiations process.Certainly, requesting service A can not send acknowledge message to source device yet.
To 323, after then having provided requesting service A and accepting candidate's permission that source terminal provides, notification source equipment is accepted this permission in step 320, and source device generates formal license and returns to requesting service A; It is consistent that requesting service A checks that the candidate of formal license and acceptance permits, installation license also sends acknowledge message to source device.If confirm inconsistently, then abandon permission, consult again or interrupt negotiations process.
In the duplicate negotiation loops process, both sides can make amendment to the content in candidate's licence list according to the type of permission, and repetitive process can be made amendment each time.But both sides also might indefinite holding consultation, in order to prevent the generation of this situation, consult both sides and can in consulting tactical, stipulate maximum negotiation number of times separately, if surpassed the number of times that sets, then send the negotiation failure, stop this negotiation to the other side.A side who consults can also send the candidate's permission that can not revise to the opposing party, and the recipient can only select to accept or refuse this permission, if refusal then notifies the other side to finish this negotiation.
Consult shown in Fig. 3 B, after requesting service and source device are repeatedly consulted, when requesting service once more after source device sends the message that asks for permission, source device judges is consulted the number of times of number of times greater than regulation, decision stops to consult, and sends to requesting service and consults failed message.
Consult shown in Fig. 3 C, after requesting service and source device were repeatedly consulted, after source device sent the candidate that can not revise to requesting service, requesting service was not accepted candidate's permission, sent to source device and consulted failed message, and decision stops to consult.
Consult shown in Fig. 4 A, requesting service and agent equipment carry out permission protocol, and by agent equipment that the main processing procedure of negotiation result notification source equipment is as follows:
Step 410, requesting service select agent equipment to carry out permission protocol from server.
Candidate's permission that step 411, the agent equipment equipment of accepting request provide is consulted successfully, and with negotiation result notification source equipment.
Step 412, source device check that candidate's permission that agent equipment is accepted meets the requirements, and returns a formal license to requesting service.This permission is directly issued requesting service by source device, and when adopting this mode, agent equipment is with the address notification source device of requesting service in step 411; Perhaps, send to agent equipment, be transmitted to requesting service by agent equipment by source device.
In this step, if definite undesirable, then send new candidate's licence list to requesting service according to consulting tactical, restart negotiation or send the negotiation failure to requesting service, finish this negotiation.Again the negotiations process requesting service can directly carry out also can carrying out indirectly alternately by agent equipment alternately with source device.
It is consistent that step 413, requesting service check that the candidate of formal license and acceptance permits, formal license is installed and returns acknowledge message, finishes negotiations process.Acknowledge message can directly send to source device, also can be transmitted to source device by agent equipment.Certainly, can not send acknowledge message to source device yet.
If inconsistent, then abandon formal license, and consult failure to new permission of source device request or transmission, finish this negotiation.This negotiation failure can directly send to source device, also can be transmitted to source device by agent equipment.Certainly, can not send the negotiation failure to source device yet.
Consult shown in Fig. 4 B, requesting service and agent equipment carry out permission protocol, and by requesting service that the main processing procedure of negotiation result notification source equipment is as follows:
Step 450, requesting terminal select agent equipment to carry out permission protocol from server.
The candidate's permission that terminal provides that accepts request of step 451, agent equipment sends to requesting service and to accept grant message.
Step 452, requesting service are with negotiation result notification source equipment.
Step 453, source device check that candidate's permission of accepting in the negotiations process meets the requirements, and returns a formal license to requesting service.
If undesirable, then send new candidate's licence list to requesting service according to consulting tactical, restart negotiation or send the negotiation failure to requesting service, finish this negotiation.Again the negotiations process requesting service can directly carry out also can carrying out indirectly alternately by agent equipment alternately with source device.
It is consistent that step 454, requesting service check that the candidate of formal license and acceptance permits, formal license is installed and returns acknowledge message, finishes negotiations process.Certainly, can not send acknowledge message to source device yet.
If inconsistent, then abandon formal license, and consult failure to new permission of source device request or transmission, finish this negotiation.
Among Fig. 4 A and Fig. 4 B, accept candidate's permission by agent equipment, step 470 at Fig. 4 C arrives step 473, provided by requesting service and accepted candidate's permission and direct processing procedure negotiation result notification source equipment, when requesting service is directly with negotiation result notification source equipment, also can send the message that finishes negotiation, certainly, also can not send this message to agent equipment.All the other flow processs and in like manner above-mentioned repeat no more.
But requesting service is accepted after the candidate permission also notification agent equipment in Fig. 4 C flow process, by agent equipment with negotiation result notification source equipment, all the other flow processs that adopt this mode all with Fig. 4 A in like manner, repeat no more.
Present embodiment represents by increase type information in permission what kind of modification negotiations process and prompting recipient can make to candidate's licence list content in the permission protocol process.The type of permission is divided into: formally, unofficially can revise, unofficially can not revise and accepted four kinds.As shown in the table:
| Type | Explanation |
| Formally | Represent that this permission is the permission of a formal issue, terminal can only use the permission of the type to come consumption digital content. |
| Unofficially can revise | Represent that this permission is candidate's permission of using in the negotiations process, the recipient continues to consult after can making amendment to this permission. |
| Unofficially can not revise | Represent that this permission is candidate's permission of using in the negotiations process, the recipient can not revise this permission, can only accept or refuse. |
| Accept | Represent that this permission is candidate's permission of using in the negotiations process, and this permission is accepted by a side. |
Any equipment can only type of service be the permission of " formally " all when consumption digital content, such permission has comprised the key of decrypts digital content, and do not comprise key information in the permission of other types, so just guarantee that terminal can't utilize the candidate in the negotiations process to permit consumption digital content, and also can reduce unnecessary data amount when consulting.Permission for there not being types of elements generally is defaulted as " formally " permission.
Type is used for making the recipient that candidate's permission is made amendment for the permission of " unofficially can revise ".Such as: the type of transmit leg transmission candidate's permission and this permission is " unofficially can revise " in negotiations process, if the recipient disagrees with this permission, then the recipient can make amendment to this permission, returns amended permission to the other side again.
Type stops negotiations process for the permission of " unofficially can not revise " with a side who helps consult.Such as: source device can be stipulated the interaction times of a negotiations process maximum in consulting tactical, when reaching maximum, this equipment sends the candidate permission of a type for " unofficially can not revise " to requesting service.Thereby requesting service can only be selected to accept this permission and finish this negotiation or refuse this permission and stop this negotiation.
Type is accepted certain candidate's permission of granting last time for the permission of " accepting " with helping requesting terminal notification source terminal or proxy terminal, and its license ID should be identical with the license ID of this candidate's permission.
The example of the method for expressing of a license type following (but being not limited to this):
＜permission 〉
＜license ID〉12345678＜/license ID 〉
＜type〉unofficially can revise＜/type 〉
＜content〉lucky Triratna .mp3＜/content 〉
＜right 〉
Play
＜restriction 〉
＜number of times〉10＜/number of times 〉
＜expense〉1 yuan＜/expense 〉
＜/restriction 〉
＜/right 〉
＜digital signature〉oweiurq98qhajgh＜/digital signature 〉
＜/permission 〉
This candidate's permissions specify the cost monobasic can play this first MP3 of lucky Triratna 10 times, and license type is unofficially can revise, if the recipient disagrees with this candidate's permission, then can make amendment to the content of candidate's permission, such as: broadcasting time and expense.
Similarly, transmit leg can increase type sub-element or attribute under each right or constraint element, be used for representing this right or the restriction can revise, increase or delete.Such as:
＜permission 〉
＜license ID〉12345678＜/license ID 〉
＜type〉unofficially can revise＜/type 〉
＜content〉lucky Triratna .mp3＜/content 〉
＜right 〉
Play
＜Limit Type: can increase/unsuppressible-suppression 〉
＜number of times type: can not revise〉10＜/number of times 〉
＜expense〉1 yuan＜/expense 〉
＜/restriction 〉
＜/right 〉
＜digital signature〉oweiurq98qhajgh＜/digital signature 〉
＜/permission 〉
The recipient of this candidate's permission can increase new restriction, and can hold consultation with regard to expense, but can not revise the number of times restriction.Type under the different elements has different semantic and different default values, and the type of daughter element only just works when license type is " unofficially can revise ", and is in negotiations process, inoperative to the permission of other types.
Consult shown in Figure 5ly, the main processing procedure of source device side is as follows in the permission protocol process:
Step 500, source device are received the permission request message that other-end sends.
Step 501, source device are resolved request message, judge whether to comprise candidate's permission in this message, if comprise then execution in step 502; Otherwise execution in step 511.
Step 502, source device judge that by resolving types of elements in the permission whether this value is " accepting " if " acceptance " illustrates that then requesting service accepted this candidate and permitted execution in step 503; Otherwise, execution in step 509.
Step 503, source device are searched candidate's permission of the preservation identical with candidate's license ID of sending.But in some cases, can not find corresponding candidate's permission.Such as: the candidate of preservation permits buffering area full, and corresponding candidate permits candidate's permission deleted or that send to be consulted to generate by agent equipment and requesting service, in the not corresponding candidate's permission of source device.
Whether step 504, source device judges find corresponding candidate's permission.If find, then execution in step 505; Otherwise execution in step 508.
Whether step 505, source device compare the permission of two correspondences identical.In the time of relatively, ignore the additional information of adding for negotiation in the permission.Such as: types of elements or attribute.If two permissions are identical, then execution in step 506; Otherwise execution in step 507, the reason that failure is described are because the permission of accepting and the candidate of preservation permit inequality.
Step 506, source device generate a formal license, and this permission is sent to requesting service.
Step 507, source device send to requesting service and consult failed message, and show the reason of failure in message.
Whether step 508, source device rejudge accepts this candidate's permission.In order to prevent unnecessary negotiation, candidate's permission here is defaulted as the type of " unofficially can not revise ".If source device is accepted this permission, then execution in step 506; Otherwise execution in step 507, the reason that failure is described are because source terminal is not accepted the result that consults.
Whether step 509, source device judges accept this candidate's permission.If accept, then execution in step 506; Otherwise execution in step 510.
Step 510, source device judge that by the types of elements in candidate's permission can this candidate's permission be modified.If candidate's permission class offset is " unofficially can revise ", then execution in step 511; If candidate's permission class offset is " unofficially can not revise ", then execution in step 507, and the reason that failure is described is because source terminal is not accepted this candidate's permission.
Step 511, source device generate candidate's licence list according to negotiation information and consulting tactical in candidate's permission.Wherein comprise one or more candidate's permissions.
Step 512, source device send to requesting service with candidate's licence list.
Consult shown in Figure 6, in the permission protocol process, the request side apparatus main processing procedure as follows:
Consult shown in Figure 7ly, the requesting terminal side is as follows to the main processing procedure of formal license:
A negotiate response information from source device is received in step 700, requesting terminal, and this information comprises a formal license, and promptly type is " formally " or the not permission of containing type element.
Whether candidate's permission that step 702, requesting service are relatively preserved is identical with formal license.In the time of relatively, equipment is ignored the additional information of adding for negotiation in the permission, such as: types of elements or attribute.If two permissions are identical, then execution in step 703; Otherwise execution in step 704.
Understand and realize the present invention for the ease of persons skilled in the art, an instantiation as shown in Figure 8, its handling process is as follows:
Step 800, device A send the information that asks for permission to source device.
Step 801, source device send candidate's licence list to device A, and wherein this tabulation comprises one or more candidate's permissions.
Step 802, device A are accepted candidate's permission in the candidate list, and source device is issued in this permission.
Step 803, source device are provided formal license, and device A is installed this permission, can consume corresponding content with this permission subsequently.
Step 804, device A have been preserved candidate's licence list that source device is provided, and to the address of server registers oneself, the server record device A is an available agent equipment.Server among this embodiment is born by source device.
Step 805, equipment B send the request broker list of device addresses to server (source device).
Step 806, server send to equipment B with the tabulation of agent equipment address.
Step 807, equipment B according to response the fastest policy selection device A be the agent equipment of oneself, and ask for permission to this equipment transmission.If source device is to respond the fastest equipment among this embodiment, then equipment B can directly be held consultation with source device.
Step 808, device A send to equipment B to candidate's licence list of preserving.
Any one candidate permission during step 809, equipment B are not accepted to tabulate, and revised the content of candidate's permission according to consulting tactical and license type, candidate's licence list of generation is sent to device A.The candidate's licence list that generates comprises one or more candidate's permissions.
Step 810, device A have been accepted new candidate's permission, and this permission is sent to source device.
Step 811, source device are accepted this permission, and provide formal license to equipment B, and equipment B is installed this permission, can consume corresponding content with this permission subsequently.
Equipment B and source device also can become proxy terminal to server registers after finishing permission protocol in the foregoing.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (16)
1. a method that realizes permission protocol between equipment is characterized in that, comprises the following steps:
The requesting service that need secure permission obtains to preserve negotiation information after the formal license from the source device that is used to provide permission, and is registered as the agent equipment of permission protocol;
Follow-up requesting service selects an agent equipment to carry out permission protocol from registered agent equipment, and negotiation result is notified described source device after consulting successfully;
Described source device is permitted to described follow-up requesting service granting according to described negotiation result.
2. the method for claim 1, it is characterized in that, the requesting service that obtains formal license with the separate service equipment of described source device on be registered as agent equipment, follow-up requesting service selects agent equipment to carry out permission protocol from this service equipment; Perhaps
The requesting service that obtains formal license is registered as agent equipment on described source device, follow-up requesting service selects agent equipment to carry out permission protocol from this source device.
3. method as claimed in claim 2 is characterized in that, comprises described source device in the registered agent equipment.
4. method as claimed in claim 2 is characterized in that, follow-up requesting service is selected an agent equipment according to the selection strategy of this locality from registered agent equipment.
5. the method for claim 1 is characterized in that, further with candidate's notification of permit source device of consulting, source device determines that this candidate's permission meets the requirements the back to follow-up requesting service granting formal license after consulting successfully.
6. method as claimed in claim 5 is characterized in that, described candidate's permission is provided by follow-up requesting service, and proxied device is accepted in negotiations process; Perhaps
Described candidate's permission is provided by agent equipment, and is accepted by follow-up requesting service in negotiations process.
7. method as claimed in claim 5 is characterized in that, after follow-up requesting service receives formal license, determines further whether it is consistent with candidate's permission of accepting, if this permission then is installed, otherwise abandons this formal license.
8. method as claimed in claim 7 is characterized in that, after follow-up requesting service abandons described formal license, further to new permission of source device request.
9. method as claimed in claim 5 is characterized in that, source device determines that described candidate permits when undesirable, further sends candidate's permission that this source device provides to follow-up requesting service, indicates it to consult again; Perhaps
Source device notifies follow-up requesting service to consult failure, finishes this time to consult.
10. the method for claim 1 is characterized in that, consult successfully the back by agent equipment with negotiation result notification source equipment; Perhaps
By follow-up requesting service with negotiation result notification source equipment.
11. method as claimed in claim 10 is characterized in that, source device is permitted to follow-up requesting service granting by described agent equipment; Perhaps, source device is directly to follow-up requesting service granting permission.
12., it is characterized in that as each described method of claim 1 to 11, in permission, carry the type information of permission, equipment determines that according to the type information permission is formal license or is candidate's permission in negotiations process.
13. method as claimed in claim 12 is characterized in that, described the type comprises: formal license, candidate can revise permission, the candidate can not revise permission and the candidate accepts permission.
14. method as claimed in claim 13 is characterized in that, can revise permission for the candidate, carries in right in permission or the constraint element to be used to show this right or to limit the attribute information that whether can change.
15. a license management system is characterized in that, comprising:
Source device is used for carrying out permission protocol with other equipment, and is responsible for providing permission;
Service equipment, the device registration that is used for obtaining formal license is to act on behalf of the agent equipment that source device carries out permission protocol;
Agent equipment is used to replace described source device to finish permission protocol, and this agent equipment obtains formal license from described source device;
Requesting service be used for selecting agent equipment to carry out permission protocol from described service equipment, and the back secures permission from described source device consulting successfully.
16. license management system as claimed in claim 15 is characterized in that, the separate setting of described source device and service equipment; Perhaps, described source device and service equipment are set to one.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100839587A CN101090389B (en) | 2006-06-16 | 2006-06-16 | Method and system for implementing permission protocol between equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006100839587A CN101090389B (en) | 2006-06-16 | 2006-06-16 | Method and system for implementing permission protocol between equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101090389A CN101090389A (en) | 2007-12-19 |
| CN101090389B true CN101090389B (en) | 2011-10-05 |
Family
ID=38943556
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006100839587A Active CN101090389B (en) | 2006-06-16 | 2006-06-16 | Method and system for implementing permission protocol between equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101090389B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8763086B2 (en) * | 2008-08-29 | 2014-06-24 | Telefonaktiebolaget L M Ericsson (Publ) | Service sharing among IMS users |
| CN105893792B (en) * | 2016-03-28 | 2019-04-19 | 湖北三新文化传媒有限公司 | Digital copyright management method, device and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1457860A1 (en) * | 2003-02-11 | 2004-09-15 | Microsoft Corporation | Publishing digital content within a defined universe such as an organization in accordance with a digital rights management (DRM) system |
| WO2005050509A1 (en) * | 2003-11-21 | 2005-06-02 | Matsushita Electric Industrial Co., Ltd. | License acquiring system, server apparatus and terminal apparatus |
| CN1700768A (en) * | 2004-05-20 | 2005-11-23 | 英特尔公司 | Method, apparatus and system for remote real-time access of multimedia content |
| CN1756344A (en) * | 2001-04-19 | 2006-04-05 | 松下电器产业株式会社 | License management system, license management device, relay device and terminal device |
-
2006
- 2006-06-16 CN CN2006100839587A patent/CN101090389B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1756344A (en) * | 2001-04-19 | 2006-04-05 | 松下电器产业株式会社 | License management system, license management device, relay device and terminal device |
| EP1457860A1 (en) * | 2003-02-11 | 2004-09-15 | Microsoft Corporation | Publishing digital content within a defined universe such as an organization in accordance with a digital rights management (DRM) system |
| WO2005050509A1 (en) * | 2003-11-21 | 2005-06-02 | Matsushita Electric Industrial Co., Ltd. | License acquiring system, server apparatus and terminal apparatus |
| CN1700768A (en) * | 2004-05-20 | 2005-11-23 | 英特尔公司 | Method, apparatus and system for remote real-time access of multimedia content |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101090389A (en) | 2007-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Graham et al. | Web services base notification 1.3 | |
| EP3467692B1 (en) | Message permission management method and device, and storage medium | |
| RU2295157C2 (en) | Method for joint usage of privilege objects between users | |
| US8561172B2 (en) | System and method for virtual information cards | |
| US8527582B2 (en) | Systems and methods for requesting and delivering network content | |
| US20110119361A1 (en) | System and method for managing redacted electronic documents using callback triggers | |
| EP1983683B1 (en) | A method and system for managing XML document | |
| CN103620602A (en) | Persistent key access to a resource in a collection | |
| US9615116B2 (en) | System, method and apparatus for securely distributing content | |
| JP6819748B2 (en) | Information processing equipment, information processing systems and programs | |
| JP2009163525A (en) | Method for transmitting e-mail | |
| US8793773B2 (en) | System and method for providing reputation reciprocity with anonymous identities | |
| CN105308614A (en) | Policy enforcement delays | |
| CN113271289A (en) | Method, system and computer storage medium for resource authorization and access | |
| CN102572804A (en) | Data calling method and device | |
| JP2009099131A (en) | Access authorization system, access control server, and business process execution system | |
| JP2018156410A (en) | Information processing apparatus and program | |
| CN101090389B (en) | Method and system for implementing permission protocol between equipment | |
| CN102647429A (en) | Application communication access control method, application process manager and online application platform | |
| JP2018157383A (en) | Management device and document management system | |
| JP6708239B2 (en) | Document management system | |
| US9071569B1 (en) | System, method, and computer program for content metadata and authorization exchange between content providers and service providers | |
| CN111737725B (en) | User marking method, device, server and storage medium | |
| CN111740940B (en) | information processing system | |
| JP6777213B2 (en) | Information processing equipment and programs |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |