JP4719199B2 - Traffic leveling control method and server in telephone system via IP network - Google Patents

Description

  The present invention relates to a traffic leveling control method and server in a telephone system via an IP network that performs voice communication between telephone terminals based on the SIP or SIMPLE protocol.

  In recent years, the provision of telephone / additional services over the IP network has been promoted in each telecommunications company (carrier), and the number of users using the IP telephone service is increasing.

  SIP (Session Initiation Protocol) or SIPPLE (SIP for Instant Messaging and Presence Leveraging Extensions) as a VOIP (Voice Over IP) protocol that is a telephone technology over the IP network (hereinafter referred to as SIP / SIMPLE) These services are provided by a SIP server (a server that controls call connection) and a presence server (a server that manages the presence / absence of terminal users).

  Some SIP / SIMPLE protocol specifications allow a server to receive a corresponding service by receiving and registering information according to various requests from a terminal user. Information registered by such a request has a predetermined registration valid time, and when the registration valid time has passed, the registered information is erased and becomes unregistered. Therefore, it is necessary to access the IP network server for a request to update the registration information within the registration valid time from the terminal side that wants to maintain these services, and the traffic for that may be excessive, and improvement is desired. ing.

  FIG. 8 shows a network configuration that is an object of the present invention. In the figure, 50 is an IP network, 51 is a user terminal, 52 and 53 are LANs of carriers (carriers) of IP telephones, 54 is a SIP server for controlling call connection to the terminals, and 55 is a terminal. It is a presence server that registers the state and controls the service corresponding to the state of the other terminal. Note that the SIP server 54 and the presence server 55 are connected to different LANs 52 and 53, but in reality, they are often LANs operated by the same carrier.

  In the network configuration as shown in FIG. 8, there are the following requests whose registration valid time is determined by SIP / SIMPLE.

  REGISTER: A request signal for requesting the location registration of the user terminal. For example, when the location registration of the own terminal (portable terminal) is performed from the user terminal 51a, the URI (Uniform Resource Identification) and IP address of the terminal are given together with this REGISTER message. When it is added and transmitted to the network, the location information (the location of the user terminal 51a) is registered in the SIP server 54 together with the terminal address. When a call is generated with the address of the terminal that has performed the location registration as the destination, the registered location is confirmed and the location is called.

  PUBLISH: A request signal for requesting user status registration in the user terminal, for example, status registration including status information such as presence or absence (or absence including whereabouts) of the user of the user terminal 51a as his / her own status When this PUBLISH message is transmitted when requesting the request, status information is registered in the presence server 55.

  SUBSCRIBE: A request signal for requesting notification of a change in the state of another user terminal. For example, when the user of the user terminal 51b changes in the state of the other user terminal 51a, a notification is sent to the own terminal 51b. This is a request message, and information on the address of the other party whose status change is to be monitored is also added. This request signal is registered and managed in the presence server 55.

  According to the SIP / SIMPLE protocol, the location registration information of the above-mentioned “REGISTER” message is retained for the user terminal registration valid time specified in advance (specified by the user), and the registration valid time is updated within the valid time. Although it is retained, it is deleted if an update request is not sent from the terminal within the registration valid time. Similarly, the status registration information of the message “PUBLISH” is also held for the specified presence update registration valid time, and is deleted if a request for updating is not transmitted from the terminal within the valid time. Furthermore, registration information including information of the monitoring target counterpart terminal designated by the “SUBSCRIBE” message is also held for the designated presence monitoring registration valid time, and is erased unless the registration valid time is updated from the terminal side.

  Since these registration valid times need to be updated periodically from the user terminal side, signal traffic on the IP network is triggered by the user and the load on the system side increases as the number of users increases. Tend to. For this reason, the original service processing provided by the system is affected.

As a conventional technique, a technique for quickly restoring a registered state even when a telephone terminal becomes unregistered on a server due to expiration of an effective time has been proposed (see Patent Document 1). In the proposed technology, the SIP server constantly monitors the registration information of each terminal in the terminal registration status table, and the registration status of the terminal is changed to “unregistered” due to the expiration of the registration valid time or a failure of the SIP server itself. Then, a “REGISTER” request message is transmitted to the corresponding terminal, and when “REGISTER” arrives from the terminal receiving the message, the registration state of the terminal registration state table is reset to “registered”. It is a thing.
JP 2006-157612 A

  According to the technique of the above-mentioned Patent Document 1, the registration information in the terminal registration information table is monitored, and the technique in the case where it is detected that the registration valid time has expired and the registration state has been changed to “unregistered”. Yes, it is a technique that is executed only after the registration state becomes “unregistered”, and there is a possibility that a problem may occur in call connection control immediately after the state becomes unregistered.

  And the trigger for sending the registration valid time of the terminal registration information is user-driven, and there is a possibility of concentration, which places a heavy load on the system side and the original service processing (call There is a problem of affecting connection control.

  The present invention relates to a telephone system via an IP network that can perform leveling control so that signal traffic for updating the registration valid time of terminal registration information set in the SIP server or presence server within the valid time does not give a load to the system. An object is to provide a traffic leveling control method and a server.

  In the present invention, in order to ensure system tolerance during burst traffic due to the original service processing, the signal traffic of the registration valid time update that occurs regularly is pre-predicted and leveled on the system side, and the optimum system capacity is always maintained. It is something that can be done.

  FIG. 1 is a diagram showing a principle configuration of the present invention. In the figure, 1 is a server (SIP server or presence server) connected to the IP network, 10 is a message reception registration unit that receives and registers request information from the user terminal, 11 is a registration update time determination unit, and 11a is Relative time calculation means, 11b is an update reception number detection means, 11c is an update reception number / time-specific limit value comparison determination means, 11d is a table update means, and 12 is a notification section. 13 is a memory, 13a is a registration information table for various services, 13b is a scheduled reception number table in which the scheduled reception number corresponding to the relative time (the number already determined to be received) is stored, and 13c is one day. It is a reception number limit value table in which a reception number limit value per unit time corresponding to each time divided by 24 hours (a number that can be received according to traffic distribution such as call control) is stored. 2 is a user terminal.

  When the server 1 receives the message signal including the terminal information requesting various services from the user terminal 2 and the registration valid time (the valid time requested by the user) via the IP network, the message reception registration unit 10 performs various services. The requested information is registered in the table corresponding to the requested service in the table 13a. At this time, the registration update time determination unit 11 performs a process of determining an optimal registration update time based on the registration valid time of the received terminal information. First, the relative time calculating means 11a calculates the relative time (how many seconds from the starting point) until the registration valid time requested by the user, starting from the current time point, and then refers to the scheduled reception number table 13b by the updated reception number detecting means 11b. The expected number of receptions X corresponding to the calculated relative time is obtained. Next, the updated reception number / time limit value comparison / determination means 11c converts the relative time into a time (a time in which one day is 24 hours), and sets a reception number limit value Y corresponding to the converted time. The received number limit value table 13c is referred to, and the expected reception number X is compared with the reception limit value Y. In this comparison, when the scheduled reception number X is smaller than the reception limit value Y, it is within the range of the server processing capacity, so the registration valid time requested by the user is determined as the update time, and the table update means 11d is the scheduled reception number table 13b. The reception scheduled number of the corresponding relative time is updated (+1). In addition, the notification unit 12 may notify the user terminal 2 of the registration valid time.

  When the reception limit value Y is less than or equal to the scheduled reception number X, the corresponding time is obtained after increasing the relative time, and the new reception scheduled number X corresponding to the increased relative time and the new reception limitation value Y are tabled. The relative time is determined by performing the same process until it is detected by referring to 13b and 13c and it is detected that the reception limit value Y is larger than the scheduled reception number X. In this case, the relative time is different from the relative time corresponding to the registration valid time requested by the user, and the registration valid time corresponding to the determined relative time is calculated and notified to the user terminal 2.

  The present invention has the following effects.

  (1) The number of occurrences of registration valid time update times for request signals (REGISTER, SUBSCRIBE, PUBLISH, etc.) from user terminals that require periodic update processing of registration valid times for services that support SIP / SIMPLE. By limiting to the number that can be processed by the above, it is possible to achieve leveling of the traffic of the server that performs the service.

  (2) Appropriate traffic can be distributed to request signal processing according to the original service load of the server for each time zone for the user terminal according to the SIP / SIMPLE protocol.

  FIG. 2 is a diagram showing a hardware configuration of the embodiment of the present invention. In the figure, 1 is a server (SIP server or presence server), 100 is a processor, 101 is a program storage memory, 101a is a SIP / SIMPLE message processing program, 101b is a registrar information (REGISTRE: location registration information) processing program, and 101c is a subscription. (SUBSCRIBE: other terminal status change notification request) processing program, 101d is a presence information (terminal status information) processing program, 102 is a main memory, 102a is a registrar table storing terminal location registration information, 102b Is a subscription table, 102c is a presence table, 102d is a reception number limit value management table per unit time (corresponding to the reception number limit value table 13c in FIG. 1), and 102e is a registration valid time update time tube. Table (corresponding to the received predetermined number table 13b of FIG. 1), 103 IP interface unit, 104 operation suppliers of LAN, 2 is the user terminal, 3 is an IP network.

  FIG. 3 shows a processing sequence corresponding to a REGISTER (location registration signal) request. When a “REGISTER” signal (including address information and a registration valid time set by the user) is transmitted from the user terminal 2 to the server 1 (S20 in FIG. 3), it is received by the server 1 (S10), and the registrar information Management search processing is performed (S11). In the server 1 of FIG. 2, the registrar information processing program 101 b in the program storage memory 101 is executed, and registration is performed in the registrar table 102 a in the main memory 102. Subsequently, a registration valid time calculation process is executed (S12 in FIG. 3). In this case, the registration valid time that can level the load due to the update of the registration valid time is obtained for the server, and the details are shown in FIG. 4 to be described later. The registration valid time determined by the registration valid time calculation process is registered in the registrar table 102a by the registration valid time setting process (S13 in FIG. 3), and the request is accepted from the user terminal 2 that has requested “REGISTER” from the server. "200 OK" indicating that this is transmitted (S14), and this is received by the user terminal 2. The “registration valid time” determined together with the notification of “200 OK” is also notified, received by the user terminal 2 and displayed and stored.

  FIG. 4 is a flowchart of the registration valid time calculation process, which is executed in step S12 of FIG. 5 is a specific example of each table, which is used for the processing of FIG. Is an example of the registration valid time update time management table (102e in FIG. 2), and the number of registration valid time updates scheduled to be received is set for each second unit of relative time. Represents the corresponding time of the current starting point. Is an example of the reception number limit value management table (102d in FIG. 2) in which the reception number limit value per unit time is set for each time (each time divided by 24 hours).

  In FIG. 4, first, the starting point value (the starting time of the relative time) is added to the registered valid time update value (a numerical value in seconds, for example, 1800 seconds) received from the user terminal. Time (seconds) is obtained (S1 in FIG. 4). B. of FIG. In this example, if the current starting point is “3202” and the registered valid time update value from the user terminal is “1800”, the relative time becomes “5002” (seconds) by adding this value. . Next, the relative time is calculated (S2 in FIG. 4). Specifically, the registration valid time update value (seconds) received from the user terminal is added to the corresponding time of the starting point (10:10:10 in the example of B in FIG. 5), and converted to time. . If the registered valid time update value is 1800 seconds (corresponding to 30 minutes), the relative time is 10:40:10.

  Next, it is determined whether or not the reception number limit value per unit time of the relative time is larger than the registered effective time update reception scheduled number of relative time (S3 in FIG. 4). Among these, the limit value of the number of receptions per unit time of the relative time is shown in FIG. The reception limit value corresponding to the relative time is obtained by referring to the table shown in FIG. In the case of 10:40:10 in the above example, it can be seen that the time limit of “10 o'clock” is “40”. On the other hand, the estimated number of registration valid time updates received for the relative time is A. If the relative time obtained by referring to the relative time reception table shown in FIG. 4 and the above added relative time is “5001”, the scheduled reception number is “40” and the two numerical values match. No is determined. In this case, the process proceeds to step S4, the relative time is set to +1, the relative time is updated from “5001” to “5002”, and the process returns to step S2. Thus, when it is determined that the reception number limit value per unit time of the relative time is larger than the registered valid time update reception scheduled number of the relative time (the scheduled reception number corresponding to the relative time “5002” is “28 ”Is smaller than the reception limit value“ 40 ”at 10:00), the process proceeds to step S5, and the registration valid time update corresponding to the relative time in the registration valid time update time management table (A. in FIG. 5) Update the scheduled reception number by adding +1. Subsequently, the registration valid time (seconds) is obtained by subtracting the starting point value (“3202” in the example of B. of FIG. 5) from the relative time, and this processing is terminated.

  FIG. 6 is a processing sequence corresponding to a request for SUBSCRIBE (request for state change notification of another user terminal). When the user terminal 2 sends a “SUBSCRIBE” signal (including the terminal address, other terminal information for requesting a change in status and the registration valid time) to the server 1 (S20 in FIG. 6), the presence server 1 receives the signal. (S10), subscription information management search processing is performed (S11). In this case, the subscription information processing program 101c in the program storage memory 101 is executed in the server 1 in FIG. 2, and the requested information about the subscription is registered in the subscription table 102b in the main memory 102. Subsequently, a registration valid time calculation process is executed (S12 in FIG. 6). The contents of this processing are the same as those described above with reference to FIGS. 4 and 5, and the setting process including registration in the subscription table 102b is performed (S13 in FIG. 6) and the requested registration valid time is requested. In order to respond that the information registration has been executed, “200 OK” is transmitted to the user terminal 2 that has requested the service (S14), and this is received by the user terminal 2. The determined “registration valid time” is also notified to the user terminal 2, received by the user terminal 2, displayed and stored.

  FIG. 7 is a processing sequence corresponding to a PUBLISH (state registration request) request. When the user terminal 2 transmits a “PUBLISH” signal (including the terminal address, status information, and registration valid time) to the server 1 (S20 in FIG. 7), the presence server 1 receives it (S10), and presence information management A search process is performed (S11). In the server 1 of FIG. 2, the presence information processing program 101 d in the program storage memory 101 is executed, and registration is performed in the presence table 102 c in the main memory 102. Subsequently, a registration valid time calculation process is executed (S12 in FIG. 7). The contents of this process are the same as those described with reference to FIGS. 4 and 5 as in FIG. 6, and a setting process including registration in the presence table 102c is performed (S13 in FIG. 7). ) That the requested presence information registration has been executed is notified to the user terminal 2 by transmitting “200 OK” (S14), and is received by the user terminal 2. At this time, the determined “registration valid time” is also notified to the user terminal 2.

It is a figure which shows the principle structure of this invention. It is a figure which shows the hardware constitutions of the Example of this invention. It is a figure which shows the process sequence corresponding to the request of REGISTER (location registration signal). It is a figure which shows the flowchart of a registration effective time calculation process. It is a figure which shows the specific example of each table. It is a figure which shows the process sequence corresponding to the request | requirement of SUBSCRIBE (request of the state change notification of another user terminal). It is a figure which shows the process sequence corresponding to the request of PUBLISH (state registration request). It is a figure which shows the network structure used as the object of this invention.

Explanation of symbols

1 server (SIP server or presence server)
DESCRIPTION OF SYMBOLS 10 Message reception registration part 11 Registration update time determination part 11a Relative time calculation means 11b Update reception number detection means 11c Update reception number and time limit value comparison determination means 11d Table update means 12 Notification part 13 Memory 13a Registration information table for various services 13b scheduled reception number table 13c received number limit value table 2 user terminal

Claims (4)

In a traffic leveling control method in a telephone system via an IP network based on a SIP or SIMPLE protocol,
When the server for controlling the service by the SIP or SIMPLE receives the registration request from the user terminal and the service request signal including the registration valid time, it stores the registration information in a table,
A relative time based on the current time is obtained from the registered valid time, and a scheduled reception number corresponding to the obtained relative time is detected from a table in which a scheduled number of registered valid time update signals corresponding to each relative time is set. ,
The seek time corresponding to the detected relative time, detects the reception speed limit corresponding to the time obtained from said table Received limit value per specific unit time each time is set,
When the detected number of received receptions is compared with the detected reception number limit value and it is determined that the scheduled reception number is less than the reception limit value, the registration valid time that is the basis of the relative time is determined appropriately. A traffic leveling control method in a telephone system via an IP network, characterized by being determined as time. In claim 1,
Comparing the detected scheduled reception number with the detected reception limit value and determining that the scheduled reception number is equal to or greater than the reception limit value, the relative time is updated by adding +1 to the relative time. Then, the number of scheduled receptions corresponding to the updated relative time is obtained from the table in which the scheduled number of registered valid time update signals corresponding to the relative time is set, and the time corresponding to the updated relative time is obtained. A reception number limit value per unit time to be obtained from a table in which the reception number limit value per unit time for each time is set and compared with the scheduled reception number;
When the scheduled reception number exceeds the reception number limit value, the relative time is further updated by +1. When the scheduled reception number is less than the reception number limit value, the registration valid time is based on the relative time at that time. A traffic leveling control method in a telephone system via an IP network. In a server in a telephone system over an IP network using SIP or SIMPLE protocol,
A reception message registration unit that stores the registration information in a registration information table when receiving a service request signal including registration information from the user terminal and the registration valid time;
A scheduled reception number table that stores the scheduled reception number of registration valid time update signals by relative time, and a reception count limit value table by time that stores the reception number limit value of the registration information update request signal per unit time by time With
The registration valid time of the registration information requested from the user terminal is converted into a relative time based on a starting point, the scheduled reception number corresponding to the relative time is obtained from the scheduled reception number table, and the relative time is converted into a time. Then, a reception limit value is obtained from the reception limit table for each time and compared with the scheduled reception number, and a relative time when the scheduled reception number is less than the reception limit value is selected, and an optimal registration valid time is selected. A registration update time determination unit including means for determining
A server in a telephone system via an IP network, comprising: a notification unit for notifying a user terminal of the determined registration update time. In claim 3,
The registration update time determination unit includes a relative time calculation means for obtaining a relative time by adding the registration valid time requested from the user terminal and a starting point, and a reception corresponding to the relative time obtained from the scheduled reception number table. Update reception number detection means for obtaining a planned number, and update reception number / time-specific limit value comparison judgment means for comparing the reception number limit value with the scheduled reception number, and the scheduled reception number has reached the reception limit value. A server in a telephone system via an IP network, characterized in that a registration valid time satisfying a non-existing condition is determined.

Images