WO2007056960A1 - Reseau de commutation de dispositif de service et dispositif de service de commutation - Google Patents

Reseau de commutation de dispositif de service et dispositif de service de commutation Download PDF

Info

Publication number
WO2007056960A1
WO2007056960A1 PCT/CN2006/003115 CN2006003115W WO2007056960A1 WO 2007056960 A1 WO2007056960 A1 WO 2007056960A1 CN 2006003115 W CN2006003115 W CN 2006003115W WO 2007056960 A1 WO2007056960 A1 WO 2007056960A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
interaction request
server
router
interaction
Prior art date
Application number
PCT/CN2006/003115
Other languages
English (en)
French (fr)
Inventor
Haiping Che
Yan Li
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.
Priority to EP06817853A priority Critical patent/EP1953973B1/en
Priority to ES06817853T priority patent/ES2401346T3/es
Publication of WO2007056960A1 publication Critical patent/WO2007056960A1/zh
Priority to US12/122,416 priority patent/US20080215752A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4541—Directories for service discovery
    • 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 switching technologies between service devices, and in particular, to a service device switching network, a switching method, and a service device.
  • a fixed communication network represented by a Public Switched Telephone Network (PSTN) and a Global System for Mobile Communication (GSM) are used.
  • PSTN Public Switched Telephone Network
  • GSM Global System for Mobile Communication
  • the representative mobile communication network can provide users with complete voice communication services.
  • the basic call service of telephone call, roaming, etc. is solved in PSTN and GSM.
  • the fixed intelligent network and the mobile intelligent network solve the call requirements for special routing and addressing of the call service.
  • Current users are no longer satisfied with a single voice call, but need to get more advanced and more complex services such as MMS, Internet, and video.
  • multiple service servers may need to work together on the network side, that is, multiple service servers may need to call each other to provide services.
  • the service referred to in the present invention refers to a service function provided by the service server, and may be a service directly facing the user, such as a short message, or a service function provided for other services in the network, such as Online or offline billing.
  • a service server can provide one or more services.
  • a service can be provided by a single service server, or can be jointly provided by multiple servers in a distributed manner.
  • the system of the Internet Multimedia Subsystem gives a typical business system. IMS is a target network for 3G (3 1 Generation, 3D Mobile) mobile networks to implement packet voice and packet data, and to provide unified multimedia services and applications.
  • IMS Internet Protocol
  • SIP Session Initation Protocol
  • FIG. 1 The structure of the IMS is as shown in FIG. 1.
  • the device involved includes a Call Session Control Function (CSCF) 110, an Application Server (AS Server) 120, and a home subscriber server. (Home Subscriber Server, "HSS") 130, Open Service Access (“OSA”) service capability server 140, OSA application server 150, Internet Protocol Multimedia Service Switching Function (IP Multimedia Service Switching Function) , referred to as "IM-SSF" 160 and the Media Resource Function Controller (“MRf C”) 170.
  • CSCF Call Session Control Function
  • AS Server Application Server
  • HSS Home Subscriber Server
  • OSA Open Service Access
  • IMSSF Internet Protocol Multimedia Service Switching Function
  • MRf C Media Resource Function Controller
  • the service system is based on the CSCF service trigger mode, and multimedia services can be used to complete more service functions.
  • a service server for example, an AS
  • the address of the other service server as the service provider needs to be set in advance in the service server as the service demander.
  • a port providing service A by sending a request message to the address and port to obtain a service service as a service server of the service provider. This practice of transmitting messages to the actual address of the service server as a service provider to obtain its services is also commonly used in PSTN fixed intelligent networks and GSM mobile intelligent networks.
  • a service device switching network includes: at least two service servers, configured to provide processing capability of at least one service; a service information center, configured to store routing information of each service processed by each of the service servers; at least one service router, configured to perform service based on the service information from the service server according to the routing information in the service information center
  • the business interaction request and its response are routed and forwarded.
  • a service device switching method is applied to the network described above; the method includes: the service server sending a service interaction request to a service router, where the service interaction request carries the requested Information of the service; the service router finds the corresponding routing information from the service information center according to the information of the service requested in the service interaction request from the service server; and provides the service monthly service according to the routing information.
  • the device forwards the service interaction request, and forwards the received response to the service interaction request to the service server that initiated the service interaction request.
  • a service router includes: a searching unit, configured to search for routing information of a requested service after receiving a service interaction request from a service server; and a forwarding unit configured to perform, based on the routing information The service-based service interaction request from the service server and its response are routed and forwarded.
  • a service server includes:
  • a service invoking unit configured to initiate a service interaction request routed and forwarded by the foregoing service router or a service interaction request response for the service interaction request; the service interaction unit is configured to perform, after the service invocation unit completes the service call through the service router, The interaction of business entities.
  • the embodiment of the invention can implement the exchange inside the service layer. Because the service information center stores the routing information of various services processed by various service servers, when the service is invoked, the routing information is searched from the service information center through the service router, and the routing and forwarding of the message is performed according to the routing information, so that it is convenient. User settings. Especially after the change of the business server that provides the business, The user who wants to invoke the corresponding service does not need to make any setting changes, as long as the operator modifies the routing information of the service in the service information center, thereby reducing the maintenance cost of the user.
  • FIG. 1 is a schematic diagram of a network structure of an IMS in the prior art
  • FIG. 2 is a schematic structural diagram of a service device switching network according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of message interaction during service routing according to an embodiment of the present invention
  • FIG. 4 is a structural block diagram of a service router according to an embodiment of the present invention
  • FIG. 5 is a structural block diagram of a service server according to an embodiment of the present invention.
  • FIG. A service equipment switching network according to an embodiment of the present invention is shown in FIG. It should be noted that this embodiment only describes the networking and signaling in the IP network. Those skilled in the art can understand that the present invention is for a fixed PSTN network, a mobile GSM/CDMA (Code Division Multiple Access, code). The same is true for the multi-access network, the third-generation mobile communication all-IP network, and the Internet.
  • the network includes service servers S1, S2, S3, service information center I, service routers R1, R2, service control center C, and service translator T.
  • the service servers S1 and S2 are connected to the service router R1, the service server S3 is connected to the service router R2, the service routers R1 and R2 are connected to the service information center I and the service control center C, and the service translator T is connected to the service control center C and Service router Rl.
  • the service servers S1, S2, and S3 are configured to provide processing capabilities of at least one service, such as an online charging service, an offline charging service, and the like.
  • the service server is directly connected to the corresponding service router, and each service server is configured with a physical address (such as an IP address) of the service router directly connected to the service server and a corresponding port number, and the service server sends a service interaction request to the configured Physical address and corresponding port number.
  • the service server S1, S2 is configured with the physical address of the service router R1 and the corresponding port number
  • the service server S3 is configured with the physical address of the service router R2 and the corresponding port.
  • the service information center I is used to store routing information of various services processed by each service server.
  • the routing information herein includes a destination logical address, a physical location address, and a correspondence between the two services processed by each service server.
  • the destination logical address of the service is used to uniquely identify a service provided on a service server.
  • the logical destination of the service destination is not the corresponding service server, but the corresponding service function.
  • Business functions can be done by one server or by multiple servers in a distributed manner.
  • the physical location address of the service may be the IP address of the service server providing the service and the corresponding port number.
  • the physical location address of the online charging service provided by the service server S1 may be 63.123.13.2:1900, and the service server S1 is When the 1900 port receives the online charging request, it triggers the online charging process and returns the processing result to the requester.
  • the service routers R1 and R2 are used to implement routing and forwarding of service interaction requests and their responses based on the service invocation protocol, and to connect different networks.
  • the general process of routing and forwarding is to find a corresponding physical location address from the service information center according to the destination logical address of the service requested in the service interaction request from the service server, and then forward the service interaction request according to the physical location address, and The received response to the service interaction request is forwarded to the service server that initiated the service interaction request.
  • the service routers R1 and R2 can also add an authentication function, that is, when receiving a service interaction request from the service server, it is determined whether the service server has the right to request the service, and if there is no permission, the request is rejected.
  • the service routers R1 and R2 may modify the service interaction request and its response before routing and forwarding the service interaction request and its response.
  • the service control center C is used for scheduling and policy control of various services on the entire network, and is connected to the service router RK R2.
  • a trigger condition in the service routers R1 and R2, for example, to determine whether the requested service is a specific service from the destination logical address.
  • the service routers R1 and R2 receive the service interaction request, determine whether the content meets the preset trigger condition. If yes, the service interaction request is triggered to the service control center C, and the service control center C performs policy control.
  • the service translator T is used to provide a service layer protocol translation service for communication between service servers. When a service server cannot communicate directly through a service protocol, a service translation service is required.
  • the business translation can translate two or more business protocols into content that the respective business server can recognize and understand.
  • the service translator T of the embodiment of the present invention implements a service translation function with a universal function, and is used to solve the problem of a protocol interface or a parameter interface difference between two or more service servers in a service network system.
  • the service server S1 uses a remote access data call interface based on the IN (Intelligent Network) protocol, and the service server S2 uses an XML (extensible markup language)-based remote access.
  • the data call interface although logically, the two can cooperate with each other to complete the mutual access function of the service data, but the interface definition is different, so that the direct connection is not possible.
  • the service translators are responsible for the adaptation of the two interfaces, so that the service servers of this type can be accessed interactively.
  • the functional entities mainly referred to as service servers
  • This addressing system is different from the existing infrastructure of the underlying network (such as IP network) and must be an addressing system independent of the underlying network. That is, this addressing system
  • the addressing method is an addressing method that is independent of the core network. But it needs It is obvious that in different bearer networks, there may be specific bearer protocols. For example, if the service network is carried over a packet-switched network, the bearer network adopts the IP protocol; if the service network passes the SS7 protocol (Signalling) System No. 7, referred to as "SS7”), the bearer network uses the Transaction Capabilities Application! Part (“TCAP”) protocol.
  • TCAP Transaction Capabilities Application! Part
  • the service server address adopts a domain name mechanism similar to the domain name service system (DOMAIN NAME SYSTEM, referred to as "DNS"), including service category name/server name/domain1/domain2/service type/business sub- Item/business parameter.
  • DNS domain name service system
  • service category name/server name/domain1/domain2/service type/business sub- Item/business parameter For example, China Mobile's CRBT server address can be addressed as follows: CRBT.CMCC.CN; CRBT's debit service processing address can be: CRBT .CMCC .CN /Charge /Parameter 1... Since the business layer has an endless stream of business types, each A business needs to have a business address code that can use text-based service addressing instead of digital-based addressing.
  • a translation service similar to the digital number and text address of the service (ENUM (Telephone Number Mapping Working Group)) can be introduced.
  • the method called from the circuit domain can be the seventh point code or the GT code, but the service enhanced address translation server (like the ENUM server) can translate the address of the seventh system into an address similar to the domain name mechanism. For example, it can be translated into CRBT.CMCC.CN/Charge/Parameterl by using 4B 7F8CED.
  • the embodiment of the present invention provides a search for the address system. The specific service routing function of the end entity.
  • the route is statically configured.
  • the server needs to be configured with the address information that needs to be contacted. This may be a static routing table. It describes the coding information of the service layer and the corresponding actual physical network address and port.
  • each server In a single-service router environment, each server only needs to configure the actual physical address of the service router and the corresponding port.
  • each service server In a tree-like service network connection environment, each service server actually only needs to configure a directly connected service router.
  • the service routers are configured to access each other or access the service information center of the center. The service information center returns the service server path information that needs to be accessed.
  • the service router In addition to the service protocol routing between the same network, the service router also handles the service routing functions between different networks, such as the service protocol encapsulation from the IP network to the service protocol of the seventh network.
  • a well-known protocol (service network request protocol) is needed to establish a contact channel between the two parties.
  • the service network request protocol is used for establishing the connection channel. It is not a real application agreement itself.
  • the application protocol is established by both parties after the service network request protocol is accepted.
  • the service invocation request is separated from the business invocation interaction. That is, it is divided into Service Invoke Protocol and Service Interaction Description Protocol.
  • the service invocation protocol is mainly used to specify the interaction mode between two service layer devices, for example, it takes several handshakes, what role each handshake plays, and so on.
  • the service interaction description protocol is used to specify the content format in the message, such as how many bits the first field occupies, what meaning it represents, how many bits the second field occupies, what it means, and so on.
  • the service interaction description protocol is similar in function to the well-known Session Description Protocol (SDP).
  • FIG. 3 shows a message interaction flowchart when the service is routed in an embodiment of the present invention. As shown in FIG. 3, in step 301, the service server S1 sends a service interaction request to the service router R1, which includes the service request description 1. Then, the process proceeds to step 302.
  • the service router R1 After receiving the service interaction request, the service router R1 sends a service route query message to the service information center I, which carries the destination logical address of the service requested by the service server S1. Then, proceeding to step 303, the service information center I finds the corresponding physical location address according to the destination logical address, that is, the IP address and port of the service server S2 that can provide the service requested by the service server S1, and the IP address of the service server S2 and The port is returned to the service router R1 as a result of the query. Then, proceeding to step 304, the service router R1 forwards the service interaction request to the service server S2 according to the received query result. The request may be modified before the service interaction request is forwarded, and the modified request is forwarded.
  • the service server S2 responds to the service router R1 with the service interaction request response, which carries the service request description 2. Thereafter, proceeding to step 306, the service router R1 forwards the received service interaction request response to the service server S1 according to the IP address of the previous service server S1. This completes the entire routing process. After that, the process proceeds to step 307.
  • the service server S1 can know the IP address of the service server S2. Therefore, the service server S2 sends a response confirmation message directly to the service server S2, indicating that the service interaction request response has been received. Thereafter, a real service application protocol is established between the service servers S1 and S2 to directly perform business entity interaction.
  • the service router R1 may add a sub-step of authentication, that is, determine whether the service server S1 has the right to request the service, and if there is permission, continue the following.
  • the way to reject may be to reply to the service server S1 with a rejection message, or to directly discard the service interaction request.
  • the service router R1 determines the basis of the locally pre-configured information related to the rights, and may also be related information obtained from the third-party server.
  • the service router can discover and process the process of coordinating and participating in the network service control center, and then the service control center issues instructions to the service router to achieve the goal of completing the integrated service.
  • the shared calling capability of the same service can be distributed to multiple service servers through the assistance of the service control center.
  • the function of the service control is somewhat similar to that of the intelligent network.
  • the service control center is equivalent to the service control point (SCP) in the intelligent network.
  • SCP service control point
  • Each service phase is related to one terminal, service A calls service B, and service B.
  • a fault may be escalated or a failure occurs.
  • a setting is made on the service router.
  • the service router receives a request for the service, it triggers the service control center to perform policy control, and then continues the subsequent process.
  • the service uses the destination logical address, and needs to invoke a service as long as the destination logical address of the service is used, and does not need to point to the physical location address of the service server that actually provides the service, so Can be user-friendly settings.
  • the service server of the service After the service server of the service is changed, the user who needs to invoke the corresponding service does not need to make any setting changes.
  • the operator can modify the correspondence between the destination logical address and the physical location address of the service in the service information center, thereby reducing the user. Maintenance costs.
  • the service router automatically routes the service server's call to the service to the service server that provides the service.
  • FIG. 4 is a structural block diagram of a service router according to an embodiment of the present invention.
  • the service router of the embodiment of the present invention includes: a searching unit 410, configured to search for routing information from the service information center 800 after receiving the service interaction request from the service server 500; the forwarding unit 420 is configured to: The service-based service interaction request of the service server 500 and its response are routed and forwarded.
  • the routing information includes a destination logical address, a physical location address, and a correspondence between the two services processed by each of the service servers.
  • 410 is a physical location address searching unit, configured to find a corresponding physical location address from the service information center 800 according to the destination logical address of the service requested in the service interaction request from the service server 500.
  • the service router of the embodiment of the present invention may further include: a control center interaction unit 430, configured to: when the content of the received service interaction request satisfies a preset condition, routing the service interaction request to the service control center 600 for policy control, and only from the business control center The instruction of 600 completes the subsequent route associated with the service interaction request.
  • the service router of the embodiment of the present invention may further include: an authentication unit 440, configured to: when receiving the service interaction request, perform authentication, reject the service interaction request that fails to pass the authentication; and notify the forwarding unit 420 to forward the service that passes the authentication. Interactive request.
  • the service router of the embodiment of the present invention may further include: a modifying unit 450, configured to modify the service interaction request and the response thereof before routing and forwarding the service interaction request and the response. Please refer to FIG. 5.
  • FIG. 5 is a structural block diagram of a service server according to an embodiment of the present invention.
  • the service invoking unit 510 is configured to initiate a service interaction request routed and forwarded by the service router 400 or a service interaction request response for the service interaction request;
  • the service interaction unit 520 is configured to perform interaction of the service entity after the service invoking unit 510 completes the service call through the service router 400.
  • the service router 400 can adopt the structural block diagram shown in FIG. 4 in specific implementation.
  • the service server of the embodiment of the present invention may further include: a translator interaction unit 530, configured to interact with the service translator 700, and obtain a service translator as the service server.
  • Inter-communication provides business layer protocol translation services.
  • the beneficial effects of the present invention are to reduce the maintenance work of the business layer. For example, multiple service servers need to invoke a billing function component.
  • the current implementation method is that these service servers point to the address where the billing function component is located. If the address of the billing component changes, all the service services need to be adjusted.
  • all service servers are directed to the identity of the charging function component, and the service router finds the address of the charging function component from the information center according to the identity of the charging function, and then routes the message to the charging function component according to the address. .
  • the address of the billing function component changes, it is sufficient to adjust the settings in the information center. No change is required in the service server, thus reducing the network maintenance cost.

Description

业务设备交换网络及交换方法、 业务设备
本申请要求于 2005 年 11 月 18 日提交'中国专利局、 申请号为 200510110520.9、 发明名称为 "业务设备交换网络及交换方法，，的中国专利 申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及业务设备之间的交换技术，特别涉及业务设备交换网络及交 换方法、 业务设备。
背景技术 随着通信技术的日益发展， 以公用电话交换网 （Public Switched Telephone Network, 简称 "PSTN" )为代表的固定通信网络和以全球移动通 信系统 ( Global System for mobile Communication, 简称 "GSM" )为代表的 移动通信网络可以为用户提供完善的语音通信服务。 在 PSTN和 GSM中解 决了电话的呼叫、 漫游等等基础呼叫业务。 此外， 通过固定智能网、 移动智 能网解决了通话类业务的特殊路由、 寻址等通话需求。 目前的用户已不满足于单一的语音通话需求， 而需要获得彩信、 上网、 视频等更高级更复杂的服务。为提供这些复杂的应用服务，在网络侧可能需 要多个业务服务器的协同工作，也就是多个业务服务器之间可能需要相互调 用对方提供的业务。本发明所称的业务是指业务服务器所提供的一种服务功 能， 可以是直接面对用户的服务， 如短消息， 也可以是为网络内部的其它业 务月良务器提供的服务功能，如在线或离线计费功能。一台业务服务器可以提 供一种或多种业务，一种业务可以由一台业务服务器单独提供，也可由多台 服务器以分布式方式联合提供。 网际协议多媒体子系统（IP Multimedia Subsystem, 简称 "IMS" ) 的体 系给出了一种目前典型的业务系统。 IMS是 3G ( 31 | Generation, 第三代移 动通信系统）移动网实现分组话音和分组数据、提供统一的多媒体业务和应 用的目标网络。 IMS采用 IP ( Internet Protocol, 网际协议）分组域作为其控 制信令和媒体传输的承载通道， 采用会话初始化协议 （Session Initation Protocol, 筒称 "SIP" )作为呼叫控制信令， 实现了业务管理、 会话控制及 承载接入的三者分离。 IMS的结构如图 1所示，其中涉及到的设备有呼叫会 话控制功能实体（ Call Session Control Function, 简称 "CSCF" ) 110、 应用 服务器 ( Application Server, 简称 "AS" ) 120、 归属签约用户服务器 ( Home Subscriber Server, 筒称 "HSS" ) 130、 开放业务接入（ Open Service Access, 简称 "OSA" )业务能力服务器 140、 OSA应用服务器 150、 网际协议多媒 体业务交换功能实体 （IP Multimedia Service Switching Function , 简称 "IM-SSF " ) 160 和媒体资源功能控制器 （Multimedia ResourceFunction Controller, 筒称 "MRf C" ) 170。 在 IMS中， 业务系统是基于 CSCF的业 务触发模式， 采用多媒体类的呼叫协议， 可以完成更多的业务功能。 在 IMS中， 当某一个业务服务器（例如 AS )需要调用另一个业务服务 器的业务 A时， 在作为业务需求者的业务服务器中需要预先设置所述作为 业务提供者的另一个业务服务器的地址和提供业务 A的端口， 通过向该地 址和端口发送请求消息以获得作为业务提供者的业务服务器的业务服务。 这种通过向作为业务提供者的业务服务器实际地址发送消息以获取其 服务的作法在 PSTN固定智能网和 GSM移动智能网中也被普遍采用。
但是， 上述方案存在维护困难的问题。 例如， 如果改由其他的业务服务 器来提供业务 A, 则需要修改作为业务需求者的业务服务器中与业务 A相 关的设置。 如果需要调用业务 A的业务服务器不只是一台特定的业务服务 器， 而是有几十台、 上百台， 那就需要修改每一台业务服务器中的设置， 工 作量相当大。
发明内容 本发明提供一种业务设备交换网络及交换方法、业务设备，使得可以在 业务层面的实现交换， 降低业务层维护的难度。 根据本发明的一个方面， 一种业务设备交换网络， 包含： 至少两个业务服务器， 用于提供至少一种业务的处理能力； 业务信息中心，用于存储每一个所述业务服务器所处理的各种业务的路 由信息； 至少一个业务路由器， 用于根据所述业务信息中心内的路由信息，对来 自所述业务服务器的基于业务的业务交互请求及其应答进行路由和转发。 根据本发明的另一方面，一种业务设备交换方法，应用于上文所述的网 絡； 所述方法包括： 所述业务服务器向业务路由器发送业务交互请求，所述业务交互请求中 携带所请求业务的信息； 所述业务路由器根据来自所述业务服务器的业务交互请求中所请求业 务的信息，从所述业务信息中心查找到对应的路由信息； 根据该路由信息向 提供业务的业务月良务器转发该业务交互请求，并将所收到的对该业务交互请 求的应答转发给发起该业务交互请求的业务服务器。 根据本发明的再一方面， 一种业务路由器， 包括： 查找单元，用于在接收到来自业务服务器的业务交互请求后查找所请求 业务的路由信息； 转发单元，用于基于所述路由信息对来自所述业务服务器的基于业务的 业务交互请求及其应答进行路由和转发。 根据本发明的又一方面， 一种业务服务器， 包括：
业务调用单元，用于发起通过前述业务路由器路由和转发的业务交互请 求或者针对业务交互请求的业务交互请求应答； 业务交互单元，用于在所述业务调用单元通过业务路由器完成业务调用 后， 进行业务实体的交互。 本发明实施例可以实现业务层内部的交换。因为在业务信息中心存储各 种业务服务器所处理的各种业务的路由信息，在进行业务调用时，通过业务 路由器从业务信息中心查找路由信息， 根据路由信息进行消息的路由和转 发， 因此可以方便用户的设置。 特別是在提供业务的业务服务器变更后， 需 要调用相应业务的用户不需要作任何设置变更，只要由运营商在业务信息中 心修改一下该业务的路由信息即可， 从而降低用户的维护成本。
附图说明
图 1是现有技术中 IMS的网络结构示意图；
图 2是根据本发明一个实施方式的业务设备交换网络结构示意图； 图 3是根据本发明一个实施方式的业务路由时消息交互的流程示意图； 图 4是本发明实施例的业务路由器的结构框图；
图 5是本发明实施例'的业务服务器的结构框图。
具体实施方式 根据本发明一个实施方式的业务设备交换网络如图 2所示。 需要说明的是， 该实施方式只描述了在 IP网络中的組网和信令， 本技 术领域的普通技术人员可以理解， 本发明对于固定 PSTN 网络、 移动 GSM/CDMA ( Code Division Multiple Access, 码分多址）网络、 第三代移动 通信全 IP网络、 因特网等同样适用。 该网络包含业务服务器 Sl、 S2、 S3 , 业务信息中心 I， 业务路由器 Rl、 R2, 业务控制中心 C, 和业务转译器 T。 其中， 业务服务器 Sl、 S2与业务 路由器 R1连接， 业务服务器 S3与业务路由器 R2连接， 业务路由器 Rl、 R2均连接业务信息中心 I和业务控制中心 C, 业务转译器 T连接于业务控 制中心 C和业务路由器 Rl。 业务服务器 Sl、 S2、 S3用于提供至少一种业务的处理能力， 例如在线 计费业务、 离线计费业务等。 业务服务器与对应的业务路由器直接连接，每一个业务服务器中配置与 该业务服务器直连的业务路由器的物理地址（例如 IP地址）及相应的端口 号， 该业务服务器将业务交互请求发送到所配置的物理地址及相应的端口 号。 例如， 业务服务器 Sl、 S2中配置业务路由器 R1的物理地址及相应的 端口号， 而业务服务器 S3 中配置业务路由器 R2的物理地址及相应的端口 业务信息中心 I用于存储每一个业务服务器所处理的各种业务的路由 信息。这里的路由信息包含每一个业务服务器所处理的各种业务的目的逻辑 地址、 物理位置地址及两者的对应关系。 业务的目的逻辑地址用于唯一识别一个业务服务器上提供的一种业务， 业务目的逻辑地址不是对应业务服务器， 而是对应业务功能。业务功能可以 是一个服务器完成， 也可以由多个服务器以分布式方式完成。 业务的物理位置地址可以是提供该业务的业务服务器的 IP地址和相应 的端口号， 例如对于业务服务器 S1所提供的在线计费业务的物理位置地址 可以是 63.123.13.2:1900, 业务服务器 S1从 1900端口收到在线计费请求时 就会触发在线计费处理， 并向请求者返回处理结果。 业务路由器 Rl、 R2用于基于业务调用协议实现业务交互请求及其应答 的路由和转发， 以及连接不同网络。 路由和转发的大致过程为，根据来自业务服务器的业务交互请求中所请 求业务的目的逻辑地址，从业务信息中心查找到对应的物理位置地址，再根 据该物理位置地址转发该业务交互请求，并将所收到的对该业务交互请求的 应答转发给发起该业务交互请求的业务服务器。 业务路由器 Rl、 R2还可以增加鉴权功能， 即收到来自业务服务器的业 务交互请求时判断该业务服务器是否有权限请求该业务，如果没有权限就拒 绝该请求。 业务路由器 Rl、 R2在对所述业务交互请求及其应答进行路由和 转发前 , 还可以对该业务交互请求及其应答进行修改。 业务控制中心 C用于全网各种业务的调度和策略控制， 与业务路由器 RK R2连接。 为了能够将业务交互请求触发到业务控制中心 C， 需要在业务路由器 Rl、 R2中预先设置触发条件， 例如从目的逻辑地址上判断请求的业务是否 为特定的业务。 当业务路由器 Rl、 R2收到业务交互请求时， 判断其中的内 容是否满足预先设置的触发条件，如果是则将该业务交互请求触发到业务控 制中心 C， 由业务控制中心 C进行策略控制。 业务控制中心 C完成策略控 制后， 向相关的业务路由器 Rl、 R2发送指令， 该业务路由器 Rl、 R2根据 收到的指令完成后续的相关路由。 业务转译器 T用于为业务服务器之间的通信提供业务层协议转译服务。 在两个业务服务器之间不能直接通过业务协议通信的时候，需要一个业务转 译的服务。该业务转译可以将两个或者多个业务协议翻译成各自业务服务器 可以认识和理解的内容。 本发明实施例的业务转译器 T实现的是具有通用功能的业务转译功能， 用于在业务网络体系下，解决两种或者多种业务服务器之间的协议接口或者 参数接口差异的问题。举例来说：业务服务器 S1使用一种基于 IN( Intelligent Network, 智能网）协议的远程访问数据调用接口， 业务服务器 S2使用一种 基于 XML ( extensible Markup Language, 可扩充标 "己语言） 的远程访问数 据调用接口， 虽然在逻辑上两者是可以互相配合完成业务数据的互访功能， 然而由于接口定义的不同， 使得不能直接互联。 需要将业务服务器 S1和 S2 都连接到一个业务转译器 T， 由业务转译器 Τ来负责两个接口的适配工作， 使得这一类的业务服务器可以交互访问。 在本发明实施例的业务设备交换网络中， 为便于寻找目的功能实体（主 要指业务服务器）， 需要有一套业务级的编址体系。 这个编址体系不同于已 有的基础网络（例如 IP网络）编址体系， 必须是独立于基础网络的编址体 系。 也就是说， 这个编址体系的编址方法是与基石出网络无关的编址方法。 但是需要说明的是， 在不同的承载网络中， 有可能有具体的承载协议。 例如， 如果业务网络通过基于包交换的网络承载， 则承载网络采用 IP协议； 如果业务网络通过七号信令协议（Signalling System No.7， 简称 "SS7" ) 网 络承载， 则承载网络采用事务处理能力应用部分（ Transaction Capabilities Application! Part, 简称 "TCAP" )协议。 本发明实施黎采用的业务层编址方法重要的是具体定义与对业务的分 类。业务服务器地址采用类似于域名服务系统（DOMAIN NAME SYSTEM, 简称 "DNS" ) 的域名机制， 包括业务类別名 /服务器名 /域 1/域 2/业务种类 / 业务子项 /业务参数。 例如中国移动的彩铃服务器地址可以如下编址： CRBT.CMCC.CN; 彩铃的扣费业务处理地址可以是： CRBT .CMCC .CN /Charge /Parameter 1… 由于业务层存在层出不穷的业务种类，因此每种业务需要有一个业务编 址代号，可以釆用基于文本机制的业务编址，而不采用基于数字机制的编址。 当然， 在具体需要与数字机制编码互通时， 可以引入类似于业务 ENUM ( Telephone Number Mapping working group, 电话号码映射工作组 )的数字 与文本地址的翻译服务。 从电路域调用的方法可以是七号点码或者 GT码的方式，但是这个业务 增强型地址翻译服务器 （类似 ENUM服务器）可以将七号体系的地址翻译 成 类 似 域名 机制 的 地址 。 例 如 可 以 4巴 7F8CED 翻译成 CRBT.CMCC.CN/Charge/Parameterl - - - 在业务网络中为便于寻找到目的的功能实体建立编址体系后，本发明实 施例提供通过这个编址体系寻找到对端实体的具体业务路由功能。 通常来说在点对点的环境下，相当于路由是静态配置，服务器之间事先 配置好需要联系的地址信息，这可能是一个静态路由表。里面描述了业务层 的编码信息与对应的实际物理网络地址与端口。 在单一业务路由器的环境下，各个服务器只需要配置业务路由器的实际 物理地址以及相应的端口。 在树状的业务网络连接环境下，各个业务服务器实际上是只需要配置直 连的业务路由器。业务路由器之间通过互相配置或者访问中心的业务信息中 心， 由业务信息中心向业务路由器返回实际需要访问的业务服务器路径信 息。 业务路由器除了要完成同种网络之间的业务协议路由之外 ,还要处理在 不同网络之间的业务路由功能， 例如从 IP网络的业务协议封装到七号网络 的业务协议。 本发明的实施例中， 业务服务器之间需要互访的时候， 需要一个公知的 协议（业务网络请求协议）来建立双方之间的联系通道， 这种业务网絡请求 协议用于联系通道的建立确认，本身并非真正的应用协议。应用协议则是在 业务网络请求协议获得接受之后由双方共同建立的。 在本发明的实施例中业务调用请求与业务调用交互相分离。也就是分为 业务调用协议 ( Service Invoke Protocol ) 与业务交互描述协议 ( Service Interaction Description Protocol )。 业务调用协议主要用于规定两个业务层设 备间的交互方式， 例如需要几次握手， 每一次握手起什么作用等等。 业务交 互描述协议用于规定消息中的内容格式，例如第一字段占多少比特，代表什 么含义， 第二个字段占多少比特， 代表什么含义， 等等。 业务交互描述协议 在作用上类似于公知的会话描述协议 ( Session Description Protocol, 简称 "SDP" )o 图 3示出本发明一个实施例中业务路由时的消息交互流程图。如图所 3 示， 在步骤 301， 业务服务器 S1向业务路由器 R1发送了业务交互请求， 其 中包含了业务请求描述 1。 此后进入步骤 302, 业务路由器 R1收到该业务交互请求后， 向业务信 息中心 I发送业务路由查询消息， 其中携带了业务服务器 S1所请求业务的 目的逻辑地址。 此后进入步骤 303 , 业务信息中心 I根据该目的逻辑地址找到对应的物 理位置地址， 也就是可提供业务服务器 S1所请求业务的业务服务器 S2的 IP地址和端口， 并将业务服务器 S2的 IP地址和端口作为查询结果返回给 业务路由器 Rl。 此后进入步骤 304, 业务路由器 R1根据收到的查询结果， 将业务交互 请求转发给业务服务器 S2。在转发业务交互请求前可以对该请求进行修改， 将修改后的请求转发出去。 此后进入步骤 305， 业务服务器 S2将业务交互请求应答回应给业务路 由器 R1 , 其中携带业务请求描述 2。 此后进入步骤 306, 业务路由器 R1根据先前业务服务器 S1的 IP地址 将收到的业务交互请求应答转发给业务服务器 Sl。 至此完成了整个路由过 程。 此后进入步骤 307， 业务服务器 S1收到业务交互请求应答后， 可以知 道业务服务器 S2的 IP地址，所以直接向业务服务器 S2发送应答确认消息， 表示已收到业务交互请求应答。 此后， 在业务服务器 S1和 S2之间建立起真正的业务应用协议， 直接 进行业务实体交互。 此时， 根据需要可能需要业务转译器 T的参与。 在上述步驟 302中， 业务路由器 R1收到来自业务服务器 S1的业务交 互请求后， 可以增加一个鉴权的子步骤， 也就是说判断业务服务器 S1是否 有权限请求该业务，如果有权限就继续下面的步骤，如果没有权限就拒绝该 业务交互请求。 拒绝的方式可以是向业务服务器 S1回复一个拒绝消息， 也 可以是直接抛弃该业务交互请求。 业务路由器 R1判断的依据可以是本地预 先配置的与权限相关的信息， 也可以是从第三方服务器获得的相关信息。 在业务服务器之间联系与交互的时候，业务路由器可以发现与检测出需 要网络业务控制中心协调和参与的过程，然后由业务控制中心发出对业务路 由器等的指令， 达到完成综合业务的目标。 例如同一种业务的分担调用能力，可以通过业务控制中心的辅助， 分布 到多个业务服务器上。 业务控制的功能有些类似智能网，业务控制中心相当于智能网中的业务 控制点（ Service Control Point, 筒称 "SCP" ), 每一个业务相 '关于一个终端， 业务 A呼叫业务 B, 业务 B可能升级或发生了故障， 在业务路由器上作一 个设置， 可以由业务路由器在收到对该业务的请求时触发到业务控制中心， 进行策略控制， 再继续后续的流程。 本发明的实施例在具体实现时，将业务用目的逻辑地址标示出来， 需要 调用一个业务时只要使用该业务的目的逻辑地址即可，不需要指向实际提供 业务的业务服务器的物理位置地址， 所以可以方便用户的设置。特別是在提 供业务的业务服务器变更后，需要调用相应业务的用户不需要作任何设置变 更，只要由运营商在业务信息中心修改一下该业务的目的逻辑地址和物理位 置地址的对应关系即可， 降低了用户的维护成本。在业务服务器上只要配置 业务路由器的物理地址即可，业务路由器会将业务服务器对业务的调用自动 路由到提供该业务的业务服务器。 引入业务控制中心后，对业务的路由过程可以作策略控制，使得路由的 过程更为灵活， 可以完成业务分担调用、 同一业务不同版本的控制等更为高 级的功能。 引入业务转译器后，两个使用不同业务通信协议的业务服务器也可以顺 利地进行通信， 从而使现有的业务处理资源可以得到充分的利用。 总之，应用本发明实施例的方案后，一方面给予了用户选择内容的自由， 另一方面运营商还保持了对业务本身的控制。 请参阅图 4, 图 4是本发明实施例的业务路由器的结构框图。 本发明实施例的业务路由器包括： 查找单元 410， 用于在接收到来自业务服务器 500的业务交互请求后从 业务信息中心 800查找路由信息； 转发单元 420， 用于基于所述路由信息对来自所述业务服务器 500的基 于业务的业务交互请求及其应答进行路由和转发。 本发明实施例的一种具体实现中，所述路由信息包含每一个所述业务服 务器所处理的各种业务的目的逻辑地址、 物理位置地址及两者的对应关系； 此时，所述查找单元 410为物理位置地址查找单元， 用于根据来自所述业务 服务器 500的业务交互请求中所请求业务的目的逻辑地址，从所述业务信息 中心 800查找到对应的物理位置地址。 本发明实施例的业务路由器还可以包括： 控制中心交互单元 430， 用于 在所收到的所述业务交互请求中的内容满足预置条件时，将该业务交互请求 路由到所述业务控制中心 600进行策略控制， 并才艮据来自该业务控制中心 600的指令完成与该业务交互请求相关的后续的路由。 本发明实施例的业务路由器还可以包括： 鉴权单元 440， 用于在收到业 务交互请求时还进行鉴权，拒绝没有通过鉴权的业务交互请求； 通知转发单 元 420转发通过鉴权的业务交互请求。 本发明实施例的业务路由器还可以包括： 修改单元 450, 用于在对所述 业务交互请求及其应答进行路由和转发前，对该业务交互请求及其应答进行 修改。 请参阅图 5 , 图 5是本发明实施例的业务服务器的结构框图。
本发明实施例的一种业务服务器包括：
业务调用单元 510 , 用于发起通过业务路由器 400路由和转发的业务交 互请求或者针对业务交互请求的业务交互请求应答；
业务交互单元 520, 用于在所述业务调用单元 510通过业务路由器 400 完成业务调用后， 进行业务实体的交互。
其中，所述业务路由器 400在具体实现时可以采用图 4所示的结构框图。 此外，针对协议之间有可能不匹配的现象,本发明实施例的业务服务器 还可以包括： 转译器交互单元 530, 用于和业务转译器 700进行交互， 获得 业务转译器为所述业务服务器之间的通信提供业务层协议转译服务。 本发明的有益效果在于减少了业务层的维护工作。例如多个业务服务器 要调用一个计费功能组件，目前的实现方式是这些业务服务器都指向这个计 费功能组件所在的地址，如果计费组件的地址发生变化则需要调整所有的业 务服务蔡。 在本发明中， 所有的业务服务器都指向计费功能组件的标识， 业 务路由器根据计费功能的标识从信息中心查到计费功能组件的地址，再根据 这个地址将消息路由到计费功能组件。 当计费功能组件的地址发生变化时， 只要调整信息中心里的设置就可以了， 业务服务器中无需任何变化， 所以降 低了网络维护的,成本。
虽然通过参照本发明的某些优选实施方式，已经对本发明进行了图示和 描述，但本领域的普通技 人员应该明白，可以在形式上和细节上对其作各 种改变， 而不偏离本发明的精神和范围。

Claims

权 利 要 求
1. 一种业务设备交换网絡， 其特征在于， 包括： 至少两个业务服务器， 用于提供至少一种业务的处理能力； 业务信息中心，用于存储每一个所述业务服务器所处理的各种业务的路 由信息；
至少一个业务路由器， 用于根据所述业务信息中心内的路由信息，对来 自所述业务服务器的基于业务的业务交互请求及其应答进行路由和转发。
2. 根据权利要求 1所述的业务设备交换网络， 其特征在于， 所述路由 信息包含每一个所述业务服务器所处理的各种业务的目的逻辑地址、物理位 置地址及两者的对应关系； 所述业务路由器包括： 物理位置地址查找单元，用于根据来自所述业务服务器的业务交互请求 中所请求业务的目的逻辑地址，从所述业务信息中心查找到对应的物理位置 地址； 转发单元，用于根据该物理位置地址向提供该业务的业务服务器转发该 业务交互请求，并将所收到的对该业务交互请求的应答转发给发起该业务交 互请求的业务服务器。
3. 根据权利要求 2所述的业务设备交换网络， 其特征在于， 还包括业 务控制中心， 用于全网各种业务的调度和策略控制； 所述业务路由器还包括： 控制中心交互单元，用于在所收到的所述业务交互请求中的内容满足预 置条件时， 将该业务交互请求路由到所述业务控制中心进行策略控制， 并根 据来自该业务控制中心的指令完成与该业务交互请求相关的后续的路由。
4. 根据权利要求 3所述的业务设备交换网络， 其特征在于， 还包含业 务转译器， 用于为所述业务服务器之间的通信提供业务层协议转译服务。
5. 根据权利要求 1至 4中任一项所述的业务设备交换网络， 其特征在 于，所述业务的目的逻辑地址用于唯一识别一个业务服务器上提供的一种业 务， 釆用域名方式编址； 所述业务的物理位置地址包含提供该业务的业务服务器地址及相应端 口号。
6. 根据权利要求 1至 4中任一项所述的业务设备交换网络， 其特征在 于，在每一个所述业务服务器中配置与该业务服务器直连的业务路由器的物 理地址及相应的端口号，该业务服务器将业务交互请求发送到所配置的物理 地址及相应的端口号。
7. 根据权利要求 1至 4中任一项所述的业务设备交换网络， 其特征在 于， 所述业务路由器还包括修改单元， 用于在对所述业务交互请求及其应答 进行路由和转发前， 对该业务交互请求及其应答进行修改。
8. —种业务设备交换方法， 应用于权利要求 1所述的网络， 其特征在 于， 包括： 业务) ^务器向业务路由器发送业务交互请求， 所述业务交互请求 中携带所请求业务的信息； 所述业务路由器根据来自所述业务服务器的业务交互请求中所请求业 务的信息， 从业务信息中心查找对应的路由信息； 根据该路由信息向提供业 务的业务服务器转发该业务交互请求； 所述业务路由器将所收到的对该业务交互请求的应答转发给发起该业 务交互请求的业务服务器。
9. 根据权利要求 8所述的业务设备交换方法， 其特征在于， 还包括： 所述发起该业务交互请求的业务服务器在收到对该业务交互请求的应 答后， 根据该路由信息向提供业务的业务服务器发出应答确认； 发起该业务交互请求的业务服务器和提供业务的业务服务器之间进行 业务实体交互。
10. 根据权利要求 8所述的业务设备交换方法， 其特征在于， 所述业务 交互请求中携带的信息包括： 所请求业务的目的逻辑地址； 所述路由信息包 括： 业务的目的逻辑地址、 物理位置地址和二者的对应关系； 所述从业务信息中心查找到对应路由信息， 包括： 根据所请求业务的目 的逻辑地址查找其对应的物理位置地址。
11. 根据权利要求 8所述的业务设备交换方法， 其特征在于， 还包括： 所述业务路由器在收到业务交互请求时进行鉴权，拒绝没有通过鉴权的业务 交互请求。
12. 根据权利要求 8所述的业务设备交换方法， 其特征在于， 还包括： 所述业务路由器收到所述业务交互请求时，如果该业务交互请求的内容 满足预置条件， 则将该业务交互请求路由到业务控制中心； 所述业务控制中心对收到的业务交互请求进行策略控制，并向所述业务 路由器发送指令； 所述业务路由器根据来自业务控制中心的指令完成与所述业务交互请 求相关的后续路由。
13. 根据权利要求 9至 12中任一项所述的业务设备交换方法， 其特征 在于， 还包括：
当两个所述业务服务器之间的业务通信协议无法直接匹配时，业务服务 器将业务数据发送到业务转译器， 由该业务转译器进行业务通信协议的转 换， 再将转换后的业务数据发送到另一个业务服务器。
14. 一种业务路由器， 其特征在于， 包括：
查找单元，用于在接收到来自业务服务器的业务交互请求后查找所请求 业务的路由信息； 转发单元，用于基于所述路由信息对来自所述业务服务器的基于业务的 业务交互请求及其应答进行路由和转发。
15. 根据权利要求 14所述的业务路由器， 其特征在于， 所述路由信息 包含每一个所述业务服务器所处理的各种业务的目的逻辑地址、物理位置地 址及两者的对应关系； 所述查找单元为物理位置地址查找单元，用于才艮据来自所述业务服务器 的业务交互请求中所请求业务的目的逻辑地址，从所述业务信息中心查找到 对应的物理位置地址。
16. 根据权利要求 14所述的业务路由器， 其特征在于， 还包括： 控制 中心交互单元， 用于在所收到的所述业务交互请求中的内容满足预置条件 时，将该业务交互请求路由到所述业务控制中心进行策略控制， 并根据来自 该业务控制中心的指令完成与该业务交互请求相关的后续的路由。
17. 根据权利要求 14所述的业务路由器， 其特征在于， 还包括： 鉴权 单元， 用于在收到业务交互请求时还进行鉴权，拒绝没有通过鉴权的业务交 互请求； 通知所述转发单元转发通过鉴权的业务交互倩求。
18. 根据权利要求 14至 17中任一项所述的业务路由器， 其特征在于， 还包括修改单元， 用于在对所述业务交互请求及其应答进行路由和转发前， 对该业务交互请求及其应答进行修改。
19. 一种业务服务器， 其特征在于， 包括：
业务调用单元， 用于发起通过如权利要求 14所述的业务路由器路由和 转发的业务交互请求或者针对业务交互请求的业务交互请求应答；
业务交互单元，用于在所述业务调用单元通过业务路由器完成业务调用 后， 进行业务实体的交互。
20. 根据权利要求 19所述的业务服务器， 其特征在于， 还包括： 转译 器交互单元， 用于和业务转译器进行交互，获得业务转译器为所述业务服务 器之间的通信提供业务层协议转译服务。
PCT/CN2006/003115 2005-11-18 2006-11-20 Reseau de commutation de dispositif de service et dispositif de service de commutation WO2007056960A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP06817853A EP1953973B1 (en) 2005-11-18 2006-11-20 Service device switch network, switch method and service router
ES06817853T ES2401346T3 (es) 2005-11-18 2006-11-20 Red de conmutación de dispositivo de servicio, método de conmutación y encaminador de servicio
US12/122,416 US20080215752A1 (en) 2005-11-18 2008-05-16 Service device, and switching network and switching method for the same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2005101105209A CN100450067C (zh) 2005-11-18 2005-11-18 业务设备交换网络及交换方法
CN200510110520.9 2005-11-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/122,416 Continuation US20080215752A1 (en) 2005-11-18 2008-05-16 Service device, and switching network and switching method for the same

Publications (1)

Publication Number Publication Date
WO2007056960A1 true WO2007056960A1 (fr) 2007-05-24

Family

ID=37390461

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003115 WO2007056960A1 (fr) 2005-11-18 2006-11-20 Reseau de commutation de dispositif de service et dispositif de service de commutation

Country Status (5)

Country Link
US (1) US20080215752A1 (zh)
EP (1) EP1953973B1 (zh)
CN (1) CN100450067C (zh)
ES (1) ES2401346T3 (zh)
WO (1) WO2007056960A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902357B (zh) * 2010-06-29 2014-07-16 中兴通讯股份有限公司 对业务服务器进行调度的方法和系统
US20130110987A1 (en) * 2011-10-31 2013-05-02 Electronics And Telecommunications Research Institute Apparatus and method for providing content location information using ospf opaque lsa
US10311426B2 (en) 2013-02-05 2019-06-04 Visa International Service Association Integrated communications network for transactions
CN105100282B (zh) * 2015-09-06 2021-06-08 浪潮软件股份有限公司 一种烟草云平台下的定时器工具
CN107087039B (zh) * 2016-02-15 2021-10-01 王正伟 交换方法和交换云
US10362141B1 (en) * 2016-03-29 2019-07-23 Amazon Technologies, Inc. Service group interaction management
US10498857B2 (en) * 2016-03-29 2019-12-03 Amazon Technologies, Inc. System interaction monitoring and component scaling
CN109039878B (zh) * 2018-07-24 2021-04-13 西安空间无线电技术研究所 一种适用于卫星光交换网络的业务接入方法及系统
CN111901238B (zh) * 2020-07-09 2022-10-18 中移（杭州）信息技术有限公司 动态路由服务方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1194079A (zh) * 1995-08-21 1998-09-23 摩托罗拉有限公司 用于呼叫处理的通信系统和业务控制器
CN1373954A (zh) * 1999-09-13 2002-10-09 诺基亚公司 下一代网络业务和智能数据网路由器的高级业务体系结构
WO2004006518A1 (ja) * 2002-07-05 2004-01-15 Allied Telesis Holdings K. K. 中継機器、中継方法、プログラム、及び通信システム

Family Cites Families (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4387427A (en) * 1978-12-21 1983-06-07 Intel Corporation Hardware scheduler/dispatcher for data processing system
US5265250A (en) * 1990-03-29 1993-11-23 At&T Bell Laboratories Apparatus and methods for performing an application-defined operation on data as part of a system-defined operation on the data
JPH06318951A (ja) * 1993-01-07 1994-11-15 Toshiba Corp セル転送方法およびセル転送システム
EP0625857B1 (en) * 1993-05-19 1998-06-24 ALCATEL BELL Naamloze Vennootschap Video server
WO1996017306A2 (en) * 1994-11-21 1996-06-06 Oracle Corporation Media server
US7930340B2 (en) * 1995-11-13 2011-04-19 Lakshmi Arunachalam Network transaction portal to control multi-service provider transactions
US6594355B1 (en) * 1997-10-06 2003-07-15 Worldcom, Inc. Method and apparatus for providing real time execution of specific communications services in an intelligent network
US6393481B1 (en) * 1997-10-06 2002-05-21 Worldcom, Inc. Method and apparatus for providing real-time call processing services in an intelligent network
US6229810B1 (en) * 1997-12-31 2001-05-08 At&T Corp Network server platform for a hybrid fiber twisted pair local loop network service architecture
US6779118B1 (en) * 1998-05-04 2004-08-17 Auriq Systems, Inc. User specific automatic data redirection system
US6505228B1 (en) * 1998-07-22 2003-01-07 Cisco Technology, Inc. Dynamic determination of execution sequence
US6353854B1 (en) * 1998-10-01 2002-03-05 International Business Machines Corporation Automatic reconfiguration system for change in management servers having protocol destination addresses
US6798772B2 (en) * 1999-09-07 2004-09-28 Nortel Network Limited Method for public access to private phone numbers and other telephonic peripherals using a caller access code
US7167821B2 (en) * 2000-06-06 2007-01-23 Microsoft Corporation Evaluating hardware models having resource contention
US7313608B1 (en) * 2000-06-21 2007-12-25 Nortel Networks Limited Method and apparatus for using documents written in a markup language to access and configure network elements
ATE433642T1 (de) * 2001-03-02 2009-06-15 Ericsson Telefon Ab L M Verfahren und vorrichtung zur zustellung einer nachricht an einen netzwerkserver in einem serverpool
GB2374242B (en) * 2001-04-07 2005-03-16 Univ Dundee Integrated circuit and related improvements
US7352853B1 (en) * 2001-05-22 2008-04-01 Cisco Technology, Inc. Automation of customer premises equipment provisioning in a telecommunications network
US20040125762A1 (en) * 2001-08-17 2004-07-01 Amit Haller Device, system, method and computer readable medium for attaching to a device identifited by an access point name in a wide area network providing particular services
US7194263B2 (en) * 2001-09-17 2007-03-20 Microsoft Corporation System and method for concurrent operation of a wireless device in two disjoint wireless networks
CN1565143A (zh) * 2001-10-04 2005-01-12 西门子公司 通信网络中业务流的分配传输
US6892264B2 (en) * 2001-10-05 2005-05-10 International Business Machines Corporation Storage area network methods and apparatus for associating a logical identification with a physical identification
EP1456778A4 (en) * 2001-10-26 2006-05-24 Zeosoft Technology Group Inc SYSTEM FOR DEVELOPING, MANAGING AND OPERATING DISTRIBUTED CLIENTS AND SERVERS
US20030083047A1 (en) * 2001-10-29 2003-05-01 Garland Phillips Method and communication network for providing operating information associated with a wireless device
JP2005513916A (ja) * 2001-12-21 2005-05-12 ミュアヘッド、チャールズ・エス 仮想専用ネットワーク・サービスの供給チェーン管理システム
US20030145106A1 (en) * 2002-01-31 2003-07-31 Sun Microsystems, Inc. System and method for directing wireless data packet traffic
KR100502413B1 (ko) * 2002-11-07 2005-07-19 삼성전자주식회사 라스터 스캔 순서 화상 데이터와 블록 스캔 순서 화상데이터 사이의 변환을 위한 화상 처리 장치 및 방법
US7269348B1 (en) * 2002-11-18 2007-09-11 At&T Corp. Router having dual propagation paths for packets
US20040255037A1 (en) * 2002-11-27 2004-12-16 Corvari Lawrence J. System and method for authentication and security in a communication system
US7831693B2 (en) * 2003-08-18 2010-11-09 Oracle America, Inc. Structured methodology and design patterns for web services
US7757033B1 (en) * 2004-02-13 2010-07-13 Habanero Holdings, Inc. Data exchanges among SMP physical partitions and I/O interfaces enterprise servers
US7177921B2 (en) * 2004-03-18 2007-02-13 Hitachi, Ltd. Method and apparatus for storage network management
US7522549B2 (en) * 2004-04-16 2009-04-21 Broadcom Corporation Registering access device multimedia content via a broadband access gateway
US8018936B2 (en) * 2004-07-19 2011-09-13 Brocade Communications Systems, Inc. Inter-fabric routing
US8150437B2 (en) * 2004-09-09 2012-04-03 Nextel Communications Company L.P. Architecture to facilitate the monetization of disparate, inter-worked pushed to talk technologies
US20060090136A1 (en) * 2004-10-01 2006-04-27 Microsoft Corporation Methods and apparatus for implementing a virtualized computer system
US7627123B2 (en) * 2005-02-07 2009-12-01 Juniper Networks, Inc. Wireless network having multiple security interfaces
US7646860B2 (en) * 2005-05-26 2010-01-12 Alcatel-Lucent Usa Inc. Enhanced private call screening
US7853953B2 (en) * 2005-05-27 2010-12-14 International Business Machines Corporation Methods and apparatus for selective workload off-loading across multiple data centers
US8799431B2 (en) * 2005-08-15 2014-08-05 Toutvirtual Inc. Virtual systems management
US8281385B2 (en) * 2005-09-29 2012-10-02 Rockwell Automation Technologies, Inc. Internet friendly proxy server extending legacy software connectivity
FI20060266A0 (fi) * 2006-03-21 2006-03-21 Nokia Corp Osoitteenselvittämismenetelmä tietoliikennejärjestelmässä
US20070258469A1 (en) * 2006-05-05 2007-11-08 Broadcom Corporation, A California Corporation Switching network employing adware quarantine techniques

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1194079A (zh) * 1995-08-21 1998-09-23 摩托罗拉有限公司 用于呼叫处理的通信系统和业务控制器
CN1373954A (zh) * 1999-09-13 2002-10-09 诺基亚公司 下一代网络业务和智能数据网路由器的高级业务体系结构
WO2004006518A1 (ja) * 2002-07-05 2004-01-15 Allied Telesis Holdings K. K. 中継機器、中継方法、プログラム、及び通信システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1953973A4 *

Also Published As

Publication number Publication date
EP1953973A4 (en) 2008-11-19
CN100450067C (zh) 2009-01-07
ES2401346T3 (es) 2013-04-18
CN1863131A (zh) 2006-11-15
EP1953973A1 (en) 2008-08-06
US20080215752A1 (en) 2008-09-04
EP1953973B1 (en) 2013-02-13

Similar Documents

Publication Publication Date Title
US6996076B1 (en) System and method to internetwork wireless telecommunication networks
EP1650916B1 (en) The system and method for realize multimedia call crossover the private network
EP1334639B1 (en) Optimal gateway discovery while roaming
WO2007056960A1 (fr) Reseau de commutation de dispositif de service et dispositif de service de commutation
US7881288B2 (en) Routing media streams from packet switched network to circuit switched network
US6910074B1 (en) System and method for service session management in an IP centric distributed network
US7620391B2 (en) Management of multiple user identities in a communication system
RU2528616C1 (ru) Шлюз сетевого обобщения и соответствующий способ обобщения оконечной точки
EP1942648B1 (en) Processing method for bearer control
US11824903B2 (en) Voice service restoration after element failure
US9444854B2 (en) Session initiation protocol (SIP) router
WO2006026901A1 (fr) Systeme de traitement de signal de service de domaine de paquet et procede utilisant ce systeme
WO2007056916A1 (fr) Systeme permettant de mettre en oeuvre un service de portabilite de numero, et procede correspondant
US20130007291A1 (en) MEDIA INTERWORKING IN IPv4 AND IPv6 SYSTEMS
KR20040106237A (ko) 미디어 경로 재지정 장치 및 방법
JP5330540B2 (ja) 企業ネットワークアクセスポイントの判定のための方法およびシステム
WO2014114088A1 (zh) 一种ngn下实现宽带业务功能的方法及业务平台
US8036211B1 (en) Legacy user proxy call session control function
EP2759098B1 (en) Method and apparatus for configuring service settings for a mobile subscriber
US9100415B2 (en) On-net direct access to voicemail
Voznak Advanced implementation of IP telephony at Czech universities
JP5679577B2 (ja) 中継システム及び中継網のコーディック選択方法
JP5634340B2 (ja) 中継システム及び中継網のコーディック選択方法
EP1299982B1 (en) Opimization of service access
KR100673175B1 (ko) 이기종 망에서의 화상전화 연동 시스템 및 그 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006817853

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2006817853

Country of ref document: EP