[0052] Directory services can be effectively applied to geospatial information resources, such as the retrieval and management of sensor metadata, and can be bound to specific applications and their metadata information models to form content and functions that meet their own needs, and provide external query services. The invention constructs a registration information model that can store sensor information, designs the mapping relationship between the sensor information model and the registration information model, and supports direct registration of sensors.
[0053] The present invention will be further explained below with specific embodiments in conjunction with the drawings:
[0054] The embodiment provides a mapping method that supports the direct registration of sensors, including constructing a sensor registration information model and constructing a mapping relationship from the sensor information model to the registration information model.
[0055] Constructing the sensor registration information model: including five sub-steps: building the registration package, defining the external object class of the registration information model, defining the relationship class of the registration information model, defining the classification structure of the registration information model, and defining the extension attribute classes of the registration information model.
[0056] Constructing the mapping relationship from sensor information model to registration information model: including building the mapping process from sensors to registered objects, building the mapping of sensor types and registered object types, building the mapping from sensor properties to registered object properties, and building the relationship between sensor related properties and registered objects Mapping, four sub-steps.
[0057] The specific implementation process of the embodiment is as follows:
[0058] Step S1: Construct a sensor registration information model, and the construction process is as follows figure 1 Shown. Details of the sensor registration information model, such as figure 2 Shown. figure 2 The concepts in need to be explained: rim:RegistryPackage represents the registration package of the registered object; rim:Service represents the service information related to the registered object; < > Indicates that the following four attributes are classification information of the registered package; Indicates that the listed attributes are the contents of the extended attributes of the registered object; < > Indicates that the listed attributes are the attributes inherited by the registered object from the parent class, and the rest of the description information is shown in Table 1.
[0059] Table 1 figure 2 The meaning of classes and attributes
[0060]
[0061]
[0062] S1-1 Create an extended registration package RegistryPackage: Regarding the relevant information that the sensor needs to store, build a registration extension package RegistryPackage of the registration information model. The registered feature classes for storage definitions mainly include external object classes, relationship classes, classifications and attributes.
[0063] S1-2 defines the external object class ExtrinsicObject that stores sensor registration objects: inherited by the external object class, including two external object classes Component and System. Component represents parts in the real world, such as thermometers; System can be composed of components, such as weather stations or satellite platforms.
[0064] S1-3 defines the relationship class Association of registered objects: inherited by the rim: Association class, including four types of AccessibleThrough, ComposedOf, InputConnection and OutputConnection, and defines the target object (SourceObject) and source object (TargetObject) of each Association. The specific description of the relationship is as follows: The "ComposedOf" relationship type represents the relationship between System and components, and can be used to build the relationship between the sensor platform and the sensor. These relationships can be linked by input values, output values and parameters, which are described by "InputConnection", "OutputConnection" and "ParameterConnection" respectively. The "AccessibleThrough" relationship links the process model and related services.
[0065] S1-4 defines the classification scheme ClassificationScheme of registered objects: According to different sensor types and application fields, a classification scheme (ClassificationScheme), classification node (ClassificationNode) and classification relationship (Classification) are added. Construct four classification structures, such as image 3 As shown, legend reference figure 2. image 3 It should be noted that ClassificationScheme represents the classification structure of the registered object; ClassificationNode represents the classification node of the classification object, and the rest of the description information is shown in Table 3.
[0066] Table 2 image 3 Concept sheet
[0067]
[0068] (1) Define the classification architecture of the intended application (IntendedApplication), which describes the application fields that the sensor can be used in; for example, when the process model can be applied to flood monitoring, the classification node "water" and its subclass "flooddetection" will be automatically added to identify Process model.
[0069] (2) Define the classification structure of service type (ServiceType), such as sensor observation service (SOS) and sensor planning service (SPS).
[0070] (3) Define the classification structure of the system type SystemType, including two classification nodes: one is the observation platform type PlatformType of the sensor, such as satellite platform; the other is the sensor type SensorType.
[0071] (4) Define the classification structure of the orbit type OrbitType, and describe the orbit type of the satellite platform, such as sun-synchronous orbit.
[0072] S1-5 defines the extended attribute class (Slot) of the registered object: According to the attribute characteristics of the sensor, it is necessary to define the Slot of the registered object to store specific attribute information. Component slot includes keywords (keywords), sensor location information (location), observation range (ObservedBoundingBox), valid time start node (ValidTimeBegin), valid time end node (ValidTimeEnd), input (inputs), output (outputs) ) And parameters; the slot of System is the same as that of Component.
[0073] Step S2: Construct a mapping relationship from the sensor information model to the registration information model.
[0074] Step S2-1: Construct the mapping process from sensor information model to registration information model, such as Figure 4 As shown, Figure 4 Refer to Table 1 for the conceptual information shown in. The detailed mapping process is as follows:
[0075] (1) Determine the type of sensor information model. If the sensor is described as System in the sensor information model, it will be converted to the external object class System; if it is described as Component, it will be converted to the external object class Component to store the registered object.
[0076] (2) According to the type of the external object class, perform the mapping from the sensor attribute to the registered object attribute, including the identifier, name, description, classification, contact information and conversion to Slot mapping. The attribute mapping process is as follows Figure 5 Shown:
[0077] Judge whether the attribute is identifier-ID, if yes, it will be mapped to the identifier of the registration information model; otherwise, judge whether the attribute has a name and description, if yes, then be mapped to the name and description attributes of the registration information model; otherwise Judge whether the attribute is contact information contact, if yes, it will be mapped to the organization information attribute Organization and personal information attribute person of the registration information model; otherwise, judge whether the attribute is service information Service, if yes, it will be mapped to the service service of the registration information model; otherwise, judge whether The attribute classification information classification is mapped to the classification node ClassificationNode and the classification relationship classification, otherwise it is mapped to the extended attribute Slot.
[0078] (3) When performing relational mapping, the conversion process is divided into two situations:
[0079] The first is that the external object class is System, and it is necessary to judge whether the sensor information model "includes components", and if the judgment result is "No", the judgment of "service-related" is performed. If the judgment result of "contains components" is "yes", the relationship "ComposedOf" is generated, and the judgment of "contains connection" is performed. If there is a connection in the description of the sensor, generate the relations "OutputConnection", "InputConnection" and "ParameterConnection" based on the link between the input, output and parameters between the system and the component, and enter the judgment of "service-related"; if the description of the sensor If there is no connection, enter the judgment of "service-related", then the relationship "AccessibleThrough" is generated to realize the connection between the sensor and the service and complete the mapping process. If it is not related to the service, directly end the mapping process.
[0080] The second is that the external object class is Component. It is judged whether it is related to the service, and the relationship "AccessibleThrough" is generated if it exists, otherwise the mapping is completed.
[0081] Step S2-2: Construct a mapping between sensor type and registered object type, such as Image 6 As shown in the mapping relations ① and ②, the sensor object type is mapped to the ObjectType attribute of the external object class, that is, for the system-System, the object type ExtrinsicObjectObjectType of the registered object is mapped; for the component-Component, the object type of the registered object ExtrinsicObjectObjectType is mapped . Image 6 Refer to Table 1 for the description of the concepts in.
[0082] Step S2-3: Construct a mapping from sensor attributes to registered object attributes, which mainly includes the following parts:
[0083] (1) Mapping of identifiers. Such as Image 6 As shown in the mapping relations ③ and ④, the identifier ID is mapped to the logical ID and ID, respectively, to describe the inherent ID of the sensor and the ID that changes with the version number. That is, for the identifier-UniqueID, the logical id (ExtrinsicObjectlid) of the registered object is mapped, and the id (ExtrinsicObjectid) of the registered object is mapped.
[0084] (2) Mapping of full name and description information. Such as Figure 7 The mapping relations are shown in ⑤ and ⑥. That is, for name-longName, map the name of the registered object rim:Name/rim:LocalizedString/value; for description-description, map the description information of the registered object rim:Description/rim:LocalizedString/value.
[0085] (3) Mapping of contact information. Such as Image 6 As shown in the mapping relations ⑦ and ⑧, there are mainly sensor organization and personal contact information mapping. That is, for the organization contact information sml:organizationName, map the organization information of the registered object /rim:Organization/rim:Name/rim:LocalizedString/value; for the personal contact information sml:individualName, map the personal information of the registered object /rim:Person/rim :PersonName.
[0086] (4) Mapping of service information. Such as Image 6 As shown in the mapping relationship ⑨, the Uniform Resource Locator (URL) of the service is stored in the access URL (accessURL) attribute of the service binding (ServiceBinding). That is, for the service ServiceURL, the service information of the registered object is mapped
[0087] rim:Service/rim:ServiceBinding/accessURI.
[0088] (5) The mapping of classification structure, such as Figure 7 Shown. Figure 7 The description is as follows. When the path description in the sensor information model is sml:classifier/sml:Term[[definition=“urn:ogc:def:property:OGC:1.0:application”], it means that the sensor’s classification information is for the expected application Related Information. thus Figure 7 The left column in the middle indicates the expected application in turn, the path of the sensor type, platform type, track type and service type in the sensor information model.
[0089] (6) Mapped to Slot. Such as Figure 8 As shown, it mainly includes abbreviations, keywords, effective time starting point, effective time ending point, location, observation range, input, output and parameters. Figure 8 The description is as follows, the path sml:validtime/gml:TimePeriod/gml:beginPosition and sml:validtime/gml:TimePeriod/gml:endPosition in the sensor information model respectively represent the beginning and end of the effective time of the sensor; sweet:field[name="observedBBOX "]/swe:Envelope represents the description of the sensor's observation range; sml:input/swe:ObservableProperty/definition describes sensor input information; sml:output/swe:Quantity/definition describes sensor output information; sml:parameter/sml:quantity/ gml:description represents sensor parameter information. The path rim:Slot[name=”urn:Liesmars:def:slot:OGC-Sensor::ShortName”]/rim:ValueList/rim:Value[1] in the registration information model means that the extended attribute can have a value for ShortName, The path representation of other registration information models is similar. It should be noted that rim:Value[*] indicates that there can be multiple values, and rim:AnyValue[1] indicates that the type of the extended attribute value can be any type.
[0090] For the expected application sml:classifier/sml:Term[definition=”urn:ogc:def:property:OGC:1.0:application”]; add an instance of the classification node ClassificationNode in the classification architecture IntendedApplication;
[0091] For sensor type sml:classifier/sml:Term[definition=”urn:ogc:def:property:OGC:1.0:sensorType”]; add an instance of the classification node SensorType in the classification architecture SystemType;
[0092] For platform type sml:classifier/sml:Term[definition=”urn:ogc:def:property:OGC:1.0:PlatformType”]; add an instance of the classification node PlatformType in the classification architecture SystemType;
[0093] For the track type sml:classifier/sml:Term[definition=”urn:ogc:def:property:OGC:1.0:OrbitType”], add an instance of the classification node ClassificationNode in the classification architecture OrbitType;
[0094] Type of service
[0095] swe:serviceLayer/swe:DataRecord/swe:field[name=”urn:ogc:def:interface:OGC:1.0:ServiceType"], add an instance of the classification node ClassificationNode in the classification architecture ServiceType.
[0096] Step S2-4: Construct a mapping from sensor-related attributes to registered object relationships, such as Picture 9 As shown, it mainly includes "ComposedOf", "InputConnection", "OutputConnection", "ParameterConnection" and "AccessibleThrough".
[0097] The abbreviation-shortName is mapped to rim:Slot[name=”urn:Liesmars:def:slot:OGC-Sensor::ShortName”]/rim:ValueList/rim:Value[1];
[0098] The keyword-keywords is mapped to rim:Slot[name=”urn:Liesmars:def:slot:OGC-Sensor::keywords”]/rim:ValueList/rim:Value[*];
[0099] The effective time starting point sml:validTime/gml:TimePeriod/gml:beginPosition is mapped to
[0100] rim:Slot[name=”
[0101] urn:Liesmars:def:slot:OGC-Sensor::ValidTimeEnd”]/rim:ValueList/rim:Value[1];
[0102] Location-Location maps to
[0103] rim:Slot[name=”
[0104] urn:Liesmars:def:slot:OGC-Sensor::Location”]/rim:ValueList/rim:AnyValue[1];
[0105] Observation range-swe:field[name="observedBBOX"]/swe:Envelope is mapped to
[0106] rim:Slot[name=”
[0107] urn:Liesmars:def:slot:OGC-Sensor::ObservedBoundingBox”]/rim:ValueList/rim:AnyValue[1];
[0108] Input sml:input/swe:ObservableProperty/definition is mapped to
[0109] rim:Slot[name=”urn:Liesmars:def:slot:OGC-Sensor::Inputs”]/rim:ValueList/rim:Value[*];
[0110] The output sml:output/swe:Quantity/definition maps to
[0111] rim:Slot[name=”urn:Liesmars:def:slot:OGC-Sensor::Outputs”]/rim:ValueList/rim:Value[*];
[0112] The parameter sml:parameter/sml:quantity/gml:description is mapped to
[0113] rim:Slot[name=”
[0114] urn:Liesmars:def:slot:OGC-Sensor::Parameters"]/rim:ValueList/rim:Value[*]
[0115] Among them, ServiceSpecificSensor needs to be stored in the Slot of the relationship "AccessibleThrough", such as Picture 9 The fourth mapping relationship is shown.
[0116] Through the definition of the above-mentioned mapping relationship, the direct registration of sensors can be supported, which helps to realize efficient management of sensors.
[0117] The specific embodiments described herein are merely examples to illustrate the spirit of the present invention. Those skilled in the technical field of the present invention can make various modifications or additions to the described specific implementations or use similar alternatives, but they will not deviate from the spirit of the present invention or go beyond what is defined in the appended claims. range.
