EP3367255A1 - Method and device for semantic verification - Google Patents
Method and device for semantic verification Download PDFInfo
- Publication number
- EP3367255A1 EP3367255A1 EP16877713.4A EP16877713A EP3367255A1 EP 3367255 A1 EP3367255 A1 EP 3367255A1 EP 16877713 A EP16877713 A EP 16877713A EP 3367255 A1 EP3367255 A1 EP 3367255A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- semantic
- description resource
- semantic description
- resource
- validation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000012795 verification Methods 0.000 title 1
- 238000010200 validation analysis Methods 0.000 claims abstract description 264
- 230000004044 response Effects 0.000 claims description 40
- 238000004891 communication Methods 0.000 claims description 15
- 230000006870 function Effects 0.000 description 26
- 238000010586 diagram Methods 0.000 description 20
- 101150119033 CSE2 gene Proteins 0.000 description 14
- 101100007792 Escherichia coli (strain K12) casB gene Proteins 0.000 description 14
- 102100029091 Exportin-2 Human genes 0.000 description 14
- 101000770958 Homo sapiens Exportin-2 Proteins 0.000 description 14
- 238000013461 design Methods 0.000 description 10
- 238000005259 measurement Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006399 behavior Effects 0.000 description 2
- 238000009529 body temperature measurement Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004325 capillary sieving electrophoresis Methods 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000003973 irrigation Methods 0.000 description 1
- 230000002262 irrigation Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3015—Name registration, generation or assignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/30—Semantic analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
- G06F16/367—Ontology
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/237—Lexical tools
- G06F40/247—Thesauruses; Synonyms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/30—Types of network names
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
Definitions
- the M2M gateway that stores the semantic description resource may trigger to perform the semantic validation on the semantic description resource by using the ontology referenced by the semantic description resource stored on an M2M platform. Therefore, another application or industry in the M2M system can learn and share a resource described by a semantic description resource on which semantic validation succeeds.
- a network architecture and a service scenario that are described in the embodiments of the present invention are intended to describe the technical solutions in the embodiments of the present invention more clearly, and do not constitute any limitation to the technical solutions provided in the embodiments of the present invention. Persons of ordinary skill in the art may know that with evolution of network architectures and appearance of new service scenarios, the technical solutions provided in the embodiments of the present invention are also applicable to similar technical problems.
- FIG. 1A provides a schematic architectural diagram of an M2M system 200 according to an embodiment of the present invention, for validating semantic description information in the M2M system.
- This embodiment of the present invention is based on an existing M2M architecture, and ontologies of semantic description resources are stored on an M2M platform.
- the ontologies that are referenced by the semantic description resources and that are stored on the M2M platform are used for performing semantic validation on semantic information of the semantic description resources.
- the semantic description resources may be stored on the M2M platform, or may be stored on M2M gateways.
- FIG. 3B is a schematic diagram of a triplet that indicates semantic information and an association relationship and that is included in a description attribute parameter of a semantic description resource associated with another semantic description resource according to an embodiment of the present invention.
- a semantic description resource SemanticDescriptorX created for a resource sensor12 includes the triplet information indicating the semantic information in FIG.
- HumitureSensor hasFunctionality mini measuringFunctionality, indicating that HumitureSensor (humiture sensor) has at least one measuringFunctionality (measurement function);
- Step 703 The gateway sends a semantic validation request message to a platform, where the semantic validation request message carries a name of the to-be-created semantic description resource, semantic information of the semantic description resource, a URI of an ontology referenced by the semantic description resource, and a URI of the associated semantic description resource.
- Step 704' The platform obtains an associated semantic description resource from a gateway 1.
- the parameter indicating that the semantic validation succeeds or the parameter indicating that no semantic validation is performed is added to the semantic description resource, so that an application server or another apparatus that subsequently obtains or accesses the semantic description resource can clearly determine whether the semantic validation has been performed, and whether a resource described by the semantic description resource can be learned and referenced.
- an embodiment of the present invention further provides a schematic structural diagram of an apparatus that stores a semantic description resource.
- the apparatus 800 includes: a receiving unit 801, a determining unit 802, a sending unit 803, an execution unit 804, an obtaining unit 805, and a validation unit 806.
- the receiving unit 801 is further configured to perform a step such as step 301, 304, 701, 704, 704', or 706 performed by the gateway in FIG. 6 and FIG. 7 .
- the determining unit 802 may further perform steps 302 and 702 performed by the gateway in FIG. 6 and FIG. 7
- the execution unit is configured to perform steps 707 and 305 in FIG. 6 and FIG. 7
- the obtaining unit may be further configured to perform steps 303 and 304 in FIG. 6 . Details are not described again in this embodiment of the present invention.
- the apparatus in FIG. 8 may be configured to: perform any procedure performed by the gateway in the foregoing method procedures, and store the semantic description resource in FIG. 2 to FIG. 3D .
Abstract
Description
- This application claims priority to Chinese Patent Application No.
201510998415.7 - The present invention relates to the field of Machine-to-Machine Communications (Machine-to-Machine Communications, M2M) technologies, and in particular, to a semantic validation method and apparatus.
- Machine-to-Machine Communications (Machine-to-Machine Communications, M2M) is a network-based application and service that use intelligent interaction between machines as a core. Based on the M2M technology, a wireless or wired communications module and application processing logic are embedded into a machine, to implement data communication without human intervention, to satisfy informatization requirements of users on aspects such as monitoring, commanding and dispatching, data collection, and measurement. Currently, the M2M technology has been applied to an increasing quantity of industries and fields, for example, industries such as intelligent transportation, agricultural irrigation, smart household, power grid, and meter reading. To satisfy requirements of application services in different industries, an M2M system operator develops a unified M2M platform to implement some public capabilities, for example, data access and storage, data sharing and transmission, group communication, data subscription notification, security, charging, and resource discovery. The M2M platform may access different types of devices and sensors, and may provide an application access interface, to allow applications in different industries to invoke, by using the access interface, the public capabilities provided by the M2M platform.
- Currently, the M2M system provides a public capability component (such as a CSE, common service entity), and provides a unified interface to perform data transmission to shield a difference between device communication manners, so that industries and applications that access the M2M system share a data transmission capability. However, for data use, the industries and applications are still closed to each other. For example, for a device belonging to different applications, in a case of no priori knowledge, another application cannot know a function of the device and an operation that can be performed by the device, and even if another application can obtain data, the another application cannot understand a meaning of the data. Consequently, data reuse and sharing between different applications cannot be implemented, hindering formation of an open data market.
- To enable the industries and applications to share a resource and data in the case of no priori knowledge, a semantic description resource is added to the M2M system, so that data and an operation can be described in a machine-understandable manner, to enable another application to determine, by using semantic description information, a function and an executable operation that are provided by a parent resource, and to determine a data meaning, such as a data type or a unit, provided by the parent resource, thereby implementing data sharing between the different applications and helping to form the open data market. In the future, a semantic function such as semantic query or semantic reasoning may be further provided by using semantic description information in the semantic description resource.
- However, based on an existing M2M architecture, validation on the semantic description resource cannot be implemented, and accuracy of semantic description information in the semantic description resource cannot be ensured. For example, consistency between the semantic description information and an ontology indicated by an ontology reference attribute cannot be ensured. Consequently, result accuracy and implementation of the function such as semantic query or semantic reasoning are affected.
- The present invention provides a method and an apparatus for implementing semantic validation, to resolve a problem in the prior art that in an M2M architecture, validation on semantic description information cannot be implemented, and accuracy of semantic description information in a semantic description resource cannot be ensured, affecting result accuracy and a function such as semantic query or semantic reasoning that may be further provided by a public capability of an M2M system.
- During specific implementation, a gateway in the M2M system may serve as an apparatus that stores a semantic description resource, and an M2M platform may serve as an apparatus that stores an ontology referenced by the semantic description resource. Specifically, the M2M gateway receives an operation request that is sent by an application server and that is related to the semantic description resource. Then, the M2M gateway determines an entity for performing semantic validation (such as the M2M gateway or platform) based on content of the operation request, and triggers the entity for performing semantic validation to perform, by using the ontology that is referenced by the semantic description resource and that is stored on the platform, semantic validation on the semantic description resource stored on the gateway. According to the present invention, the semantic validation may be applied to the M2M system, to ensure accuracy of a resource and data that are shared between industries and applications that use the public capability of the M2M system in a case of no priori knowledge.
- According to a first aspect, an embodiment of the present invention provides a semantic validation method, where the method is applied to a Machine-to-Machine Communications M2M system. An apparatus (such as an M2M gateway) that stores a semantic description resource receives an operation request related to a first semantic description resource, where the operation request related to the first semantic description resource includes: semantic information of the first semantic description resource, an association relationship between the first semantic description resource and another semantic description resource, and a URI of an ontology referenced by the first semantic description resource. Then, the apparatus that stores the semantic description resource determines, based on the association relationship between the first semantic description resource and the another semantic description resource, that the first semantic description resource is associated with the semantic description resource, and then sends a semantic validation request message to an apparatus that stores the ontology referenced by the first semantic description resource. The semantic validation request message is used for instructing to use the ontology indicated by the URI of the ontology referenced by the first semantic description resource and an ontology referenced by the associated semantic description resource indicated by the association relationship to perform semantic validation on the semantic information of the first semantic description resource and semantic information of the associated semantic description resource. According to this embodiment of the present invention, the M2M gateway that stores the semantic description resource may trigger to perform the semantic validation on the semantic description resource by using the ontology referenced by the semantic description resource stored on an M2M platform. Therefore, another application or industry in the M2M system can learn and share a resource described by a semantic description resource on which semantic validation succeeds.
- In a possible design, the apparatus that stores the semantic description resource may further receive a semantic validation success response message returned by the apparatus that stores the ontology referenced by the first semantic description resource; and then perform the operation request related to the first semantic description resource, and set, in the first semantic description resource, a parameter indicating that the semantic validation succeeds. Alternatively, the apparatus that stores the semantic description resource may further receive a response message that indicates that no semantic validation is performed and that is returned by the apparatus that stores the ontology referenced by the first semantic description resource; and then perform the operation request related to the first semantic description resource, and set, in the first semantic description resource, a parameter indicating that no semantic validation is performed. The parameter indicating that the semantic validation succeeds or the parameter indicating that no semantic validation is performed is added to the semantic description resource, so that an application server or another apparatus that subsequently obtains or accesses the semantic description resource can clearly determine whether the semantic validation has been performed, and whether a resource described by the semantic description resource can be learned and referenced.
- In a possible design, the apparatus that stores the semantic description resource may determine, by determining that the semantic description resource includes an association attribute indicating an association relationship between the semantic description resource and another semantic description resource or that the description attribute of the semantic description resource includes triplet information indicating an association relationship between the semantic description resource and another semantic description resource, that the semantic description resource is associated with the another semantic description resource. Alternatively, the apparatus that stores the semantic description resource may determine, by determining that the semantic description resource does not include an association attribute indicating an association relationship between the semantic description resource and another semantic description resource and the description attribute of the semantic description resource does not include triplet information indicating an association relationship between the semantic description resource and another semantic description resource, that the semantic description resource is not associated with the another semantic description resource. Therefore, the apparatus that stores the semantic description resource may more accurately and effectively determine whether the description resource is associated with the another semantic description resource, and the apparatus that stores the semantic description resource does not need to analyze the entire semantic description resource.
- In possible design, the apparatus that stores the semantic description resource may further receive an operation request related to a second semantic description resource, where the operation request related to the second semantic description resource includes: semantic information of the second semantic description resource, and a URI of an ontology referenced by the second semantic description resource. Then, the apparatus that stores the semantic description resource determines that the second semantic description resource is not associated with another semantic description resource; obtains, from an apparatus that stores the ontology referenced by the second semantic description resource, the ontology referenced by the second semantic description resource; and finally performs validation on the semantic information of the second semantic description resource by using the ontology referenced by the second semantic description resource. Therefore, according to the apparatus that stores the semantic description resource, the ontology referenced by the semantic description resource not associated with the another semantic description resource may be obtained from the apparatus that stores the ontology, and then the semantic validation may be performed. Therefore, the platform does not need to perform the semantic validation, thereby reducing works of the platform.
- In a possible design, the apparatus that stores the semantic description resource may further receive a semantic description resource obtaining request, and determine that a to-be-obtained semantic description resource includes the parameter indicating that no semantic validation is performed. Then, a semantic validation procedure is triggered, and the semantic description resource is returned after the semantic validation succeeds. Based on the semantic validation on the semantic description resource that includes the parameter indicating that no semantic validation is performed, it is ensured that all semantic description resources sent to another application server are semantic description resources that are successfully validated. Therefore, the another application server can share and learn the semantic description resources.
- In another possible design, the apparatus that stores the semantic description resource may further receive an operation request related to a third semantic description resource, and determine that the third semantic description resource is not associated with another semantic description resource. However, an ontology referenced by the third semantic description resource is not obtained from an apparatus that stores the ontology referenced by the third semantic description resource. The operation request related to the third semantic description resource may be further performed first; and then a parameter indicating that no semantic validation is performed may be set in the third semantic description resource. The parameter indicating that no semantic validation is performed is set, so that an application server or another apparatus that subsequently obtains or accesses the semantic description resource can clearly determine whether the semantic validation has been performed, and whether a resource described by the semantic description resource can be learned and referenced.
- In another possible design, the apparatus that stores the semantic description resource may further receive a semantic description resource obtaining request, where the obtaining request carries a URI of a to-be-obtained semantic description resource and an identifier indicating semantic validation; and then, determine, based on the URI of the to-be-obtained semantic description, that the to-be-obtained semantic description resource includes the parameter indicating that no semantic validation is performed. Then, the apparatus that stores the semantic description resource triggers, based on a determining result, to perform semantic validation on semantic information of the to-be-obtained semantic description resource; and after determining that the validation on the semantic information of the to-be-obtained semantic description resource succeeds, sends the to-be-obtained semantic description resource to an apparatus that sends the obtaining request. In this design, before sending the semantic description resource, the apparatus that stores the semantic description resource triggers to perform semantic validation again on the semantic description resource on which no semantic validation is performed, and sends the semantic description resource to the apparatus that sends the obtaining request after the semantic validation succeeds, to ensure that the semantic validation on the obtained semantic description resource succeeds.
- In another possible design, after determining that the validation on semantic information of the to-be-obtained semantic description resource succeeds, the apparatus that stores the semantic description resource further updates the parameter that indicates that no semantic validation is performed and that is included in the to-be-obtained semantic description resource to a parameter indicating that the semantic validation succeeds. Therefore, when an apparatus needs to obtain a semantic description resource next time, the semantic description resource may be directly sent without triggering semantic validation again.
- According to a second aspect, an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction used by the foregoing apparatus that stores the semantic description resource. The computer storage medium includes a program designed for performing the foregoing aspect.
- According to a third aspect, an embodiment of the present invention provides an apparatus that stores the semantic description resource. The apparatus that stores the semantic description resource has a function of implementing a behavior of the apparatus for storing the semantic description resource in the foregoing method. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the foregoing function.
- According to a fourth aspect, a structure of an apparatus that stores a semantic description resource includes a memory, a transceiver, and a processor. The memory is configured to store computer executable program code, and is coupled to a transceiver. The program code includes an instruction. When the processor executes the instruction, the instruction enables the apparatus to execute information or an instruction provided in the foregoing method.
- According to a fifth aspect, an embodiment of the present invention provides a semantic validation method, where the method is applied to a Machine-to-Machine Communications M2M system. An apparatus (such as an M2M platform) that stores an ontology referenced by a semantic description resource receives a semantic validation request message sent by an apparatus that stores a semantic description resource, where the semantic validation request message includes semantic information of a first semantic description resource, a uniform resource identifier URI of an ontology referenced by the first semantic description resource, and an association relationship between the first semantic description resource and another semantic description resource. The apparatus that stores the ontology referenced by the semantic description resource obtains, based on the association relationship between the first semantic description resource and the another semantic description resource, semantic information of the associated another semantic description resource and a URI of an ontology referenced by the associated semantic description resource. Finally, the apparatus that stores the ontology referenced by the semantic description resource performs semantic validation on the semantic information of the first semantic description resource and the semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and the ontology indicated by the URI of the ontology referenced by the associated semantic description resource. According to this embodiment of the present invention, the apparatus (such as the M2M platform) that stores the ontology referenced by the semantic description resource may perform, by using the stored ontology, the semantic validation on the semantic description resource stored on an M2M gateway. Therefore, another application or industry in the M2M system can learn and share a resource described by a semantic description resource on which semantic validation succeeds.
- In a possible design, after the semantic validation succeeds, the apparatus (such as the M2M platform) that stores the ontology referenced by the semantic description resource returns a semantic validation success response message to the apparatus (such as the M2M gateway) that stores the semantic description resource, where the semantic validation success response message is used for instructing to set, for the first semantic description resource, a parameter indicating that the semantic validation succeeds; or when the semantic information of the associated another semantic description resource and the URI of the ontology referenced by the associated semantic description resource are not obtained, returns a response message indicating that no semantic validation is performed to the apparatus (such as the M2M gateway) that stores the semantic description resource, where the response message indicating that no semantic validation is performed is used for instructing to set, for the first semantic description resource, a parameter indicating that no semantic validation is performed. The parameter indicating that the semantic validation succeeds or the parameter indicating that no semantic validation is performed is added to the response message, so that the M2M gateway confirms a semantic validation result, and an application server or another apparatus that subsequently obtains or accesses the semantic description resource can clearly determine whether the semantic validation has been performed.
- In a possible design, the apparatus (such as the M2M platform) that stores the ontology referenced by the semantic description resource may further receive an ontology obtaining request sent by the apparatus that stores the semantic description resource, where the ontology obtaining request carries a URI of an ontology, where the ontology indicated by the URI of the ontology is used for validating semantic information of the semantic description resource stored in the apparatus that stores the semantic description resource; and then the apparatus (such as the M2M platform) that stores the ontology referenced by the semantic description resource returns the ontology indicated by the URI of the ontology to the apparatus (such as the M2M gateway) that stores the semantic description resource. Therefore, the apparatus that stores the semantic description resource can perform, by using the obtained ontology, the semantic validation on the semantic description resource stored by the apparatus that stores the semantic description resource. Therefore, the semantic validation becomes more flexible.
- According to a sixth aspect, an embodiment of the present invention provides a computer storage medium, configured to store a computer software instruction used by the foregoing apparatus that stores the ontology referenced by the semantic description resource. The computer storage medium includes a program designed for performing the foregoing aspect.
- According to a seventh aspect, an embodiment of the present invention provides an apparatus that stores an ontology referenced by a semantic description resource. The apparatus that stores the ontology referenced by the semantic description resource has a function of implementing a behavior of the apparatus that stores the ontology referenced by the semantic description resource in the foregoing method. The function may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the foregoing function.
- According to an eighth aspect, a structure of an apparatus that stores an ontology referenced by a semantic description resource includes a memory, a transceiver, and a processor. The memory is configured to store computer executable program code, and is coupled to the transceiver. The program code includes an instruction. When the processor executes the instruction, the instruction enables the apparatus to execute information or an instruction provided in the foregoing method.
- It can be learned from the foregoing solutions that, in the embodiments of the present invention, the M2M gateway determines an entity for performing semantic validation (such as the M2M gateway or platform) based on content of the operation request, and triggers the entity for performing semantic validation to perform, by using the ontology that is referenced by the semantic description resource and that is stored on the platform, the semantic validation on the semantic description resource stored on the gateway. According to the present invention, the semantic validation may be applied to the M2M system, to ensure accuracy of a resource and data that are shared between industries and applications that use a public capability of the M2M system in a case of no priori knowledge.
- To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly describes the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description merely show some embodiments of the present invention, and persons of ordinary skill in the art can derive other implementations from these accompanying drawings without creative efforts. All these embodiments or implementations shall fall within the protection scope of the present invention.
-
FIG. 1A is an M2M system-based network architectural diagram according to an embodiment of the present invention; -
FIG. 1B is a schematic structural diagram of an apparatus that stores a semantic description resource or an apparatus that stores an ontology referenced by a semantic description resource according to an embodiment of the present invention; -
FIG. 2 shows a structure of a semantic description resource serving as a child resource of a resource sensor12 described by the semantic description resource according to an embodiment of the present invention; -
FIG. 3A is a schematic diagram of a triplet that indicates semantic information and that is included in a description attribute parameter of a semantic description resource not associated with another semantic description resource according to an embodiment of the present invention; -
FIG. 3B is a schematic diagram of a triplet that indicates semantic information and an association relationship and that is included in a description attribute parameter of a semantic description resource associated with another semantic description resource according to an embodiment of the present invention; -
FIG. 3C is a schematic diagram of a triplet that indicates semantic information and an association relationship and that is included in a description attribute parameter of a semantic description resource SemanticDescriptorY associated with a semantic description resource SemanticDescriptorX according to an embodiment of the present invention; -
FIG. 3D is a schematic diagram of a triplet that indicates semantic information and that is included in a description attribute parameter of a semantic description resource SemanticDescriptorZ associated with a semantic description resource SemanticDescriptorY according to an embodiment of the present invention; -
FIG. 4 is a schematic diagram of a triplet of content of a HumitureSensor class-related ontology part in an ontology baseOntology according to an embodiment of the present invention; -
FIG. 5 is a schematic diagram of a triplet of a Humiture Sensor-related ontology whose depth is 1 according to an embodiment of the present invention; -
FIG. 6 is a method flowchart of a semantic validation method according to an embodiment of the present invention; -
FIG. 7 is a method flowchart of a semantic validation method according to an embodiment of the present invention; -
FIG. 8 is a schematic structural diagram of an apparatus that stores a semantic description resource; and -
FIG. 9 is a schematic structural diagram of an apparatus that stores an ontology referenced by a semantic description resource. - The technical solutions according to embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings. Apparently, the described embodiments are merely some but not all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
- A network architecture and a service scenario that are described in the embodiments of the present invention are intended to describe the technical solutions in the embodiments of the present invention more clearly, and do not constitute any limitation to the technical solutions provided in the embodiments of the present invention. Persons of ordinary skill in the art may know that with evolution of network architectures and appearance of new service scenarios, the technical solutions provided in the embodiments of the present invention are also applicable to similar technical problems.
-
FIG. 1A provides a schematic architectural diagram of anM2M system 200 according to an embodiment of the present invention, for validating semantic description information in the M2M system. This embodiment of the present invention is based on an existing M2M architecture, and ontologies of semantic description resources are stored on an M2M platform. The ontologies that are referenced by the semantic description resources and that are stored on the M2M platform are used for performing semantic validation on semantic information of the semantic description resources. Further, the semantic description resources may be stored on the M2M platform, or may be stored on M2M gateways. Therefore, the semantic validation on the semantic description resource provided in this embodiment of the present invention may be a validation performed on the semantic description resource by the M2M platform based on the ontology that is referenced by the semantic description resource and that is stored on the M2M platform, or may be a validation performed, by the M2M gateway by obtaining, from the M2M platform, the ontology that is referenced by the semantic description resource and that is stored on the M2M platform, on the semantic description resource stored on the M2M gateway. An ontology is a formalized and clear description about a sharing concept model, and the ontology is used for performing semantic validation on semantic information of a semantic description resource. The semantic information is information that describes a resource that is described by the semantic description resource. The semantic information in this embodiment of the present invention may exist in a triplet form, and is used for describing a resource that is described by a semantic description resource (for example, the semantic information may be information that is in triplet information inFIG. 3A to FIG. 3D and whose subject is a resource described by a semantic description resource. In another optional implementation, the semantic information may be triplet information inFIG. 3A to FIG. 3D except information about a triplet including an association relationship (for example, a predicate hasResDescriptorLink). It is commonly understood that, the ontology may provide common understanding about knowledge in a field, determine universally recognized words in the field, and provide clear definitions of these words (terms) and a mutual relationship between the words. In this embodiment of the present invention, the ontology may be obtained by the M2M platform from an existing ontology library and stored on the M2M platform, or may be configured by the M2M platform in advance. - In this embodiment of the present invention, an apparatus that stores a semantic description resource may be each gateway or M2M platform in the M2M system, and an apparatus that stores an ontology referenced by a semantic description resource may be the M2M platform. Correspondingly, this embodiment of the present invention may be applied to another system, provided that in the another system, the apparatus that stores the semantic description resource and the apparatus that stores the ontology referenced by the semantic description resource are not a same apparatus.
- In addition, first, second, and third in the embodiments of the present invention have no technical significance, and are used only for distinguishing between terms.
- Specifically, the M2M system provided in this embodiment of the present invention includes an
M2M platform 102, anM2M gateway 103, anM2M device 104, and anapplication server 101. As shown inFIG. 1A , theM2M platform 101 may be an IN (Infrastructure Node, infrastructure node), theM2M gateway 102 is an MN (Middle Node, middle node), and the M2M device may be an ASN (Application Service Node, application service node) or an AND ((Application Dedicated Node, application dedicated node), not shown in the figure). In addition, a CSE (Common Service Entity, common service entity) serves as a public capability component of the M2M system, and may bear a public capability. The CSE may be included in the M2M platform, the M2M gateway, or the ASN that serves as the M2M device, to implement a corresponding function. The CSE enables, by using an Mca reference point, an AE (Application Entity, application entity) to access an open public capability of the CSE; implements, by using an Mcc reference point, communication between CSEs; and invokes a bottom-layer network capability by using an Mcn reference point. - In the architecture shown in
FIG. 1A , the M2M gateway may store a semantic description resource of each resource, and receive an operation request that is related to the semantic description resource and that is sent by each application server. The operation request related to the semantic description resource may be a request for creating a semantic description resource or a request for updating a semantic description resource. The M2M gateway and the M2M platform may further trigger a semantic validation procedure before performing the operation request related to the semantic description resource. The semantic validation procedure may be: determining an entity for performing semantic validation (such as the M2M gateway that stores the semantic description resource or the M2M platform that stores the ontology referenced by the semantic description resource), and performing semantic validation by the determined entity for performing semantic validation. The M2M platform further stores the ontology referenced by each semantic description resource, and provides the ontology referenced by the semantic description resource to a semantic validation gateway, or directly performs semantic validation on the semantic description resource by using the ontology referenced by the semantic description resource. Specifically, for the semantic validation procedure, refer to the following detailed description in this embodiment of the present invention. - The semantic description resources stored on the M2M gateway and the M2M platform may serve as a form of child resources of existing resources, or may serve as independent resources. A semantic description resource is used for describing semantic information of a related resource. Descriptions of data and an operation of the related resource in a machine-understandable manner enables another application to determine, by using the semantic description resource, a function, an executable operation, and a meaning of data such as a data type or a unit, that are provided by the resource described by the semantic description resource, to implement data sharing between different applications, and help to form an open data market.
-
FIG. 1B is a schematic structural diagram of an apparatus that stores a semantic description resource according to an embodiment of the present invention. The apparatus is configured to receive, an operation request related to a semantic description resource, and trigger a semantic description resource validation procedure in the M2M system shown inFIG. 1A . Theapparatus 200 may include one ormore ports 208 coupled to a transceiver (transceiver) 206. Thetransceiver 206 may be a transmitter, a receiver, or a combination thereof for sending or receiving a data packet to or from another network node by using theport 208. Aprocessor 202 is coupled to thetransceiver 206, and is configured to process the data packet. Theprocessor 202 may include one or more multi-core processors and/or amemory 204. Theprocessor 202 may be a general purpose processor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or a digital signal processor (DSP). - The
memory 204 may be a non-transient storage medium coupled to theprocessor 202, and is configured to store different types of data, such as a semantic description resource, or a resource described by a semantic description resource. Thememory 204 may include a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), or a dynamic storage device of another type that is capable of storing information and an instruction, or may be a magnetic disk storage. Thememory 204 may be configured to store an instruction for implementing a method related to semantic validation. It may be understood that an executable instruction is programmed or loaded to at least one of theprocessor 202 of theapparatus 200, a cache, and a long-term storage. - The
apparatus 200 that stores the semantic description resource may execute one or more instructions according to this embodiment of the present invention, to trigger semantic validation. These instructions may be stored in thememory 204, or may be integrated into a kernel or a plug-in of a kernel of an operating system of the apparatus. - In another embodiment, the
device 200 serves as the apparatus that stores the semantic description resource, and includes thememory 204, theprocessor 202, thetransceiver 206, and one ormore ports 208 coupled to the transceiver. Thememory 204 is configured to store computer executable program code. Theprocessor 202 is coupled to thememory 204 and thetransceiver 206. - The program code includes an instruction. When the processor executes the instruction, the instruction enables the apparatus to perform related steps performed by a gateway in
FIG. 6 andFIG. 7 . - In addition,
FIG. 2 may further be used as a schematic structural diagram of an apparatus that stores an ontology referenced by a semantic description resource according to an embodiment of the present invention. As the apparatus that stores the ontology referenced by the semantic description resource, the device inFIG. 2 includes amemory 204, aprocessor 202, atransceiver 206, and one ormore ports 208 coupled to the transceiver. Thememory 204 is configured to store computer executable program code. Theprocessor 202 is coupled to thememory 204 and thetransceiver 206. - The program code includes an instruction. When the processor executes the instruction, the instruction enables the apparatus to perform related steps performed by a platform in
FIG. 6 andFIG. 7 . - In an example, a structure of a semantic description resource semanticDescriptor stored in the apparatus that stores the semantic description resource in
FIG. 1 to FIG. 8 may be shown inFIG. 2 , and a semantic description resource semanticDescriptorX used as a child resource of a resource sensor sensor12 is used for describing semantic information related to a resource sensor12. The semantic description resource includes a parameter of a description attribute descriptor and a parameter of an ontology (ontologyRef) referenced by the semantic description resource. The parameter of the description attribute (descriptor) includes semantic information of the semantic description resource and an association relationship between the semantic description resource and another semantic description resource. The parameter of the referenced ontology (ontologyRef) includes a uniform resource identifier (Uniform Resource Identifier, URI) of the ontology referenced by the semantic description resource. In an optional implementation, the parameter of the ontology referenced by the semantic description resource may alternatively exist in a form of a dashed line inFIG. 2 , and serve as a parameter of an attribute of the resource (sensor12) described by the semantic description resource instead of serving as an attribute parameter of the semantic description resource. This is not limited in this embodiment of the present invention. In another optional implementation, the parameter of the referenced ontology may alternatively be included in the parameter of the description attribute (descriptor). In addition, the resource sensor12 further includes two child resources: a temperature container tempContainer and a humidity container humidityContainer. A child resource semanticDescriptorY of the resource tempContainer is used for describing semantic information related to the resource tempContainer. Further, a child resource semanticDescriptorZ of a child resource contentInstance1 of the resource tempContainer is used for describing semantic information related to the resource contentInstance1. -
FIG. 3A is a schematic diagram of a triplet that indicates semantic information and that is included in a description attribute parameter of a semantic description resource not associated with another semantic description resource according to an embodiment of the present invention. Specifically, inFIG. 3A , a parameter of a description attribute (descriptor) of a semantic description resource SemanticDescriptorX that serves as a resource sensor12 includes the following information:
< baont:sensor12 > <rdf: type> Humiture Sensor</rdf: type> < baont:hasManufaturer> "wulianchuangan"< /baont:hasManufaturer> < baont:hasSerialNumber> 123456789< /baont:hasSerialNumber> < baont:hasFunctionality> tempContainer< /baont:hasFunctionality> < baont:hasFunctionality> humidityContainer< /baont:hasFunctionality> </ baont:sensor12> </rdf:RDF>
- the triplet information tempContainer hasResDescriptorLink http://www.onem2m.org/CSE1/**/sensor12/tempContainer/semDesciptor indicating the association relationship indicates that tempContainer is associated with a semantic description resource whose URI is http://www.onem2m.org/CSE1/**/sensor12/tempContainer/semDesciptorY, that is, tempContainer is a resource described by the semantic description resource whose URI is http://www.onem2m.org/CSE1/**/sensor12/tempContainer/semDesciptorY; and
- the triplet information humidityContainer hasResDescriptorLink http://www.onem2m.org/CSE2/**/ humidityContainer/semDesciptor1 indicating the association relationship indicates that humidityContainer is associated with a semantic description resource whose URI is http://www.onem2m.org/CSE2/**/ humidityContainer/semDesciptor1, that is, humidityContainer is a resource described by the semantic description resource whose URI is http://www.onem2m.org/CSE2/**/ humidityContainer/semDesciptor1.
- a triplet tempContainer rdf:type measuringTemperature indicating semantic information indicates that tempContainer is a type of measuringTemperature (temperature measurement);
- a triplet tempContainer quantifies contentInstance1 indicating semantic information indicates that tempContainer measures a quantity of contentInstance1; and
- a triplet contentInstance1 hasResDescriptorLink http://www.onem2m.org/CSE1/**/sensor12/tempContainer/contentInstance1/semDescriptorZ indicating an association relationship indicates that contentInstance1 is associated with a semantic description resource whose URI is http://www.onem2m.org/CSE1/**/sensor12/tempContainer/contentInstance1/semDescriptorZ, that is, contentInstance1 is a resource described by the semantic description resource whose URI is http://www.onem2m.org/CSE1/**/sensor12/tempContainer/contentInstance1/semDescriptorZ.
- contentInstance1 rdf:type TemperatureAspect indicates that contentInstance1 is a type of TemperatureAspect (temperature aspect);
- contentInstance1 hasUnit Celsius indicates that a unit of contentInstance1 is Celsius (degree Celsius); and
- contentInstance1 has Value content indicates that a value of contentInstance1 is content (content in content).
- HumitureSensor hasSerialNumuber.. ^^Integer, indicating that a HumitureSensor (humiture sensor) class has a sequence number ^^Integer, where a value of ^^Integer is an integer;
- HumitureSensor hasManufacturer ^^string, indicating that a manufacturer of HumitureSensor (humiture sensor) is ^^ string, where a value of ^^ string is a character string;
- HumitureSensor hasFunctionality mini measuringFunctionality, indicating that Humiture Sensor (humiture sensor) has at least one measuringFunctionality (measurement function);
- HumitureSensor hasMode sleeping, indicating that HumitureSensor (humiture sensor) has a sleeping (sleeping) mode;
- HumitureSensor isSubClassof complicatedSensor, indicating that HumitureSensor (humiture sensor) is a subclass of complicatedSensor (complex sensor);
- measuringFunctionality hasSubclass measuringTemperture, indicating that measuringFunctionality (measurement function) has a subclass of measuringTemperture (temperature measurement);
- measuringFunctionality hasSubclass measuringHumidity, indicating that measuringFunctionality (measurement function) has a subclass of measuringHumidity (humidity measurement);
- measuringTemperture quantifies TemperatureAspect, indicating that measuringTemperture measures a quantity of temperatureAspect (temperature aspect); and
- measuringHumidity quantifies HumidityAspect, indicating that measuringHumidity measures a quantity of HumidityAspect (humidity aspect).
humidityContainer rdf:type controllingFunction, indicating that humidityContainer is of a type of controllingFunction (control function).
controllingFunction isdisjointwith measuringFunctionality, indicating that measuringFunctionality (measurement function) and controllingFunction (control function) do not overlap.
the determining
the sending
the obtaining
the
Claims (24)
- A semantic validation method, wherein the method is applied to a Machine-to-Machine Communications M2M system, and the method comprises:receiving an operation request related to a first semantic description resource, wherein the operation request related to the first semantic description resource comprises: semantic information of the first semantic description resource, an association relationship between the first semantic description resource and another semantic description resource, and a URI of an ontology referenced by the first semantic description resource;determining, based on the association relationship between the first semantic description resource and the another semantic description resource, that the first semantic description resource is associated with the semantic description resource;sending, based on the URI of the ontology referenced by the first semantic description resource, a semantic validation request message to an apparatus that stores the ontology referenced by the first semantic description resource, wherein the semantic validation request message comprises the semantic information of the first semantic description resource, the URI of the ontology referenced by the first semantic description resource, and a URI of the associated semantic description resource indicated by the association relationship; and the semantic validation request message is used for instructing to perform semantic validation on the semantic information of the first semantic description resource and semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and an ontology referenced by the associated semantic description resource.
- The method according to claim 1, wherein the method further comprises:receiving a semantic validation success response message returned by the apparatus that stores the ontology referenced by the first semantic description resource;performing the operation request related to the first semantic description resource; andsetting, in the first semantic description resource, a parameter indicating that the semantic validation succeeds.
- The method according to claim 1, wherein the method further comprises:receiving a response message that indicates that no semantic validation is performed and that is returned by the apparatus that stores the ontology referenced by the first semantic description resource;performing the operation request related to the first semantic description resource; andsetting, in the first semantic description resource, a parameter indicating that no semantic validation is performed.
- The method according to any one of claims 1 to 3, wherein the determining, based on the association relationship between the first semantic description resource and the another semantic description resource, the another semantic description resource associated with the first semantic description resource is specifically:determining that the first semantic description resource comprises an association attribute indicating the association relationship between the first semantic description resource and the another semantic description resource; ordetermining that a description attribute of the first semantic description resource comprises triplet information indicating the association relationship between the first semantic description resource and the another semantic description resource.
- The method according to any one of claims 1 to 4, wherein the method further comprises:receiving an operation request related to a second semantic description resource, wherein the operation request related to the second semantic description resource comprises: semantic information of the second semantic description resource, and a URI of an ontology referenced by the second semantic description resource;determining that the second semantic description resource is not associated with another semantic description resource;obtaining, based on the URI of the ontology referenced by the second semantic description resource, from an apparatus that stores the ontology referenced by the second semantic description resource, the ontology referenced by the second semantic description resource; andperforming validation on the semantic information of the second semantic description resource by using the ontology referenced by the second semantic description resource.
- The method according to claim 5, wherein the method further comprises:
determining that the validation on the semantic information of the second semantic description resource succeeds, performing the operation request related to the second semantic description resource, and setting, in the second semantic description resource, a parameter indicating that the semantic validation succeeds. - The method according to claim 5 or 6, wherein the determining that the second semantic description resource is not associated with another semantic description resource is specifically:
determining that the second semantic description resource does not comprise an association attribute indicating an association relationship between the second semantic description resource and the another semantic description resource, and determining that a description attribute of the second semantic description resource does not comprise triplet information indicating the association relationship between the second semantic description resource and the another semantic description resource. - The method according to any one of claims 1 to 7, wherein the method further comprises:receiving an operation request related to a third semantic description resource, wherein the operation request related to the third semantic description resource comprises: semantic information of the third semantic description resource, and a URI of an ontology referenced by the third semantic description resource;determining that the third semantic description resource is not associated with a semantic description resource;sending, based on the URI of the ontology referenced by the third semantic description resource, an ontology obtaining request to an apparatus that stores the ontology referenced by the third semantic description resource;determining that the ontology referenced by the third semantic description resource is not received;performing the operation request related to the third semantic description resource; andsetting, in the third semantic description resource, a parameter indicating that no semantic validation is performed.
- The method according to claim 4 or 8, wherein the method further comprises:receiving a semantic description resource obtaining request, wherein the obtaining request carries a URI of a to-be-obtained semantic description resource;determining, based on the URI of the to-be-obtained semantic description, that the to-be-obtained semantic description resource comprises the parameter indicating that no semantic validation is performed;triggering to perform semantic validation on semantic information of the to-be-obtained semantic description resource;determining that the validation on the semantic information of the to-be-obtained semantic description resource succeeds; andsending the to-be-obtained semantic description resource to an apparatus that sends the obtaining request.
- The method according to claim 9, wherein after the determining that the validation on the semantic information of the to-be-obtained semantic description resource succeeds, the method further comprises:
updating the parameter that indicates that no semantic validation is performed and that is comprised in the to-be-obtained semantic description resource to a parameter indicating that the semantic validation succeeds. - A semantic validation method, wherein the method is applied to a Machine-to-Machine Communications M2M system, and the method comprises:receiving a semantic validation request message sent by an apparatus that stores a semantic description resource, wherein the semantic validation request message comprises semantic information of a first semantic description resource, a uniform resource identifier URI of an ontology referenced by the first semantic description resource, and an association relationship between the first semantic description resource and another semantic description resource;obtaining, based on the association relationship between the first semantic description resource and the another semantic description resource, semantic information of the associated another semantic description resource and a URI of an ontology referenced by the associated semantic description resource; andperforming semantic validation on the semantic information of the first semantic description resource and the semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and the ontology indicated by the URI of the ontology referenced by the associated semantic description resource.
- The method according to claim 11, wherein the method further comprises:after the semantic validation succeeds, returning a semantic validation success response message to the apparatus that stores the semantic description resource, wherein the semantic validation success response message is used for instructing to set, for the first semantic description resource, a parameter indicating that the semantic validation succeeds; orwhen the semantic information of the associated another semantic description resource and the URI of the ontology referenced by the associated semantic description resource are not obtained, returning a response message indicating that no semantic validation is performed to the apparatus that stores the semantic description resource, wherein the response message indicating that no semantic validation is performed is used for instructing to set, for the first semantic description resource, a parameter indicating that no semantic validation is performed.
- The method according to claim 11 or 12, wherein the method further comprises:receiving an ontology obtaining request sent by the apparatus that stores the semantic description resource, wherein the ontology obtaining request carries a URI of an ontology, wherein the ontology indicated by the URI of the ontology is used for validating semantic information of the semantic description resource stored in the apparatus that stores the semantic description resource; andreturning the ontology indicated by the URI of the ontology to the apparatus that stores the semantic description resource.
- A semantic validation apparatus, wherein the apparatus is applied to a Machine-to-Machine Communications M2M system, and the apparatus comprises:a receiving unit, configured to receive an operation request related to a first semantic description resource, wherein the operation request related to the first semantic description resource comprises: semantic information of the first semantic description resource, an association relationship between the first semantic description resource and another semantic description resource, and a URI of an ontology referenced by the first semantic description resource;a determining unit, configured to determine, based on the association relationship between the first semantic description resource and the another semantic description resource, that the first semantic description resource is associated with the semantic description resource; anda sending unit, configured to send, based on the URI of the ontology referenced by the first semantic description resource, a semantic validation request message to an apparatus that stores the ontology referenced by the first semantic description resource, wherein the semantic validation request message comprises the semantic information of the first semantic description resource, the URI of the ontology referenced by the first semantic description resource, and a URI of the associated semantic description resource indicated by the association relationship; and the semantic validation request message is used for instructing to perform semantic validation on the semantic information of the first semantic description resource and semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and an ontology referenced by the associated semantic description resource.
- The apparatus according to claim 14, wherein the apparatus further comprises an execution unit, and
the receiving unit is further configured to receive a semantic validation success response message returned by the apparatus that stores the ontology referenced by the first semantic description resource; and the execution unit is configured to: perform the operation request related to the first semantic description resource, and set, in the first semantic description resource, a parameter indicating that the semantic validation succeeds; or
the receiving unit is further configured to receive a response message that indicates that no semantic validation is performed and that is returned by the apparatus that stores the ontology referenced by the first semantic description resource; and the execution unit is configured to: perform the operation request related to the first semantic description resource, and set, in the first semantic description resource, a parameter indicating that no semantic validation is performed. - The apparatus according to claim 14 or 15, wherein that a determining unit determines, based on the association relationship between the first semantic description resource and the another semantic description resource is specifically:determining that the first semantic description resource comprises an association attribute indicating the association relationship between the first semantic description resource and the another semantic description resource; ordetermining that a description attribute of the first semantic description resource comprises triplet information indicating the association relationship between the first semantic description resource and the another semantic description resource.
- The apparatus according to claim 15 or 16, wherein the apparatus further comprises an obtaining unit and a validation unit, wherein
the receiving unit is further configured to receive an operation request related to a second semantic description resource, wherein the operation request related to the second semantic description resource comprises: semantic information of the second semantic description resource, and a URI of an ontology referenced by the second semantic description resource;
the determining unit is further configured to determine that the second semantic description resource is not associated with another semantic description resource;
the obtaining unit is configured to obtain, based on the URI of the ontology referenced by the second semantic description resource, from an apparatus that stores the ontology referenced by the second semantic description resource, the ontology referenced by the second semantic description resource; and
the validation unit is configured to perform validation on the semantic information of the second semantic description resource by using the ontology referenced by the second semantic description resource. - The apparatus according to claim 17, wherein
the determining unit is further configured to determine that the validation on the semantic information of the second semantic description resource succeeds; and
the execution unit is further configured to: perform the operation request related to the second semantic description resource, and set, in the second semantic description resource, a parameter indicating that the semantic validation succeeds. - The apparatus according to claim 17, wherein that the determining unit determines that the second semantic description resource is not associated with another semantic description resource is specifically:
determining that the second semantic description resource does not comprise an association attribute indicating an association relationship between the second semantic description resource and the another semantic description resource, and determining that a description attribute of the second semantic description resource does not comprise triplet information indicating the association relationship between the second semantic description resource and the another semantic description resource. - The apparatus according to claim 15, wherein the apparatus further comprises a trigger unit, wherein
the receiving unit is further configured to receive a semantic description resource obtaining request, wherein the obtaining request carries a URI of a to-be-obtained semantic description resource;
the determining unit is further configured to determine, based on the URI of the to-be-obtained semantic description, that the to-be-obtained semantic description resource comprises the parameter indicating that no semantic validation is performed;
the trigger unit is further configured to trigger to perform semantic validation on semantic information of the to-be-obtained semantic description resource;
the determining unit is further configured to determine that the validation on the semantic information of the to-be-obtained semantic description resource succeeds; and
the sending unit is further configured to send the to-be-obtained semantic description resource to an apparatus that sends the obtaining request. - A semantic validation apparatus, wherein the apparatus is applied to a Machine-to-Machine Communications M2M system, and the apparatus comprises:a receiving unit, configured to receive a semantic validation request message sent by an apparatus that stores a semantic description resource, wherein the semantic validation request message comprises semantic information of a first semantic description resource, a uniform resource identifier URI of an ontology referenced by the first semantic description resource, and an association relationship between the first semantic description resource and another semantic description resource;an obtaining unit, configured to obtain, based on the association relationship between the first semantic description resource and the another semantic description resource, semantic information of the associated another semantic description resource and a URI of an ontology referenced by the associated semantic description resource; anda validation unit, configured to perform semantic validation on the semantic information of the first semantic description resource and the semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and the ontology indicated by the URI of the ontology referenced by the associated semantic description resource.
- The apparatus according to claim 21, wherein the apparatus further comprises a sending unit, wherein
the sending unit is configured to: after the semantic validation succeeds, return a semantic validation success response message to the apparatus that stores the semantic description resource, wherein the semantic validation success response message is used for instructing to set, for the first semantic description resource, a parameter indicating that the semantic validation succeeds; or
when the obtaining unit does not obtain the semantic information of the associated another semantic description resource and the URI of the ontology referenced by the associated semantic description resource, the sending unit is configured to return a response message indicating that no semantic validation is performed to the apparatus that stores the semantic description resource, wherein the response message indicating that no semantic validation is performed is used for instructing to set, for the first semantic description resource, a parameter indicating that no semantic validation is performed. - A semantic validation apparatus, wherein the apparatus is applied to an M2M system, and the apparatus comprises:a memory, configured to store computer executable program code;a transceiver; anda processor, coupled to the memory and the transceiver, whereinthe program code comprises an instruction, and when the processor executes the instruction, the instruction enables the apparatus to perform the following operations:receiving an operation request related to a first semantic description resource, wherein the operation request related to the first semantic description resource comprises: semantic information of the first semantic description resource, an association relationship between the first semantic description resource and another semantic description resource, and a URI of an ontology referenced by the first semantic description resource;determining, based on the association relationship between the first semantic description resource and the another semantic description resource, that the first semantic description resource is associated with the semantic description resource;sending, based on the URI of the ontology referenced by the first semantic description resource, a semantic validation request message to an apparatus that stores the ontology referenced by the first semantic description resource, wherein the semantic validation request message comprises the semantic information of the first semantic description resource, the URI of the ontology referenced by the first semantic description resource, and a URI of the associated semantic description resource indicated by the association relationship; and the semantic validation request message is used for instructing to perform semantic validation on the semantic information of the first semantic description resource and semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and an ontology referenced by the associated semantic description resource.
- A semantic validation apparatus, wherein the apparatus is applied to an M2M system, and the apparatus comprises:a memory, configured to store computer executable program code;a transceiver; anda processor, coupled to the memory and the transceiver; whereinthe program code comprises an instruction, and when the processor executes the instruction, the instruction enables the apparatus to perform the following operations:receiving a semantic validation request message sent by an apparatus that stores a semantic description resource, wherein the semantic validation request message comprises semantic information of a first semantic description resource, a uniform resource identifier URI of an ontology referenced by the first semantic description resource, and an association relationship between the first semantic description resource and another semantic description resource;obtaining, based on the association relationship between the first semantic description resource and the another semantic description resource, semantic information of the associated another semantic description resource and a URI of an ontology referenced by the associated semantic description resource; andperforming semantic validation on the semantic information of the first semantic description resource and the semantic information of the associated semantic description resource by using the ontology indicated by the URI of the ontology referenced by the first semantic description resource and the ontology indicated by the URI of the ontology referenced by the associated semantic description resource.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510998415.7A CN106919550B (en) | 2015-12-25 | 2015-12-25 | Semantic verification method and device |
PCT/CN2016/111102 WO2017107903A1 (en) | 2015-12-25 | 2016-12-20 | Method and device for semantic verification |
Publications (3)
Publication Number | Publication Date |
---|---|
EP3367255A1 true EP3367255A1 (en) | 2018-08-29 |
EP3367255A4 EP3367255A4 (en) | 2018-12-26 |
EP3367255B1 EP3367255B1 (en) | 2020-08-26 |
Family
ID=59088998
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP16877713.4A Active EP3367255B1 (en) | 2015-12-25 | 2016-12-20 | Method and device for semantic verification |
Country Status (6)
Country | Link |
---|---|
US (1) | US11088989B2 (en) |
EP (1) | EP3367255B1 (en) |
JP (1) | JP6578067B2 (en) |
KR (1) | KR102084473B1 (en) |
CN (1) | CN106919550B (en) |
WO (1) | WO2017107903A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11553618B2 (en) | 2020-08-26 | 2023-01-10 | PassiveLogic, Inc. | Methods and systems of building automation state load and user preference via network systems activity |
US11830383B2 (en) | 2021-09-08 | 2023-11-28 | PassiveLogic, Inc. | External activating of quiescent device |
US20230071312A1 (en) * | 2021-09-08 | 2023-03-09 | PassiveLogic, Inc. | External Activation of Quiescent Device |
Family Cites Families (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7249380B2 (en) * | 2002-09-05 | 2007-07-24 | Yinan Yang | Method and apparatus for evaluating trust and transitivity of trust of online services |
US7103597B2 (en) * | 2002-10-03 | 2006-09-05 | Mcgoveran David O | Adaptive transaction manager for complex transactions and business process |
US8495004B2 (en) * | 2006-03-27 | 2013-07-23 | International Business Machines Corporation | Determining and storing at least one results set in a global ontology database for future use by an entity that subscribes to the global ontology database |
US20100185700A1 (en) * | 2007-09-17 | 2010-07-22 | Yan Bodain | Method and system for aligning ontologies using annotation exchange |
US8140680B2 (en) * | 2008-01-09 | 2012-03-20 | International Business Machines Corporation | Machine-processable semantic description for resource management |
US8954474B2 (en) * | 2008-04-21 | 2015-02-10 | The Boeing Company | Managing data systems to support semantic-independent schemas |
KR101086996B1 (en) * | 2008-10-30 | 2011-11-29 | 주식회사 케이티 | Apparatus for generating ontology and method thereof |
US20100281061A1 (en) | 2009-04-30 | 2010-11-04 | International Business Machines Corporation | Semantic Data Validation of Disjoint Data |
US9384327B2 (en) * | 2009-09-14 | 2016-07-05 | Clinerion Ltd. | Semantic interoperability system for medicinal information |
US20110087685A1 (en) | 2009-10-09 | 2011-04-14 | Microsoft Corporation | Location-based service middleware |
US8750145B2 (en) * | 2009-11-23 | 2014-06-10 | Interdigital Patent Holdings, Inc. | Method and apparatus for machine-to-machine communication registration |
BR112012022204B1 (en) * | 2010-03-01 | 2022-04-19 | IOT Holdings, Inc | Gateway between machines |
CN102136933B (en) | 2010-09-30 | 2013-08-28 | 华为技术有限公司 | Equipment management method, middleware and machine communication platform, equipment and system |
WO2012118711A2 (en) * | 2011-03-03 | 2012-09-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for accessing services affiliated with a discovered service provider |
CN102542513B (en) * | 2012-01-17 | 2015-04-01 | 上海交通大学 | Body-based verification tool of power grid public information model and method thereof |
CN103596117B (en) * | 2012-08-13 | 2017-12-15 | 华为终端(东莞)有限公司 | It was found that the method for machine-to-machine service, equipment and system |
KR101432128B1 (en) * | 2013-01-29 | 2014-08-21 | 주식회사 케이티 | M2M platform for converting resources into abstracted device object on M2M network |
CN103473409B (en) * | 2013-08-25 | 2016-06-01 | 浙江大学 | The FPGA automatic fault diagnosis method in a kind of knowledge based storehouse |
CN103593335A (en) * | 2013-09-05 | 2014-02-19 | 姜赢 | Chinese semantic proofreading method based on ontology consistency verification and reasoning |
KR20160091314A (en) * | 2013-11-29 | 2016-08-02 | 엘지전자 주식회사 | Method for service subscription resource-based authentication in wireless communication system |
CN104750709A (en) * | 2013-12-26 | 2015-07-01 | ***通信集团公司 | Semantic retrieval method and semantic retrieval system |
US11238073B2 (en) * | 2014-02-07 | 2022-02-01 | Convida Wireless, Llc | Enabling resource semantics |
WO2016011361A1 (en) * | 2014-07-18 | 2016-01-21 | Convida Wireless, Llc | M2m ontology management and semantics interoperability |
WO2016109521A1 (en) * | 2014-12-30 | 2016-07-07 | Convida Wireless, Llc | Semantics annotation and semantics repository for m2m systems |
WO2017012678A1 (en) * | 2015-07-20 | 2017-01-26 | Nec Europe Ltd. | Method and system for querying semantic information stored across several semantically enhanced resources of a resource structure |
US20180089281A1 (en) * | 2016-09-29 | 2018-03-29 | Convida Wireless, Llc | Semantic query over distributed semantic descriptors |
-
2015
- 2015-12-25 CN CN201510998415.7A patent/CN106919550B/en active Active
-
2016
- 2016-12-20 JP JP2018531661A patent/JP6578067B2/en active Active
- 2016-12-20 EP EP16877713.4A patent/EP3367255B1/en active Active
- 2016-12-20 KR KR1020187016789A patent/KR102084473B1/en active IP Right Grant
- 2016-12-20 WO PCT/CN2016/111102 patent/WO2017107903A1/en active Application Filing
-
2018
- 2018-06-19 US US16/012,421 patent/US11088989B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN106919550B (en) | 2021-09-07 |
JP6578067B2 (en) | 2019-09-18 |
EP3367255A4 (en) | 2018-12-26 |
JP2019507917A (en) | 2019-03-22 |
KR102084473B1 (en) | 2020-03-04 |
CN106919550A (en) | 2017-07-04 |
US11088989B2 (en) | 2021-08-10 |
KR20180084092A (en) | 2018-07-24 |
US20180300403A1 (en) | 2018-10-18 |
WO2017107903A1 (en) | 2017-06-29 |
EP3367255B1 (en) | 2020-08-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11711682B2 (en) | Cross-resource subscription for M2M service layer | |
EP2957085B1 (en) | Service layer resource propagation across domains | |
KR102245367B1 (en) | Method and apparatus for authenticating access authority for specific resource in wireless communication system | |
US20140289366A1 (en) | Service providing method and system for instance hosting | |
US11088989B2 (en) | Semantic validation method and apparatus | |
US20170337088A1 (en) | Managing application relationships in machine-to-machine systems | |
CN108306844B (en) | Method for API communication between server and client | |
US11671514B2 (en) | Service layer message templates in a communications network | |
US11936749B2 (en) | Cross-domain discovery between service layer systems and web of things systems | |
US10715628B2 (en) | Attribute operating method and device | |
EP3128715A1 (en) | Resource creation method and apparatus | |
WO2016192746A1 (en) | Method and apparatus for implementing self-operation functions within a network | |
US20230421663A1 (en) | Efficient resource representation exchange between service layers | |
WO2017206634A1 (en) | Method and device for querying semantics | |
Creutz et al. | Cyber-Physical Contracts in Offline Regions | |
EP4113902A1 (en) | System operation based on intent service graph | |
CN115658708A (en) | Data association method, device, server and computer readable storage medium | |
CN117099345A (en) | Apparatus and method for generating a response to an attack in a communication network using machine learning | |
WO2019157274A1 (en) | Service layer methods for offloading iot application message generation and response handling |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE |
|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180522 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
A4 | Supplementary search report drawn up and despatched |
Effective date: 20181126 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G06F 17/27 20060101AFI20181120BHEP Ipc: H04L 29/12 20060101ALI20181120BHEP Ipc: H04L 29/08 20060101ALI20181120BHEP Ipc: H04W 4/00 20180101ALI20181120BHEP Ipc: G06F 17/30 20060101ALI20181120BHEP |
|
DAV | Request for validation of the european patent (deleted) | ||
DAX | Request for extension of the european patent (deleted) | ||
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602016042968 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: G06F0017270000 Ipc: H04L0029060000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 12/06 20090101ALI20200131BHEP Ipc: H04W 4/70 20180101ALI20200131BHEP Ipc: H04W 4/38 20180101ALI20200131BHEP Ipc: G06F 40/20 20200101ALI20200131BHEP Ipc: H04L 29/06 20060101AFI20200131BHEP |
|
INTG | Intention to grant announced |
Effective date: 20200220 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
GRAL | Information related to payment of fee for publishing/printing deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR3 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAR | Information related to intention to grant a patent recorded |
Free format text: ORIGINAL CODE: EPIDOSNIGR71 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
INTC | Intention to grant announced (deleted) | ||
INTG | Intention to grant announced |
Effective date: 20200716 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602016042968 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1307499 Country of ref document: AT Kind code of ref document: T Effective date: 20200915 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201228 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201126 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201127 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201126 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20200826 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1307499 Country of ref document: AT Kind code of ref document: T Effective date: 20200826 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20201226 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602016042968 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
26N | No opposition filed |
Effective date: 20210527 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20201231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201220 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201220 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602016042968 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0029060000 Ipc: H04L0065000000 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602016042968 Country of ref document: DE Owner name: HUAWEI CLOUD COMPUTING TECHNOLOGIES CO., LTD.,, CN Free format text: FORMER OWNER: HUAWEI TECHNOLOGIES CO. LTD., SHENZHEN, GUANGDONG, CN |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20220428 AND 20220504 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200826 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201231 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230524 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20231102 Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20231108 Year of fee payment: 8 Ref country code: DE Payment date: 20231031 Year of fee payment: 8 |