WO2008067728A1 - A method, network and device of routing session - Google Patents

A method, network and device of routing session Download PDF

Info

Publication number
WO2008067728A1
WO2008067728A1 PCT/CN2007/003448 CN2007003448W WO2008067728A1 WO 2008067728 A1 WO2008067728 A1 WO 2008067728A1 CN 2007003448 W CN2007003448 W CN 2007003448W WO 2008067728 A1 WO2008067728 A1 WO 2008067728A1
Authority
WO
WIPO (PCT)
Prior art keywords
route
identifier
wildcard
user
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2007/003448
Other languages
English (en)
French (fr)
Inventor
Lingzhi Mao
Youzhu Shi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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 EP07845809A priority Critical patent/EP2091186A4/en
Publication of WO2008067728A1 publication Critical patent/WO2008067728A1/zh
Priority to US12/480,380 priority patent/US20090245240A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, network, and device for routing a session. Background technique
  • IP Multimedia Subsystem is an IP multimedia subsystem defined by the 3rd Generation Partnership Project (3GPP), which is a 3G (3rd Generation) mobile network that implements packet voice and packet data. And a target network that provides unified multimedia services and applications.
  • 3GPP 3rd Generation Partnership Project
  • 3rd Generation 3rd Generation
  • the IMS adopts the IP packet domain as the bearer channel for its control signaling and media transmission, and adopts the SIP (Session Initiation Protocol) protocol as the call control signaling, which realizes the separation of service management, session control and bearer access.
  • the IMS adopts a packet domain as a bearer channel for upper layer control signaling and media transmission, and implements separation of the service/control network and the bearer network, adopts SIP signaling for call control signaling, and RTP/RTCP (Real-Time Protocol I).
  • Real-Time Control Protocol Real-Time Transport Protocol (SDP), SDP (Session Descriptor Protocol), Real-Time Streaming Protocol (RTSP), DNS (Domain Name System)
  • SDP Real-Time Transport Protocol
  • SDP Session Descriptor Protocol
  • RTSP Real-Time Streaming Protocol
  • DNS Domain Name System
  • the protocol cooperates to complete the registration, session routing, and service triggering of the terminal in the IMS. See Figure 1 for a schematic diagram of the IMS network architecture.
  • the proxy session control function entity P-CSCF is a signaling proxy entity for the IMS terminal to access the IMS network, and all signaling from and to the IMS terminal passes through the P-CSCF;
  • the inquiry/service call session control function entity I/S-CSCF completes the call session control
  • the egress gateway control function entity BGCF completes the network egress selection function
  • Multimedia resource function controller MRFC is used to control the multimedia resource function processor MRFP;
  • MRFP mainly completes the processing of media streams (such as: multi-party conference, audio code conversion);
  • the HSS UPSF is a user data configuration unit that stores service related information such as subscription data of the user. Since - see Figure 2, a typical IMS user does the called session routing process, including the following steps:
  • the I-CSCF After receiving the session request, the I-CSCF sends a LIR (Location Request) message to the HSS according to the public identity of the destination user requested by the session.
  • LIR Location Request
  • the HSS carries the S-CSCF address serving the user in the LIA (Location Verification Response) message according to the information saved by the destination user during the registration process.
  • LIA Lication Verification Response
  • the I-CSCF sends a session request to the S-CSCF.
  • the S-CSCF performs subsequent routing according to the route set information retained by the destination user during the registration process.
  • the HSS is allocated as the relevant S-CSCF served by the destination user.
  • the S-CSCF obtains the route set information retained by the destination user during the registration process. That is, the P-CSCF address accessed by the user and the contact address of the user, etc., and the session is routed to the destination user (refer to 3GPP TS.24.229 for the detailed procedure of IMS user registration and routing).
  • the S-CSCF needs to retain the route set information of the destination user.
  • the enterprise network accesses the IMS network
  • only one user identifier namely, domain name user identifier
  • the internal users of the enterprise network ie, domain name related users
  • Adding or deleting users does not need to know the IMS network, nor does it need to have an IMS Service subscription in the IMS network. Therefore, it is not necessary to register for each user inside the enterprise network, and thus the S-CSCF does not Keep routing set information of users inside the enterprise network.
  • the inventor found that, based on the above-mentioned domain name user identifier accessing the IMS network, when the domain name related user does not register in the IMS network, if the user wants to perform correct session routing according to the identity of the domain name related user, it is currently impossible to implement. . Summary of the invention
  • the embodiments of the present invention provide a method, a network, and a device for routing a session, which are used to solve the problem that when a domain name related user is not registered in the IMS network, the correct session routing according to the identity of the domain name related user cannot be implemented.
  • a method for routing a session in the embodiment of the present invention includes the following steps: A.
  • the call session control unit acquires a route set of the session according to the route matching information; B.
  • the call session control unit routes the session by the route set.
  • a network for routing a session includes: a call session control unit, configured to route a session according to a route set; a storage unit, configured to store route matching information; and a user database, configured to receive a location query request, Assigning a corresponding call session control unit; a route set obtaining unit, configured to obtain a route set of the tongue according to the route matching information.
  • a user database of the embodiment of the present invention includes: a storage unit, configured to store route matching information; and an allocating unit, configured to allocate a call session control unit according to the route matching information stored by the storage unit when receiving the location query request.
  • a call session control unit of the embodiment of the present invention includes: a storage unit, configured to store route matching information; a route set obtaining unit, configured to acquire a route set of the session according to the route matching information stored by the storage unit, and Informing the routing unit; the routing unit, configured to acquire the route set obtained by the unit according to the route set, and route the session.
  • the domain name user is registered in the IMS network (for example, the enterprise network identifier is registered in the IMS network), but the domain name related user (such as the internal user of the enterprise network) is not registered on the IMS network, and the call is made.
  • the session control unit acquires the route set of the current session according to the route matching information, and the call session control unit routes the session with the route set.
  • the IMS can be made to route the session for the unregistered user, and the routing capability of the IMS network is enhanced.
  • DRAWINGS 1 is a schematic diagram of an existing IMS network architecture
  • FIG. 2 is a flow chart of a session of an existing IMS user as a called party
  • FIG. 3 is a flow chart of steps of an embodiment of a method according to the present invention.
  • FIG. 4 is a schematic structural diagram of an embodiment of a routing session network according to the present invention.
  • FIG. 5 is a schematic structural diagram of an embodiment of a user database according to the present invention.
  • FIG. 6 is a schematic structural diagram of an embodiment of a call session control unit according to the present invention.
  • Embodiment 7 is a signaling flowchart of Embodiment 1 of a method according to the present invention.
  • FIG. 8 is a schematic diagram of a UML model of an extended public identity according to an embodiment of the present invention.
  • FIG. 9 is a signaling flowchart of Embodiment 2 of a method according to the present invention. detailed description
  • the identity of the domain name related user can still be used (enterprise network)
  • the internal user identifier is configured to perform the correct session routing.
  • Prerequisites 1 The HSS, or the HSS and the call session control unit, store route matching information, where the route matching information includes: a domain name user identifier, and a corresponding wildcard route identifier.
  • the wildcard route identifier is configured in the management mode; or is obtained according to the registration process of the domain name user identifier; or configured by the application server, the wildcard route identifier represents a series of user identities satisfying a certain condition, and the wildcard symbol can be used. Make a logo like this! *!
  • the @huawei.com identifier identifies all users whose domain name is huawei.com, and can also be identified by other logical expressions, such as the wildcard condition described by XML.
  • the ID satisfies all the identities of the domain name huawei.com.
  • Prerequisite 2 The domain name user ID is registered on the IMS network.
  • the domain name user identifier may be a domain name or an IP address of the enterprise network, such as sip:huawei.com, or a user identifier that identifies the enterprise network, such as sip:destination@huawei.com, or an identity enterprise network. Wildcard user ID for all internal users, such as ! *!@huawei.com.
  • the domain name user identity registration may be a normal IMS registration, or may indicate in the registration message that this is a domain name user identity registration.
  • the embodiment of the present invention includes the following main steps:
  • the user database receives a location query request
  • the user database receives a location query request from the call session control unit, and the request message includes the session destination user identity.
  • the user database allocates a call session control unit
  • the user database matches the called user identifier in the location query message with the locally stored wildcard routing identifier. If any wildcard routing identifier is matched, the user database is assigned as the call of the domain name user service corresponding to the wildcard routing identifier. Session control unit.
  • the route set is a set of addresses of the nodes passing through in the subsequent session path.
  • the route set may include the address of the proxy session unit accessed by the called user and the contact address of the destination user of the session request.
  • the called user described in this article is the session request destination user.
  • This step includes at least the following two situations:
  • Case 1 After message forwarding between network elements, after the call session control unit receives the session request, the called user identifier is sent to the user database to send a request message.
  • the user database matches the called user identifier by using the wildcard routing identifier. When any of the wildcard routing identifiers is met, the user database sends the corresponding domain name user identifier to the call session control unit, or the routing set corresponding to the domain name identifier.
  • the call session control unit uses the route set corresponding to the domain name user identifier as the route set of the session, or uses the route set delivered by the user database as the route set of the session;
  • the wildcard route identifier can be sent at the same time, so that when the session request is received again, the call session control unit directly performs matching and routing, thereby reducing interaction with the user database and saving network resources.
  • the call session control unit uses the route set corresponding to the domain name user identifier or the route set delivered by the user database as the route set of the current session.
  • Case 2 When the domain name user registers, the user database sends the wildcard route identifier to the call session control unit. After the call session control unit receives the session request, the call session control unit matches the called user identifier in the session request with the wildcard route identifier sent by the previous user database. When any of the wildcard route identifiers are met, the call session control unit uses the route set of the domain name user corresponding to the matched wildcard route identifier as the route set of the current session.
  • the call session control unit routes the session by using the route set.
  • the embodiment of the present invention further provides a routing session network, as shown in FIG. 4, which includes: a user database, a storage unit, a route set acquiring unit, and a call session control unit sequentially connected;
  • the route set obtaining unit includes interconnected wildcard route identifier determining subunits and acquiring subunits.
  • the user database is configured to allocate a call session control unit when receiving the location query request.
  • the user database mainly stores user identity, registration information, and service trigger information.
  • the user database is called HSS (Home Subscriber Server), and the corresponding user database in the TISPAN architecture is defined as UPSF (User Configuration Service Function).
  • UPSF User Configuration Service Function
  • the Diameter protocol can be made between the user database and the call session control unit.
  • the storage unit is configured to store route matching information.
  • the route set obtaining unit is configured to obtain a route set of the current session according to the route matching information stored by the storage unit, and notify the call session control unit. Further, the wildcard route identifier determining subunit is configured to match the called user identifier in the session request by using a wildcard route identifier in the route matching information stored by the storage unit; where the obtaining subunit is used Obtaining a route set corresponding to the wildcard route identifier matched by the wildcard route identifier judging subunit.
  • the call session control unit is configured to provide a registration service, a session control, and the like for the user terminal.
  • there may be other call session control units such as P-CSCF, I-CSCF between the call session control unit S-CSCF, the user terminal and the S-CSCF.
  • the E1 interface between the call session control unit and the user terminal may be a SIP protocol or the like.
  • the embodiment of the present invention further provides a user database.
  • the method includes: a storage unit, and an allocation unit and a route set obtaining unit connected to the storage unit; and further, the route set acquiring unit The interconnected wildcard route identification subunit and the acquisition subunit are included.
  • the storage unit is configured to store route matching information, including, for example, a domain name user identifier and a wildcard route identifier.
  • the allocating unit is configured to allocate a call session control unit according to the route matching information stored by the storage unit when receiving the location query request.
  • the allocating unit is configured to match the wildcard routing identifier according to the destination identity in the query request, and allocate a corresponding call session control unit, that is, a call session control unit served by the domain name user.
  • the route set obtaining unit is configured to obtain the current session set according to the route matching information stored by the storage unit, and notify the call session control unit or send the route matching information to the call session control unit.
  • the wildcard route identifier determining subunit is configured to match the called user identifier in the session request with the wildcard route identifier in the route matching information stored by the storage unit; and acquire the subunit for acquiring The route set corresponding to the wildcard route identifier matched by the wildcard route identifier judging subunit.
  • the embodiment of the present invention further provides a call session control unit.
  • the method includes: a storage unit, a route set acquisition unit connected to the storage unit, and a routing unit with the route set acquisition unit.
  • the route set obtaining unit includes the interconnected wildcard route identifier determining subunit and the obtaining subunit.
  • the storage unit is configured to store route matching information.
  • the route set obtaining unit is configured to obtain a route set of the current session according to the route matching information stored by the storage unit, and notify the routing unit. Further, the wildcard routing identifier is judged a subunit, configured to match, by using a wildcard route identifier in the route matching information stored by the storage unit, the called user identifier in the session request; and acquiring a subunit, configured to obtain a match with the wildcard route identifier determining subunit The wildcard route to it identifies the corresponding route set.
  • the routing unit is configured to: according to the route set obtained by the route set obtaining unit, routing the session.
  • the method of the embodiment of the present invention is specifically described below by means of two method embodiments.
  • Method Embodiment 1 The HSS sends routing information to the S-CSCF during the session establishment process. Referring to FIG. 7, the following specific steps are included:
  • the session request arrives at the destination network I-CSCF;
  • the session request carries the called user identifier: UnRegId@huawei.com, and the UnRegId@huawei.com is not currently registered on the IMS network.
  • the I-CSCF queries the HSS to provide the S-CSCF address for serving the HSS by sending an LIR (Location Information Request) message carrying UnRegId@huawei.com;
  • LIR Location Information Request
  • the HSS After receiving the LIR message, the HSS does not perform the registration process on the HSS because the UnRegId@huawei.com has not been registered in the HSS. Therefore, the HSS first determines whether the session request directed to the user satisfies the subsequent route according to the locally stored wildcard route identifier.
  • the wildcard routing identifier can be stored by extending the data structure on the HSS.
  • the data structure of the Public identification public identity stored on the HSS can be extended, and the extended UML model of the public identity is as shown in FIG. 8.
  • the wildcard route identifier is stored by adding a field Wildcared route to the public identity.
  • the wildcard route identifier can be configured in an administrative manner in the HSS.
  • the domain name user identifier and its corresponding wildcard route identifier are configured in the HSS through the operation and maintenance interface, so that the user identifier that satisfies the wildcard route identifier is even Subsequent routes are still available for registration.
  • 'The AS configures the wildcard route ID through the Sh interface.
  • the HSS and/or the S-CSCF obtain the wildcard route identifier, and the registration message carries the wildcard route identifier information, for example, the To message header field is carried in the Register message!
  • the Register message carries the To header field of 2878!*!, indicating that the wildcard route identifier is satisfied for all sessions of the 2878 field.
  • the routing condition that is, the registered domain name user ID is the wildcard user ID.
  • the HSS and/or S-CSCF are also According to the registration of the domain name user identifier, the corresponding wildcard routing identifier is associated, for example, the routing provisioning condition corresponding to a domain name user identifier is configured through management configuration.
  • the related S-CSCF is an S-CSCF that provides services for domain name users.
  • the HSS returns the information of the S-CSCF to the I-CSCF in the LIA message.
  • the I-CSCF sends an INVITE request to the S-CSCF allocated by the HSS;
  • the S-CSCF sends a SAR (Server Allocation Request) message to the HSS in accordance with the processing of the unregistered user in 3GPP 24.229 to actively request to download user related data;
  • SAR Server Allocation Request
  • the SAR message contains the called user ID of this session: UnRegId@huawei.com.
  • the HSS determines that the wildcard routing identifier of the local storage is satisfied according to UnRegId@huawei.com carried in the SAR message (the related content in step 3);
  • the routing information is sent to the S-CSCF by using the SAA (Server Assignment Request Response) message.
  • the routing information includes at least: a domain name user identifier or a domain name user identifier corresponding to the wildcard matching condition met by UnRegId@huawei.com Routing set.
  • Destination-ID :: ⁇ AVP header: xxx 10415>
  • the URI carries the domain name user identifier, and the value may be TEL URI or SIP.
  • the S-CSCF uses the route set corresponding to destination@huawei.com as the route set of the session. Pass the domain name user ID method 2:
  • the HSS carries the domain name user identifier in the Public-Identification public identity information (the extended public identity model is shown in FIG. 8), and further, the identifier that is carried in the public identity information is the domain name user identifier, and is The [identity type] attribute of the public identity adds a new enumeration category, such as: Destination Route category. The public identification of this category is considered to be the domain name user identifier.
  • the S-CSCF Since the domain name user ID has been registered in the IMS network, the S-CSCF has recorded its note.
  • the HSS can carry the extended Diameter AVP in the SAA message.
  • Route-set:: ⁇ AVP header: xxx 10415>
  • p-addr identifies the P-CSCF address accessed by the user
  • C-ADDR identifies the contact address of the user
  • the HSS may also send a wildcard route identifier to the S-CSCF.
  • the S-CSCF receives the session request again, it can determine whether the called user identifier satisfies the subsequent routing condition by using the wildcard route identifier, and then routes the session request by using the routing set corresponding to the domain name user identifier, thereby reducing the number of the session request. Message interaction between the HSS and the S-CSCF.
  • the Diameter AVP may be extended to transmit an additional indication to notify the S-CSCF.
  • the service profile of the domain name user is used as the service profile of the called user in this session for subsequent processing. Or use other methods to achieve this goal, such as: using the Public identity attribute Wildcared PSI field to carry the wildcard route identifier, or set the Public identity attribute Identity to the new enumeration type, such as [Route & Service], to indicate that the S-CSCF uses the domain name user corresponding
  • the routing set and the service configuration file are used as the routing set of the session and the service configuration file for subsequent processing.
  • the S-CSCF obtains the routing set corresponding to the domain name user identifier as the routing set of the current session according to the routing information in the SAA message, or directly adopts the routing set delivered by the HSS as the routing set of the session;
  • the HSS may also return a route set to the I-CSCF, and the I-CSCF passes the route set to the S-CSCF.
  • the HSS returns a service configuration file corresponding to the domain name user to the S-CSCF, where the service configuration file includes a route set corresponding to the domain name user, and the S-CSCF executes a service configuration file, such as iFC (initial The filtering rule), the corresponding application server name in the last iFC is the routing address corresponding to the domain name user, and the S-CSCF uses this as the routing path of the current session.
  • iFC initial The filtering rule
  • the enterprise network After the session request is routed to the domain name user, that is, the enterprise network, the enterprise network internally routes the session request to the called user, so that when the internal user of the enterprise network is not registered in the IMS network, the internal user identifier of the enterprise network can still be used. Make the correct session routing.
  • Method Embodiment 2 When registering the domain name user identifier, the HSS sends routing information to the S-CSCF that provides services for the domain name user. See Figure 9 for the following specific steps:
  • S-CSCF receives a registration request initiated by the domain name user identifier
  • the S-CSCF registers the HSS with the SAR message, and the SAR message carries the domain name user identifier
  • the HSS compares the domain name user identifier according to the preset information, thereby determining that the registration request is initiated by the domain name user;
  • Attribute of the ID adding new ⁇ identity type] Class another 1 J, such as energizing a new category [destination route] is identified to the public identifier corresponding to the user ID is the domain user, called the domain user is met wild routing identifier of the user Routes can be performed according to the route set corresponding to the domain name user.
  • a new category [wildcard URI] is added to the HSS to identify the wildcard route identifier.
  • the HSS sends the wildcard route identifier to the S-CSCF.
  • the extended Diameter protocol attribute pair can be carried in the SAA message, such as
  • Matched-route :: ⁇ AVP header: xxx 10415>
  • the wildcared URI represents the wildcard route identifier, such as the wildcared URI can be set! * l@huawei.com, which identifies all user IDs for the domain name huawei.com.
  • the S-CSCF may obtain the wildcard route identifier by using the registration request process of the home name user identifier.
  • the S-CSCF receives an initial session request, such as an INVITE message, it is determined according to the wildcard route identifier, and the session meeting the condition is processed according to the route set corresponding to the domain name user identifier;
  • the S-CSCF determines that the called user identifier, such as UnRegId@huawei.com, carried in the session request matches the wildcard routing identifier, and obtains the registration routing path corresponding to the domain name user identifier, and uses the route.
  • the enterprise network After the subsequent session request is routed to the domain name user, that is, the enterprise network, the enterprise network internally routes the session request to the called user, so that the internal users of the enterprise network are not registered in the IMS network.
  • the time when the HSS sends the route matching information (the wildcard route identifier) to the S-CSCF is not limited to the process of initiating the registration by using the domain name user identifier, and the HSS may also send the route matching information to the S in other processes.
  • -CSCF such as: HSS carries routing samples during the active push of user files With the information, the HSS sends a PPR (File Push Request message) to the S-CSCF, which carries the route matching information.
  • the domain name user is registered in the IMS network (for example, the enterprise network identifier is registered in the IMS network), but the domain name related user (such as the internal user of the enterprise network) is not registered in the IMS network.
  • the call session control unit is allocated according to the route matching information; then, the route set corresponding to the session is obtained according to the route matching information; and finally, the call session control unit routes the route with the route set. Second session. Therefore, the IMS can perform the tongue routing for the unregistered users, and enhance the routing capability of the IMS network.
  • the user database transmits the route matching information and the domain name user route set to the call session control unit by extending the attribute of the Diameter protocol to the AVP; or the user database transmits the domain name to the call session control unit by extending the public identity information.
  • the wildcard route identifier is configured in a management manner; or is obtained by the user database according to the registration report information of the domain name user identifier; or configured by the application server.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种路由会话的方法、 网络及设备 技术领域
本发明涉及通信领域， 特别是涉及一种路由会话的方法、 网络及设备。 背景技术
IP多媒体子系统 IMS ( IP Multimedia Subsystem )是第三代移动通信标准 化伙伴项目 3GPP ( 3rd Generation Partnership Project )标准定义的一个 IP多媒 体子系统， 是 3G ( 3rd Generation )移动网实现分组话音和分组数据， 以及提 供统一的多媒体业务和应用的目标网络。
IMS 采用 IP 分组域作为其控制信令和媒体传输的承载通道， 采用 SIP ( Session Initiation Protocol, 会话初始化协议）协议作为呼叫控制信令， 实现 了业务管理、 会话控制及承载接入的三者分离。 具体的， IMS 采用分组域为 其上层控制信令和媒体传输的承载通道，实现业务 /控制网络和承载网络分离， 采用 SIP信令为呼叫控制信令， 与 RTP/RTCP ( Real-Time Protocol I Real-Time Control Protocol , 实时传输协议 /实时控制协议）、 SDP ( Session Descriptor Protocol; 会话描述协议）、 RTSP ( Real - Time Streaming Protocol, 实时传送 流媒体协议）、 DNS ( Domain Name System, 域名系统）等协议配合， 共同完 成 IMS中终端的注册、 会话路由、 业务触发等服务。 参见图 1所示， 为 IMS 网络架构示意图。
其中， 代理会话控制功能实体 P-CSCF为 IMS终端接入 IMS网络的信令 代理实体， 所有来自、 发往 IMS终端的信令均经过 P-CSCF;
问讯 /服务呼叫会话控制功能实体 I/S-CSCF完成呼叫会话控制；
出口网关控制功能实体 BGCF完成网络出口选择功能；
多媒体资源功能控制器 MRFC用于控制多媒体资源功能处理器 MRFP;
MRFP主要完成媒体流的处理（如： 多方会议、 音频代码转换）；
HSS UPSF 为用户数据配置单元， 其存贮用户的签约数据等业务相关信 自- 参见图 2所示， 一次典型的 IMS用户做被叫的会话路由过程， 包括下列 步骤：
1 ) I-CSCF收到会话请求后，根据会话请求的目的用户公有标识， 向 HSS 发送 LIR (地理位置查询请求） 消息。
2 ) HSS根据目的用户在注册过程中保存的信息， 在 LIA (地理位置查询 响应） 消息中携带为该用户服务的 S-CSCF地址。
3 ) I-CSCF发送会话请求至 S-CSCF。
4 ) S-CSCF根据会话请求目的用户在注册过程中保留的路由集信息进行 后续路由。
根据上述流程可以看出， 会话到达被叫网络后， 由 HSS分配为目的用户 服务的相关 S-CSCF; 会话到达该 S-CSCF后， 该 S-CSCF根据目的用户在注 册过程保留的路由集信息， 即用户接入的 P-CSCF地址以及用户的联系地址 等， 将会话路由至目的用户 （关于 IMS用户注册、 路由的详细过程可以参考 3GPP TS.24.229 )。
由此可见， 基于现有技术若想将会话正确路由到目的用户， 需要 S-CSCF 保留该目的用户的路由集信息。
而在企业网接入 IMS网络的情况下， 仅需要注册一个用于代表企业网的 身份的用户标识（即域名用户标识）， 企业网内部用户 （即域名相关用户） 由 企业网进行管理， 这些用户的添加、 删除不需要知会 IMS网络， 也不需要在 IMS网络具有服务订购关系（ IMS Service subscription )， 因此也不需要针对企 业网内部的每个用户进行注册，进而 S-CSCF上不会保留企业网内部用户的路 由集信息。 （详细的描述见 TISPAN WI 1047以及相关文稿 )
发明人在发明过程中发现， 基于上述以域名用户标识接入 IMS网络的情 况， 当域名相关用户没有在 IMS网络进行注册时， 若想根据域名相关用户的 标识进行正确的会话路由， 目前无法实现。 发明内容
本发明实施例提供一种路由会话的方法、 网络及设备， 用以解决在域名 相关用户没有在 IMS网络进行注册时， 目前无法实现根据域名相关用户的标 识进行正确的会话路由的问题。
本发明实施例的一种路由会话的方法， 包括下列步骤： A、 呼叫会话控制 单元根据路由匹配信息获取本次会话的路由集； B、 呼叫会话控制单元以该路 由集路由本次会话。
本发明实施例的一种路由会话的网络， 包括： 呼叫会话控制单元， 用于 根据路由集路由会话； 存储单元， 用于存储路由匹配信息； 用户数据库， 用 于在收到位置查询请求时， 分配对应的呼叫会话控制单元； 路由集获取单元， 用于根据路由匹配信息， 获取本次 舌的路由集。
本发明实施例的一种用户数据库， 包括： 存储单元， 用于存储路由匹配 信息； 分配单元， 用于在收到位置查询请求时， 根据存储单元存储的路由匹 配信息， 分配呼叫会话控制单元。
本发明实施例的一种呼叫会话控制单元， 包括： 存储单元， 用于存储路 由匹配信息； 路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对 应获取本次会话的路由集， 并告知路由单元； 路由单元， 用于根据路由集获 取单元获取的路由集， 路由会话。
本发明实施例在域名用户在 IMS网络进行了注册（例如： 以企业网标识 在 IMS网络进行了注册）， 但域名相关用户 （如企业网内部用户）没有在 IMS 网络进行注册的前提下， 呼叫会话控制单元根据路由匹配信息对应获取本次 会话的路由集， 并且呼叫会话控制单元以该路由集路由本次会话。 从而可以 使得 IMS可以针对对于未注册用户的会话进行路由， 增强了 IMS网络的路由 能力。 附图说明 图 1为现有 IMS网络架构示意图；
图 2为现有 IMS用户作为被叫的会话路由流程图；
图 3为本发明方法实施例步骤流程图；
图 4为本发明路由会话网络实施例的结构示意图；
图 5为本发明用户数据库实施例的结构示意图；
图 6为本发明呼叫会话控制单元实施例的结构示意图；
图 7为本发明方法实施例一的信令流程图；
图 8为本发明实施例扩展后的公有身份的 UML模型示意图；
图 9为本发明方法实施例二的信令流程图。 具体实施方式
基于上述现有以域名用户标识（企业网标识）接入 IMS网络的情况， 为 了在域名相关用户 （企业网内部用户）没有在 IMS网络进行注册时， 仍然可 以根据域名相关用户的标识（企业网内部用户标识）进行正确的会话路由， 本发明方法实施例执行之前， 至少要满足下列条件：
前提条件 1: HSS, 或者 HSS和呼叫会话控制单元中存储有路由匹配信 息， 所述路由匹配信息包括： 域名用户标识， 以及与之对应的通配路由标识。 其中的通配路由标识通过管理方式进行配置； 或才艮据域名用户标识的注册过 程获得； 或通过应用服务器进行配置， 通配路由标识代表了满足某一条件的 系列用户身份， 可以采用通配符号进行标识如！ *！ @huawei.com标识标识满 足条件的为所有域名为 huawei.com的用户身份， 也可以由其他逻辑表达式进 行标识如采用 XML描述的通配条件
<Idcondition >
< domain>huawei.com</domain>
</Idcondition>
标识对于所有域名为 huawei.com 的身份满足条件
进一步， 若路由匹配信息不是来自管理方式的配置时， 还需满足下列条 件：
前提条件 2: 域名用户标识在 IMS网络进行了注册
所述的域名用户标识可以是企业网的域名或 IP地址， 如 sip:huawei.com, 也可以是一个标识企业网的用户标识，如 sip:destination@huawei.com，也可以 是一个标识企业网所有内部用户的通配用户标识， 如! *!@huawei.com。 所述 的域名用户标识注册可以是一个普通的 IMS注册， 也可以在注册消息中指示 这是一个域名用户标识注册。
满足上述前提条件之后， 参见图 3所示， 本发明实施例包括下列主要步 骤：
51、 用户数据库收到位置查询请求；
用户数据库收到呼叫会话控制单元的位置查询请求， 该请求消息中包含 会话目的用户身份标识。
52、 用户数据库分配呼叫会话控制单元；
用户数据库以本地存储的通配路由标识对位置查询消息中的被叫用户标 识进行匹配， 若匹配到任一通配路由标识， 则用户数据库分配为所述通配路 由标识对应的域名用户服务的呼叫会话控制单元。
53、 根据路由匹配信息获取本次会话的路由集；
其中路由集为后续会话路径中经过节点的地址集合， 如路由集中可以包 含被叫用户接入的代理会话单元地址以及会话请求目的用户的联系地址。
本文所述的被叫用户即会话请求目的用户。
本步骤至少包括以下两种情况：
情况一、 通过网元之间的消息转发， 在所述呼叫会话控制单元收到会话 请求后， 以被叫用户标识向用户数据库发送请求消息。 用户数据库以通配路 由标识对所述被叫用户标识进行匹配， 当满足任一通配路由标识时， 则用户 数据库向呼叫会话控制单元下发相应的域名用户标识， 或该域名标识对应的 路由集； 呼叫会话控制单元以该域名用户标识对应的路由集作为本次会话的 路由集， 或者以用户数据库下发的路由集作为本次会话的路由集； 进一步还 可同时下发通配路由标识， 以便再次收到会话请求时， 由呼叫会话控制单元 直接进行匹配和路由， 从而减少与用户数据库的交互， 节约网络资源。 呼叫 会话控制单元以该域名用户标识对应的路由集或以用户数据库下发的路由 集， 作为本次会话的路由集。
情况二、 用户数据库在域名用户注册时， 将所述通配路由标识下发至呼 叫会话控制单元。 之后， 通过网元之间的消息转发， 在所述呼叫会话控制单 元收到会话请求后， 以之前用户数据库下发的通配路由标识对所述会话请求 中的被叫用户标识进行匹配， 当满足任一通配路由标识时， 则呼叫会话控制 单元使用与所述匹配到的通配路由标识对应的域名用户的路由集， 作为本次 会话的路由集。
S4、 呼叫会话控制单元以该路由集路由本次会话；
与上述方法对应， 本发明实施例还提供了路由会话网络， 参见图 4所示， 其包括： 依次相连的用户数据库、 存储单元、 路由集获取单元和呼叫会话控- 制单元； 进一步， 所述路由集获取单元中包括相互连接的通配路由标识判断 子单元和获取子单元。
所述用户数据库， 用于在收到位置查询请求时， 分配呼叫会话控制单元。 该用户数据库主要存储用户身份、注册信息和服务触发信息等， 在 3GPP IMS 架构中用户数据库被称为 HSS (归属用户服务器)， 对应的在 TISPAN架构中 用户数据库被定义为 UPSF (用户配置服务功能） ，用户数据库与呼叫会话控制 单元之间可以使 Diameter协议。
所述存储单元， 用于存储路由匹配信息。
所述路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对应获 取本次会话的路由集， 并告知呼叫会话控制单元。 进一步， 其中的通配路由 标识判断子单元， 用于以存储单元存储的路由匹配信息中的通配路由标识， 对所述会话请求中的被叫用户标识进行匹配； 其中的获取子单元， 用于获取 与通配路由标识判断子单元匹配到的通配路由标识相应的路由集。
所述呼叫会话控制单元， 用于为用户终端提供注册服务、 会话控制等功 能， 在 IMS网络中， 呼叫会话控制单元 S-CSCF, 用户终端和 S-CSCF之间还 可能存在其他的呼叫会话控制单元如 P-CSCF、 I- CSCF。 呼叫会话控制单元和 用户终端之间的 E1接口可以是 SIP协议等。
对应上述网络本发明实施例还提供了用户数据库， 参见图 5所示， 其包 括： 存储单元， 以及与所述存储单元相连的分配单元和路由集获取单元； 进 一步， 所述路由集获取单元中包括相互连接的通配路由标识判断子单元和获 取子单元。
所述存储单元， 用于存储路由匹配信息， 包括如域名用户标识、 通配路 由标识。
所述分配单元， 用于在收到位置查询请求时， 根据存储单元存储的路由 匹配信息， 分配呼叫会话控制单元。
进一步， 所述分配单元用于根据查询请求中的目的身份， 匹配通配路由 标识， 并分配相应的呼叫会话控制单元， 即为域名用户服务的呼叫会话控制 单元。
所述路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对应获 取本次会话由集， 并告知呼叫会话控制单元或发送路由匹配信息至呼叫会话 控制单元。 进一步， 其中的通配路由标识判断子单元， 用于以存储单元存储 的路由匹配信息中的通配路由标识， 对所述会话请求中的被叫用户标识进行 匹配； 获取子单元， 用于获取与通配路由标识判断子单元匹配到的通配路由 标识相应的路由集。
对应上述网络本发明实施例还提供了呼叫会话控制单元， 参见图 6所示， 其包括： 存储单元， 与所述存储单元相连的路由集获取单元， 以及与所述路 由集获取单元的路由单元； 进一步， 所述路由集获取单元中包括相互连接的 通配路由标识判断子单元和获取子单元。
所述存储单元， 用于存储路由匹配信息。
所述路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对应获 取本次会话的路由集， 并告知路由单元。 进一步， 其中的通配路由标识判断 子单元， 用于以存储单元存储的路由匹配信息中的通配路由标识， 对所述会 话请求中的被叫用户标识进行匹配； 获取子单元， 用于获取与通配路由标识 判断子单元匹配到的通配路由标识相应的路由集。
所述路由单元， 用于根据路由集获取单元获取的路由集， 路由会话。 以下通过两个方法实施例具体描述本发明实施例的方法。
方法实施例一、 HSS在会话过程建立过程中向 S-CSCF下发路由信息， 参见图 7所示， 包括下列具体步骤：
1、 会话请求到达目的网络 I-CSCF;
所述会话请求中携带有被叫用户标识： UnRegId@huawei.com， 该 UnRegId@huawei.com当前未在 IMS网络进行注册。
2、 I-CSCF 通过发送 LIR ( location information Request ) 消息携带 UnRegId@huawei.com向 HSS查询为其提供服务的 S-CSCF地址；
3、 HSS 收到 LIR消息后， 由于 UnRegId@huawei.com尚未在 HSS执行注 册过程， 因此 HSS首先根据本地保存的通配路由标识判断指向该用户的会话 请求是否满足进行后续路由的奈件；
可通过在 HSS上扩展数据结构来存储所述通配路由标识。 例如可以扩展 HSS 上存储的 Public identification公有身份的数据结构， 扩展后的公有身份 的 UML模型如图 8所示。其中通过在公有身份中增加一个字段 Wildcared route 来存储所述通配路由标识。 在本例子中可以设置 Public identification 的 [Wildcared route】字段为！*！ @huawei.com ，标识对于所有域名为 huawei.com 的用户身份满足通配路由标识。
所述通配路由标识在 HSS中可以管理方式进行配置， 例如： 通过操作维 护接口在 HSS中配置域名用户标识及其对应的通配路由标识， 对于满足通配 路由标识的用户标识， 使其即使尚未注册仍然可以进行后续路由。 或者， '由 AS 通过 Sh接口对通配路由标识进行配置。 或者， 在以域名用户标识发起的 注册过程中， HSS和 /或 S-CSCF获得通配路由标识， 可以是注册消息中携带 通配路由标识信息，例如：在 Register 消息携带 To 头域为 ！*!@huawei.com , 表示通配路由标识为对于所有域名为 huawei.com的用户满足后续路由条件， 又例如： 在 Register 消息携带 To 头域为 2878!*!， 表示通配路由标识为对于 所有 2878字段的会话满足后续路由条件， 即注册的域名用户标识就是通配用 户标识， 而如果注册的 i或名用户标识不是通配用户标识， 如 huawei.com或 destination@huawei.com , 则 HSS和 /或 S-CSCF也可以才艮据域名用户标识的注 册， 关联对应通配路由标识， 如通过管理配置配置某一域名用户标识对应的 路由通配条件等。
HSS 判断指向所述会话目的用户身份满足后续路由条件后， 为该会话请 求分配相关的 S-CSCF。 所述相关的 S-CSCF , 即为域名用户提供服务的 S- CSCF。
4、 HSS在 LIA消息中向 I-CSCF返回该 S-CSCF的信息；
5、 I-CSCF发送 INVITE请求至 HSS分配的 S-CSCF;
6、 S-CSCF按照 3GPP 24.229 中采用对于未注册用户的处理， 向 HSS发 送 SAR (服务器分配请求） 消息， 以主动请求下载用户相关数据；
SAR消息中包含本次会话的被叫用户标识： UnRegId@huawei.com。
7、 HSS根据 SAR 消息中携带的 UnRegId@huawei.com判定满足本地存储 的通配路由标识（同步骤 3中的相关内容）；
8、 通过 SAA (服务器分配请求响应） 消息下发路由信息至 S-CSCF; 所述路由信息中至少包括： 与 UnRegId@huawei.com满足的通配匹配条件 对应的域名用户标识或域名用户标识对应的路由集。
a )对于路由集包含域名用户标识的情况：
传递域名用户标识方法 1:
通过在 HSS下发的 Diameter协议消息中扩展一个新的 Diameter协 议 AVP (属性对）
Destination-ID ::= <AVP header: xxx 10415>
[U I]
其中 URI 中携带域名用户标识， 其取值可以为 TEL URI或者 SIP URI
如设置 URI 内容为 destination@huawei.com ，标识通知 S-CSCF使 用 destination@huawei.com对应的路由集作为本次会话的路由集。 传递域名用户标识方法 2:
HSS通过下发的 Public-Identification公共身份信息 （扩展后的公共 身份模型如图 8所示） 中携带域名用户标识， 进一步的， 为表明公 共身份信息中携带的标识为域名用户标识， 针对现有公共身份的 [identity type】属性增力口新的枚举类别， 如： Destination Route 类 别。 具体此类别的公有标识即认为是域名用户标识。
由于域名用户标识在 IMS网络中已经注册过， S-CSCF已经记录下它的注
会话。
b )对于路由信息中包含路由集的情况， HSS可以通过在 SAA消息中携 带扩展 Diameter AVP
Route-set：: = <AVP header: xxx 10415>
[P-addr]
[C-addr]
其中 p-addr标识用户接入的 P-CSCF地址， C-ADDR标识用户的联系地 址
使得 S-CSCF可以直接利用此 AVP中包含的路由地址， 作为本次会话的 路由集使用。
更为优化地， HSS还可以下发通配路由标识至 S-CSCF。 这样 S-CSCF再 次收到会话请求时， 即可先以通配路由标识判定被叫用户标识是否满足后续 路由条件， 再以所述域名用户标识对应的路由集对该会话请求进行路由从而 减少了 HSS同 S-CSCF之间的消息交互。
更为优化地， 为了使 S-CSCF在匹配被叫用户路由集的同时， 匹配该用户 对应的业务配置，可以通过扩展 Diameter AVP来传递附加指示，通知 S-CSCF 使用域名用户对应的业务配置文件（ Service profile )， 作为本次会话被叫用户 的业务配置文件进行后续处理。或者采用其他方法达到这一目，如：利用 Public identity属性 Wildcared PSI 字段携带通配路由标识，或设置 Public identity属 性 Identity为新枚举类型 如【 Route & Service】， 来指示 S-CSCF使用域名用 户对应的路由集以及业务配置文件作为本次会话的路由集以及业务配置文件 进行后续处理。
9、 S-CSCF根据 SAA消息中的路由信息， 获取与域名用户标识对应的路 由集， 作为本次会话的路由集； 或者直接以 HSS下发的路由集， 作为本次会 话的路由集；
此外， 可选的， 在步骤 4中， HSS也可以向 I-CSCF返回路由集， I-CSCF 将该路由集传递给 S-CSCF。
此外， 可选的， 在步骤 8中， HSS向 S-CSCF返回域名用户对应的业务 配置文件， 业务配置文件中包含了域名用户对应的路由集， S-CSCF执行业务 配置文件， 如 iFC (初始过滤规则）， 最后一个 iFC中对应的应用服务器名称 为域名用户对应的路由地址， S-CSCF以此作为本次会话的路由路径。
10、 以该路由集进行后续的路由处理；
所述会话请求被路由到域名用户即企业网后， 企业网内部再将该会话请 求路由到被叫用户， 从而实现企业网内部用户没有在 IMS网络进行注册时， 仍然可以根据企业网内部用户标识进行正确的会话路由。
方法实施例二、 HSS 在对域名用户标识注册时， 下发路由信息至为该域 名用户提供服务的 S-CSCF。 参见图 9所示， 包括下列具体步骤：
1、 S-CSCF .收到以域名用户标识发起的注册请求；
2、 S-CSCF使用 SAR 消息向 HSS进行注册， SAR 消息中携带有该域名 用户标识；
3、 HSS根据预置的信息对照所述域名用户标识， 从而判定该注册请求是 由域名用户发起；
为达到这一目的， 需要扩展 HSS上存储的 public identification公共身份 标识的属性，增加新的【 identity type】类另1 J，如增力新的类别【 destination route】 来标识此公有标识对应的用户标识为域名用户， 所谓域名用户即满足通配路 由标识的用户可以按照域名用户对应的路由集进行路由； 在 HSS上增加新的 类别 [wildcard URI】用于标识通配路由标识。
4、 HSS 下发通配路由标识至 S-CSCF;
可以在 SAA消息中携带扩展的 Diameter协议属性对 , 如
Matched-route ::= <AVP header: xxx 10415〉
[wildcared U I]
其中 wildcared URI 代表通配路由标识， 如可以设置 wildcared URI 为！* l@huawei.com， 标识所有对于域名为 huawei.com的用户标识， 当然也可 以采用其他方式来携带通配路由标识， 如使用图 8所示的公共身份中扩展的 【 Wildcared route】属性来携带。
此外， 可选的， 如方法实施例一步骤 3所述， S-CSCF也可以自己 居域 名用户标识的注册请求过程获得通配路由标识。
5、 当 S-CSCF收到一个初始会话请求， 如 INVITE消息时， 根据所述通 配路由标识进行判断， 对于满足条件的会话则按照域名用户标识对应的路由 集进行处理；
和方法实施例一类似的， S-CSCF判断会话请求中携带的被叫用户标识如 UnRegId@huawei.com , 和通配路由标识相匹配， 则获得域名用户标识对应的 注册路由路径， 以此路由会话请求； 或者处理域名用户标识对应的业务配置 文件， 如 iFC, 得到域名用户对应的路由地址， 以此路由会话请求。
所述后续会话请求被路由到域名用户即企业网后， 企业网内部再将该会 话请求路由到被叫用户， 从而实现企业网内部用户没有在 IMS网络进行注册
本方法实施例中， HSS向 S-CSCF下发路由匹配信息 （通配路由标识） 的时机不限于以域名用户标识发起注册的流程中， HSS 也可在其他过程中下 发路由匹配信息至 S-CSCF, 如： HSS在用户档案主动推送过程中携带路由匹 配信息， 则 HSS发送 PPR (档案推送请求消息）至 S-CSCF ， 该 PPR消息中 携带有路由匹配信息。
综上所述， 本发明实施例在域名用户在 IMS网络进行了注册（例如： 以 企业网标识在 IMS网络进行了注册）， 但域名相关用户 （如企业网内部用户） 没有在 IMS网络进行注册的前提下， 用户数据库收到位置查询请求时， 根据 路由匹配信息分配呼叫会话控制单元； 之后根据路由匹配信息对应获取本次 会话的路由集； 最后所述呼叫会话控制单元以该路由集路由本次会话。 从而 可以使得 IMS对于未注册用户进行 ^舌路由， 增强了 IMS网络的路由能力。
进一步， 所述用户数据库通过扩展 Diameter协议的属性对 AVP ， 向呼叫 会话控制单元传送所述路由匹配信息及域名用户路由集； 或者所述用户数据 库通过扩展公共身份信息， 向呼叫会话控制单元传送域名用户标识， 以及通 过扩展 Diameter协议的属性对 AVP , 向呼叫会话控制单元传送通配路由标 识； 或者所述用户数据库通过扩展 Diameter协议的属性对 AVP, 向呼叫会话 控制单元传送域名用户标识。
所述通配路由标识通过管理方式进行配置； 或由用户数据库才艮据域名用 户标识的注册上报信息获得； 或通过应用服务器进行配置。 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种路由会话的方法， 其特征在于， 包括下列步骤：
A、 获取通配路由标识；
B、 使用通配路由标识对应的路由集路由本次会话。
2、 如权利要求 1 所述的方法， 其特征在于， 所述获取通配路由标识的方 法为： 域名用户注册时， 数据库单元向呼叫会话控制单元发送通配路由标识， 所述通配路由标识对应的路由集为域名用户注册时对应的路由集。
3、 如权利要求 2所述的方法， 其特征在于， 呼叫会话控制单元保存通配 路由标识以及与之对应的域名用户标识或域名用户对应路由集。
4、 如权利要求 2或 3所述的方法， 其特征在于， 所述步骤 B前还包括下 列步骤：
用户数据库分配为通配路由标识对应的域名用户服务的呼叫会话控制单 元。
5、 如权利要求 1或 2所述的方法， 其特征在于， 所述使用通配路由标识 对应的路由集路由本次会话包括下列步骤：
在呼叫会话控制单元收到会话请求后， 以通配路由标识对所述会话请求 中的用户标识进行匹配， 当满足任一通配路由标识时， 呼叫会话控制单元使 用与所述匹配到的通配路由标识对应的域名用户的路由集， 作为本次会话的 路由集路由本次会话。
6、 如权利要求 2 所述的方法， 其特征在于， 所述用户数据库通过扩展 Diameter协议的属性对 AVP ， 向呼叫会话控制单元传送所述通配路由标识及 域名用户路.由集； 或者
所述用户数据库通过扩展公共身份信息， 向呼叫会话控制单元传送域名 用户标识或匹配路由标识， 以及通过扩展 Diameter协议的属^对 AVP ， 向呼 叫会话控制单元传送通配路由标识； 或者
所述用户数据库通过扩展 Diameter协议的属性对 AVP, 向呼叫会话控制 单元传送域名用户标识。
7、 如权利要求 6所述的方法， 其特征在于， 所述通配路由标识通过管理 方式进行配置； 或由用户数据库根据域名用户标识的注册上报信息获得； 或 通过应用服务器进行配置。
8、 如权利要求 2或 6所述的方法， 其特征在于， 所述用户数据库通过新 增身份标识类别用于保存或标识通配路由标识； 或者，
通过扩展公共身份标识类别保存或标识通配路由标识。
9、 如权利要求 2或 3所述的方法， 其特征在于， 所述呼叫会话控制单元 通过新增身份标识类别保存或标识通配路由标识； 或者，
通过扩展公共身份标识类别保存或标识通配路由标识。
10、 一种路由会话的网络， 其特征在于， 包括：
呼叫会话控制单元， 用于根据路由集路由会话；
存储单元， 用于存储路由匹配信息；
用户数据库， 用于在收到位置查询请求时， 分配对应的呼叫会话控制单
7L;
路由集获取单元， 用于根据路由匹配信息， 获取本次会话的路由集。
11、 如权利要求 10所述的网络， 其特征在于， 所述路由集获取单元中包 括：
通配路由标识判断子单元， 用于以存储单元存储的路由匹配信息中的通 配路由标识， 对所述会话请求中的被叫用户标识进行匹配；
获取子单元， 用于获取与通配路由标识判断子单元匹配到的通配路由标 识相应的路由集。
12、 一种用户数据库， 其特征在于， 包括：
存储单元， 用于存储路由匹配信息；
分配单元， 用于在收到位置查询请求时， 根据存储单元存储的路由匹配 信息， 分配呼叫会话控制单元。
13、 如权利要求 12所述的用户数据库， 其特征在于， 所述数据库还包括 路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对应获取本次会 话的域名用户标识或域名用户路由集， 并告知呼叫会话控制单元。
14、 如权利要求 12所述的用户数据库， 其特征在于， 所述分配单元使用 位置查询请求中的目的身份， 匹配通配路由标识， 并分配相应的呼叫会话控 制单元。
15、 如权利要求 12所述的用户数据库， 其特征在于， 所述路由集获取单 元中包括：
通配路由标识判断子单元， 用于以存储单元存储的路由匹配信息中的通 配路由标识， 对所述会话请求中的被叫用户标识进行匹配；
获取子单元， 用于获取与通配路由标识判断子单元匹配到的通配路由标 识相应的路由集。
16、 一种呼叫会话控制单元， 其特征在于， 包括：
存储单元， 用于存储路由匹配信息；
路由集获取单元， 用于根据存储单元存储的路由匹配信息， 对应获取本 次会话的路由集， 并告知路由单元；
路由单元， 用于根据路由集获取单元获取的路由集， 路由会话。
17、 如权利要求 16所述的呼叫会话控制单元， 其特征在于， 所述路由集 获取单元中包括：
通配路由标识判断子单元， 用于以存储单元存储的路由匹配信息中的通 配路由标识， 对所述会话请求中的被叫用户标识进行匹配；
获取子单元， 用于获取与通配路由标识判断子单元匹配到的通配路由标 识相应的路由集。
PCT/CN2007/003448 2006-12-08 2007-12-05 A method, network and device of routing session Ceased WO2008067728A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07845809A EP2091186A4 (en) 2006-12-08 2007-12-05 PROCEDURE, NETWORK AND INSTALLATION FOR MEETING ROUTES
US12/480,380 US20090245240A1 (en) 2006-12-08 2009-06-08 Method, network and apparatus for routing sessions

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610153110.7A CN101197806B (zh) 2006-12-08 2006-12-08 一种路由会话的方法、网络及设备
CN200610153110.7 2006-12-08

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/480,380 Continuation US20090245240A1 (en) 2006-12-08 2009-06-08 Method, network and apparatus for routing sessions

Publications (1)

Publication Number Publication Date
WO2008067728A1 true WO2008067728A1 (en) 2008-06-12

Family

ID=39491660

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/003448 Ceased WO2008067728A1 (en) 2006-12-08 2007-12-05 A method, network and device of routing session

Country Status (4)

Country Link
US (1) US20090245240A1 (zh)
EP (1) EP2091186A4 (zh)
CN (1) CN101197806B (zh)
WO (1) WO2008067728A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8451841B2 (en) 2009-12-28 2013-05-28 At&T Intellectual Property I, L.P. Method and apparatus for processing a call to an aggregate endpoint device
US8793388B2 (en) * 2009-12-28 2014-07-29 At&T Intellectual Property I, L.P. Method and apparatus for processing a call to an aggregate endpoint device
EP2583428B1 (en) * 2010-06-18 2014-06-25 Telefonaktiebolaget LM Ericsson (publ) Methods and apparatuses for handling public identities in an internet protocol multimedia subsystem network
US9401962B2 (en) * 2010-10-28 2016-07-26 Verizon Patent And Licensing Inc. Traffic steering system
WO2012107082A1 (en) * 2011-02-08 2012-08-16 Telefonaktiebolaget L M Ericsson (Publ) Methods and apparatuses for handling public identities in an internet protocol multimedia subsystem network
EP2500856A1 (en) * 2011-03-15 2012-09-19 Amadeus S.A.S. Method and system for providing a session involving a plurality of software applications
WO2012106888A1 (zh) * 2011-07-14 2012-08-16 华为技术有限公司 一种实现跨域信息处理的方法和系统
US10123302B2 (en) * 2012-07-20 2018-11-06 Nec Corporation Paging control apparatus, paging method, wireless terminal, and non-transitory computer-readable medium
US9525848B2 (en) * 2014-05-30 2016-12-20 Highfive Technologies, Inc. Domain trusted video network
US9894182B2 (en) * 2015-11-10 2018-02-13 Alcatel Lucent Extensions to standard diameter routing
WO2020025997A1 (en) * 2018-07-30 2020-02-06 Telefonaktiebolaget Lm Ericsson (Publ) Internet protocol (ip) multimedia subsystem (ims) routing
EP4009602B1 (en) * 2020-12-07 2022-11-09 Siemens Healthcare GmbH Providing a first digital certificate and a dns response

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030021238A1 (en) * 2001-07-03 2003-01-30 Knut Snorre Bach Corneliussen Conference as virtual users in multi media network
CN1398103A (zh) * 2001-04-03 2003-02-19 阿尔卡塔尔公司 使用会话启动协议消息中的信息的呼叫路由选择
CN1778086A (zh) * 2003-02-19 2006-05-24 诺基亚公司 通过ims系统路由消息
CN1874217A (zh) * 2005-09-27 2006-12-06 华为技术有限公司 一种确定路由的方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6917612B2 (en) * 2000-09-01 2005-07-12 Telefonaktiebolaged L M Ericsson System and method for address resolution in internet protocol (IP)-based networks
FI20010018A7 (fi) * 2001-01-05 2002-07-06 Nokia Corp Tilaajalle soitetun puhelun reitittäminen
GB0306830D0 (en) * 2003-03-25 2003-04-30 Nokia Corp Routing messages
US8817772B2 (en) * 2003-07-02 2014-08-26 Nokia Corporation Function mode routing
DE602005015864D1 (de) * 2004-08-11 2009-09-17 Ericsson Telefon Ab L M Bereitstellung von identitäten eines öffentlichen dienstes
FI20045298A0 (fi) * 2004-08-16 2004-08-16 Nokia Corp Mediapalvelun reititys
CN100531194C (zh) * 2004-09-07 2009-08-19 华为技术有限公司 分组域业务信号处理系统及其方法
US7453876B2 (en) * 2004-09-30 2008-11-18 Lucent Technologies Inc. Method and apparatus for providing distributed SLF routing capability in an internet multimedia subsystem (IMS) network
BRPI0520466B8 (pt) * 2005-08-12 2019-06-18 Ericsson Telefon Ab L M servidor de assinante doméstico para manter identidades de serviço público em uma rede, entidade de serviço passível de ser designada para tratar um serviço, entidade de roteamento para rotear uma invocação de um serviço, e, método para invocar um serviço identificado através de uma identidade de serviço público em uma rede
CN100502402C (zh) * 2005-08-19 2009-06-17 华为技术有限公司 一种在ims网络中处理会话消息的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1398103A (zh) * 2001-04-03 2003-02-19 阿尔卡塔尔公司 使用会话启动协议消息中的信息的呼叫路由选择
US20030021238A1 (en) * 2001-07-03 2003-01-30 Knut Snorre Bach Corneliussen Conference as virtual users in multi media network
CN1778086A (zh) * 2003-02-19 2006-05-24 诺基亚公司 通过ims系统路由消息
CN1874217A (zh) * 2005-09-27 2006-12-06 华为技术有限公司 一种确定路由的方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN101197806B (zh) 2012-04-18
US20090245240A1 (en) 2009-10-01
CN101197806A (zh) 2008-06-11
EP2091186A1 (en) 2009-08-19
EP2091186A4 (en) 2012-04-18

Similar Documents

Publication Publication Date Title
WO2008067728A1 (en) A method, network and device of routing session
US8300629B2 (en) Device and method for providing interaction management for communication networks
CN101185305B (zh) Ip多媒体子系统(ims)中的呼叫前转
TWI375443B (en) Message handling in an ip multimedia subsystem
US8693312B2 (en) Method, system and device for processing registration exception in user registration procedure
CN101160808B (zh) 一种ip多媒体子系统中用户注册触发实现方法
WO2007093124A1 (en) The method and system of multimedia resource scheduling
WO2005069645A1 (en) A method for reducing interface load of home subscriber server
US20120155333A1 (en) Appratus and method for lawful interception
CN101345750A (zh) 各服务通信控制装置、系统及方法
WO2006099815A1 (en) A method for implementing the user registering in the ip multimedia subsystem and the system thereof
CN101690084B (zh) 通信网络中的接入域选择
CN101212323B (zh) Ims网络为群用户提供服务的方法和系统
JP2010527170A (ja) Ｉｐマルチメディアサブシステムにおけるユーザｉｄの処理
CN101489266B (zh) 一种基于签约数据的ims用户级控制方法及系统
WO2007090348A1 (en) A method, apparatus and system for checking the validity for globally routable user agent uri
CN101383817B (zh) 控制访问非sip业务方法及系统、服务注册中心
KR100703426B1 (ko) 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 발신 및 착신 호를 가능하게 하는 방법 및 장치
CN100583837C (zh) 一种基于ims的业务实现方法
KR20100003869A (ko) 라우팅 장치 및 라우팅 방법
WO2008080349A1 (en) User device, service call session control function entity and registration method of user device
CN101494890A (zh) 一种路由会话的方法、网络及设备
KR20060033407A (ko) 아이피 기반 멀티미디어 서브시스템에서 가입자 정보유실시 착신호를 가능하게 하는 방법
CN1941774B (zh) 在网络中实现公共用户标识携带的方法及系统
CN101132394A (zh) 确定服务用户方向的方法

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: 07845809

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007845809

Country of ref document: EP