JP2009049550A - Gateway device - Google Patents

Gateway device Download PDF

Info

Publication number
JP2009049550A
JP2009049550A JP2007211708A JP2007211708A JP2009049550A JP 2009049550 A JP2009049550 A JP 2009049550A JP 2007211708 A JP2007211708 A JP 2007211708A JP 2007211708 A JP2007211708 A JP 2007211708A JP 2009049550 A JP2009049550 A JP 2009049550A
Authority
JP
Japan
Prior art keywords
session
identification information
communication
importance
communication destination
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
JP2007211708A
Other languages
Japanese (ja)
Other versions
JP2009049550A5 (en
Inventor
Nami Ei
Hiroshi Masukawa
Hitoshi Yoshida
Kazuma Yumoto
均 吉田
博史 桝川
一磨 湯本
波 衛
Original Assignee
Hitachi Ltd
株式会社日立製作所
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 Hitachi Ltd, 株式会社日立製作所 filed Critical Hitachi Ltd
Priority to JP2007211708A priority Critical patent/JP2009049550A/en
Publication of JP2009049550A publication Critical patent/JP2009049550A/en
Publication of JP2009049550A5 publication Critical patent/JP2009049550A5/ja
Application status is Withdrawn legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/14Network-specific arrangements or communication protocols supporting networked applications for session management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/02Network-specific arrangements or communication protocols supporting networked applications involving the use of web-based technology, e.g. hyper text transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/28Network-specific arrangements or communication protocols supporting networked applications for the provision of proxy services, e.g. intermediate processing or storage in the network

Abstract

Even when all of the usable sessions are used, a new session can be connected by disconnecting one of the sessions, and the disconnected session is automatically recovered.
Information on the importance level of a communication session and necessity of recovery is set in advance corresponding to the URI of a communication source terminal and the URI of a communication destination partner, and stored in a session importance level table. For example, when a connection request for a highly important session such as an emergency session is received, the least important one of existing sessions is selected and disconnected. Information on the disconnected communication session (for example, the communication source URI and the communication destination URI) is stored in the session recovery table 140. As soon as the session resource becomes available, the session is automatically recovered according to the communication source URI and communication destination URI stored in the session recovery table 140.
[Selection] Figure 2

Description

  The present invention relates to a gateway device, and more particularly to a gateway device for connecting a specific new session when the number of available sessions is all used.

  In the ISDN network, when line resources are exhausted (both two B channels are used), it is disclosed in Patent Document 1 that a physical line is disconnected to enable a new important call. For example, Patent Document 1 discloses that when a call is determined to be a priority call, a relay contact is opened and a line of an I interface connected to a plurality of ISDN communication terminals is disconnected from the line terminating device. .

In addition, it is known that, for example, other sessions with low priority are disconnected in response to a connection request from a user terminal with high priority (see, for example, Patent Documents 2 to 5).
JP-A-11-266324 JP 2006-148648 A Japanese Patent Laid-Open No. 10-1111853 JP 2003-16031 A JP 2004-187094 A

  In the technique disclosed in Patent Document 1 described above, all the lines that are in use are disconnected without comparing and selecting the communication importance of each line, and lines that do not need to be disconnected are also stopped. For this reason, the efficiency of a communication line may fall. Further, none of the techniques of Patent Documents 1 to 5 considers a method of automatically resuming a disconnected communication and resuming it even when a line is available. For this reason, the user has to manually reconnect.

  Furthermore, when a user terminal with a high priority is still connected, even if a user with a low priority tries to reconnect, the connection of a user with a low priority that has been disconnected may not be permitted. The user has to try again and again. On the other hand, the timing when the user tries to reconnect is irrelevant to the disconnection / release of the session, so there is no time until the user tries to reconnect after the session of another user terminal with a higher priority is disconnected / released. There may be time. Accordingly, the line utilization efficiency decreases.

  In view of the above points, the present invention enables connection of a new session with high importance by disconnecting one of the sessions, even when the number of available sessions is all used, and disconnecting. It is an object of the present invention to provide a gateway device that can automatically recover a session that has been made.

  For example, the present invention selects and disconnects the least-important session among the existing sessions according to the importance of the communication session in which the communication source terminal, the communication partner, and the like are configured as parameters.

  The present invention, for example, stores information on a disconnected communication session in a SIP (Session Initiation Protocol) gateway according to the necessity of reconnection that is set in advance together with the importance level. Reconnected.

  This SIP gateway, for example, is connected to an IP network using SIP, a session monitoring unit that monitors a communication session status in real time, a session control unit that disconnects / connects a session, and is responsible for recovery of a disconnected session Session recovery unit, line control unit for managing communication packet routing, line I / F unit in charge of transfer of communication packet, session status table for storing information on session status during communication, available session resource and consumption status One of the features is a session resource table that stores information on the session, a session importance table that stores importance information on the session, and a session recovery table that stores information on sessions that are disconnected and need to be recovered.

  The SIP gateway is a terminal set to have the highest importance level when all the sessions having the maximum number of sessions specified in the subscription service contract are occupied in the subscriber premises connected to the IP network using SIP. In response to a new session connection request from an emergency call terminal (for example, an emergency call terminal), the existing session with the lowest importance is selected according to the importance of the communication session configured as a parameter of the terminal, communication partner, etc. One of the features is to enable a new session connection by selecting and disconnecting.

The SIP gateway is characterized in that the disconnected existing session is automatically reconnected as soon as the session resource of the SIP gateway becomes available depending on the necessity of reconnection set in advance together with the importance level. And
One of the characteristics of the SIP gateway is that the user can freely set the session importance level.

According to the solution of the present invention,
In a system in which a session is connected between a terminal and a communication destination device via a network, the gateway device is arranged between a plurality of the terminals and the network, and the number of usable sessions is set in advance,
Corresponding to the communication source identification information and communication destination identification information of the session, a session importance storage area in which the importance of the session is stored in advance,
A session status storage area in which communication source identification information and communication destination identification information are stored for each of one or a plurality of currently connected sessions;
A session recovery storage area for storing communication source identification information and communication destination identification information of a disconnected session;
A session recovery unit that recovers a session between devices indicated by the communication source identification information and the communication destination identification information stored in the session recovery storage area;
A session control unit for controlling connection and disconnection of the session,
The session control unit
When the number of currently connected sessions is the same as the number of available sessions, a connection request for a new session including communication source identification information and communication destination identification information indicating the terminal is received from one of the terminals. The communication source identification information and the communication destination identification information are identified for one or a plurality of already connected sessions, and the session importance is determined based on the specified communication source identification information and the communication destination identification information. Referring to the storage area, find the importance for each connected session,
Select the session with the lowest importance or the one with the importance less than the predetermined criteria,
Disconnect the selected session,
The communication source identification information and communication destination identification information of the selected session are stored in the session recovery storage area,
According to the communication source identification information and the communication destination identification information included in the connection request for the new session, connect a new session between the communication source terminal and the communication destination device,
The session recovery unit and / or the session control unit,
When a usable session is made by disconnecting the new session or another session, a session between terminals or devices indicated by the communication source identification information and the communication destination identification information stored in the session recovery storage area is connected. Thus, the gateway device for recovering the disconnected session is provided.

  According to the present invention, even when the number of available sessions is all used, it is possible to connect a new session with high importance by disconnecting one of the sessions, and automatically disconnect the disconnected sessions. A gateway device that can be restored automatically can be provided.

(Hardware configuration)
FIG. 1 is a conceptual diagram of a network configuration including a SIP gateway.
The network system includes, for example, a plurality of terminals UA20 (for example, terminals UA-A21 to N24), a SIP gateway device (hereinafter, SIP GW) 10, and one or a plurality of communication destination devices UA30 (for example, a communication destination UA-). a31-m34). In this embodiment, SIP is described as an example, but other protocols may be used. Further, the terminal UA20 and the communication destination device UA30 may not be physical terminals / devices, but may be logical applications.

  The SIP GW 10 is installed in a subscriber (user) home, for example, and is located between the home terminal UA 20 and the public SIP network 40. For example, it can be located at the boundary between the home network and the public network 40. A session is connected between the terminal UA20 and the communication destination UA30 via the IP network 40 and the SIP GW10. In such a network configuration, the maximum number of sessions that can be used from within the home (assuming two sessions in this example) is defined in advance by the subscriber's subscription service contract.

The communication destination device UA30 is, for example, a server that distributes a video stream, a video conference server, a terminal that performs voice communication, a server (security center) that monitors security, or the like.
The terminal UA20 is, for example, a PC, a telephone set, a set top box, a sensor controller for security monitoring, or the like. Note that the present invention is not limited to this, and an appropriate terminal or device may be used.

  For example, the set-top box receives the video stream from the communication destination UA 30 that distributes the video stream. The telephone performs voice communication with the communication destination UA 30. For example, the PC connects to the communication destination UA 30 for performing a video conference, and performs the video conference. For example, it communicates with a video conference server in a company. Note that the PC can have the same functions as the above-described set-top box and telephone.

  A sensor for security monitoring is attached to, for example, a door or near the door, and detects the intrusion of a suspicious person or the like. Moreover, the sensor for a crime prevention, the sensor which detects a fire, gas leak, and electric leakage etc. may be sufficient. Moreover, the switch etc. for making emergency calls, such as care and medical care, may be sufficient. When a controller (for example, terminal UA-C23) that controls a sensor for security monitoring detects an abnormality such as an intrusion of a suspicious person, it notifies information indicating the abnormality to a security monitoring server (for example, communication destination UA-c33). . In the present embodiment, for example, an emergency session related to security is preferentially connected even if another session is already connected. For example, even if a subscriber is in the house and uses the maximum number of sessions that can be used by telephone or PC, a security session is connected and a server that monitors security for information indicating an abnormality (for example, a security center) Can be notified.

  Each terminal UA20 and each communication destination UA30 is assigned a URI (identification information) in advance. The URI is not limited to a physical terminal or device, and may be assigned to an application.

FIG. 2 is a conceptual diagram of the internal configuration of the SIP GW 10.
The SIP GW 10 includes, for example, a CPU 11, a line control unit 12, a line interface unit (line I / F unit) 13, a session control unit 14, a session monitoring unit 15, a session restoration unit 16, and a memory 100. Have. The memory 100 includes, for example, a session status table (session status storage area) 110, a session resource table (session resource storage area) 120, a session importance level table (session importance storage area) 130, and a session recovery table (session recovery). Storage area) 140. Each unit is connected by a bus or the like.

  The line control unit 12 manages the routing of communication packets. The line I / F unit 13 is an interface in charge of transfer of communication packets. The session control unit 14 controls disconnection / connection of a session. The session monitoring unit 15 monitors the session status during communication in real time. For example, the session monitoring unit 15 monitors a session and stores the number of sessions in communication in the session resource management table. The session recovery unit 16 is responsible for recovering the disconnected session. For example, when there is an empty session, the session recovery unit 16 stores the terminal UA URI (communication source URI, communication source identification information) and communication destination UA URI (communication destination identification information) stored in the session recovery table 140. The session control unit 14 restores the session between the devices shown.

  The session status table 110 stores information on the session status during communication. The session resource table 120 stores information on the number of available session resources and the consumption status. The session importance level table 130 stores predetermined session importance level information. The session recovery table 140 stores information on sessions that are disconnected and need to be recovered. The configuration of each table will be described in detail later.

(Table structure)
FIG. 4 is a configuration diagram of the session resource table 120.
The session resource table 120 includes, for example, a maximum number of sessions specified by a service contract between a user and a carrier, and a session number counter during communication that represents a consumption state of session resources. The communication session number counter is incremented / decremented according to connection / disconnection of a session.

FIG. 5 is a configuration diagram of a session importance level table 130 that stores session importance level information.
The session importance level table 130 can be freely set in advance by the user. The session importance level table 130 includes, for example, a terminal UA URI, a communication destination UA URI, importance level information, and recovery necessity information.

  The terminal UA URI is identification information for identifying a plurality of terminals UA 20 corresponding to different applications connected to the SIP GW 10. The communication destination UA URI is identification information for identifying the communication destination UA 30. The recovery necessity information defines the necessity of session reconnection in the case of forced disconnection. The user can freely set whether or not recovery is necessary. Note that the restoration necessity information may be omitted.

  As an example of importance, the illustrated example assumes the order of P0 to P6 in order from the highest importance to the lowest importance. P0 has the highest importance, and it is necessary to satisfy the transmission request of this importance. Here, P0 is set to a session for security monitoring, for example. It may be an emergency session such as 110 call. Although there is one session of importance P0 in this example, there may be a plurality of sessions.

  P1 to P6 represent the disconnection order (priority order) of various sessions when disconnection is necessary. Sessions to be disconnected are in order from P6 to P1. In the illustrated example, P1 is a session for receiving a video stream from a specific server (for example, a pay content server), P2 is a video conference session with the company, P3 is a telephone session with the company, and P4 is an arbitrary In a session for receiving a video stream from the server, P5 is set as a video conference session with an arbitrary party, and P6 is set as a telephone session with an arbitrary party.

If a session for receiving a video stream from a paid content server is disconnected in the middle, there may be a case where the user is charged twice, such as downloading again from the beginning when connecting next time. In this example, the video stream reception session from the pay content server is set to be highly important, and such double charging can be prevented.
Note that the number of levels of importance does not have to be fixed at seven levels as shown, and can be set as appropriate by the user.

FIG. 6 is a configuration diagram of the session status table 110 that stores information on the session status during communication.
The session status table 110 includes a session management number (fixed) for identifying the session internally, a unique session ID (Call ID) generated every time the session occurs, and the URI of the terminal UA that is the communication source of the session. And the URI of the communication destination UA. The illustrated example is a session status table 110 when the maximum number of sessions is assumed to be two.

  The table shown in FIG. 6A is an example when a session that has already reached the maximum number of sessions is in communication. In this example, in the session with session management number S1, terminal UA-A21 (URI: stb-tanaka@home1.com) which is a set top box and communication destination UA-a31 (URI: download @ icp2) which is a video distribution server .Com) are connected with the session ID aaa. In the session with the session management number S2, the terminal UA-B22 (URI: videocon-tanaka@home1.com) as a PC and the communication destination UA-b32 (URI: videocon@company1.com) as a video conference server Are connected with session ID aaa.

The table shown in FIG. 6B is a table after the session with the session management number S1 is disconnected.
The table shown in FIG. 6C is a table in a state in which new session information is stored in S1 after the new session is established. For example, a new session includes a session between a security monitoring terminal UA-C23 (URI: sec-tanaka@home1.com) and a communication destination UA-c33 (URI: center@security1.com) as a security center server. Connected with ID ccc. Details of the process of transition from FIG. 6A to FIG. 6C will be described later.

FIG. 8 is a configuration diagram of the session recovery table 140 that stores information on a session that is disconnected and needs to be recovered.
The session recovery table 140 is disconnected with, for example, a “disconnection time” that stores time information when the session is disconnected and a “recovery time” that stores the recovered time information (may be blank until recovery). Session ID, terminal UA URI, and communication destination UA URI. After the session is recovered, the time information recovered from the session control unit 14 is input to the “recovery time” field.

(Session connection processing)
FIG. 3 is a process flowchart for a new session connection request by the session control unit 14.
First, the terminal UA20 transmits a connection request for a new session including the terminal UA URI (communication URI) and the communication destination UA URI (communication destination URI) of the terminal itself to the SIP GW10. For example, the terminal UA-C23 transmits a connection request for a new session. Note that the connection request for a new session may further include a session ID.

  The session control unit 14 of the SIP GW 10 receives a connection request for a new session from the terminal UA 20 via the line I / F unit 13 (S101). The session control unit 14 searches the session resource table 120 to determine whether there is a session resource to be allocated to the new session (S103). For example, the session control unit 14 refers to the session resource table 120, and when the number of sessions in communication and the maximum number of sessions are the same value (when there is no free resource) (S105: Yes), the process proceeds to step S107. In other cases (when there are free resources) (S105: No), the process proceeds to step S131.

  In step S107, the session control unit 14 searches the session importance level table 130 based on the communication source URI and the communication destination URI included in the connection request for the new session, and obtains the corresponding importance level (S107). The session control unit 14 determines whether the obtained new session has the highest importance (P0) (S109). When the calculated importance is not P0 (S109: No), the session control unit 14 returns a session connection rejection message to the terminal UA20 (S137). On the other hand, if the calculated importance is P0 (S109: Yes), the process proceeds to step S111. In addition to the case where the calculated importance is P0 (highest), the process may proceed to step S111 if the importance is higher than a predetermined reference.

  In step S111, the session control unit 14 searches the session status table 110, and acquires the communication source URI and communication destination URI of the existing session (S111). Further, the session control unit 14 acquires session importance level information and recovery request information (recovery request presence / absence) by collating with the session importance level table 130 based on the acquired communication source URI and communication destination URI. (S113). The session control unit 14 executes the processes of steps S111 and S113 for all existing sessions, and acquires importance information and recovery request information for each connected session.

The session control unit 14 identifies the session with the lowest importance by comparing the obtained importance for each session (S115 to S119). Note that the session control unit 14 may specify one of the sessions whose importance is lower than a predetermined reference.
The session control unit 14 disconnects the identified session (S121). The session control unit 14 determines whether there is a recovery request according to the recovery request information of the disconnected session (S123).

  When the disconnected session requests recovery (S123: Yes), the session control unit 14 moves and stores information on the session from the session status table 110 to the session recovery table 140 (S127). More specifically, when the recovery request information acquired in step S113 indicates that recovery is necessary, the session control unit 14 determines the communication source URI and communication destination URI of the session specified in the session status table 110. Are stored in the session recovery table 140, and the communication source URI and communication destination URI are deleted from the session status table 110.

  On the other hand, when the disconnected session does not request recovery (S123: No), the session control unit 14 deletes the communication source URI and the communication destination URI related to the session from the session status table 110 (S125).

  In step S129, the session control unit 14 (or session monitoring unit 15) updates the session resource table 120 (S129). For example, the session control unit 14 decrements the session number counter during communication in the session resource table 120 by one.

The session control unit 14 permits and connects a new session (S131). For example, the session control unit 14 connects a new session between the communication source terminal UA and the communication destination UA in accordance with the communication source URI and the communication destination URI included in the connection request for the new session. In addition, the session control unit 14 stores the communication source URI, the communication destination URI, and the session ID in the session status table 110. The session ID can be given as appropriate.
The session control unit 14 increments the in-communication session number counter of the session resource table 120 by 1 (S135).

(Session recovery processing)
FIG. 7 is a flowchart of recovery processing for a disconnected session by the session recovery unit 16.
When there is a new input in the session recovery table 140 (corresponding to S201, S127 in FIG. 3), the session recovery unit 16 searches the session resource table 120 (S203), and whether there is a free resource. It is confirmed whether or not (S205). For example, the session recovery unit 16 determines that there is a free resource if the value of the communication session counter in the session resource table 120 is smaller than the maximum number of sessions, while the value of the communication session counter indicates the maximum number of sessions. If it is not smaller, it can be determined that there is no available resource.

  When there is no resource vacancy (S205: No), the session recovery unit 16 searches the session resource table 120 again after a predetermined time, for example, and checks whether there is a resource vacancy (S203, S205). On the other hand, when there is an available resource (S205: Yes), the session recovery unit 16 transmits information on the session to be recovered to the session control unit 14 and requests a recovery process (S207). The session control unit 14 executes a session recovery process to be described later according to the request. If the session recovery is successful in the session recovery process, the session control unit 14 inputs the actual recovery time in the “recovery time” field of the session recovery table 140 (step S317 described later).

  The session recovery unit 16 checks whether or not there is input (stored data) in the “recovery time” field of the session recovery table 140 (S209). If there is no input in the “recovery time” field (S209: No), the session recovery unit 16 requests the session control unit 14 for recovery processing again (S207). When there is an input in the “recovery time” field (S209: Yes), the session recovery unit 16 deletes the information on the corresponding session from the session recovery table 140 (S211).

FIG. 9 is a flowchart of session recovery processing in the session control unit 14.
The session control unit 14 receives a recovery request from the session recovery unit 16 (S301, S207 in FIG. 7). The session control unit 14 searches the session recovery table 140 (S303), and acquires the terminal UA URI and the communication destination UA URI (S305). The session control unit 14 transmits an INVITE message to the acquired terminal UA URI (S307). The session control unit 14 determines whether a 200 OK response message has been received from the terminal UA (S309). If there is no reception, the INVITE message is retransmitted (S307). If there is reception, the process proceeds to step S311.

  The session control unit 14 transmits an INVITE message to the acquired communication destination UA URI (S311). This INVITE message includes, for example, the acquired terminal UA URI (communication source URI) and communication destination UA URI. The session control unit 14 determines whether a 200 OK response message has been received from the communication destination UA (S313). If there is no reception, the INVITE message is retransmitted (S311). If there is reception, the process proceeds to step S315.

The session control unit 14 transmits an ACK message to each of the terminal UA and the communication destination UA (S315). Through the above processing, the session stored in the session recovery table 140 is reconnected. The session control unit 14 writes the current time in the “recovery time” field of the session recovery table 140 (S317).
In this example, the process is divided into the session control unit 14 and the session recovery unit 16, but one control unit may perform the process.

FIG. 10 is a communication sequence diagram.
For example, when two sessions of the maximum number of sessions are used up in communication between the terminal UA-A21 / communication destination UA-a31 and between the terminal UA-B22 / communication destination UA-b32, the terminal UA-C23 has the highest importance. It is a sequence diagram when there is an emergency session connection request.

  A session of S1 (SessionID aaa) and S2 (SessionID bbb) is established between the terminal UA-A21 / communication destination UA-a31 and between the terminal UA-B22 / communication destination UA-b32. At this time, the session status table 110 is as shown in FIG.

  The terminal UA-C23 sends a session connection request (INVITE message) addressed to the communication destination UA-c33 to the SIP GW 10 (S501). The session connection request includes, for example, the terminal UA URI (sec-tanaka@home1.com) of the terminal UA-C23 in the From header, and the communication destination UA URI (center@security.com) of the communication destination UA-c33 in the To header. Including.

The SIP GW 10 refers to the session resource table 120 and determines here that the number of sessions in communication has reached the maximum number of sessions (corresponding to S503 and S103 and S105 in FIG. 3).
The SIP GW 10 refers to the session importance level table 130 and determines that the new session is P0 having the highest importance level (S505, corresponding to S107 and S109 in FIG. 3).

  The SIP GW 10 specifies the existing session S1 (aaa) having the lowest importance (S507, corresponding to S111 to S119 in FIG. 3). Referring to the session status table 110 and the session importance level table 130, the session with the session management number S1 has the importance level P4, and the session with the session management number S2 has the importance level P2. Therefore, the session of the session management number S1 with low importance is specified by the SIP GW 10.

  In the session disconnection process, a BYE message (disconnect request) is sent from the SIP GW 10 to the terminal UA-A21 and the communication destination UA-a31 according to the communication source URI and communication destination URI of the session management number S1 in the session status table 110, respectively. (S509, S511). The BYE message can include a line of reason = emergency (emergency) as a reason for disconnection. Further, the SIP GW 10 receives 200 OK from the terminal UA-A21 and the communication destination UA-a31 (S513, S515).

  Further, when there is a recovery request, the SIP GW 10 stores the communication source URI and communication destination URI of the session management number S1 of the session status table 110 in the session recovery table 140 and writes the disconnection time (S127 in FIG. 3). . The SIP GW 10 deletes the entry of the session management number S1 in the session status table 110 (S127 and S125 in FIG. 3). The deleted table 110 is, for example, as shown in FIG.

After disconnecting the identified session S1 (SessionID aaa), the SIP GW 10 sends an INVITE message to the communication destination UA-c33 of the new session, and the session S1 between the terminal UA-C23 / communication destination UA-c33. (SessionID ccc) is established (S517 to S525, corresponding to S131 in FIG. 3).
Through the above processing, the terminal UA-C23 / destination UA-c33 can communicate with each other (S527).

  After the new session S1 (SessionID ccc) is communicated, a BYE message is sent from the terminal UA-C23 to the SIP GW 10 and from the SIP GW 10 to the communication destination UA-c33 in order to end the session (S529, S531). Further, the SIP GW 10 receives 200 OK from the communication destination UA-c33 and transmits it to the terminal UA-C23 (S533, S535). As a result, the session resource for S1 is released.

  When a recovery request is sent to the session control unit 14 from the session recovery unit 16 that has determined that a session is available by releasing the new session resource (session disconnection) or by disconnecting another session, the SIP It is determined that the GW 10 can be restored (S537).

The recovery process is performed by sending an INVITE message from the SIP GW 10 to the terminal UA-A21 and the communication destination UA-a31 based on the information stored in the session recovery table 140 (S539 to S549).
As a result, the session between the disconnected terminal UA-A21 / destination UA-a31 is recovered in the form of S1 (SessionID ddd).

  The present invention is applicable to, for example, a gateway device, a system in which terminals and devices communicate with each other via the gateway device, and the like.

FIG. 2 is a conceptual diagram of a SIP GW network configuration. The internal structure conceptual diagram of SIP GW. 9 is a process flowchart for a new session connection request in the SIP GW. The block diagram of the session resource table which stores the information regarding the available session resource and consumption status. The block diagram of the session importance degree table which stores the importance information of a session. The block diagram of the session status table which stores the information of session status during communication. The recovery processing flowchart of a session that is disconnected and needs to be recovered. The block diagram of the session recovery table which stores the information of the session which is cut | disconnected and needs recovery. The flowchart of the recovery process in a session control part. Sequence when there is an urgent session connection request with the highest importance of UA-C when two sessions of the maximum number of sessions are used up in communication between UA-A / UA-a and UA-B / UA-b Figure.

Explanation of symbols

10 SIP gateway device 20 Terminal UA
30 Communication destination device UA
11 CPU
12 Line Control Unit 13 Line Interface Unit 14 Session Control Unit 15 Session Monitoring Unit 16 Session Recovery Unit 100 Memory 110 Session Status Table (Session Status Storage Area)
120 Session resource table (session resource storage area)
130 Session importance table (session importance storage area)
140 Session recovery table (session recovery storage area)

Claims (11)

  1. In a system in which a session is connected between a terminal and a communication destination device via a network, the gateway device is arranged between a plurality of the terminals and the network, and the number of usable sessions is set in advance,
    Corresponding to the communication source identification information and communication destination identification information of the session, a session importance storage area in which the importance of the session is stored in advance,
    A session status storage area in which communication source identification information and communication destination identification information are stored for each of one or a plurality of currently connected sessions;
    A session recovery storage area for storing communication source identification information and communication destination identification information of a disconnected session;
    A session recovery unit that recovers a session between devices indicated by the communication source identification information and the communication destination identification information stored in the session recovery storage area;
    A session control unit for controlling connection and disconnection of the session,
    The session control unit
    When the number of currently connected sessions is the same as the number of available sessions, a connection request for a new session including communication source identification information and communication destination identification information indicating the terminal is received from one of the terminals. The communication source identification information and the communication destination identification information are identified for one or a plurality of already connected sessions, and the session importance is determined based on the specified communication source identification information and the communication destination identification information. Referring to the storage area, find the importance for each connected session,
    Select the session with the lowest importance or the one with the importance less than the predetermined criteria,
    Disconnect the selected session,
    The communication source identification information and communication destination identification information of the selected session are stored in the session recovery storage area,
    According to the communication source identification information and the communication destination identification information included in the connection request for the new session, connect a new session between the communication source terminal and the communication destination device,
    The session recovery unit and / or the session control unit,
    When a usable session is made by disconnecting the new session or another session, a session between terminals or devices indicated by the communication source identification information and the communication destination identification information stored in the session recovery storage area is connected. Thus, the gateway device restores the disconnected session.
  2. The session importance storage area further stores recovery necessity information indicating whether or not the disconnected session needs to be restored, corresponding to the communication source identification information and the communication destination identification information,
    The session control unit refers to the session importance storage area based on the communication source identification information and communication destination identification information of the new session included in the connection request for the new session, and the corresponding recovery necessity information needs to be recovered. The gateway device according to claim 1, wherein the communication source identification information and the communication destination identification information of the selected session are stored in the session recovery storage area.
  3. The session recovery unit and / or the session control unit,
    The communication source identification information and the communication destination identification information stored in the session recovery storage area are read, and the communication source identification is sent to the terminal or device indicated by the communication source identification information and the terminal or device indicated by the communication destination identification information. The gateway device according to claim 1, wherein the disconnected session is recovered by transmitting a connection request for connecting between the information and the terminal or device indicated by the communication destination identification information.
  4. Delete the communication source identification information and communication destination identification information of the selected session from the session status storage area,
    The gateway apparatus according to claim 1, wherein communication source identification information and communication destination identification information included in a connection request for a new session are stored in the session status storage area.
  5. A session resource storage area for storing the number of connected sessions and a predetermined number of usable sessions;
    A session monitoring unit that monitors a session and stores the number of connected sessions in the session resource storage area;
    The session control unit
    When a connection request for a new session is received, the session resource storage area is referred to, and when the number of connected sessions and the number of usable sessions are the same value, the selected session is disconnected, and the new session The gateway device according to claim 1, wherein the gateway device is connected.
  6. When the new session or another session is released, the session monitoring unit decreases the number of connected sessions stored in the session resource table,
    The gateway device according to claim 5, wherein the session recovery unit recovers the disconnected session when the number of connected sessions in the session resource table is smaller than the number of usable sessions.
  7.   The gateway apparatus according to claim 1, wherein the new session is a session related to security.
  8.   When the session control unit receives a connection request for a new session, the session control unit obtains the importance of the new session by referring to the session importance storage area based on the communication source identification information and the communication destination identification information included in the connection request. 2. The gateway device according to claim 1, wherein when the importance is highest or higher than a predetermined criterion, the selected less important session is disconnected and the new session is connected.
  9. The session control unit receives, from the terminal that monitors security, a connection request for a new session having the communication source identification information as identification information of the terminal and the communication destination identification information as identification information of the security center,
    In the session importance storage area, the first importance having the highest importance is stored corresponding to the communication source identification information indicating the terminal and the communication destination identification information indicating the security center.
    The gateway device according to claim 8, wherein a session between the terminal and the security center is preferentially connected.
  10. The session importance storage area includes
    Corresponding to communication source identification information indicating a terminal or set top box for displaying video and communication destination identification information indicating a server that performs video stream distribution, second importance is stored,
    The gateway device according to claim 9, wherein the second importance is set lower than the first importance and higher than the importance of other sessions.
  11. The session importance storage area includes
    Corresponding to communication source identification information indicating a terminal that performs a video conference and communication destination identification information indicating a predetermined conference server, the third importance is stored,
    Corresponding to communication source identification information indicating a terminal performing voice communication and communication destination identification information indicating a predetermined terminal, a fourth importance is stored,
    The gateway device according to claim 9, wherein the third and fourth importance levels are set lower than the first importance level and higher than the importance levels of other sessions.
JP2007211708A 2007-08-15 2007-08-15 Gateway device Withdrawn JP2009049550A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2007211708A JP2009049550A (en) 2007-08-15 2007-08-15 Gateway device

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2007211708A JP2009049550A (en) 2007-08-15 2007-08-15 Gateway device
US12/184,352 US20090049180A1 (en) 2007-08-15 2008-08-01 Gateway apparatus
CN 200810145630 CN101369996B (en) 2007-08-15 2008-08-07 Gateway device

Publications (2)

Publication Number Publication Date
JP2009049550A true JP2009049550A (en) 2009-03-05
JP2009049550A5 JP2009049550A5 (en) 2010-02-18

Family

ID=40363852

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2007211708A Withdrawn JP2009049550A (en) 2007-08-15 2007-08-15 Gateway device

Country Status (3)

Country Link
US (1) US20090049180A1 (en)
JP (1) JP2009049550A (en)
CN (1) CN101369996B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009278296A (en) * 2008-05-14 2009-11-26 Nec Corp Ip telephone communication system, sbc device, emergency call priority connection method, and its program
JP2016503261A (en) * 2012-12-20 2016-02-01 オランジュ Mechanism for managing communication sessions
JP2016096460A (en) * 2014-11-14 2016-05-26 株式会社日立情報通信エンジニアリング Voip gateway and telephone call control method
JP2017123117A (en) * 2016-01-08 2017-07-13 Kddi株式会社 Communication device, communication system, communication method, and program

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2227063B1 (en) 2009-03-04 2012-03-14 Fujitsu Limited Improvements to wireless sensor networks
US8335218B2 (en) * 2009-04-13 2012-12-18 Qualcomm Incorporation Methods and devices for restoring session state
JP5264629B2 (en) * 2009-06-23 2013-08-14 キヤノン株式会社 Communication terminal and communication terminal control method
US8473949B2 (en) 2010-07-08 2013-06-25 Microsoft Corporation Methods for supporting users with task continuity and completion across devices and time
FR2964281A1 (en) * 2010-09-01 2012-03-02 France Telecom Method of processing sip messages
US20130250797A1 (en) * 2010-12-14 2013-09-26 Nobuhiko Itoh Communication control system, control device, communication control method, and communication control program
JP5765123B2 (en) * 2011-08-01 2015-08-19 富士通株式会社 Communication device, communication method, communication program, and communication system
CN103905785B (en) * 2012-12-27 2018-03-13 中国电信股份有限公司 Method, system and the SIP gateways that control SIP video traffics continue
US9609068B2 (en) * 2013-12-16 2017-03-28 Fuji Xerox Co., Ltd. Session management system, session management apparatus, and non-transitory computer readable medium
US20180097851A1 (en) * 2016-10-04 2018-04-05 Avaya Inc. Session initiation protocol (sip) dialog reconstruction through reconstruction anchors for user agents

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01114247A (en) * 1987-10-28 1989-05-02 Nec Eng Ltd Forced disconnection and re-connection system
JPH0823375A (en) * 1994-07-06 1996-01-23 Mitsubishi Electric Corp Isdn call connection control system
JPH11285040A (en) * 1998-03-26 1999-10-15 Victor Co Of Japan Ltd Emergency call forced-connection device
JP2000022713A (en) * 1998-07-07 2000-01-21 Hitachi Ltd Communication band control system

Family Cites Families (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5530703A (en) * 1994-09-23 1996-06-25 3Com Corporation Remote communication server with automatic filtering
US5889954A (en) 1996-12-20 1999-03-30 Ericsson Inc. Network manager providing advanced interconnection capability
JP3733984B2 (en) * 1997-01-29 2006-01-11 富士ゼロックス株式会社 Information storage device and information storage method
US6006269A (en) * 1998-03-11 1999-12-21 Hewlett-Packard Company Admission control system with messages admitted or deferred for re-submission at a later time on a priority basis
US6055564A (en) * 1998-03-11 2000-04-25 Hewlett Packard Company Admission control where priority indicator is used to discriminate between messages
DE69924103T2 (en) * 1998-04-28 2005-12-15 Nokia Corp. Method and network for managing wsp (wireless session protocol) meetings
JP3403971B2 (en) * 1999-06-02 2003-05-06 富士通株式会社 Packet transfer device
US7835929B2 (en) * 2001-02-28 2010-11-16 Bennett Levitan S Method and system for managing a portfolio
GB2363297B (en) * 2000-06-09 2004-04-07 Hewlett Packard Co Secure network communications
US20030125023A1 (en) * 2001-03-15 2003-07-03 Eyal Fishler Method and system for providing a wireless terminal communication session integrated with data and voice services
US7155521B2 (en) * 2001-10-09 2006-12-26 Nokia Corporation Starting a session in a synchronization system
US7284061B2 (en) * 2001-11-13 2007-10-16 Canon Kabushiki Kaisha Obtaining temporary exclusive control of a device
AU2003239385A1 (en) * 2002-05-10 2003-11-11 Richard R. Reisman Method and apparatus for browsing using multiple coordinated device
US7212537B2 (en) 2002-07-10 2007-05-01 Samsung Electronics Co., Ltd. Apparatus and method for recovering communication sessions in a wireless network gateway
CN100463469C (en) * 2002-10-25 2009-02-18 国际商业机器公司 Method, device and system for sharing applied program conversation information on multichannels
US20090254399A1 (en) * 2004-02-14 2009-10-08 Cristol Steven M System and method for optimizing product development portfolios and aligning product, brand, and information technology strategies
US7016479B2 (en) * 2004-04-23 2006-03-21 Sorenson Communications, Inc. Method and system for call restoration in a video relay service
US8121462B2 (en) * 2004-06-29 2012-02-21 Panasonic Corporation Video edition device and method
US20060089131A1 (en) * 2004-10-22 2006-04-27 Henry Huang Delay timers for managing internal state changes and messages in user equipment for real-time multimedia applications
JP2006301028A (en) * 2005-04-15 2006-11-02 Canon Inc Image forming apparatus and its control method
IES20050439A2 (en) * 2005-06-30 2006-08-09 Asavie R & D Ltd A method of network communication
JP4742903B2 (en) * 2006-02-17 2011-08-10 日本電気株式会社 Distributed authentication system and distributed authentication method
US20080205267A1 (en) * 2007-02-23 2008-08-28 Telefonaktiebolaget Lm Ericsson (Publ) Service Differentiation in the IP Multimedia Subsystem Utilizing Context-Aware Signaling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01114247A (en) * 1987-10-28 1989-05-02 Nec Eng Ltd Forced disconnection and re-connection system
JPH0823375A (en) * 1994-07-06 1996-01-23 Mitsubishi Electric Corp Isdn call connection control system
JPH11285040A (en) * 1998-03-26 1999-10-15 Victor Co Of Japan Ltd Emergency call forced-connection device
JP2000022713A (en) * 1998-07-07 2000-01-21 Hitachi Ltd Communication band control system

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009278296A (en) * 2008-05-14 2009-11-26 Nec Corp Ip telephone communication system, sbc device, emergency call priority connection method, and its program
JP2016503261A (en) * 2012-12-20 2016-02-01 オランジュ Mechanism for managing communication sessions
JP2016096460A (en) * 2014-11-14 2016-05-26 株式会社日立情報通信エンジニアリング Voip gateway and telephone call control method
JP2017123117A (en) * 2016-01-08 2017-07-13 Kddi株式会社 Communication device, communication system, communication method, and program

Also Published As

Publication number Publication date
CN101369996B (en) 2011-05-04
CN101369996A (en) 2009-02-18
US20090049180A1 (en) 2009-02-19

Similar Documents

Publication Publication Date Title
US8706892B2 (en) Communication system and server
DE60014677T2 (en) Method and device for message processing control of a network gatekeeper
KR100453757B1 (en) Packet telephony power management
US6252884B1 (en) Dynamic configuration of wireless networks
US9240946B2 (en) Message restriction for diameter servers
TW578413B (en) Methods and apparatus for controlling IP applications during resource shortages
US20020118671A1 (en) Extending office telephony and network data services to a remote client through the internet
EP1563639B1 (en) Method and apparatus for multi-media communication over multiple networks
JP3512832B2 (en) Inter-LAN communication method and LAN / WAN connection device
JP2006140989A (en) Method and system for fast session establishment between equipment using h.324 and related telecommunication protocol
JP4276698B2 (en) Data communication system and recording medium
CA2554416C (en) Congestion handling in a packet communication system
US8068824B2 (en) Automated reconnection of interrupted voice call session
US6418210B1 (en) Method and apparatus for providing information between a calling network and a called network
US7953884B2 (en) Method and apparatus for overload control and audit in a resource control and management system
DE60014234T2 (en) System and method for enabling fault tolerant systems
US20050180317A1 (en) Server backup device
KR20020060962A (en) Packet telephony power management
CA2246872A1 (en) Network traffic controller
JP2003514447A (en) Method for providing prepaid telephone service via the internet protocol network system
JP2002540643A (en) Switching dynamic communication channel for the computer network
KR20040061079A (en) Apparatus and method for session establishment in radio network organized mobile nodes
JPH0856239A (en) D-channel packet communication system
US7483523B2 (en) Time delay compensation device for the management of multimedia communications via an asynchronous network and a telephone network
US20070183407A1 (en) Auxiliary bridging device supporting multiple pathway telephony bridging

Legal Events

Date Code Title Description
A621 Written request for application examination

Effective date: 20100105

Free format text: JAPANESE INTERMEDIATE CODE: A621

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20100105

A977 Report on retrieval

Effective date: 20110502

Free format text: JAPANESE INTERMEDIATE CODE: A971007

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20110517

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20110713

A131 Notification of reasons for refusal

Effective date: 20110809

Free format text: JAPANESE INTERMEDIATE CODE: A131

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20110915

A761 Written withdrawal of application

Effective date: 20110927

Free format text: JAPANESE INTERMEDIATE CODE: A761