JP2005159582A - Service method between ip telephone using ip network and general telephone (including isdn), and authentication message format therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a service method capable of call connection between an IP telephone using an IP network and a general telephone (including ISDN), and an authentication message format therefor. <P>SOLUTION: A main server 200 for providing/managing an IP telephone number so that call connection can be made between the IP telephone and the general telephone (including ISDN) via a gateway comprises an authentication server 210 for authenticating whether or not it is a subscriber for each communication start time by an authentication message format. When the subscriber of an IP telephone number presses the number of the general telephone (including ISDN) for call request, a gateway 28 sequentially performs a step of authenticating the subscriber of the IP telephone number by the authentication server to check whether or not the subscriber can enjoy IP telephone service, a step of confirming from the gate keeper after the authentication whether or not a caller is the subscriber of the IP telephone number in the gateway 28 when the subscriber of the IP telephone number calls the general telephone (including ISDN), and a call connection step of making a call to the general telephone (including ISDN) through an usual call connection process after confirming the IP telephone number. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  In the present invention, an IP telephone number provider's main server performs authentication when calling a caller so that a call can be made between an IP telephone using an IP network and a general telephone (including ISDN). The present invention relates to a service method enabling a call connection with a general telephone (including ISDN) and an authentication message format for the service method.

  In general, it has developed from a stage of making a telephone call via a wired network to a stage of making a wireless telephone call via a wireless network, but recently it has reached a stage where it is possible to make a telephone call for both wired and wireless use. At the present time when the Internet is mainstream, the environment has been developed so that calls between Internet terminals can be made.

FIG. 1 is a configuration diagram showing a relationship between a general telephone wired network A and an Internet wired network B. As shown in FIG. 1, a general telephone (including ISDN) wired network A is a general telephone used by a subscriber who subscribes to a switching center 11 that provides a line via a public switched circuit network (PSTN) 1. It has a configuration including 12 (including ISDN).
The Internet wired network B performs Internet communication between the computer 23 connected to the Internet service provider 21 via a dedicated line via the router 22 provided from the Internet service provider (ISP) 12 and the other Internet service provider 21-1. Thus, the packet network 30 that constitutes the Internet network, and the gateway 40 that converts the packet network from the Internet service providers 21 and 21-1 to the network system and connects to the network 1.

  These perform calls between subscribers of general telephones (including ISDN) 12 through the switching center 11, and subscribers who have subscribed to the Internet service provider 21 request subscriber numbers via the Internet service provider 21. Connect. When connecting with a user of the computer 12 via a modem connected to a general telephone (including ISDN) 12, the mail is exchanged by connecting to the computer 23 having the IP via the gateway 40. Alternatively, a call can be made.

On the other hand, as shown in FIG. 2, the wireless network is divided and installed in each area, and a base station 51 that exchanges data with the mobile phone 54, and a base that manages each base station 51 as a certain group. It includes a station 52 and a switching station 53 that summarizes each base station 52 and performs a function of recognizing a customer number and the like, checking a call time and the like, and switching functions.
When the exchange 53 is connected to another exchange 53-1, for example, 017, the exchange 53 converts the data into codes so that they can pass each other by contract.

  FIG. 3 is a block diagram of a system in which wired and wireless networks are combined, and a wireless network C that allows a mobile telephone 54 to make a call via a base station 51, a base station 52, and a wireless mobile telephone switching center 53, and a line A general wired telephone 12 connected via the network 1 is connected to the telephone wired network A through which the user makes a call, and the wired telephone switching center 11 is connected to enable wired / wireless connection. Connect and enable the Internet. The configuration includes an Internet wired network B used by a computer 23 user who subscribes to the Internet service provider 21 as a member, and includes an Internet service provider (21 is an exchange station 11 and a gateway 40 for network conversion.

  On the other hand, as shown in FIG. 4, a network configuration using an Internet terminal has a number of gatekeepers 26 for recognizing IP addresses, such as a computer 23, a Web phone 24, a PC phone 25, and the like. A router 22 that switches to share a gatekeeper line, an Internet service provider 21 that is connected via each router 22, an Internet packet network 30 that is provided via the Internet service provider 21, and a general wired telephone exchange 11 A network 1 for connecting a general telephone (including ISDN) 12 via a mobile phone 54 and a mobile telephone 54 to make a call via a base station 51, a base station center 52, and a wireless mobile telephone switching center 53. 53 is connected to the network 1 and is a general telephone (including ISDN) 2 is connected to the general wired telephone switching center 11 or the wireless mobile telephone switching center 53 and the gatekeeper 26, so that the general network telephone (including ISDN) 12 and the mobile telephone are connected to each other. The gateway 28 functions so that the telephones 12 and 54 and the Internet terminal 28 can be interconnected by mutual conversion of the telephone number 54 and the Internet IP address.

In this case, the gateway 28 simultaneously stores the subscriber IP address of the Internet terminal 29 and the subscriber telephone number using the network 1, and the subscriber telephone number is stored in the OLE (Originating Local Exchange) 11. A desired telephone is called via the (or wireless (mobile) telephone exchange 53) to make a call.
That is, the gateway 28 functions based on the telephone number when connected to the circuit network 1 and interconnects based on the IP address when using the packet network 30 of the Internet network. For this purpose, the gateway 28 is required to store the IP address and the telephone number at the same time. D is a general telephone (including ISDN) network that includes a wired network and a wireless network C that form a circuit network and can be used selectively.

  In order to make a call between the PC phones 25 of the Internet terminal, as shown in FIG. 5, the PC phone 25 requests the IP address authentication of the PC phone 25-1 to the gatekeeper 26 (ARQ) (1) . The gatekeeper 26 compares the IP of the PC phone 25-1 with the built-in data to determine whether it can be connected or not, and notifies the PC phone 25 of the connection (2). Then, the PC phone 25 requests the gatekeeper 26 to set up (3), and the gatekeeper 26 sets up the state of the PC phone 25-1 based on this (4). Next, the PC phone 25-1 requests the gatekeeper 26 for authentication (5), and the gatekeeper 26 accepts this (6). When the acceptance is completed, the PC phone 25 and the PC phone 25-1 are connected to each other (7).

  In this case, the PC phone 25 means an IP phone, and an IP phone (for example, a Web phone) can be fundamentally interconnected via an Internet IP address. However, it is difficult for ordinary people to memorize the IP (address), and the IP changes from time to time in a LAN environment using dynamic IP, so check using a program (for example, the “Get Local Host ()” program). Because there is nothing else, the public cannot understand. Therefore, in this case, it is difficult for a general person to confirm the IP address unless the person has expertise.

  In order to solve such a problem, in IP telephones, an easy-to-remember and convenient number similar to the ordinary telephone (including ISDN) used by ordinary people is given instead of the IP address, and then an actual telephone call is made. At this time, the gatekeeper 26, which is a telephone exchange device of the web phone, uses the mapping table (IP address, IP phone number) to find the IP address of the terminal to be called and transmits it to the web phone, so Play the same role.

  However, according to the recommendation ITU-T, designated items (fields) (E.164 numbers, e-mail numbers, alias numbers) are designated and used by telephone numbers that can be used instead of IP addresses. An example of such a mapping structure is a table as shown in FIG. 10a (having IP address 61, alias name 62, e-mail number 63, telephone number (E.164) 64, and status 65 fields). it can. However, these structures are currently used, and in the case of a Web phone that has not yet been put into practical use, unless it is an expert, it can be determined whether it is a Web phone or an IP phone using only the existing Web phone number. It is difficult for the server to provide the service because it cannot be accurately understood. In addition, a general telephone (including ISDN) user has a different telephone number system from an IP telephone such as a Web telephone and cannot communicate with each other. And, when calling from an ordinary telephone (including ISDN) to an IP telephone, it is impossible to commercialize the service because it is not possible to authenticate whether or not the subscriber is a requirement necessary for adding a charge.

The present invention is to solve such a conventional problem, and its purpose is that an IP telephone user also uses a general telephone (including ISDN) through an authentication process provided by a business operator that operates and manages the IP telephone. It is to provide a service method that enables a telephone call to a person.
Another object of the present invention is to provide a service method that allows a general telephone (including ISDN) user to make a call with an IP telephone through an authentication process provided by a provider operating and managing the IP telephone. It is in.
Still another object of the present invention is to provide an authentication data format that enables a service between an IP telephone user and a general telephone (including ISDN) user, thereby facilitating the authentication. There is in making it possible.

In order to achieve the above object, the present invention provides an authentication server in a main server that manages an IP telephone so that a general telephone (including ISDN) subscriber is authenticated when requesting a call connection to the IP telephone, Once authenticated, it will be able to talk to each other with the help of the main server.
In addition, the present invention creates a standard message format for performing authentication between the gateway and the authentication server, and enables a call upon receiving mutual authentication.

  That is, the present invention is performed by a main server that assigns and manages IP telephone numbers so that IP telephones and ordinary telephones (including ISDN) can be connected via a gateway in a general telephone (including ISDN) network. The main server includes an authentication server that authenticates whether or not the subscriber is in the authentication message format every time a call is started, and when the IP telephone number subscriber presses a general telephone (including ISDN) number to request a call, the gateway In the gateway, the IP phone number subscriber receives the IP phone service or is authenticated from the authentication server, and when the IP phone number subscriber calls the general telephone (including ISDN) number, the caller at the gateway Checking whether or not the phone number is a subscriber from the gatekeeper, and after confirming the IP phone number, a call connection step for making a call to a general telephone (including ISDN) through a normal call connection process Sequentially performed, to provide a service method between IP telephone and ordinary telephone using the IP network (including ISDN).

  The present invention is performed by a main server that assigns and manages an IP telephone number so that an ordinary telephone (including ISDN) and an IP telephone can be connected to each other via a gateway in an ordinary telephone (including ISDN) network. The server includes an authentication server that authenticates whether or not the subscriber is a subscriber at the beginning of a call. When the caller presses the IP phone number carrier identification number, the gateway uses the authentication server to send an ordinary telephone (including ISDN) user to the IP. When the telephone service is received or authenticated, and when the general telephone (including ISDN) user calls the IP telephone number including the IP telephone number identification number of the IP telephone, the gateway calls the IP telephone. IP phone and IP phone using IP network, which sequentially performs a step of confirming whether the number is a gatekeeper and a call connection step of making a call through a normal call connection process after confirming the IP phone number ISDN included Provide service methods.

  In addition, the present invention configures a message format that the main server authenticates in response to a request through the gateway so that a call between a general telephone (including ISDN) and an IP telephone is possible, the message format is an authentication program version field, A source count (SC) field indicating the number of authentication rejection reason data fields included in the message, a type (TYPE) field indicating the type of command message by authentication, a length field indicating the total length of the message, An IP telephone using the IP network and a general telephone (ISDN), which is composed of a telephone number (Caller ID) field of a calling party and a return value (Return Value) field indicating an authentication result by the command as basic fields. Service authentication message format To provide.

  The present invention provides a method for providing a telephone number of a Web telephone to be used in an Internet environment, in which an existing user adds a contract number or sign before a field element based on the recommended ITU-T. Therefore, even if the IP phone address is not known, the Web phone user functions so as to be connected and used with the Web phone number.

  In addition, when a call from an IP phone to a general phone (including ISDN) is requested, the service can be provided only to the subscriber by performing the service authentication procedure for the IP phone subscriber, which is an essential requirement for the service used. User restriction due to the authentication process is utilized as a traffic control method to provide an effect of guaranteeing the call quality Qos. In addition, low-priced telephone service via the IP network (VoIP) becomes possible, and by providing a format for using a message required for authentication in the communication protocol in the form of a communication protocol, the current gateway or the like can be used. Provide a draft standard for required certification procedures.

  In addition, when calling with a regular telephone (including ISDN) via the Internet, it is possible to make a call at a lower price than the existing telephone network, and various additions provided by the Internet network. Services (weather information, securities information, news, e-mail) can also be provided on landlines (including ISDN). Moreover, in the past, it was impossible to make a call with an IP phone unless an IP phone was installed. However, in the present invention, even if the recipient does not install an IP phone, an existing IP phone subscriber can use a regular phone ( When a call request is made to a subscriber (including ISDN), mutual communication with a general telephone (including ISDN) is enabled through authentication of the main server.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
FIG. 6 is a network configuration diagram according to the present invention, and is connected to the authentication server 210 of the main server 200 as an IP telephone service provider via a general telephone (including ISDN) network D and a packet network 30 of the Internet network (IP network). A gateway 28 for processing call setup according to the media communication protocol H.323; a gatekeeper 26 for controlling call authentication, call setup and registration of these entries between the gateway 28 and an Internet terminal 29 such as an IP telephone; The main server 200 controls registration and switching of the terminal 29.

  The main server 200 determines whether or not a general telephone (including ISDN) user via a general telephone (including ISDN) network D is a call permission target for a call with an Internet terminal in an authentication database (IdentifyGWDB). Authentication server 210 that performs authentication in comparison with a database, IP telephone number server 220 that stores IP telephone number data of Internet terminals 29 and ordinary telephones (including ISDN), weather information, securities information, and traffic provided on the Internet It comprises an additional service server 230 that provides additional services such as information. DBs are databases 211, 221 and 231.

  The gatekeeper 26 enables a telephone call to a general telephone (including ISDN) (including wired and wireless telephones 12 and 54) of the switching center 11 subscriber via the gatekeeper 26 of the communication carrier and the media gateway 28-1. The gatekeeper 26 is located in the main server and is connected to a gatekeeper 26 'for each carrier through a circuit network. Each gatekeeper 26' is connected to the wired / wireless telephone 12 via a media gateway 28-1 for each region. , 54 to connect. Since the wired / wireless telephones 12 and 54 are used for call connection via an ordinary communication carrier exchange, etc., they are indicated in abbreviated form.

FIG. 7 is a block diagram showing the internal structure of the gateway 28 according to the present invention. Call setting is performed between the general telephone (including ISDN) D including the line network PSTN and the gatekeeper 26 using the gateway 28. Configure as follows.
The gateway 28 includes a signal unit 28-11 that processes the SS7 protocol of the switching center 11, and a media gateway 28 that includes an MG unit 28-12 that processes media data in the time division data format and transmits the media data to the Internet terminal. -1 and a signal gateway (SG: Signal Gateway) 28-1 that classifies additional services from data via the signal unit 28-11 and call setup data via the single unit 28-11 It includes a gatekeeper 26 and a media gateway controller (MGC) 28-3 that performs a multimedia communication protocol H.323.

  Such a configuration shows a normal gateway configuration, and a product AS5300 manufactured by Cisco, which is generally commercialized, can be cited as an example. The present invention is such that the gateway 28 is controlled by the main server 200 of the present invention shown in FIG. 6 and performs the authentication function of FIG. 9 in order to implement the present invention. 3 was completed according to the present invention.

  FIG. 8 is a call setting procedure diagram for making a call between an ordinary telephone (including ISDN) and an IP telephone using the ordinary telephone (including ISDN) network D and gateway 28 used in the present invention. Then, before performing step S3, an authentication step S20 for receiving authentication through an authentication server is added.

In FIG. 8, in response to a call request from a general telephone (including ISDN) 12, the switching center 11 first queries LNP (Local Number Portability) and sets the SS7 protocol (SS7 Signaling) (protocol Q.931) (step S1). . The exchange OLE 11 transmits an IAM message (ISUP Initial Address Message) to a media gateway controller (VOIP Media Gateway Controller; hereinafter referred to as “MGC”) 28-3 of the gateway 28 via the adjacent exchange 11. In this case, the information included in the IAM includes transmission circuit information (Forward Circuit Information), a carrier identification code (Carrier Identification Code), a receiver number (Called Party Number), and a caller number (Calling Party Number) (step S2). ).
At this time, the MGC 28-3 transmits a message asking whether the service is available to the authentication server 210 of FIG. 6 configured as the main server in the present invention, and receives a serviceIdentify return result message.
Accordingly, the MGC sends a call setting message to the exchange OLE of the caller (step S3).

Next, the type SDP String, which is a media capability message of the exchange OLE, is transmitted as an ACK message from the exchange OLE11 (S4).
A telephone number digit sequence is transmitted (S4-1).
The MGC sends a signal to the caller that a recognition message has been received (S4-2).
The MGC generates a connection message by sending a CRCX message to the called party. That is, at this stage, the MGC sends a setup message to the gatekeeper 26 and performs a protocol H.323 call setup procedure via the IP network (S5).
Thereafter, the call connection ID is selected for the receiver of the called party, and the receiver returns information on the IP address, UDP port, media type, and connection mode (S6).
Then, the MDCX message signal from the MGC reaches the exchange OLE11 (S7).
The exchange OLE then informs the MGC that the notification request message has been accommodated thereby. Therefore, ring back starts (S8).

The MGC sends an RQNT message to the recipient to check the on-hook state (step S9).
Then, the MGC receives an ACK message that the notification request message has been accepted by the recipient (a state where the call is connected) (S10).
The MGC sends an ACM (Address Complete Message) message to the exchange OLE that sent the IAM (step S11).
The receiver transmits an NTFT message to the MGC, which indicates that the telephone is “off-hook” and indicates “Answer” (S12).
Then, MGC reacts with an ACK message (S13).
Then, the MGC sends an RQNT message to the receiver and checks the hang-up state (S14).

Next, the MGC sends this ACK message (S15).
Thereafter, the MGC 28-3 sends an MDCX message signal to the gateway signal unit 28-11, receives the confirmation message ACK, and notifies that the call setup between the recipient and the gateway 28 is completed (S16, S17).
The MGC notifies the exchange OLE 11 that the call has been set up safely by using an ISUP (ANM) message (S18).
Next, the exchange OLE sends a Connect message to the caller (S19).

  FIG. 9 is a flowchart showing an authentication stage of the present invention, which includes an authentication server having an authentication function, a main server for assigning and managing a user number is provided, and the media gate controller 28-3 confirms authentication with the authentication server 210. A message transmission step (S21) for transmitting a serviceIdentify Invoke message for authentication, an authentication processing step (S22) for authenticating whether the user is a subscriber by checking the message in the authentication server 210, and an authentication processing result message (serviceIdentify return) Result message transmission stage (S23) for transmitting result, serviceIdentify return error), and the media gateway controller 28-3 receives the result message, stops the call setup if the result message is an error, and calls if there is a result message It consists of an authentication result processing stage (S24) where the setting continues.

  FIG. 10b is a structural example of a mapping table showing IP telephone numbers according to the present invention. Referring to FIG. 10b, the fields of the present invention have an IP address 61, an alias name 62, an e-mail number 63, a telephone number (E.164) 64, and a status 65 field as in the prior art (FIG. 10a). However, according to the present invention, an additional IP phone recognition adding unit 130 is added to the beginning of the existing element name in the field element configuration obtained by removing the IP address 61 and status 65 fields from the elements constituting each field.

  This additional unit 130 is an IP telephone number that identifies the main server, and an IP telephone number that distinguishes whether or not it is an IP telephone number and an IP telephone number carrier identification number (including characters and / or numbers such as 00Y and 0 **) 110 Recognition numbers (letters and / or numbers, null) 120 are given in order. Preferable examples of the respective identification numbers 110 and 120 constituting the adding unit 130 include numbers (0 to 9) or characters (#, *, null). In this case, if the character is null, it is applied to the IP phone number recognition number 120, which means that it is the same as the existing phone number (TelCo No, Mobile Phone No.) system. Of course, additional characters or symbols can be added to the end of existing telephone number elements as needed. This added number can be expanded to two digits, three digits, etc. in addition to a single digit. Moreover, when a call is made from overseas to the country, or vice versa, it can be recognized as an IP phone number by adding the IP phone recognition numbers or characters before the national number.

  When the IP phone number mapping table is configured in this way, it is authenticated via the main server for mail or phone calls under the Internet environment, and it is possible to connect to subscribers' interconnections or general telephones (including ISDN) Therefore, when the member subscription result and the subscription number are provided from the main server that provides the web phone service, the web phone provider identification number and the phone number including the addition unit for web phone recognition are provided. Since it is possible to immediately confirm whether or not such a telephone number is the telephone number of the Web telephone user, the main server can be connected without knowing the IP address used by the Web telephone user in the Internet environment. By using the authentication, not only the Web telephone subscribers but also the Web telephone users can call the general telephone (including ISDN) users (the reverse order is also possible) and connect easily.

  FIG. 11 shows a message format for authentication between the media gateway controller 28-3 of the gateway 28 and the authentication server 210 of the main server 200 shown in FIGS. This message format includes an authentication program version V field (2 bits), a source count SC field (5 bits) indicating the number of authentication rejection reason data fields included in the message, and a command message type (media) by authentication. Type (TYPE) field (8 bits) indicating message 100 (serviceIdentify Invoke), 101 (serviceIdentify return result), 102 (serviceIdentify return error), 103 (serviceIdentify Reject) generated by gateway controller MGC) 28-3, and message Length field (16 bits) indicating the total length of the caller, Caller ID field (16 bits) of the caller who made the call, and the authentication result (0: Success, 1: Fail, 2) : Authentication server Internal Error) A return value field (8 bits) is sequentially constructed as a basic field.

Next to the Return Value field, a Reason field (32 bits) indicating the reason for rejecting authentication, and a Description field (32 bits) indicating a detailed description of the reason for rejecting authentication in the Reason field. Multiples) are added sequentially.
In the above description, the field V to the field Return Value have a fixed length, and the fields Reason and Description have a variable length.

  FIG. 12 is a state diagram showing the stage of authentication by the authentication server when there is a request from the gateway. The initial state of the authentication server 210 is the idle state (stage), and the general telephone (including ISDN) network D If an authentication request is received from the media gateway controller MGC 28-3 of the gateway 28 in response to the request from, the request is accepted.

  That is, in the step of receiving the authentication, when an authentication request message (service Identity Invoke) NW1 arrives from the gateway 28, the authentication server 210 switches to a standby phase and an idle phase (Idle State) ST1, which switches to an authentication processing phase. The authentication database (IdentifyGWDB) is accessed with the caller ID (Caller ID) transmitted by the request message to determine service availability, and when this determination is completed, the authentication processing stage (Processing State) is switched to the authentication completion stage ST3. When authentication ends successfully with ST2, a serviceIdentify return result (ONW2) or serviceIdentify Reject (ONW1) message is sent out to the gateway after sending out the result. If an error occurs in the authentication process, a serviceIdentify return error (ONW3) message is sent. Create During the authentication completion stage ST3 to be transmitted to the gateway and a certain timeout (TIME-OUT), after waiting for the completion of the authentication work, if the timeout is completed, a message for rejecting the authentication request is created and sent to the gateway, After switching to the activated state ST5, all the support used for authentication is released, returning to the idle state and waiting for another authentication request ST4, and after the step ST3, the authentication server is switched to the idle phase ST1. And an awakening stage ST5 waiting for another authentication request. In the figure, message NW1 is an authentication request message (serviceIdentify Invoke), message ONW1 is an authentication request reject message (serviceIdentify Reject), message ONW2 is an authentication request result message (serviceIdentify return result), and message ONW3 is an authentication request result message (serviceIdentify return error). ) Respectively.

  FIG. 13 is a flowchart for performing the authentication processing stage ST2 performed by the authentication server. When a serviceIdentify Invoke event message is generated from the gateway, the version V (Version) field of this message is compared with the authentication server version, and the caller Check whether the (Caller ID) data conforms to the telephone number (numeric) format (T1, T2, T3) and in a format where the version does not match or the caller (Caller ID) value is valid If not, create a serviceIdentify return error message and transmit it to the gateway (T4, T5), and if the version matches or the caller value is in a valid format, the database used for authentication (IdentifyGWDB) The field value for accessing and determining service availability indicates “1” indicating service availability. (T6, T7) to confirm whether or not, if “1”, a serviceIdentify return result (TYPE = 101) message is created and transmitted to the gateway (T10, T11), “0” If the service period has expired or is not registered in the authentication database, a serviceIdentify Reject (TYPE = 103) message is created. At this time, the reason for rejection and a detailed explanation of the reason are given in the reason field and Steps (T8, T9) for creating in the description field are performed.

  FIG. 14 is a diagram showing an example of the data format of the authentication database (IdentifyGWDB) shown in FIG. 13, which is a database for determining an authentication standard regarding a caller (Caller ID) requested to be authenticated from the gateway. The ID field is the database search criteria, indicating the caller's phone number, the Name field is the name of the caller's applicant, the apply data field is the application date, the due date field is the due date, and the field (valid ) Indicates service availability, and the field (remark) indicates a remarks column.

  FIG. 15 is a state diagram showing authentication in the gateway 28 according to the present invention. At the stage of receiving authentication, an authentication request program (evIdentifyStateChanged ()) from the gateway 28 to the authentication server 210 is additionally performed. When the message (ISUP (IAM) SS7) arrives at the entry point (Entry Point) where the request for authentication starts, the stage (evIdentifyIdle stage) ST11 that moves to the state (evIdentifyNew) ST11 and the message (ISUP (IAM) SS7) The call-back program extracts the caller number from the message IAM, generates a serviceIdentify Invoke message, and sends it to the authentication server (evIdentifyNew stage) ST12, ISUP (IAM ) The SS7 message arrives and the authentication service 210 sends the call service authentication result for the caller. The waiting time is set while waiting for the exchange OLE to send out the CRCX message, and when this time is exceeded, the process moves to this stage (evIdentifyTO) (evIdentifyWaitForOrig stage) ST13, (evIdentifyWaitForOrig stage) When the waiting time elapses in ST13, it moves in this state, ends the authentication procedure, and informs that the message (serviceIdentify Invoke) created in stage (evIdentifyNew) is transmitted to the authentication server 210, Waiting for the result arrival from the authentication server (evIdentifySent stage) ST15, and when the message (serviceIdentify return error) NW3 or (serviceIdentify Reject) NW1 arrives from the authentication server 210 and authentication fails, a NACK message is sent to the exchange OLE , Moving to this stage (evIdentify Idle) (evIdentifyRejected stage) ST16, and authentication server 210 When the service identification return result (NW2) message arrives and the service authentication is performed, the media gateway controller MGC28-3 transmits the CRCX message to the exchange OLE and moves to this stage (evIdentifyIdle) (evIdentifyApproved stage) It consists of ST17.

  The present invention described above is not limited to the above-described embodiments and drawings. Therefore, it will be apparent to those skilled in the art that various substitutions, modifications, and changes can be made without departing from the technical idea of the present invention.

It is a block diagram of a general wired network. 1 is a configuration diagram of a general wireless network. It is a block diagram which shows the structure of a general wired / wireless and internet wired network. It is an illustration of a network configuration using a general Internet terminal. It is a block diagram which shows the procedure which performs general IP authentication via a gatekeeper. It is a network block diagram of this invention. It is an illustration figure of the gateway structure of FIG. It is a call setting procedure diagram of the present invention for making a telephone call between a general telephone (including ISDN) and an IP telephone. 4 is a flowchart of the present invention for performing authentication between a gateway and an authentication server. (A) is a data mapping format representing a general telephone number, and (b) is a telephone number data mapping format for the service of the present invention. It is a message format for authenticating the gateway and authentication server of the present invention. It is a state diagram which authenticates with an authentication server. It is a flowchart which performs authentication processing with the authentication server in this invention. It is an exemplary view of a data format for providing a database to an authentication server in the present invention. It is a state diagram which authenticates with the gateway which comprises this invention.

Explanation of symbols

A ... Telephone wired network B ... Internet wired network C ... Wireless network 1 ... Line network 11 ... Wired telephone exchange 12 ... General telephone (including ISDN)
DESCRIPTION OF SYMBOLS 21 ... Internet service provider 22 ... Router 23 ... Computer 28 ... Gateway 28-1 ... Media gateway 28-2 ... Signal gateway 28-3 ... Media gateway controller 28-11 ... Signal part 28-12 ... MG part 29 ... Internet terminal DESCRIPTION OF SYMBOLS 30 ... Packet network 40 ... Gateway 51 ... Base station 52 ... Base station center 53 ... Switching office 54 ... Mobile telephone 110 ... IP telephone number provider identification number 120 ... IP telephone number identification number 130 ... Addition part 200 ... Main server 210 ... Authentication server 220 ... IP telephone number server 230 ... Additional service server

Claims (7)

This is done by the main server that assigns and manages IP telephone numbers so that IP telephones and ordinary telephones (including ISDN) can be connected via a gateway on the ordinary telephone (including ISDN) network.
The main server includes an authentication server that authenticates whether or not the subscriber is using an authentication message format for each initial call.
When an IP telephone subscriber (caller) presses a general telephone (including ISDN) number to request a call, the gateway receives an IP telephone service or authentication from the authentication server,
Once authenticated, when an IP phone number subscriber calls a landline (including ISDN) number, the gateway checks from the gatekeeper whether the caller is an IP phone number subscriber;
After confirming the IP phone number, the call connection stage for making a call with a regular phone (including ISDN) is performed sequentially through a normal call connection process, and between an IP phone using an IP network and a regular phone (including ISDN) Service method. In the authentication step, when an authentication request message (serviceIdentity Invoke) (service identify invoke) NW1 arrives from the gateway, the authentication server shifts to a standby phase and switches to an authentication processing phase (Idle State) (ST1). )When,
Accessing the authentication database (Identify GWDB) with the caller ID transmitted by the authentication request message to determine service availability, and when this determination is completed, the authentication processing stage switches to the authentication completion stage (ST3) (Processing State) (ST2)
If authentication ends without any problem, create a serviceIdentify return result (ONW2) or serviceIdentify Reject (ONW1) message that sends the result, then send it to the gateway. If an error occurs during the authentication process, create a serviceIdentify return error (ONW3) message Authentication completion stage (ST3) to be transmitted to the gateway,
After waiting for the completion of the authentication work for a certain time-out (TIME-OUT), if the time-out is completed, create a message rejecting the authentication request and send it to the gateway to the awaken stage (ST5) After the conversion, all the support used for authentication is canceled, the standby stage (ST4) waiting for another authentication request after returning to the idle state,
The IP network according to claim 1, wherein after the step (ST3), the authentication server includes an awakening step (ST5) in which the authentication server is switched to the idle step (ST1) and waits for another authentication request. Service method between IP phone and regular phone (including ISDN). In the authentication processing step (ST2), when a serviceIdentify Invoke event message is generated from the gateway, the version V (Version) field of this message is compared with the authentication server version, and the caller ID data is stored in the telephone number (Caller ID). (Numerical) step (T1, T2, T3) to check whether it fits the format;
If the version does not match or the Caller ID value is not in a valid format, a serviceIdentify return error message is created and transmitted to the gateway (T4, T5);
If the versions match or the caller value is in a valid format, the database value used for authentication (Identify GWDB) is accessed, and the field value for determining service availability is “1” indicating service availability. A step of confirming whether or not (T6, T7),
If “1”, a serviceIdentify return result (TYPE = 101) message is created and transmitted to the gateway (T10, T11);
If “0”, the service time has expired or it is not registered in the authentication database, and a serviceIdentify Reject (TYPE = 103) message is created. At this time, the reason for refusal and the detailed explanation of the reason are given. 3. The service method between an IP telephone using an IP network and a general telephone (including ISDN) according to claim 2, wherein the steps (T8, T9) are created in the reason field and the description field. At the time of authentication request stage authentication request, the authentication request function authentication request change (evIdentifyStateChanged ()) from the gateway to the authentication server is additionally performed,
When an ISUP (IAM) SS7 message arrives as an entry point (Entry Point) where a request for authentication starts, an authentication request function includes a stage (evIdentifyIdle stage) (ST11) until a transition to a new state (evIdentifyNew)
The callback function extracts the caller number from the message IAM after the ISUP (IAM) SS7 message arrives and a new authentication request is generated, then creates a serviceIdentify Invoke message and sends it to the authentication server (evIdentifyNew stage) (ST12),
While waiting for the sending of a CRCX message to the switching center OLE while the ISUP (IAM) SS7 message arrives and the authentication server determines the result of the telephone service authentication for the caller (Caller), wait timeout waiting time is set If this time is exceeded, a stage (evIdentifyWaitForOrig stage) (ST13) of moving to a stage (evIdentifyTO),
If the waiting time elapses in the above step (evIdentifyWaitForOrig step) (ST13), it changes in this state, ends the authentication procedure, informs that the serviceIdentify Invoke message created in the evIdentifyNew step has been transmitted to the authentication server, and authenticates Waiting for result arrival from the server (evIdentifySent stage) (ST15);
When a serviceIdentify return error (NW3) or serviceIdentify Reject (NW1) message arrives from the authentication server and authentication fails, a NACK message is sent to the exchange OLE, and the process proceeds to the evIdentify Idle stage (evIdentifiedRejected stage) (ST16);
When the service identification is received from the authentication server and the service authentication is performed, the media gateway controller (MGC) transmits the CRCX message to the exchange OLE and moves to the evIdentifyIdle stage (evIdentifyApproved stage) ( The service method between an IP telephone using an IP network and a general telephone (including ISDN) according to claim 1, characterized in that it comprises: This is done by the main server that assigns and manages IP telephone numbers so that ordinary telephones (including ISDN) and IP telephones can be connected via a gateway on the public telephone (including ISDN) network.
The main server includes an authentication server that authenticates whether or not it is a subscriber for each initial call,
When the caller presses the IP phone number carrier identification number, the gateway receives the IP phone service from the authentication server or receives authentication from the authentication server,
When authenticated, when a general telephone (including ISDN) user calls an IP telephone number including the IP telephone number identification number of the IP telephone, the gateway checks whether the telephone number is the IP telephone number from the gatekeeper. Stages,
A service method between an IP telephone using an IP network and a general telephone (including ISDN), characterized in that after a confirmation of an IP telephone number, a call connection stage for making a call through a normal call connection process is sequentially performed. Configure the message format that the main server authenticates by request through the gateway so that calls can be made between ordinary phones (including ISDN) and IP phones,
The message format is the authentication program version field,
A source count (SC) field indicating the number of authentication rejection reason data fields included in the message;
A type (TYPE) field indicating the type of command message by authentication;
A Length field indicating the total length of the message;
The phone number (Caller ID) field of the caller who made the call,
A service authentication message format between an IP telephone using an IP network and a general telephone (including ISDN), wherein a return value field indicating an authentication result by the command is sequentially configured as a basic field. Next to the Return Value field, a Reason field indicating the reason for rejecting authentication, and
7. A service between an IP telephone using an IP network and a general telephone (including ISDN) according to claim 6, wherein a description field indicating a detailed explanation of the reason for the authentication failure is sequentially added to the reason field. Authentication message format.

Images