WO2006038436A1 - Sip端末制御システム - Google Patents
Sip端末制御システム Download PDFInfo
- Publication number
- WO2006038436A1 WO2006038436A1 PCT/JP2005/016760 JP2005016760W WO2006038436A1 WO 2006038436 A1 WO2006038436 A1 WO 2006038436A1 JP 2005016760 W JP2005016760 W JP 2005016760W WO 2006038436 A1 WO2006038436 A1 WO 2006038436A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- request
- address information
- control device
- sip
- Prior art date
Links
- 230000007246 mechanism Effects 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 17
- 230000004044 response Effects 0.000 description 14
- 238000000034 method Methods 0.000 description 9
- 238000004891 communication Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 230000004308 accommodation Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 239000000284 extract Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42136—Administration or customisation of services
- H04M3/42178—Administration or customisation of services by downloading data to substation equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/25—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service
- H04M2203/251—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service where a voice mode or a visual mode can be used interchangeably
- H04M2203/253—Aspects of automatic or semi-automatic exchanges related to user interface aspects of the telephonic communication service where a voice mode or a visual mode can be used interchangeably where a visual mode is used instead of a voice mode
Definitions
- the present invention occurred in the center system in order to download various data to a SIP terminal (meaning a terminal capable of connection control by SIP) and to upload various data to the SIP terminal.
- the present invention relates to a SIP terminal control system that notifies a SIP terminal of a download request, upload request, upgrade request, etc. via an IP network.
- a firmware distribution system for updating the firmware of a mobile phone terminal is known as a system for accessing the terminal via the center side IP network and updating the terminal software (for example, Patent Document 1). reference).
- the model name, version information of installed firmware, etc. for all mobile phone terminals are stored in a firmware distribution server in a database. Refer to this database to check the current firmware version of the specified model mobile phone terminal, and to install the latest version of firmware via the mobile phone network. to access. After confirming that this access is received by the mobile terminal and the mobile phone terminal is in an operable state, the firmware distribution server transmits the update firmware module to the mobile phone terminal.
- the device management server manages the address information (IP address, telephone number, etc.) of all managed terminals, and the device management server uses the address information to make a call connection to each individual terminal. Downloads, upgrades, etc. are performed with the line connected.
- the access destination terminal When the access destination terminal is viewed from the device management server on the IP network side, if the terminal is located inside the firewall, a download request is sent to the IP network side power terminal. An attempt to notify an upgrade request or upload request is rejected by the firewall. Therefore, as a countermeasure, the device management server needs to establish a session by making a call connection to each terminal one by one.
- Patent Document 1 Japanese Patent Laid-Open No. 2003-209510
- the object of the present invention is made in view of the above circumstances, and it is necessary to uniquely provide a database for managing the IP address of each terminal and an authentication mechanism for authenticating each terminal for terminal control. It is also necessary to provide a SIP terminal control system that can send download requests, upload requests, and upload requests to each terminal from the IP network side.
- the present invention notifies each terminal of various requests such as a download request, an upload request, and an upgrade request to the SIP terminal by using the SIP call control device SIP that accommodates the SIP terminal.
- the database that manages the IP address and the authentication mechanism that authenticates each terminal can use the existing functions of the IP call control device and can access the SIP terminal across the firewall by using SIP.
- FIG. 1 is an overall configuration diagram of a SIP terminal control system according to an embodiment of the present invention.
- FIG. 2 Sequence diagram when SIP terminal requests registration in one embodiment of the present invention
- FIG. 3 Sequence diagram when SIP terminal notifies version number in one embodiment of the present invention
- FIG. 4 Sequence diagram when terminal control server requests download in one embodiment of the invention
- FIG. 5 is a sequence diagram when the terminal control server makes an upload request in one embodiment of the present invention.
- FIG. 6 is a sequence diagram when the terminal management server Z version management device makes an upgrade request in one embodiment of the present invention.
- FIG.7 A diagram showing an example of the system configuration for uploading a data file recorded on an answering machine at home to a server.
- FIG. 8 A diagram showing a specific example of the SUBS CRIBE request used to notify the version management device of the version information of the client terminal
- FIG. 9 A diagram showing a specific example of a NOTIFY request used to notify a download request to a client terminal
- FIG. 10 A diagram showing a specific example of a SUBSCRIBE request for notifying the client terminal of an upload request by the IP call control device.
- FIG.11 A diagram showing a specific example of a NOTIFY request in which the client terminal power is also sent to the IP call controller.
- the center system generates a download request to the terminal, and upon receiving the download request, the IP call control apparatus acquires the address information database output terminal address information, and the address
- This is a SIP terminal control system in which the IP call control device uses information to connect to the terminal via an IP network and notify a download request.
- the IP call control apparatus receives a download request for the terminal issued by the center system, and the IP call control apparatus connects to the terminal via the IP network. Since the download request is notified, the center system does not have to have a database for managing the IP address of each terminal for terminal control and an authentication mechanism for authenticating each terminal, and the IP call control device is installed in the accommodating terminal. You can access the SIP terminal across the firewall.
- the download request can be notified.
- the IP call control device is connected to the terminal using a SIP message, notifies the terminal of a download request and notifies the address information of the download server.
- the center system generates an upload request to the terminal, and upon receiving the upload request, the IP call control device acquires address information database output terminal address information, and the address A SIP terminal control system, wherein the IP call control device uses information to connect to the terminal via an IP network and notify an upload request.
- the IP call control device receives an upload request for the terminal issued by the center system, and the IP call control device connects to the terminal via the IP network. Since the upload request is notified, there is no need for the center system to have a database for managing the IP address of each terminal for terminal control and an authentication mechanism for authenticating each terminal. You can access the SIP terminal across the firewall.
- the IP call control device is connected to the terminal using a SIP message, notifies the terminal of the upload request and notifies the upload destination address information.
- the center system generates an upgrade request for internal software or an environment file for the terminal, and upon receipt of this upgrade request, the IP call control device performs the address information database function. Get information and this ad
- the SIP terminal control system is characterized in that the IP call control device connects to the terminal via an IP network and notifies an update request using the less information.
- the IP call control device receives an upgrade request for the terminal issued by the center system, and the IP call control device connects to the terminal via the IP network. Therefore, it is not necessary for the center system to have a database that manages the IP address of each terminal and an authentication mechanism that authenticates each terminal for terminal control. As a result, the SIP terminal can be accessed through the firewall and an upgrade request can be notified.
- the IP call control device is connected to the terminal using a SIP message, notifies the terminal of the upgrade request and notifies the address information of the download server.
- the terminal control server generates a request for uploading an answering voice recording data file to the IP telephone
- the IP call control device receives an address information database in response to the occurrence of the upload request.
- the address information is acquired, and using this address information, the IP call control device connects to the IP telephone via the IP network to notify the upload request and the address information of the upload destination, and the IP that has received the upload request.
- the voice mail recording data file upload method is characterized in that the telephone sets upload the voice mail recording data file to an upload server designated as an upload destination.
- Still another aspect of the present invention is a step of receiving a download request for a terminal issued by a terminal control server, and acquiring address information of a terminal that is a notification destination of the received download request from an address information database of an accommodation terminal.
- a notification method comprising the steps of: using the address information to connect to the terminal via an IP network using a SIP message and notifying a download request.
- a step of accepting an upload request issued by a terminal control server to a terminal and acquiring address information of a terminal that is a notification destination of the accepted upload request from an address information database of an accommodation terminal Step and this
- a notification method comprising: connecting to the terminal via an IP network using address information using a SIP message and notifying an upload request.
- Still another aspect of the present invention provides a step of accepting an upgrade request for internal software or an environment file for a terminal issued by a management server, and an address information for a terminal that is a notification destination of the accepted upgrade request. And a step of notifying an upgrade request by connecting to the terminal via the IP network using a SIP message using the address information. .
- FIG. 1 is an overall configuration diagram of a SIP terminal control system according to the present embodiment.
- the SIP terminal side system 10 connects an IP telephone 11 as a SIP terminal to the LAN 12 and connects to the IP network 30 via the router 13 and the gateway 14.
- the gateway 14 has a NAT function and a firewall function.
- the SIP terminal side system 10 is connected to an existing switching apparatus 16 via a VoIP gateway 15 and can be connected to a public switching network.
- the SIP terminal is not limited to the IP telephone 11 or the like.
- the gateway 14 connected to the IP network 30 and the VoIP gateway 15 connected to the public exchange network can also be targeted.
- the power that illustrates IP telephone 11 as a SIP terminal in Fig. 1 In addition, personal computers, network-connected office equipment (network printers, Internet faxes, etc.), home appliances (IP TV equipment, IP video cameras, etc.) ) Can also be a target.
- the center-side system 20 includes an IP call control device 41, a terminal control server 51, and a download server 61.
- the IP call control device 41 and the terminal control server 51 and the IP call control device 41 and the download server 61 are connected by a dedicated line.
- the IP call control device 41 and the terminal control server 51 are not necessarily connected by a dedicated line, but a secure data communication environment is desirable.
- the IP call control device 41 and the download server 61 may be arranged independently on the IP network 30 without being included in the center side system 20 and operated by the same or different operators.
- the IP call control device 41 is connected to the IP network 30 via the LAN 42 and the router 43 and the SBC (Session Border Controller) 44.
- SBC44 is a NAT function in SIP and RTP And a firewall function.
- the IP call control device 41 includes an address information database 45 in which address information (IP address) of an accommodation terminal (including a gateway device) of the IP telephone 11 is registered.
- address information database 45 information necessary for authentication (user ID, password, etc.) other than the force call control for registering information can also be registered. For example, the file version number information of the accommodating terminal and the terminal status may be registered.
- the IP call control device 41 includes a database control unit 46 that reads from and writes to the address information database 45, a call control unit 47 that controls connection between SIP terminals by SIP with reference to the address information database 45, and a SIP terminal In addition to the authentication process for the registration request, an application unit 48 that executes various applications is provided.
- the IP call control device 41 is connected to the terminal control server 51 through a dedicated line via the router 49 and is connected to the download server 61 via a dedicated line via the router 40.
- the terminal control server 51 is connected to the IP network 30 from the gateway 53 via the LAN 52.
- the gateway 53 functions as a router and has a NAT function and a firewall function.
- the terminal control server 51 uses the SIP connection service by the IP call control device 41 to connect to the SIP terminal and notifies a download request, an upgrade request, or an upload request. Not only the notification of these requests, but also by connecting the terminal control server 51 and the SIP terminal by the IP call control device 41, the terminal control server 51 accesses the SIP terminal via the IP network 30 to perform various controls. It is possible to do.
- the terminal control server 51 is connected to the IP call control device 41 through a router 54 via a dedicated line.
- the download server 61 is connected to the IP network 30 from the gateway 63 via the LAN 62.
- the gateway 63 functions as a router and has a NAT function and a firewall function.
- the download server 61 receives the request from the terminal and downloads data to the request source terminal. For data transfer, an appropriate protocol such as FTP is used according to the data content.
- the above SIP terminal system may be configured to realize the functions of the NORATORs 13, 40, 43, 49, 54, and 64 with a switch.
- FIG. 2 is a sequence diagram when the SIP terminal makes a registration request to the IP call control device 41. Since the SIP terminal is a client that requests the IP call control device 41 to register address information, the SIP terminal is described as a client terminal in FIG.
- the client terminal is not limited to the IP phone 11 as long as it is a device that implements SIP and can be connected to the session by the IP call control device 41.
- VoIP gateway 15 can also be a target, and personal computers not shown in the figure, network-connected office equipment (network printers, Internet FAX, etc.), Internet home appliances (IP telephones, IP TV devices, etc.), etc. Can be a client terminal.
- the client terminal issues a registration request for requesting registration of its latest information (for example, address information and user ID) to the IP call control device 41 (S101). Registration requests can be made periodically, or triggered by some event.
- the IP call control device 41 receives a registration request issued by the client terminal via the IP network 30.
- the IP call control device 41 accepts the received registration request (T101) and issues an authentication request to the requesting client terminal (T102).
- the authentication request transmitted from the IP call control device 41 to the client terminal includes information necessary for authentication.
- the client terminal accepts an authentication request issued by the IP call control device 41 (S102), and returns a registration request including authentication information to the IP call control device 41 (S103).
- Authentication information to be returned includes information necessary for authentication.
- IP call control device 41 Upon receiving the authentication information transmitted from the client terminal (T103), IP call control device 41 confirms the authentication information ( ⁇ 104). For example, the user of the client terminal pre-registers in the address information database 45 and sees a match with the password. If the password matches, authentication success information is set (T105). If the password does not match, authentication failure information is set ( ⁇ 106). The authentication result is notified to the client terminal ( ⁇ 107).
- the client terminal accepts the authentication result notified from the IP call control device 41 (S104). If the accepted authentication result indicates an authentication failure, a registration request may be issued again to attempt registration.
- the IP call control device 41 uses T10 for the client terminal for which the authentication success information is set.
- the corresponding part of the address information database 45 is updated with the information received in 1 (for example, address information, user ID).
- the latest address information of the client terminal is registered in the address information database 45.
- the address information registered in the address information database 45 is the latest when all SIP terminals (client terminals) registered in the IP call control device 41 generate the above registration request periodically or irregularly. Updated to For example, even when the IP address changes as the client terminal moves between access points, the IP call control device 41 can always grasp the latest address information in response to a registration request from the client terminal.
- FIG. 3 shows a sequence in which the client terminal notifies its version number information to the version number management apparatus.
- the terminal control server 51 of the center-side system 20 can also serve as a version number management device, or a system configuration in which a version number management device is installed on the IP network 30 can be adopted.
- the client terminal notifies the version number information of the currently installed software to the IP call control device 41 periodically or when an event occurs (S201).
- SIP is used for communication between the client terminal and the IP call control device 41.
- the client terminal sends a version number notification using a SUBSCRIBE request, which is one of the SIP event notifications.
- Figure 8 shows a specific example of the SUBSCRIBE request used to notify the version number management device of the version number information of the client terminal. Describe the version information (information on the latest file) of the client terminal in the Event header field of the SUBSCRIBE request.
- the IP call control device 41 receives the SUBSCRIBE request issued by the client terminal, recognizes that the descriptive power of the Event header field is the version number notification, and accepts the version number notification (T201). If the client terminal is not a user registered in the address information database 45 of the IP call control device 41, the version number notification is not accepted. Upon receiving the version number notification, the IP call control device 41 sends version number information to the version number management device. Send data (T202). In this example, communication is also performed between the IP call control device 41 and the version number management device using SIP! /.
- the version information received by IP call controller 41 at T201 is SUBS.
- the version number management apparatus receives the version number information sent from the IP call control apparatus 41 in the form of a SUBSCRIBE request (Q201).
- the version management device has a version database in which version information is stored for each client.
- the received version information is stored in the version database (Q202).
- the version management device succeeds in storing the received version number information in the version database, it returns a version number notification OK indicating that the version number notification has been received (Q203).
- IP call control device 41 When the IP call control device 41 receives 200OK from the version number management device (T203), it transmits 200 ⁇ to the connection destination client terminal ( ⁇ 204).
- the client terminal receives 200 ⁇ ⁇ and confirms that the version number notification is completed (S202), and ends the version number notification process.
- the client terminal connects to the version management apparatus via the IP call control apparatus 41 via SIP, and uses the SUBSCRIBE request supported by SIP to transmit its version information to the version management apparatus. To notify.
- FIG. 4 is a sequence diagram in which the client terminal downloads data in response to a download request issued by the terminal control server 51.
- a SIP NOTIFY request (SIP message) is used to notify the download request.
- the terminal control server 51 generates a download request to the client terminal (Q3
- the download request is notified to the IP call controller 41 in the form of a NOTIFY request.
- the specific information for example, user ID
- the specific information of the client terminal that is the notification destination shall be included in the NOTIFY request.
- the IP call control device 41 receives the NOTIFY request from the terminal control server 51 and accepts the download request (T301). In this embodiment, the IP call control device 41 determines whether or not it is necessary to download a new file to the client terminal that is the notification destination (T302). If it is determined that an aisle download is required, a NOTIFY request is used to notify the client terminal of the download request (T303).
- the terminal control server 51 manages version number information of files installed in each client terminal.
- the IP call control device 41 has a version number management mechanism.
- the version number management device shown in FIG. 3 may be included in the IP call control device 41, or may be arranged outside and connected to the version number management device each time to make an inquiry.
- the latest version number of the client terminal that is the notification destination of the download request is obtained by the version number management mechanism.
- the latest version of the client terminal is compared with the version requested for download this time, and if they match, it is determined that the download is unnecessary. In this case, “200 OK” is returned to the terminal control server 51 and the process is terminated.
- FIG. 9 shows a specific example of a NOTIFY request used to notify a download request to a client terminal. Indicate that it is a file download request notification in the Event header field of the NOTIFY request.
- Multipart / mixed is specified in the Content-Type header field, and the access method (access-type) and access expiration date (expiration) for the site (download sano) that stores the file to be downloaded to the client terminal in the message body Write address information (URL)! /
- the client terminal receives the NOTIFY request from the IP call control device 41, recognizes that the description content of the header field is also a download request notification, and accepts the request (S301).
- the client terminal that has received the request extracts information necessary for downloading the file from the NOTIFY request.
- the file to be downloaded is stored in the download server 61, and the download server 61 is set to accept a download request having a client terminal capability via HTTP.
- the client terminal accesses the download server 61 by HTTP using the URL of the download server 61 described in the NOTIFY request. Then, a download request for requesting the file designated by the NOTIFY request is notified (S302).
- the download server 61 accepts a download request for the client terminal capability (D 301), the specified file is transmitted to the requesting client terminal (D3 02).
- files such as FTP and HTTP can be used to transfer files.
- the download server 61 ends the process when the data transmission of the file is completed (D303).
- the client terminal downloads a file from the download server 61 (S303). When the download is completed (S304), it is determined whether or not the download is successful (S305). If the download is successful, success information is set (S306). If the download is failed, failure information is set (S307). Finally, the client terminal notifies the result of the setting content in S306 or S307 to the IP call control device 41 (S308). As a result notification, 200OK is returned. In this way, the file is downloaded to the client terminal in response to the download request issued by the terminal control server 51.
- IP call control apparatus 41 Upon receiving 200OK in response to the download request notified to the client terminal in T303 (T304), IP call control apparatus 41 recognizes that the download request has been accepted, and transmits 200 ⁇ to terminal control server 51. ( ⁇ 305).
- terminal control server 51 Upon receiving 200OK in response to the download request notified to IP call control device 41 in Q301 (Q302), terminal control server 51 recognizes that the download request has been accepted and terminates the download request processing for the client terminal. To do.
- the download request issued by the terminal control server 51 outside the firewall when viewed from the client terminal (IP phone 11 or the like) is received by the IP call control device 41 that accommodates the client terminal. Since the request is transmitted to the client terminal, the terminal control server 51 has the latest address information and authentication mechanism of all terminals (including gateways) accommodated in the IP call control device 41. Download requests can be notified to client terminals over firewalls. Therefore, the system configuration of the terminal control server 51 functioning as the center system can be simplified, and the cost can be reduced.
- FIG. 5 shows that the client terminal is uploaded by the upload request issued by the terminal control server 51. It is a sequence diagram to load.
- a SIP SUBSCRIBE request is used for notification of an upload request.
- the data to be uploaded is not particularly limited as long as it is data held in the client terminal. For example, communication quality information, communication history (log), control program, environment information, etc. can be targeted.
- the terminal control server 51 When requesting uploading of data held in the client terminal, the terminal control server 51 notifies the upload request to the IP call control device 41 having the client terminal as the accommodating terminal (Q401).
- the upload request is made in the SUBSCRIBE request format.
- IP call control apparatus 41 receives the SUBSCRIBE request from terminal control server 51 and accepts the upload request (T401).
- the IP call control device 41 acquires the IP address of the client terminal designated as the notification destination from the terminal control server 51 from the address information database 45 using the user ID included in the SUBSCRIBE request as a key. If the IP address of the client terminal exists in the address information database 45, it means that the client terminal is a terminal accommodating the IP call control device 41.
- the IP call control device 41 notifies the client terminal of an upload request (T402). Upload requests are made using SUB SCRIBE requests.
- FIG. 10 is a diagram showing a specific example of a SUBSCRIBE request for notifying an upload request from the IP call control device 41 to the client terminal.
- the data type requesting upload (terminal setting data in this example) is described.
- the address information of the upload destination (IP call control device) is described in the Contact header field.
- the client terminal uploads the terminal setting data to the IP call control device 41 (S402a).
- the NOTIFY request is used to notify the terminal setting data requested by the SUBSCRIBE request.
- FIG. 11 is a specific example of a NOTIFY request transmitted from the client terminal to the IP call control device 41.
- the data type (terminal setting data in this example) to be notified is described in the Event header field of the NOTIFY request.
- the setting data that is the data body to be uploaded is described in the message body.
- the IP call control device 41 receives a NOTIFY request in response to the SUBSCRIBE request transmitted in T402 (T403a). Extract MIME body from received NOTIFY request The terminal setting data is acquired, and the terminal setting data is transmitted to the terminal control server 51 (T404).
- the NOTIFY request format can also be used for data transmission to the terminal control server 51.
- Terminal control server 51 receives a NOTIFY request for the SUBSCRIBE request transmitted in Q401 (Q402). retrieve the terminal setting data from the received NOTIFY request, save it for terminal management, and end the upload request processing.
- the IP call control device 41 when the client terminal uploads to the IP call control device 41 (S402b), the IP call control device 41 does not transmit to the terminal control server 51, but the IP call control device 41 41 may store and manage (T403b). For example, the version information of the client terminal is uploaded to the IP call control device 41, and used to check the version information of the corresponding client terminal when a file download request is received from the terminal control server 51.
- an upload server different from the terminal control server 51 and the IP call control device 41 may be installed on the IP network 30 so that the client terminal capability of accepting the upload request is directly uploaded to the upload server. good.
- the IP call controller 41 is T
- the protocol used for uploading data to the client terminal IP call control device 41 or the upload server is not limited to SIP, and protocols such as HTTP and FTP may be used.
- the upload request issued by the terminal control server 51 outside the firewall as viewed from the client terminal is transmitted to the IP call control device 41 that accommodates the client terminal using the SIP request. Since it is configured to communicate to the client terminal, the terminal control server 51 has the latest address information and authentication mechanism for all terminals (including gateways) accommodated in the IP call control device 41, and can overcome the firewall. The upload request can be notified to the client terminal. Therefore, the system configuration of the terminal control server 51 functioning as the center system can be simplified, and the cost can be reduced. Next, the operation when the internal software or environment file of the client terminal is upgraded by the upgrade request issued by the terminal management server Z version management apparatus V will be described.
- a terminal management server or a version management device may be used as a device that issues an upgrade request.
- the terminal management server Z version management device is not shown in FIG. 1, the terminal control server 51 may also be used, or may be installed on the IP network 30.
- the terminal management server that is also used by the terminal control server 51 generates an upgrade request.
- FIG. 6 is a sequence diagram in which the client terminal upgrades the internal software or environment file in response to an upgrade request issued by the terminal management server.
- a NOTIFY request is used for notification of an upgrade request from the IP call control device 41 to the client terminal.
- the terminal management server checks the version information of each client terminal that is the accommodating terminal of the IP call control device 41 (Q501), and if it determines that the internal software or environment file needs to be upgraded, it issues an upgrade request. Occurs (Q502). For example, it is determined whether the internal software or environment file needs to be upgraded from the version information sent to the client terminal, and if a client terminal using an old version of the internal software or environment file is detected, the client terminal An upgrade request is issued. The upgrade request can be notified to the IP call controller 41 in the form of a NOTIFY request.
- the IP call control device 41 receives the upgrade request notified from the terminal management server (T501).
- the IP call control device 41 accepts the request and searches the address information database 45 for the IP address of the client terminal that is the notification destination using the user ID as a key. If the address information of the client terminal is registered in the address information database 45, the client terminal is an accommodation terminal authenticated by the IP call control device 41. After obtaining the IP address of the client terminal, the IP call control device 41 transmits an upgrade request with the IP address as the transmission destination (T502).
- the upgrade request that the IP call control device 41 notifies the client terminal is made using a NOTIFY request. This NOTIFY request has the same configuration as shown in Fig. 9. Can do.
- Event header field of the NOTIFY request is a description requesting the upgrade of the internal software or environment file, and the address information (URL) of the server that stores the upgrade data in the message body of the NOTIFY request and the information specifying the upgrade data Describe.
- the client terminal receives the NOTIFY request related to the upgrade request, receives the upgrade request (S501), and determines whether or not the upgrade is possible (S502). For example, if the software to be upgraded is being used, it is determined that the upgrade is not possible and the process is terminated. On the other hand, if it is determined in S502 that the upgrade is possible, a download request is issued to the server with reference to the contact information included in the received NOTIFY request (S503).
- the contact information is data such as address information (URL) of the server storing the upgrade data and information specifying the upgrade data. In this example, it is assumed that the download server 61 shown in FIG. 1 is specified by the contact information.
- the download server 61 also receives the download request for the client terminal and accepts the request (D501), and then transmits the requested data (internal software, environment file, etc.) to the client terminal (D502). ). When transmission of all corresponding data is completed (D503), the download is terminated.
- the client terminal receives and stores response data for the download request (S504).
- S505 When the download is completed (S505), 200OK is returned to the IP call controller 41 in response to the NOTIFY request received in S501 (S506). This informs that the download of the internal software or environment file requested for the upgrade has been completed.
- IP call control device 41 When IP call control device 41 receives 200OK in response to the NOTIFY request transmitted in T502 (T503), it returns 200OK in response to the NOTIFY request received in T501 (T504). As a result, the result of the upgrade request is notified to the requesting terminal management server.
- the terminal management server receives 200OK in response to the NOTIFY request sent in Q502 (Q503), it means that it has received the result for the upgrade request, and a series of updates. Finish the grade request processing.
- FIG. 7 shows an example of a system configuration when a data file recorded on an answering machine at home is uploaded to a server.
- a recording device 72 is attached to the IP phone 71 at home! The data file recorded in the recording device 72 can be transmitted from the IP phone 71 to the IP network 30.
- the IP phone 71 is connected to the LAN 73 and can be connected to the IP network 30 via the router 74.
- the user can access the upload server 91 from the company personal computer (PC) 81 to obtain the recorded data file.
- the PC 81 is connected to the LAN 82 and can be connected to the IP network 30 via the router 83 and the gateway 84.
- the upload server 91 can be configured by a Web server.
- the upload server 91 is connected to the LAN 92 and can be connected to the IP network 30 via the gateway 93.
- IP phone 71 at home converts the message input from the caller into voice mail recording data and stores it in recording device 72.
- the data file stored in the recording device 72 of the IP phone 71 is uploaded to the upload server 91 in response to an upload request from the terminal control server 51.
- an IP call control device 41 is interposed in the upload. That is, the IP call control device 41 accepts an upload request issued by the terminal control server 51, and sends a SUBSCRIBE request from the IP call control device 41 to the corresponding IP phone 71 to notify the upload request.
- the IP phone 71 which is a SIP terminal transmits the data file of the answering machine recording data stored in the recording device 72 to the upload server 91.
- the user accesses the upload server 91 from the PC 81 outside the home, and downloads the data file of the voice mail recording data uploaded from the IP phone 71 at home.
- the recorded data on the answering machine at home can be heard by playing the data file of the answering machine recording data downloaded to PC81.
- the voice mail recording data recorded by the IP phone 71 at home is Since the upload request issued by the terminal control server 51 can be uploaded to the upload server 91, the IP phone 71 can be recorded on the answering machine at home by simply installing the answering machine and uploading function on the IP phone 71. You can listen to the contents.
- the target of upload data uploaded from a SIP terminal is not limited to the data described above.
- various types of communication records (information) of SIP terminals can be targeted, and the quality of voice information, information on whether or not the voice has reached the connection, and communication history (log) may be targeted. .
- the present invention does not require a unique database for managing the IP address of each terminal or an authentication mechanism for authenticating each terminal for terminal control, and is downloaded to each terminal on the IP network side. Request, upgrade request, upload request can be notified, SI
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephonic Communication Services (AREA)
- Computer And Data Communications (AREA)
- Stored Programmes (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/576,617 US20080059640A1 (en) | 2004-10-05 | 2005-09-12 | Sip Terminal Control System |
EP05782088A EP1798944A4 (en) | 2004-10-05 | 2005-09-12 | SIP TERMINAL CONTROL SYSTEM |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004-293126 | 2004-10-05 | ||
JP2004293126A JP4348271B2 (ja) | 2004-10-05 | 2004-10-05 | Sip端末制御システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006038436A1 true WO2006038436A1 (ja) | 2006-04-13 |
Family
ID=36142517
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/016760 WO2006038436A1 (ja) | 2004-10-05 | 2005-09-12 | Sip端末制御システム |
Country Status (5)
Country | Link |
---|---|
US (1) | US20080059640A1 (ja) |
EP (1) | EP1798944A4 (ja) |
JP (1) | JP4348271B2 (ja) |
CN (1) | CN101053244A (ja) |
WO (1) | WO2006038436A1 (ja) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BRPI0520536A2 (pt) * | 2005-09-15 | 2009-06-13 | Ericsson Telefon Ab L M | método de sincronizar dados armazenados em um cliente de subsistema de multimìdia de ip com dados armazenados em um servidor de aplicação de sip do subsistema de multimìdia de ip, terminal de cliente de subsistema de multimìdia de ip, e, servidor de aplicação de sip |
JP4551866B2 (ja) * | 2005-12-07 | 2010-09-29 | 株式会社リコー | 通信システムおよび呼制御サーバ装置およびプログラム |
US20090092109A1 (en) * | 2005-12-19 | 2009-04-09 | Torbjorn Cagenius | Method and Apparatus for Enabling Discovery Within a Home Network |
JP4698486B2 (ja) * | 2006-05-29 | 2011-06-08 | Necインフロンティア株式会社 | Ip電話サービスシステム及びip電話サービス方法 |
JP2008042739A (ja) * | 2006-08-09 | 2008-02-21 | Nec Access Technica Ltd | Sipによるipアドレス取得方法、ネットワーク・システム、及びsip端末 |
JP2008217587A (ja) * | 2007-03-06 | 2008-09-18 | Nec Infrontia Corp | 双方向コンテンツ表示システム及び方法 |
JP4881252B2 (ja) * | 2007-07-31 | 2012-02-22 | 株式会社東芝 | インタフェース装置、このインタフェース装置を備えた交換装置及びインタフェース装置で使用される制御方法 |
US8665897B2 (en) * | 2009-10-26 | 2014-03-04 | Adc Dsl Systems, Inc. | Systems and methods for high-speed digital subscriber line software download |
JP2013077956A (ja) * | 2011-09-30 | 2013-04-25 | Nomura Research Institute Ltd | モバイル端末管理システム |
US20130227162A1 (en) * | 2012-02-29 | 2013-08-29 | F-Secure Corporation | Management of Data Upload Speed |
JP5387730B2 (ja) * | 2012-06-11 | 2014-01-15 | 株式会社ナカヨ通信機 | サーバ機能を選択可能な電話端末 |
CN102833436A (zh) * | 2012-08-31 | 2012-12-19 | 电子科技大学 | 实现voip代理的方法以及系统 |
CN103248775A (zh) * | 2012-11-16 | 2013-08-14 | 佳都新太科技股份有限公司 | 一种基于ip网络并线录音的实现方案 |
US8825814B1 (en) * | 2013-05-23 | 2014-09-02 | Vonage Network Llc | Method and apparatus for minimizing application delay by pushing application notifications |
WO2019111810A1 (ja) * | 2017-12-05 | 2019-06-13 | Necプラットフォームズ株式会社 | 通信装置、通信データ記録システム、通信方法、およびプログラム |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002082794A2 (en) * | 2001-04-03 | 2002-10-17 | Voxpath Networks, Inc. | System and method for performing ip telephony |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6678735B1 (en) * | 2000-01-26 | 2004-01-13 | Nortel Networks Limited | Method and apparatus for a sip client manager |
US7024461B1 (en) * | 2000-04-28 | 2006-04-04 | Nortel Networks Limited | Session initiation protocol enabled set-top device |
JP4212230B2 (ja) * | 2000-10-31 | 2009-01-21 | 富士通株式会社 | メディア通信システム及び該システムにおける端末装置 |
JP4349766B2 (ja) * | 2001-12-07 | 2009-10-21 | 株式会社日立製作所 | アドレス変換装置 |
US20030236892A1 (en) * | 2002-05-31 | 2003-12-25 | Stephane Coulombe | System for adaptation of SIP messages based on recipient's terminal capabilities and preferences |
JP2004080567A (ja) * | 2002-08-21 | 2004-03-11 | Matsushita Electric Ind Co Ltd | ネットワーク端末装置とアドレス管理サーバ、及びそのネットワーク通信方法 |
KR100475186B1 (ko) * | 2002-12-02 | 2005-03-10 | 삼성전자주식회사 | 접속 설정 프로토콜을 이용한 단말 장치의 등록 방법 |
US7110763B2 (en) * | 2002-12-12 | 2006-09-19 | Alcatel | Graphical proxy for less capable terminals |
JP2004206459A (ja) * | 2002-12-25 | 2004-07-22 | Matsushita Electric Ind Co Ltd | セッション管理装置 |
US20050015499A1 (en) * | 2003-05-15 | 2005-01-20 | Georg Mayer | Method and apparatus for SIP user agent discovery of configuration server |
KR100547115B1 (ko) * | 2003-05-23 | 2006-01-26 | 삼성전자주식회사 | Sip 프로토콜을 확장한 rdt 메시지를 이용하여클라이언트와 서버 간 데이터를 송수신하는 방법,기록매체, 시스템, 클라이언트(uac), 및 서버(uas) |
JP2005020286A (ja) * | 2003-06-25 | 2005-01-20 | Matsushita Electric Ind Co Ltd | ネットワーク管理装置、携帯端末、ネットワークシステム、及びこれを用いた通信方法 |
DE60315361T2 (de) * | 2003-08-01 | 2008-05-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Verfahren und vorrichtung zum routen einer dienstanforderung |
US20050055687A1 (en) * | 2003-09-04 | 2005-03-10 | Georg Mayer | Software update information via session initiation protocol event packages |
JP2005086467A (ja) * | 2003-09-09 | 2005-03-31 | Hitachi Ltd | セッション制御装置、情報通信端末、サーバ、及び端末 |
US8085741B2 (en) * | 2004-03-10 | 2011-12-27 | Core Wireless Licensing S.A.R.L. | System and method for pushing content to a terminal utilizing a network-initiated data service technique |
ES2346110T3 (es) * | 2004-04-13 | 2010-10-08 | Research In Motion Limited | Metodo para un terminal de pulsacion para hablar (ptt) de protocolo de inicio de sesion para indicar el modo operativo de respuesta a un servidor de red de pulsacion para hablar (ptt) de protocolo de internet. |
US20060050683A1 (en) * | 2004-09-09 | 2006-03-09 | Nextel Communications, Inc. | Prioritization of service requests received at a session initiation protocol (SIP) server |
-
2004
- 2004-10-05 JP JP2004293126A patent/JP4348271B2/ja not_active Expired - Fee Related
-
2005
- 2005-09-12 US US11/576,617 patent/US20080059640A1/en not_active Abandoned
- 2005-09-12 WO PCT/JP2005/016760 patent/WO2006038436A1/ja active Application Filing
- 2005-09-12 CN CNA2005800339397A patent/CN101053244A/zh active Pending
- 2005-09-12 EP EP05782088A patent/EP1798944A4/en not_active Withdrawn
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002082794A2 (en) * | 2001-04-03 | 2002-10-17 | Voxpath Networks, Inc. | System and method for performing ip telephony |
Non-Patent Citations (2)
Title |
---|
PETRIE D.: "A Framework for SIP User Agent Configuration.", INTERNET DRAFT., November 2001 (2001-11-01), XP015004838, Retrieved from the Internet <URL:http://www.watersprings.org/pub/id/draft-petrie-sip-config-framework-01.txt> [retrieved on 20051206] * |
See also references of EP1798944A4 * |
Also Published As
Publication number | Publication date |
---|---|
JP2006109111A (ja) | 2006-04-20 |
US20080059640A1 (en) | 2008-03-06 |
EP1798944A4 (en) | 2011-12-21 |
CN101053244A (zh) | 2007-10-10 |
JP4348271B2 (ja) | 2009-10-21 |
EP1798944A1 (en) | 2007-06-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2006038436A1 (ja) | Sip端末制御システム | |
EP2028825B1 (en) | Configuration of network devices | |
US8954542B2 (en) | Method and system for transmitting and receiving configuration and registration information for session initiation protocol devices | |
US20090201830A1 (en) | Method & system for network entity configuration | |
US7627656B1 (en) | Providing configuration information to an endpoint | |
CN101543012B (zh) | 通信系统 | |
JP5470402B2 (ja) | 移動通信ネットワークにおけるチャット/VoIPサービスの提供方法並びにネットワークサーバ及び移動ユーザ装置 | |
JP5180048B2 (ja) | サービス提供システム、サービス提供方法およびサービス提供プログラム | |
US8885810B2 (en) | Telephone communication control apparatus, telephone communication system and telephone communication control method used for the same | |
US20090175270A1 (en) | Telephone recording and storing arbitrary keystrokes sequence with replay with a single stroke | |
US20110131177A1 (en) | Method and system for providing rapid updating of services in an ims environment | |
JP5263287B2 (ja) | 通信システム及び通信方法 | |
JP2004186893A (ja) | Lan外接続ipキーテレフォンシステム及びその端末と主装置並びにそのlan外接続方法 | |
WO2012081950A2 (ko) | 복수의 클라이언트 간의 어플리케이션 자동 공유 방법 및 장치 | |
JP5227885B2 (ja) | WebシステムとVoIPシステムとを連携する連携方法、VoIPシステム、および連携プログラム | |
JP4800332B2 (ja) | サービス提供システム、サービス提供方法およびサービス提供プログラム | |
JP5260467B2 (ja) | アクセス制御システムおよびアクセス制御方法 | |
JP4950096B2 (ja) | サービス提供システム、サービス提供方法およびサービス提供プログラム | |
JP4715146B2 (ja) | プレゼンス情報処理システム、プレゼンス情報処理方法およびプレゼンス情報処理プログラム | |
WO2009130931A1 (ja) | Imsシステム、as装置およびmgw装置、imsシステムにおける輻輳規制通知方法 | |
KR20050038867A (ko) | 원격지 다자간 공동 문서 작업 환경 서비스 제공 시스템및 방법 | |
JP2003283668A (ja) | 携帯情報通信端末装置のサービス設定変更方法、携帯情報通信端末装置のサービス設定自動変更システム、携帯情報通信端末装置、管理サーバネットワークシステム | |
KR100629792B1 (ko) | 기업용 무선 어플리케이션 서비스를 위한 리퀘스트 핸들러및 그 처리방법 | |
JP2011008712A (ja) | サービス提供システムおよびサービス提供方法 | |
KR100927048B1 (ko) | 부가서비스 서버, 브이오아이피 장치 및 터미널 어댑터장치의 작동방법 및 그 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11576617 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200580033939.7 Country of ref document: CN Ref document number: 2005782088 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2005782088 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 11576617 Country of ref document: US |