CN101741620B - Ontology rule description-based service quality grade verifying method - Google Patents
Ontology rule description-based service quality grade verifying method Download PDFInfo
- Publication number
- CN101741620B CN101741620B CN2009102633972A CN200910263397A CN101741620B CN 101741620 B CN101741620 B CN 101741620B CN 2009102633972 A CN2009102633972 A CN 2009102633972A CN 200910263397 A CN200910263397 A CN 200910263397A CN 101741620 B CN101741620 B CN 101741620B
- Authority
- CN
- China
- Prior art keywords
- role
- service
- variable
- certain
- entity
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses an ontology rule description-based service quality grade verifying method. The method comprises the following steps: modeling an entity, a role and a rule through an OWL and an SWRL; finding the relation among the entity, the role and the rule; enabling the SWRL to satisfy an authority form of role distribution in trust management through a certain syntax rule; defining different authorities in various participants according to the functions thereof; managing the resource mastered by the participants through the authorities; finding a trust chain by an ontology inference engine; and verifying whether a relation exits between a target service and a certain quality grade so as to realize the process of verifying the quality grade. By adopting the OWL language based on an ontology, various objects and relations thereof can be described conveniently and flexibly; and by combining the semantic web rule language (SWRL) with an inference engine (JESS) and establishing a rule and performing logical inference, implicit semantic association among the ontology can be found effectively.
Description
Technical field
The present invention relates to the service quality grade verifying method of software resource under a kind of Internet running environment, specifically is a kind of service quality grade verifying method based on ontology rule description.
Background technology
Open Internet running environment has expedited the emergence of the development of one type of new software model such as picture open source alliance, network configuration software.They are based on the software resource that is distributed in each node of network through working in coordination with the demand that the user constantly changes accomplished each other.The continuous evolution of the dynamic combined of software resource and system has proposed challenge to the reliability guarantee of these type of open software systems.Improve the reliability of whole open software systems, will guarantee that at first employed assembly of system and service are highly reliable, service is chosen in the process and service quality rating to be carried out certain requirement and restriction can be guaranteed the quality of serving to a certain extent.
The service that is present on the Internet is open; For various types of services; The certain quality standard is all arranged; Various service quality certification authority can carry out quality evaluation and authentication to the service that some service providers provide according to quality standard, signs and issues these services of certain authorisation verification and satisfies the certain quality grade.The user can verify in certification authority that whether certain service satisfies certain class requirement, chooses user satisfaction and the system reliability in the process thereby improve service when using service.
Service quality rating checking major side overweights selects rational credible verification method; Traditional trust management system has partly solved the open safety problem of being brought of running environment; Through explicit portrayal and processing to trusting relationship between the security domain; The open authorization message of being brought of response environment lacks problem preferably, but because traditional trust management system under the Internet open environment, is difficult to the participation entity of description and portrayal complicacy; Also dumb when statement is authorized simultaneously, also be difficult to reach the knowledge sharing under the open environment.And OWL and SWRL just can describe various entities, role and mandate in the service quality rating proof procedure, and the present invention proposes with regard to being based on this.
Summary of the invention
But technical problem to be solved by this invention provided telecommunications services in open, dynamic, the various environment of a kind of suitable solution choose in the verification method of service quality rating.
Service quality grade verifying method based on ontology rule description of the present invention may further comprise the steps:
1) at first, finds out the participation entity in the service quality proof procedure, participate in entity and comprise: the SSMO of quality standard management organization, the SMO of Service Management mechanism, service distribution side SP and service Service;
2) with based on the participation entity in role's the trust management contextual definition step 1);
3) based on step 2) in the participation entity and the role of definition, provide the syntax rule of SWRL, the mandate that draws role assignments through this syntax rule;
4) participate in the SSMO of quality standard management organization, the SMO of Service Management mechanism in the entity and serve publisher SP and realize management, license to those services of satisfying quality standard through these and issue grading certificate standard, credit rating according to the mandate of step 3);
5) based on step 1)-4) in entity, role and the mandate of definition carry out reasoning checking, in reasoning process, each mandate will judge all whether the role assignments in this mandate is legal, should carry out SupportProof;
6) authorization rule is put into the ontology inference machine and is produced implicit knowledge after, judge the checking request then, if true, i.e. certain service reaches certain substandard credit rating requirement, otherwise this service does not reach the credit rating requirement.
Above-mentioned steps 1) the participation entity in the quality verification process comprises:
Quality standard management organization (SSMO): mainly contain two kinds of functions
A) authorize certain Service Management mechanism (SMO) power of attorney that certain class standard uses, promptly certain SMO can specify certain standard role to certain concrete grade, and just SMO can further authorize the grade of service role of certain standard;
B) different Service Management mechanisms is divided into different groups, carries out similar to different groups again
A) delegable in only is not to certain concrete SMO, but certain SMO group;
C) SSMO for example: iso standard tissue, ansi standard tissue etc.;
Service Management mechanism (SMO): major function has
A) authorize the credit rating that certain service has certain class standard;
B) give service packet, and authorize the credit rating that certain group service has certain class standard;
C) authorize certain service distribution side (SP) and have the credit rating role who defines among the SMO, this role is and 1) in certain substandard credit rating role associate through authorization;
D) authorizing certain service distribution can be to distribute the credit rating role's who defines among this SMO right;
E) SMO for example: CQC China quality authentication mechanism, JC etc.;
Service distribution side (SP)
Role of certain concrete service is promptly given in the service of oneself issuing when a) stating certain service to this service;
B) state that certain service has the credit rating role who defines among certain SMO;
C) SP for example: IBM, Apple, HP, Oracle, Alibaba etc.; Service (Service)
A) Service is that the main body of being verified in the process is chosen in service, mainly is whether certain service of checking has certain substandard credit rating;
B) Service for example: Short Message Service SMSService, mail service EmailService, weather forecast service WeatherService, ticket-booking service BookTicketService etc.;
Above-mentioned steps 2) role who respectively participates in defining in the entity NameSpace has:
The role who defines among the SSMO has:
A) certain substandard credit rating StandardRank is such as ISO.RankA, ISO.RankB, ISO.RankC are arranged
B) SMO group role SMOGroup, the introducing of SMO group can be convenient to SSMO management SMO and SMO is gathered mandate, such as EuropeGroup, AisanGroup, AmericanGroup etc. are arranged;
The role who defines among the SMO has:
A) the grade role SMORank among this SMO; For the ease of SMO the credit rating StandardRank that defines among the SSMO is managed and further mandate; In SMO, introduced SMORank; Set up the mapping relations between SMORank and the StandardRank through issue mandate in SMO, SMORank has: CQC.ISO.RanA, CQC.ISO.RankB, JC.ANSI.RankC;
B) SP group role SPGroup; Also be SP to be managed and make things convenient for for the ease of SMO SP set is authorized, such as having: service provider's set, the WSSPGroup that service provider's set, the B2BSPGroup that ITSPGroup representes to be engaged in the IT industry representes to be engaged in the B2B industry representes to be engaged in service provider's set of Web Service etc.;
The role who defines among the SP has:
A) the role ServiceRole of certain type of service, being used for certain service of authentication to be oneself issue, this role is composed Apple.Service to certain service through form of authorisation;
Above-mentioned steps 3) definition is based on the mandate of SWRL in, and the form that limits the SWRL ontology rule through syntax rule is represented various forms of mandates.The syntax rule grammar G of authorizing=<v
N, V
T, P, delegation>, V wherein
NBe non-terminal set, V
TBe the alphabet that finishing sign is formed, P is the rewriting rule set of finite non-NULL, the distinguished symbol of delegation for authorizing.V
N={ delegation, antecedent, consequent; ObjectPropertyName, variable, EC; RC, OP}, wherein delegation representes to authorize; Corresponding among the SWRL is swrl:Imp, and antecedent is the former piece of rule, and consequent is the consequent of rule; Variable is Entity among the OWL, Role and subclass thereof or the corresponding Instance Name of swrl:Variable class, and objectPropertyName is the Instance Name of the owl:ObjectProperty of Entity and Role and its context dependent couplet.P is following in the rewriting rule set:
(1)delegation：＝antecedent→consequent
(2)antecedent：＝Entity(variable)EC*|Entity(?variable)EC*∧
hasRole(?variable，variable)
(3) consequent：＝(hasRole(variable，variable)|
hasRoleAndAssignment(variable，variable)|hasRole(?variable，
variable)|hasRoleAnd?Assignment(?variable，variable))RC*
(4)EC：＝∧OP(variable，variable)|ε
(5)RC：＝∧OP(variable，variable)|ε
(6)OP：＝objectPropertyName
Above-mentioned steps 4) according to grammar G, participate in entity for each in, the mandate that they provide comprises:
The SSMO of quality standard management organization
A) give the role of certain concrete certain SMOGroup of SMO of Service Management mechanism, such as SMO (JC) → hasRole (JC, ISO.User);
B) give the right of distribution of credit rating role StandardRank under certain group SMOGroup standard, such as SMO (? TP) ∧ hasRole (? TP, ISO.User) → hasRightOfAssignment (? TP, ISO.RankA);
C) give the right of distribution of credit rating role StandardRank under certain SMO standard, such as SMO (TP) → hasRightOfAssignment (TP, ISO.RankA);
The SMO of Service Management mechanism
A) give the right of distribution that certain serves provider SP SMORank, such as ServiceProvider (Apple) → hasRightOfAssignment (Appie, JC.RankA);
B) give set of service and have StandardRank role with certain SMORank, such as: Service (? S) ∧ hasRole (? S, JC.RankA) → hasRole (? S, ISO.RankA);
Service provider SP
A) give certain ServiceRole role of service that certain oneself is issued, such as: Service (SMSService6) → hasRole (SMSService6, Apple.Service);
B) give set of service and have certain SMORank role with certain ServiceRole, such as: Service (? S) ∧ hasRole (? S, Apple.Service) → hasRole (? S, JC.RankA);
Above-mentioned steps 5) with the entity that defines in the preceding several steps, role and mandate, realizes the trust chain discovery in the ontology inference machine.But in trust management system based on the role; Because the role has various participants in its namespace, to define separately; Other participants will use the role who does not belong among this namespace, its corresponding delegable arranged, i.e. similar ServiceProvider (Apple) → hasRightOfAssignment (Apple in the step 4; JC.RankA) mandate of this form, promptly Apple has the right of giving other entities the JC.Rank role authorization.So, will judge all whether the role who distributes has power of attorney, and we are called this proof the Support Proof of mandate for all mandates that we use.
Support Proof detailed process: suppose that certain is authorized is D; The publisher of this mandate is Issuer (D); The role who authorizes among the D is headRole (D); Participant's entity under this role is belongToEntity (headRole (D)), and these are realized as basic operator, mainly are to obtain through the SWRL rule of resolving in the OWL file.An if Issuer (D)!=belongToEntity (headRole (D)) so just carries out Support Proof, proves that promptly hasRightOfAssignment (Issuer (D), headRole (D)) is true.
Above-mentioned steps 6) in to employed mandate or be publisher oneself definition; Carried out Support Proof, can directly put into the ontology inference machine to these mandates so and carry out reasoning, carried out trust chain and find; Thereby obtain after the implicit knowledge in order to judge whether certain service service has the credit rating role role of certain standard; Send request to inference machine, such as: Entity (? S) ∧ Role (ISO.RankA) → hasRole (? S, ISO.RankA); Obtain having the set of service S of ISO.RankA; If service is in S set, then service has role ISO.RankA, and promptly service's satisfies the RankA class requirement under the iso standard.
After above-mentioned steps finishes, can accomplish the checking that service quality rating is required, this chooses in service and is playing the part of important role in the process, is the checking user for the rigid demand of service.
Beneficial effect of the present invention:
Various participation entities in the guidance system developer Analysis Service quality verification process of the present invention comprise standard management tissue, Service Management tissue, serve provider, service etc.By trust management thought based on the role; And entity, role and mandate in the trust management are described with OWL and SWRL; Descriptive power and the flexibility of service, mandate have not only been increased; Also be convenient to knowledge sharing between the different participants, more can realize the discovery and the derivation of trust chain by the ontology inference machine.
The present invention adopts the owl language based on body can make things convenient for, describe flexibly various objects and relation thereof; Service relates to the various relations between multiple different entity, entity attribute and the entity in choosing, and Owl can showing needed descriptor semantization.And owl has realized the standardization on certain level; This just means that computer is when understanding the various representations of knowledge; Need not have knowledge and the interior knowledge description method of specific area in the specific area; Owl can be distributed to the structure and the description of body simultaneously, and this just in time meets the characteristics of no control centre under the open environment.SWRL passes through to increase rule description on the OWL basis, in the existing syntax and semantics of back compatible OWL, strengthens the knowledge representation ability greatly.In the ontology inference process, semantic net rule language SWRL and inference engine JESS are combined, through setting up rule and carrying out reasoning from logic, can effectively find semantic association implicit between the body.
Thereby the present invention is directed to some insincere person and forge the situation that some special rights is obtained in mandate, in the trust chain discovery procedure, do not belong to the situation of authorizing the publisher, provided Support Proof method to role in authorizing.Through a cover service quality verification method of the present invention, can guarantee serviced component that user under the open environment or system the use credible and user satisfaction of height of trying one's best, and then promote the whole system reliability to greatest extent.
Description of drawings
Fig. 1: the OWL class graph of a relation of entity, role, mandate among the OCTM;
Fig. 2: trust management plateform system structure chart;
Fig. 3: the entity in the calendar management system, role, mandate graph of a relation;
Fig. 4: concrete authorization rule.
Embodiment
Below in conjunction with specific embodiment the present invention is further described.
1, the definition of concrete entity, role, mandate among the present invention
Fig. 1 has provided entity, role, the definition of mandate and the relation between them basic among the OCTM.Wherein the concrete implication of each element is following:
(1) entity is represented with the Entity class, and the role representes with the Role class, authorizes and representes with the Delegation class
(2) entity entity have the right of certain role role, with hasRole (entity, role) expression
(3) entity entity have the right of distributing certain role role, with hasRightOfAssignment (entity, role) expression
(4) entity entity had both had this role role, had again to distribute this role's right, with hasRoleAndAssignment (entity, role) expression
(5) certain mandate delegation of entity entity issue are with issuerDelegation (entity, delegation) expression
Authorize delegation by certain entity entity issue for (6) one, with issueredBy (delegation, entity) expression
Authorize the instance that comprises a swrl:Imp among the delegation for (7) one, be used for representing authorization rule, with hasRule (delegation, rule) expression
Certain entity entity under (8) role role is with belongTo (role, entity) expression
Authorize entity and the role who comprises among the de for (9) one, with assertedEntity (de, entity) and assertedRole (de role) representes
(10) entity, role and mandate all have corresponding C ontext, with hasContext (delegation, context) expression
According to the notion of entity, role and mandate in above definition and the trust management model, can draw the characteristics 1 that ObjectProperty wherein has: (1) issueredBy is Functional Property; (2) hasDelegation is InverseFunctional Property; (3) issueredBy and hasDelegation Inverse Properties each other; (4) belongTo is Functional Property.
2, the realization of checking inference engine
The checking inference engine receives service quality rating checking request, resolves and authorizes, and conscientious mandate is collected, and judges to authorize and whether carries out Support Proof and carry out Support Proof, carry out ontology inference, judges whether request sets up.Fig. 2 has provided the system framework figure of checking inference engine, mainly comprises following components: TrustManagement Engine (TME), Delegation Collector (DC), Delegation Parser andManager (DPM) and Trust and Context Reasoner (TCR).
(1) trust management engine (TME) unique parts that to be the trust management platform link to each other with management platform on other nodes with upper layer application; It receives the Query request of user or the transmission of other nodes; Organize other modules in the calling platform according to request type; Bearing results at last returns to requestor .TME and mainly receives following two kinds of Query request: queryRoleTrue (Entity entity, Role role), judges whether entity entity has role role; Be that (whether entity is true role) to hasRole.QueryAssignmentTrue (Entityentity, Role role), judge entity entity whether persona have the right of delegable, promptly (whether entity is true role) to hasRightOfAssignment.
(2) authorize gatherer (DC) DC according to parameter entity and role, collect in the trust network and produce relevant mandate and the knowledge of trusting relationship with role with entity.Collect in the process of authorizing at DC,, judge whether the entity under the role is identical in authorizing the publisher and authorizing consequent, if different, explains that then this mandate is a delegable, prove and authorize the publisher that this mandate is had power of attorney for all mandates.
(3) authorize resolver (DPM) mainly to be used for resolving mandate and associated description information thereof in the local knowledge base; Basic operator: headRole (Delegation de) below having realized; BodyRole (Delegation de), roles (Delegation de), belongToEntity (Role role); Issuer (Delegation de), bodyDirectEntity (Delegation de) etc.TME and DC can obtain the authorization message in the local knowledge base through calling DPM, and the user can manage local knowledge base through Prot é g é instrument.
(4) trusting relationship and ontology inference machine (TCR) TCR collect the mandate that obtains and relevant ontology describing information and common knowledge (comprising public OWL class, axiom and identically true formula etc.) with DC and put into inference machine; Produce tacit knowledge; Again the user is asked to import inference machine, but whether the request of last judges is satisfied or is exported the result to the user.
3, concrete application scenarios
In a concrete service quality rating checking scene, we have the ISO of standard management mechanism at hypothesis, the credit rating standard role of pair short message service are arranged: ISO.SMS.RankA, ISO.SMS.RankB, ISO.SMS.RankC under the iso standard; The JC of Service Management mechanism is arranged, the grade role to the service of sending short messages of definition is arranged: JC.SMS.RankA, JC.SMS.RankB, JC.SMS.RankC among the JC; Serve provider Apple, Apple to the service definition of its issue role Apple.SMS.Service, and Apple has issued the concrete breath service of a sending short messages SMSService6.The mandate that different participants go up issue is as follows:
(1) include among the namespace of service distribution side Apple:
A) Entity: define the subclass Service of Entity, create the instance of a Service then
SMSService6；
B) Role: create an Apple.SMS.Service role instance;
c)?Delegation：
i. Service(SMSService6) ?→ hasRole(SMSService6，
Apple.SMS.Service)
ii.Service(?s)∧hasRole(?s，Apple.SMS.Service)→hasRole(?s，
JC.SMS.RankA)
(2) include among the namespace of Service Management structure JC:
A) Entity: the subclass ServiceProvider of definition Entity, and create a ServiceProvider
Instance Apple;
B) Role: create JC.SMS.RankA, JC.SMS.RankB, JC.SMS.RankC role in fact
Example;
c)?Delegation：
i.?Service(?s)∧hasRole(?s，JC.SMS.RankA)→hasRole(?s，
ISO.SMS.RankA)
ii. ServiceProvider(Apple)→hasRightOfAssignment(Apple，
JC.SMS.RankA)
(3) include among the namespace of the ISO of standard management mechanism:
A) Entity: define the subclass SMO of Entity, and create the instance JC of a SMO;
B) Role: create ISO.SMS.RankA, ISO.SMS.RankB, ISO.SMS.RankC,
ISO.User role;
c)?Delegation：
i. SMO(JC)→hasRole(JC，ISO.User)
ii.SMO(?TP)∧hasRole(?TP，ISO.User)→hasRightOfAssignment(?TP，
ISO.SMS.RankA)
Above-mentioned knowledge and mandate have all been comprised in the Authorized Library of each participation entity; When service is chosen when the user wants to judge whether the SMSService6 of Apple issue satisfies the RankA credit rating of iso standard, just to the checking inference engine send ask Service (? S) ∧ Role (ISO.SMS.RankA) → hasRole (? S, ISO.SMS.RankA); Obtain having ISO.SMS.RankA role's set of service S; Judge that then SMSService6 whether in S set, if exist, representes that then SMSService6 satisfies the RankA requirement of iso standard; If do not exist, then do not satisfy.
Introduction according to the front; We know that the checking inference engine will be before carrying out ontology inference for the role who authorizes in some its publisher of mandate and this mandate not simultaneously; Carry out Support Proof, give the set that has Apple.SMS.Service role such as second mandate among the namespace of service distribution side Apple with the JC.SMS.RankA role assignments, but JC.SMS.RankA defines in the namespace of Service Management structure JC; So will in JC, judge hasRightOfAssignment (Apple; Whether JC.SMS.RankA) set up, ServiceProvider (Apple) → hasRightOfAssignment is just arranged in JC, and (Apple JC.SMS.RankA) authorizes; Thereby Support Proof has been carried out in second mandate among the Apple, is operable.Also to carry out Support Proof for second mandate among the JC equally, because ISO.SMS.RankA defines in the namespace of ISO.
Claims (5)
1. service quality grade verifying method based on ontology rule description is characterized in that may further comprise the steps:
1) at first, finds out the participation entity in the service quality proof procedure, participate in entity and comprise: the SSMO of quality standard management organization, the SMO of Service Management mechanism, service distribution side SP and service Service;
2) with based on the participation entity in role's the trust management contextual definition step 1);
3) based on step 2) in the participation entity and the role of definition, provide the syntax rule of SWRL, the mandate that draws role assignments through this syntax rule;
4) participate in the SSMO of quality standard management organization, the SMO of Service Management mechanism in the entity and serve publisher SP and realize management, license to those services of satisfying quality standard through these and issue grading certificate standard, credit rating according to the mandate of step 3);
5) based on step 1)-4) in entity, role and the mandate of definition carry out reasoning checking, in reasoning process, each mandate will judge all whether the role assignments in this mandate is legal, promptly will carry out Support Proof;
6) authorization rule is put into the ontology inference machine and is produced implicit knowledge after, judge the checking request then, if true, i.e. certain service reaches certain substandard credit rating requirement, otherwise this service does not reach the credit rating requirement.
2. in the service quality grade verifying method based on ontology rule description according to claim 1, it is characterized in that step 2) in role definition comprise:
The role who defines in the quality standard management organization has:
A) certain substandard credit rating StandardRank;
B) the group role of Service Management mechanism SMOGroup;
The role of Service Management mechanism definition has:
A) the grade role SMORank in this Service Management mechanism;
B) service distribution side's group role SPGroup;
The role who defines in the service distribution side has:
A) the role ServiceRole of certain type of service.
3. the service quality grade verifying method based on ontology rule description according to claim 1 and 2 is characterized in that the syntax rule of step 3) SWRL is: G=＜V
N, V
T, P, delegation＞, V wherein
NBe non-terminal set, V
TBe the alphabet that finishing sign is formed, P is the rewriting rule set of finite non-NULL, the distinguished symbol of delegation for authorizing; V
N={ delegation, antecedent, consequent; ObjectPropertyName, variable, EC; RC, OP}, wherein delegation representes to authorize; Corresponding among the SWRL is swrl:Imp, and antecedent is the former piece of rule, and consequent is the consequent of rule; Variable is Entity among the OWL, Role and subclass thereof or the corresponding Instance Name of swrl:Variable class, and objectPropertyName is the Instance Name of the owl:ObjectProperty of Entity and Role and its context dependent couplet; P is following in the rewriting rule set:
(1)delegation：＝antecedent→consequent
(2)antecedent：＝Entity(variable)EC
*|Entity(?variable)EC
*∧hasRole(?variable，variable)
(3)consequent：＝(hasRole(variable，variable)|
hasRoleAndAssignment(variable，variable)|
hasRole(?variable，variable)|hasRoleAnd
Assignment(?variable，variable))RC
*
(4)EC：＝∧OP(variable，variable)|ε
(5)RC：＝∧OP(variable，variable)|ε
(6)OP：＝objectPropertyName。
4. the service quality grade verifying method based on ontology rule description according to claim 2, its
Be characterised in that the mandate that step 4) provides comprises:
The SSMO of quality standard management organization
A) give the role of certain concrete certain SMOGroup of SMO of Service Management mechanism;
B) give the right of distribution that certain organizes credit rating role StandardRank under SMOGroup standard;
C) give the right of distribution of credit rating role StandardRank under certain SMO standard;
The SMO of Service Management mechanism
A) give the right of distribution that certain serves provider SP SMORank;
B) give set of service and have StandardRank role with certain SMORank;
Service provider SP
A) give certain ServiceRole role of service that certain oneself is issued;
B) give set of service and have certain SMORank role with certain Servi ceRote.
5. the service quality grade verifying method based on ontology rule description according to claim 1 and 2; The detailed process that it is characterized in that step 5) Support Proof is: suppose that certain is authorized is D; The publisher of this mandate is Issuer (D); The role who authorizes among the D is headRole (D), and the participant's entity under this role is belongToEntity (headRole (D)); An if Issuer (D)!=belongToEntity (headRole (D)) so just carries out Support Proof, proves that promptly hasRightOfAssignment (Issuer (D), headRole (D)) is true.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102633972A CN101741620B (en) | 2009-12-18 | 2009-12-18 | Ontology rule description-based service quality grade verifying method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009102633972A CN101741620B (en) | 2009-12-18 | 2009-12-18 | Ontology rule description-based service quality grade verifying method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101741620A CN101741620A (en) | 2010-06-16 |
| CN101741620B true CN101741620B (en) | 2012-11-28 |
Family
ID=42464554
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009102633972A Expired - Fee Related CN101741620B (en) | 2009-12-18 | 2009-12-18 | Ontology rule description-based service quality grade verifying method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101741620B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101175064A (en) * | 2006-12-18 | 2008-05-07 | 中兴通讯股份有限公司 | Forwarding periodic line scheduling method based on service quality |
| CN101588595A (en) * | 2009-07-07 | 2009-11-25 | 董志 | Method for dynamically regulating data transfer rate in wireless application service system |
-
2009
- 2009-12-18 CN CN2009102633972A patent/CN101741620B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101175064A (en) * | 2006-12-18 | 2008-05-07 | 中兴通讯股份有限公司 | Forwarding periodic line scheduling method based on service quality |
| CN101588595A (en) * | 2009-07-07 | 2009-11-25 | 董志 | Method for dynamically regulating data transfer rate in wireless application service system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101741620A (en) | 2010-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Servos et al. | Current research and open problems in attribute-based access control | |
| Xu et al. | An efficient privacy‐enhanced attribute‐based access control mechanism | |
| Grandison et al. | A survey of trust in internet applications | |
| Sánchez et al. | Enhancing privacy and dynamic federation in IdM for consumer cloud computing | |
| Cao et al. | A trust model for data sharing in smart cities | |
| Schreck | Security and privacy in user modeling | |
| Liu et al. | Trust‐based secure information sharing between federal government agencies | |
| Squicciarini et al. | Achieving privacy in trust negotiations with an ontology-based approach | |
| CN106170964A (en) | User's virtual identity based on different identity service | |
| Kagal et al. | Developing secure agent systems using delegation based trust management | |
| Ouechtati et al. | Trust-abac towards an access control system for the internet of things | |
| Silva et al. | ACROSS: A generic framework for attribute-based access control with distributed policies for virtual organizations | |
| Ahmed et al. | Security policies in distributed CSCW and workflow systems | |
| Jin et al. | Role-based access management for ad-hoc collaborative sharing | |
| Bekara et al. | Xpacml extensible privacy access control markup langua | |
| Yang et al. | Smart-contract enabled decentralized knowledge fusion for blockchain-based conversation system | |
| Coetzee et al. | Autonomous trust for web services | |
| Speiser et al. | Web technologies and privacy policies for the smart grid | |
| CN101741620B (en) | Ontology rule description-based service quality grade verifying method | |
| Gemmill et al. | Cross‐domain authorization for federated virtual organizations using the myVocs collaboration environment | |
| Perez et al. | Advanced policies for the administrative delegation in federated environments | |
| Nazareth et al. | Using spki/sdsi for distributed maintenance of attribute release policies in shibboleth | |
| Esposito et al. | Interoperable access control by means of a semantic approach | |
| Ardagna et al. | Trust management | |
| Salvador et al. | A semantically distributed approach to map ip traffic measurements to a standardized ontology |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20121128 Termination date: 20211218 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |