JP3814647B2 - Network terminal equipment - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a network terminal device that can more reliably execute self-terminal registration with a gatekeeper.
[0002]
[Prior art]
A recent IP (Internet Protocol) network has become a basic infrastructure not only for the Internet but also for LANs of companies and the like. Since various effects such as a reduction in communication costs and a reduction in management costs can be expected by the IP network, the spread thereof is rapidly progressing. In the network facsimile apparatus, ITU-T Recommendation H.3 which regulates data exchange on the IP network. The protocol according to H.323 is also becoming popular. H. H.323 is a standard for exchanging multimedia data such as image data on an IP network in real time, and its feature is the conventional recommendation H.323 for ISDN. 320 is based on LAN.
[0003]
ITU-T recommendation In an Internet facsimile machine compatible with H.323 (hereinafter simply referred to as “H.323”), preparations for establishing a call with a gatekeeper are made prior to communication. Specifically, ITU-T recommendation H.264. A 225.0 (hereinafter simply referred to as “H.225.0”) protocol is used to exchange a call control address, confirm a network bandwidth for communication, and the like.
[0004]
Usually, H.M. The H.323 terminal needs to set an IP address or the like in the gatekeeper. The registration process of the own terminal to the gatekeeper is performed when the terminal is activated. H. H.323 by a RAS (Registration, Admission and Status) message to the gatekeeper according to H.323. In the procedure in which the H.323 terminal registers itself, the gatekeeper can set TTL (Time To Live) as a member of an RRQ (Registration Request) message.
[0005]
H. When a call operation starts between the H.323 terminal and the gatekeeper, The H.323 terminal exchanges a call establishment request message with the gatekeeper using the call control address acquired in the RAS procedure. When the call is approved, the other registered H.264 is already registered. Negotiation with a H.323 terminal is started, a data encoding method is sent to the terminal, and a communication mode and a communication port are determined.
[0006]
[Problems to be solved by the invention]
By the way, in the gatekeeper, when the TTL is set, the H.D. Some devices do not guarantee the registration of the H.323 terminal (put it in a state where registration can be deleted) or perform registration deletion. In this case, the gatekeeper is H.264. A registration deletion request (URQ: Unregistration Request) is issued to the H.323 terminal to delete the registration. If the registration is deleted from the gatekeeper, the communication start may be rejected when the communication start request (ARQ: Admission Request) is performed next time.
[0007]
Further, there is a possibility that a network delay occurs in communication on the LAN. This network delay causes the gatekeeper or H.264 There are cases where the RAS message from the H.323 terminal does not reach the other party within the prescribed message waiting time (within the message waiting timer). In this case, H.C. The H.323 terminal transmits a message to the gatekeeper again. The RAS message from the H.323 terminal does not reach the gatekeeper.
[0008]
Further, H.C. When the 323 terminal receives an RRJ (Registration Reject) message from the gatekeeper in its own terminal registration procedure and the reason for refusal is Duplicate Aliases, it is necessary to register with the gatekeeper again using the same alias. Even if you try to do it, you will receive an RRJ message with the same rejection reason (duplicate alias).
[0009]
In some cases, the gatekeeper refuses to start communication, and the reason is that the destination is not registered (Called Party Not Registered). The rejection of the start of communication due to the non-registration of the transfer destination is performed by the callee H.264 This means that the H.323 terminal is not registered with the gatekeeper. The H.323 terminal receives the incoming call H.323. There is no choice but to wait for the H.323 terminal to register with the gatekeeper.
[0010]
It is an object of the present invention to provide a network facsimile apparatus that can solve the above-mentioned various problems at once by more surely executing self-terminal registration with a gatekeeper.
[0011]
[Means for Solving the Problems]
The present invention, the own terminal that is connected via a gatekeeper and networks, packet network directly-connected network terminal device for transmitting and receiving image information and executes the own terminal registration process by exchanging RAS messages against the gatekeeper A registration processing execution means; and a storage means for storing a packet survival time (TTL) included in the registration acceptance response when the registration acceptance response is received from the gatekeeper by the own terminal registration processing execution means, and the storage means The self-terminal registration process is re-executed by the self -terminal registration process execution means at least once before the packet survivable time expires.
[0012]
In the network facsimile apparatus of the present invention, the self-terminal registration request (RRQ) is automatically issued again to the gatekeeper before the TTL elapses, that is, while the registration is guaranteed. Can be eliminated.
[0013]
In the network facsimile apparatus of the present invention, when receiving a registration deletion request (URQ) from the gatekeeper at the time of shutdown, user restriction, etc., the self-terminal registration procedure execution means executes the registration deletion procedure once and then arbitrarily The self-terminal registration procedure can be executed again at this timing. Thereby, the unregistered state in the gatekeeper can be shortened.
[0014]
In the network facsimile apparatus of the present invention, the local terminal registration procedure execution means executes the local terminal registration after the next time when there is no response from the gatekeeper due to network delay or the like in the local terminal registration procedure to the gatekeeper. H. It is possible to increase the timeout value of the RAS message specified in 225.0, or to increase the setting value of the retry count of the RAS message. Thereby, even if network delay has occurred, the possibility of self-terminal registration can be increased.
[0015]
In the network facsimile apparatus of the present invention, when the self-terminal registration procedure executing means receives a RAS message of self-terminal registration refusal from the gatekeeper as a response to the self-terminal registration request, when the reason for refusal is an alias overlap, From the next time, when executing the self-terminal registration procedure, the self-terminal registration request is made without specifying the alias, and the alias is assigned by the gatekeeper to obtain the alias, or prepared for preliminary use. The self-terminal registration procedure can be executed by designating the second alias. Thereby, registration refusal due to alias duplication can be prevented.
[0016]
The network facsimile apparatus of the present invention comprises means for storing a first destination alias and a second destination alias as destination aliases, and when the call with the first destination alias fails, the second destination alias is used. Can be called again. As a result, H.has two aliases. It is possible to communicate with the H.323 terminal using any destination alias.
[0017]
In the present invention, a means for storing the mail address of the network administrator is provided, and when the RAS message for refusing the communication start is received from the gatekeeper, if the refusal reason cannot be transferred to the designated destination, the network management It is possible to send an e-mail indicating that the e-mail could not be transferred to the addressee, or to further include the address information in the e-mail. As a result, the H.D. The H.323 terminal can be detected and investigated early, and the registration manager is not registered. It becomes easy to specify the H.323 terminal.
[0018]
DETAILED DESCRIPTION OF THE INVENTION
1 and 2 show an embodiment of a network facsimile apparatus (Internet Aware FAX) according to an embodiment of the present invention and a network system incorporating the facsimile apparatus. In FIG. 1, network facsimile apparatuses 11 and 21 and a gateway are connected to an IP network 100. FIG. 2 is a diagram specifically showing the system of FIG. 1, and LAN 1 and LAN 2, which are also local IP networks, are connected to the Internet 200 as an IP network.
[0019]
The LAN 1 includes an Internet facsimile machine 11, a gatekeeper 12, a hub 13, a computer 14, and a router 15.
As shown in FIG. 3, the Internet facsimile machine 11 includes an operating system (OS) 111, an application program interface (API) 112 that operates on the operating system 111, 232 procedure execution unit 113, RAS execution unit (self-terminal registration procedure execution means in the present invention) 114 capable of executing a RAS procedure, control data storage unit 115, 38 packet control unit 116 and mail transmission control unit 117. Here, the operating system 111 is Winsock (an interface capable of executing the IP protocol at the Windows (registered trademark of US Microsoft Corporation) level).
[0020]
As shown in FIG. 3, the gatekeeper 12 includes an operating system (Winsock) 121, an application program interface 122 that operates on the operating system 121, 232 procedure execution unit 123 and exchange control unit 124 for exchanging transfer data. The gatekeeper 12 is H.264. It is possible to perform multimedia communication conforming to 323V2, and to perform communication with the Internet facsimile apparatus 11 by the RAS procedure for converting an alias into an IP address.
[0021]
In FIG. 2, the hub 13 connects the Internet facsimile machine 11, the gatekeeper 12, the computer 14, and the router 15.
The router 15 is a gateway for connecting the LAN 1 to the Internet 200.
[0022]
The LAN 2 includes an Internet facsimile machine 21, a hub 23, a computer 24, and a router 25. The configuration of the Internet facsimile machine 21 is the same as that of the Internet facsimile machine 11 shown in FIG. The functions of the hub 23, the computer 24, and the router 25 are the same as the functions of the hub 13, the computer 14, and the router 15 of the Internet facsimile machine 11 described above.
[0023]
The Internet facsimile machines 11 and 21 prepare to establish a call with the gatekeeper 12 prior to communication. Specifically, H.C. RAS messages are exchanged according to the 225.0 protocol. The RAS message is exchanged before the logical channel is opened by OLC (Open Logical Channel). By exchanging RAS messages, registration of own terminal information (address, etc.) to the gatekeeper 12 and confirmation of the network bandwidth are performed. When the call establishment request message is exchanged with the gatekeeper 12 and the call is approved, Negotiations between 323 terminals (in the example of FIG. 1 or FIG. 2, Internet facsimile machines 11 and 21) are started, a data encoding method is sent, and a communication mode and a communication port are determined.
[0024]
There are various situations in which registration cannot be performed during registration of the own terminal by the Internet facsimile machine 11 or 21 described above, but the inconvenience at this time can be solved by the processing examples described below.
The Internet facsimile machine 11 in the LAN 1 executes its own terminal registration protocol with the gatekeeper 12 in the same LAN, and the Internet facsimile machine 21 in the LAN 2 communicates with the gatekeeper 12 via the Internet 200. Execute the terminal registration protocol. In the first processing example and the second to sixth processing examples to be described later, a case will be described in which the Internet facsimile machine 11 in the LAN 1 executes a self-terminal registration protocol with the gatekeeper 12 in the same LAN.
[0025]
First, as shown in FIG. 4, in the first processing example of the present invention, prior to communication, the Internet facsimile machine 11 transmits an RRQ (Registration Request) message to the gatekeeper 12 as a self-terminal registration request (S101).
If the gatekeeper 12 approves registration, an RCF (Registration Confirm) message is returned to the Internet facsimile machine 11 as registration approval (S102). If this is not returned, the state before the RRQ transmission is restored. The gatekeeper 12 uses TTL (Time as a member of the RCF message.
To Live) can be set.
[0026]
If the gatekeeper 12 does not set TTL in the RCF message (“No” in S103), the process ends. If the gatekeeper 12 has set TTL in the RCF message (“Yes” in S103), the TTL is stored in a predetermined storage device (memory, register, etc.) (S104). Then, the re-registration timing is set (S105), and it is checked whether or not the re-registration timing has ended (S106). When the re-registration timing has ended ("Yes" in S106), the process returns to S101.
[0027]
In the first processing example, before the TTL expires, the RRQ message is transmitted again to extend the self-terminal registration. As a result, the registration is not deleted from the gatekeeper 12 when the TTL expires, and the unregistered state can be canceled as much as possible.
The second processing example of the present invention shows a case where the gatekeeper 12 returns a URQ (Unregistration Request) message to the Internet facsimile apparatus 11 as a registration deletion request.
[0028]
When the Internet facsimile machine 11 is in its own terminal registration state (S201) and receives a URQ from the gatekeeper 12 (S202), According to H.323, an acceptance response is made with a UCF (UnregistrationConfirm) message (S203). When the UCF message is transmitted, the own terminal information registered in the gatekeeper 12 is deleted.
Thereafter, after waiting for an arbitrary time to elapse (S204), an RRQ message is transmitted again as the self-terminal registration procedure (S205). Thereafter, the processing changes depending on the response of RCF or RRJ. If the RCF is received, the registration is successful, and if the RRJ is received, the registration fails (S206).
[0029]
The third processing example of the present invention shows processing when execution of the RAS procedure is hindered by network delay or packet loss, and arrival of the RAS message is delayed or does not reach. In this case, H.C. The response waiting time (time-out value) of the RAS message specified in 225.0 is extended, or the retry count setting value for RAS message transmission is increased.
A case where the response waiting time (timeout value) of the RAS message is extended will be described with reference to FIG. H. The H.232 procedure execution unit 113 transmits an RRQ to the gatekeeper 12 (S301), and checks whether registration has been accepted, that is, whether an RCF (Registration Confirm) message has been received (S302). If the RCF is received, this process ends. If not received, it is checked whether the number of retries has reached the set number (S303). If not, the process returns to step S301, and again. An RRQ is transmitted and the check in S302 is performed. When the number of retries reaches the set number in the check of step S303, the timeout value is extended (S304A), and after waiting for a predetermined time to pass, an RRQ (Registration Request) message is transmitted to the gatekeeper 12 (S305). ) Thereafter, the process returns to S302, and the same process as described above is repeated.
Accordingly, even after the next time, transmission processing can be performed with a large timeout value when transmitting the RRQ message as the self-terminal registration procedure. When the timeout value is increased, the timeout value can be decreased (for example, returned to the previous state) at an appropriate time.
[0030]
FIG. 6B is a flowchart when the retry count setting value is increased instead of the timeout value. In this case, the step of step S304A can be replaced with step S304B of increasing the retry count setting value. When the RRQ message is transmitted as the self-terminal registration procedure from the next time, the retry count can be increased.
When the number of retries is increased, the number of retries can be reduced (for example, returned to the previous state) at an appropriate time.
[0031]
The gatekeeper 12 checks whether the same alias has already been registered for the alias of the facsimile machine 11 sent as a member of the RRQ message. If the same alias has already been registered, the gatekeeper 12 transmits to the facsimile apparatus 11 an RRJ (Registration Reject) message in which a value indicating a duplicate alias is set as a member. The fourth processing example of the present invention shows processing in this case.
[0032]
As shown in FIG. The 232 procedure execution unit 113 transmits an RRQ to the gatekeeper 12 (S401), and checks whether registration rejection, that is, an RRJ message is received (S402). If the RRJ message has not been received, the process ends. When an RRJ message is received, it is checked whether or not a value indicating a duplicate alias is set in RRJ (S403). If a value indicating a duplicate alias is not set in RRR, the process is passed to S406, which will be described later. If it is set, an RRQ packet without an alias is created (S404A), and this RRQ packet is stored as a gatekeeper 12. (S405). The gatekeeper 12 that has received the RRQ packet without an alias automatically assigns an arbitrary alias to the facsimile apparatus 11. After this, H.C. The 232 procedure execution unit 113 waits for an RCF or RRJ response from the gatekeeper 12 and performs corresponding processing (S406).
[0033]
FIG. 7B is a flowchart for performing self-terminal registration by using the second alias instead of creating an RRQ packet without an alias. In this case, the step of Step S404A is replaced with Step S404B of creating an RRQ packet with the second alias.
[0034]
In the fifth processing example, the facsimile apparatus 11 can handle two aliases (first alias and second alias), and the facsimile apparatus 21 can also handle two aliases (first destination alias and second destination alias). it can. In this case, a case will be described in which the facsimile apparatus 11 makes a re-call when it receives a rejection reason “Called Party Not Registered” from the gatekeeper 12.
[0035]
In FIG. The H.232 procedure execution unit 113 transmits an ARQ (Admission Request) to the gatekeeper 12 as a communication start request (S501). At this time, the first destination alias is set in ARQ. H. The H.232 procedure execution unit 113 checks whether or not a communication start rejection, that is, an ARJ (Admission Rejection) message has been received (S502). If the ARJ message has not been received, the process ends. If an ARJ message is received, it is checked whether or not a value indicating no destination registration is set in ARJ (S503). If the value indicating no destination registration is not set in AJ, the process ends. If it is set, an ARQ packet in which the second destination alias is set is created (S504). Is transmitted to the gatekeeper 12 (S505), and the processing here ends. In this case, if an ARQ request is made again and there is no destination registration, for example, the processing can proceed to a sixth processing example described below.
[0036]
In the sixth processing example, if the ARJ message is received and the reason for refusal is no destination registration, the partner terminal is not registered, so the network administrator's mail address stored in advance is used for communication. A case will be described in which the network administrator is informed by e-mail transmission of the failure. As shown in FIG. The H.232 procedure execution unit 113 transmits an ARQ (Admission Request) to the gatekeeper 12 as a communication start request (S601). At this time, a destination alias is set in ARQ. H. The H.232 procedure execution unit 113 checks whether or not a communication start rejection, that is, an ARJ (Admission Rejection) message has been received (S602). If the ARJ message has not been received, the process ends. When the ARJ message is received, it is checked whether or not a value indicating no destination registration is set in the ARJ (S603). If the destination registration is in the ARJ, the process ends. If there is no registered destination, an email indicating that the destination alias is not registered is transmitted to the network administrator (S604). The process in the sixth process example can be performed in parallel with the process without destination registration in the fifth embodiment.
[0037]
【The invention's effect】
According to the present invention, even when a TTL (Time To Live) time-out, self-terminal registration failure due to network delay, registration refusal due to alias overlap, destination alias non-registration, etc. occur, a re-call is made. In some cases, the possibility of registration is extremely high. If the destination alias is unregistered, the network administrator is notified of this by mail, so that the network administrator can discover terminals that are not registered in the gatekeeper at an early stage.
[Brief description of the drawings]
FIG. 1 is a diagram simply showing a network facsimile apparatus according to an embodiment of the present invention and a network system incorporating the facsimile apparatus.
FIG. 2 is a diagram showing in detail a network facsimile apparatus according to an embodiment of the present invention and a network system in which the facsimile apparatus is incorporated.
3 is a diagram showing a configuration of the facsimile apparatus and the gatekeeper shown in FIGS. 1 and 2. FIG.
FIG. 4 is a flowchart showing a first processing example of the present invention.
FIG. 5 is a flowchart showing a second processing example of the present invention.
FIG. 6 is a flowchart showing a third processing example of the present invention.
FIG. 7 is a flowchart showing a fourth processing example of the present invention.
FIG. 8 is a flowchart showing a fifth processing example of the present invention.
FIG. 9 is a flowchart showing a sixth processing example of the present invention.
[Explanation of symbols]
1, 2 LAN
11, 21 Internet facsimile machine 12 Gatekeeper 13 Hub 14 Computer 15 Router 111, 121 Operating system 112, 122 Application program interface (API)
113, 123 H.I. 232 procedure execution unit 114 RAS execution unit 115 control data storage unit 116 38 packet control unit 117 mail transmission control unit 124 exchange control unit 200 Internet

Claims (6)

In a packet network direct connection type network terminal device that is connected to a gatekeeper via a network and transmits and receives image information,
And own terminal registration process executing means for executing the own terminal registration process by exchanging RAS messages against the gatekeeper, upon receiving the registration acceptance response from the gatekeeper by the self terminal registration process executing means, to the registration acceptance response Storage means for storing the packet survivable time (TTL) included ;
The network terminal device , wherein the own terminal registration process is re-executed by the own terminal registration process execution means at least once before the packet survivable time of the storage means expires. When receiving a registration deletion request (URQ) from the gatekeeper, the own terminal registration process executing means executes the registration deletion process and then executes the own terminal registration process again at an arbitrary timing. The network terminal device according to claim 1. The self-terminal registration process executing means, when executing the self-terminal registration process to the gatekeeper, when there is no response from the gatekeeper, when executing the self-terminal registration from the next time on, the ITU-T recommendation H. 3. The network terminal device according to claim 1, wherein a timeout value of the RAS message defined in 225.0 is increased, or a retry count setting value of the RAS message is increased. When the self-terminal registration process executing means receives a RAS message for refusing self-registration registration from the gatekeeper as a response to the self-terminal registration request, when the reason for refusal is an alias overlap, the self-terminal registration processing means When executing the process , make a local terminal registration request without specifying an alias, obtain an alias by receiving an alias assignment from the gatekeeper, or specify a second alias prepared for preliminary use. The network terminal apparatus according to claim 1, wherein the self-terminal registration process is executed. Means for storing a first destination alias and a second destination alias as destination aliases, and the own terminal registration processing execution means, when calling by the first destination alias fails, sets the second destination alias 5. The network terminal device according to claim 1, wherein the network terminal device is used to make a re-call. Means for storing a mail address of the network administrator, and when the RAS message indicating that the start of communication is rejected from the gatekeeper, if the reason for the rejection is not transferable to the designated destination, The network terminal device according to claim 1, further comprising: transmitting a mail indicating that the mail could not be transferred to the destination, or further including information on the destination in the mail.

Images