JP2013017036A - Sip terminal management system, sip server, and sip terminal management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a SIP terminal management system, SIP server, and SIP terminal management method capable of reducing a communication amount for monitoring the life and death of a SIP terminal without performing additional mounting on the SIP terminal.SOLUTION: A SIP terminal management system includes: a management station 10 corresponding to a Simple Network Management Protocol (SNMP); SIP terminals 30 corresponding to a SIP; and a SIP server 20 performing SIP communication with the SIP terminals. The SIP server 20 includes a proxy response function part 23 for managing the operation states of the SIP terminals 30 on the basis of the SIP communication with the SIP terminals 30. The proxy response function part 23 makes a response based on the operation states in place of the SIP terminals 30 to a response request from the management station 10 to the SIP terminals 30.

Description

  The present invention relates to a SIP terminal management system, a SIP server, and a SIP terminal management method, and in particular, a management station corresponding to SNMP (Non-Patent Documents 1 and 2) is a SIP terminal corresponding to SIP (Non-Patent Documents 3 and 4). Relates to a SIP terminal management system, a SIP server, and a SIP terminal management method.

  Conventionally, management of devices connected by a private network in a company or the like (country, local government, school, etc.) often uses SNMP (Simple Network Management Protocol) as shown in FIG. Regarding SNMP, existing technologies and products can also be used for management stations and managed devices (SNMP terminals). In SNMP often used in private networks such as companies, a request (for example, SNMP Get) for obtaining management information (Management Information Base information, hereinafter referred to as “MIB information”) from a management station (manager) to an SNMP terminal (agent). Request) is transmitted. When receiving the request, the SNMP terminal transmits a response to the request to the management station. In addition, the SNMP terminal transmits a trap (notification) to the management station when a predetermined event occurs or when a management information value exceeds a preset threshold value. When performing device management using SNMP, a response request (PING, ICMP Echo Request, Non-Patent Document 5) from a management station is often used in combination with monitoring of the operating status of the SNMP terminal (life and death monitoring).

  On the other hand, mobile user terminals connected to a telecommunications carrier network, particularly a mobile telecommunications carrier network, are diversified, such as smartphones and tablets. These mobile user terminals are connected to a SIP server installed in a telecommunications carrier network or a private network such as a company as SIP terminals corresponding to voice communication, and may be used as voice call terminals.

  In managing mobile user terminals (SIP terminals), a method of using a device management architecture based on OMA (Open Mobile Alliance, Non-Patent Document 6) as shown in FIG. There is. OMA is an industry group that manages mobile device standards and aims at technical standardization of mobile web applications. OMA compliant device management architecture uses Sync ML for information exchange. Sync ML is a standard for data synchronization between different devices. XML-based markup is used and is used as the basis for most protocols defined in OMA. A Sync ML document is called a message. Sync ML uses transport, integrity, and security-related standards such as TCP / IP, HTTP, SSL / TLS, MD5, URI, and other common Internet content types and encoding.

"RFC1157: SNMP: Simple Network Management Protocol" [online], May 1990, <URL: http://www.ietf.org/rfc/rfc1157.txt> Wikipedia, "Simple Network Management Protocol", [online], [May 23, 2011 search], Internet <URL: http://en.wikipedia.org/wiki/Simple_Network_Management_Protocol> "RFC3261: SIP: Session Initiation Protocol", [online], June 2002, <URL: http://www.ietf.org/rfc/rfc3261.txt> Supervised by Yasuaki Chimura and Katsuhiko Sakaguchi, "Next Generation SIP Textbook", Impress R & D Co., Ltd., March 2010, ISBN978-4-8443-2828-5 Wikipedia, "Ping", [online], [Search May 23, 2011], Internet <URL: http://en.wikipedia.org/wiki/Ping> Michael Brenner, Musa Ammehopa, “OMA Standard Text”, published by Rick Telecom, Inc., March 2010, ISBN978-4-89797-827-7 Shizuka Kitahara, "Series: SNMP (3) for automating monitoring", [online], April 25, 2003, Internet <URL: http://www.atmarkit.co.jp/fnetwork/rensai/snmp03/01 .html> Gonzalo Camarillo and Miguel A. Marlin, "IMS Standard Text (revised version)", published by Rick Telecom, Inc., March 2010, ISBN978-4-89797-842-0

  Conventionally, it is necessary to use two device management architectures, SNMP and OMA, for managing all devices including SIP-compatible mobile user terminals (SIP terminals) connected to private networks such as enterprises or telecommunications carrier networks. There is a problem that integrated management by one device management architecture cannot be performed.

  In addition, when using the OMA device management architecture in a small device that is a mobile user terminal (SIP terminal) with extremely limited storage capacity and processing capability, it is necessary to implement a Sync ML function based on HTTP. For this reason, there is a problem that the storage capacity and processing capacity of the small device increase.

  Furthermore, since monitoring of the operating status (life monitoring) for mobile user terminals (SIP terminals) is performed periodically, there is a problem that the amount of communication related to life monitoring is increased.

  Therefore, an object of the present invention made in view of such a point is that it is not necessary to implement Sync ML in a mobile user terminal (SIP terminal), and the amount of traffic for alive monitoring of the mobile user terminal (SIP terminal) is reduced. A SIP terminal management system, a SIP server, and a SIP terminal management method are provided.

  In order to solve the above-described problems, a SIP terminal management system according to the present invention includes a management station that supports SNMP, a SIP terminal that supports SIP, and a SIP server that performs SIP communication with the SIP terminal, The SIP server includes a proxy response function unit that manages an operation status of the SIP terminal based on the SIP communication with the SIP terminal, and the proxy response function unit responds to a response request from the management station to the SIP terminal. On the other hand, a response based on the operation status is made instead of the SIP terminal.

  The SIP server according to the present invention is a SIP server that performs SIP communication with a SIP terminal, and includes a proxy response function unit that manages an operation status of the SIP terminal based on the SIP communication with the SIP terminal, The proxy response function unit responds to a response request from the management station corresponding to SNMP to the SIP terminal based on the operation status instead of the SIP terminal.

  The SIP terminal management method according to the present invention is a SIP terminal management in a SIP terminal management system comprising a management station compatible with SNMP, a SIP terminal compatible with SIP, and a SIP server that performs SIP communication with the SIP terminal. A method in which the SIP server manages an operation status of the SIP terminal based on the SIP communication with the SIP terminal; and a response request from the management station to the SIP terminal Instead, responding based on the operating status.

  According to the SIP terminal management system, the SIP server, and the SIP terminal management method according to the present invention, it is not necessary to install Sync ML in the mobile user terminal (SIP terminal), and the life and alive monitoring of the mobile user terminal (SIP terminal) Can be reduced.

It is a figure which shows the structure of the SIP terminal management system which concerns on the 1st Embodiment of this invention. It is a figure which shows the functional block of a SIP terminal management system. It is a figure which shows the process sequence of a SIP terminal management system. It is a figure which shows the structure of the conventional terminal management system.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

(First embodiment)
FIG. 1 is a diagram showing a configuration of a SIP terminal management system according to the first embodiment of the present invention. The SIP terminal management system includes a management station 10 corresponding to SNMP, a SIP server 20, a SIP terminal (managed device) 30, and an SNMP terminal 40, and belongs to a telecommunications carrier network. 30 and the SNMP terminal 40 belonging to a private network such as a company are managed in a unified manner. Here, communication relating to device management between the management station 10 and the SNMP terminal 40 uses existing SNMP, and will not be described in detail in the present embodiment. Hereinafter, processing of the management station 10, the SIP server 20, and the SIP terminal (managed device) 30 will be described in detail.

  FIG. 2 is a diagram showing functional blocks of the SIP terminal management system shown in FIG. The SIP server 20 includes a proxy response function unit 23 in addition to the proxy server 21 and the registration server 22. The SIP terminal (management target device) 30 includes a management target function unit 32 in addition to the user agent 31.

  The management station 10 performs device management corresponding to existing SNMP. The management station 10 sends a response request (ICMP Echo Request) for inquiring the operation status of the SIP terminal (managed device) 30 to the proxy response function unit 23 of the SIP server 20, and management information of the SIP terminal (managed device) 30 ( A request (SNMP Get Request) for inquiring MIB information) is transmitted. Further, the management station 10 receives a response response (ICMP Echo Reply) and non-delivery notification (ICMP Destination Unreachable), a response to the request (MIB information), and a notification by a trap from the proxy response function unit 23.

  The SIP terminal (managed device) 30 is, for example, a smartphone or tablet terminal that supports SIP, and transmits registration information of the own terminal and management information of the own terminal to the SIP server 20 using a SIP message. is there.

  The user agent 31 sends a register message to the proxy server 21 when the SIP terminal (managed device) 30 is activated or before the SIP user agent timer (not shown) becomes zero. Send. This registration message includes the SIP URI of the SIP terminal (managed device) 30 that is the transmission source. When the user agent 31 receives a registration completion message from the proxy server 21, the user agent 31 sets an expiration date (Expires) in the user agent timer. The user agent 31 decrements the user agent timer by 1 every second.

  The management target function unit 32 is a function unit that transmits a response including management information of the SIP terminal (management target device) 30 to the proxy response function unit 23 and notifies a trap. When the management target function unit 32 receives a request from the proxy response function unit 23 (converted from the SNMP message to the SIP message by the proxy response function unit 23), the management target function unit 32 receives management information (information corresponding to MIB information in SNMP). ) As a response to the proxy response function unit 23. In addition, the management target function unit 32 transmits a trap (notification) to the proxy response function unit 23 when a predetermined event occurs or a management information value exceeds a preset threshold value. These “events” and “thresholds” are specified by the administrator via the management station 10 and held in the management target function unit 32, and conform to the standard functions of SNMP. Therefore, detailed description in the present invention will not be made.

  The SIP server 20 performs SIP communication with the SIP terminal (managed device) 30 to manage the operation status (life status) of the SIP terminal (managed device) 30 and from the management station 10 to the SIP terminal (managed device). In response to the response request and request to 30, the SIP terminal (managed device) 30 responds on behalf of the request, or the SIP terminal (managed device) 30 sends a request converted into a SIP message.

  When the proxy server 21 receives the registration message from the user agent 31, the proxy server 21 transmits the registration message to the registration server 22. When the proxy server 21 receives the registration completion message from the registration server 22, the proxy server 21 transmits the registration completion message to the user agent 31. The proxy server 21 refers to the session timer management table shown in Table 1 when the session expiration time (Session Expires) is included when mediating the SIP message, and the session timer of the corresponding SIP URI is referred to. Set the session expiration date. The session expiration date is included in, for example, a registration message from the user agent 31. The proxy server 21 decrements the session timer by 1 every second. When the session timer becomes 0 or less, the proxy server 21 transmits a SIP URI and “SIP terminal (managed device) communication error” to the proxy response function unit 23 as an occurrence of a keep-alive error. Then, the subtraction of the session timer with respect to the SIP URI ends.

  When receiving the registration message from the proxy server 21, the registration server 22 authenticates the SIP terminal (managed device) 30. For authentication, processing normally performed in SIP is used, and details of the authentication method are not described in detail. When the authentication is successful, the registration server 22 transmits the SIP URI of the SIP terminal (managed device) 30 and “normal SIP terminal (managed device)” to the proxy response function unit 23, and sends a registration completion message to the proxy server. To 21. Also, the registration server 22 refers to the timer management table shown in Table 2 and initializes the corresponding SIP URI timer with a predetermined initial value (eg, 3,600 seconds). The registration server 22 decrements the timer by 1 every second. When the timer becomes 0 or less, the registration server 22 transmits a SIP URI and “SIP terminal (managed device) communication error” to the proxy response function unit 23 as a time-out has occurred, and the SIP End subtraction of the timer from the URI.

  The proxy response function unit 23 manages the operation status of the SIP terminal (managed device) 30 based on the SIP communication with the SIP terminal (managed device) 30, and sends the SIP terminal (managed device) 30 to the management station 10. Instead of the function unit, the function unit responds based on the operation status. When the proxy response function unit 23 receives the SIP URI and “SIP terminal (managed device) normal” from the registration server 22, the proxy response function unit 23 refers to the management table shown in Table 3 and changes the status of the corresponding SIP URI to “ Normal. When the proxy response function unit 23 receives the SIP URI and “SIP terminal (managed device) communication error” from the proxy server 21 or the registration server 22, the proxy response function unit 23 sets the status of the corresponding SIP URI to “abnormal”. And When the proxy response function unit 23 receives a response request (ICMP Echo Request) from the management station 10, the proxy response function unit 23 refers to the management table shown in Table 3 and when the state corresponding to the target IP address of the response request is normal, A response reply (ICMP Echo Reply) is transmitted, and in the case of abnormality, a non-delivery notification (ICMP Destination Unreachable) is transmitted. The proxy response function unit 23 responds to the management station 10 with the target IP address as the transmission source address at the time of transmission.

  The proxy response function unit 23 receives a request from the management station 10. The proxy response function unit 23 has a request whose value is constantly changing (a MIB information that is constantly changing, such as “number of xxx”, for example, see Non-Patent Document 7). The management table shown in Table 3 is referred to, and the request converted into the SIP message is transmitted to the SIP URI corresponding to the IP address. The proxy response function unit 23 stores the response to the request for the request whose value does not change (the MIB information whose value does not change such as “physical address” and “media type”). In this case, a response is transmitted to the management station 10 based on management information (MIB information) managed for each target IP address of the request. At this time, the proxy response function unit 23 makes a response to the management station 10 with the target IP address as the source address. If the response to the request is not stored, the proxy response function unit 23 refers to the management table shown in Table 3 based on the target IP address of the request, and performs the SIP response to the SIP URI corresponding to the IP address. Send the request converted to a message.

  The proxy response function unit 23 receives a response or a trap from the SIP terminal (managed device) 30. If the response does not change, the proxy response function unit 23 stores the response. The proxy response function unit 23 refers to the management table shown in Table 3 on the basis of the SIP URI of the response or trap, converts the response or trap into an SNMP message and manages it by using the IP address corresponding to the SIP URI as a transmission source. Transmit to station 10. The proxy response function unit 23 can receive and process response requests and responses of a plurality of different target IP addresses.

  FIG. 3 is a diagram showing a processing sequence of the SIP terminal management system according to the present invention. In order to clarify the processing according to the present invention, in the processing sequence shown in FIG. 3, among the processing required in normal SIP, challenge response processing and notification (Notify) at the time of registration are received. For example, error notification processing such as a prior notification request (Subscribe) transmission processing and a re-registration processing by the user agent 31 when registration is not completed is omitted.

  When the SIP terminal (managed device) 30 is activated, the user agent 31 transmits a registration message to the proxy server 21 (step S101). When the proxy server 21 receives the registration message from the user agent 31, the proxy server 21 transmits the registration message to the registration server 22 (step S102). When the registration server 22 receives the registration message from the proxy server 21, the registration server 22 authenticates the SIP terminal (managed device) 30 (step S103). If the authentication is successful, the registration server 22 transmits the SIP URI of the SIP terminal (managed device) 30 and “normal SIP terminal (managed device)” to the proxy response function unit 23 (step S104), and a registration completion message Is transmitted to the proxy server 21 (step S105). When the proxy server 21 receives the registration completion message from the registration server 22, the proxy server 21 transmits the registration completion message to the user agent 31 (step S106).

(Alive monitoring: normal operation)
The management station 10 transmits a response request for inquiring about the operating status of the SIP terminal (managed device) 30 to the proxy response function unit 23 of the SIP server 20 (step S107). The proxy response function unit 23 refers to the management table shown in Table 3, and transmits a response reply (ICMP Echo Reply) when the state corresponding to the target IP address of the response request is normal (step S108).

(Management information acquisition: When the response does not change)
The management station 10 transmits a request for inquiring management information (MIB information) of the SIP terminal (managed device) 30 to the proxy response function unit 23 of the SIP server 20 (step S109). If the response to the request does not change, the proxy response function unit 23 transmits the stored response to the management station 10 when the response is stored (step S110).

(Management information acquisition: Response changes)
The management station 10 transmits a request for inquiring management information (MIB information) of the SIP terminal (managed device) 30 to the proxy response function unit 23 of the SIP server 20, and the proxy response function unit 23 changes the response. Converts the request into a SIP message and transmits it to the management target function unit 32 of the corresponding SIP URI (step S111). The management target function unit 32 transmits management information (MIB information) for the received request as a response to the proxy response function unit 23. The proxy response function unit 23 converts the received response into an SNMP message and sends it to the management station 10. Transmit (step S112).

(Trap notification)
In addition, the management target function unit 32 transmits a trap (notification) to the proxy response function unit 23 when a predesignated event occurs or the management information value exceeds a preset threshold value. The response function unit 23 converts the received trap into an SNMP message and transmits it to the management station 10 (step S113).

(Alive monitoring: When operation is abnormal)
When the timer becomes 0 or less, the registration server 22 transmits a SIP URI and “SIP terminal (managed device) communication error” to the proxy response function unit 23, assuming that a timeout has occurred (step S114). ). Further, when the session timer becomes 0 or less, the proxy server 21 determines that a keep alive error has occurred, and notifies the proxy response function unit 23 of the SIP URI and “SIP terminal (managed device) communication error”. Is transmitted (step S115). The management station 10 transmits a response request for inquiring about the operating status of the SIP terminal (managed device) 30 to the proxy response function unit 23 of the SIP server 20 (step S116). The proxy response function unit 23 refers to the management table shown in Table 3, and transmits a non-delivery notification (ICMP Destination Unreachable) when the state corresponding to the target IP address of the response request is abnormal (step S117).

  Thus, according to the present embodiment, the proxy response function unit 23 manages the operation status of the SIP terminal (managed device) 30 based on the SIP communication with the SIP terminal (managed device) 30, and manages the management station 10. In response to a response request from the SIP terminal (managed device) 30 to the SIP terminal (managed device) 30, a response based on the operation status is made instead of the SIP terminal (managed device) 30. Thereby, it is not necessary to install Sync ML in the SIP terminal (management target device) 30, and it is possible to reduce the traffic of the life / death monitoring of the SIP terminal (management target device) 30. In particular, in mobile communication, the proxy response function unit 23 responds to a response request from the management station 10 based on the state of communication by SIP, so that communication for management occurs in the SIP terminal (managed device) 30. Therefore, power consumption related to wireless communication can be suppressed.

  When the proxy response function unit 23 receives a management information request for the SIP terminal (managed device) 30 from the management station 10, the proxy response function unit 23 converts the request into a SIP message and transmits the request to the SIP terminal (managed device) 30. The managed function unit 32 of the SIP terminal (managed device) 30 transmits management information for the request converted into the SIP message as a response to the proxy response function unit 23, and the proxy response function unit 23 converts the response into an SNMP message. The data is converted and transmitted to the management station 10. This allows SNMP terminals connected to private networks such as companies and SIP terminals such as smartphones and tablets connected to the carrier network to be integrated and managed by a management station that supports SNMP. it can. In particular, device management can be easily performed even with a SIP terminal whose storage capacity and processing capacity are remarkably limited due to cost factors, such as a single telephone or an interphone without a display.

  Further, when the proxy response function unit 23 receives a request from the management station 10, the proxy response function unit 23 stores a response to the request. If the response does not change, the proxy response function unit 23 transmits the stored response to the management station 10. . Thereby, generation | occurrence | production of the new communication accompanying apparatus management can be suppressed as much as possible.

(Second Embodiment)
The SIP terminal management system in the second embodiment includes a presence agent (not shown) in addition to the first embodiment. In the first embodiment, the alive monitoring of the SIP terminal (managed device) 30 uses a registration message from the user agent 31, a session timer of the proxy server 21, and a timer of the registration server 22. It was. According to the second embodiment, the operation status of the SIP terminal (managed device) 30 can be grasped by the presence agent, thereby accurately monitoring the operating status of the SIP terminal (managed device) 30. It becomes possible. Note that the basic operation of each functional unit in the second embodiment is the same as that in the first embodiment, and a description thereof will be omitted. Hereinafter, the operation of each functional unit related to the presence agent will be described in detail.

  The presence agent manages presence such as the state (normal / abnormal) of the SIP terminal (managed device) 30 using existing technology (for example, Non-Patent Document 8). Are arranged as presence servers.

  The user agent 31 of the SIP terminal (managed device) 30 sends “presence information (operation) to the presence agent when the SIP terminal (managed device) 30 is started or when there is an operation from the user. Medium) ”(PUBLISH). Further, the user agent 31 issues “presence information (stopped)” to the presence agent when the SIP terminal (managed device) 30 ends or when a stop operation is performed by the user ( PUBLISH). In this case, presence information with an expiration date of 0 seconds is issued to the presence agent.

  When the number of SIP terminals (managed devices) 30 increases, the proxy response function unit 23 transmits a notification request (SUBSCRIBE) regarding the SIP terminals (managed devices) 30 to the presence agent. When the number of SIP terminals (managed devices) 30 increases, the proxy response function unit 23 transmits the end of the notification request regarding the SIP terminals (managed devices) 30 to the presence agent.

  When the presence agent receives a notification request (SUBSCRIBE) regarding the SIP terminal (managed device) 30 from the proxy response function unit 23, the presence agent notifies (NOTIFY) presence information regarding the SIP terminal (managed device) 30.

  The proxy response function unit 23 receives a notification (NOTIFY) from the presence agent. When the proxy response function unit 23 receives “presence information (in operation)” as a notification (NOTIFY), the proxy response function unit 23 refers to the management table shown in Table 3 and sets the state of the corresponding SIP URI to “normal”. When the proxy response function unit 23 receives “presence information (stopped)” as a notification (NOTIFY), the proxy response function unit 23 sets the state of the corresponding SIP URI to “abnormal”.

  In this way, by using the presence agent, it is possible to more accurately monitor the operation (alive / dead) status of the SIP terminal (managed device) 30.

  Although the present invention has been described based on the drawings and examples, it should be noted that those skilled in the art can easily make various modifications and corrections based on the present disclosure. Therefore, it should be noted that these variations and modifications are included in the scope of the present invention. For example, the functions included in each component, each step, etc. can be rearranged so that there is no logical contradiction, and multiple components, steps, etc. can be combined or divided into one It is.

DESCRIPTION OF SYMBOLS 10 Management station 20 SIP server 21 Proxy server 22 Registration server 23 Proxy response function part 30 SIP terminal (device to be managed)
31 User Agent 32 Managed Function Unit 40 SNMP Terminal

Claims (8)

A management station that supports SNMP;
SIP terminal corresponding to SIP,
A SIP server for performing SIP communication with the SIP terminal,
The SIP server includes a proxy response function unit that manages an operation status of the SIP terminal based on the SIP communication with the SIP terminal;
The SIP terminal management system, wherein the proxy response function unit responds to a response request from the management station to the SIP terminal based on the operation status instead of the SIP terminal. When the proxy response function unit receives a management information request for the SIP terminal from the management station, the proxy response function unit converts the request into a SIP message and transmits the request to the SIP terminal.
The SIP terminal includes a management target function unit that transmits management information for the request converted into the SIP message to the proxy response function unit as a response.
The SIP terminal management system according to claim 1, wherein the proxy response function unit converts the response into an SNMP message and transmits the SNMP message to the management station.   The proxy response function unit stores a response to the request when the request is received from the management station, and transmits the response to the management station when the response does not change. The SIP terminal management system according to claim 2, characterized in that: A SIP server for performing SIP communication with a SIP terminal,
A proxy response function unit that manages the operation status of the SIP terminal based on the SIP communication with the SIP terminal;
The SIP response function unit responds to a response request from a management station corresponding to SNMP to the SIP terminal based on the operation status instead of the SIP terminal. When the proxy response function unit receives a management information request for the SIP terminal from the management station, the proxy response function unit converts the request into a SIP message and transmits the request to the SIP terminal.
5. The SIP server according to claim 4, wherein the proxy response function unit converts a response to the request received from the SIP terminal into an SNMP message and transmits the SNMP message to the management station.   The proxy response function unit stores a response to the request when the request is received from the management station, and transmits the response to the management station when the response does not change. The SIP server according to claim 5, wherein: A management station that supports SNMP;
SIP terminal corresponding to SIP,
A SIP terminal management method in a SIP terminal management system comprising: a SIP server that performs SIP communication with the SIP terminal,
The SIP server is
Managing the operating status of the SIP terminal based on the SIP communication with the SIP terminal;
Responding to a response request from the management station to the SIP terminal based on the operation status instead of the SIP terminal. When the SIP server receives a management information request for the SIP terminal from the management station, the request is converted into a SIP message and transmitted to the SIP terminal;
The SIP terminal transmitting management information for the request converted into the SIP message as a response to the proxy response function unit;
The SIP terminal management method according to claim 7, further comprising: a step in which the SIP server converts the response into an SNMP message and transmits the SNMP message to the management station.

Images