Sélection de la langue

Search

Sommaire du brevet 2331706 

Énoncé de désistement de responsabilité concernant l'information provenant de tiers

Une partie des informations de ce site Web a été fournie par des sources externes. Le gouvernement du Canada n'assume aucune responsabilité concernant la précision, l'actualité ou la fiabilité des informations fournies par les sources externes. Les utilisateurs qui désirent employer cette information devraient consulter directement la source des informations. Le contenu fourni par les sources externes n'est pas assujetti aux exigences sur les langues officielles, la protection des renseignements personnels et l'accessibilité.

Disponibilité de l'Abrégé et des Revendications

L'apparition de différences dans le texte et l'image des Revendications et de l'Abrégé dépend du moment auquel le document est publié. Les textes des Revendications et de l'Abrégé sont affichés :

  • lorsque la demande peut être examinée par le public;
  • lorsque le brevet est émis (délivrance).
(12) Demande de brevet: (11) CA 2331706
(54) Titre français: PROCEDE DE SIGNALISATION DANS UN POINT DE TRANSFERT DE SIGNALISATION
(54) Titre anglais: METHOD FOR SIGNALING IN A SIGNALING TRANSFER POINT
Statut: Réputée abandonnée et au-delà du délai pour le rétablissement - en attente de la réponse à l’avis de communication rejetée
Données bibliographiques
(51) Classification internationale des brevets (CIB):
  • H04Q 03/00 (2006.01)
(72) Inventeurs :
  • GRADISCHNIG, KLAUS (Allemagne)
(73) Titulaires :
  • SIEMENS AKTIENGESELLSCHAFT
(71) Demandeurs :
  • SIEMENS AKTIENGESELLSCHAFT (Allemagne)
(74) Agent: SMART & BIGGAR LP
(74) Co-agent:
(45) Délivré:
(86) Date de dépôt PCT: 1999-05-04
(87) Mise à la disponibilité du public: 1999-11-18
Requête d'examen: 2004-04-28
Licence disponible: S.O.
Cédé au domaine public: S.O.
(25) Langue des documents déposés: Anglais

Traité de coopération en matière de brevets (PCT): Oui
(86) Numéro de la demande PCT: PCT/EP1999/003048
(87) Numéro de publication internationale PCT: EP1999003048
(85) Entrée nationale: 2000-11-10

(30) Données de priorité de la demande:
Numéro de la demande Pays / territoire Date
98108645.7 (Office Européen des Brevets (OEB)) 1998-05-12

Abrégés

Abrégé français

Dans des réseaux de signalisation, il peut y avoir des boucles d'acheminement, faisant que des données sont acheminées dans une boucle vers une destination à laquelle elles ne parviennent jamais. L'invention indique comment reconnaître et éliminer aussi vite que possible de telles boucles.


Abrégé anglais


Routing loops may occur in signaling networks so that messages are routed to a
destination in a loop without ever reaching said destination. The invention
shows how such loops can be detected and eliminated as speedily as possible.

Revendications

Note : Les revendications sont présentées dans la langue officielle dans laquelle elles ont été soumises.


5
Claims
1. Method for the signalling in a signalling transfer point, in accord
wherewith
-- signalling messages stemming from source signalling points are routed in
the direction toward destination signalling points,
-- the presence of a loop or, respectively, the possibility of the presence of
a
loop over a departing linkset to a destination signalling point (SP X) is
checked by a routing test (MRVT) and/or by a real-time method,
-- given a positive check result, signalling messages are automatically
prevented from continuing to be sent to the destination signalling point
(SP X) via the appertaining linkset.
2. Method according to claim 1, characterized in that
-- given said positive check result, test messages are first sent via a
linkset to
destinations that can be reached via said linkset;
-- in the case of returning test messages, signalling messages are then
automatically prevented from being sent to a destination that had returning
test messages.
3. method according to claim 1 or 2, characterized in that signalling
messages are prevented (downstream) from being sent to the appertaining
destination
via the appertaining linkset in that the specific, departing linkset to this
destination is
blocked in the routing table of the signalling transfer point.
4. Method according to claim 1 or 2, characterized in that signalling
messages are prevented (upstream) from being sent to the appertaining
destination via
the appertaining linkset in that the signalling transfer point (STP A) sends a
transfer
prohibited message regarding the destination signalling point (SP X) to the
preceding
signalling transfer point (STP B), whereupon the preceding signalling transfer
point
(STP B) will reroute or, respectively, stop the traffic to the destination
signalling point
(SP X).
5. Method according to one of the claims 1 through 4, characterized in that
said interruption of the loop is controlled by the operations maintenance and
administration part (OMAP).

6. Method according to one of the claims 1 through 5, characterized in that
said interruption of the loop is controlled by the message transfer part
(MTO).
7. Method according to one of the claims 1 through 6, characterized in
that, after blocking the linkset contained in the loop, the new, current route
is in turn
immediately checked for freedom from loops in the signalling transfer point
(STP A).
8. Signalling system of a signalling transfer point that routes signalling
messages to destination signalling points, characterized in that
-- it checks the presence of a loop or, respectively, the possibility of the
presence of a loop over a departing linkset to a destination signaling point
(SP X) by a routing test (MRVT) and/or by a real-time method, whereby
-- when a positive check result is obtained, signalling messages are
automatically prevented from continuing to be sent to the destination
signalling point via the appertaining linkset.
9. Signalling system of a signalling transfer point according to claim 8,
characterized in that it verifies the detected possibility of the presence of
a loop by
sending test messages to destinations reachable via said linkset before it
automatically
prevents signalling messages from continuing to be cent via the appertaining
linkset to
a destination for which said test messages return.

Description

Note : Les descriptions sont présentées dans la langue officielle dans laquelle elles ont été soumises.


CA 02331706 2000-11-10
1
METHOD FOR SIGNALLING IN A SIGNALLING TRANSFER POINT
It can occur in signalling networks according to signalling system No. 7
that routing loops occur in the network on MTP level 3 due to incorrect
plamaing or
operating errors, so that messages are routed to one or more destinations in a
loop
without ever reaching their destination. Of particular interest here are loops
:having a
length greater than 2 ("length of a loop" means the plurality of signalling
points
participating in a loop) and, in particular, how such loops can be eliminated
when they
are recognized.
If loops potentially present in the tables ~~re in fact used for routing, thus
represents a serious problem for the network since rrtessages, on the one
hand, do not
arrive at their destination and, on the other hand, use valuable resources in
the
network. It should therefore be eliminated as fast as possible.
Loops having the length 2 (so-called ping-gong loops) cannot occur given
a functioning protocol in the MTP (message transfer point). Should they
nonetheless
arise, these loops can be easily recognized in real time in a signalling
transfer point in
that a check is carried out to see whether a message i,s to be routed over the
same
linkset on which it was received. They are just as easy to correct in that the
unsuccessful protocol actions (sending transfer prohiibited -- TFP -- messages
to the
cooperating party) are repeated.
2 0 Loops having a length >2 are more difficult to recognize. A check can in
fact be performed with every message in a specific STP as to whether this
message
derives izom precisely this STP (by comparing the CiPC contained in the
me:csage to
the PointCode of the STP). When this is the case, there is a loop in the
network.
STPs, however, do not necessarily generate messages or, respectively, do not;
2 5 necessarily generate messages to the destination or destinations to which
there is a
loop.
This problem can be solved by a real-time method that recognizes the
possibility of a loop, for example due to a lasting overload on a linkset.
When said
method recognizes the possibility of a loop, the operating personnel can be
informed
3 0 so that corrective measures can be initiated.

CA 02331706 2000-11-10
2
The standard (Q.753, Q.754) defines another solution of the problem, what
is referred to as the M~'F' route verification test (MRVT) that checks all
possible paths
in an MTP network between two given points for correctness, including freedom
from
loops. Upon occurrence of errors such as, for example, loops, the operating
;personnel
is informed in order to undertake corrections. MRVT in fact has the advantage
over a
real-time method that it ~;.an also recognize loops bei:ore they are actually
used, since
all possible paths are checked, not only the current ones. The disadvantage,
however,
is that a separate protocol is required for it. When this is not realized in
the entire
network, the check is not possible or is only possible in incomplete form.
This
l0 situation is specifically established in the international signalling
network. I)ue to the
load that it generates, moreover, the MRVT cannot constantly check all routes
between all points in the network.
The invention is based on the object of overcoming the aforementioned
disadvantages.
This object is achieved by a method according to claim 1.
The invention is explained in greater detail below with the assistance of
the drawing, whereby the drawing comprises 3 Figures.
Figure 1 shows an example of a loop.
Figures 2 and 3 shows methods for parting a loop.
2 0 The present invention particularly reveals how, given real-time
recognition of loops having a length > 2 and/or upon recognition of loops by
the
MRVT, the loops can be broken by automatic, real-time, protocol-compatible
methods that are simple to realize. The time elapsing before the operating
personal
takes action can thus be bridged.
2 5 It must thereby be mentioned that it is advantageous, given possible loops
that were recognized by the MRVT or a real-time method for a linkset, to check
before having potential recourse to automatic correction measures (the MRV'T,
namely, does not supply any statements whether a possible loop is also being
employed at the time and, under certain circumstances, the real-time method
cannot
3 0 make any statements about the destination to which a possible loop is
present). Said
check ensues by sending otherwise unemployed MT'P network management messages

CA 02331706 2000-11-10
3
to the destinations that c;an be reached (according to the routing) via the
appertaining
linkset. When such test messages return to the STP, these messages are
detf;cted by
comparing the OPC contained in the message to the point code of the STP, and a
loop
or, respectively, several loops are recognized. Correction measures can
thereby
remain limited to loops being currently employed.
Said check vvith the assistance of test messages is already useful when it is
realized in only one STP since all loops that run through this STP can be
recognized.
The check method can also always be active.
Another possibility is comprised in making the initiation of correction
1 o measures dependent of the evaluation of the (relative) probability that
the possible
loop could be employed. These information can be made available by the M:RVT
in
the form of priorities of the individual paths constituting the loop.
When a loop to a destination X is recognized in an STP A by the MRVT
or by real-time methods, one can proceed in the following way for breaking the
loop:
a) Breaking the loop "downstream" in that the speciific departing path to this
destination is blocked in the routing table in A. This step can, in
particular, be
implemented when other paths to X are also available proceeding from A. In
this
case, it is recommendable to also check the route employed as an alternative
for the
occurrence of a loop. Although the lack of a detection of a loop is no
guarantee that
2 0 there is not some other loop that no longer contains A, there is at least
a probability
that the problem has been eliminated.
b) Alternatively, or if, fo:r example, there no longer happens to an alternate
(loop-free)
route proceeding from A, the loop can be broken "upstream", i.e. to the
preceding
STP B on the loop, in that A sends B a transfer prohibited message with
respect to X.
2 5 In response thereto, B will reroute or, respectively, stop the traffic to
X. Since B will
subsequently periodically review the availability of the route to X via A with
what are
referred to as route set messages, it must be assured that A does not answer
these
messages with a transfer allowed, since B could otherwise re-close the loops.
After final correction of the routing tables by the operating persormel, the
3 0 actions automatically undlertaken by the MTP or the operations maintenance
and
administration part (OMAP) can be in turn reversed by the operating personnel
(Note:

CA 02331706 2000-11-10
4
OMAP comprises higher-ranking SS7 management functions, for example MRVT,
screening functions and measurements. "Informing the operating personnel" is
also
(partially) part of the OMAP)
A special characteristic of the invention is comprised in the mechanism for
breaking loops having the length > 2 with automatic measures that are simple
to
realize upon utilization of existing protocol features. In particular, the
method can
already be employed and is useful when it is realized in only a single STP.
One possibility for realizing the alternative b) is to automatically activate
what is referred to as ILS/DPC screening (ILS = incoming linkset; see Q.705,
~8) in
A for messages from ~ to X. However, a linking of the ILS/DPC screening into
the
MTP management network is needed for this purpose such that an illegal message
is
answered with a TFP message and the route set test messages are also correctly
handled.

Dessin représentatif
Une figure unique qui représente un dessin illustrant l'invention.
États administratifs

2024-08-01 : Dans le cadre de la transition vers les Brevets de nouvelle génération (BNG), la base de données sur les brevets canadiens (BDBC) contient désormais un Historique d'événement plus détaillé, qui reproduit le Journal des événements de notre nouvelle solution interne.

Veuillez noter que les événements débutant par « Inactive : » se réfèrent à des événements qui ne sont plus utilisés dans notre nouvelle solution interne.

Pour une meilleure compréhension de l'état de la demande ou brevet qui figure sur cette page, la rubrique Mise en garde , et les descriptions de Brevet , Historique d'événement , Taxes périodiques et Historique des paiements devraient être consultées.

Historique d'événement

Description Date
Demande non rétablie avant l'échéance 2007-05-04
Le délai pour l'annulation est expiré 2007-05-04
Réputée abandonnée - omission de répondre à un avis sur les taxes pour le maintien en état 2006-05-04
Lettre envoyée 2004-05-07
Requête d'examen reçue 2004-04-28
Toutes les exigences pour l'examen - jugée conforme 2004-04-28
Exigences pour une requête d'examen - jugée conforme 2004-04-28
Inactive : Page couverture publiée 2001-03-07
Inactive : CIB en 1re position 2001-03-04
Inactive : Notice - Entrée phase nat. - Pas de RE 2001-02-22
Lettre envoyée 2001-02-22
Demande reçue - PCT 2001-02-19
Demande publiée (accessible au public) 1999-11-18

Historique d'abandonnement

Date d'abandonnement Raison Date de rétablissement
2006-05-04

Taxes périodiques

Le dernier paiement a été reçu le 2005-04-13

Avis : Si le paiement en totalité n'a pas été reçu au plus tard à la date indiquée, une taxe supplémentaire peut être imposée, soit une des taxes suivantes :

  • taxe de rétablissement ;
  • taxe pour paiement en souffrance ; ou
  • taxe additionnelle pour le renversement d'une péremption réputée.

Les taxes sur les brevets sont ajustées au 1er janvier de chaque année. Les montants ci-dessus sont les montants actuels s'ils sont reçus au plus tard le 31 décembre de l'année en cours.
Veuillez vous référer à la page web des taxes sur les brevets de l'OPIC pour voir tous les montants actuels des taxes.

Historique des taxes

Type de taxes Anniversaire Échéance Date payée
Enregistrement d'un document 2000-10-11
Taxe nationale de base - générale 2000-10-11
TM (demande, 2e anniv.) - générale 02 2001-05-04 2001-04-20
TM (demande, 3e anniv.) - générale 03 2002-05-06 2002-04-30
TM (demande, 4e anniv.) - générale 04 2003-05-05 2003-04-30
TM (demande, 5e anniv.) - générale 05 2004-05-04 2004-04-16
Requête d'examen - générale 2004-04-28
TM (demande, 6e anniv.) - générale 06 2005-05-04 2005-04-13
Titulaires au dossier

Les titulaires actuels et antérieures au dossier sont affichés en ordre alphabétique.

Titulaires actuels au dossier
SIEMENS AKTIENGESELLSCHAFT
Titulaires antérieures au dossier
KLAUS GRADISCHNIG
Les propriétaires antérieurs qui ne figurent pas dans la liste des « Propriétaires au dossier » apparaîtront dans d'autres documents au dossier.
Documents

Pour visionner les fichiers sélectionnés, entrer le code reCAPTCHA :



Pour visualiser une image, cliquer sur un lien dans la colonne description du document (Temporairement non-disponible). Pour télécharger l'image (les images), cliquer l'une ou plusieurs cases à cocher dans la première colonne et ensuite cliquer sur le bouton "Télécharger sélection en format PDF (archive Zip)" ou le bouton "Télécharger sélection (en un fichier PDF fusionné)".

Liste des documents de brevet publiés et non publiés sur la BDBC .

Si vous avez des difficultés à accéder au contenu, veuillez communiquer avec le Centre de services à la clientèle au 1-866-997-1936, ou envoyer un courriel au Centre de service à la clientèle de l'OPIC.

({010=Tous les documents, 020=Au moment du dépôt, 030=Au moment de la mise à la disponibilité du public, 040=À la délivrance, 050=Examen, 060=Correspondance reçue, 070=Divers, 080=Correspondance envoyée, 090=Paiement})


Description du
Document 
Date
(aaaa-mm-jj) 
Nombre de pages   Taille de l'image (Ko) 
Dessin représentatif 2001-03-06 1 15
Dessins 2000-11-09 3 71
Abrégé 2000-11-09 1 10
Description 2000-11-09 4 196
Revendications 2000-11-09 2 87
Rappel de taxe de maintien due 2001-02-19 1 112
Avis d'entree dans la phase nationale 2001-02-21 1 194
Courtoisie - Certificat d'enregistrement (document(s) connexe(s)) 2001-02-21 1 113
Rappel - requête d'examen 2004-01-05 1 123
Accusé de réception de la requête d'examen 2004-05-06 1 176
Courtoisie - Lettre d'abandon (taxe de maintien en état) 2006-06-28 1 175
PCT 2000-11-09 15 573