CN101257495A - Semantic message transmission method and communication system as well as message processing device - Google Patents
Semantic message transmission method and communication system as well as message processing device Download PDFInfo
- Publication number
- CN101257495A CN101257495A CNA2008100840808A CN200810084080A CN101257495A CN 101257495 A CN101257495 A CN 101257495A CN A2008100840808 A CNA2008100840808 A CN A2008100840808A CN 200810084080 A CN200810084080 A CN 200810084080A CN 101257495 A CN101257495 A CN 101257495A
- Authority
- CN
- China
- Prior art keywords
- semantic
- message
- network service
- processing apparatus
- gateway side
- 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
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a semantic information transmitting method, a communication system and a message handling device, used for information alternation between the semantic network service functional entity and the gateway. The implement of the invention includes: receiving the first semantic information transmitted by the semantic network service functional entity; enquiring the first nonsemantic information corresponding to the first semantic information in the preset corresponding relation of semantic information and nonsemantic information; transmitting the first nonsemantic information to the gateway device. The implement of the invention also provides a communication system and a message handling device.
Description
Technical field
The present invention relates to communication field, relate in particular to a kind of semantic method for message transmission and communication system and message processing apparatus.
Background technology
Mutual actuating logic all is predefined between service of existing application layer and the gateway frame interface, in case application demand changes, mutual actuating logic need adopt artificial mode to upgrade or change between top service and the framework interface, therefore semantic network (Web) service technology arises at the historic moment, this technical advantage is to have the ability of reasoning, can can reduce artificial participation to a great extent according to the variation self actuating logic of extraneous demand.
But the inventor finds in realizing process of the present invention: semantic network service function entity and the extraneous mutual message that all is based on semanteme, and existing gateway can only support the request of non-semantic message to handle.Various mutual in, the authentication link is that service is used and first mutual link of gateway, is further mutual basis.From the prior art, the authentication part of existing gateway does not possess with the semantic network service carries out the mutual ability of authentication, be the authentication of existing gateway partly be merely able to handle non-semantic service based on interface description language (IDL, Interface Description Language) or web service definition language (WSDL, Web Service Definition Language) non-semantic message such as, can't solve the authentication problem of semantic network service, cause the follow-up of semantic network service and gateway can't carry out alternately.
Summary of the invention
The embodiment of the invention provides a kind of semantic method for message transmission and communication system and message processing apparatus, makes the semantic network service function entity to carry out interacting message with gateway.
The semantic method for message transmission that the embodiment of the invention provides comprises: receive the first semantic message that the semantic network service function entity sends; The first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message; Send the described first non-semantic message to the gateway side device.
The communication system that the embodiment of the invention provides comprises: message processing apparatus, and the communication that can be used for handling between semantic network service function entity and the gateway side device connects; Described message processing apparatus is used to receive the first semantic message that described semantic network service function entity sends, the first corresponding non-semantic message of the inquiry described first semantic message sends the described first non-semantic message to described gateway side device in the corresponding relation of the semantic message that presets and non-semantic message; Described semantic network service function entity is used for sending the first semantic message to described message processing apparatus; Described gateway side device is used to receive the first non-semantic message that described message processing apparatus sends.
The message processing apparatus that the embodiment of the invention provides comprises: semantic Message Processing engine message conversion subelement; Described message conversion subelement provides corresponding relation between semantic message and the non-semantic message to described semantic Message Processing engine; The corresponding relation that described semantic Message Processing engine is used for providing according to described message conversion subelement is non-semantic message with semantic message conversion, or is semantic message with non-semantic message conversion.
As can be seen from the above technical solutions, the embodiment of the invention has the following advantages:
In the embodiment of the invention, receive after the first semantic message of semantic network service function entity transmission, the first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message, and send the described first non-semantic message to the gateway side device.So can realize the conversion between semantic message and the non-semantic message in the embodiment of the invention, promptly handle non-semantic message by the gateway side device, and handle semantic message by the semantic network service function entity, realize alternately by message conversion between the two, so the embodiment of the invention makes the semantic network service function entity to carry out interacting message with gateway.
Description of drawings
Fig. 1 is the semantic method for message transmission first embodiment flow chart in the embodiment of the invention;
Fig. 2 is the semantic method for message transmission second embodiment flow chart in the embodiment of the invention;
Fig. 3 is a communication system embodiment schematic diagram in the embodiment of the invention;
Fig. 4 is a message processing apparatus embodiment schematic diagram in the embodiment of the invention.
Embodiment
The embodiment of the invention provides a kind of semantic method for message transmission and communication system and message processing apparatus, makes the semantic network service function entity to carry out interacting message with gateway.
Below the method for message transmission in the embodiment of the invention is described in detail, sees also Fig. 1, this
Semantic method for message transmission first embodiment comprises among the bright embodiment:
101, receive the first semantic message that the semantic network service function entity sends;
In the present embodiment, the service that is provided when the semantic network service function entity needs and the gateway side device carries out then can sending the first semantic message to the gateway side device when mutual.
Need to prove, semantic message described in present embodiment and the subsequent embodiment is meant the message that includes concrete implication, this implication is used to express user's expectation, this implication can directly be understood by machine simultaneously, authentication request message for example, user expectation authenticates by this authentication request message, service end is after receiving this authentication request message, can know that user expectation authenticates, and can authenticate the user according to this authentication request message, be understandable that the semantic message in the practical application can also be the message of other types equally, does not limit herein.
Message processing apparatus receives the first semantic message that this semantic network service function entity sends, concrete message processing apparatus can be integrated in the gateway, perhaps independently be present in the network, but semantic network service function entity and gateway side device interactive messages can be passed through this message processing apparatus.
102, the first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message;
Message processing apparatus gets access to after the first semantic message of semantic network service function entity transmission, can judge that according to the sign of this message this message is semantic message, and because the gateway side device is not supported semantic message, so message processing apparatus is inquired about the first corresponding non-semantic message of this first semantic message according to this first semantic message in the corresponding relation between the semantic message that presets and the non-semantic message.
Need to prove, when system constructing or initialization, preset the corresponding relation between semantic message and the non-semantic message, corresponding semantic message is consistent or similar with the function that non-semantic message is realized, for example, if the first semantic message is used to carry out authentication request, first then corresponding with this first semantic message non-semantic message is used to carry out authentication request equally, and just the data structure of the first semantic message and the first non-semantic message is different.
103, send the described first non-semantic message to the gateway side device.
Message processing apparatus sends this first non-semantic message so that the gateway side device can be carried out subsequent operation according to this first non-semantic message to the gateway side device after getting access to the first non-semantic message corresponding with the first semantic message.
In the present embodiment, message processing apparatus can be known the purpose side of this first semantic message according to the first semantic message that receives, promptly which gateway side device is this first semantic message mail to from the semantic network service function entity, for example, if this first semantic message is used to carry out authentication request, then message processing apparatus can know that the purpose side of this first semantic message is the gateway side authentication device, then message processing apparatus is after getting access to the first corresponding non-semantic message, this first non-semantic message is sent to the gateway side authentication device, makes this authentication device to carry out authentication according to this first non-semantic message.
In the above-mentioned flow process, because message processing apparatus can be corresponding non-semantic message with semantic message conversion, so the gateway side device can be handled accordingly according to the non-semantic message after the conversion, therefore can realize the interacting message between semantic network service function entity and the gateway side device.
In actual applications, interacting message is two-way often, so in the present embodiment, the gateway side device can send message to the semantic network service function entity too, particularly, the gateway side device sends the second non-semantic message to message processing apparatus, message processing apparatus can judge that according to the sign of this message this message is non-semantic message, so message processing apparatus is according to this second non-semantic message second corresponding semantic message of this second non-semantic message of inquiry in the corresponding relation between the semantic message that presets and the non-semantic message.
For example, in the above-mentioned authorizing procedure, the gateway side authentication device carries out generating authentication responses message after the authentication according to the first non-semantic message, and this authentication responses message is sent to message processing apparatus, message processing apparatus judges that the purpose side of this authentication responses message is the semantic network service function entity, be semantic authentication responses message then with this authentication responses message conversion, and the semantic authentication responses message that will obtain after will changing is sent to the semantic network service function entity, makes the semantic network service function entity to carry out follow-up flow process according to this semanteme authentication responses message.
By above-mentioned flow process as can be known, in the present embodiment, message processing apparatus can be changed semantic message and non-semantic message, when needs send to the gateway side device, message processing apparatus is non-semantic message with semantic message conversion, when needs sent to the semantic network service function entity, message processing apparatus was semantic message with non-semantic message conversion, thus the present embodiment scheme can so that the semantic network service function entity can and the gateway side device between carry out interacting message.
For ease of understanding, describe with an instantiation below, being example in the following embodiments with the authorizing procedure describes the flow process of interacting message, is understandable that in actual applications, concrete message interaction process is not limited to authorizing procedure.
See also Fig. 2, semantic method for message transmission second embodiment comprises in the embodiment of the invention:
201, receive semantic initial authentication request message;
The semantic network service function entity is to the initial authentication request message initiateAuthentication of network side authentication device transmission semantization, and this semanteme initial authentication request message comprises client territory clientDomain and the auth type authType based on body.
The following describes in the embodiment of the invention, contact between " semanteme " and " body ": " semanteme " just is meant that various resources in the network (such as the data on the network, webpage etc.) have implication, this implication not only can be understood by the user, also can be by machine perception.
" body " then is to make implication both be understood by the user, also by the approach of machine perception and mode, that is to say, body is that the formalization to the shared ideas model offers some clarification on, and body provides basic terms and the relation that constitutes association area vocabulary.So can describe various resources on the network with body in the present embodiment.For example: client territory " clientDomain " uses ontology representation, and like this, " clientDomain " this notion has just had semanteme.
Need pass through message processing apparatus owing to carry out interacting message between semantic network service function entity and the network side authentication device in the present embodiment, so message processing apparatus can at first obtain the semantic initial authentication request message that the semantic network service function entity sends.
For ease of understanding, the authentication process with concrete generalized calls control (GCC, Generic Call Control) service is that example describes below:
With auth type parameter authType is example, and its parametric form is as follows.
<owl:Class rdf:ID＝″authType″>
<rdfs:subClassOf rdf:resource＝″#ParlayType″/>
<rdfs:comment rdf:datatype＝″http://1.org/2001/XMLSchema#string″>
Auth type
</rdfs:comment>
</owl:Class>
Concrete implication to above-mentioned parameter is described below:
What " owl:Class " expression defined is a body class, and ID represents the title of this body;
<rdfs:subClassOfrdf:resource＝″#ParlayType″/>
Wherein, subClassOf represents that this body class (authType) that defines is the subclass of this body class of ParlayType;
<rdfs:comment rdf:datatype＝″http://1.org/2001/XMLSchema#string″>
Wherein, datatype represents that the concrete manifestation form of authType is character string (String);
The effect of above-mentioned body is a definition authType parameter.
202, semantic initial authentication request message is carried out buffer memory;
Message processing apparatus can be with this request message buffer memory to the formation of application side message sink after getting access to semantic initial authentication request message, need to prove, this application side message sink formation is used for the message of application side (being semantic network service function entity side) is carried out buffer memory and queuing, this application side message sink formation can be the memory of a stack architecture, or the memory of data link table structure, or the memory of other data store organisations, this application side message sink formation can be arranged in message processing apparatus, or independent the existence.
203, according to the corresponding relation that presets semantic initial authentication request message is converted to WSDL message;
Particularly, when semantic initial authentication request message is buffered to the formation of application side message sink, application side pretreatment unit in the message processing apparatus is searched in preset mapping table and the corresponding implementation identifier of semantic initial authentication request (ID), be ID_initiateAuthentication, this application side pretreatment unit is used for determining the implementation ID of current semantic message correspondence.
Concrete semantic message and the mapping table between the implementation ID are as shown in the table:
Table 1
| Semantic message | Implementation ID |
| initiateAuthentication | ID_initiateAuthentication |
Need to prove that this mapping table is used to store the implementation of semantic message and this semanteme message correspondence, function that promptly should semanteme message, and need carry out which kind of processing according to this semanteme message.
After the application side pretreatment unit gets access to implementation ID, semantic initial authentication request message and this implementation ID are sent to semantic Message Processing engine in the message processing apparatus, create a running example by this semanteme Message Processing engine according to this semanteme initial authentication request message and this implementation ID, this running example calls corresponding implementation information initiateAuthenticationProcess according to implementation ID semantic initial authentication request is handled.Wherein, with the parameter c lientDomain in the semantic initial authentication request and authType input as implementation initiateAuthenticationProcess.
The process of above-mentioned establishment running example can be regarded as the object of creating class in the present embodiment, and invoked procedure information is that the object of creating realizes that by the function that calls himself wherein clientDomain and authType are two parameters of function.
The message conversion subelement that semantic Message Processing engine can trigger in the process of implementation initiateAuthenticationProcess operation in the message processing apparatus carries out message conversion with request message conversion subelement to semantic initial authentication request message, the message conversion subelement is to the map information initiateAuthenticationWsdlGrounding of the local storage of semantic Message Processing engine feedback, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message.
Semantic Message Processing engine is converted to initiateAuthentication request message based on WSDL, promptly non-semantic initial authentication request message according to this map information with semantic initiateAuthentication request message.
Need to prove, all describe in present embodiment and the subsequent embodiment with the message of WSDL form example as non-semantic message, being understandable that, can also be the non-semantic message of other types, for example message of IDL form in actual applications equally.
Parameter c lientDomain that comprises in the wherein semantic initiateAuthentication request message and authType are the WSDL form by the body format conversion also, so far promptly finish the conversion of message format.
Above-mentioned concrete message format conversion can realize by extensible stylesheet table transfer language (XSLT, Extensible Stylesheet Language Transformations), is example with auth type authType still, and it is expressed as follows based on the WSDL form.
<xsd:simpleType name＝′TpAuthType′>
<xsd:restriction base＝′osaxsd:TpString′/>
</xsd:simpleType>
Below above-mentioned parameter is specifically described:
<xsd:simpleType name＝′TpAuthType′>
Wherein, what the simpleType explanation defined is the simple parameter type, and name represents that the title of this parameter is TpAuthType;
＜xsd:restriction base=' osaxsd:TpString '/〉 be used to illustrate that the specific implementation form of this parameter is character string (TPString)
Defined the TpAuthType parameter above.Above-mentioned parameter TpAuthType is corresponding to parameter authType, and wherein the former is the general data type, and the latter is a body types.The former is that the latter is through obtaining after the XSLT conversion.
204, this WSDL message is sent to the gateway side device and carries out authentication;
Semantic Message Processing engine is finished after the conversion of message format, the initiateAuthentication request message of the WSDL form that obtains after the conversion is sent in the gateway side Dispatching Unit ranks, this gateway side Dispatching Unit can be arranged in message processing apparatus, also can independently exist.
The gateway side Dispatching Unit receives after the initiateAuthentication request message of this WSDL form, the purpose side of judging this initiateAuthentication request message is the gateway side authentication device, then this request message is carried out waiting lines and sends.
After this request message is sent to the gateway side authentication device, authentication device carries out authentication according to the initiateAuthentication request message based on WSDL that receives, detailed process can be the initial authentication initial method InitialAuthentication () that inserts object IpInitial of: authentication device operation, obtain response message TpAuthDomain, comprise quoting of authentication module interface in this response message.
Above-mentioned " quoting of authentication module interface " is used to call the authentication module interface function, by calling this interface function and then can calling the communication network ability of bottom, concrete calling interface function, and do not limit according to the process that interface function calls the communication network ability of bottom herein.
205, be semantic authentication responses message with the authentication responses message conversion that receives;
Authentication device carries out authentication and obtains after the response message, this response message is sent to the formation of gateway side message sink, this gateway side message sink formation is used to receive the non-semantic message that gateway side device (for example gateway side authentication device) sends, and to the transmission of ranking of this non-semantic message, this gateway side message sink formation can be the memory of a stack architecture, or the memory of data link table structure, or the memory of other data store organisations, this gateway side message sink formation can be arranged in message processing apparatus, or independent the existence.
Gateway side pretreatment unit in the message processing apparatus receives from after the response message TpAuthDomain in the formation of gateway side message sink, at first in mapping table, search the message conversion process ID relevant with response message TpAuthDomain, be ID_initiateAuthenticationResponse, then response message TpAuthDomain and message conversion process ID:ID_initiateAuthenticationResponse thereof together be sent to semantic Message Processing engine.
After semantic Message Processing engine receives response message TpAuthDomain and implementation ID thereof, a running example is created in the processing that is similarly this message, and this running example calls corresponding implementation information initiateAuthenticationProcess according to implementation ID semantic initial authentication request is handled.
The message conversion subelement that semantic Message Processing engine can trigger in the process of implementation initiateAuthenticationProcess operation in the message processing apparatus carries out message conversion with request message conversion subelement to semantic response message, the message conversion subelement is to the map information initiateAuthenticationWsdlGrounding of the local storage of semantic Message Processing engine feedback, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message.
Semantic Message Processing engine is converted to semantic response message according to this map information with response message, and being about to response message TpAuthDomain is body types by the WSDL type conversion.
206, send this semanteme authentication responses message to the semantic network service function entity.
Semantic Message Processing engine obtains after the semantic response message, should the semanteme response message be sent in the application side Dispatching Unit, this application side Dispatching Unit determines that the purpose side of this semanteme response message is the semantic network service function entity, then, comprise quoting of authentication module interface in this semanteme response message to the transmission of ranking of this semanteme response message.
The process that authentication message (comprising initial authentication request message and response message) is transmitted between semantic network service function entity and gateway side authentication device has been described in the above-mentioned flow process, need to prove, in the authentication process of reality, after the semantic network service function entity receives semantic response message, still have subsequent step, be specially:
(1) the semantic network service function entity calls the method selectAuthenticationMechanism of gateway side authentication device by message processing apparatus, selects with the mutual authentication mechanism of authentication module;
(2) the semantic network service function entity carries out two-way authentication by message processing apparatus and gateway side authentication device;
Concrete mutual authentication process comprises:
The semantic network service function entity authenticates gateway side, if authentication success returns authenticationSucceeded;
Gateway side authenticates semantic semantic network service function entity, if authentication success returns authenticationSucceeded.
Generally speaking, by the semantic network service function entity gateway side is authenticated earlier, gateway side authenticates the semantic network gateway then.
(3) the semantic network service function entity obtains an IpAccess object reference by the requestAccess method that message processing apparatus calls authentication device;
Obtain the IpAccess object reference by calling " requestAccess " method during above-mentioned calling.Wherein, the object reference of IpAccess is a return value of calling the requestAccess function.Operating process is by calling the requestAccess function, obtained the return value of this function, and promptly the IpAccess object quotes.
(4) the semantic network service function entity calls the selectSigningAlgorithm method of IpAccess object with authentication module negotiation transaction signature algorithm by message processing apparatus.
The above-mentioned selectSigningAlgorithm method of calling the IpAccess object is consulted transaction signature algorithm with authentication module, is exactly in fact that the selectSigningAlgorithm function that calls the IpAccess object is consulted transaction signature algorithm with authentication module.The ability of selectSigningAlgorithm function is that the parlay gateway provides itself, when business is carried out, only need call this function, just can finish function corresponding.In the present embodiment, the semantic network service function entity can call this non-semantic function by message processing apparatus, thereby reaches the purpose of calling bottom communication network capability service.
By above-mentioned flow process as can be known, in the present embodiment, message processing apparatus can be changed semantic message and non-semantic message, when needs send to the gateway side device, message processing apparatus is non-semantic message with semantic message conversion, when needs sent to the semantic network service function entity, message processing apparatus was semantic message with non-semantic message conversion, thus the present embodiment scheme can so that the semantic network service function entity can and the gateway side device between carry out interacting message.
Foregoing description method for message transmission embodiment in the embodiment of the invention, below the communication system in the embodiment of the invention is described, see also Fig. 3, the communication system embodiment in the embodiment of the invention comprises:
Message processing apparatus 302, the communication that can be used for handling between semantic network service function entity 301 and the gateway side device 302 connects;
Wherein, message processing apparatus 302 is used to receive the first semantic message that semantic network service function entity 301 sends, and in the corresponding relation of the semantic message that presets and non-semantic message the first corresponding non-semantic message of the inquiry described first semantic message, send the described first non-semantic message to gateway side device 303;
Correspondingly, message processing apparatus 302 also is used to receive the second non-semantic message that gateway side device 303 sends, and in the corresponding relation of the semantic message that presets and non-semantic message the second corresponding semantic message of the inquiry described second non-semantic message, send the described second semantic message to semantic network service function entity 301;
Semantic network service function entity 301 is used for sending the first semantic message to message processing apparatus 302, and receives the second semantic message that message processing apparatus 302 sends;
Among the above-mentioned communication system embodiment, the service that is provided when semantic network service function entity 301 needs and gateway side device 303 carries out when mutual, then can send the first semantic message to gateway side device 303, this message can be authentication request message, or data communication request message, or other types are not done qualification herein to semantic message.
Message processing apparatus 301 receives the first semantic message that this semantic network service function entity 302 sends, concrete message processing apparatus 301 can be integrated in the gateway, perhaps independently be present in the network, but semantic network service function entity 302 can pass through this message processing apparatus 301 with gateway side device 303 interactive messages.
Message processing apparatus 301 gets access to after the first semantic message of semantic network service function entity 302 transmissions, can judge that according to the sign of this message this message is semantic message, and because gateway side device 303 is not supported semantic message, so message processing apparatus 301 is inquired about the first corresponding non-semantic message of this first semantic message according to this first semantic message in the corresponding relation between the semantic message that presets and the non-semantic message.
Message processing apparatus 301 sends this first non-semantic message so that gateway side device 303 can be carried out subsequent operation according to this first non-semantic message to gateway side device 303 after getting access to the first non-semantic message corresponding with the first semantic message.
In actual applications, interacting message is two-way often, so in the present embodiment, gateway side device 303 can send message to semantic network service function entity 302 too, particularly, gateway side device 303 sends the second non-semantic message to message processing apparatus 301, message processing apparatus 301 can judge that according to the sign of this message this message is non-semantic message, so message processing apparatus 301 is according to this second non-semantic message second corresponding semantic message of this second non-semantic message of inquiry in the corresponding relation between the semantic message that presets and the non-semantic message.
Need to prove that above-mentioned gateway side device 303 can be dissimilar gateway side devices in the difference of practical application, for example in authorizing procedure, this gateway side device 303 can be the gateway side authentication device, and is similar in other flow processs, repeats no more herein.
In the present embodiment, message processing apparatus can be changed semantic message and non-semantic message, when needs send to the gateway side device, message processing apparatus is non-semantic message with semantic message conversion, when needs send to the semantic network service function entity, message processing apparatus is semantic message with non-semantic message conversion, thus the present embodiment scheme can so that the semantic network service function entity can and the gateway side device between carry out interacting message.
See also Fig. 4, the message processing apparatus embodiment in the embodiment of the invention comprises:
Application side message sink formation 401 is used for the semantic message that receives is carried out buffer memory, and waiting lines handles;
Application side pretreatment unit 402 is used for searching and the corresponding implementation ID of semantic message in preset mapping table, and semantic message and corresponding implementation ID are sent to semantic Message Processing engine 403;
Semantic Message Processing engine 403, be used for carrying out corresponding processing procedure according to this semanteme message and this implementation ID, trigger message conversion subelement 404 with the acquisition request map information, map information according to message conversion subelement 404 feedbacks is non-semantic message with semantic message conversion, and the non-semantic message that will be converted to is sent to gateway side Dispatching Unit 405;
Message conversion subelement 404 is used for the map information to the local storage of semantic Message Processing engine 403 feedbacks, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message;
Gateway side Dispatching Unit 405 is used to receive the non-semantic message that semantic Message Processing engine 403 sends, and the non-semantic message that receives ranked is sent to the gateway side device.
Foregoing description be to send the process of semantic message to the gateway side device from the semantic network service function entity, can have inverse process accordingly in actual applications, then the message processing apparatus in the present embodiment can also comprise:
Gateway side message sink formation 406 is used for the non-semantic message that receives is carried out buffer memory, and waiting lines handles;
Gateway side pretreatment unit 407 is used for searching and the corresponding implementation ID of semantic message in preset mapping table, and non-semantic message and corresponding implementation ID are sent to semantic Message Processing engine 403;
Semantic Message Processing engine 403, also be used for carrying out corresponding processing procedure according to this non-semantic message and this implementation ID, trigger message conversion subelement 404 with the acquisition request map information, map information according to message conversion subelement 404 feedbacks is semantic message with non-semantic message conversion, and the semantic message that will be converted to is sent to application side Dispatching Unit 408;
Message conversion subelement 404 is used for the map information to the local storage of semantic Message Processing engine 403 feedbacks, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message;
Application side Dispatching Unit 408 is used to receive the semantic message that semantic Message Processing engine 403 sends, and the semantic message that receives ranked is sent to the semantic network service function entity.
Need to prove, above-mentioned application side message sink formation 401 and gateway side message sink formation 406 are selectable unit, be that these two unit are not limited to be integrated in the message processing apparatus, and can be used as independently unit equally, perhaps independently storage server is finished the function of these two unit, and specific implementation is not done qualification herein.
Need to prove that the message processing apparatus in the present embodiment can further include:
Implementation subelement 409, be used for storage and the corresponding implementation information of semantic message, semantic network service in the present embodiment can be based on body network service language (OWL-S, Ontology WebLanguage for Services) realizes, therefore, can adopt ServiceModel document form storage implementation information in the implementation subelement;
Basic service information subelement 410 is used to store semantic network service (the being also referred to as atomic service) information with minimum complete function collection, has wherein stored the ServiceProfile fileinfo of semantic network service.
Above-mentioned message conversion subelement 404, implementation subelement 409 and basic service information subelement 410 can be merged into same device, promptly semantic message elements 400, the processing that is mainly semantic message provides support;
In addition, the message processing apparatus in the present embodiment can also comprise ontology knowledge storehouse 411, is used to semantic Message Processing engine 403 and semantic message elements 400 that the support of Ontological concept is provided.Particularly, the ServiceProcess fileinfo and the ServiceGrouding fileinfo of semantic network service have been stored in the semantic message elements 400, and semantic Message Processing engine also needs to use body in handling semantic message process, these all need to use the Ontological concept in ontology knowledge storehouse.The OWL standard is followed in this ontology knowledge storehouse.
Above-mentioned ontology knowledge storehouse 411 is used to provide the body support, particularly, stores the basic terms and the relation that constitute association area vocabulary in the ontology knowledge storehouse 411.Because semantic Message Processing engine 403 and semantic message elements 400 all are to have semantic network element, so just need be described by body, are supported by the relevant information that ontology knowledge storehouse 411 provides, and make these network element can have semanteme.
For ease of understanding, be that example illustrates the transfer of data contact between above-mentioned each unit with concrete authentication process below:
Message processing apparatus can be with this request message buffer memory to application side message sink formation 401 after getting access to semantic initial authentication request message;
When semantic initial authentication request message is buffered to application side message sink formation 401, application side pretreatment unit 402 is searched in preset mapping table and the corresponding implementation identifier of semantic initial authentication request (ID), be ID_initiateAuthentication, semantic initial authentication request message and this implementation ID are sent to semantic Message Processing engine 403, create a running example by this semanteme Message Processing engine 403 according to this semanteme initial authentication request message and this implementation ID, this running example calls corresponding implementation information initiateAuthenticationProcess according to implementation ID semantic initial authentication request is handled.Wherein, with the parameter c lientDomain in the semantic initial authentication request and authType input as implementation initiateAuthenticationProcess.
Semantic Message Processing engine 403 can trigger message conversion subelement 404 and carry out message conversion with 404 pairs of semantic initial authentication request messages of request message conversion subelement in the process of implementation initiateAuthenticationProcess operation, message conversion subelement 404 is to the map information initiateAuthenticationWsdlGrounding of the local storage of semantic Message Processing engine feedback, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message.
Semantic Message Processing engine 403 is converted to initiateAuthentication request message based on WSDL according to this map information with semantic initiateAuthentication request message.Parameter c lientDomain that comprises in the wherein semantic initiateAuthentication request message and authType are the WSDL form by the body format conversion also, so far promptly finish the conversion of message format.
Semantic Message Processing engine 403 is finished after the conversion of message format, the initiateAuthentication request message of the WSDL form that obtains after the conversion is sent in the gateway side Dispatching Unit 405 ranks, this gateway side Dispatching Unit 405 can be arranged in message processing apparatus, also can independently exist.
Gateway side is distributed after the initiateAuthentication request message that Unit 405 receive this WSDL form, the purpose side of judging this initiateAuthentication request message is the gateway side authentication device, then this request message is carried out waiting lines and sends.
Authentication device carries out authentication and obtains after the response message, this response message is sent to gateway side message sink formation 406, gateway side pretreatment unit 407 receives from after the response message TpAuthDomain in the gateway side message sink formation 406 afterwards, at first in mapping table, search the message conversion process ID relevant with response message TpAuthDomain, be ID_initiateAuthenticationResponse, then response message TpAuthDomain and message conversion process ID:ID_initiateAuthenticationResponse thereof together be sent to semantic Message Processing engine 403.
After semantic Message Processing engine 403 receives response message TpAuthDomain and implementation ID thereof, a running example is created in the processing that is similarly this message, and this running example calls corresponding implementation information initiateAuthenticationProcess according to implementation ID semantic initial authentication request is handled.
Semantic Message Processing engine 403 can trigger message conversion subelement 404 and carry out message conversion with 404 pairs of semantic response messages of request message conversion subelement in the process of implementation initiateAuthenticationProcess operation, message conversion subelement 404 is to the map information initiateAuthenticationWsdlGrounding of the local storage of semantic Message Processing engine 403 feedbacks, and the content that is comprised in this map information promptly is the corresponding relation between semantic message and the non-semantic message.
Semantic Message Processing engine 403 is converted to semantic response message according to this map information with response message, and being about to response message TpAuthDomain is body types by the WSDL type conversion.
Semantic Message Processing engine 403 obtains after the semantic response message, should the semanteme response message be sent in the application side Dispatching Unit 408, this application side Dispatching Unit 408 determines that the purpose side of these semanteme response messages is semantic network service function entities, then to the transmission of ranking of this semanteme response message.
In the foregoing description, receive after the first semantic message of semantic network service function entity transmission, the first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message, and send the described first non-semantic message to the gateway side device.So can realize the conversion between semantic message and the non-semantic message in the embodiment of the invention, promptly handle non-semantic message by the gateway side device, and handle semantic message by the semantic network service function entity, realize alternately by message conversion between the two, so the embodiment of the invention makes the semantic network service function entity to carry out interacting message with gateway.
One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to finish by program, described program can be stored in a kind of computer-readable recording medium, this program comprises the steps: when carrying out
Receive the first semantic message that the semantic network service function entity sends;
The first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message;
Send the described first non-semantic message to the gateway side device.
The above-mentioned storage medium of mentioning can be a read-only memory, disk or CD etc.
More than a kind of semantic method for message transmission provided by the present invention and communication system and message processing apparatus are described in detail, for one of ordinary skill in the art, thought according to the embodiment of the invention, part in specific embodiments and applications all can change, in sum, this description should not be construed as limitation of the present invention.
Claims (15)
1, a kind of semantic method for message transmission is characterized in that, comprising:
Receive the first semantic message that the semantic network service function entity sends;
The first corresponding non-semantic message of the inquiry described first semantic message in the corresponding relation of the semantic message that presets and non-semantic message;
Send the described first non-semantic message to the gateway side device.
2, method according to claim 1 is characterized in that, described method also comprises:
Receive the second non-semantic message that the gateway side device sends;
The second corresponding semantic message of the inquiry described second non-semantic message in the corresponding relation of the semantic message that presets and non-semantic message;
Send the described second semantic message to the semantic network service function entity.
3, method according to claim 1 is characterized in that, described gateway side device is the gateway side authentication device;
The step of the first semantic message that described reception semantic network service function entity sends comprises:
Receive the semantic initial authentication request message that the semantic network service function entity sends;
Described in the corresponding relation of the semantic message that presets and non-semantic message the step of the corresponding first non-semantic message of the inquiry described first semantic message comprise:
Obtain the corresponding relation between semantic message and the non-semantic message;
Inquire about the non-semantic initial authentication request of described semantic initial authentication request message correspondence according to described corresponding relation;
Send described non-semantic initial authentication request message to described gateway side authentication device, be used to indicate described gateway side authentication device described semantic network service function entity to be carried out authentication according to described non-semantic initial authentication request message.
4, method according to claim 3 is characterized in that, comprises after the step of the semantic initial authentication request message that described reception semantic network service function entity sends:
Described semantic initial authentication request message is carried out buffer memory;
Inquire about the implementation identifier of described semantic initial authentication request message correspondence;
Calling corresponding implementation information according to described implementation identifier handles described semantic initial authentication request message.
5, according to claim 3 or 4 described methods, it is characterized in that, describedly after the gateway side authentication device sends the step of described non-semantic initial authentication request message, comprise:
Receive the non-semantic response message of gateway side authentication device feedback;
Inquire about the corresponding semantic response message of described non-semantic response message according to semantic message that gets access to and the corresponding relation between the non-semantic message;
Send described semantic response message to the semantic network service function entity, be used to indicate described semantic network service function entity to carry out subsequent operation according to described semantic response message.
6, method according to claim 5 is characterized in that, comprises after the step of the non-semantic response message of described reception gateway side authentication device feedback:
Described non-semantic response message is carried out buffer memory;
Inquire about the implementation identifier of described non-semantic response message correspondence;
Calling corresponding implementation information according to described implementation identifier handles described non-semantic response message.
7, method according to claim 5 is characterized in that, describedly comprises after the semantic network service function entity sends the step of described semantic response message:
The semantic network service function entity is selected authentication mechanism by message processing apparatus;
Carry out two-way authentication according to authentication mechanism and the gateway side authentication device selected;
After authentication is passed through, consult transaction signature algorithm with the gateway side authentication device.
8, a kind of communication system is characterized in that, comprising:
Message processing apparatus, the communication that can be used for handling between semantic network service function entity and the gateway side device connects;
Described message processing apparatus is used to receive the first semantic message that described semantic network service function entity sends, the first corresponding non-semantic message of the inquiry described first semantic message sends the described first non-semantic message to described gateway side device in the corresponding relation of the semantic message that presets and non-semantic message;
Described semantic network service function entity is used for sending the first semantic message to described message processing apparatus;
Described gateway side device is used to receive the first non-semantic message that described message processing apparatus sends.
9, communication system according to claim 8 is characterized in that,
Described message processing apparatus also is used to receive the second non-semantic message that described gateway side device sends, the second corresponding semantic message of the inquiry described second non-semantic message sends the described second semantic message to described semantic network service function entity in the corresponding relation of the semantic message that presets and non-semantic message;
Described semantic network service function entity also is used to receive the second semantic message that described message processing apparatus sends;
Described gateway side device also is used for sending the second non-semantic message to described message processing apparatus.
10, according to Claim 8 or 9 described communication systems, it is characterized in that described message processing apparatus can be integrated with described gateway side device.
11, a kind of message processing apparatus is characterized in that, comprising:
Semantic Message Processing engine, the message conversion subelement;
Described message conversion subelement provides corresponding relation between semantic message and the non-semantic message to described semantic Message Processing engine;
The corresponding relation that described semantic Message Processing engine is used for providing according to described message conversion subelement is non-semantic message with semantic message conversion, or is semantic message with non-semantic message conversion.
12, message processing apparatus according to claim 11 is characterized in that, described message processing apparatus also comprises:
The formation of application side message sink is used for the semantic message that receives is carried out buffer memory, and waiting lines handles;
The application side pretreatment unit is used for searching and the corresponding implementation identifier of semantic message in preset mapping table, and semantic message and corresponding implementation identifier are sent to semantic Message Processing engine;
The gateway side Dispatching Unit is used to receive the non-semantic message that described semantic Message Processing engine sends, and the non-semantic message that receives ranked is sent to the gateway side device.
13, according to claim 11 or 12 described message processing apparatus, it is characterized in that described message processing apparatus also comprises:
The formation of gateway side message sink is used for the non-semantic message that receives is carried out buffer memory, and waiting lines handles;
The gateway side pretreatment unit is used for searching and the corresponding implementation identifier of semantic message in preset mapping table, and non-semantic message and corresponding implementation identifier are sent to semantic Message Processing engine;
The application side Dispatching Unit is used to receive the semantic message that described semantic Message Processing engine sends, and the semantic message that receives ranked is sent to the semantic network service function entity.
14, message processing apparatus according to claim 13 is characterized in that, described message processing apparatus also comprises:
The implementation subelement, be used for storage and the corresponding implementation information of semantic message, the identifier that comprises implementation, semantic network service in the present embodiment can realize based on body network service language OWL-S, therefore, can adopt service model ServiceModel document form storage implementation information in the implementation subelement;
Basic service information subelement is used to store the semantic network information on services with minimum complete function collection, has wherein stored the service documents ServiceProfile fileinfo of semantic network service.
15, message processing apparatus according to claim 14 is characterized in that, described message conversion subelement, and implementation subelement and basic service information subelement can integratedly be realized.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100840808A CN101257495B (en) | 2008-03-26 | 2008-03-26 | Semantic message transmission method and communication system as well as message processing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100840808A CN101257495B (en) | 2008-03-26 | 2008-03-26 | Semantic message transmission method and communication system as well as message processing device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101257495A true CN101257495A (en) | 2008-09-03 |
| CN101257495B CN101257495B (en) | 2012-01-04 |
Family
ID=39891964
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100840808A Expired - Fee Related CN101257495B (en) | 2008-03-26 | 2008-03-26 | Semantic message transmission method and communication system as well as message processing device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101257495B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582894B (en) * | 2009-06-10 | 2011-12-14 | 重庆大学 | Semantic gateway used for integration of enterprise informatization heterogeneous system |
| CN103473243A (en) * | 2012-06-08 | 2013-12-25 | 富士通株式会社 | Method and device for generating semantic network service document |
| CN106062791A (en) * | 2014-01-30 | 2016-10-26 | 谷歌公司 | Associating a segment of an electronic message with one or more segment addressees |
-
2008
- 2008-03-26 CN CN2008100840808A patent/CN101257495B/en not_active Expired - Fee Related
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582894B (en) * | 2009-06-10 | 2011-12-14 | 重庆大学 | Semantic gateway used for integration of enterprise informatization heterogeneous system |
| CN103473243A (en) * | 2012-06-08 | 2013-12-25 | 富士通株式会社 | Method and device for generating semantic network service document |
| CN103473243B (en) * | 2012-06-08 | 2017-03-01 | 富士通株式会社 | The method and apparatus of generative semantics network service document |
| CN106062791A (en) * | 2014-01-30 | 2016-10-26 | 谷歌公司 | Associating a segment of an electronic message with one or more segment addressees |
| CN106062791B (en) * | 2014-01-30 | 2019-12-24 | 谷歌有限责任公司 | Associating segments of an electronic message with one or more segment addressees |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101257495B (en) | 2012-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101065947B (en) | Web service registry and method of operation | |
| US7752634B1 (en) | Non-intrusive personalization of web services | |
| US6993555B2 (en) | Method and system for interactively responding to instant messaging requests | |
| US8949311B2 (en) | Dynamic, non-intrusive personalization of web services | |
| US7529833B2 (en) | Method, system, and web service broker for dynamic web service invocation | |
| EP1851935B1 (en) | Dynamic extensible lightweight access to web services for pervasive devices | |
| US20030140119A1 (en) | Dynamic service discovery | |
| US7930702B2 (en) | Web services layer synchrony in relation to the business layer synchrony | |
| US8788618B2 (en) | Leveraging presence service system and method for distributed web service delivery and deployment | |
| US20050050228A1 (en) | Method and apparatus for the use of dynamic XML message formats with web services | |
| US20020133535A1 (en) | Identity-centric data access | |
| US20030036917A1 (en) | Service provision system and method | |
| JPH1196099A (en) | Service providing system | |
| EP2107712B1 (en) | Method, apparatus and system for composite service process, replacement and concrete service invocation | |
| EP2330847A1 (en) | Method, system and apparatus for service negotiation | |
| US7783718B2 (en) | Locating services using compiled scopes | |
| JP2004518219A (en) | Mechanism and method for session management in portal structure | |
| WO2002087133A2 (en) | Method and system for generalized and adaptive transaction processing between uniform information services and applications | |
| CN101202694A (en) | Method and system for supplying web service on pervasive device | |
| CN102257789A (en) | System and methods for improving interaction routing performance | |
| CN101257495B (en) | Semantic message transmission method and communication system as well as message processing device | |
| KR101080862B1 (en) | System and method for REST style Third Party Call API | |
| US20050060399A1 (en) | Method and system for managing programs for web service system | |
| CN105516271A (en) | Business processing system, business processing method and business processing apparatus | |
| CN101150576B (en) | Network server access system and its method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| ASS | Succession or assignment of patent right |
Owner name: HUAWEI TECHNOLOGY CO., LTD.; APPLICANT Free format text: FORMER OWNER: HUAWEI TECHNOLOGY CO., LTD. Effective date: 20081114 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20081114 Address after: Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Province, China: 518129 Applicant after: HUAWEI Technologies Ltd Co-applicant after: Beijing University of Posts and Telecommunications Address before: Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Province, China: 518129 Applicant before: Huawei Technologies Co., Ltd. |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120104 Termination date: 20160326 |