WO1998059467A2 - Method and device for establishing connections between two subscribers in two different subnetworks - Google Patents

Method and device for establishing connections between two subscribers in two different subnetworks Download PDF

Info

Publication number
WO1998059467A2
WO1998059467A2 PCT/SE1998/001204 SE9801204W WO9859467A2 WO 1998059467 A2 WO1998059467 A2 WO 1998059467A2 SE 9801204 W SE9801204 W SE 9801204W WO 9859467 A2 WO9859467 A2 WO 9859467A2
Authority
WO
WIPO (PCT)
Prior art keywords
gatekeeper
zone
sending
management means
signal
Prior art date
Application number
PCT/SE1998/001204
Other languages
French (fr)
Other versions
WO1998059467A3 (en
Inventor
Theo Kanter
Anders Ryde
Claes Frisk
Anders Christian Svennevik
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Telia Ab
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 Telefonaktiebolaget Lm Ericsson (Publ), Telia Ab filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to AU79499/98A priority Critical patent/AU7949998A/en
Publication of WO1998059467A2 publication Critical patent/WO1998059467A2/en
Publication of WO1998059467A3 publication Critical patent/WO1998059467A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4535—Network directories; Name-to-address mapping using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers

Definitions

  • the present invention relates to the communication between terminals in Internet Protocol (IP) based networks.
  • IP Internet Protocol
  • the Internet is being used to an increasing degree for commercial communication.
  • I- VPN Internet Virtual Private Network
  • a Virtual Private Network may comprise a number of zones, or subnetworks. For example each department in a company may have its own zone, all zones being connected to one large network. Each zone has its own gatekeeper, which holds information about all addresses in its own zone.
  • VPN Virtual Private Network
  • the zone management means holds information about all addresses found in gatekeepers in the VPN and assists in the address resolution within a VPN.
  • - Roaming in the network is supported, that is, users are enabled to move between different terminals and different zones in the network.
  • a private network for audio, video and/or data communication is created, which comprises internal zones and which can cooperate with external clients and location services.
  • the network according to the invention promotes distribution of functionality with respect to TCP/IP.
  • Figure 1 shows a connection between two end users in a zone, assisted by a gatekeeper, according to prior art
  • Figure 2 shows a connection between two end users in different zones, assisted by gatekeepers and a zone management means, according to the invention
  • Figure 3 shows the signalling that takes place when a connection between two end users in different zones is set up, according to the invention
  • Figures 4A and 4B show the signalling that takes place when a new gatekeeper is to be registered and unregistered, respectively, with the zone management means;
  • Figures 5A and 5B show the signalling that takes place when a new endpoint is to be registered, respectively, with the zone management means;
  • Figure 6 illustrates the principles for roaming in the network according to the invention. Detailed Description of Embodiments
  • Figure 1 is a schematic drawing of a connection between two end users 1 in a zone 3 of a private network, assisted by a gatekeeper 5, as common in the art.
  • the gatekeeper 5 holds information about the location of all addresses belonging to its zone, and also sets up connections within the zone.
  • the solution according to the invention may be implemented in any kind of data network.
  • a protocol known as H.323 which is a de facto standard in audio, video and/or data communication, will be used as a basis for the discussion.
  • FIG. 2 is a schematic drawing of a network according to the invention.
  • the network is divided into different zones 13, 13', each zone comprising a gatekeeper 15. 16'.
  • Each end user 11, 11' is connected the gatekeeper 15, 15' of the zone 13, 13 ' to which it belongs.
  • All gatekeepers are connected to one zone management means 17, according to the invention.
  • the zone management means 17 comprises a table 19 of the logical addresses, or alias addresses, of all registered end points in all zones of the network, and the zone in which each end point is registered.
  • the gatekeeper 15 requests the destination from the zone management means 15.
  • the zone management means 17 informs the gatekeeper 15 of the physical location of the end user 11 ' to which the connection is to be set up.
  • the signalling between the gatekeepers 15, 15' of the two networks then proceeds in the way common in the art.
  • FIG. 3 shows the signalling that takes place when an end user 11 in one zone 13 wishes to set up a connection to another end user 11 ' in a different zone 13 ' .
  • the end user 11 who wants to set up a connection to another end user 11 ', sends an Address Request (ARQ) signal to its gatekeeper 15.
  • ARQ Address Request
  • the ARQ signal comprises the following:
  • the destination alias address (the address of the receiving end user 11 ')
  • the Destination Call Signalling Address (normally the address of the receiving end user 11')
  • the gatekeeper 15 sends a Zone Request (Zone RQ) signal comprising the Destination Alias Address of the receiving end user 1 1 ' to the zone management means 17.
  • Zone Request Zone RQ
  • the zone management means 17 responds by sending a Zone Confirmation (Zone CF) signal to the gatekeeper 15, comprising the message
  • the gatekeeper 15 can then send a Location Request (Location RQ) signal to the gatekeeper 15' of the zone to which the receiving end user 11 ' belongs.
  • Location RQ Location Request
  • the gatekeeper 15' responds by sending a Location Confirmation (Location CF) signal to the gatekeeper 15, comprising the Destination Call Signalling Address
  • the gatekeeper 15 responds to the end user 11 with an Address Confirmation (ACF) signal comprising the following information: - the bandwidth available/allocated - the call model to be used
  • ACF Address Confirmation
  • the end user 11 then sends a Setup signal to the gatekeeper 15 comprising the following information
  • the gatekeeper forwards the information in the setup signal to the receiving end user 11 '.
  • the receiving end user 11 ' sends an Address Request (ARQ) signal to its gatekeeper 15', comprising the following information:
  • the gatekeeper 15' responds by sending an Address Confirmation (ACF) signal to the end user 11', comprising the following information
  • the receiving end user 11' then sends a Connect signal to the gatekeeper 15 in the zone of the sending end user 11, comprising the following information:
  • FIG 4A shows the signalling that takes place between a gatekeeper 15, 15' and a zone management means 17 when a new gatekeeper is to be registered with the zone management means 17, if the H.323 protocol is used.
  • the gatekeeper 15, 15' sends a Gatekeeper Registration Request , GK_RRQ, comprising the GatekeeperWellKnownRasAddress, which is the address by which the Gatekeeper 15, 15' is known in the network, to the zone management means 17.
  • the zone management means 17 responds with a Gatekeeper Registration Confirmation, GKJ .CF, signal comprising the Zoneldentifier. which is the identification to be used for the zone of the new gatekeeper, to confirm that the gatekeeper has been registered as a gatekeeper for this zone.
  • FIG 4B shows the signalling that takes place between a gatekeeper 15 and a zone management means 17 when an existing gatekeeper 15 is to be unregistered, that is deleted from the domain of the zone management means 17.
  • the gatekeeper 15 sends a Gatekeeper Unregistration Request, GKJQRQ, to the zone management means 17, comprising the Zoneldentifier.
  • the zone management means 17 responds by sending a Gatekeeper Unregistration Confirmation, GK_UCF, signal back to the gatekeeper 15, comprising the NumberOfEndPointsUnregistered, which indicates how many end points are connected to the gatekeeper 15 that has been unregistered.
  • the GK_UCF signal confirms that the gatekeeper 15, is no longer registered with the zone management means 17.
  • Figure 5 A shows the signalling that takes place between and endpoint, that is a user terminal 11, and a gatekeeper 15, and between a gatekeeper 15 and a zone management means 17, when a new endpoint 11 is to be registered, according to H.323 protocol.
  • the gatekeeper 15 sends an End Point Registration Request, EP_RRQ, signal to the zone management means 17, comprising the following:
  • the zone management means 17 responds to the gatekeeper 15 by sending an End Point Registration Confirmation, EP_RCF, signal, comprising the AliasAddress of the new end point 11.
  • EP_RCF End Point Registration Confirmation
  • the gatekeeper 15 then responds to the new end point 11 with a Registration Confirmation, RCF, signal comprising the following:
  • the new end point 11 has now been registered with the gatekeeper 15 and the zone management means 17.
  • Figure 5B shows the signalling that takes place when an existing endpoint 11 is to be unregistered, that is, now longer to be connected to the gatekeeper 15.
  • EndPointldentifier the identifier of the end point 11 to be unregistered - AliasAddress - the address by which the end point 11 is known in the network
  • the gatekeeper 15 sends an End Point Umegistration Request, EP_URQ, signal to the zone management means 17, comprising the following:
  • the zone management means 17 responds to the gatekeeper 15 by sending an End
  • EPJUCF Point Umegistration Confirmation, EPJUCF, signal, comprising the AliasAddress of the end point 11.
  • the gatekeeper 15 then responds to the new end point 11 with an Unregistration
  • the new end point 11 has now been unregistered from the gatekeeper 15 and the zone management means 17.
  • Figure 6 illustrates the principles for roaming in the network according to the invention, that is, for a person or a terminal to move between zones.
  • a number of end points, 21a, 21b, 21c in a first zone 23 are connected to a first gatekeeper 25.
  • end points 21d, 21e in a second zone 13 ' are connected to a second gatekeeper 25'.
  • Both gatekeepers 25, 25' are connected to a zone management means 27.
  • Each gatekeeper 25, 25' is also connected to a database means 29 and 29' respectively.
  • the database means 29, 29' comprise records of information about the services assigned to each end point 21a,... 2 le in the zone 23, 23 ' to which the database means 29, 29' belongs. Examples of services may be a wake-up call, or the supplementary services as specified in the H.323, such as call redirection.
  • the services are executed in execution means 31 and 31 ' respectively.
  • the logical addresses of all end points or users 21a,...21e - must be unique in the whole network.
  • the most convenient way of assuring this is to include the name of the zone to which the user belongs in the name. In this example this would mean that a user 2 la in the first zone 23 would be identified by its - number (or logical name) together with the number (or logical name) of the zone, for example 23.21a or another well-defined format. The user might keep this name even when he moved to another zone, or the zone name might be changed.
  • the gatekeeper 25' then informs the zone management means 27 that the subscriber is now found in the zone 23 ' of this gatekeeper 25'.
  • the signalling is performed according to Figure 5 A.
  • the user 21a must disconnect from the first gatekeeper 25, as shown in Figure 5B, before connecting to the new gatekeeper 25 '.
  • the zone management means automatically deletes the user 21a from the first gatekeeper 25.
  • the services assigned to the user 21a are stored in the database means 29 connected to tihe first gatekeeper 25.
  • the service records belonging to that user 21a may be moved to the database means 29' connected to the new gatekeeper 25 '.
  • a service When a service is activated, it will then be executed in the execution means 31' of this zone 23 '. It would also be possible to keep the service records in the first database 29. In that case, the execution of the service would be carried out in the execution means 31 of the first zone 23.
  • Moving within one zone may be done in the same way, except that no changes are needed to the services.

Abstract

The present invention relates to a method and an apparatus for establishing connections between tow subscribers in an Internet Protocol (IP) based network, said network being divided into zones, or subnetworks, each zone being managed by a gatekeeper (15, 15'; 25, 25'). All gatekeepers are connected to a zone management means (17; 27), which holds information about the logical addresses of all user terminals (11, 11'). A first user (11) in a first zone (13) managed by a first gatekeeper, who wishes to establish a connection to another user (11') in another zone (13') managed by a second gatekeeper (15') sends a request to the first gatekeeper (15), from which the request is forwarded to the zone management means (17). The zone management means (17) requests the address from the second gatekeeper (15') and returns an address confirmation, so that the connection may be set up.

Description

METHOD AND DEVICE FOR ESTABLISHING CONNECΗONS BETWEEN TWO SUBSCRIBERS IN TWO DIFFERENT SUBNETWORKS
Technical Field
The present invention relates to the communication between terminals in Internet Protocol (IP) based networks.
Background
The Internet is being used to an increasing degree for commercial communication. In particular there is a demand for real-time applications for voice, image and data in decentralized corporate data networks.
With present technology, companies may connect several Intranets and remote users in an Internet Virtual Private Network (I- VPN).
A Virtual Private Network (VPN) may comprise a number of zones, or subnetworks. For example each department in a company may have its own zone, all zones being connected to one large network. Each zone has its own gatekeeper, which holds information about all addresses in its own zone.
There are known solutions for letting end users in a network communicate by means of a gatekeeper within a zone or via a location service, but direct communication between the different gatekeepers is not handled today.
Summarv of the Invention
It is an object of the present invention to provide a Virtual Private Network (VPN) with internal zones, in which direct communication between the different zones is enabled.
It is another object of the invention to enable the roaming between different zones in a VPN. These objects are achieved according to the invention by a zone management means, which is connected to the gatekeepers of all the zones in the VPI.
The zone management means holds information about all addresses found in gatekeepers in the VPN and assists in the address resolution within a VPN.
The solution according to the invention offers the following advantages:
- Roaming in the network is supported, that is, users are enabled to move between different terminals and different zones in the network. - A private network for audio, video and/or data communication is created, which comprises internal zones and which can cooperate with external clients and location services.
- The network according to the invention promotes distribution of functionality with respect to TCP/IP.
Brief Description of the Drawings
Figure 1 shows a connection between two end users in a zone, assisted by a gatekeeper, according to prior art;
Figure 2 shows a connection between two end users in different zones, assisted by gatekeepers and a zone management means, according to the invention;
Figure 3 shows the signalling that takes place when a connection between two end users in different zones is set up, according to the invention;
Figures 4A and 4B show the signalling that takes place when a new gatekeeper is to be registered and unregistered, respectively, with the zone management means; Figures 5A and 5B show the signalling that takes place when a new endpoint is to be registered, respectively, with the zone management means; and
Figure 6 illustrates the principles for roaming in the network according to the invention. Detailed Description of Embodiments
Figure 1 is a schematic drawing of a connection between two end users 1 in a zone 3 of a private network, assisted by a gatekeeper 5, as common in the art. The gatekeeper 5 holds information about the location of all addresses belonging to its zone, and also sets up connections within the zone.
The solution according to the invention may be implemented in any kind of data network. For simplicity, a protocol known as H.323, which is a de facto standard in audio, video and/or data communication, will be used as a basis for the discussion.
Figure 2 is a schematic drawing of a network according to the invention. The network is divided into different zones 13, 13', each zone comprising a gatekeeper 15. 16'. Each end user 11, 11' is connected the gatekeeper 15, 15' of the zone 13, 13 ' to which it belongs. All gatekeepers are connected to one zone management means 17, according to the invention. The zone management means 17 comprises a table 19 of the logical addresses, or alias addresses, of all registered end points in all zones of the network, and the zone in which each end point is registered.
An end user 11 who wishes to establish a connection to another end user 11 ' in a different zone, initiates this by signalling to the gatekeeper 15. The gatekeeper 15 requests the destination from the zone management means 15. The zone management means 17 informs the gatekeeper 15 of the physical location of the end user 11 ' to which the connection is to be set up. The signalling between the gatekeepers 15, 15' of the two networks then proceeds in the way common in the art.
If the H.323 protocol is used, the signalling that takes place will be as shown in more detail in Figures 3, 4A, 4B, 5A and 5B.
Figure 3 shows the signalling that takes place when an end user 11 in one zone 13 wishes to set up a connection to another end user 11 ' in a different zone 13 ' . The end user 11 who wants to set up a connection to another end user 11 ', sends an Address Request (ARQ) signal to its gatekeeper 15. The ARQ signal comprises the following:
- the destination alias address (the address of the receiving end user 11 ') - the Destination Call Signalling Address (normally the address of the receiving end user 11')
- d e Source Alias Address (the address of the end user 11 initiating the connection)
- the Source Call Signalling Address (normally the address of the end user 11 initiating the connection) - the desired bandwidth
- The desired Call Model
The gatekeeper 15 sends a Zone Request (Zone RQ) signal comprising the Destination Alias Address of the receiving end user 1 1 ' to the zone management means 17.
The zone management means 17 responds by sending a Zone Confirmation (Zone CF) signal to the gatekeeper 15, comprising the message
DestinationOkWellKnownRasAddress, which indicates that the address has been located. (RAS Address = Registration Admission and Status Address)
The gatekeeper 15 can then send a Location Request (Location RQ) signal to the gatekeeper 15' of the zone to which the receiving end user 11 ' belongs.
The gatekeeper 15' responds by sending a Location Confirmation (Location CF) signal to the gatekeeper 15, comprising the Destination Call Signalling Address
The gatekeeper 15 responds to the end user 11 with an Address Confirmation (ACF) signal comprising the following information: - the bandwidth available/allocated - the call model to be used
- the destination call signalling address
The end user 11 then sends a Setup signal to the gatekeeper 15 comprising the following information
- bearer capability
- user to user information
The gatekeeper forwards the information in the setup signal to the receiving end user 11 '.
The receiving end user 11 ' sends an Address Request (ARQ) signal to its gatekeeper 15', comprising the following information:
- the destination alias address - the Destination Call Signalling Address
- the Source Alias Address
- the Source Call Signalling Address
- the desired bandwidth
- The desired Call Model
The gatekeeper 15' responds by sending an Address Confirmation (ACF) signal to the end user 11', comprising the following information
- Bandwidth
- Call Model - Destination Call Signalling Address
The receiving end user 11' then sends a Connect signal to the gatekeeper 15 in the zone of the sending end user 11, comprising the following information:
- Transport Address H.245 Control Channel - Destination endpoint Type The gatekeeper 15 forwards the Connect signal to the end user 11.
Figure 4A shows the signalling that takes place between a gatekeeper 15, 15' and a zone management means 17 when a new gatekeeper is to be registered with the zone management means 17, if the H.323 protocol is used. The gatekeeper 15, 15' sends a Gatekeeper Registration Request , GK_RRQ, comprising the GatekeeperWellKnownRasAddress, which is the address by which the Gatekeeper 15, 15' is known in the network, to the zone management means 17. The zone management means 17 responds with a Gatekeeper Registration Confirmation, GKJ .CF, signal comprising the Zoneldentifier. which is the identification to be used for the zone of the new gatekeeper, to confirm that the gatekeeper has been registered as a gatekeeper for this zone.
Figure 4B shows the signalling that takes place between a gatekeeper 15 and a zone management means 17 when an existing gatekeeper 15 is to be unregistered, that is deleted from the domain of the zone management means 17. Again the H.323 protocol is assumed. The gatekeeper 15 sends a Gatekeeper Unregistration Request, GKJQRQ, to the zone management means 17, comprising the Zoneldentifier. The zone management means 17 responds by sending a Gatekeeper Unregistration Confirmation, GK_UCF, signal back to the gatekeeper 15, comprising the NumberOfEndPointsUnregistered, which indicates how many end points are connected to the gatekeeper 15 that has been unregistered. The GK_UCF signal confirms that the gatekeeper 15, is no longer registered with the zone management means 17.
Figure 5 A shows the signalling that takes place between and endpoint, that is a user terminal 11, and a gatekeeper 15, and between a gatekeeper 15 and a zone management means 17, when a new endpoint 11 is to be registered, according to H.323 protocol. First the new endpoint 11 sends a .Registration Request, RRQ, signal to its gatekeeper 15, comprising the following: - CallSignallingAddress - The address of the gatekeeper 15
- RAS_Address - Registration Admission and Status Address
- TerniinalType - The type of terminal connected at the end point 11
- AliasAddress - The address by which the new end point 11 will be known in the network
The gatekeeper 15 sends an End Point Registration Request, EP_RRQ, signal to the zone management means 17, comprising the following:
- EndPointldentifier - identifying the new end point 11 - Zoneldentifier - identifying the zone in which the new end point is found
- AliasAddress - the address by which the new end point will be known in the network
The zone management means 17 responds to the gatekeeper 15 by sending an End Point Registration Confirmation, EP_RCF, signal, comprising the AliasAddress of the new end point 11.
The gatekeeper 15 then responds to the new end point 11 with a Registration Confirmation, RCF, signal comprising the following:
- GK_CallSignalAddress - the address of the gatekeeper - EndPointldentifier - the identifier of the new end point 11
The new end point 11 has now been registered with the gatekeeper 15 and the zone management means 17.
Figure 5B shows the signalling that takes place when an existing endpoint 11 is to be unregistered, that is, now longer to be connected to the gatekeeper 15.
First the new endpoint 11 sends a Unregistration Request, URQ, signal to its gatekeeper 15, comprising the following:
- CallSignallingAddress - the address of the gatekeeper 15
- EndPointldentifier - the identifier of the end point 11 to be unregistered - AliasAddress - the address by which the end point 11 is known in the network The gatekeeper 15 sends an End Point Umegistration Request, EP_URQ, signal to the zone management means 17, comprising the following:
- EndPointldentifier - identifying the new end point 11 - Zoneldentifier - identifying the zone 13 in which the new end point 11 is found
- AliasAddress - the address by which the end point 11 is known in the network
The zone management means 17 responds to the gatekeeper 15 by sending an End
Point Umegistration Confirmation, EPJUCF, signal, comprising the AliasAddress of the end point 11.
The gatekeeper 15 then responds to the new end point 11 with an Unregistration
Confirmation, UCF, signal.
The new end point 11 has now been unregistered from the gatekeeper 15 and the zone management means 17.
Figure 6 illustrates the principles for roaming in the network according to the invention, that is, for a person or a terminal to move between zones. A number of end points, 21a, 21b, 21c in a first zone 23 are connected to a first gatekeeper 25.
Other end points 21d, 21e in a second zone 13 ' are connected to a second gatekeeper 25'. Both gatekeepers 25, 25' are connected to a zone management means 27.
Each gatekeeper 25, 25' is also connected to a database means 29 and 29' respectively. The database means 29, 29' comprise records of information about the services assigned to each end point 21a,... 2 le in the zone 23, 23 ' to which the database means 29, 29' belongs. Examples of services may be a wake-up call, or the supplementary services as specified in the H.323, such as call redirection. The services are executed in execution means 31 and 31 ' respectively.
For roaming to be possible, the logical addresses of all end points or users 21a,...21e - must be unique in the whole network. The most convenient way of assuring this is to include the name of the zone to which the user belongs in the name. In this example this would mean that a user 2 la in the first zone 23 would be identified by its - number (or logical name) together with the number (or logical name) of the zone, for example 23.21a or another well-defined format. The user might keep this name even when he moved to another zone, or the zone name might be changed.
A user 21a who wishes to move from one zone 23 to another 23 ', registers with the gatekeeper 25' in the new zone 23'. The gatekeeper 25' then informs the zone management means 27 that the subscriber is now found in the zone 23 ' of this gatekeeper 25'. The signalling is performed according to Figure 5 A. In one embodiment of the invention, the user 21a must disconnect from the first gatekeeper 25, as shown in Figure 5B, before connecting to the new gatekeeper 25 '. In another embodiment the zone management means automatically deletes the user 21a from the first gatekeeper 25.
The services assigned to the user 21a are stored in the database means 29 connected to tihe first gatekeeper 25. When the user 21a moves to a different zone, the service records belonging to that user 21a may be moved to the database means 29' connected to the new gatekeeper 25 '.When a service is activated, it will then be executed in the execution means 31' of this zone 23 '. It would also be possible to keep the service records in the first database 29. In that case, the execution of the service would be carried out in the execution means 31 of the first zone 23.
Moving within one zone may be done in the same way, except that no changes are needed to the services.

Claims

1. An apparatus (17) for enabling connections between a transmitting (11) and a receiving (11 ') user terminal, each one of said terminals (11, 11 ') being located in an audio, video and/or data communication network, said networks forming zones (13, 13 ') in a larger data communication network, each zone (13, 13') being managed by a gatekeeper (15, 15'), said apparatus being connected to the gatekeepers of at least two zones (13, 13') in the network, characterized in that it comprises: - connections to the gatekeepers (15, 15') of all zones (13, 13 ') in the network
- information about the logical addresses of user terminals (11, 11') found in the different zones (13, 13').
2. An apparatus according to claim 1, characterized in that a subscriber connected to one gatekeeper (15) may register temporarily with another gatekeeper (15').
3. An apparatus according to claim 1 or 2, characterized in that it is adapted for H.323 protocol signalling.
4. A method for establishing a connection between a sending user terminal (11) and a receiving user terminal (I T) each one of said terminals (11, 11') being located in an audio, video and/or data communication network, said networks forming zones (13, 13') of a larger data communication network, each zone (13, 13') being managed by a gatekeeper (15, 15') characterized by the following steps:
- Sending a signal from a first user terminal (11) in a first zone (13) to the gatekeeper (15) of that zone (13), requesting an address for a second user terminal (11') in a second zone (13'); - Requesting information about the second zone (13 ') in which the second user terminal (I T) is found, and the gatekeeper (15') of this zone (13 '), from an apparatus (17) comprising information about all user terminals (11, 11 ');
- Locating the second user terminal (11') in the second zone (13'); - Disconnecting the connection to the zone management means (17);
- Establishing the connection between the first (11) and the second (11') user terminal.
5. A method according to claim 4, characterized in that the signal sent from the first user terminal is an address request signal according to H.323 protocol.
6. A method according to claim 4 or 5, characterized in that the identification of the second zone (13') is carried out in the following steps:
- Sending a zone request signal from the gatekeeper (15) to the zone management means (17);
- Sending a location request signal from the zone management means (17) to the gatekeeper (15') in the zone of the receiving user terminal (11 ');
- Sending a location confirmation signal from the gatekeeper (15') to the zone management means (17); - Sending an address confirmation signal from the zone management means (17) to the gatekeeper (15).
7. A method according to any one of claims 4, 5 or 6, characterized in that the second user teπ inal (11') in the second zone (13 ') is located, and the connection be- tween the first (11) and the second (I T) user terminal is set up, in the following steps:
- Sending a setup signal from the sending end user (11) to the gatekeeper (15), specifying the bearer capability;
- Sending the information in the setup signal from the gatekeeper (15) to the re- ceiving end user (I T); - Sending an address request signal from the receiving end user (11') to its gatekeeper (15');
- Sending an address confirmation signal from the gatekeeper (15') to the end user
- Sending a connect signal from the receiving end user (11') to the gatekeeper of the sending end user (11);
- Forwarding the connect signal from the gatekeeper (15) to the sending end user
8. A network for audio, video and/or data communication characterized in that it comprises a number of subnetworks, or zones (13, 13'), each zone managed by a gatekeeper (15, 15'), and all gatekeepers connected to a zone management means (17) according to any one of claims 1-3.
PCT/SE1998/001204 1997-06-23 1998-06-22 Method and device for establishing connections between two subscribers in two different subnetworks WO1998059467A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU79499/98A AU7949998A (en) 1997-06-23 1998-06-22 Method and device for establishing connections between two subscribers in two different subnetworks

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SE9702384A SE513246C2 (en) 1997-06-23 1997-06-23 Procedure and device in an IP-based network
SE9702384-0 1997-06-23

Publications (2)

Publication Number Publication Date
WO1998059467A2 true WO1998059467A2 (en) 1998-12-30
WO1998059467A3 WO1998059467A3 (en) 1999-04-01

Family

ID=20407466

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE1998/001204 WO1998059467A2 (en) 1997-06-23 1998-06-22 Method and device for establishing connections between two subscribers in two different subnetworks

Country Status (3)

Country Link
AU (1) AU7949998A (en)
SE (1) SE513246C2 (en)
WO (1) WO1998059467A2 (en)

Cited By (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000060894A1 (en) * 1999-04-06 2000-10-12 Nokia Networks Oy Handover in a mobile communication system using conference facility
WO2001005122A1 (en) * 1999-07-12 2001-01-18 Nokia Networks Oy A scheme to relocate h.323 gatekeeper during a call when endpoint changes its zone
WO2001005115A2 (en) * 1999-07-13 2001-01-18 Innomedia Pte Ltd. Voice over internet protocol proxy gateway
WO2001006712A1 (en) * 1999-07-14 2001-01-25 Siemens Information And Communication Networks, Inc. Gatekeeper with several local domains
WO2001011838A1 (en) * 1999-08-11 2001-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Arrangement and method of providing communication between endpoints in a packetbased network using an ip-protocol
EP1085774A2 (en) * 1999-09-16 2001-03-21 AT&T Corp. H.323 Mobility architecture for terminal user and service mobility
EP1089520A2 (en) * 1999-09-28 2001-04-04 AT&T Corp. H.323 User, service and service provider mobility framework for the multimedia intelligent networking
EP1093255A1 (en) * 1999-10-14 2001-04-18 Alcatel Method for connecting a first user-terminal to a second user-terminal, related devices and related software modules
WO2001058091A1 (en) * 2000-02-04 2001-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Communication system, method and controller for routing calls within private networks distributed among geographically distant zones
WO2001080488A2 (en) * 2000-04-12 2001-10-25 Openreach.Com Methods and systems for managing virtual addresses for virtual networks
EP1152581A2 (en) * 2000-05-03 2001-11-07 Siemens Aktiengesellschaft Verfahren zum Sichern der Dienstgüte von Verbindungen zwischen Teilbereichen eines paketorientierten Netzes mit einem Ressourcenmanager
EP1161806A1 (en) * 1999-01-29 2001-12-12 General Instrument Corporation Key management for telephone calls to protect signaling and call packets between cta's
WO2003003660A1 (en) * 2001-06-27 2003-01-09 Hyglo Ab System and method for establishment of virtual private networks using transparent emulation clients
WO2003019862A1 (en) * 2001-08-29 2003-03-06 Huawei Technologies Co., Ltd. A calling method for node across zones in ip network system
WO2003061243A1 (en) * 2002-01-15 2003-07-24 Cisco Technology, Inc. Method and apparatus for dynamically assigning a network endpoint to a network region
KR20030093540A (en) * 2002-06-03 2003-12-11 (주)코스모브리지 System and method for controlling a telephony-communication service based on the internet-network
US6718030B1 (en) 2000-08-10 2004-04-06 Westell Technologies, Inc. Virtual private network system and method using voice over internet protocol
WO2004036332A2 (en) * 2002-10-17 2004-04-29 Nokia Corporation Virtual private network with mobile nodes
US6732177B1 (en) 1999-09-16 2004-05-04 At&T Corp. Intelligent signaling scheme for computer-readable medium for H.323 mobility architecture
US6775255B1 (en) 1999-09-16 2004-08-10 At&T Corp. H.323 mobility architecture for terminal, user and service mobility
US6807422B1 (en) * 1999-11-25 2004-10-19 Nokia Corporation Logical channel control procedures for handover
US6850254B1 (en) 1999-12-02 2005-02-01 International Business Machines Corporation System and method for defining parameter relationship on user interfaces
US6859448B1 (en) 1999-09-16 2005-02-22 At&T Corp. H.323 mobility protocol for terminal, user and service mobility
EP1528750A2 (en) * 2003-07-03 2005-05-04 AT&T Corp. Communications across different virtual private networks
US6947432B2 (en) 2000-03-15 2005-09-20 At&T Corp. H.323 back-end services for intra-zone and inter-zone mobility management
US7218722B1 (en) 2000-12-18 2007-05-15 Westell Technologies, Inc. System and method for providing call management services in a virtual private network using voice or video over internet protocol
WO2007063211A1 (en) * 2005-12-02 2007-06-07 France Telecom Automatic communication initiation system
US7260084B2 (en) 2000-09-29 2007-08-21 Siemens Aktiengesellschaft Method for establishing a connection from a terminal of a communication network to a network-external connection destination, and associated apparatus and network
CN100337460C (en) * 2001-11-09 2007-09-12 日本电气株式会社 Content transmitting system
US7317701B2 (en) 1999-09-28 2008-01-08 At&T Corporation H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US7363381B2 (en) * 2003-01-09 2008-04-22 Level 3 Communications, Llc Routing calls through a network
US7395354B2 (en) 2002-02-21 2008-07-01 Corente, Inc. Methods and systems for resolving addressing conflicts based on tunnel information
USRE42920E1 (en) 2000-05-02 2011-11-15 At&T Intellectual Property Ii, L.P. System and method for inter-domain mobility management
US20150281078A1 (en) * 2012-12-06 2015-10-01 Huawei Technologies Co., Ltd. Method and Apparatus for Cross-Service-Zone Communication, and Data Center Network

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5398242A (en) * 1992-04-07 1995-03-14 Digital Equipment Corporation Automatically configuring LAN numbers
US5437046A (en) * 1993-02-24 1995-07-25 Legent Corporation System and method for resolving the location of a station on a local area network
US5537412A (en) * 1992-07-29 1996-07-16 Sony Corporation Audio-visual network connection system and method using gateways
EP0731582A2 (en) * 1995-03-10 1996-09-11 AT&T IPM Corp. Method and apparatus for interconnecting lans
US5633866A (en) * 1995-11-17 1997-05-27 Bay Networks, Inc. Method and apparatus for routing packets in networks having connection-oriented subnetworks

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2748871B2 (en) * 1994-12-26 1998-05-13 日本電気株式会社 Location registration method and location registration method
JPH08331150A (en) * 1995-06-05 1996-12-13 Fujitsu Ltd Communication system and method therefor

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5398242A (en) * 1992-04-07 1995-03-14 Digital Equipment Corporation Automatically configuring LAN numbers
US5537412A (en) * 1992-07-29 1996-07-16 Sony Corporation Audio-visual network connection system and method using gateways
US5437046A (en) * 1993-02-24 1995-07-25 Legent Corporation System and method for resolving the location of a station on a local area network
EP0731582A2 (en) * 1995-03-10 1996-09-11 AT&T IPM Corp. Method and apparatus for interconnecting lans
US5633866A (en) * 1995-11-17 1997-05-27 Bay Networks, Inc. Method and apparatus for routing packets in networks having connection-oriented subnetworks

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ITU-T STANDARD H. 323, 1996, Paragraph 6.4. *

Cited By (66)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2312791A1 (en) * 1999-01-29 2011-04-20 General Instrument Corporation Key management for telephone calls to protect signaling and call packets between CTA's
EP1161806A1 (en) * 1999-01-29 2001-12-12 General Instrument Corporation Key management for telephone calls to protect signaling and call packets between cta's
EP1161806A4 (en) * 1999-01-29 2009-04-22 Gen Instrument Corp Key management for telephone calls to protect signaling and call packets between cta's
US7929701B1 (en) 1999-01-29 2011-04-19 General Instrument Corporation Multiple level public key hierarchy for performance and high security
WO2000060894A1 (en) * 1999-04-06 2000-10-12 Nokia Networks Oy Handover in a mobile communication system using conference facility
US6985732B1 (en) 1999-04-06 2006-01-10 Nokia Corporation Handover in a mobile communication system using conference facility
WO2001005122A1 (en) * 1999-07-12 2001-01-18 Nokia Networks Oy A scheme to relocate h.323 gatekeeper during a call when endpoint changes its zone
US6674734B1 (en) 1999-07-12 2004-01-06 Nokia Corporation Scheme to relocate H. 323 gatekeeper during a call when endpoint changes its zone
WO2001005115A2 (en) * 1999-07-13 2001-01-18 Innomedia Pte Ltd. Voice over internet protocol proxy gateway
WO2001005115A3 (en) * 1999-07-13 2001-05-03 Innomedia Pte Ltd Voice over internet protocol proxy gateway
WO2001006712A1 (en) * 1999-07-14 2001-01-25 Siemens Information And Communication Networks, Inc. Gatekeeper with several local domains
US6904041B1 (en) 1999-07-14 2005-06-07 Siemens Communications, Inc. System and method for communication domains and subdomains in zones of real time communication systems
GB2367974B (en) * 1999-08-11 2003-10-22 Ericsson Telefon Ab L M Arrangement and method of providing communication between endpoints in a packetbased network using an ip-protocol
WO2001011838A1 (en) * 1999-08-11 2001-02-15 Telefonaktiebolaget Lm Ericsson (Publ) Arrangement and method of providing communication between endpoints in a packetbased network using an ip-protocol
GB2367974A (en) * 1999-08-11 2002-04-17 Ericsson Telefon Ab L M Arrangement and method of providing communication between endpoints in a packetbased network using an ip-protocol
US6732177B1 (en) 1999-09-16 2004-05-04 At&T Corp. Intelligent signaling scheme for computer-readable medium for H.323 mobility architecture
US6775255B1 (en) 1999-09-16 2004-08-10 At&T Corp. H.323 mobility architecture for terminal, user and service mobility
EP1085774A2 (en) * 1999-09-16 2001-03-21 AT&T Corp. H.323 Mobility architecture for terminal user and service mobility
EP1085774A3 (en) * 1999-09-16 2003-01-29 AT&T Corp. H.323 Mobility architecture for terminal user and service mobility
US6859448B1 (en) 1999-09-16 2005-02-22 At&T Corp. H.323 mobility protocol for terminal, user and service mobility
US7317701B2 (en) 1999-09-28 2008-01-08 At&T Corporation H.323 user, service and service provider mobility framework for the multimedia intelligent networking
KR100724294B1 (en) * 1999-09-28 2007-06-04 에이티 앤드 티 코포레이션 H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US7346022B1 (en) 1999-09-28 2008-03-18 At&T Corporation H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US7317703B2 (en) 1999-09-28 2008-01-08 At&T Corporation H.323 user, service and service provider, mobility framework for the multimedia intelligent networking
US7508835B2 (en) 1999-09-28 2009-03-24 At&T Intellectual Property, Ii, L.P. H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US7471686B2 (en) 1999-09-28 2008-12-30 At&T Intellectual Property, Ii, L.P. H.323 user, service and service provider mobility framework for the multimedia intelligent networking
EP1089520A3 (en) * 1999-09-28 2003-06-25 AT&T Corp. H.323 User, service and service provider mobility framework for the multimedia intelligent networking
EP1089520A2 (en) * 1999-09-28 2001-04-04 AT&T Corp. H.323 User, service and service provider mobility framework for the multimedia intelligent networking
EP1959634A1 (en) * 1999-09-28 2008-08-20 AT&T Corp. H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US6944664B1 (en) 1999-10-14 2005-09-13 Alcatel Method for connecting a first user-terminal to a second using-terminal, related devices and related software modules
EP1093255A1 (en) * 1999-10-14 2001-04-18 Alcatel Method for connecting a first user-terminal to a second user-terminal, related devices and related software modules
US6807422B1 (en) * 1999-11-25 2004-10-19 Nokia Corporation Logical channel control procedures for handover
US6850254B1 (en) 1999-12-02 2005-02-01 International Business Machines Corporation System and method for defining parameter relationship on user interfaces
US7356040B2 (en) 2000-02-04 2008-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Communication system, method and controller for routing calls within private networks distributed among geographically distant zones
WO2001058091A1 (en) * 2000-02-04 2001-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Communication system, method and controller for routing calls within private networks distributed among geographically distant zones
US6947432B2 (en) 2000-03-15 2005-09-20 At&T Corp. H.323 back-end services for intra-zone and inter-zone mobility management
WO2001080037A3 (en) * 2000-04-12 2002-05-02 Openreach Com Methods and systems for using names in virtual networks
WO2001080488A2 (en) * 2000-04-12 2001-10-25 Openreach.Com Methods and systems for managing virtual addresses for virtual networks
WO2001080037A2 (en) * 2000-04-12 2001-10-25 Openreach.Com Methods and systems for using names in virtual networks
WO2001080488A3 (en) * 2000-04-12 2002-05-02 Openreach Com Methods and systems for managing virtual addresses for virtual networks
USRE42920E1 (en) 2000-05-02 2011-11-15 At&T Intellectual Property Ii, L.P. System and method for inter-domain mobility management
EP1152581B1 (en) * 2000-05-03 2007-02-21 Siemens Aktiengesellschaft Verfahren zum Sichern der Dienstgüte von Verbindungen zwischen Teilbereichen eines paketorientierten Netzes mit einem Ressourcenmanager
EP1152581A2 (en) * 2000-05-03 2001-11-07 Siemens Aktiengesellschaft Verfahren zum Sichern der Dienstgüte von Verbindungen zwischen Teilbereichen eines paketorientierten Netzes mit einem Ressourcenmanager
US6718030B1 (en) 2000-08-10 2004-04-06 Westell Technologies, Inc. Virtual private network system and method using voice over internet protocol
US7260084B2 (en) 2000-09-29 2007-08-21 Siemens Aktiengesellschaft Method for establishing a connection from a terminal of a communication network to a network-external connection destination, and associated apparatus and network
US7218722B1 (en) 2000-12-18 2007-05-15 Westell Technologies, Inc. System and method for providing call management services in a virtual private network using voice or video over internet protocol
WO2003003660A1 (en) * 2001-06-27 2003-01-09 Hyglo Ab System and method for establishment of virtual private networks using transparent emulation clients
WO2003019862A1 (en) * 2001-08-29 2003-03-06 Huawei Technologies Co., Ltd. A calling method for node across zones in ip network system
US8032638B2 (en) 2001-08-29 2011-10-04 Huawei Technologies Co., Ltd. Calling method for node across zones in IP network system
CN100337460C (en) * 2001-11-09 2007-09-12 日本电气株式会社 Content transmitting system
WO2003061243A1 (en) * 2002-01-15 2003-07-24 Cisco Technology, Inc. Method and apparatus for dynamically assigning a network endpoint to a network region
CN100375483C (en) * 2002-01-15 2008-03-12 思科技术公司 Method and apparatus for dynamically assigning network endpoint to network region
US7072959B2 (en) 2002-01-15 2006-07-04 Cisco Technology, Inc. Method and apparatus for dynamically assigning a network endpoint to a network region for selecting a proper codec
US7395354B2 (en) 2002-02-21 2008-07-01 Corente, Inc. Methods and systems for resolving addressing conflicts based on tunnel information
KR20030093540A (en) * 2002-06-03 2003-12-11 (주)코스모브리지 System and method for controlling a telephony-communication service based on the internet-network
WO2004036332A2 (en) * 2002-10-17 2004-04-29 Nokia Corporation Virtual private network with mobile nodes
WO2004036332A3 (en) * 2002-10-17 2007-12-27 Nokia Corp Virtual private network with mobile nodes
US7363381B2 (en) * 2003-01-09 2008-04-22 Level 3 Communications, Llc Routing calls through a network
EP1528750A3 (en) * 2003-07-03 2005-05-11 AT&T Corp. Communications across different virtual private networks
EP1528750A2 (en) * 2003-07-03 2005-05-04 AT&T Corp. Communications across different virtual private networks
US7313605B2 (en) 2003-07-03 2007-12-25 At&T Corp. Externally controlled reachability in virtual private networks
US9288187B2 (en) 2003-07-03 2016-03-15 At&T Intellectual Property Ii, L.P. Externally controlled reachability in virtual private networks
WO2007063211A1 (en) * 2005-12-02 2007-06-07 France Telecom Automatic communication initiation system
US20150281078A1 (en) * 2012-12-06 2015-10-01 Huawei Technologies Co., Ltd. Method and Apparatus for Cross-Service-Zone Communication, and Data Center Network
EP2922246B1 (en) * 2012-12-06 2019-04-03 Huawei Technologies Co., Ltd. Method and data center network for cross-service zone communication
US11671363B2 (en) * 2012-12-06 2023-06-06 Huawei Technologies Co., Ltd. Method and apparatus for cross-service-zone communication, and data center network

Also Published As

Publication number Publication date
SE513246C2 (en) 2000-08-07
SE9702384L (en) 1998-12-24
AU7949998A (en) 1999-01-04
WO1998059467A3 (en) 1999-04-01
SE9702384D0 (en) 1997-06-23

Similar Documents

Publication Publication Date Title
WO1998059467A2 (en) Method and device for establishing connections between two subscribers in two different subnetworks
US7260084B2 (en) Method for establishing a connection from a terminal of a communication network to a network-external connection destination, and associated apparatus and network
US6421339B1 (en) Methods and systems for call forwarding
US6490275B1 (en) Method and apparatus for improving call setup efficiency in multimedia communications systems
KR100369803B1 (en) Packet voice call service method in wireless telecommunication network and network architecture therefor
EP1334639B1 (en) Optimal gateway discovery while roaming
US6449284B1 (en) Methods and means for managing multimedia call flow
KR100326332B1 (en) Method for communicating between terminal of packet-based network and terminal to be connected through remote access server
JP2003503803A (en) Authentication method and system
JP2001285372A (en) Integrated mobile communication system and method across a plurality of platforms
WO1998059470A2 (en) Method and apparatus to enable a first subscriber in a larger network to retrieve the address of a second subscriber in a virtual private network
US8886242B2 (en) Push-to-talk interworking
US7756142B2 (en) Signaling agent realizing method based on media gateway control protocol
EP1432173B1 (en) A calling method for node across zones in ip network system
US7342905B1 (en) Communications system
EP1317108A1 (en) Call control network, access control server and call control method
KR100401262B1 (en) An apparatus and method for providing a video telephone service over the packet data network
Cisco Cisco High-Performance Gatekeeper
EP1175751A1 (en) Connection management method
KR100539732B1 (en) Call server structure for lan telephony
KR100738195B1 (en) System and method for route optimization in SIP using DHCP
US7903636B2 (en) Method for controlling power characteristics in packet-oriented communication networks
US7583680B1 (en) Method and arrangement for transmitting information between subsystems in hybrid cellular telecommunication systems
CN100391181C (en) Video network and method for implementing video terminal registration in the same network
JP2000151711A (en) Method and device for connecting non-connected terminal to packet switching network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 09469010

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1999504314

Format of ref document f/p: F

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA