+

WO2002011401A1 - Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323 - Google Patents

Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323 Download PDF

Info

Publication number
WO2002011401A1
WO2002011401A1 PCT/US2000/020924 US0020924W WO0211401A1 WO 2002011401 A1 WO2002011401 A1 WO 2002011401A1 US 0020924 W US0020924 W US 0020924W WO 0211401 A1 WO0211401 A1 WO 0211401A1
Authority
WO
WIPO (PCT)
Prior art keywords
endpoints
sub
switching center
internet protocol
call signal
Prior art date
Application number
PCT/US2000/020924
Other languages
English (en)
Inventor
Mahesh Patel
Subrata Mukherjee
Original Assignee
Ericsson, Inc.
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 Ericsson, Inc. filed Critical Ericsson, Inc.
Priority to AU2000265074A priority Critical patent/AU2000265074A1/en
Priority to PCT/US2000/020924 priority patent/WO2002011401A1/fr
Publication of WO2002011401A1 publication Critical patent/WO2002011401A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • 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/50—Address allocation
    • H04L61/5076—Update or notification mechanisms, e.g. DynDNS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1106—Call signalling protocols; H.323 and related
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/30—Network data restoration; Network data reliability; Network data fault tolerance
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention relates generally to telecommunications systems and methods for implementing a cellular system within an H.323 system, and specifically to providing efficient de-registration of multiple mobile stations utilizing H.323 protocols.
  • LANs Local Area Networks
  • H.323 may be integrated into personal computers or implemented in stand-alone devices, such as wireline or wireless endpoints, e.g. , video or audio telephones.
  • H.323 entities can provide real-time audio, video and/or data communications capabilities in point-to-point or multipoint conferences .
  • each H.323 endpoint is registered with a Gatekeeper for the H.323 system.
  • the Gatekeeper stores an Internet Protocol (IP) address for the H.323 endpoint, so that when a connection to that H.323 endpoint is requested, the Gatekeeper will know where to route the connection.
  • IP Internet Protocol
  • the H.323 endpoint is a Mobile Station (MS)
  • MS Mobile Switching Center
  • the IP address for the MS being served by an H.323 system typically includes the IP address for a Mobile Switching Center (MSC) serving the MS along with a specific port number for that MS. Therefore, although each MS has a separate subscriber record within the Gatekeeper, each MS has the same IP address, e.g. , the IP address of the MSC.
  • the routing information the
  • Gatekeeper stores the permanent subscriber information for the MS and routes calls to and from the MS within the H.323 system.
  • MSs also have a subscription with a Home Location Register (HLR) within the H.323 system or within a Public Land Mobile Network (PLMN) that is associated with the H.323 system area. Therefore, when a call to an MS originates from outside the H.323 system, a query to the HLR is performed to determine where to route- the call. If the MS is registered within the H.323 system, the HLR will provide the address for the MSC serving the MS within the H.323 system.
  • HLR Home Location Register
  • PLMN Public Land Mobile Network
  • the HLR When an HLR shuts down and restarts, the HLR typically loses all of the stored location information for each mobile subscriber associated with the HLR. Therefore, the HLR must send a RESET message to each MSC within the PLMN that the HLR is associated with. In response to the RESET message, each MSC must remove each mobile subscriber currently registered with that MSC. Therefore, unless those mobile subscribers perform a location update, calls cannot be made or received by them.
  • the MSC upon receipt of the RESET message, the MSC sends a separate request for de-registration of each mobile subscriber to the Gatekeeper.
  • the H.323 MSC sends a first de-registration request for a first mobile subscriber to the Gatekeeper.
  • the Gatekeeper subsequently de-registers the first mobile subscriber and acknowledges the de-registration of that first mobile subscriber to the MSC.
  • the MSC sends a second de-registration request for a second mobile subscriber to the Gatekeeper.
  • the Gatekeeper subsequently de-registers the second mobile subscriber and acknowledges the de-registration to the MSC. This process continues until the last mobile subscriber served by the MSC is de-registered with the Gatekeeper. It should be understood that the MSC can send the second de- registration request prior to receiving the acknowledgment of de-registration of the first request. However, each de-registration request must be sent separately. This process is extremely inefficient and slow.
  • the present invention is directed to telecommunications systems and methods for de-registering all registered Mobile Stations (MSs) at one time from the Gatekeeper of an H.323 system.
  • MSs Mobile Stations
  • HLR Home Location Register
  • the H.323 Mobile Switching Center (MSC) sends a single Unregistration Request (URQ) message to the Gatekeeper requesting de-registration of all of the registered MSs served by the MSC.
  • URQ Unregistration Request
  • the H.225 protocol for the URQ message is modified to indicate that all MSs associated with the MSC are to be de-registered.
  • the modified URQ message can indicate that a certain group of MSs served by the MSC are to be de-registered.
  • FIGURE 1 is a block diagram of components in an H.323 local area network based upon the Internet Protocol (IP) ;
  • IP Internet Protocol
  • FIGURE 2 is a block diagram of components in an H.323 local area network based upon IP that provides mobile communications;
  • FIGURE 3 illustrates the de-registration of multiple mobile stations from a Gatekeeper within an H.323 system in accordance with preferred embodiments of the present invention;
  • FIGURES 4A-4E illustrate various embodiments of a modified Unregistration Request (URQ) message sent to the Gatekeeper to de-register multiple mobile stations; and
  • UQ Unregistration Request
  • FIGURE 5 is a signaling diagram illustrating the steps for de-registering multiple mobile stations from a Gatekeeper within an H.323 system upon the receipt of a RESET message from a Home Location Register.
  • FIGURE 1 of the drawings A sample H.323 system is shown in FIGURE 1 of the drawings.
  • a first H.323 endpoint 120 which can be, for example, a personal computer or IP telephone, e.g. , by providing a user name and password
  • an H.225 Registration Request (RRQ) message 115 is sent from the first H.323 endpoint 120 to a Gatekeeper 180.
  • the Gatekeeper 180 stores an Internet Protocol (IP) routing address 187 within a subscriber record database 185 for the first H.323 endpoint 120.
  • IP Internet Protocol
  • a second user on a second H.323 endpoint 125 places a call to the first user on the first H.323 endpoint 120, e.g. , by dialing a telephone number or entering a user ID for the first user, the call is routed over the LAN backbone 110 to the Gatekeeper 180, which retrieves the address 187 for the first H.323 endpoint 120 and re-directs the call to the first H.323 endpoint 120.
  • IP voice packets are sent between the first and second H.323 endpoints 120 and 125, respectively, without necessarily being routed through the Gatekeeper 180. If the calling party is within the Public Land
  • PLMN Public Switched Telephone Network
  • PSTN 160 the call is routed to the Gatekeeper 180 throug a Gateway 150, and subsequently to the first H.323 endpoint 120.
  • Voice and data are sent to and from the first H.323 endpoint 120 via the Gateway 150, which converts the voice and data between the IP and the PLMN/PSTN format.
  • speech and data may be routed within the H.323 system 100 and through the Internet 175 via an IP Router 170.
  • the H.323 endpoint is a Mobile Station (MS) 20, such as a cellular telephone
  • the MS 20 can register with the H.323 system 100 through a cellular system 10 within the H.323 system 100 by providing, for example, an International Mobile Subscriber Identity (IMSI) number 122 uniquely identifying the mobile subscriber.
  • the mobile communications system 10 i.e. cellular system
  • the mobile communications system 10 includes a Mobile Switching Center (MSC) 14 for handling mobility management and controlling calls made to and from MSs 20 within the H.323 system 100, a Base Station Controller (BSC) 23 for controlling radio-related functions, such as channel assignment, and at least one A-bis Gateway 140 and associated BTS 24, all of which are connected to the LAN backbone 110.
  • MSC Mobile Switching Center
  • BSC Base Station Controller
  • the BTS 24 is connected to the LAN backbone 110 via the A-bis Gateway 140.
  • the A-bis Gateway 140 converts between circuit-switched signaling and payload used by the BTS 24 and packet-switched signaling and payload used by the H.323 system 100.
  • the BTS 24 operates as a transceiver for transmitting and receiving data and control messages to and from the MS 20 over an air interface.
  • the MSC 14 and BSC 23 can be separate nodes or can be integrated together in one node.
  • the cellular system 10 within the H.323 system 100 may also include a Home Location Register (HLR) 26 for storing location information of the MSs 20, and non-H.323 system-related subscriber information associated with the MSs 20 belonging to the H.323 system 100. It should be understood that the HLR 26 may also be located outside of the H.323 system 100.
  • HLR Home Location Register
  • the Gatekeeper 180 is also responsible for determining whether an H.323 subscriber is currently within the H.323 system 100. Therefore, when an MS 20 wants to register with the H.323 system 100, e.g. , when the MS 20 powers on, the MS 20 transmits a location update message to the BTS 24, which forwards the location update message to the A-bis Gateway 140.
  • the A-bis Gateway 140 converts the location update message into an Internet Protocol (IP) packet for transmission to the MSC 14 via BSC 23.
  • IP Internet Protocol
  • MSC 14 in turn, transmits an H.225 Registration Request
  • RRQ RRQ message 115, which includes a subscriber number and other alias' of the IMSI number 122, such as an e-mail address, to the Gatekeeper 180 over the LAN backbone 110. Thereafter, the Gatekeeper 180 stores routing information 187, e.g. , the IP address for the MSC 14 and an associated port number for the MS 20, within a subscriber record database 185 within the Gatekeeper 180.
  • routing information 187 e.g. , the IP address for the MSC 14 and an associated port number for the MS 20, within a subscriber record database 185 within the Gatekeeper 180.
  • each MS 20 associated with the MSC 14 is registered individually with the Gatekeeper 180, the MSC 14 itself is considered to be an H.323 endpoint. Therefore, in the H.323 architecture, there are multiple sub-endpoints (MSs 20) , controlled by one main endpoint (MSC 14) .
  • the main endpoint (MSC 14) When there is a need to de-register all the sub-endpoints (MSs 20) at one time, such as at H.323 system shut down or upon receiving a RESET message from the HLR 26, the main endpoint (MSC 14) currently must de- register each sub-endpoint (MS 20) from the Gatekeeper 180 one at a time.
  • the MSC 14 can send a single de-registration message 130 to the Gatekeeper 180 requesting de- registration of all MSs 20 associated with that MSC 14.
  • the de-registration message 130 is referred to as an Unregistration Request (URQ) message 130.
  • URQ Unregistration Request
  • This URQ message 130 is sent from the MSC 14 (main endpoint) to the Gatekeeper 180 to indicate that the association between one MS 20 and the Gatekeeper 180 should be broken.
  • This URQ message 130 includes a Call Signal Address 135 that identifies the call signaling address for the MS 20 that is to be de-registered. Since there are multiple MSs 20 associated with the MSC 14, this Call Signal Address 135 typically includes an Internet Protocol (IP) address of the MSC 14 and a specific port number associated with the MS 20.
  • IP Internet Protocol
  • the MSC 14 can send a message to the Gatekeeper 180 indicating that each MS 20 associated with the MSC 14 must be de- registered.
  • the Call Signal Address parameter 135 within the URQ message 130 can be modified to indicate that each MS 20 associated with the MSC 14 must be de-registered.
  • the URQ message 130 as a whole or another parameter within the URQ message 130 could be modified to indicate that all MSs 20 must be de-registered.
  • a new message instead of the URQ message 130, can be sent to the Gatekeeper 180 instructing the Gatekeeper 180 to de-register all MSs 20.
  • the Call Signal Address 135 can include an IP address 132 of the MSC 14 and an indication 134 that all MSs 20 associated with the MSC 14 must be de-registered.
  • This indication 134 can be either a single notation or a range of port numbers, e.g. , port 1 ... port n, associated with the IP address of the MSC 14.
  • the Call Signal Address 135 can include a certain number 138 of the MSs associated with the MSC 14. This may be useful in systems where load sharing is important.
  • the Call Signal Address 135 can include the IP address 132 of the MSC 14, along with a list of port numbers 138, e.g. , port 1 ... port 10. Subsequent URQ messages 130 can include the rest of the port numbers associated with the IP address 132 of the MSC 14.
  • the Call Signal address 135 in a further alternative embodiment, as shown in FIGURE 4C of the drawings, in the situation where a RESET message 145 is received from one HLR 26, but not all of the MSs 20 within the H.323 system 100 are registered with that HLR 26, the Call Signal address 135 can also indicate the specific MSs 20 registered with the HLR 26 that sent the RESET message 145.
  • the MSC 14 could have multiple IP addresses 132 1 -132 n associated therewith.
  • IP address 132 x is associated with the HLR 26 that sends the RESET message 145. Therefore, when the HLR 26 sends the RESET message 145, the MSC 14 can include the IP address 132 x of the MSC 14 that is associated with that HLR 26 and the indication 134 that all MSs 20 associated with that IP address 132 x be de-registered within the URQ message 130 that is sent to the Gatekeeper 180.
  • the HLR 26 is shown within the PLMN/PSTN 160, it should be noted that the HLR 26 could be located within the H.323 system 100.
  • the MSC 14 can maintain a database 15 of all MSs 20 registered with the MSC 14 and their associated HLR's 26. Thereafter, when the RESET message 145 is received from one of these HLRs 26, the Call Signal Address 135 within the URQ message 130 can include the IP address 132 for the MSC 14 and a list 139 of all port numbers associated with the HLR 26 that sent the RESET message 145.
  • the MSC 14 receives the RESET message 145 from the HLR 26 (step 500) , the MSC 14 sends a modified URQ message 130 (step 510) , requesting de-registration of all MSs 20 associated with the MSC 14 and that HLR 26, to the Gatekeeper 180.
  • the modified URQ message 130 can take any of the formats described in FIGURES 4A-4E.
  • the Gatekeeper 180 de-registers all MSs 20 indicated by the MSC 14 from the Gatekeeper's 180 records (step 520). Thereafter, the Gatekeeper 180 sends an Unregistration Confirm (UCF) message to the MSC 14 (step 530) , which acknowledges the de-registration of all of the specified MSs 20.
  • UPF Unregistration Confirm
  • each MS 20 will need to register with the Gatekeeper 180, e.g. , by sending an Update Location message to the MSC 14 (step 540) .
  • the MSC 14 transmits the H.225 Registration Request (RRQ) message to the Gatekeeper 180 (step 550) , which, in turn, stores routing information, e.g.
  • the Gatekeeper 180 sends a registration confirmation message to the MSC 14 confirming the registration of the MS 20 (step 570) .
  • the MSC 14 transmits the update location message to the HLR 26 (step 580) , which stores the address for the MSC 14 within a subscriber record database therein (step 590) .
  • the HLR 26 acknowledges the update location message, to the MSC 14, which in turn acknowledges the update location message to the MS 20 (step 595) .
  • the MS 20 can place and receive calls, and send and receive short messages, as is understood in the art.

Landscapes

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

Abstract

L'invention porte, dans le cadre d'un système de télécommunications, sur un système et un procédé de désenregistrement simultané par le portier d'un système H.323 de toutes les stations mobiles (MS). Dans l'exécution préférée, après l'arrêt du système H.323 ou dès réception d'un message de RàZ d'un HLR, le centre mobile de commutation (MSC) transmet au portier un unique message de demande de désenregistrement (URQ) demandant le désenregistrement de tous les MS desservis par le MSC. Le protocole H.225 des messages URQ est alors modifié pour indiquer que tous les MS associés au MSC sont à désenregistrer. En variante, le message URQ modifié peut indiquer qu'un certain groupe de MS desservi par le MSC est à désenregistrer.
PCT/US2000/020924 2000-07-31 2000-07-31 Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323 WO2002011401A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU2000265074A AU2000265074A1 (en) 2000-07-31 2000-07-31 System and method for de-registration of multiple h.323 end points from a h.323 gatekeeper
PCT/US2000/020924 WO2002011401A1 (fr) 2000-07-31 2000-07-31 Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2000/020924 WO2002011401A1 (fr) 2000-07-31 2000-07-31 Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323

Publications (1)

Publication Number Publication Date
WO2002011401A1 true WO2002011401A1 (fr) 2002-02-07

Family

ID=21741647

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/020924 WO2002011401A1 (fr) 2000-07-31 2000-07-31 Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323

Country Status (2)

Country Link
AU (1) AU2000265074A1 (fr)
WO (1) WO2002011401A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000033518A2 (fr) * 1998-12-03 2000-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000033518A2 (fr) * 1998-12-03 2000-06-08 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede de mise en oeuvre de commutation mobile et de services de lignes collectives dans un reseau a commutation par paquets

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"ETSI TS 100 525 V7.1.0 (2000-01), DIGITAL CELLULAR TELECOMMUNICATIONS SYSTEM (PHASE 2+); RESTORATION PROCEDURES (GSM 03.07 VERSION 7.1.0 RELEASE 1998)", ETSI TECHNICAL SPECIFICATION, January 2000 (2000-01-01), SOPHIA ANTIPOLIS, FRANCE, pages 1 - 21, XP002166478 *
"ITU-T, H.225.0, CALL SIGNALLING PROTOCOLS AND MEDIA STREAM PACKETIZATION FOR PACKET-BASED MULTIMEDIA COMMUNICATION SYSTEMS, CHAPTER 7.1 H.225.0 MESSAGE DEFINITIONS", ITU-T RECOMMANDATION, SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS, INFRASTRUCTURE OF AUDIOVISUAL SERVICES - TRANSMISSION MULTIPLEXING AND SYNCHRONIZATION, September 1999 (1999-09-01), pages 14 - 65, XP002166477 *
"ITU-T, H.323, PACKET BASED MULTIMEDIA COMMUNICATIONSSYSTEMS", ITU-T RECOMMENDATION, SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS, INFRASTRUCTURE OF AUDIOVISUAL SERVICES - SYSTEMS AND TERMINAL EQUIPMENT FOR AUDIOVISUAL SERVICES, September 1999 (1999-09-01), pages 1 - 129, XP002166480 *
HERMAN C. H. RAO, YI-BING LIN, SHENG-LIN CHO: "iGSM: VoIP SERVICE FOR MOBILE NETWORKS", IEEE COMMUNICATIONS MAGAZINE, April 2000 (2000-04-01), pages 62 - 69, XP002166479 *

Also Published As

Publication number Publication date
AU2000265074A1 (en) 2002-02-13

Similar Documents

Publication Publication Date Title
US6314284B1 (en) System and method for providing service transparency for mobile terminating calls within an H.323 system
KR100396643B1 (ko) 무선패킷데이터단말
US7058042B2 (en) One-to-one communication
EP1123626B1 (fr) Passerelle de numero itinerant de protocole internet
US6400950B1 (en) System and method for de-registration of multiple H.323 end points from a H.323 gatekeeper
US20040176128A1 (en) System, mobile communications unit, and softswitch method and apparatus for establishing an Internet Protocol communication link
KR101015642B1 (ko) 헤테로지니어스 네트워크를 통한 데이터 푸쉬 서비스시스템 및 방법
US6603849B2 (en) System and method for call re-direction in H.323 network
KR101332993B1 (ko) 사용자 개시 핸드오프에 기초한 세션 개시 프로토콜(ｓｉｐ)
WO1997026764A1 (fr) Systeme de communications mobiles numerique et procedes de traitement d'un appel de raccordement
JP4418136B2 (ja) 通信システム
EP1238514A1 (fr) Procede et systeme de routage des appels en fonction de la position des appelants dans un reseau ip mobile
US7809839B2 (en) Method and system for call set-up between mobile communication terminals
JP2002543677A (ja) 異種ネットワーク間の相互動作用仮想番号計画
EP1102503B1 (fr) Système integré de téléphonie sur un réseau IP et de communication cellulaire et procedée de fonctionnement
US20030119500A1 (en) System and method for providing terminal mobility in h.323 systems
EP1380182A1 (fr) Communication biunivoque dans le cas d'un systeme disposant d'un plan de controle different et d'entites logiques de plan utilisateur
US20090282155A1 (en) Providing peer-to-peer media
WO2002011401A1 (fr) Systeme et procede de desenregistrement de plusieurs points terminaux h.323 par un portier h.323
KR100501161B1 (ko) 착신제어시스템을 이용한 착신 데이터 로밍 서비스 시스템및 방법
KR100708363B1 (ko) 패킷서비스통지기능이 구비된 더불유씨디엠에이 시스템 및 그 제어방법
KR100538552B1 (ko) 착신제어시스템을 이용한 착신 컨텐츠 정보 표시방법
JP3655224B2 (ja) 移動通信システム、及び呼接続確立方法、並びに、ゲートウェイ装置、及び通信端末装置
KR100501160B1 (ko) 착신제어시스템을 이용한 ｉｍｔ-2000의 동기 망에서비동기 망으로의 착신 데이터 로밍 서비스 시스템 및 방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

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

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ 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 GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
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: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载