WO2009076872A1 - 业务路由方法、业务路由器、客户端设备及业务网络系统 - Google Patents

业务路由方法、业务路由器、客户端设备及业务网络系统 Download PDF

Info

Publication number
WO2009076872A1
WO2009076872A1 PCT/CN2008/073372 CN2008073372W WO2009076872A1 WO 2009076872 A1 WO2009076872 A1 WO 2009076872A1 CN 2008073372 W CN2008073372 W CN 2008073372W WO 2009076872 A1 WO2009076872 A1 WO 2009076872A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
information
request message
routing
requester
Prior art date
Application number
PCT/CN2008/073372
Other languages
English (en)
French (fr)
Inventor
Qifeng Ma
Jianfeng Liu
Junhong He
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009076872A1 publication Critical patent/WO2009076872A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching 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

Definitions

  • the present invention relates to the field of service network technologies, and more particularly to a service routing method, a service router, a client device, and a service network system. Background technique
  • the service network is to interconnect many services, share resources, cooperate with each other, and finally complete the user's needs.
  • the service network can include service routers, as well as registration servers, directory servers, and management centers.
  • the specific business can be commercially deployed infrastructure. Through the business network, telecom operators and IT (Information Technology) operators integrate services and content to form an end-to-end whole, providing valuable services to individual or enterprise end users, that is, the business network interconnects many services. Together, shared resources collaborate and ultimately meet the needs of users.
  • IT Information Technology
  • the service network based on the Session Initiation Protocol (SIP) is used as an example.
  • the User Agent Client (UAC) needs to query related information according to the user's needs. A business logical address that satisfies the user's needs, and sets the header of the service request message to the business logical address, and then sends the service request message.
  • the SIP proxy server (Proxy) can perform related checks, such as syntax check, loop detection, and the like. If the proxy server is an intermediate proxy server, no further processing is required to forward the request directly to the next hop.
  • the proxy server is the proxy server of the target universal resource identifier (Target URI)
  • the specific request target is determined for the service request, which may be a set or a set of SIP URIs, and the proxy server processes according to the priority order.
  • the proxy server replaces the request universal resource identifier Request-URI of the service request message with the target address, concurrently Sent to the corresponding user agent server (UAS, User Agent Server)neig
  • UAS User Agent Server
  • the user agent server determines whether the request message is legal, and after determining that the request message is legal, completes the relevant processing and returns a successful response. Establish a session.
  • the problem that the existing routing mode cannot be dynamically routed according to the specific requirements of the user is currently solved in the service network by redirecting the service request, for example, by setting a redirect server, and in some architectures, redirecting the server.
  • the service routing information is pushed to the client, so that it can separate itself from the subsequent message flow, but at the same time provide an accurate request location service.
  • the redirect server can pre-configure the relationship between the user request and its destination object (user, service).
  • the redirect server can return the destination address information required by the requester according to the pre-configuration information. , so that the requester can establish a session with the object they need.
  • the redirection mechanism is adopted, the user needs to request the destination object address information from the redirect server first, and then establish a session with the destination object according to the object address information returned by the redirect server, resulting in a complicated process of using the service and being inflexible.
  • Using a business network is more complicated.
  • the search discovery mechanism between the service and the service also adopts a redirection mechanism, in addition to the above-mentioned user redirection process, the collaborative service is Redirection is also required, which makes the process of interaction between services more complicated, and the complexity of users using the service network is greater. Summary of the invention
  • the technical problem to be solved by the embodiments of the present invention is to provide a service routing method, a service router, a client device, and a service network system, so that a service requester can initiate a related service according to its own needs without specifying a service destination address. Requests, streamline business interaction processes, increase the flexibility of business interactions, and reduce the complexity of users using business networks.
  • a service routing method including:
  • a service router including:
  • a receiving unit configured to receive a service request message, where the service request message includes service information of a service required by the service requester;
  • An analysis processing unit configured to parse the service request message, and obtain service information carried in the service request message
  • a service routing processing unit configured to perform service routing according to the obtained service information, and determine service routing information corresponding to the obtained service information
  • a message forwarding processing unit configured to select, according to the service routing processing unit, the determined service routing information, and forward the service request message.
  • a client device including:
  • a service request message encapsulating unit configured to encapsulate a service request message including service information of a service required by a service requester
  • a service request message sending unit configured to send, by the service request message encapsulating unit, a service request message including service information of a service required by the service requester to the service network.
  • a service network system comprising: a client device that initiates a service request, and a service router that processes a service route forwarding;
  • the client device includes:
  • a service request message encapsulating unit configured to encapsulate a service request message including service information of a service required by a service requester
  • a service request message sending unit configured to send, by the service request message encapsulating unit, a service request message including service information of a service required by the service requester to the service network;
  • the service router includes:
  • a receiving unit configured to receive a service request message that includes service information of a service required by the service requester
  • An analysis processing unit configured to parse the service request message, and obtain service information carried in the service request message
  • a service routing processing unit configured to perform service routing according to the obtained service information, and determine service routing information corresponding to the obtained service information
  • a message forwarding processing unit configured to select, according to the service routing processing unit, the determined service routing information, and forward the service request message.
  • the service request message sent by the user carries the service information of the service required by the service requester; the service router parses the service request message to obtain the service information of the service required by the service requester; The service requester needs the business information of the service to perform the service routing process; finally, the service forwarding message is routed according to the selected service routing information, and the related service request is initiated according to the service requirement of the service without specifying the service destination address.
  • the service router performs service routing processing according to the service information of the service required by the service requester. Therefore, the service interaction process can be streamlined, the flexibility of service interaction is improved, and the complexity of the user using the service network is reduced.
  • FIG. 1 is a schematic diagram of a prior art service network structure
  • FIG. 2 is a schematic diagram of an existing SIP-based service routing processing process
  • FIG. 3 is a schematic flowchart of a service routing method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a logical entity networking of a SIP protocol applied to an embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a SIP-based service routing method according to an embodiment of the present invention.
  • FIG. 6 is a schematic flow chart of a service routing method for extending an IR parameter based on a SIP protocol according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a service network system according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another embodiment of a service router according to the present invention.
  • FIG. 9 is a schematic structural diagram of a service routing processing unit according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of another structure of a service routing processing unit according to an embodiment of the present invention;
  • FIG. 11 is a schematic diagram of networking of a SIP-based service network system according to an embodiment of the present invention.
  • this figure is a flowchart of a service routing method according to an embodiment of the present invention.
  • the service requester does not initiate the relevant service request in the case of specifying the destination address of the triggered service, but initiates the related service request according to the service requirement of the service, that is, the service request message sent by the service requester may carry the service.
  • the service information of the service required by the requester for example, the service information of the service required by the service requester may be a service function, a service name, and/or a service attribute information, or a service information of a service required by another service requester.
  • the device responsible for processing the service route can perform service routing according to the following process:
  • a service request message that includes service information of a service required by a service requester.
  • the service request message may be a message of a different protocol, for example, a SIP service request message or a service request message of another protocol type used in the service network, such as a service request message of a Simple Object Access Protocol (SOAP).
  • SOAP Simple Object Access Protocol
  • the service request message may be determined according to the received service request message, and the service is performed when the judgment result is yes.
  • the request message parsing process that is, 102, can normally forward the received service request message when the judgment result is no.
  • the service request message is a SIP service request message
  • the SIP service request message is parsed, and the service information of the service required by the service requester carried in the SIP service request message is obtained.
  • the key can be based on the obtained business information.
  • the word matching determines the corresponding service routing information, for example, pre-storing the service information and the corresponding service routing information, and matching the stored service information keywords with the pre-stored service information keywords when performing service routing. Then, the corresponding service routing information is determined according to the matched service information; or the corresponding service routing information may be determined according to the obtained service information, for example, the semantic analysis is implemented by integrating a related inference engine that supports the semantics independently. The semantic analysis is mainly based on the ontology information, so that the computer can understand the meaning of the words.
  • the corresponding service routing information can be determined according to the result of the semantic analysis.
  • the service information of the service required by the service requester is ""YidianCoffee"
  • the computer through the semantic analysis of the query semantic analysis library, it can be judged that the service requester is actually looking for a restaurant, and may further analyze the Western restaurant, so that the user can determine the corresponding service route according to the semantic analysis result. information.
  • the service request message is forwarded according to the service routing information determined to be selected. For example, the service request message may be directly forwarded to the next hop according to the determined service routing information; or, the service routing information in the service request message may be updated first, and then the updated service request message is forwarded and routed; or And filling the determined service routing information into the corresponding message domain of the service request message, and then performing routing and forwarding on the filled service request message.
  • the next hop is continued, and the subsequent service router determines the processing of the service routing information.
  • the routing control policy may also be controlled, for example, the routing function is denied for some illegal requests.
  • the service requester initiates a related service request according to the service requirement of the service
  • the device responsible for processing the service route in the service network performs service routing according to the service information required by the service requester, determines service routing information, and then selects according to the service.
  • the determined service routing information is forwarded by the user. From the perspective of the user, the user only needs to initiate a service request according to the service requirement of the user, and does not need to know the destination device address of the required service, thereby reducing the complexity of the user using the service network. From the service point of view, the device responsible for processing the service route directly performs service routing according to the service information required by the service requester, which encapsulates the business interaction process and improves the flexibility of business interaction.
  • the following is an example of a SIP service network.
  • SIP is built on top of SMTP (Single Mail Transfer Protocol) and HTTP (Hypertext Transfer Protocol). It is an application layer protocol that can establish, modify or abort multimedia sessions or calls.
  • FIG. 4 the figure is a schematic diagram of a logical entity networking of the SIP protocol applied in the embodiment of the present invention.
  • a User Agent is a logical entity that initiates or receives a session; the UA is further divided into a UAC and a UAS; the UAC is used to generate a service request, and the UAS is used to respond to a service request.
  • the proxy server routes the SIP service request to the UAS, and routes the SIP reply to the UAC.
  • a service request may reach the UAS through multiple proxyes. Each of them will make a routing decision, and the service request can be modified a little before being sent to the next node, and the response will be sent back to the UAC through the proxy path in reverse order with the service request, that is, when a UAC sends a service request, these service requests may be Passed to the UAS through some proxy servers.
  • the UAS generates a response, the response is sent to the UAC in the same way.
  • FIG. 5 it is a schematic flowchart of a SIP-based service routing method according to an embodiment of the present invention.
  • the UAC may be a user's mobile phone, a PDA, or a PC;
  • the routers SR-A and SR-B are proxy servers that support the SIP service routing function;
  • the UAS is a server that provides the user with a service that is ultimately required to be used, and specific routing processing. The process is as follows:
  • the UAC initiates a SIP Invite (SIP Request, Session Initiation Protocol Request) according to the service requirement of the user, that is, sends a SIP Invite request message to the SR-A, where the SIP Invite request message carries the service information of the service required by the service requester.
  • the SIP Invite request message is a SIP service request message.
  • the SR-A performs service routing query selection processing, determines service routing information, and specifies a specific destination address and subsequent routing information, according to the service information content of the service required by the service requester carried in the SIP Invite request message.
  • the SR-A forwards the SIP Invite message to the SR-B of the next hop according to the service routing information obtained by the 202.
  • the SR-B processes according to the normal SIP message, that is, forwards the SIP Invite service request message to the destination UAS.
  • the UAS responds according to the normal request.
  • the UAC updates or populates the contents of the header field To.
  • the subsequent signaling processing is the same as the normal SIP processing.
  • the SIP service request message in order to carry the service information of the service required by the service requester in the SIP service request message, may be extended, for example, by adding a new in the Request-URI header field in the SIP service request message.
  • the business information of the business required by the business requester; or The service information of the service required by the service requester is carried by the newly extended SIP header field; or the service information of the service required by the service requester is carried by the existing SIP header field.
  • the service information of the service required by the service requester is carried by the newly added parameter of the Request-URI header field in the SIP service request message.
  • the uri-parameter parameter is defined in the SIP protocol, and the uri-parameter value has Transport-param/user-param/method-param/ttl-param/ maddr-param/lr-param/other-param.
  • the uri-parameter parameter definition may be extended, and a parameter ir-param ( ir ) is added to carry the service information of the service required by the service requester.
  • the definition of the specific ir-param ( ir ) is shown in Table 1:
  • the functional characteristics required by the SIP requester described in the above Function may include a service type, a service name, etc., such as a Query restaurant Menu, a Search Engine, a POC Service, a Location Service, a Presence Service, etc.; and an Attribute is an additional information describing a function of the Function, ⁇ Function 4 is described as 'Query Restaurant Menu' and attribute further is attached to port 4 as 'nearby' or 'cheap price', or Function is described as 'Search Engine', attribute is further described as 'English' or 'Chinese' Wait.
  • a service type such as a Query restaurant Menu, a Search Engine, a POC Service, a Location Service, a Presence Service, etc.
  • an Attribute is an additional information describing a function of the Function, ⁇ Function 4 is described as 'Query Restaurant Menu' and attribute further is attached to port 4 as 'nearby' or 'cheap price', or Function is described as
  • the SIP Invite request message of 201 can take the following form: :
  • the ir parameter carries information about the service required by the service requester, that is, 'Search Engine: Chinese', which represents a search service that needs to support Chinese search.
  • the display-name may be used to indicate the extension in the foregoing solution.
  • the ir-param ( ir ) parameter information a special tag value is added to indicate that this is a To header field that supports SIP routing, such as "SIP-service-routing".
  • SIP-service-routing An example of the main parameters of the SIP Invite request message sent by the UAC of 201 in the above embodiment may be in the following form:
  • INVITE sip Proxyl.com; SIP/2.0
  • CSeq 1 INVITE
  • the To header field carries the information of the service required by the service requester, that is, 'Search: Chinese
  • the value of the tag is SIP-service-routing, indicating that this is a To header field supporting SIP routing, so that The service router determines the service routing information according to the information of the service required by the service requester carried in the To header field.
  • the SIP header field can be added to carry the service information of the service required by the service requester, for example, the newly added SIP header field is Service-info, and the value can also be in the above scheme.
  • INVITE sip Proxyl.com; SIP/2.0
  • FIG. 6 the figure is a schematic flowchart of a service routing method for extending an IR parameter based on a SIP protocol according to an embodiment of the present invention.
  • the proxy receives the SIP Invite request message.
  • Proxy extracts the ir parameter content, that is, the aforementioned Function: attribute.
  • the proxy sends the hop parameter according to the routing mechanism of the proxy itself, and keep the ir parameter. For example, if the proxy detects the ir parameter, but the proxy cannot determine the target object for the original SIP request according to the related information, the proxy does not delete the ir parameter. According to its own routing mechanism, the Invite message is routed to the next Proxy for processing.
  • the subsequent Proxy processing flow is similar to this embodiment. For example, when the To header field is reused, it is first determined whether the Tag value of the To header field is a special value of the service route. If yes, the Proxy extracts the function and attribute information in the To header field to perform a search and match, which is the current SIP. The service request determines a most suitable service routing information, and updates or fills the service routing information in the original SIP service request according to the matching result, and finally routes the service request to the destination end.
  • the processing flow of the subsequent Proxy is similar to this embodiment. For example, when a Service-info header field is added, it first detects whether there is a new header field Service-info. If so, the Proxy extracts the function and attribute information in the Service-info header field, and performs search and matching. The current SIP service request determines a most suitable service routing information, and updates or fills the service routing information in the original SIP service request according to the matching result, and finally routes the request to the destination end.
  • FIG. 7 is a schematic structural diagram of a service network system according to an embodiment of the present invention.
  • the service network system in this embodiment includes: a client device 1 and a service router 2, wherein the client device 1 , in this embodiment, the client device 1 not only refers to a user agent, but also a service requester and a service provider, according to different
  • the protocol used by the service network the client device 1 may be a client device of a corresponding protocol, for example, a SIP protocol client device.
  • the client device in this embodiment may include:
  • the service request message encapsulating unit 11 is configured to encapsulate a service request message including the service information of the service required by the service requester.
  • the service request message encapsulating unit 11 may Encapsulating the service information of the service required by the service requester in the SIP service request message in various manners, for example, carrying the service information of the service required by the service requester by using a newly added parameter of the Request-URI header field; or by newly expanding the SIP header field Carrying the service information of the service required by the service requester; or by reusing the existing SIP header field to carry the service information of the service required by the service requester, etc., here is no longer an example;
  • the service request message sending unit 12 is configured to send the service request message encapsulated by the service request message encapsulating unit 11 and include the service information of the service required by the service requester to the service network.
  • the service router 2 in this embodiment, is not only responsible for basic message processing, but also includes service routing information processing functions, for example, querying related information and matching, and finally determining service routing information for the user's service request and performing routing and forwarding.
  • the service router 2 may include:
  • the receiving unit 21 is configured to receive a service request message that includes service information of a service required by the service requester.
  • the receiving unit 21 performs receiving processing according to the corresponding protocol. For example, if the service network adopts the SIP protocol, the receiving process may be performed according to the SIP protocol; and the parsing processing unit 22 is configured to parse the The service request message acquires the service information carried in the service request message.
  • the service request message is a SIP service request message, and the SIP service request message may be parsed to obtain the service information of the service required by the service requester carried by the corresponding parameter (for example, the ir parameter) in the SIP service request message;
  • the service routing processing unit 23 is configured to perform service routing processing according to the obtained service information of the service required by the service requester, and determine service routing information corresponding to the acquired service information.
  • the service routing processing unit 23 may be based on the acquired service.
  • the service information of the service required by the requester is matched by the keyword to determine the corresponding service routing information.
  • the service routing information may be determined according to other methods, for example, according to the obtained service information of the service requester. Referring to FIG. 9, as a specific embodiment, the service routing processing unit 23 may include:
  • a storage unit 231, configured to store a correspondence between service information and service routing information
  • the routing unit 232 is configured to query the correspondence between the service information and the service routing information saved by the storage unit 231 according to the obtained service information, and determine corresponding service routing information.
  • the service routing processing unit 23 may include: a semantic parsing processing unit 233, configured to perform semantic analysis to determine a corresponding service route according to the acquired service information of the service required by the service requester. information.
  • Service Router 2 also includes:
  • the message forwarding processing unit 24 is configured to select the determined service routing information according to the routing processing unit 232, and forward the service request message by routing.
  • the service router responsible for processing the service route in the service network performs service routing processing according to the service information required by the service requester. And routing and forwarding according to the selected service routing information, which reduces the complexity of the user using the service network from the perspective of the user; from the service point of view, the business interaction process can be centralized, and the flexibility of the business interaction is improved.
  • the next hop may be continued and processed by the subsequent service router.
  • this figure is a schematic structural diagram of another embodiment of the service router of the present invention. Similar to the above embodiment, the service router of this embodiment includes:
  • the receiving unit 21 the parsing processing unit 22, the service routing processing unit 23, and the message forwarding processing unit 24,
  • the service router in this embodiment further includes:
  • the routing control policy processing unit 25 is configured to provide a routing control policy to the routing processing unit 23.
  • the policy may be to provide a routing function for some illegal requests, and the like.
  • the service routing processing unit 23 is further configured to control the service request message according to the routing control policy provided by the routing control policy processing unit 25.
  • the service network router according to the embodiment can reduce the complexity of the user using the service network not only from the perspective of the user; from the service point of view, the service interaction process can be streamlined, and the flexibility of the service interaction is improved, and the route is improved.
  • the processing of the control policy processing unit 25 can further improve the flexibility of the service routing process to meet various practical needs.
  • the foregoing service network system can be implemented based on various protocols without loss of generality.
  • the following is an example of a service network based on the SIP protocol.
  • FIG. 11 is a schematic diagram of networking of a SIP-based service network system according to an application of an embodiment of the present invention.
  • the UAs are connected to each other through a Proxy, where the UA refers not only to the user agent, but also to the service requester and the service provider.
  • the UA can perform basic SIP message processing as well as service routing related information processing, such as encapsulation processing of service information required by the service demander carried in the SIP; similarly, the Proxy can perform basic SIP message processing, such as SIP.
  • the receiving process of the message and the routing and forwarding of the SIP message and the update, etc., in addition, the proxy can also perform the processing of the SIP service routing function, for example, determining the service routing information and some routing control policies according to the service information of the service required by the service requester, etc. Take a specific application process as an example:
  • UA1 is an application on the mobile user User terminal;
  • UA2 is a service that provides a Query restaurant Menu in Shenzhen.
  • relevant information has been posted to the network, which is the Proxy in the above figure.
  • the Proxy can determine routing information based on the specific destination address.
  • CSeq 1 INVITE where the ir parameter carries the service information of the service of the service requester, ie 'Query restaurant Menu: nearby'.
  • SRI analyzes the ir parameter, and generates a query request according to the parameter content 'Query restaurant menu: nearby', and then sends the query request to the determining processing unit, determining that the processing unit is based on the relevant
  • the configuration policy initially analyzes the request, such as whether the request needs to be rejected (eg, a policy violation), and if it is a normal request, the determining processing unit further determines a specific destination address by, for example, related information of the service information storage module.
  • the obtained destination address is service@UAS.com
  • the main parameters of the SIP request are updated according to the obtained destination address as follows:
  • INVITE sip service@UAS.com; SIP/2.0
  • SR2 is processed according to the normal SIP request message, that is, the request is forwarded to the destination UA2; the subsequent processing is the same as the general SIP message processing, which will not be described in detail here.
  • the service request message sent by the user end carries the service information of the service required by the service requester;
  • the service request message is used to obtain the service information of the service required by the service requester; and then the service routing process is performed according to the service information of the service required by the obtained service requester; and finally, the service request message is forwarded according to the service routing information selected and selected. Since the service destination address is not required to be specified, the service request is initiated according to the service requirement of the service, and then the service router performs the service routing process according to the service information of the service required by the service requester. Therefore, the service interaction process can be optimized and the service interaction can be improved. Flexibility and reduce the complexity of users using business networks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Description

业务路由方法、 业务路由器、 客户端设备及业务网络系统 本申请要求于 2007 年 12 月 15 日提交中国专利局、 申请号 为 200710032646.8、 发明名称为 "业务路由方法、 业务路由器、 客户端设备及 业务网络系统" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请 中。 技术领域
本发明涉及业务网络技术领域， 更具体的说， 本发明涉及一种业务路由方 法、 业务路由器、 客户端设备及业务网络系统。 背景技术
参考图 1 , 业务网络就是把许多业务互联起来， 共享资源、 互相协作并最终 完成用户的需求， 业务网络中可包括业务路由器以及注册服务器、 目录服务器 以及管理中心等设备， 是一种提供了使具体业务可以商业化部署的基础架构。 通过业务网络， 电讯业者和信息技术（IT, Information Technology )经营者一起， 整合服务和内容， 形成端到端的整体， 为个人或企业的最终用户提供有价值的 服务， 即业务网络把许多业务互联起来， 共享资源互相协作并最终满足用户的 需求。
现有的业务网络中， 在业务目的地址已知的情况下可以较好的满足用户的 需求。 如图 2所示， 以基于会话初始协议（SIP, Session Initiation Protocol )路 由机制的业务网络为例， 用户代理客户端 （UAC, User Agent Client )首先需要 根据用户的需求， 查询相关的信息， 获取能满足用户需求的业务逻辑地址， 并 将业务请求消息的头部设置为该业务逻辑地址， 然后将该业务请求消息发送出 去。 SIP代理服务器（Proxy )接收到用户代理客户端的业务请求消息后可进行 相关的检查， 如语法检查， 环路检测等。 如果该代理服务器是中间代理服务器， 就不需要做进一步的处理， 直接转发请求到下一跳。 而如果代理服务器是目标 通用资源标志符（ Target URI )的代理服务器， 则就要为该业务请求确定具体的 请求目标， 可能是一个也可能是一组 SIP URI, 该代理服务器按照优先级先后处 理，把业务请求消息的请求通用资源标志符 Request-URI替换成目标地址， 并发 送到对应的用户代理服务端（UAS , User Agent Server )„ 用户代理服务端接收到 请求消息后， 判断请求消息是否合法， 并在判断请求消息合法后， 完成相关的 处理， 并回送成功响应， 建立会话。
而随着业务网络的发展， 业务的种类和形式会越来越丰富， 业务网络也越 来越复杂， 在这种情况下， 采用图 2所示的业务路由方式， 用户查找能满足自 己需要的服务会变得很困难。 并且， 在图 2所示的业务路由方式中， 业务网络 中用户往往只关心自己的具体需求， 具体的业务路由选择由网络代替用户进行， 这样， 由于目前的业务路由机制只支持明确的目的地址路由， 无法根据用户的 具体需求进行动态的路由选择。
针对现有的路由方式无法根据用户的具体需求进行动态路由的问题， 目前 在业务网络中主要通过对业务请求重定向解决， 例如通过设置采用重定向服务 器， 在某些架构下， 重定向允许服务器在一个请求的应答中， 推送业务路由信 息到客户端， 这样就可以做到把自己从后续的消息流中脱离出来， 但是同时又 能提供准确的请求定位服务。 重定向服务器可以预先把用户请求和其目的对象 (用户、 服务） 的关系配置好， 在用户发起重定向请求时， 重定向服务器可以 根据预先的配置信息， 返回请求者所需要的目的对象地址信息， 从而请求者可 与其需要的对象建立会话。
由于采用了重定向机制， 用户需要先向重定向服务器请求目的对象地址信 息， 然后再根据重定向服务器返回的对象地址信息与目的对象建立会话， 导致 业务使用的流程比较复杂， 且不够灵活， 用户使用业务网络比较复杂。 而且， 考虑到未来不同业务之间通过协作完成用户需求的情况会比较普遍， 若业务与 业务之间的搜索发现机制也采用重定向机制， 则除了上述用户的重定向流程外， 协作的业务之间还需要重定向， 这样会使致业务之间交互的流程比较复杂， 用 户使用业务网络的复杂度更大。 发明内容
本发明实施例解决的技术问题是提供一种业务路由方法、 业务路由器、 客 户端设备及业务网络系统， 以使业务请求者可以在不需要指定业务目的地址的 情况下根据自身的需求发起相关业务请求， 筒化业务交互流程， 提高业务交互 的灵活性， 并降低用户使用业务网络的复杂性。 一种业务路由方法， 包括：
接收业务请求消息， 所述业务请求消息包括业务请求者所需业务的业务信 息；
获取所述业务请求消息中携带的业务信息；
根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对 应的业务路由信息；
根据所述业务路由信息路由转发所述业务请求消息。
一种业务路由器， 包括：
接收单元， 用于接收接收业务请求消息， 所述业务请求消息包括业务请求 者所需业务的业务信息；
解析处理单元， 用于解析所述业务请求消息， 获取所述业务请求消息中携 带的业务信息；
业务路由选择处理单元， 用于根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对应的业务路由信息；
消息转发处理单元， 用于根据所述业务路由选择处理单元选择确定的所述 业务路由信息， 路由转发所述业务请求消息。
一种客户端设备， 包括：
业务请求消息封装单元， 用于封装包括有业务请求者所需业务的业务信息 的业务请求消息；
业务请求消息发送单元， 用于将所述业务请求消息封装单元封装的包括有 业务请求者所需业务的业务信息的业务请求消息发送到业务网络。
一种业务网络系统， 包括： 发起业务请求的客户端设备， 处理业务路由转 发的业务路由器；
其中所述客户端设备包括：
业务请求消息封装单元， 用于封装包括有业务请求者所需业务的业务信息 的业务请求消息；
业务请求消息发送单元， 用于将所述业务请求消息封装单元封装的包括有 业务请求者所需业务的业务信息的业务请求消息发送到业务网络；
所述业务路由器包括：
接收单元， 用于接收包括业务请求者所需业务的业务信息的业务请求消息； 解析处理单元， 用于解析所述业务请求消息， 获取所述业务请求消息中携 带的业务信息；
业务路由选择处理单元， 用于根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对应的业务路由信息；
消息转发处理单元， 用于按照所述业务路由选择处理单元选择确定的所述 业务路由信息， 路由转发所述业务请求消息。
在本发明实施例中， 用户发送的业务请求消息中携带业务请求者所需业务 的业务信息； 业务路由器解析所述业务请求消息以获取业务请求者所需业务的 业务信息； 然后根据所述获取的业务请求者所需业务的业务信息进行业务路由 选择处理； 最后按照选择确定的业务路由信息路由转发业务请求消息， 由于不 需要指定业务目的地址的情况下根据自身的业务需求发起相关业务请求， 业务 路由器根据业务请求者所需业务的业务信息进行业务路由选择处理， 因此， 可 筒化业务交互流程， 提高业务交互的灵活性， 并降低用户使用业务网络的复杂 性。 附图说明 例或现有技术描述中所需要使用的附图作筒单地介绍， 显而易见地， 下面描述 中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付 出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1是现有的一种业务网络结构示意图；
图 2是现有的基于 SIP的业务路由处理过程的示意图；
图 3是本发明实施例的业务路由方法的流程示意图；
图 4是本发明实施例的应用的 SIP协议的逻辑实体组网示意图；
图 5是本发明实施例的基于 SIP的业务路由方法的流程示意图；
图 6是本发明实施例的基于 SIP协议扩展 IR参数的业务路由方法的流程示 意图；
图 7是本发明实施例的业务网络系统的结构示意图；
图 8是本发明的业务路由器的另一种实施例的结构示意图；
图 9是本发明实施例的业务路由选择处理单元的一种结构示意图； 图 10是本发明实施例的业务路由选择处理单元的另一种结构示意图； 图 11是本发明实施例的应用的一种基于 SIP的业务网络系统的组网示意图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行清 楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是 全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例， 都属于本发明要求保护的范围。
参考图 3, 该图是本发明实施例的业务路由方法的流程图。
本实施例中业务请求者不是在指定被触发业务的目的地址的情况下发起相 关业务请求， 而是根据自身的业务需求发起相关业务请求， 即业务请求者发送 的业务请求消息中可携带有业务请求者所需业务的业务信息， 例如所述业务请 求者所需业务的业务信息可能是业务功能、 业务名称和 /或业务属性信息等， 或 者其他业务请求者所需业务的业务信息， 这里不再详述， 业务网络中负责处理 业务路由的设备， 可按照下述过程进行业务路由：
101 , 接收包括业务请求者所需业务的业务信息的业务请求消息。 具体实现 时， 例如， 接收包括业务功能、 业务名称和业务属性信息等业务请求者所需业 务的业务信息中的一个或几个的组合的业务请求消息， 根据不同的业务网络， 所述业务请求消息可能是不同协议的消息， 例如， SIP业务请求消息或者业务网 络中采用的其他协议类型的业务请求消息， 例如筒单对象访问协议（SOAP, Simple Object Access Protocol ) 的业务请求消息等。
另外， 需要说明的， 具体接收包括业务请求者所需业务的业务信息的业务 请求消息时， 还可根据接收到的业务请求消息判断是否需要进行业务路由选择 处理， 在判断结果为是时进行业务请求消息解析处理， 即 102, 在判断结果为否 时则可正常转发接收到的业务请求消息。
102, 获取所述业务请求消息中携带的业务信息。 具体实现时， 例如， 若所 述业务请求消息为 SIP业务请求消息，则对所述 SIP业务请求消息进行解析，获 取所述 SIP业务请求消息中携带的业务请求者所需业务的业务信息。
103, 根据所述获取的业务信息进行业务路由选择处理， 确定所述获取的业 务信息对应的业务路由信息。 具体实现时， 可以根据获取的业务信息进行关键 字匹配确定相应的业务路由信息， 例如， 预先保存业务信息及其对应的业务路 由信息， 在进行业务路由选择时， 可根据获取的业务信息的关键字与预先存储 的业务信息关键字进行匹配， 进而根据匹配的业务信息确定相应的业务路由信 息； 或者也可以根据获取的业务信息作语义解析， 确定相应的业务路由信息， 例如， 通过集成独立支持语义的相关推理引擎来实现语义解析。 其中， 语义解 析主要是根据本体信息， 使得计算机能够理解词语的含义， 本实施例中可根据 语义解析的结果确定相应的业务路由信息， 举例说， 如业务请求者所需业务的 业务信息是 "茗典咖啡"， 计算机通过查询语义解析库进行语义解析， 可以判断 该业务请求者实际上是想找一个餐馆， 还可能进一步分析是西餐馆， 从而根据 语义解析结果可为用户确定相应的业务路由信息。
104, 按照选择确定的所述业务路由信息路由转发所述业务请求消息。 具体 实现时， 例如， 可直接按照确定的业务路由信息将业务请求消息转发给下一跳； 或者， 先更新业务请求消息中的业务路由信息， 再对更新后的业务请求消息进 行路由转发； 或者， 将选择确定的业务路由信息填充到业务请求消息的对应消 息域中， 再对填充后的业务请求消息进行路由转发。
另外， 若上述流程中当前无法确定业务路由信息， 则继续下一跳， 由后续 的业务路由器进行确定业务路由信息的处理。
需要说明的， 本实施例中在进行业务路由选择处理时还可以根据路由控制 策略进行控制， 例如， 对某些非法的请求拒绝提供路由功能等。
从上述本实施例可知， 业务请求者根据自身的业务需求发起相关业务请求， 业务网络中负责处理业务路由的设备根据业务请求者需求的业务信息进行业务 路由选择， 确定业务路由信息， 进而按照选择确定的业务路由信息进行路由转 发， 从用户的角度来说， 用户只需要根据自身的业务需求发起业务请求， 不需 要知道提供所需业务的目的设备地址， 从而降低了用户使用业务网络的复杂性； 从业务的角度来说， 负责处理业务路由的设备直接根据业务请求者需求的业务 信息进行业务路由选择， 筒化了业务交互流程， 并且提高了业务交互的灵活性。
下面以 SIP协议的业务网络为例进行说明。
SIP是在诸如 SMTP (筒单邮件传送协议）和 HTTP (超文本传送协议）基 础之上建立起来的， 是一个应用层的协议， 可以建立、 修改或者中止多媒体会 话或者呼叫。 参考图 4, 该图是本发明实施例的应用的 SIP协议的逻辑实体组网示意图。 如图 4所示， 用户代理（UA, User Agent )是发起或接收会话的逻辑实体； UA又分为 UAC和 UAS; UAC是用来产生业务请求的， UAS是用来响应业务 请求的。
代理服务器路由 SIP业务请求到 UAS, 并且路由 SIP应答到 UAC。 一个业 务请求可能通过多个 proxy到达 UAS。 每一个都会作出路由决定， 在发送给下 一个节点前可对业务请求做一点修改， 而应答会通过和业务请求逆序的 proxy 路径回送给 UAC, 即当一个 UAC发送一个业务请求， 这些业务请求可能通过 一些代理服务器传递到 UAS上。 当 UAS产生一个应答， 那么这个应答就会同 样的被传送到 UAC。
参考图 5,该图是本发明实施例的基于 SIP协议的业务路由方法的流程示意 图。
本实施例中 UAC可以是用户手机、 PDA或 PC; 路由器 SR-A、 SR-B为支 持 SIP业务路由功能的代理服务器； UAS是服务器， 为用户提供其最终需要使 用的一个服务， 具体路由处理流程如下：
201 , UAC根据用户的业务需求发起 SIP Invite ( SIP请求， 会话初始协议请 求）， 即向 SR-A发送 SIP Invite请求消息， 其中所述 SIP Invite请求消息中携带 业务请求者所需业务的业务信息， 所述 SIP Invite请求消息即为 SIP业务请求消 息。
202, SR-A根据 SIP Invite请求消息中携带的业务请求者所需业务的业务信 息内容， 进行业务路由查询选择处理， 确定业务路由信息， 指定具体的目的地 址和后续的路由信息等。
203, SR-A根据 202获取的业务路由信息， 转发 SIP Invite消息给下一跳的 SR-B。
204, SR-B按照正常的 SIP消息处理， 即把 SIP Invite的业务请求消息转发 给目的地 UAS。 UAS按照正常的请求进行响应， UAC收到响应后更新或填充头 域 To的内容， 后续的信令处理同一般的 SIP处理。
具体实现时， 本实施例中为了在 SIP 业务请求消息中携带业务请求者所需 业务的业务信息， 可扩展 SIP业务请求消息， 例如， 通过在 SIP业务请求消息中 的 Request - URI头域增加新的参数， 携带业务请求者所需业务的业务信息； 或 者通过新扩展 SIP 头域携带业务请求者所需业务的业务信息； 或者通过重用已 有的 SIP头域携带业务请求者所需业务的业务信息。
以通过 SIP业务请求消息中的 Request - URI头域的新增加参数携带业务请 求者所需业务的业务信息为例，通常， SIP协议中已经定义了 uri-parameter参数， uri-parameter ] 取值 有 transport-param/user-param/method-param/ttl-param/ maddr-param/lr-param/other-param。 本实施例中为了在 SIP业务请求消息中携带 业务请求者所需业务的业务信息， 可扩展 uri-parameter参数定义， 新增一个参 数 ir-param ( ir )携带业务请求者所需业务的业务信息， 并作为确定业务路由信 息的指示， 具体所述 ir-param ( ir ) 的定义参考表一所示：
Figure imgf000010_0001
Figure imgf000010_0002
上述 Function描述的 SIP请求者需要的功能特性可以包括业务类型， 业务 名称等, 例如 Query restaurant Menu, Search Engine、 POC Service、 Location Service, Presence Service等； 而 Attribute是对 Function功能描述的附加信息， 列^口 Function 4 述为 'Query Restaurant Menu' 而 attribute进一步附力口 4 述为 'nearby' 或 'cheap price' , 或 Function描述为 'Search Engine' , attribute进一 步附加描述为 'English' 或 'Chinese' 等。 举例说， 假设用户希望使用搜索服 务， 并且代理服务器要支持中文检索， 通过新增参数 ir-param ( ir )携带业务请 求者所需业务的业务信息， 则 201的 SIP Invite请求消息可采用如下形式：
INVITE sip: Proxy-A.com; ir = Search Engine: Chinese SIP/2.0
Via: SIP/2.0/UDP 10.70.108. l;branch=z9hG4bK99a
From: bob <sip:bob@Proxy-A.com>;tag=n88ah
Call-ID: lj9FpLxk3uxtma7@host.example.com
CSeq: 1 INVITE 其中， ir 参数携带业务请求者需要的业务的信息， 即 'Search Engine: Chinese' , 代表需要支持中文检索的搜索服务。
另外， 若通过重用已有的 SIP 头域来实现携带业务请求者所需业务的业务 信息， 则可采用下述方式， 例如， 在 To头域中可以用 display-name来表示上述 扩展方案中的 ir-param ( ir )参数信息， 新增一个特殊的 Tag值表示这是一个支 持 SIP路由的 To头域， 例如 "SIP-service-routing"。 这样上述的实施例中的 201 的 UAC发出去的 SIP Invite请求消息主要参数的一个例子可采用如下形式：
INVITE sip: Proxyl.com; SIP/2.0
Via: SIP/2.0/UDP 10.70.108. l;branch=z9hG4bK99a
To: Search Engine: Chinese <sip : service @ example .com>； tag= SIP-service-routing
From: User <sip:user ©Proxy l.com>;tag=n88ah
CSeq: 1 INVITE 其中， To头域中携带业务请求者需要的业务的信息， 即 'Search:Chinese，， 并以 tag值为 SIP-service-routing表示这是一个支持 SIP路由的 To头域， 以便业 务路由器根据 To 头域中携带的业务请求者需要的业务的信息确定业务路由信 息。
另外， 与前面所述的扩展方法类似， 还可通过新增 SIP 头域来携带业务请 求者所需业务的业务信息， 例如新增的 SIP头域为 Service-info, 其值也可以上 述方案中描述的功能和属性字段的形式。这样上述的实施例中的 UAC发出去的 SIP Invite请求消息主要参数如下所示：
INVITE sip: Proxyl.com; SIP/2.0
Via: SIP/2.0/UDP 10.70.108. l;branch=z9hG4bK99a
To: <sip： service @ example . com>；
From: User <sip:user ©Proxy l.com>;tag=n88ah
Service-info: Search Engine: Chinese
CSeq: 1 INVITE 其中， 新增的 SIP头域 Service-info, 携带业务请求者需要的业务的信息, 参考图 6, 该图是本发明实施例的基于 SIP协议扩展 IR参数的业务路由方 法的流程示意图。
301 , Proxy接收到 SIP Invite请求消息。
302, 判断 Request-URI是否包含 ir参数； 当判断结果为否时， 即不包含 ir 参数， 则执行 303; 如果检测到 ir参数， 则执行 304。
303 , 则按照正常的 SIP请求处理流程进行处理。
304, Proxy提取 ir参数内容即前述的 Function: attribute。
305 , 根据该内容查询符合要求的目标对象， 判断是否可以确定目的地址； 若是， 执行 307; 若否， 则执行 306。
306,按 proxy自身的路由机制发送到下一个跳，保留 ir参数；例如如果 Proxy 检测到 ir参数， 但是该 Proxy无法根据相关的信息为原始 SIP请求确定目标对 象， 那么该 Proxy不删除 ir参数， 按照它自身的路由机制， 把该 Invite消息路由 到下一个 Proxy进行处理。
307, 根据目标地址， 构建新的路由信息， 并把此新的路由信息更新或填充 到 SIP Invite请求消息中， 同时删除 ir参数， 然后把修改后的 SIP invite请求消 息按照正常的处理方式发送出去。
需要说明的， 若通过重用已有的 SIP 头域来实现携带业务请求者所需业务 的业务信息，后续的 Proxy处理流程与本实施例类似。 例如， 当重用 To头域时， 首先判断 To头域的 Tag值是否是业务路由的特殊值， 如果是， Proxy就提取 To 头域中的功能和属性信息， 进行查找和匹配， 为当前的 SIP 业务请求确定一个 最合适的业务路由信息， 并根据匹配结果更新或填充原 SIP 业务请求中的业务 路由信息， 最终把业务请求路由到目的端。
同样的， 若通过新增 SIP 头域来携带业务请求者所需业务的业务信息， 后 续 Proxy的处理流程与本实施例类似。 例如， 当新增 Service-info头域时， 首先 检测有没有新增的头域 Service-info, 如果有， Proxy就提取 Service-info头域中 的功能和属性信息， 并进行查找和匹配， 为当前的 SIP业务请求确定一个最合 适的业务路由信息， 并根据匹配结果更新或填充原 SIP业务请求中的业务路由 信息， 最终把请求路由到目的端。
为了实现本发明实施例所提供的上述方法， 需要对现有的网络系统及设备 的功能作相应的扩展。
参考图 7, 该图是本发明实施例的业务网络系统的结构示意图。
本实施例中业务网络系统包括： 客户端设备 1和业务路由器 2, 其中 客户端设备 1 , 本实施例中客户端设备 1不仅指用户代理， 也可以是服务请 求者和服务提供者， 根据不同业务网络采用的协议， 客户端设备 1 可以是相应 协议的客户端设备， 例如 SIP协议客户端设备， 本实施例中所述客户端设备可 包括：
业务请求消息封装单元 11 , 用于封装包括有业务请求者所需业务的业务信 息的业务请求消息， 具体实现时， 例如， 参考前述说明， 若业务网络采用 SIP 协议， 业务请求消息封装单元 11可通过各种方式在 SIP业务请求消息中封装业 务请求者所需业务的业务信息， 例如通过 Request - URI头域的新增加参数携带 业务请求者所需业务的业务信息； 或者通过新扩展 SIP 头域携带业务请求者所 需业务的业务信息； 或者通过重用已有的 SIP 头域携带业务请求者所需业务的 业务信息等， 这里不再一一例举；
业务请求消息发送单元 12,用于将所述业务请求消息封装单元 11封装的包 括有业务请求者所需业务的业务信息的业务请求消息发送到业务网络。
业务路由器 2, 本实施例中业务路由器 2不仅负责基本的消息处理，还包括 业务路由信息处理功能， 例如， 查询相关信息并进行匹配， 最终为用户的业务 请求确定业务路由信息并进行路由转发， 具体实现时， 例如， 业务路由器 2可 包括：
接收单元 21 , 用于接收包括业务请求者所需业务的业务信息的业务请求消 息。 具体实现时， 根据业务网络采用的不同协议， 接收单元 21按照相应的协议 进行接收处理，例如，业务网络采用 SIP协议，则可按照 SIP协议进行接收处理； 解析处理单元 22, 用于解析所述业务请求消息， 获取所述业务请求消息中 携带的业务信息。 具体实现时， 例如， 业务请求消息为 SIP 业务请求消息， 则 可解析该 SIP业务请求消息获取该该 SIP业务请求消息中相应参数 (例如 ir参 数）携带的业务请求者所需业务的业务信息；
业务路由选择处理单元 23 , 用于根据所述获取的业务请求者所需业务的业 务信息进行业务路由选择处理， 确定所述获取的业务信息对应的业务路由信息。 具体实现时， 例如参考前述说明， 业务路由选择处理单元 23可根据获取的业务 请求者所需业务的业务信息进行关键字匹配确定相应的业务路由信息； 或者也 可根据其他方式， 例如根据获取的业务请求者所需业务的业务信息作语义解析 确定相应的业务路由信息， 具体参考图 9, 作为一个具体的实施例， 业务路由选 择处理单元 23可包括：
存储单元 231 , 用于保存业务信息与业务路由信息的对应关系； 和
路由选择单元 232, 用于根据所述获取的业务信息， 查询所述存储单元 231 保存的业务信息与业务路由信息的对应关系， 确定相应的业务路由信息。
作为另一个具体的实施例， 参考图 10, 业务路由选择处理单元 23可包括： 语义解析处理单元 233 , 用于根据获取的业务请求者所需业务的业务信息， 作语义解析确定相应的业务路由信息。
业务路由器 2还包括：
消息转发处理单元 24, 用于按照所述路由选择处理单元 232选择确定的业 务路由信息， 路由转发所述业务请求消息。
根据本实施例的业务网络系统， 业务请求者根据自身的业务需求通过客户 端设备发起相关业务请求后， 业务网络中负责处理业务路由的业务路由器根据 业务请求者需求的业务信息进行业务路由选择处理， 进而按照选择确定的业务 路由信息进行路由转发， 从用户的角度来说可降低用户使用业务网络的复杂性； 从业务的角度来说可筒化业务交互流程， 并且提高业务交互的灵活性。
需要说明的，若上述业务路由选择处理单元 23当前无法确定业务路由信息， 则可继续下一跳， 由后续的业务路由器进行处理。
另外，参考图 8,该图是本发明的业务路由器的另一种实施例的结构示意图。 与上述实施例相同的， 本实施例的业务路由器包括有：
接收单元 21、 解析处理单元 22、 业务路由选择处理单元 23以及消息转发 处理单元 24,
另外， 本实施例与上述实施例不同的在于， 本实施例的业务路由器还包括 有：
路由控制策略处理单元 25 ,用于向路由选择处理单元 23提供路由控制策略， 例如， 如前所述， 所述策略可以是对某些非法的请求拒绝提供路由功能等。
此时， 业务路由选择处理单元 23 , 还用于根据所述路由控制策略处理单元 25提供的路由控制策略， 对所述业务请求消息进行控制。 根据本实施例的业务网络路由器， 不仅从用户的角度来说可降低用户使用 业务网络的复杂性； 从业务的角度来说可筒化业务交互流程， 并且提高业务交 互的灵活性， 而且通过路由控制策略处理单元 25的处理， 可进一步提高业务路 由处理的灵活性， 以满足各种实际需求。
上述的业务网络系统可基于各种协议实现， 不失一般性， 下面以基于 SIP 协议的业务网络为例进行说明。
参考图 11 , 该图是本发明实施例的应用的一种基于 SIP的业务网络系统的 组网示意图。
如图所示， 本实施例中 UA之间通过 Proxy相互联系， 这里的 UA不仅指用 户代理，也可以是服务请求者和服务提供者。而 UA既能进行基本 SIP消息处理， 也能进行业务路由相关信息处理， 例如 SIP 中携带的业务需求者所需业务的业 务信息的封装处理； 同样的， Proxy能进行基本 SIP消息处理， 例如 SIP消息的 接收处理以及 SIP消息的路由转发以及更新等， 另外， Proxy也能进行 SIP业务 路由功能的处理， 例如根据业务请求者所需业务的业务信息确定业务路由信息 以及一些路由控制策略等， 下面以一个具体的应用过程为例进行说明：
本应用过程是假设上述 UA1是一个移动用户 User终端上的应用； UA2是 在深圳一个提供 Query restaurant Menu的服务。并且相关的信息都已经发布到网 络上了， 即上图中的 Proxy上。 另外 Proxy可以根据具体的目的地址确定路由信 息。
当用户 User漫游到某地后想查询一下附近一些餐馆的菜单，通过 UA1发送 一个 SIP请求给网络。 主要参数如下所示：
INVITE sip: Proxyl.com; ir = Query restaurant Menu: nearby SIP/2.0
Via: SIP/2.0/UDP 10.70.108. l;branch=z9hG4bK99a
From: User <sip:user ©Proxy l.com>;tag=n88ah
CSeq: 1 INVITE 其中 ir 参数携带业务请求者所的业务的业务信息， 即 'Query restaurant Menu: nearby'。
SRI分析 ir参数, 并才艮据该参数内容 'Query restaurant menu: nearby' 生成 查询请求， 然后将该查询请求发送到确定处理单元， 确定处理单元根据相关的 配置策略初步分析该请求， 如是否需要拒绝该请求（例如违反政策等待）， 如果 是正常请求， 确定处理单元进一步通过例如业务信息存储模块的相关信息确定 具体的目的地址。
根据所述新的目的地址更新或填充原有 SIP请求消息， 并生成相关的路由 信息，再转发出去。具体到这个实施例子，得到的目的地址为 service@UAS.com, 根据得到的目的地址， 更新所述 SIP请求主要参数如下：
INVITE sip: service@UAS.com; SIP/2.0
Via: SIP/2.0/UDP Proxy 1.com;branch=z9hG4bKafarl
Via: SIP/2.0/UDP 10.70.108. l;branch=z9hG4bK99a
From: User <sip:user ©Proxy l.com>;tag=n88ah
To: < service@UAS.com >
Route： Proxy 2.com
Call-ID: lj9FpLxk3uxtma7@host.example.com
CSeq: 1 INVITE
SR2按照正常的 SIP请求消息处理， 即把请求转发给目的端 UA2; 后续处 理同一般的 SIP消息处理， 这里不再详细介绍。
综上， 根据上述本发明实施例提供的业务路由方法、 业务路由器、 客户端 设备及业务网络系统， 用户端发送的业务请求消息中携带业务请求者所需业务 的业务信息； 业务路由器解析所述业务请求消息以获取业务请求者所需业务的 业务信息； 然后根据所述获取的业务请求者所需业务的业务信息进行业务路由 选择处理； 最后按照选择确定的业务路由信息路由转发业务请求消息。 由于不 需指定业务目的地址， 只要根据自身的业务需求发起相关业务请求， 然后业务 路由器根据业务请求者所需业务的业务信息进行业务路由选择处理， 因此， 可 筒化业务交互流程， 提高业务交互的灵活性， 并降低用户使用业务网络的复杂 性。
以上所述仅为本发明的较佳实施例而已， 并非用于限定本发明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同替换、 改进等， 均应包 含在本发明的保护范围之内。

Claims

权 利 要 求
1、 一种业务路由方法， 其特征在于， 包括：
接收业务请求消息， 所述业务请求消息包括业务请求者所需业务的业务信 息；
获取所述业务请求消息中携带的业务信息；
根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对 应的业务路由信息；
根据所述业务路由信息路由转发所述业务请求消息。
2、 根据权利要求 1所述的业务路由方法， 其特征在于， 在所述接收业务请 求消息之后， 包括：
根据接收到的所述业务请求消息判断是否需要进行业务路由选择处理， 并 在判断结果为是时， 获取所述业务请求消息中携带的业务信息。
3、 根据权利要求 1所述的业务路由方法， 其特征在于， 根据所述获取的业 务信息进行业务路由选择时还包括：
根据路由控制策略对所述业务请求消息进行控制。
4、 根据权利要求 1所述的业务路由方法， 其特征在于， 所述根据所述获取 的业务信息进行业务路由选择， 确定所述业务信息对应的业务路由信息为： 根据所述获取的业务信息， 查询保存的业务信息与业务路由信息的对应关 系， 确定相应的业务路由信息； 或者
根据所述获取的业务信息作语义解析， 确定相应的业务路由信息。
5、 根据权利要求 1所述的业务路由方法， 其特征在于， 所述业务请求消息 为会话初始协议业务请求消息。
6、 根据权利要求 5所述的业务路由方法， 其特征在于， 所述会话初始协议 业务请求消息中通过下述方式携带业务请求者所需业务的业务信息： 通过请求通用资源定位符头域的新增加参数携带业务请求者所需业务的业 务信息； 或者
通过新扩展会话初始协议头域携带业务请求者所需业务的业务信息； 或者 通过重用已有的会话初始协议头域携带业务请求者所需业务的业务信息。
7、 根据权利要求 1-6任一项所述的业务路由方法， 其特征在于， 所述业务 请求者所需业务的业务信息包括：
业务功能、 业务名称和业务属性信息中的至少一种。
8、 一种业务路由器， 其特征在于， 包括：
接收单元， 用于接收业务请求消息， 所述业务请求消息包括业务请求者所 需业务的业务信息；
解析处理单元， 用于解析所述业务请求消息， 获取所述业务请求消息中携 带的业务信息；
业务路由选择处理单元， 用于根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对应的业务路由信息；
消息转发处理单元， 用于根据所述业务路由选择处理单元选择确定的所述 业务路由信息， 路由转发所述业务请求消息。
9、 根据权利要求 8所述的业务路由器， 其特征在于， 还包括：
路由控制策略处理单元， 用于向所述业务路由选择处理单元提供路由控制 策略；
所述业务路由选择处理单元， 还用于根据所述路由控制策略处理单元提供 的路由控制策略， 对所述业务请求消息进行控制。
10、 根据权利要求 8所述的业务路由器， 其特征在于， 所述业务路由选择 处理单元包括：
存储单元， 用于保存业务信息与业务路由信息的对应关系；
路由选择单元， 用于根据所述获取的业务信息， 查询所述存储单元保存的 业务信息与业务路由信息的对应关系， 确定相应的业务路由信息。
11、 根据权利要求 8 所述的业务路由器， 其特征在于， 所述业务路由选择 处理单元包括：
语义解析处理单元， 用于根据获取的业务信息作语义解析， 确定相应的业 务路由信息。
12、 一种客户端设备， 其特征在于， 包括：
业务请求消息封装单元， 用于封装包括有业务请求者所需业务的业务信息 的业务请求消息；
业务请求消息发送单元， 用于将所述业务请求消息封装单元封装的包括有 业务请求者所需业务的业务信息的业务请求消息发送到业务网络。
13、 根据权利要求 12所述的客户端设备， 其特征在于， 所述客户端设备为 会话初始协议用户代理客户端设备， 所述业务请求消息为会话初始协议业务请 求消息；
其中所述业务请求消息封装单元通过下述方式在会话初始协议业务请求消 息中封装业务请求者所需业务的业务信息：
通过请求通用资源定位符头域的新增加参数携带业务请求者所需业务的业 务信息； 或者
通过新扩展会话初始协议头域携带业务请求者所需业务的业务信息； 或者 通过重用已有的会话初始协议头域携带业务请求者所需业务的业务信息； 其中， 所述业务请求消息封装单元封装的业务请求者所需业务的业务信息 包括： 业务功能、 业务名称和 /或业务属性信息。
14、 一种业务网络系统， 包括： 发起业务请求的客户端设备， 处理业务路 由转发的业务路由器；
其特征在于， 所述客户端设备包括：
业务请求消息封装单元， 用于封装包括有业务请求者所需业务的业务信息 的业务请求消息；
业务请求消息发送单元， 用于将所述业务请求消息封装单元封装的包括有 业务请求者所需业务的业务信息的业务请求消息发送到业务网络； 所述业务路由器包括：
接收单元， 用于接收包括业务请求者所需业务的业务信息的业务请求消息； 解析处理单元， 用于解析所述业务请求消息， 获取所述业务请求消息中携 带的业务信息；
业务路由选择处理单元， 用于根据所述获取的业务信息进行业务路由选择， 确定所述获取的业务信息对应的业务路由信息；
消息转发处理单元， 用于按照所述业务路由选择处理单元选择确定的所述 业务路由信息， 路由转发所述业务请求消息。
15、 根据权利要求 14所述的业务网络系统， 其特征在于， 所述客户端设备 为会话初始协议用户代理客户端设备， 所述业务路由器为会话初始协议业务路 由器， 所述业务请求消息为会话初始协议业务请求消息。
PCT/CN2008/073372 2007-12-15 2008-12-08 业务路由方法、业务路由器、客户端设备及业务网络系统 WO2009076872A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200710032646.8A CN101459650A (zh) 2007-12-15 2007-12-15 业务路由方法、业务路由器、客户端设备及业务网络系统
CN200710032646.8 2007-12-15

Publications (1)

Publication Number Publication Date
WO2009076872A1 true WO2009076872A1 (zh) 2009-06-25

Family

ID=40770284

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/073372 WO2009076872A1 (zh) 2007-12-15 2008-12-08 业务路由方法、业务路由器、客户端设备及业务网络系统

Country Status (2)

Country Link
CN (1) CN101459650A (zh)
WO (1) WO2009076872A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605145B (zh) * 2009-07-10 2013-01-23 上海汽车集团股份有限公司 一种车载信息服务系统
US8543471B2 (en) * 2010-08-24 2013-09-24 Cisco Technology, Inc. System and method for securely accessing a wirelessly advertised service
CN103200102B (zh) * 2012-01-09 2018-02-13 中兴通讯股份有限公司 一种业务路由方法、装置和系统
CN102685105B (zh) * 2012-03-23 2015-06-10 中兴通讯股份有限公司 一种会话发起协议头部的查找方法及装置
CN106464684B (zh) * 2015-03-06 2020-06-02 北京花旺在线商贸有限公司 业务处理方法及装置
CN105847054A (zh) * 2016-03-25 2016-08-10 国网福建省电力有限公司 一种业务信息动态获取的方法
CN115632980A (zh) * 2022-10-24 2023-01-20 平安银行股份有限公司 路由配置实现方法、装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050120121A1 (en) * 2001-03-30 2005-06-02 Microsoft Corporation Service routing and web integration in a distributed, multi-site user authentication system
CN1859271A (zh) * 2006-03-29 2006-11-08 华为技术有限公司 一种无线业务应用的ip域网络及其路由方法
CN101026583A (zh) * 2002-11-06 2007-08-29 株式会社Ntt都科摩 通信控制系统,通信控制方法,可适用于该系统和方法的路由控制器和路由器
CN101044725A (zh) * 2004-10-06 2007-09-26 诺基亚公司 业务路由选择

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050120121A1 (en) * 2001-03-30 2005-06-02 Microsoft Corporation Service routing and web integration in a distributed, multi-site user authentication system
CN101026583A (zh) * 2002-11-06 2007-08-29 株式会社Ntt都科摩 通信控制系统,通信控制方法,可适用于该系统和方法的路由控制器和路由器
CN101044725A (zh) * 2004-10-06 2007-09-26 诺基亚公司 业务路由选择
CN1859271A (zh) * 2006-03-29 2006-11-08 华为技术有限公司 一种无线业务应用的ip域网络及其路由方法

Also Published As

Publication number Publication date
CN101459650A (zh) 2009-06-17

Similar Documents

Publication Publication Date Title
US11991255B2 (en) Interworking service for the restful internet of things
EP3259898B1 (en) Message bus service directory
US7243162B2 (en) Processing network communication control messages
US11871333B2 (en) Wireless network service type
US20040003058A1 (en) Integration of service registration and discovery in networks
US20070237139A1 (en) Node
WO2009076872A1 (zh) 业务路由方法、业务路由器、客户端设备及业务网络系统
WO2009033376A1 (fr) Procédé et système de sélection de chemin
JP2004518219A (ja) ポータル構造におけるセッション管理に関する機構及び方法
US20140181188A1 (en) Cpm service provisioning system and method for interworking with non-cpm service
Bushmitch et al. A SIP-based device communication service for OSGi framework
CN102742241B (zh) Ims网络之间的安全xdm通信
CN101584182A (zh) 发现基于电话的Web服务器的方法及相关电子设备和计算机程序产品
KR101107948B1 (ko) 통신 시스템에서의 서비스 제공
US10447739B2 (en) Network entities comprising interworking functions, methods of controlling same, and computer programs
US20240357016A1 (en) Interworking service for the restful internet of things
Jacob et al. Automatic routing of semantic sip messages in ims
WO2008077324A1 (fr) Procédé et système de fourniture de fonction de service
Ahmad Distributing a SIP servlet engine for standalone mobile ad hoc networks
Mokhtar et al. Service Discovery in Pervasive Computing Environments
KR20040049708A (ko) 인터넷 전화 서비스 제공 시스템 및 방법
KR20050020754A (ko) 디지털 아이템 어댑테이션(ｄｉａ)에 대한 니고시에이션메커니즘

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08861627

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08861627

Country of ref document: EP

Kind code of ref document: A1