WO2001095603A1 - Communication system - Google Patents

Communication system Download PDF

Info

Publication number
WO2001095603A1
WO2001095603A1 PCT/EP2001/006246 EP0106246W WO0195603A1 WO 2001095603 A1 WO2001095603 A1 WO 2001095603A1 EP 0106246 W EP0106246 W EP 0106246W WO 0195603 A1 WO0195603 A1 WO 0195603A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
server
notification
network
attributes
Prior art date
Application number
PCT/EP2001/006246
Other languages
French (fr)
Inventor
Menso Appeldorn
Martin Remco Van Der Werff
Marten De Boer
Original Assignee
Koninklijke Kpn N.V.
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 Koninklijke Kpn N.V. filed Critical Koninklijke Kpn N.V.
Priority to AU2001272447A priority Critical patent/AU2001272447A1/en
Publication of WO2001095603A1 publication Critical patent/WO2001095603A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/537—Arrangements for indicating the presence of a recorded message, whereby the presence information might include a preview or summary of the message
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • 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/4547—Network directories; Name-to-address mapping for personal communications, i.e. using a personal identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • the invention relates to a communication system for sending notification messages from servers, connected to a first network, to user terminals, connected to a second network.
  • a system of this type is more or less known from EP-798899-A1.
  • This patent proposes a communication system in which a notification server sends a notification message to the telephone set of a subscriber as soon as an e-mail message for that subscriber has been received in an e-mail server.
  • the object of the present invention is to provide a broadly applicable service to product and service providers and their customers (users) by means of a notification server that is connected to both the said first network and the said second network and that comprises a database with user identifiers and corresponding user attributes, whereby, if the notification server receives a (first) notification message from the server of such a product or service provider, the notification server determines which user identifier the notification message contains and then sends a second notification message to the user corresponding to the user identifier, with control by the attributes corresponding to that user identifier.
  • the notification server bundles messages originating from product and service providers via the first network and distributes them to the users for whom the messages are intended, making use of attributes specifying the manner in which the message is to be sent to the user, at what time, in which form, etc.
  • the first network i.e. the network by which various servers send notification messages to the notification server, may vary according to the server. For example, while one service/product provider may send messages to the notification server by e-mail, another may do this by fax and a third by X25 or the Internet.
  • the notification server therefore comprises communication means for receiving notification messages from the various servers via these various first networks.
  • the networks via which users receive notification messages from the notification server may vary according to the user.
  • messages may be sent via a mobile telephone network, for example by means of SMS messages or via the fixed network, for example by means of a synthetic voice message.
  • the notification server accordingly comprises communication means for sending notification messages via these various networks to the various user terminals.
  • the database of the notification server which contains the user identifier plus user attributes, may also comprise a server identifier and corresponding server attributes.
  • the notification server will then, moreover, on receipt of a notification message, determine which server identifier the received notification message contains and can then send the notification message to the user, making use of the server attributes.
  • the message to the user can in this way contain form attributes such as logo, accompanying text, etc., thus giving the impression that the message originates directly from the product/service provider.
  • the message can be offered to the user in a personalised form.
  • the server of the provider may comprise a card reader for reading out the user identifier from a user card offered to this card reader.
  • the server of the provider may also comprise a terminal for entering the user identifier and possibly user attributes .
  • the notification server is preferably accessible by the user terminals, via the second network, for reading out or modifying the user attributes.
  • FIG. 1 shows an embodiment of the communication system according to the invention, suitable for sending notification messages from servers 1 of product or service providers, connected to a first network 2 (two of which have been drawn) , to user terminals 3, connected to a second network 4 (three of which have been drawn) .
  • the drawn networks 2 may be different networks, for example an ISDN and a PSTN, or both the same network.
  • the drawn networks 4 can be different networks (ISDN, Internet, GSM, UMTS) or the same.
  • the first networks 2 can be the same as the networks 4 or different.
  • the notification server 5 which is connected to both the first network 2 and the second network 4.
  • the notification server 5 via appropriate means (interfaces) , is adapted to receive or send notification messages via all possible communication means (networks) with the product and service providers and with the customers/users.
  • the notification server 5 comprises a database with user identifiers and corresponding user attributes. These user attributes comprise instructions relating to the conditions, manner, form and time of sending a notification message.
  • the notification server 5 sends such a notification message to a user after the notification server 5 has first received a notification message from a server 1, relating to a relationship between the user and that product or service provider. For example, the user has ordered a product from the provider and the latter sends a message to say that the ordered product has arrived. When placing the order, the customer/user gave his/her user identifier to the provider. As soon as the order arrives, :,he server 1 sends a message to the notification server 5. This message contains the user identifier given by the user to the provider when placing the order.
  • the notification server 5 determines which user identifier the notification message contains and then sends a second notification message to the user corresponding to that user identifier, with control by the attributes corresponding to that user identifier, recorded in the database.
  • These attributes, recorded under the user identifier in the notification server 5, specify amongst other things the type of network 4 via which the (second) notification message is to be given to the user terminal 3, at what time and in which form. For example, messages from provider A must be sent as SMS message via the GSM network to the mobile phone of user B, tel.
  • the user attributes may additionally contain information specifying that the same notification must also be sent via the Internet to the Internet e-mail address, but now complete with the provider attributes and at the earliest possible time.
  • the notification server bundles all the messages from product and service providers and distributes them to the users for whom those messages are intended, making use of attributes specifying how the message should be sent to the user, at what time, in which form, etc.
  • the database of the notification server which contains the user identifier plus attributes, may also comprise a server identifier and corresponding (fixed) server attributes.
  • the notification server determines which server identifier the received notification message contains and can then send the notification message to the user with co-control by those server attributes.
  • the message to the user may contain form attributes, such as logo, accompanying text, etc., giving the impression that the message originates directly from the product/service provider.
  • the message can be offered to the user in a personalised form.
  • the server 1 can comprise a card reader 6 for reading the user identifier from a user card 7 offered to this card reader 6.
  • the user identifier can also be input manually, via a (not drawn) terminal by the provider.
  • the notification server is accessible via the second network 4 by the user terminals 3 for reading out or modifying the user attributes.
  • this reading out and modifying takes place via a data terminal (PC) , but can also take place via a (mobile or fixed) voice terminal, provided that the notification server comprises a voice response (VR) interface for this purpose .
  • PC data terminal
  • VR voice response

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Communication system for sending notification messages from servers (1), connected to a first network (2), to user terminals (3), connected to a second network (4). A notification server (5) is connected to both the first network (2) and the second network (4) and comprises a database with user identifiers and corresponding user attributes. If the notification server (5) receives a first notification message from a server (1), the notification server sends a second notification message to the user on the basis of the user-specific communication-, form- and time-attributes.

Description

Communication system
BACKGROUND OF THE INVENTION
The invention relates to a communication system for sending notification messages from servers, connected to a first network, to user terminals, connected to a second network. A system of this type is more or less known from EP-798899-A1. This patent proposes a communication system in which a notification server sends a notification message to the telephone set of a subscriber as soon as an e-mail message for that subscriber has been received in an e-mail server.
SUMMARY OF THE INVENTION
The object of the present invention is to provide a broadly applicable service to product and service providers and their customers (users) by means of a notification server that is connected to both the said first network and the said second network and that comprises a database with user identifiers and corresponding user attributes, whereby, if the notification server receives a (first) notification message from the server of such a product or service provider, the notification server determines which user identifier the notification message contains and then sends a second notification message to the user corresponding to the user identifier, with control by the attributes corresponding to that user identifier.
The notification server bundles messages originating from product and service providers via the first network and distributes them to the users for whom the messages are intended, making use of attributes specifying the manner in which the message is to be sent to the user, at what time, in which form, etc.
The first network, i.e. the network by which various servers send notification messages to the notification server, may vary according to the server. For example, while one service/product provider may send messages to the notification server by e-mail, another may do this by fax and a third by X25 or the Internet.
The notification server therefore comprises communication means for receiving notification messages from the various servers via these various first networks.
Similarly, the networks via which users receive notification messages from the notification server may vary according to the user. For example, messages may be sent via a mobile telephone network, for example by means of SMS messages or via the fixed network, for example by means of a synthetic voice message. The notification server accordingly comprises communication means for sending notification messages via these various networks to the various user terminals.
The database of the notification server, which contains the user identifier plus user attributes, may also comprise a server identifier and corresponding server attributes. The notification server will then, moreover, on receipt of a notification message, determine which server identifier the received notification message contains and can then send the notification message to the user, making use of the server attributes. For example, the message to the user can in this way contain form attributes such as logo, accompanying text, etc., thus giving the impression that the message originates directly from the product/service provider. Based on the user attributes, such as name, address, etc., the message can be offered to the user in a personalised form.
In order, in the contact between the product or service provider and the consumer (user) , to input the identification code (identifier) and link it to an event to be reported by the provider - via the notification server - to the user, the server of the provider may comprise a card reader for reading out the user identifier from a user card offered to this card reader. As an alternative, the server of the provider may also comprise a terminal for entering the user identifier and possibly user attributes .
The notification server is preferably accessible by the user terminals, via the second network, for reading out or modifying the user attributes.
EMBODIMENTS Figure 1 shows an embodiment of the communication system according to the invention, suitable for sending notification messages from servers 1 of product or service providers, connected to a first network 2 (two of which have been drawn) , to user terminals 3, connected to a second network 4 (three of which have been drawn) . The drawn networks 2 may be different networks, for example an ISDN and a PSTN, or both the same network. This also applies to the networks 4: the drawn networks 4 can be different networks (ISDN, Internet, GSM, UMTS) or the same. In addition, the first networks 2 can be the same as the networks 4 or different. Accordingly, it is an object of the invention to offer a widely applicable service to product and service providers and their customers by means of a notification server 5 which is connected to both the first network 2 and the second network 4. By drawing the networks 2 and 4 as separate networks, it is emphasised that the notification server 5, via appropriate means (interfaces) , is adapted to receive or send notification messages via all possible communication means (networks) with the product and service providers and with the customers/users.
The notification server 5 comprises a database with user identifiers and corresponding user attributes. These user attributes comprise instructions relating to the conditions, manner, form and time of sending a notification message. The notification server 5 sends such a notification message to a user after the notification server 5 has first received a notification message from a server 1, relating to a relationship between the user and that product or service provider. For example, the user has ordered a product from the provider and the latter sends a message to say that the ordered product has arrived. When placing the order, the customer/user gave his/her user identifier to the provider. As soon as the order arrives, :,he server 1 sends a message to the notification server 5. This message contains the user identifier given by the user to the provider when placing the order. As soon as the notification server 5 receives a notification message from the server 1 of such a product or service provider, the notification server determines which user identifier the notification message contains and then sends a second notification message to the user corresponding to that user identifier, with control by the attributes corresponding to that user identifier, recorded in the database. These attributes, recorded under the user identifier in the notification server 5, specify amongst other things the type of network 4 via which the (second) notification message is to be given to the user terminal 3, at what time and in which form. For example, messages from provider A must be sent as SMS message via the GSM network to the mobile phone of user B, tel. 06 , not before 5 p.m., without displaying any attributes that may originate from the provider (since these are not very suitable for an SMS message) . The user attributes may additionally contain information specifying that the same notification must also be sent via the Internet to the Internet e-mail address, but now complete with the provider attributes and at the earliest possible time.
Thus, the notification server bundles all the messages from product and service providers and distributes them to the users for whom those messages are intended, making use of attributes specifying how the message should be sent to the user, at what time, in which form, etc.
The database of the notification server, which contains the user identifier plus attributes, may also comprise a server identifier and corresponding (fixed) server attributes. On receipt of a notification message, the notification server determines which server identifier the received notification message contains and can then send the notification message to the user with co-control by those server attributes. For example, the message to the user may contain form attributes, such as logo, accompanying text, etc., giving the impression that the message originates directly from the product/service provider. Based on the user attributes, such as name, address, etc., the message can be offered to the user in a personalised form. ("Dear Mr. J., we are pleased to inform you that the garden bench you ordered has arrived. Yours sincerely, The Garden Gnome Ltd."). In order, in the contact between the product or service provider and the consumer (user) , to input the identification code (identifier) and to link it to an event (here the arrival of the ordered product) to be reported by the provider - via the notification server - to the user, the server 1 can comprise a card reader 6 for reading the user identifier from a user card 7 offered to this card reader 6. Alternatively, the user identifier can also be input manually, via a (not drawn) terminal by the provider. The notification server is accessible via the second network 4 by the user terminals 3 for reading out or modifying the user attributes. Preferably, this reading out and modifying takes place via a data terminal (PC) , but can also take place via a (mobile or fixed) voice terminal, provided that the notification server comprises a voice response (VR) interface for this purpose .

Claims

1. Communication system for sending notification messages from servers (1) , connected to a first network (2) , to user terminals (3), connected to a second network (4), CHARACTERIZED BY a notification server (5) that is connected to both the first network (2) and the second network (4) and that comprises a database with user identifiers and corresponding user attributes, whereby, if the notification server (5) receives a first notification message from a server (1) , the notification server determines which user identifier the notification message contains and then sends a second notification message to the user corresponding to the user identifier, with control by the attributes corresponding to that user identifier.
2. Communication system according to claim 1, CHARACTERIZED IN THAT the first network (1) , by which various servers (1) send notification messages to the notification server (5) , varies according to the server, and that the notification server comprises communication means for receiving notification messages from the various servers via these various first networks.
3. Communication system according to claim 1, CHARACTERIZED IN THAT the second network (4) , by which various user terminals (3) receive notification messages from the notification server (5) , varies according to the user terminal, and that the notification server comprises communication means for sending notification messages to the various user terminals via the various second networks .
4. Communication system according to claim 1, CHARACTERIZED IN THAT the database of the notification server also contains a server identifier and corresponding server attributes, and the notification server, on receipt of a notification message, determines which server identifier the received notification message contains and sends the second notification message to the user, with co-control by those server attributes.
5. Communication system according to claim 1, CHARACTERIZED IN THAT a said server (1) comprises a card reader (6) for reading out the user identifier from a user card (7) which is offered to the card reader.
6. Communication system according to claim 1 or 5, CHARACTERIZED IN THAT a said server (1) comprises a terminal (8) for inputting the user identifier or user attributes.
7. Communication system according to claim 1, CHARACTERIZED IN THAT the notification server (5) is accessible by the user terminals
(3) via the second network (4) for reading out or modifying the user attributes.
PCT/EP2001/006246 2000-06-07 2001-06-01 Communication system WO2001095603A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001272447A AU2001272447A1 (en) 2000-06-07 2001-06-01 Communication system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NL1015393 2000-06-07
NL1015393A NL1015393C2 (en) 2000-06-07 2000-06-07 Communication system.

Publications (1)

Publication Number Publication Date
WO2001095603A1 true WO2001095603A1 (en) 2001-12-13

Family

ID=19771509

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2001/006246 WO2001095603A1 (en) 2000-06-07 2001-06-01 Communication system

Country Status (3)

Country Link
AU (1) AU2001272447A1 (en)
NL (1) NL1015393C2 (en)
WO (1) WO2001095603A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2104318A1 (en) * 2008-03-21 2009-09-23 Koninklijke KPN N.V. Notification service

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0750265A1 (en) * 1995-06-20 1996-12-27 Matsushita Electric Industrial Co., Ltd. Data retrieval apparatus, evaluation entry apparatus and sensibility entry apparatus
US5742905A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
WO1999017521A1 (en) * 1997-09-30 1999-04-08 Siemens Aktiengesellschaft Method for announcing a message to a subscriber
US5982856A (en) * 1994-09-16 1999-11-09 Octel Communications Corporation Network-based multimedia communications and directory system and method of operation
WO1999065256A2 (en) * 1998-06-10 1999-12-16 Logica, Inc. System and method for delivering e-mail notification to mobile phones
WO2000067436A1 (en) * 1999-05-03 2000-11-09 Infoactive, Inc. Unified messaging system

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5982856A (en) * 1994-09-16 1999-11-09 Octel Communications Corporation Network-based multimedia communications and directory system and method of operation
US5742905A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
EP0750265A1 (en) * 1995-06-20 1996-12-27 Matsushita Electric Industrial Co., Ltd. Data retrieval apparatus, evaluation entry apparatus and sensibility entry apparatus
WO1999017521A1 (en) * 1997-09-30 1999-04-08 Siemens Aktiengesellschaft Method for announcing a message to a subscriber
WO1999065256A2 (en) * 1998-06-10 1999-12-16 Logica, Inc. System and method for delivering e-mail notification to mobile phones
WO2000067436A1 (en) * 1999-05-03 2000-11-09 Infoactive, Inc. Unified messaging system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2104318A1 (en) * 2008-03-21 2009-09-23 Koninklijke KPN N.V. Notification service

Also Published As

Publication number Publication date
NL1015393C2 (en) 2001-12-10
AU2001272447A1 (en) 2001-12-17

Similar Documents

Publication Publication Date Title
EP1523165B1 (en) Internet-based event notification
JP4860750B2 (en) SMS2PSTN Integrated Messaging Service Providing System and Method Using Short / Multimedia Message Service Gateway
US5765033A (en) System for routing electronic mails
CN1823347B (en) Be used to provide a kind of system and method for service
AU749528B2 (en) Method and arrangement for transferring information using an existing message based service in a digital network
CN101180908B (en) Private routing control numbers
WO2003084187A2 (en) Wireless data system
KR20000016304A (en) Method and system for extended addressing plans
US20040086094A1 (en) Method of providing personal event notification during call setup
US20030236769A1 (en) Method and device for mobile communication
WO1998003005A1 (en) Method in telecommunication operating service
CN104184864A (en) Method for Context Sensitive Calling
AU2002351528A1 (en) A system and a method for connecting telephone calls directly on the basis of a text query
US20020123940A1 (en) Method and system for ordering a product or service
US20080242327A1 (en) System and method for sending sms and text messages
KR20070090657A (en) Systen for providing a mobile present and a method the same
KR100436424B1 (en) Method for Providing Information Service to Wireless Terminals, and Information Service System and Messaging Agent System Suitable for the Same
WO2001095603A1 (en) Communication system
US20090270115A1 (en) Receipt Notification of Asynhronous Messages
US8744501B2 (en) System and method for service invocation and response with a communication device based on transmitted code content recognition
US20180359365A1 (en) Server System for Preparation of User-Specific Information for Users in at Least One Com-munication Network
KR20020032460A (en) the voice service provision method which uses a short message service and a automatic response service
CN201057558Y (en) Multimedia service system
GB2390956A (en) Telecommunications services apparatus
KR20060034023A (en) Method and system for providing advertisement service during a period of standing by tele-phone conversation

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP 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 SL TJ TM TR TT TZ UA UG US 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 TR BF BJ CF CG CI CM GA GN GW 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)
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