WO2011161365A1

WO2011161365A1 - Notification of incident on an rnis accessway linked to an ip network

Info

Publication number: WO2011161365A1
Application number: PCT/FR2011/051408
Authority: WO
Inventors: José DOREE; Jean-Claude Le Rouzic
Original assignee: France Telecom
Priority date: 2010-06-24
Filing date: 2011-06-20
Publication date: 2011-12-29
Also published as: FR2961987A1; EP2586214A1

Abstract

The invention relates to a method of notification of incident on an RNIS accessway linked to an IP network. This method comprises the following steps: detection of said incident by a device for linking said RNIS accessway to said IP network; and sending by said linking device of a session control message to a device, termed the requester, of the IP network, having previously subscribed with the linking device, in an explicit or implicit manner, to the notification of at least one state item of information of the RNIS accessway.

Description

NOTIFICATION OF INCIDENT ON ISDN ACCESS CONNECTED TO AN IP NETWORK

The present invention relates to Integrated Services Digital Network (ISDN).

More specifically, the present invention relates to the connection of an ISDN access to a telecommunications network of IP ("Internet Protocol") type.

It will be recalled that the Switched Telephone Network (RTC), and in particular the public switched telephone network RTCP (in English, PSTN), is a fixed telephony network in which an analogue terminal or a digital installation are connected to a central office by one or more twisted pairs of copper son fed by the network, the assembly constituting what is called the "local loop". The telephone exchanges are themselves linked together by high speed links. The analog or digital telephone terminals can be of various kinds, for example an individual telephone (subscriber station), a payphone, or a PABX (initials of the words "Private Automatic Branch eXchange" meaning "private telephone switch") which serves mainly to connect the telephones of an establishment ("internal" lines) with the public telephone network ("external" lines).

It is also recalled that conventional advanced session control protocols, such as the H.323 and SIP (Session Initiation Protocol) protocols, use so-called "signaling messages" to enable a terminal to request a connection with a user. other terminal, or also messages indicating that a telephone line is busy, or signaling that the called telephone ring, or signaling that such a phone is connected to the network and can be attached in one way or another. When a client registered on a network using an advanced session control protocol wishes to benefit from a multimedia service offered by the network, it sends a signaling message to the network specifying its request.

The H.323 protocol has been developed by ITU-T. It specifies procedures for signaling, coder-decoder negotiation, and information transport. It is widely used by manufacturers of voice and video conferencing, as well as in several real-time Internet applications such as "NetMeeting".

The SIP protocol has been defined by NETF in RFC 3261. This protocol allows the establishment, modification and termination of multimedia sessions in a network using the IP protocol. The SIP protocol also allows for event notification procedures and the sending of information outside the context of a session. It is widely used for instant messaging service orders. Thus, in a SIP environment, there are different types of communications such as session establishment requests and queries exchanged outside any dialog.

The invention is particularly suitable for IMS ("IP Multimedia Subsystem") type infrastructures. The IMS has been defined by the 3rd Generation Partnership Project (3GPP) and TISPAN (Telecommunications and Internet Converged Services and Protocols for Advanced Networking). It is a network architecture introduced by 3GPP for mobile networks, then taken over by TISPAN for fixed networks. This architecture, which uses the SIP protocol, allows the dynamic establishment and the control of multimedia sessions between two clients as well as the reservation of the resources at the level of the network of transport of the multimedia flows. Thanks to this architecture, Network operators can conveniently implement a management policy, provide a predetermined Quality of Service, and calculate the amounts to be billed to customers. The IMS currently provides access to telephony, video telephony, presence and instant messaging services, which it also manages.

The telephone operators have begun the migration of their telephone switching network to so-called "Voice over IP" or VoIP networks, which allow the transmission of conversational data (voice and fax). While the number of traditional PSTN subscribers is declining, that of VoIP subscribers, who have subscribed to a bundled services offer (Internet / TV / unlimited telephony), is growing strongly. These VoIP subscribers are (or will be) connected to IMS network cores, while the PSTN subscribers are currently connected to time switches in the telephone exchanges through the Subscriber Connection Units (URA) ( a "time switch" operates on time multiplexed signals). In these circumstances, the operators must operate in parallel two different networks, which increases the costs of operation and maintenance.

It therefore appeared desirable to converge these networks without replacing the terminals of the RTC park (because of the attachment of many customers to their traditional telephone line, and the expenses that their replacement would entail), hence the notion "RTC emulation". The PSTN subscribers are then connected to new types of ARUs that perform the call signaling protocol adaptation for IMS core communication, as well as the encoding / decoding of the media streams: in the context of the present invention these new types of URA will be called "URA-SIP". Examples of these URA-SIPs include home bridges and gateways in ("Residential Gateways" in English), and secondly the gateways located in the network of an operator ("Voice Gateways" in English) such as DSLAM-SIP or DSLAM-H.248 (DSLAM are the initials of "Digital Subscriber Line Access Multiplexer" means "Digital Subscriber Line Access Multiplexer" means devices that collect DSL data traffic over a number of telephone lines.

This convergence also concerns ISDN type subscribers. As explained in the online encyclopedia "Wikipedia", ISDN access offers digital links based on the quality of the RTC, and offering speeds up to 2 Mbit / s. ISDN combines the broad geographic coverage of a telephone network with the transport capacity of a data network carrying voice, data and video. With ISDN, for example, smaller regional and international sites can connect to corporate networks at a cost that is better suited to actual consumption than with dedicated lines. A subscriber can thus request ISDN connections either to replace specialized lines, or in addition to increase the bandwidth or ensure redundancy.

The International Telecommunication Union (ITU) has defined ISDN technology so that it can provide digital connectivity with a wide variety of services. Two important features allow the RTC to evolve to offer ISDN services:

• the connections must be digital end-to-end; and

• the network must offer a set of ISDN-compliant user interface / network protocols; in this way, all ISDN equipment uses the same physical connections and signaling protocols to access the services. In an analog telephone network, the local loop allows a single transmission channel; this channel processes only one service at any given time: voice or data. With ISDN, the local loop (comprising one or two pairs of twisted wires) is divided into several logical channels, called B and D, distinguished by their functions and their bit rates. In addition, two types of access can be used, characterized by their respective numbers of B and D channels: the basic access access S0 / T0 (Basic Rate Access or BRA), and the primary access S2 / T2 ("Primary Rate Access" or PRA). It is of course very important that ISDN access can guarantee end-to-end error free transport of digital information.

In the case of an ISDN installation connected to the PSTN, in order to guarantee the high availability and the high quality of the ISDN service, the operator regularly carries out preventive tests which use re-closure mechanisms, as well as procedures error rate calculation (using the CRC - cyclic redundancy check mechanisms specified in the ISDN physical bearer layer). These maintenance procedures are described in the ITU-T 1.430 standards for basic access (ISDN BRA), and ITU-T 1.431 for primary access (ISDN PRA).

If at the end of these tests, or following an incident (break or alteration of the cable, power failure, and so on), the ISDN access is deemed to be defective, the interface can then be declared out of service and the operator is obliged (contractually, most often) to remedy as quickly as possible the defects observed. If the fault is located in the client facility, incident reporting and operator intervention are only required under conditions (usually only for primary ISDN access, and under contract conditions).

Consider now the case of an ISDN installation connected to an IP network. FIG. 1 schematically illustrates, by way of example, the connection of an ISDN access to an IP network, for a basic access (ISDN BRA) or a primary access (ISDN PRA), via a connection device 1 constituted by a URA-SIP or a set consisting of an H.248 gateway and an intermediate entity of the network, such as the AGCF (initials of the words "Access Gateway Control Function" meaning Access Gateway Control Function) . To simplify the figure, the rest of the IP network is not represented.

In this figure:

• the ISDN access connection port to the URA-SIP is denoted as "LT" (initials of the English words "Line Termination");

• the connection interface of the client-installation to the ISDN access is marked "T"; at the associated end of the ISDN access is a device denoted "NT1" (initials of the words "Network Termination 1"); NT1 equipment is also commonly referred to as TNR (for "Digital Network Termination" in French ISDN access) in the case of basic access connections; and

• The customer-equipment itself is noted as "TE" (initials of the English words "Terminal Equipment").

We thus distinguish several sections:

• the "Digital Digital Section", located between the LT port and the T interface; this section is the responsibility of the operator; and

• the "User Digital Section"("User Digital Section"), located between the T interface and the TE client equipment; this section is generally the responsibility of the user, but may be subject to special supervision by the network operator, particularly in the case of the primary access (ISDN PRA) mentioned above. FIG. 2 diagrammatically illustrates, as another example, the connection of a primary ISDN access (ISDN PRA) to an IP network via a connection device 1 constituted by a transit gateway ("Trunking Gateway" or TGW). To simplify the figure, the rest of the IP network is not represented.

In this figure:

• the connection port for ISDN access to the TGW is "LT";

• the connection point of the client installation to the ISDN access is "T2"; at the associated end of the ISDN access is a device denoted "NT1"; at the associated end of the subscriber installation is a PABX denoted "NT2"; and

• the client-equipments themselves are denoted "TE", and are connected to the PABX via an interface denoted "S0 / T0".

We thus distinguish several sections:

· The "Digital Digital Section" located between the LT port and the T2 connection point; this section is the responsibility of the operator, and has primary access (ISDN PRA); and

• the "User Digital Section" located between the T2 connection point and the TE client equipment; this section is under the responsibility of the user (s), and in this example has basic access (ISDN BRA).

In general, for ISDN accesses connected to an IP network, such as those shown in these figures as examples, it is not possible to indicate to the call processing device the nature of a fault when it is detected, so as to discern whether this defect is located in the operator-section (immediate intervention required) or in the user-section (conditional intervention). The TISPAN TS 183 036 standard, which specifies the interworking between the ISDN DSS.1 protocol and the SIP protocol, provides only one error code at the interface. SIP, said code (transmission of a BYE / CANCEL with "Reason Header" containing a cause value 27 "Destination out of order") covering different cases without distinction.

Even if differentiated error codes were used, it would be possible, with the above method, to communicate the fault location information only during an attempt to establish a session to the client equipment, or when breaking a session already established (BYE or CANCEL broadcast only).

These limitations make it impossible, for example, to preemptively signal error or degradation following maintenance tests, and also make it impossible to detect errors for "dedicated start" accesses (in which the subscriber can make calls). but can not receive it).

It is also impossible for an operator to require the testing of a digital user section and / or an operator digital section, and also to suspend an ongoing test in the event of an incoming or outgoing call. .

The need for a mechanism to accurately locate an error in the operator section is particularly important when the ISDN access operator (operating a DSLAM for example) and the service operator (in charge of the control and as a service to the customer) are different, as is the case in some networks: indeed, it is necessary to clearly separate and identify the responsibilities of each. In addition, in this case, the service operator does not have - unlike the network operator - the ability to query the connection device to obtain information about the status of the ISDN access.

The present invention thus relates to a method of incident notification on an ISDN access connected to an IP network. This method is remarkable in that it comprises the following steps: detection of said incident by a connection device of said ISDN access to said IP network, and

- sending by said connection device a session control message to a device, called said requestor, of the IP network, having previously subscribed to the connection device, explicitly or implicitly, to the notification of at least one piece of information status of ISDN access.

Thanks to the invention, the management of an ISDN access by an operator is considerably improved thanks to the automatic provision of status information concerning this ISDN access. As explained above, this is particularly advantageous in the case where the requesting state information device is a service operator distinct from the ISDN access operator.

This provision of information therefore allows an operator to react quickly and implement an appropriate repair action, so as to minimize the downtime for ISDN customers.

According to particular features, said status information advantageously relates to:

- a defect noted, or a deterioration of quality noted, or a lack of defect, in the digital user section of the ISDN access, and / or

- a defect noted, or a deterioration of quality noted, or a lack of defect, in the digital operator section of the ISDN access.

It is thus possible, in particular, to report a degradation of part of the ISDN access without prohibiting calls or causing a de-registration of the user.

According to other particular features, said session control message contains a specific header ("header"). associated with the subscription to said state information (in the context of the invention, a "header" designates a specific line in a session control message).

With these provisions, the invention requires only a modest extension of session control protocols (SIP, or other).

Correlatively, the invention relates to various devices.

It thus concerns, firstly, a device for connecting an ISDN access to an IP network. This connecting device is remarkable in that it has means for:

- detect an incident on said ISDN access, and

sending a session control message to a device, said calling party, of said IP network, having previously subscribed to said connection device, explicitly or implicitly, to the notification of at least one access status information ISDN.

It also concerns, secondly, a device, said applicant, an IP network. This requesting device is remarkable in that it has means for:

- subscribe, explicitly or implicitly, to the notification of at least one status information of an ISDN access to a connection device of said ISDN access to said IP network, and

receiving, from said connection device, a session control message following the detection by the connecting device of an incident on the ISDN access.

According to particular characteristics of these two devices, said status information relates to:

- a defect noted, or a deterioration of quality noted, or a lack of defect, in the digital user section of the ISDN access, and / or - a defect noted, or a deterioration of quality noted, or a lack of defect, in the digital operator section of the ISDN access.

The advantages offered by these devices are essentially the same as those offered by the correlative methods succinctly set forth above.

Note that it is possible to realize the devices succinctly described above in the context of software instructions and / or in the context of electronic circuits.

The invention also relates to a computer program downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor. This computer program is notable in that it includes instructions for performing the steps of any of the incident notification methods succinctly set forth above, when run on a computer.

The advantages offered by this computer program are essentially the same as those offered by said methods.

Other aspects and advantages of the invention will appear on reading the detailed description below of particular embodiments, given by way of non-limiting examples. The description refers to the figures which accompany it, already described above, in which:

FIG. 1 schematically represents the connection of an ISDN access to an IP network via a URA-SIP, and

- Figure 2 shows schematically the connection of an ISDN access to an IP network via a transit gateway.

The operation and advantages of the invention will now be illustrated in the context of various embodiments. It is recalled that the Internet Engineering Task Force (IETF) RFC 3265 generally defines a subscription / notification mechanism called "event package". The invention proposes a new type of event, which will be called "DigitalSection-supervision" hereinafter.

According to the invention, a device 2 of an IP network, requesting status information from an ISDN access connected to the IP network, subscribes, explicitly or implicitly, to the notification of this information to a device connection 1 of the ISDN access to the IP network.

This connection device 1, supervisor and generator of the state information, can be, for example (see description of FIGS. 1 and 2 above), a URA-SIP (home gateway, enterprise gateway, gateway, etc.). operator such as a DSLAM-SIP or DSLAM-H248, possibly associated with an AGCF, and so on) or a TGW transit gateway.

In the case where the IP network is of the IMS type, the requesting device 2 can be, in particular:

An AS server (initials of the English words "application server" meaning "application server") such as a voicemail server, a presence server or a telephony server,

• a P-CSCF (Proxy-Call Server Control Function) server (the P-CSCF servers serve as points of contact between the user terminals and the IMS network), or

• an S-CSCF server (initials of the English words "Serving-Call Server Control Function" meaning "Service Call Control Function") (S-CSCF servers manage the registration procedure of user terminals , as well as the routing of the resulting signaling, or destination, of these user terminals), or

• an IBCF server (initials of the English words "Interconnection Border Control Function" meaning the Interconnection Border Control Function) (the IBCF servers serve as gateways to external networks, and in particular act as firewalls).

The states of ISDN access that may be useful for notification include:

- the state "user interface failure" indicates a fault found in the digital user section of the ISDN access;

- the "network interface failure" status indicates a fault found in the digital operator section of the ISDN access;

the state "normal condition at user interface" indicates a fault absence in the digital user section (return: normal condition);

- The condition "normal condition at network interface" indicates a fault absence in the operator numeric section (return: normal condition); and

the "grading" state indicates a degradation of quality noted in the digital operator section; this type of degradation allows calls to be disposed of, but can trigger maintenance operations; the conditions for triggering the notification of these states depend on the quality policy of the operator of the ISDN access (crossing an error rate threshold, for example).

The state information according to the invention may be conveyed in a new header ("header"), which will be called for example "DigitalSection-Supervision". The "method", that is the type of session control message that will convey this new header, may be of a conventional type (eg NOTIFY, INFO, MESSAGE, INVITE, OPTIONS or other), or of a new type specific to the implementation of the present invention.

In the case of a network using the SIP protocol, the "From" header indicates the identity of the ISDN access to which the forwarded information applies. This identity may correspond, according to the operator policies, to a line identifier (according to the format isdn-accessid @ operator ms.com) in accordance with the specification ETSI TS 183 043, or to a routable public identity such as an IMPU (initials of the English words "IP Multimedia Public Identity"), according to the global format number@operator.ims.com, such as +33296123456@operator.ims.com.

In the case of an implicit subscription to state information, there is no associated subscription request (no SUBSCRIBE message). The notifier may be configured to issue NOTIFY messages to a designated recipient (s). The configuration may be more specific and apply for example only to a subset of the resources managed by the notifier and / or to a subset of the state information. The notifier may be configured with the identity of the recipient (AS, S-CSCF, and so on); alternatively, it will use the domain name of the recipient's attachment network, in which case it will be up to the IMS heart to route the notification messages correctly. In addition, the notifier may be configured with the list of ISDN accesses for which supervision is requested; alternatively, it may provide a supervision of all ISDN access, or a lack of supervision.

In the case of an explicit subscription, the subscriber may indicate in the header "To" and / or the "Request-URI" the identity (line identifier or routable public identity) of the ISDN access for which supervision is requested. Alternatively, the header "To" and / or the "Request-URI" may contain the temporary public identity used in group registration ("Group Registration") in accordance with ETSI TS 183 043; in this case, all ISDN accesses implicitly associated with the group will be supervised. Moreover, the subscriber may optionally indicate in the body of the subscription message the list of states for which he wishes to be notified: states of type "user", "network", "grading" (as described above), or any combination of these states; we can foresee that, by default, if the list of states is not specified, it is the set of states that will be subscribed.

These events obviously interact with the call processing itself, as well as with the information system; the details of these interactions are to be fixed by each operator.

Two examples of SIP messages exchanged in connection with the invention will now be given. For the sake of simplification, the encodings proposed below for the body of these messages are all in text format, but one can naturally, alternatively, use other types of encoding, for example in XML.

1) Subscription to the "DigitalSection-Supervision" event

The ISDN access concerned in this example is identified by the French public identity 02 96 05 1 1 1 1. The subscriber, myAS@operator.ims.com, indicates that he wants to be notified for "network" and "grading" events only.

SUBSCRIBE sip: +33296051111 @operator. ims. com SIP / 2.0

To: <sip: + 33296051111 @ operator. ims. com>

From: <sip: myASSoperator. ims. com>; tag = 78923

Call-Id: [...]

CSeq: 1 SUBSCRIBE

Contact : [ ... ]

Event: DigitalSection-Supervision

Expires: [...]

Accept: application / DigitalSection_Supervision-notification Content-Type: application / DigitalSection-Supervision- Notification

Content-Length: 31

EventCategory: Network Grading 2) Notification to the requesting device to inform it of a defect in the digital operator section

NOTIFY sip: myASgoperator. ims. corn SIP / 2.0

To: [...]

From: <sip: + 33296051111 @ operator. ims. corn> tag = 78923

Contact : [ ... ]

Call-ID: [...]

CSeq: 2 NOTIFY

Event: DigitalSection-Supervision

Subscription-State: active; expires = [...]

Content-Type: application / DigitalSection-Supervision- Notification

Content-Length: 51

ISDN-Supervision-event: Network-interface-failure

Note finally that the implementation of the invention within the nodes of a telecommunications network (more specifically, the requesting devices and the state information generating devices for ISDN access) can be achieved by means of software and / or hardware components.

The software components can be integrated into a typical network node management computer program. Therefore, as indicated above, the present invention also relates to a computer system. This computer system conventionally comprises a central processing unit controlling signals by a memory, as well as an input unit and an output unit. In addition, this computer system can be used to execute a computer program comprising instructions for implementing the incident notification method according to the invention.

Indeed, the invention also relates to a downloadable computer program from a communication network comprising instructions for executing the steps of an incident notification method according to the invention, when it is executed on a computer . This computer program may be stored on a computer readable medium and may be executable by a microprocessor. This program can use any programming language, and present itself as source code, object code, or intermediate code between source code and object code, in a partially compiled form or in any other desirable form.

The invention also relates to a computer-readable information medium, comprising instructions of a computer program as mentioned above.

The information carrier may be any entity or device capable of storing the program. For example, the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording medium, for example a USB flash drive ("USB flash drive"). in English) or a hard drive.

On the other hand, the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The computer program according to the invention can in particular be downloaded to an Internet type network.

As a variant, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the incident notification method according to the invention.

Claims

1. An incident notification method on an ISDN access connected to an IP network, characterized in that it comprises the following steps:

detection of said incident by a connection device (1) of said ISDN access to said IP network, and

- sending by said connection device (1) a session control message to a device (2), said requestor of the IP network, having previously subscribed to the connection device (1), explicitly or implicitly, the notification of at least one status information of the ISDN access.

Incident reporting method according to claim 1, characterized in that said status information relates to:

An incident reporting method according to claim 1 or claim 2, characterized in that said session control message contains a specific header (DigitalSection-Supervision) associated with the subscription to said state information.

4. Device for connecting (1) an ISDN access to an IP network, characterized in that it has means for:

- detect an incident on said ISDN access, and

sending a session control message to a device (2), said calling party, of said IP network, having previously subscribed to said connection device (1), explicitly or implicitly, to the notification of at least one information item; status of ISDN access.

Connecting device (1) according to claim 4, characterized in that said status information relates to:

6. Connecting device (1) according to claim 4 or claim 5, characterized in that it belongs to the group comprising a home gateway, a corporate gateway, an operator gateway, and a transit gateway.

7. Device (2), said calling party, of an IP network, characterized in that it has means for:

- subscribe, explicitly or implicitly, to the notification of at least one status information of an ISDN access to a connection device (1) of said ISDN access to said IP network, and

receiving, from said connection device (1), a session control message following the detection by the connection device (1) of an incident on the ISDN access.

Applicant device (2) according to claim 7, characterized in that said status information relates to:

Applicant device (2) according to claim 7 or claim 8, characterized in that, said IP network being of IMS type, said requesting device (2) belongs to the group comprising an application server (AS), a server P-CSCF, an S-CSCF server, and an IBCF server.

An immovable, or partially or totally removable, data storage means having computer program code instructions for performing the steps of an incident reporting method according to any one of claims 1 to 3.

1 1. Computer program downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor, characterized in that it comprises instructions for the execution of the steps of a notification process of a An incident according to any one of claims 1 to 3 when executed on a computer.