WO2012013029A1 - 一种实现不同类型业务嵌套的方法和系统 - Google Patents

一种实现不同类型业务嵌套的方法和系统 Download PDF

Info

Publication number
WO2012013029A1
WO2012013029A1 PCT/CN2011/070740 CN2011070740W WO2012013029A1 WO 2012013029 A1 WO2012013029 A1 WO 2012013029A1 CN 2011070740 W CN2011070740 W CN 2011070740W WO 2012013029 A1 WO2012013029 A1 WO 2012013029A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
application server
server
core network
proxy server
Prior art date
Application number
PCT/CN2011/070740
Other languages
English (en)
French (fr)
Inventor
韩银俊
张国炳
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP11811731.6A priority Critical patent/EP2600590B1/en
Publication of WO2012013029A1 publication Critical patent/WO2012013029A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1096Supplementary features, e.g. call forwarding or call holding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1101Session protocols
    • H04L65/1104Session initiation protocol [SIP]

Definitions

  • the present invention relates to a multi-service nesting technique in a communication network, and more particularly to a method and system for implementing nesting of different types of services. Background technique
  • the intelligent network is developed on the basis of the existing telephone network, and refers to a telephone network or an integrated service digital network with intelligent functions, and its network intelligence is configured on several service control points distributed in the whole network, and Network intelligence is controlled by software to provide more flexible intelligent control functions.
  • the intelligent network does not need to modify the end office and the switch when adding new services, and the telecom company personnel and even the users themselves can modify the software to achieve the purpose of providing new services at any time. Since the development of the intelligent network in the 1990s, after more than ten years of development, it has been very mature and stable.
  • the applications of the intelligent network include: fixed intelligent network service, mobile intelligent network service, integrated intelligent network service; among them, fixed intelligent network services, such as: called centralized payment service, automatic accounting card service, mass call service, and advertising telephone service, etc.
  • Mobile intelligent network services mainly refer to mobile intelligent network services in the Global System for Mobile Communications (GSM) and Code Division Multiple Access (CDMA) systems, such as: prepaid services, mobile virtual Private network services and time-sharing services; integrated intelligent network can support Intelligent Network Application Protocol (INAP), Customized Applications for Mobile Network Enhanced Logic (CAMEL) and wireless intelligent network (WIN, Wireless Intelligent Network) specification, integrated intelligent network services can cover fixed telephone network, GSM network and CDMA network.
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • INP Intelligent Network Application Protocol
  • CAMEL Customized Applications for Mobile Network Enhanced Logic
  • WIN, Wireless Intelligent Network Wireless Intelligent Network
  • IP IP Multimedia Subsystem
  • SIP Session Initiation Protocol
  • the main object of the present invention is to provide a method and system for implementing different types of service nesting, which can add new service capabilities while network upgrade does not affect existing network services.
  • a method for implementing different types of service nesting includes: the core network sends an INVITE message to the service proxy server according to the subscription information of the user, and initiates a service trigger; the service proxy server triggers according to the received INVITE message and the preset configuration information. a first application server of a service type, and triggering a second application service of another service type according to an event request message sent by the application server and/or the INVITE message sent by the core network, and the configuration information Server.
  • the first application server is an application server that carries an application enhancement logic (CAMEL) service
  • the second application server is an application server that carries a Session Initiation Protocol (SIP) service
  • the service proxy server is according to the first application.
  • the event request message sent by the server, and/or the INVITE message sent by the core network, and the preset configuration information trigger the second application server of the other service type, as: when the service proxy server generates the InitialDP message to trigger the first application that carries the CAMEL service.
  • the server sends the charging request message to the service proxy server according to its own business logic; the service proxy server according to the charging request message and/or the INVITE message sent by the core network, and the preset configuration information, Generating an INVITE message to trigger a second application server that carries the SIP service; or
  • the first application server is an application server that carries the SIP service
  • the second application server is an application server that carries the CAMEL service
  • the service proxy server when the service proxy server generates an INVITE message to trigger the first application server that carries the SIP service, the first application server Sending an INVITE call request message to the service proxy server according to its own service logic; the service proxy server generates an InitialDP message to trigger the bearer CAMEL service according to the INVITE call request message and/or the INVITE message sent by the core network, and the preset configuration information.
  • the second application server when the service proxy server generates an INVITE message to trigger the first application server that carries the SIP service, the first application server Sending an INVITE call request message to the service proxy server according to its own service logic; the service proxy server generates an InitialDP message to trigger the bearer CAMEL service according to the INVITE call request message and/or the INVITE message sent by the core network, and the preset configuration information.
  • the second application server when the service
  • the second application server After the first application server and the second application server are triggered, the second application server sends an INVITE call request message to the core network through the service proxy server to request to call the called user.
  • the method further includes: after the called user rings, the core network transmits the ringing response to the second application server through the service proxy server; the second application server sends the ringing response to the core network through the service proxy server, and notifies The calling user is called the user is ringing.
  • the method further includes: after the called user answers, the core network transmits the response response to the second application server through the service proxy server; the second application server reports the called user response event to the first application server, and passes the response response
  • the service proxy server sends to the core network, It is known that the calling user is responding to the called user; the service proxy server reports the charging event report to the first application server.
  • the method further includes: after the called user hangs up, the core network sends the BYE request to the second application server through the service proxy server; the second application server sends a BYE request to the core network through the service proxy server, requesting to end the session of the calling user;
  • the service proxy server reports the charging event report and the called user on-hook event to the first application server; the first application server sends a call release indication to the service proxy server.
  • a system for implementing nesting of different types of services including:
  • the core network is configured to send an INVITE message to the service proxy server according to the subscription information of the user, and initiate a service trigger;
  • a service proxy server configured between the core network and the application server, configured to trigger a first application server of a service type according to the received INVITE message and the preset configuration information, and according to the event request sent by the application server
  • the message and/or the INVITE message sent by the core network, and the configuration information triggers a second application server of another service type; and the one or more application servers are configured to trigger the corresponding service according to the trigger message of the service proxy server, and send the corresponding service to the service proxy server.
  • Event request message configured between the core network and the application server, configured to trigger a first application server of a service type according to the received INVITE message and the preset configuration information, and according to the event request sent by the application server
  • the message and/or the INVITE message sent by the core network, and the configuration information triggers a second application server of another service type
  • the one or more application servers are configured to trigger the corresponding service according to the trigger message of the service proxy server, and send the corresponding service to the service proxy server.
  • the first application server is an application server that carries the CAMEL service
  • the second application server is an application server that carries the SIP service
  • the service proxy server is further configured to receive the INVITE call request sent by the second application server, and The INVITE call request is sent to the core network to request a call to the called user.
  • the service proxy server is further configured to receive a ringing response sent by the core network after the called user rings, and transmit the ringing response to the second application server; and further configured to receive the vibration sent by the second application server.
  • the bell responds, and sends the ringing response to the core network, notifying the calling user that the called user is ringing; after the called user answers, receiving the response sent by the core network, and transmitting the response to the second response Application server; also set to receive the second application server Sending a response response, and sending the response response to the core network, informing the calling user that the called user answers; and setting the report to report the charging event to the first application server.
  • the service proxy server is further configured to receive the BYE request sent by the second application server after the called user hangs up, and send the BYE request to the core network to notify the called user that the called user hangs up;
  • An application server reports an on-hook event and receives a call release indication sent by the first application server.
  • the method and system of the present invention have the advantages that: the information exchange between the core network and the application server can be realized by using the service proxy server, and the original service and the new service are realized without affecting the existing network service.
  • the business nesting of the added services solves the drawbacks of the existing network when the new network is added, which is beneficial to the stability and maintenance of the existing network.
  • FIG. 1 is a schematic structural diagram of a system for implementing different types of service nesting according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for implementing different types of service nesting according to an embodiment of the present invention. detailed description
  • the core network sends an INVITE message to the service proxy server according to the subscription information of the user, and initiates a service trigger; the service proxy server triggers the first type of the service type according to the received INVITE message and the preset configuration information.
  • the application server further triggers a second application server of another service type according to the request event message sent by the application server and/or the INVITE message sent by the core network, and the configuration information.
  • the present invention uses a softswitch network as a core network, an application server (AS, Application Server) as an intelligent network application server, and a core network and an application server.
  • AS Application Server
  • the service proxy server accesses the INVITE message sent by the core network, triggers an application server of a service according to the service type and trigger sequence triggered in the configuration information, and the triggered application server may be referred to as the first application.
  • the application server may be referred to as the second application server.
  • the service proxy server is equivalent to the application server; on the application server side, the service proxy server represents the core network.
  • the method for implementing different types of service nesting in the embodiment of the present invention includes the following steps:
  • Step 201 The core network sends an INVITE message to the service proxy server according to the subscription information of the user, and initiates a service trigger.
  • the INVITE message may be a CAMEL message or a SIP message, where the INVITE message includes the calling and called number.
  • Step 202 The service proxy server triggers an application server AS1 of a service type according to the received INVITE message and the preset configuration information.
  • the configuration information may include: a triggered service type, a triggering sequence, a triggering manner, an application server address, and the like; the service proxy server according to the calling and called number and the configuration information in the INVITE message, according to the triggering sequence Trigger an application type AS1 of a service type.
  • Step 203 AS1 sends an event request message to the service proxy server according to its own business logic.
  • the event request message is an accounting request message, including: a monitoring event (RRBE), an application charging event (AC), a connection event (Connect), and a continuation event. (Continue), etc.; if AS1 is an application server that carries SIP services, the event request message is an INVITE call request message.
  • Step 204 The service proxy server triggers the application server AS2 of another service type according to the event request message sent by the AS1 and/or the INVITE message sent by the core network and the configuration information.
  • AS1 is an application server that carries the CAMEL service
  • the service agent The server triggers other types of application servers according to the configuration information and the connection number sent by AS1, and/or the INVITE message sent by the core network in the trigger sequence.
  • the original service is a CAMEL service
  • the newly added service is a SIP service
  • the service proxy server can access the INVEL message, trigger the original CAMEL service, and trigger the newly added according to the configuration information of the service agent.
  • the SIP service is used to complete the nesting of the CAMEL service and the SIP service.
  • the AS1 is an application server that carries the CAMEL service
  • the AS2 is an application server that carries the SIP service.
  • Step 301 The core network sends an INVITE message to the service proxy server according to the subscription information of the user to initiate a service trigger, and the service proxy server replies with a temporary response to the core network. ;
  • Step 302 The service proxy server generates a trigger message according to the preset configuration information.
  • the initial DP message is sent to the AS1 carrying the CAMEL service, and the CAMEL service is triggered.
  • the configuration information preset by the service proxy server includes: Service type, triggering sequence, triggering mode, application server address, etc.
  • the service proxy server obtains information such as the service type, the triggering mode, and the application server address to be triggered in the configuration information according to the user attribute in the INVITE message, and triggers according to the trigger.
  • the InitialDP message that generates the CAMEL specification is sent to the AS1, and the AS1 carrying the CAMEL service is triggered.
  • Step 303 The AS1 sends an accounting request message to the service proxy server according to its own service logic, requesting charging.
  • the accounting request message sent by the AS1 to the service proxy server includes: a monitoring event, an application charging event, a connection event, and a continuation event.
  • Step 304 The service proxy server generates an INVITE message and sends the INVITE message to the bearer SIP service according to the configuration information and the charging request message sent by AS1 and/or the INVITE message sent by the core network.
  • AS2 triggering SIP service;
  • AS2 replies with 100 temporary response to the service proxy server;
  • the service proxy server obtains the configuration information corresponding to the connection number according to the connection number in the sending request event message of the AS1 and/or the INVITE message sent by the core network, and triggers the SIP service.
  • Step 305 The AS2 sends an INVITE call request message to the service proxy server according to its own service logic, and the service proxy server replies with a temporary response to the AS2.
  • AS2 sends an INVITE call request message to the service proxy server, requesting the service proxy server to call the called user; after receiving the INVITE call request message, the service proxy server replies with a temporary response to AS2.
  • Step 306 The service proxy server sends an INVITE call request message to the core network to request to call the called user. After receiving the INVITE call request message, the core network replies with a temporary response. Step 307: After the called user rings, the core network gives The service proxy server replies with a 180 ringing response, and the service proxy server transmits a 180 ringing response to the AS2;
  • Step 308 AS2 sends a 180 ringing response to the service proxy server, and the service proxy server transmits a 180 ringing response to the core network, informing the calling user that the called user is ringing;
  • Step 309 The called user answers, the core network replies with a response response to the service proxy server, and the service proxy server replies to the core network with a confirmation message ACK;
  • Step 310 The service proxy server transmits a 200 response response to the AS2, and the AS2 replies to the service proxy server with a confirmation message ACK;
  • Step 311 The AS2 sends a response response to the service proxy server, and the service proxy server sends a confirmation message ACK to the AS2, and reports the called user response event to the AS1.
  • Step 312 The service proxy server sends a 200 response response to the core network, notifying the calling user that the called user is answering; the core network returns a confirmation message ACK to the service proxy server;
  • Step 313 The service proxy server reports the charging event report to the AS1.
  • Step 314 If the call is still continuing, AS1 continues to send billing to the service proxy server. Request a message, request billing;
  • Step 315 The called user hangs up, the core network sends a BYE request to the service proxy server, and the service proxy server sends the BYE request to the AS2;
  • Step 316 AS2 replies to the service agent BY server with a 200 OK response of the BYE, and the service agent replies to the core network with a 200 OK response of the BYE;
  • Step 317 The AS2 sends a BYE request to the service proxy server to terminate the session of the calling user, and the service proxy server replies to the AS2 with a 200 OK response of the BYE.
  • Step 318 The service proxy server reports the charging event report and the called user's on-hook event to the AS1; the AS1 sends a call release indication to the service proxy server;
  • Step 319 The service proxy server sends a BYE request to the core network, and releases the session of the calling user.
  • Step 320 The core network replies to the service proxy server with a response of the BYE request.
  • steps 302-304 are specifically:
  • the service proxy server generates an INVITE message to trigger the AS1 carrying the SIP service; the AS1 sends an INVITE call request message to the service proxy server according to its own service logic; the service proxy server according to the INVITE call request message and/or the INVITE message sent by the core network, And the preset configuration information, generate an InitialDP message to trigger AS2 that carries the CAMEL service.
  • AS1 is an application server that carries SIP services
  • AS2 is an application server that carries CAMEL services.
  • the present invention further provides a system for implementing different types of service nesting.
  • the present invention includes: a core network, a service proxy server, and more than one application server;
  • the core network is configured to send an INVITE message to the service proxy server according to the subscription information of the user, and initiate a service trigger.
  • a service proxy server configured between the core network and the application server, configured to trigger a first application server of a service type according to the received INVITE message and preset configuration information, and further send according to the triggered application server An event request message and/or an INVITE message sent by the core network, and the configuration information, triggering a second application server of another service type;
  • the application server is configured to trigger a corresponding service according to the trigger message of the service proxy server, and send an event request message to the service proxy server.
  • the first application server is an application server that carries a CAMEL service
  • the second application server is an application server that carries a SIP service
  • the service proxy server is further configured to receive an INVITE call request message sent by the AS2, and send the INVITE call request message to the core network to request to call the called user.
  • the service proxy server is further configured to: after receiving the ringing of the called user, receive a ringing response sent by the core network, and transmit the ringing response to the AS2; further configured to receive a ringing response sent by the AS2, and The ringing response is sent to the core network to notify the calling user that the called user is ringing.
  • the service proxy server is further configured to: after receiving the response from the called user, receive an response sent by the core network, and transmit the response to the AS2; and further, receive the response sent by the AS2, and send the response response.
  • the core network is notified to the called user that the called user answers; and is further used to report the charging event report to AS1.
  • the service proxy server is further configured to: after receiving the hang-up, the called user receives the BYE request sent by the AS2, and sends the BYE request to the core network to notify the called user that the called user hangs up; and is also used to report the hang-up event to the AS1. And receive the call release indication sent by AS1.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种实现不同类型业^^套的方法和系统 技术领域
本发明涉及通信网络中多业务嵌套技术, 特别是一种实现不同类型业 务嵌套的方法和系统。 背景技术
智能网是在现有电话网的基础上发展而来的, 是指具有智能功能的电 话网或综合业务数字网, 它的网络智能配置于分布在全网中的若干个业务 控制点上, 并由软件实现网络智能的控制, 以提供更为灵活的智能控制功 能。 智能网在增加新业务时不用改造端局和交换机, 而由电信公司人员甚 至用户自己修改软件就能达到随时提供新业务的目的。 智能网从上世纪 90 年代发展至今, 经过了十几年的发展, 目前已经非常成熟和稳定。
智能网的应用包括: 固定智能网业务、 移动智能网业务、 综合智能网 业务; 其中, 固定智能网业务, 如: 被叫集中付费业务、 自动记账卡业务、 大众呼叫业务以及广告电话业务等; 移动智能网业务, 主要指全球移动通 信系统 (GSM , Global System for Mobile Communications ) 与码分多址 ( CDMA, Code Division Multiple Access ) 系统中的移动智能网业务, 如: 预付费业务、 移动虚拟专用网业务以及分时分区业务等; 综合智能网能同 时支持智能网应用协议 ( INAP , Intelligent Network Application Protocol )、 移动网络定制应用增强逻辑( CAMEL , Customized Applications for Mobile network Enhanced Logic ) 和无线智能网络 ( WIN , Wireless Intelligent Network )规范, 综合智能网业务可以覆盖固定电话网, GSM网和 CDMA 网。
目前, 在现有的智能网架构下, 一个用户在同一时刻只能触发一个业 务, 这就限制了一个用户同时签约多个业务的可能性。 如果需要实现多个 业务, 就必须将多个业务逻辑放在一个业务中实现, 极大的限制了智能网 业务的开展; 另一方面, 在现有的智能网业务开展得很成熟时, 如果需要 在现有的业务上添加新的功能, 不得不对现有的业务进行改进, 运营商需 要对现有业务付出昂贵的业务维护费用, 同时也影响了智能网业务的稳定 性。
为了支持更多的业务功能, 业务和控制相分离, 控制和承载相分离, 是电信 IP化发展的趋势。 底层的固定和移动的核心网正在升级改造, 并改 造为基于 IP的软交换(SS, Soft Switch )网络、 或 IP多媒体子系统( IMS, IP Multimedia Subsystem ) ,应用层的智能网应用服务器也逐渐被具有会话起 始协议( SIP, Session Initiation Protocol )接入功能的应用服务器所取代。
但是, 网络的升级改造必然会对原有的网络用户形成冲击, 因此, 必 须解决好以下几个问题: 第一, 在网络升级的同时, 保持原有网络的业务 能力, 保护原有的网络投资; 第二, 为原有网络用户开放新的业务能力时, 能与原有的业务相兼容。 但是, 现有技术还没有能有效解决上述问题的技 术方案。 发明内容
有鉴于此, 本发明的主要目的在于提供一种实现不同类型业务嵌套的 方法和系统, 能在网络升级不影响现有网络业务的同时增添新的业务能力。
为解决上述技术问题, 本发明的技术方案是这样实现的:
一种实现不同类型业务嵌套的方法, 包括: 核心网根据用户的签约信 息向业务代理服务器发送 INVITE消息,发起业务触发; 业务代理服务器根 据所接收到的 INVITE 消息和预先设置的配置信息触发一种业务类型的第 一应用服务器, 并根据所述应用服务器发送的事件请求消息和 /或核心网发 送的所述 INVITE消息、以及所述配置信息触发其他业务类型的第二应用服 务器。
所述第一应用服务器为承载应用增强逻辑(CAMEL )业务的应用服务 器, 所述第二应用服务器为承载会话起始协议(SIP )业务的应用服务器; 所述业务代理服务器根据所述第一应用服务器发送的事件请求消息、 和 /或 核心网发送的 INVITE消息、以及预先设置的配置信息触发其他业务类型的 第二应用服务器, 为: 当业务代理服务器生成 InitialDP 消息触发承载 CAMEL业务的第一应用服务器时, 第一应用服务器根据自身的业务逻辑, 向业务代理服务器发送计费请求消息; 业务代理服务器根据计费请求消息 和 /或核心网发送的所述 INVITE 消息、 以及预先设置的配置信息, 生成 INVITE消息触发承载 SIP业务的第二应用服务器; 或者,
所述第一应用服务器为承载 SIP 业务的应用服务器, 所述第二应用服 务器为承载 CAMEL 业务的应用服务器; 当业务代理服务器生成 INVITE 消息触发承载 SIP 业务的第一应用服务器时, 第一应用服务器根据自身的 业务逻辑, 向业务代理服务器发送 INVITE呼叫请求消息; 业务代理服务器 根据所述 INVITE呼叫请求消息和 /或核心网发送的 INVITE消息、 以及预 先设置的配置信息, 生成 InitialDP消息触发承载 CAMEL业务的第二应用 服务器。
第一应用服务器和第二应用服务器被触发后, 第二应用服务器通过业 务代理服务器向核心网发送 INVITE呼叫请求消息, 请求呼叫被叫用户。
该方法还包括: 被叫用户振铃后, 核心网将振铃响应通过业务代理服 务器传递给第二应用服务器; 第二应用服务器再将所述振铃响应通过业务 代理服务器发送给核心网, 通知主叫用户被叫用户正在振铃。
该方法还包括: 被叫用户应答后, 核心网将应答响应通过业务代理服 务器传递给第二应用服务器; 第二应用服务器向第一应用服务器上报被叫 用户应答事件, 并将所述应答响应通过业务代理服务器发送给核心网, 通 知主叫用户被叫用户正在应答; 业务代理服务器向第一应用服务器上报计 费事件报告。
该方法还包括: 被叫用户挂机后, 核心网通过业务代理服务器将 BYE 请求发送给第二应用服务器; 第二应用服务器通过业务代理服务器向核心 网发送 BYE请求, 请求结束主叫用户的会话; 业务代理服务器向第一应用 服务器上报计费事件报告、 以及被叫用户挂机事件; 第一应用服务器向业 务代理服务器发送呼叫释放指示。
一种实现不同类型业务嵌套的系统, 包括:
核心网, 设置为根据用户的签约信息向业务代理服务器发送 INVITE 消息, 发起业务触发;
业务代理服务器, 设置于核心网和应用服务器之间, 设置为根据所接 收到的 INVITE 消息和预先设置的配置信息触发一种业务类型的第一应用 服务器, 并根据所述应用服务器发送的事件请求消息和 /或核心网发送的 INVITE消息、 以及所述配置信息触发其他业务类型的第二应用服务器; 一个以上应用服务器, 设置为根据业务代理服务器的触发消息触发相 应业务, 并向业务代理服务器发送事件请求消息。
所述第一应用服务器为承载 CAMEL业务的应用服务器, 所述第二应 用服务器为承载 SIP 业务的应用服务器; 所述业务代理服务器, 还设置为 接收第二应用服务器发送的 INVITE呼叫请求,并将所述 INVITE呼叫请求 发送给核心网, 请求呼叫被叫用户。
所述业务代理服务器, 还设置为被叫用户振铃后, 接收核心网发送的 振铃响应, 并将所述振铃响应传递给第二应用服务器; 还设置为接收第二 应用服务器发送的振铃响应, 并将所述振铃响应发送给核心网, 通知主叫 用户被叫用户正在振铃; 被叫用户应答后, 接收核心网发送的应答响应, 并将所述应答响应传递给第二应用服务器; 还设置为接收第二应用服务器 发送的应答响应, 并将所述应答响应发送给核心网, 通知主叫用户被叫用 户应答; 并设置为向第一应用服务器上报计费事件报告。
所述业务代理服务器, 还设置为被叫用户挂机后, 接收第二应用服务 器发送的 BYE请求, 并将所述 BYE请求发送给核心网, 通知主叫用户被 叫用户挂机; 还设置为向第一应用服务器上报挂机事件, 并接收第一应用 服务器发送的呼叫释放指示。
釆用本发明所述的方法和系统, 其优点在于: 能利用业务代理服务器 实现核心网和应用服务器之间的信息交互, 在不影响现有网络业务的情况 下, 实现了原有业务和新增业务的业务嵌套, 解决了现有网络增加新业务 时必须修改原有业务的弊端, 有利于现有网络的稳定和维护。 附图说明
图 1为本发明实施例中实现不同类型业务嵌套的系统组成结构示意图; 图 2为本发明实施例中实现不同类型业务嵌套的方法流程图。 具体实施方式
本发明的基本思想是: 核心网根据用户的签约信息向业务代理服务器 发送 INVITE消息,发起业务触发;业务代理服务器根据所接收到的 INVITE 消息和预先设置的配置信息触发一种业务类型的第一应用服务器, 并进一 步根据所述应用服务器发送的请求事件消息和 /或核心网发送的 INVITE消 息、 以及所述配置信息触发其他业务类型的第二应用服务器。
如图 1 所示, 在实现不同类型业务嵌套的系统中, 本发明将软交换网 络作为核心网, 将应用服务器(AS, Application Server )作为智能网应用服 务器, 并在核心网和应用服务器之间设置业务代理服务器。 业务代理服务 器通过核心网发送的 INVITE消息接入,根据配置信息中触发的业务类型和 触发顺序触发一种业务的应用服务器, 所触发的应用服务器可称为第一应 用服务器; 再根据第一应用服务器发送的事件请求消息和 /或 INVITE消息、 以及配置信息触发新加入的其他业务的应用服务器, 此应用服务器可称为 第二应用服务器。 这样, 在核心网一侧看来, 业务代理服务器就相当于应 用服务器; 而在应用服务器一侧看来, 业务代理服务器就代表核心网。
本发明实施例中实现不同类型业务嵌套的方法, 如图 2 所示, 包括以 下步骤:
步骤 201 : 核心网根据用户的签约信息向业务代理服务器发送 INVITE 消息, 发起业务触发;
本步骤中,所述 INVITE消息可以是 CAMEL消息、或 SIP消息,其中, INVITE消息中包括主被叫号码。
步骤 202: 业务代理服务器根据所接收到的 INVITE消息和预先设置的 配置信息, 触发一种业务类型的应用服务器 AS1 ;
本步骤中, 所述配置信息中可以包括: 触发的业务类型、 触发顺序、 触发的方式、应用服务器地址等; 业务代理服务器根据所述 INVITE消息中 的主被叫号码以及配置信息, 按照触发顺序触发一种业务类型的应用服务 器 AS1。
步骤 203: AS1根据自身的业务逻辑, 向业务代理服务器发送事件请求 消息;
本步骤中, 如果 AS1是承载 CAMEL业务的应用服务器, 则所述事件 请求消息为计费请求消息, 包括:监控事件(RRBE )、 申请计费事件(AC )、 连接事件 ( Connect )和继续事件( Continue )等; 如果 AS1是承载 SIP业 务的应用服务器, 则所述事件请求消息为 INVITE呼叫请求消息。
步骤 204: 业务代理服务器根据 AS1发送的事件请求消息和 /或核心网 发送的 INVITE消息、以及配置信息,触发其他业务类型的应用服务器 AS2。
本步骤中, 如果 AS1是承载 CAMEL业务的应用服务器, 则业务代理 服务器根据配置信息和 AS1发送的连接号码, 和 /或核心网发送的 INVITE 消息, 按照触发顺序触发其他类型的应用服务器。
下面通过实施例对本发明所述的方案进行详细描述。
本实施例中, 假设原有的业务是 CAMEL业务, 新加入的业务是 SIP 业务, 业务代理服务器可以通过 INVITE 消息接入, 触发原有的 CAMEL 业务,并根据业务代理的配置信息触发新加入的 SIP业务,从而完成 CAMEL 业务和 SIP业务的嵌套; 其中, AS1为承载 CAMEL业务的应用服务器, AS2为承载 SIP业务的应用服务器。
下面对本发明所述的方法进行详细描述, 本实施例中具体步骤如下: 步骤 301 : 核心网根据用户的签约信息向业务代理服务器发送 INVITE 消息发起业务触发, 业务代理服务器向核心网回复 100临时响应;
步骤 302: 业务代理服务器根据预先设置的配置信息, 生成触发消息一 —InitialDP消息发送给承载 CAMEL业务的 AS1 , 触发 CAMEL业务; 本步骤中, 所述业务代理服务器预先设置的配置信息包括: 触发的业 务类型、 触发顺序、 触发的方式、 应用服务器地址等; 业务代理服务器根 据 INVITE消息中的用户属性,在配置信息中获取需要触发的业务类型、触 发的方式及应用服务器地址等信息, 并按照触发顺序, 当在配置信息中获 取到需要触发 CAMEL业务时, 生成 CAMEL规范的 InitialDP消息发送给 AS1 , 触发承载 CAMEL业务的 AS1。
步骤 303: AS1根据自身的业务逻辑, 向业务代理服务器发送计费请求 消息, 请求计费;
本步骤中, AS1 向业务代理服务器发送的计费请求消息中包括: 监控 事件、 申请计费事件、 连接事件和继续事件等。
步骤 304: 业务代理服务器根据配置信息和 AS1发送的计费请求消息 和 /或核心网发送的 INVITE消息,生成 INVITE消息发送给承载 SIP业务的 AS2, 触发 SIP业务; AS2向业务代理服务器回复 100临时响应;
本步骤中, 业务代理服务器根据 AS1的发送请求事件消息中的连接号 码和 /或核心网发送的 INVITE消息获取到与所述连接号码对应的配置信息, 触发 SIP业务。
步骤 305: AS2根据自身的业务逻辑, 向业务代理服务器发送 INVITE 呼叫请求消息, 业务代理服务器给 AS2回复 100临时响应;
本步骤中, AS2给业务代理服务器发送 INVITE呼叫请求消息,请求业 务代理服务器呼叫被叫用户; 业务代理服务器收到 INVITE呼叫请求消息 后 , 给 AS2回复 100临时响应。
步骤 306: 业务代理服务器将 INVITE呼叫请求消息发送给核心网, 请 求呼叫被叫用户,核心网收到 INVITE呼叫请求消息后,回复 100临时响应; 步骤 307: 被叫用户振铃后,核心网给业务代理服务器回复 180振铃响 应, 业务代理服务器将 180振铃响应传递给 AS2;
步骤 308: AS2将 180振铃响应发送给业务代理服务器, 业务代理服务 器将 180振铃响应传递给核心网, 通知主叫用户被叫用户正在振铃;
步骤 309:被叫用户应答,核心网给业务代理服务器回复 200应答响应, 业务代理服务器给核心网回复证实消息 ACK;
步骤 310: 业务代理服务器将 200应答响应传递给 AS2, AS2向业务代 理服务器回复证实消息 ACK;
步骤 311 : AS2向业务代理服务器发送 200应答响应, 业务代理服务器 给 AS2回复证实消息 ACK, 并向 AS 1上报被叫用户应答事件;
步骤 312: 业务代理服务器向核心网发送 200应答响应, 通知主叫用户 被叫用户正在应答; 核心网给业务代理服务器回复证实消息 ACK;
步骤 313: 业务代理服务器向 AS1上报计费事件报告;
步骤 314: 如果呼叫仍在继续, AS1继续给业务代理服务器发送计费请 求消息, 请求计费;
步骤 315: 被叫用户挂机, 核心网向业务代理服务器发送 BYE请求, 业务代理服务器将 BYE请求发送给 AS2;
步骤 316: AS2向业务代理 Λ良务器回复 BYE的 200 OK响应, 业务代 理月良务器向核心网回复 BYE的 200 OK响应;
步骤 317: AS2向业务代理服务器发送 BYE请求, 请求结束主叫用户 的会话, 业务代理服务器向 AS2回复 BYE的 200 OK响应;
步骤 318: 业务代理服务器向 AS1上报计费事件报告、 以及被叫用户 挂机事件; AS1向业务代理服务器发送呼叫释放指示;
步骤 319: 业务代理服务器给核心网发送 BYE请求, 释放主叫用户的 会话;
步骤 320: 核心网给业务代理服务器回复 BYE请求的 200响应。
基于本实施例给出的实现流程, 实际应用中, 如果原有业务是 SIP 业 务, 新加入业务是 CAMEL业务, 步骤 302~304具体为:
业务代理服务器生成 INVITE消息触发承载 SIP业务的 AS1 ; AS1根据 自身的业务逻辑, 向业务代理服务器发送 INVITE呼叫请求消息; 业务代理 服务器根据所述 INVITE呼叫请求消息和 /或核心网发送的 INVITE消息、 及预先设置的配置信息,生成 InitialDP消息触发承载 CAMEL业务的 AS2。 这种情况下, AS1为承载 SIP业务的应用服务器, 而 AS2为承载 CAMEL 业务的应用服务器。
为实现上述方法, 本发明还提供了一种实现不同类型业务嵌套的系统, 如图 1 所示, 包括: 核心网、 业务代理服务器、 一个以上应用服务器; 其 中,
核心网, 用于、 即设置为根据用户的签约信息向业务代理服务器发送 INVITE消息, 发起业务触发; 业务代理服务器, 设置于核心网和应用服务器之间, 用于根据所接收 到的 INVITE 消息和预先设置的配置信息触发一种业务类型的第一应用服 务器, 并进一步根据所触发的应用服务器发送的事件请求消息和 /或核心网 发送的 INVITE消息、以及所述配置信息,触发其他业务类型的第二应用服 务器;
应用服务器, 用于根据业务代理服务器的触发消息触发自身相应业务, 并向业务代理服务器发送事件请求消息。
所述第一应用服务器为承载 CAMEL业务的应用服务器, 第二应用服 务器为承载 SIP业务的应用服务器;
所述业务代理服务器,还用于接收 AS2发送的 INVITE呼叫请求消息, 并将所述 INVITE呼叫请求消息发送给核心网, 请求呼叫被叫用户。
所述业务代理服务器, 还用于被叫用户振铃后, 接收核心网发送的振 铃响应, 并将所述振铃响应传递给 AS2; 还进一步用于接收 AS2发送的振 铃响应, 并将所述振铃响应发送给核心网, 通知主叫用户被叫用户正在振 铃。
所述业务代理服务器, 还用于被叫用户应答后, 接收核心网发送的应 答响应, 并将所述应答响应传递给 AS2; 还用于接收 AS2发送的应答响应, 并将所述应答响应发送给核心网, 通知主叫用户被叫用户应答; 并进一步 用于向 AS1上报计费事件报告。
所述业务代理服务器, 还用于被叫用户挂机后, 接收 AS2发送的 BYE 请求, 并将所述 BYE请求发送给核心网, 通知主叫用户被叫用户挂机; 还 用于向 AS1上报挂机事件, 并接收 AS1发送的呼叫释放指示。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围, 凡在本发明的精神和原则之内所作的任何修改、 等同替换和改进 等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种实现不同类型业务嵌套的方法, 包括:
核心网根据用户的签约信息向业务代理服务器发送 INVITE消息,发起 业务触发;
业务代理服务器根据所接收到的 INVITE 消息和预先设置的配置信息 触发一种业务类型的第一应用服务器, 并进一步根据所述应用服务器发送 的事件请求消息和 /或核心网发送的所述 INVITE消息、 以及所述配置信息 触发其他业务类型的第二应用服务器。
2、 根据权利要求 1所述的方法, 其中,
所述第一应用服务器为承载应用增强逻辑(CAMEL )业务的应用服务 器, 所述第二应用服务器为承载会话起始协议(SIP )业务的应用服务器; 所述业务代理服务器根据所述第一应用服务器发送的事件请求消息、 和 /或核心网发送的 INVITE消息、 以及预先设置的配置信息触发其他业务 类型的第二应用服务器, 为: 当业务代理服务器生成 InitialDP消息触发承 载 CAMEL业务的第一应用服务器时, 第一应用服务器根据自身的业务逻 辑, 向业务代理服务器发送计费请求消息; 业务代理服务器根据计费请求 消息和 /或核心网发送的所述 INVITE消息、 以及预先设置的配置信息, 生 成 INVITE消息触发承载 SIP业务的第二应用服务器;
或者,
所述第一应用服务器为承载 SIP 业务的应用服务器, 所述第二应用服 务器为承载 CAMEL业务的应用服务器;
当业务代理服务器生成 INVITE消息触发承载 SIP业务的第一应用服务 器时, 第一应用服务器根据自身的业务逻辑, 向业务代理服务器发送 INVITE呼叫请求消息; 业务代理服务器根据所述 INVITE呼叫请求消息和 /或核心网发送的 INVITE消息、 以及预先设置的配置信息, 生成 InitialDP 消息触发承载 CAMEL业务的第二应用服务器。
3、 根据权利要求 2所述的方法, 其中, 该方法还包括: 第一应用服务 器和第二应用服务器被触发后, 第二应用服务器通过业务代理服务器向核 心网发送 INVITE呼叫请求消息, 请求呼叫被叫用户。
4、 根据权利要求 3所述的方法, 其中, 该方法还包括: 被叫用户振铃 后, 核心网将振铃响应通过业务代理服务器传递给第二应用服务器; 第二 应用服务器再将所述振铃响应通过业务代理服务器发送给核心网, 通知主 叫用户被叫用户正在振铃。
5、 根据权利要求 3所述的方法, 其中, 该方法还包括: 被叫用户应答 后, 核心网将应答响应通过业务代理服务器传递给第二应用服务器; 第二 应用服务器向第一应用服务器上报被叫用户应答事件, 并将所述应答响应 通过业务代理服务器发送给核心网, 通知主叫用户被叫用户正在应答; 业 务代理服务器向第一应用服务器上报计费事件报告。
6、 根据权利要求 3、 4或 5所述的方法, 其中, 该方法还包括: 被叫 用户挂机后, 核心网通过业务代理服务器将 BYE请求发送给第二应用服务 器; 第二应用服务器通过业务代理服务器向核心网发送 BYE请求, 请求结 束主叫用户的会话; 业务代理服务器向第一应用服务器上报计费事件报告、 以及被叫用户挂机事件; 第一应用服务器向业务代理服务器发送呼叫释放 指示。
7、 一种实现不同类型业务嵌套的系统, 包括: 核心网、 业务代理服务 器、 一个以上应用服务器; 其中,
核心网, 设置为根据用户的签约信息向业务代理服务器发送 INVITE 消息, 发起业务触发;
业务代理服务器, 设置于核心网和应用服务器之间, 设置为根据所接 收到的 INVITE 消息和预先设置的配置信息触发一种业务类型的第一应用 服务器, 并进一步根据所述应用服务器发送的事件请求消息和 /或核心网发 送的 INVITE 消息、 以及所述配置信息触发其他业务类型的第二应用服务 器;
应用服务器, 设置为根据业务代理服务器的触发消息触发相应业务, 并向业务代理服务器发送事件请求消息。
8、 根据权利要求 7 所述的系统, 其中, 所述第一应用服务器为承载 CAMEL业务的应用服务器,所述第二应用服务器为承载 SIP业务的应用服 务器;
所述业务代理服务器, 还设置为接收第二应用服务器发送的 INVITE 呼叫请求, 并将所述 INVITE呼叫请求发送给核心网, 请求呼叫被叫用户。
9、 根据权利要求 7所述的系统, 其中, 所述业务代理服务器, 还设置 为被叫用户振铃后, 接收核心网发送的振铃响应, 并将所述振铃响应传递 给第二应用服务器; 还进一步设置为接收第二应用服务器发送的振铃响应, 并将所述振铃响应发送给核心网, 通知主叫用户被叫用户正在振铃;
被叫用户应答后, 接收核心网发送的应答响应, 并将所述应答响应传 递给第二应用服务器; 还设置为接收第二应用服务器发送的应答响应, 并 将所述应答响应发送给核心网, 通知主叫用户被叫用户应答;
并进一步设置为向第一应用服务器上报计费事件报告。
10、根据权利要求 7、 8或 9所述的系统, 其中, 所述业务代理服务器, 还设置为被叫用户挂机后, 接收第二应用服务器发送的 BYE请求, 并将所 述 BYE请求发送给核心网, 通知主叫用户被叫用户挂机;
还设置为向第一应用服务器上报挂机事件, 并接收第一应用服务器发 送的呼叫释放指示。
PCT/CN2011/070740 2010-07-27 2011-01-28 一种实现不同类型业务嵌套的方法和系统 WO2012013029A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP11811731.6A EP2600590B1 (en) 2010-07-27 2011-01-28 Method for realizing nesting of services with different categories and system thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010241617.4 2010-07-27
CN201010241617.4A CN101924789B (zh) 2010-07-27 2010-07-27 一种实现不同类型业务嵌套的方法和系统

Publications (1)

Publication Number Publication Date
WO2012013029A1 true WO2012013029A1 (zh) 2012-02-02

Family

ID=43339429

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/070740 WO2012013029A1 (zh) 2010-07-27 2011-01-28 一种实现不同类型业务嵌套的方法和系统

Country Status (3)

Country Link
EP (1) EP2600590B1 (zh)
CN (1) CN101924789B (zh)
WO (1) WO2012013029A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101468A (zh) * 2015-07-14 2015-11-25 北京金山安全软件有限公司 网络连接的设置方法、装置和移动终端

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101924789B (zh) * 2010-07-27 2014-03-19 中兴通讯股份有限公司 一种实现不同类型业务嵌套的方法和系统
CN104284446A (zh) * 2013-07-12 2015-01-14 中兴通讯股份有限公司 一种业务并行建立的方法及基站
CN107770128A (zh) * 2016-08-17 2018-03-06 中国移动通信有限公司研究院 一种业务执行方法及执行装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004103012A1 (en) * 2003-05-19 2004-11-25 Siemens Aktiengesellschaft Method and means for handling multiple services of an intelligent network within a mobile communication network
CN101222483A (zh) * 2007-01-11 2008-07-16 华为技术有限公司 业务触发方法、系统及业务触发装置
CN101247641A (zh) * 2007-02-14 2008-08-20 华为技术有限公司 一种实现电路域业务交互的方法、系统、服务器及处理器
CN101729930A (zh) * 2009-11-17 2010-06-09 中兴通讯股份有限公司 一种通过智能网网关来实现多智能业务融合的方法
CN101924789A (zh) * 2010-07-27 2010-12-22 中兴通讯股份有限公司 一种实现不同类型业务嵌套的方法和系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001059987A2 (en) * 2000-02-08 2001-08-16 Syndeo Corporation Method and apparatus for diverting a packet-switched session utilizing an intelligent proxy agent
FR2889012B1 (fr) * 2005-07-22 2007-08-24 Alcatel Sa Dispositif de gestion de ressources de serveurs media pour l'interfacage entre serveurs d'applications et serveurs media au sein d'un reseau de communication
EP2090070B1 (en) * 2006-12-11 2010-09-01 Telefonaktiebolaget LM Ericsson (publ) Service adaptation in an IP multimedia subsystem network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004103012A1 (en) * 2003-05-19 2004-11-25 Siemens Aktiengesellschaft Method and means for handling multiple services of an intelligent network within a mobile communication network
CN101222483A (zh) * 2007-01-11 2008-07-16 华为技术有限公司 业务触发方法、系统及业务触发装置
CN101247641A (zh) * 2007-02-14 2008-08-20 华为技术有限公司 一种实现电路域业务交互的方法、系统、服务器及处理器
CN101729930A (zh) * 2009-11-17 2010-06-09 中兴通讯股份有限公司 一种通过智能网网关来实现多智能业务融合的方法
CN101924789A (zh) * 2010-07-27 2010-12-22 中兴通讯股份有限公司 一种实现不同类型业务嵌套的方法和系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
See also references of EP2600590A4 *
YOU WEI ET AL.: "Plan Research 3G Migration Intelligence Network Construction and Multi-services Trigger", JOURNAL OF JILIN UNIVERSITY, vol. 25, no. 4, July 2007 (2007-07-01), pages 435 - 439, XP008168841 *
YU ZHIHU ET AL.: "Solutions to Multi-service Triggering Problem in Intelligent etwork", JOURNAL OF BEIJING UNIVERSITY OF POSTS AND TELECOMMUNICATIONS, vol. 29, May 2006 (2006-05-01), pages 52 - 56, XP008168817 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101468A (zh) * 2015-07-14 2015-11-25 北京金山安全软件有限公司 网络连接的设置方法、装置和移动终端

Also Published As

Publication number Publication date
EP2600590A1 (en) 2013-06-05
EP2600590B1 (en) 2017-03-22
EP2600590A4 (en) 2014-04-30
CN101924789A (zh) 2010-12-22
CN101924789B (zh) 2014-03-19

Similar Documents

Publication Publication Date Title
US7620384B2 (en) Converged service control for IMS networks and legacy networks
CN100372304C (zh) 基于软交换设备感知业务的wimax动态qos实现方法
JP4958972B2 (ja) Imsネットワークにおける通知の提供
US8200196B2 (en) Method and a system for enabling multimedia ring-back-within the context of a voice-call
US20060203802A1 (en) Method and system for dynamically specifying and instantly transmitting and representing/displaying call data
WO2009152699A1 (zh) Sip终端及其上报状态的方法、系统以及sip服务器
CN100459634C (zh) 通话的实现方法
WO2009052673A1 (en) Uniform service access system and access method
WO2012013029A1 (zh) 一种实现不同类型业务嵌套的方法和系统
US20090055879A1 (en) System and method for implementing streaming service
WO2009055966A1 (en) Method for generating a real time billing information in a packet switching based network and network element
WO2014094438A1 (zh) Ims架构下信息传送方法、装置和通信系统
CN1266885C (zh) 一种基于软交换实现监听的方法
WO2011153752A1 (zh) 在ctd业务中实现呼叫转接的方法、系统及应用服务器
CN101365157A (zh) 一种业务触发方法、系统及装置
CN102668487B (zh) 一种媒体网关实现呼叫的方法及系统
CN101771547B (zh) Sip软交换平台计费系统的实现方法
WO2009056041A1 (fr) Procédé, système et dispositif de transmission d'informations d'attribut de frais
CN101742370B (zh) 通信系统中呼叫处理的方法、网络节点和应用服务器
KR100461726B1 (ko) 인터넷 기반 통합망에서 개방형 서비스 api를 이용한서비스를 제공하는 시스템
WO2012089055A1 (zh) 在ip多媒体子系统网络实现被叫付费业务的方法和装置
WO2008089631A1 (fr) Procédé et dispositif de mise au point d'un service de renseignements pour ngn
WO2012171290A1 (zh) 询问转接实现方法、应用服务器、业务终端和系统
WO2011079709A1 (zh) 会话处理方法及装置
WO2007101409A1 (fr) Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2011811731

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2011811731

Country of ref document: EP