WO2006080080A1 - Systeme et procede de gestion d'appels telephoniques - Google Patents

Systeme et procede de gestion d'appels telephoniques Download PDF

Info

Publication number
WO2006080080A1
WO2006080080A1 PCT/JP2005/001237 JP2005001237W WO2006080080A1 WO 2006080080 A1 WO2006080080 A1 WO 2006080080A1 JP 2005001237 W JP2005001237 W JP 2005001237W WO 2006080080 A1 WO2006080080 A1 WO 2006080080A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
request
destination
user
call
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2005/001237
Other languages
English (en)
Japanese (ja)
Inventor
Takashi Matsumoto
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujitsu Ltd
Original Assignee
Fujitsu Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujitsu Ltd filed Critical Fujitsu Ltd
Priority to PCT/JP2005/001237 priority Critical patent/WO2006080080A1/fr
Priority to JP2007500392A priority patent/JPWO2006080080A1/ja
Publication of WO2006080080A1 publication Critical patent/WO2006080080A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/42365—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity
    • H04M3/42374—Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity where the information is provided to a monitoring entity such as a potential calling party or a call processing server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • the present invention relates to a telephone management system and a telephone management method between a plurality of telephones including a mobile telephone, and more particularly to a telephone management system and a telephone management method for selecting one telephone from a plurality of telephones and connecting lines. .
  • a telephone number of a fixed telephone (telephone network or VoIP (Voice over Internet Protocol)) of the office of the department to which the user belongs is assigned. Users use fixed telephones and mobile telephones according to the situation. At this time, there is a technique for changing the contents of the call service based on the user's presence information.
  • the presence information is information indicating a situation where the user is currently placed.
  • presence information changes dynamically, such as attendance and attendance information. Therefore, presence information that dynamically changes depending on the computer system can also be managed. For example, multiple personal configurations such as personal enrollment information, attendance information, schedule information, meeting attendance information, telephone call forwarding destination, telephone relay discrimination, and building management based on personal information
  • personal management system that comprehensively and timely manages manufacturing information
  • VoIP calls may be made within the DMZ (demilitarized zone) of the intranet and outside the DMZ.
  • line connection technology via DMZ is used.
  • there is a technique for realizing call establishment and multimedia communication between a terminal connected to an intranet and a terminal connected to an external network while ensuring the security of the intranet see Patent Document 3).
  • Patent Document 1 Japanese Patent Laid-Open No. 2003-324472
  • Patent Document 2 Japanese Patent Laid-Open No. 11-39570
  • Patent Document 3 Japanese Patent Laid-Open No. 2003-324485
  • the communication terminal selection unit selects a transfer destination terminal based on the terminal information list received from the presence management unit. Then, the caller terminal receives the information of the transfer destination terminal selected by the communication terminal selection unit via the call transfer unit. Then, the caller terminal makes an incoming call to the transfer destination terminal (see FIG. 10 of the application).
  • This gives an example For example, based on presence information such as user busyness and job rank, a communication terminal having the optimum number of communication terminals that can be used by the recipient can be selected.
  • a call request from a caller terminal is received by a telephone call control device, the telephone call control device determines a destination terminal, and transmits an incoming call request to the destination terminal.
  • the telephone call control device that has received a call request from the caller terminal does not refer to means for coordinating with the communication terminal selection unit. They can't be configured to connect the call line between the called terminal and the caller terminal according to the presence information just by outputting the call request. However, it is more convenient for users to connect to the most suitable phone according to their presence information simply by making a call from the caller terminal. Is desired.
  • the present invention has been made in view of the above points, and by simply outputting a call request from the caller terminal device, the call destination terminal device and the caller terminal device according to the presence information are output.
  • the present invention provides a telephone management system that performs incoming processing on another terminal device based on a call request from the terminal device as shown in FIG.
  • This telephone management system responds to an address conversion request including presence management device 1 that manages presence information indicating the state of a user and destination designation information that designates one or more users.
  • User presence information corresponding to the destination designation information indicated in the address translation request is acquired from the presence management device 1, and the destination terminal device 5 corresponding to the presence information is determined according to the predetermined destination selection criteria.
  • Address translation device 2 that outputs address information indicating the address of destination terminal device 5 as a response to the address translation request, and a call request from call source terminal device 4 are received, and an incoming call indicated by the call request is received.
  • An address translation request for obtaining an address identifying the destination of the destination designation information is output to the address translation device 2, and a response is received from the address translation device 2. Having a telephone call control equipment 3 for incoming processing to the destination terminal device 5 to be uniquely indicated by the address information. [0013] According to such a telephone management system, when there is a call request from the call source terminal device 4, the telephone call control device 3 causes the address conversion request including the destination designation information indicated by the call request. Is output to the address translation device 2. Next, the address translation device 2 responds to the address translation request including the destination designation information for designating one or more users, and the presence that designates the user corresponding to the destination designation information indicated in the address translation request.
  • the information acquisition request is transmitted to the presence management apparatus 1 that manages presence information indicating the state where the user is placed.
  • the presence management device 1 responds with the presence information of the user specified in the presence information acquisition request.
  • the address conversion device 2 determines the receiving terminal device 5 according to the presence information returned from the presence management device 1 according to the predetermined destination selection criteria, and sets the address of the determined destination terminal device 5.
  • the address information shown is output to the telephone call control device 3. Then, the telephone call control device 3 performs an incoming call process on the destination terminal device 5 uniquely indicated by the address information returned from the address translation device 2.
  • a state where the user is placed is displayed.
  • Each of the destination designation information indicated by the request transmission request in response to a request transmission request including a presence management device for managing presence information to be indicated and two destination designation information for designating one or more users.
  • the presence information of the user corresponding to the presence information is acquired from the presence management device, two destination terminal devices according to the presence information are determined according to a predetermined destination selection criterion, and the address of the determined receiving terminal device is determined.
  • An address conversion device that outputs a two-party connection request specifying two address information indicating the address and the address conversion device power in response to the output two-party connection request.
  • a telephone management system comprising: a telephone call control device that performs incoming processing on the destination terminal device corresponding to each of two addresses specified in the incoming request.
  • a presence information acquisition request designating a user corresponding to each destination designation information indicated by the request transmission request is transmitted to the presence management apparatus.
  • the presence management device responds to the presence information acquisition request from the address translation device with the presence information of each user specified in the presence information acquisition request.
  • the address conversion device determines two destination terminal devices according to the presence information for each user responded from the presence management device according to a predetermined destination selection criterion, and the determined destination terminal device A two-party connection request specifying two address information indicating the address is output.
  • the two-party call controller outputs an incoming call request to the address specified in the two-party connection request.
  • the telephone call control device performs the incoming call processing for the destination terminal device corresponding to each of the two addresses specified in the incoming call request.
  • the two-party call controller controls the two-party call between the two receiving terminal devices that responded to the incoming call processing.
  • the destination terminal device corresponding to the destination designation information indicated in the call request is determined by the address conversion device according to the presence information, and the incoming call is determined by the telephone call control device. Incoming call processing was performed on the destination terminal.
  • the call source terminal device can process incoming calls to the terminal device according to the presence information only by outputting a call request in the same manner as a normal telephone call.
  • FIG. 1 is a diagram showing an outline of the present embodiment.
  • FIG. 2 is a diagram showing a system configuration example according to the embodiment of the present invention.
  • FIG. 3 is a diagram illustrating a hardware configuration example of a SIP server used in the present embodiment.
  • FIG. 4 is a block diagram showing functions of a terminal device and the like.
  • FIG. 5 is a diagram showing an example of a presence DB stored in a presence management server.
  • FIG. 6 is a block diagram showing functions of a SIP server and an address translation server.
  • FIG. 7 is a diagram showing an example data structure of an address analysis table.
  • FIG. 8 is a diagram showing an example of destination selection criteria.
  • FIG. 9 is a diagram showing a procedure of destination determination processing in response to a call request.
  • FIG. 10 is a diagram showing a processing procedure when a telephone line is connected in response to a request from a third party.
  • FIG. 11 is a diagram showing processing when an incoming call selection criterion is described in XSLT.
  • FIG. 12 A diagram showing information passed as XML data.
  • FIG. 13 is a flowchart showing a processing procedure by the address translation server.
  • FIG. 14 is a diagram showing a first example of priority determination criteria.
  • FIG. 15 is a diagram showing a second example of priority determination criteria.
  • FIG. 16 is a diagram showing a third example of priority determination criteria.
  • FIG. 17 is a diagram showing a fourth example of the priority determination criterion.
  • FIG. 1 is a diagram showing an outline of the present embodiment.
  • the telephone management system includes a presence management device 1, an address translation device 2, and a telephone call control device 3.
  • the presence management device 1 manages presence information indicating a state where the user is placed. For example, it is managed as information presence information such as whether or not the user is in the office and whether or not the user is logged in to the terminal device at his / her seat.
  • the address translation device 2 responds to the address translation request including the destination designation information designating one or more users, and the presence of the user corresponding to the destination designation information indicated by the address translation request Information is acquired from the presence management device 1.
  • the destination designation information includes information (name and employee number) for designating the user.
  • the address translation device 2 sets the destination terminal device 5 corresponding to the presence information to a predetermined value. Determine according to destination selection criteria. For the destination selection criteria, for example, if the user is logged in to the terminal device at his / her seat, his / her phone is the destination, and if the user is not talking to his / her terminal device, the mobile terminal device such as PHS is the destination. And so on are defined.
  • the address conversion device 2 when determining a destination from the terminal devices used by each of a plurality of users, the address conversion device 2 first selects a destination user based on a destination selection criterion. For example, the priority of telephone reception is determined in the Gnolepe, and the address translation device 2 determines whether or not it is possible to answer the telephone in order from the user with the highest priority (for example, whether or not it is present). . Next, the address translation device 2 selects the user with the highest priority among the users who can answer the call. And the address translation device 2
  • the destination terminal device is determined according to the destination selection criteria from among the terminal devices used by the selected user.
  • the address translation device 2 outputs address information indicating the determined address of the destination terminal device 5 as a response to the address translation request.
  • the telephone call control device 3 accepts a call request from the call source terminal device 4. Upon receiving the call request, the telephone call control device 3 outputs an address conversion request including the destination designation information indicated by the call request to the address conversion device 2. The telephone call control device 3 performs an incoming call process on the destination terminal device 5 that is uniquely indicated by the address information returned from the address translation device 2.
  • the call request transmitted from the caller terminal apparatus 4 is accepted by the telephone call control apparatus 3 (step Sl). Then, the telephone call control device 3 outputs an address conversion request for acquiring an address for identifying the destination of the destination designation information indicated by the call request to the address conversion device 2 (step S2). .
  • the address translation device 2 is in a state in which the presence information acquisition request designating the user corresponding to the destination designation information indicated by the address translation request is placed. Is transmitted to the presence management apparatus 1 that manages presence information indicating (step S3). Then, the presence management device 1 responds with the presence information of the user specified in the presence information acquisition request. [0027] Furthermore, the address translation device 2 determines the destination terminal device 5 corresponding to the presence information returned from the presence management device 1 according to a predetermined destination selection criterion (step S4). Then, the address translation device 2 outputs address information indicating the determined address of the destination terminal device 5 to the telephone call control device 3.
  • the incoming call processing is performed on the destination terminal device 5 that is uniquely indicated by the address information returned from the address translation device 2 (step S5). At this time, if the destination terminal device 5 responds to the incoming call, a call between the calling source terminal device 4 and the destination terminal device 5 is started.
  • the call source terminal device 4 only has to output a call request in the same manner as in a normal telephone call.
  • the incoming call processing to the terminal device according to the presence information can be performed without adding a special function to the calling source terminal device 4.
  • the call line between the caller terminal device 4 and the callee terminal device 5 is connected based on the call request transmitted from the caller terminal device 4. It is also possible to connect a call line between two other parties based on a request from a third party. Even in this case, the other two terminal devices can be selected based on the presence information.
  • FIG. 2 is a diagram showing a system configuration example according to the embodiment of the present invention.
  • the user 52 makes a call to the user 51.
  • a terminal device 410 and a fixed telephone 420 are placed in the seat of the user 51 in the office.
  • the terminal device 410 has a call function using VoIP.
  • the user 51 carries the mobile terminal device 430.
  • the user 53 uses the terminal device 530.
  • Intra Network 21 includes SIP (Session Initiation Protocol) server 100, address translation server 200, presence management server 310, LDAP (Lightweight Directory Access Protocol) server 320, business management server 330, access point 340, norator 350, and Terminal device 410 is connected.
  • SIP Session Initiation Protocol
  • LDAP Lightweight Directory Access Protocol
  • the SIP server 100 is a computer that manages IP telephones by SIP (call control protocol used for Internet telephones using VoIP).
  • the address translation server 200 is a computer that determines a connection destination device corresponding to a call in accordance with presence information.
  • the presence management server 310 is a computer that manages user presence.
  • the LDAP server 320 is a computer that manages information on users who use the network.
  • the business management server 330 is a computer that executes various business operations using a Web server application or the like.
  • the norator 350 is connected to the Internet 33 and relays packets between the intranet 21 and the Internet 33.
  • a terminal device 530 is connected to the Internet 33.
  • the access point 340 is a device that performs wireless communication with other devices based on a wireless LAN (Local Area Network) standard.
  • the mobile terminal device 430 possessed by the user 51 can connect a telephone line to another mobile terminal device 510 by performing wireless communication with the access point 340.
  • the SIP server 100 is connected to the extension telephone network 22 and the gateway 360.
  • a fixed telephone 420 is connected to the extension telephone network 22.
  • the gateway 360 is connected to the fixed telephone network 31 and the wireless telephone network 32, and relays packets transmitted and received through these telephone networks.
  • a fixed telephone 520 is connected to the fixed telephone network 31.
  • a mobile terminal device 510 can be connected to the radio telephone network 32 by radio.
  • the devices in the system operate in cooperation with each other. Based on the presence information (indicating the current status) of user 51, the device to be called (terminal device 410, fixed telephone 420, or mobile terminal device 430) is selected by the system's cooperative operation Then, a communication line is connected between the selected device and the mobile terminal device 510.
  • the system according to the present embodiment has a function of calling other two users in response to a request from a third party and connecting a telephone line between the two users. Yes.
  • the user 53 can operate the terminal device 530 to make a call between the user 51 and the user 52. At this time, if the user 51 can use a plurality of terminal devices, the incoming call processing is performed on an appropriate terminal device according to the presence information.
  • the user 51 53 can instruct the terminal to make a call using a computer system.
  • a system corresponding to a terminal used by the user 53
  • the WEB server (corresponding to the terminal used by the user 53) that receives the question is the user's telephone (user 51 It is also possible to make a call between the telephone of the answerer (equivalent to the telephone of user 52).
  • the phone 51 connected to the user 51 is a self-seat telephone (fixed telephone 420), voice mail (voice mail server function in the business management server 330), VoIP-based ubiquitous telephone. It is assumed that there is a VoIP call function of the mobile terminal device 430 and a PHS ubiquitous telephone (PHS call function of the mobile terminal device 430).
  • each server shown in FIG. 2 can be realized by the following hardware.
  • FIG. 3 is a diagram illustrating a hardware configuration example of the SIP server used in the present embodiment.
  • the entire SIP server 100 is controlled by a CPU (Central Processing Unit) 101.
  • a random access memory (RAM) 102, a hard disk drive (HDD) 103, a graphic processing device 104, an input interface 105, and communication interfaces 106 and 107 are connected to the CPU 101 via a bus 108.
  • the RAM 102 temporarily stores at least a part of a ⁇ S (Operating System) program application program to be executed by the CPU 101. Also in RAM102 Stores various data necessary for processing by the CPU 101.
  • the HDD 103 stores the OS and application programs.
  • a monitor 11 is connected to the graphic processing device 104.
  • the graphic processing device 104 displays an image on the screen of the monitor 11 in accordance with a command from the CPU 101.
  • a keyboard 12 and a mouse 13 are connected to the input counter face 105.
  • the input interface 105 transmits a signal sent from the keyboard 12 or mouse 13 to the CPU 101 via the bus 108.
  • the communication interface 106 is connected to the intranet 21.
  • the communication interface 106 transmits / receives data to / from other computers via the intranet 21.
  • the communication interface 107 is connected to the gateway 360 via a communication medium such as a LAN.
  • the communication interface 106 transmits / receives data to / from the gateway 360.
  • FIG. 3 only the hardware configuration of the SIP server 100 is shown.
  • Address conversion server 200, presence management server 310, LDAP server 320, business management server 330, gateway 360, and terminal devices 410, 530 Can be realized with the same hardware configuration.
  • the terminal devices 410 and 530 are further provided with an audio input / output interface.
  • the audio input / output interface is connected to a VoIP microphone and speaker.
  • a user who uses the terminal devices 410 and 530 performs a voice call by VoIP using a microphone and a speaker.
  • FIG. 4 is a block diagram illustrating functions of the terminal device and the like.
  • the terminal device 410 includes a client application (APL) 411, a soft phone 412, a presence transmission unit 413, a web browser 414, and the like.
  • the client APL 411 is application software that executes various processes in the terminal device 410 in accordance with an operation input from a user.
  • Softphone 412 is application software for making calls via VoIP. is there.
  • Presence transmission unit 413 is application software for transmitting presence information of terminal device 410.
  • the web browser 414 is application software for browsing content provided by the web server 331 in the business management server 330.
  • the mobile terminal device 430 includes a client application (APL) 431, a soft phone 432, a presence transmission unit 433, a Web browser 434, and the like.
  • APL client application
  • the function of each component of the mobile terminal device 430 is the same as the component of the same name in the terminal device 410.
  • the presence management server 310 stores a presence DB acquired from another device.
  • the presence management server 310 transmits the presence DB of the designated user to the address translation server 200 in response to a request of the address translation server 200.
  • the business management server 330 is provided with a Web server 331, a voice mail server 332, and a linkage unit 333.
  • the Web server 331 transmits various Web contents (including contents created for mobile phones etc.) in response to HTTP requests.
  • the voice mail server 332 receives a voice message of a specific user partner by VoIP and registers it in the database. Then, the voice mail server 332 transmits the registered voice message to the user terminal device by VoIP in response to a request from the user.
  • the cooperation unit 333 requests the presence management server 310 to connect a telephone line using VoIP between a terminal device equipped with a Web browser and another terminal device.
  • a SIP 3PCC (Third Party Call Control) controller 110 is connected to the SIP server 100.
  • the SIP3PCC controller 110 is a control circuit that allows a third party to set up a call between two terminals.
  • the mobile terminal device 510 has a web browser 511 mounted thereon.
  • the web browser 511 is application software for browsing content provided by the web server 331 in the business management server 330.
  • the presence management server 310 acquires presence information from the presence transmission unit 413 of the terminal device 410 and the presence transmission unit 433 of the mobile terminal device 430. For example, from the terminal device 410 fixedly placed on the desk, whether or not the user has logged in, whether or not the operation input time has exceeded a predetermined time, etc. Is sent to the presence management server 310 as presence information. Also, from the mobile terminal device 430, information such as the strength of radio waves from a mobile phone (mobile phone or PHS) base station (whether or not communication is possible) is sent to the presence management server 310 as presence information. The presence management server 310 manages presence information sent from each device for each user.
  • the softphone 412 of the terminal device 410 and the softphone 432 of the mobile terminal device 430 perform VoIP communication with the SIP server 100, and other terminal devices via the SIP server 100 Connect the call line with.
  • the web browser 414 of the terminal device 410, the web browser 434 of the mobile terminal device 430, and the web browser 511 of the mobile terminal device 510 access the business management server 330 using HTTP or the like, and are provided by the web server 331. Browse the content to be played. VoIP communication with the SIP server 100 is performed, and a call line with another terminal device is connected via the SIP server 100.
  • the SIP server 100 communicates with the address translation server 200 via SOAP (Simple Object Access
  • processing linked to the address translation server 200 is performed.
  • the SIP server 100 cooperates with the address translation server 200 via the SIP3PCC controller 110 to establish a VoIP call line between the two terminal devices. Connecting.
  • the SIP server 100 and the address translation server 200 communicate with other devices using various communication protocols.
  • the SIP server 100 and the address translation server 200 operate in cooperation with other devices, and can select a terminal device and connect a call line according to the presence of the other party.
  • FIG. 5 is a diagram showing an example of the presence DB stored in the presence management server.
  • the presence DB is stored in association with the user ID for each user.
  • presence senders, items, and contents are registered in association with each other.
  • the presence sender column the type of the device that transmitted the presence information is registered.
  • Presence information items are registered in the item column.
  • the contents column the contents of presence information are registered.
  • Sens information is sent.
  • the access point 340 transmits presence information indicating whether or not the user has logged in to the ubiquitous telephone (VoIP).
  • VoIP ubiquitous telephone
  • the login processing of the mobile terminal device 430 as VoIP is performed by the mobile terminal device 430 to the access point 340 while the mobile terminal device 430 of the user 51 is within the range where radio waves reach from the access point 340. On the other hand, it is done regularly.
  • the access point 340 performs a forced logout process of the mobile terminal device 430 when the login process from the mobile terminal device 430 has not been performed for a predetermined time or longer. Then, the access point 340 transmits presence information indicating whether or not each mobile terminal apparatus has logged in to the presence management server 310 periodically (or when the state changes).
  • FIG. 6 is a block diagram showing functions of the SIP server and the address translation server.
  • the SIP server 100 includes a call reception unit 121, an address analysis unit 122, an address analysis table 123, a call destination inquiry unit 124, and an incoming call processing unit 125.
  • the call reception unit 121 receives a call request (call request specifying a user) from a terminal device used by the user. When the call reception unit 121 receives the call request, the call reception unit 121 passes the call request to the address analysis unit 122.
  • the address analysis unit 122 refers to the address analysis table 123, and determines the attribute of the designated destination (whether it is the designation of a specific terminal device or the designation of a user or user gnole).
  • the address analysis table 123 defines a range of addresses allocated to terminal devices and users.
  • the address analysis unit 122 notifies the destination inquiry unit 124 of the address.
  • the address analysis unit 122 notifies the incoming call processing unit 125 of the address.
  • the destination inquiry unit 124 When receiving an address from the address analysis unit 122, the destination inquiry unit 124 outputs an address conversion request to the address conversion server 200.
  • the address translation request includes information for designating the destination (destination designation information).
  • destination designation information When an arbitrary user is designated as the destination, for example, the name or employee number of the user becomes the destination designation information.
  • a user group is designated as a destination, information (such as the name of a department) that identifies the user group is destination designation information.
  • incoming call processing unit 125 When receiving an address from address analysis unit 122, incoming call processing unit 125 performs incoming call processing on the terminal device corresponding to the address.
  • the incoming call processing unit 125 receives the address sent from the address translation server 200 in response to the address translation request from the destination query unit 124, and performs incoming processing on the terminal device corresponding to the address. (Call processing with a specified device). Furthermore, when receiving two addresses for a two-party call from the SIP3PCC controller 110, the incoming call processor 125 performs incoming call processing on the terminal device corresponding to each address.
  • the SIP3PCC controller 110 is provided with a two-party connection processing unit 111.
  • the two-party connection processing unit 111 transmits two addresses passed from the address translation server 200 to the SIP server 100 when performing a two-party call, and controls the call between the terminal devices specified by each address. To do.
  • the address conversion server 200 includes a presence acquisition unit 211, a destination selection unit 212, a request transmission reception unit 213, and a request transmission execution unit 214.
  • the presence acquisition unit 211 acquires a user ID corresponding to identification information such as a name and employee number indicated in the address conversion request from the LD AP server 320 in response to the address conversion request of the SIP server 100. Then, the presence acquisition unit 211 acquires presence information corresponding to the acquired user ID from the presence management server 310. When the presence acquisition unit 211 receives a user ID from the request transmission reception unit 213, the presence acquisition unit 211 acquires presence information corresponding to the ID from the presence management server 310.
  • the destination selection unit 212 acquires presence information sent from the presence management server 310, and selects a terminal device as a destination. Then, the destination selection unit 212 notifies the determined address of the terminal device to the SIP server 100 or the request transmission execution unit 214.
  • the presence information acquired in response to the address translation request from the SIP server 100 indicates the current status of the call partner. Therefore, the destination selection unit 212 determines a terminal device that is a destination according to presence information in accordance with a predefined destination selection criterion. Then, the destination selection unit 212 notifies the SIP server 100 of the determined terminal device address.
  • the presentation acquired in response to a request transmission request from the presence management server 310 The service information indicates the current status of a plurality of users selected in accordance with the contents of the request. Therefore, the destination selection unit 212 determines a terminal device that is a destination according to the presence information in accordance with a predetermined destination selection criterion. Then, the destination selection unit 212 notifies the requested transmission execution unit 214 of the determined terminal device address.
  • the request transmission accepting unit 213 receives a request transmission request from the business management server 330 sent via the presence management server 310.
  • the request transmission accepting unit 213 outputs the presence acquisition requests of a plurality of users specified by the received request transmission request to the presence acquisition unit 211.
  • the request transmission execution unit 214 Upon receiving the address specifying the destination from the destination selection unit 212, the request transmission execution unit 214 transmits a connection request for a two-party call including the address to the SIP3PCC controller 110.
  • Communication between the SIP server 100 and the address conversion server 200, and communication between the SIP3PCC controller 110 and the address conversion server 200 is realized by inter-object communication using SOAP.
  • FIG. 7 shows an example of the data structure of the address analysis table.
  • the address analysis tape No. 123 defines a range of addresses allocated to terminal devices and users.
  • addresses beginning with 2-4 are addresses (unique addresses) for uniquely identifying terminal devices.
  • direct adhesion processing is performed on the terminal device corresponding to the extension.
  • Addresses beginning with 5 and addresses other than numbers designate users. That is, an address that starts with 5 and an address other than a number is an address corresponding to a gnole that consists of a set of a plurality of terminal devices (for example, a plurality of terminal devices used by one user).
  • An address starting with 0 indicates an outside line number. That is, an address starting with 0 is an address (unique address) for uniquely identifying a terminal device.
  • the outside line points to the call request If specified, outgoing calls are made.
  • destination selection criteria defined by destination selection unit 212 will be described in detail.
  • FIG. 8 is a diagram illustrating an example of destination selection criteria.
  • priority is set for the user's presence.
  • the horizontal axis shows the presence of the user and the vertical axis shows the priority.
  • the priority of the self-seat telephone is divided into a case where the user is logged in to the terminal device (personal use personal computer) and a case where the user is logged out. If you are logged out, the priority of your phone is “0”. When logged in, it is subdivided into whether it is present or away. If you are present, the priority of your phone is “10”. If you are away from your desk, the priority of your phone is “4”. The presence or absence of presence can be determined, for example, based on whether or not an operation input to the terminal device of the user's own seat has been performed for a predetermined time or more.
  • the priority of voice mail is “5”.
  • the priority of VoIP-based ubiquitous calls can be divided into the case of logging in to a mobile terminal device and the case of logging out.
  • the priority of VoIP ubiquitous calls is “7”.
  • the priority of VoIP ubiquitous calls is “0”.
  • Whether or not the user is logged in to the VoIP-based ubiquitous telephone can be determined, for example, based on whether or not the mobile terminal device 430 is within a range where radio waves from the access point 340 can reach. This presence information is transmitted to the presence management server 310 by the presence transmission function in the access point 340.
  • the priority of the ubiquitous IP phone by PHS is divided according to whether it is a weekday or a holiday. On weekdays, priorities are divided according to time zones. In the weekday from 9:00 to 18:00 (normal business hours), the priority of the ubiquitous IP phone by PHS is “6”. In other times, the priority of the PHS ubiquitous IP phone is “3”. During holidays, the priority of PHS ubiquitous IP phones is “3”.
  • the priority of the ubiquitous IP phone by PHS is corrected according to the caller who made the call. That is, if the preset priority user is the caller, The value “+3” is added first. For example, by registering a company boss or an important customer as a priority user, even if it is out of business hours on a weekday or on a holiday, calls from that user will be prioritized by PHS ubiquitous IP phones. The degree is “6”. As a result, during work hours on weekdays and on holidays, calls from supervisors and important customers are received by ubiquitous IP phones by PHS outside the company (terminal devices at their desks are logged out and ubiquitous IP phones by VoIP are logged out). be able to.
  • FIG. 9 is a diagram showing a procedure of a destination determination process in response to a call request.
  • the user 52 specifies the employee number of the user 51 as an address (5xxx) from the mobile terminal device 510. It is an example when a call request is output. Note that the user 52 is not a priority user in the destination selection criteria of FIG.
  • step Sl l When a call request is issued from mobile terminal device 510, transmission of call request is accepted by call reception unit 121 of SIP server 100 (step Sl l). Then, the call reception unit 121 sends the call request to the address analysis unit 122.
  • the address analysis unit 122 refers to the address analysis table 123 and analyzes the address specified in the call request (step S 12). In this example, the address starts with 5, so you can see that it is a user-specified address. Therefore, the address analysis unit 122 notifies the destination inquiry unit 124 of the address specified in the call request.
  • the destination inquiry unit 124 inquires of the address translation server 200 about the destination of the received address (step S13). Specifically, the destination inquiry unit 124 transmits an address conversion request including the employee number indicated in the call request to the address conversion server 200.
  • the presence acquisition unit 211 of the address conversion server 200 acquires presence information corresponding to the employee number from the presence management server 310 (step S14). At this time, the presence acquiring unit 211 acquires the user ID corresponding to the employee number in the LDAP server 320, and is registered in association with the user ID. Requests presence information to the presence management server 310.
  • Presence information sent from the presence management server 310 is acquired by the destination selection unit 212, and a terminal device as the destination is selected (step S15).
  • the user 51 is not logged in to the terminal device 410 at his / her seat, but the mobile terminal device 430 is within a range where radio waves from the access point 340 can reach. That is, VoIP login by the mobile terminal device 430 is performed to the access point 340.
  • VoIP-based ubiquitous calls are the highest at priority 6.
  • the destination selection unit 212 determines the VoIP call function of the mobile terminal device 430 as the destination, and acquires the corresponding address. Note that the address of each terminal device is managed by the address translation server 200. The destination selection unit 212 transmits the address of the selected terminal device to the SIP server 100.
  • the incoming call processor 125 of the SIP server 100 performs incoming call processing on the mobile terminal device 430 carried by the user 51 based on the address sent from the address translation server 200 (step S16). ). At this time, if the user 51 responds to a call from the mobile terminal device 430, a call line between the mobile terminal device 430 and the mobile terminal device 510 is connected, and a call between the user 51 and the user 52 becomes possible. .
  • FIG. 10 is a diagram showing a processing procedure when a telephone line is connected in response to a request from a third party.
  • the call request is received by the Web server 331 in the business management server 330 and is sent to the presence management server via the linkage unit 33. Passed to 310.
  • the presence management server 310 outputs a request transmission request specifying the users 51 and 52 to the address conversion server 200.
  • request transmission reception unit 213 receives the request transmission request (step S21).
  • the request transmission reception unit 213 Presence acquisition request of users 51 and 52 specified in the request to send
  • the presence acquisition unit 211 acquires the user IDs of the users 51 and 52 from the LDAP server 320, and acquires presence information corresponding to the user IDs from the presence management server 310 (step S22). Presence information sent from the presence management server 310 is received by the destination selection unit 212.
  • destination selection unit 212 determines a terminal device as a destination from among the terminal devices used by users 51 and 52 (step S23). The destination selection unit 212 then sends the determined destination terminal device address to the request transmission execution unit 21.
  • the request transmission execution unit 214 transmits a call line connection request between the terminal devices corresponding to the received two addresses to the SIP3PCC controller 110 (step S 24). Then, the two-party connection processing unit 111 in the SIP3PCC controller 110 performs connection processing between the terminal devices specified by the addresses (step S25). Specifically, the two-party connection processing unit 111 transmits incoming requests for two addresses to the SIP server 100.
  • the incoming call processing unit 125 of the SIP server 100 is connected to the mobile terminal device 430 used by the user 51 and the mobile terminal device 510 used by the user 52 in response to the incoming request passed to the SIP3PCC controller 110.
  • the incoming call processing is executed (step S26).
  • the user 51 and the user 52 respond to calls from the mobile terminal device 430 and the mobile terminal device 510, respectively, the call lines between the mobile terminal device 430 and the mobile terminal device 510 are connected.
  • a call between the user 51 and the user 52 becomes possible.
  • XML Extensible Markup Language
  • XSLT Extensible Stylesheet Language Transformations
  • XSLT is a predetermined transformation language for describing transformation rules for documents written in XML.
  • XSLT allows the computer to execute processing in accordance with the XSLT definition content by causing the XSLT processor to execute it.
  • FIG. 11 is a diagram showing processing when the incoming call selection criterion is described in XSLT.
  • the address conversion server 200 is provided with a JavaVM Qava (registered trademark) virtual machine 221.
  • the Java VM 211 converts a program written in the Java language into the native code of the address translation server 200 and executes it.
  • the address translation server 200 includes a linkage unit as a program that runs on the JavaVM 221.
  • XML parser 223, and XSLT processor 224 are implemented.
  • the cooperation unit 222 receives an address conversion request from the SIP server 100, outputs the address conversion request to the message transmission / reception unit 231, and transmits an address conversion result from the message transmission / reception unit 231 to the SIP server 100. Further, the cooperation unit 222 acquires the presence information 312 from the presence management server 310 in response to a request from the presence acquisition control unit 233.
  • the XML parser 223 analyzes information described in XML.
  • the XSLT processor 224 performs a terminal device selection process according to the device selection logic information 60 described in XSLT.
  • the linkage unit 222 and the XSLT processor 224 request the XML parser 223 to analyze the XML data and understand the contents of the XML data by receiving the analysis result. .
  • the address translation server 200 is provided with a message transmission / reception unit 231, a user ID search unit 232, and a presence acquisition control unit 233.
  • the message transmission / reception unit 231 is a function realized by the javaVM 221 executing a Java program.
  • the message transmission / reception unit 231 requests the user ID search unit 232 to search for a user ID in response to the address conversion request received via the linkage unit 222.
  • the message transmission / reception unit 231 passes the call information 241 included in the address translation request to the XSLT processor 224.
  • the call information 241 includes caller identification information, day of the week time, and the like.
  • the message transmitting / receiving unit 231 receives the selected device identification information 243 from the XSLT processor 224.
  • the selected device identification information 243 includes the address of the terminal device that is the destination.
  • the user ID search unit 232 acquires the user ID corresponding to the address indicated by the address conversion request from the LDAP server 320.
  • the user ID search unit 232 passes the acquired user ID to the presence acquisition control unit 233.
  • the presence acquisition control unit 233 acquires the user ID from the user ID search unit 232
  • the presence acquisition control unit 233 acquires the presence information 312 via the linkage unit 222.
  • the presence acquisition control unit 233 analyzes the contents of the acquired presence information 312 to generate a user presence 242 and passes the user presence 242 to the XSLT processor 224.
  • This user presence 242 includes information on device information (type of terminal device) and priority user information (whether it corresponds to a priority user).
  • the function of the presence acquisition unit 211 shown in FIG. 6 is realized by the message transmission / reception unit 231, the user ID search unit 232, the presence acquisition control unit 233, and the cooperation unit 222 operating on the JavaVM 221. Yes.
  • the function of the destination selection unit 212 is realized by a message transmission / reception unit 231 and an XSLT processor 224 operating on the Java VM 221.
  • the address translation request is passed to the message transmission / reception unit 231 via the linkage unit 222. Then, the message transmission / reception unit 231 issues a user ID search request to the user ID search unit 232. At the same time, call information 241 is generated by the message transmission / reception unit 231 and passed to the XSLT processor 224.
  • the user ID search unit 232 uses the LDAP server 320, Then, the user ID of the user corresponding to the address indicated by the address conversion request is acquired and passed to the presence acquisition control unit 233. Then, the presence acquisition control unit 233 acquires presence information 312 from the presence management server 310 via the cooperation unit 222. Then, the presence acquisition control unit 233 analyzes the content of the acquired presence information 312 and passes it to the XSLT processor 224 as the user presence 242.
  • the XSLT processor 224 selects a destination terminal device according to the call information 241 and the user presence 242 according to the destination selection definition indicated by the device selection logic information 60. Thereafter, the XSLT processor 224 passes the selected device identification information 243 to the message transmission / reception unit 231. The message transmitting / receiving unit 231 transmits the selected device identification information 243 as an address conversion result to the SIP server 100 via the linkage unit 222.
  • FIG. 12 is a diagram showing information passed as XML data.
  • the delivery of information by XML data is indicated by a solid line, and the delivery of other information is indicated by a dotted line.
  • an address conversion request from the SIP server 100 to the address conversion server 200 and a response to the address conversion request are made with XML data.
  • an address translation request from the SIP3PCC controller 110 to the address translation server 200 and a response to the address translation request are made with XML data.
  • Address conversion and two-way connection requests issued from the linkage unit 333 of the business management server 330 to the address conversion server 200 are performed using XML data.
  • a two-party connection request from the address translation server 200 to the SIP3PCC controller 110 is also made with XML data.
  • XML data can be sent and received using SOAP or IM (instant message).
  • FIG. 13 is a flowchart showing a processing procedure by the address translation server. In the following, the process illustrated in FIG. 13 will be described in order of step number.
  • the cooperation unit 222 receives XML data indicating an address translation request.
  • Step S32 The linkage unit 222 requests the XML parser 223 to analyze the XML data. Then, the XML parser 223 analyzes the XML data. The result of the analysis is the XML parser. 3 is passed to the linkage unit 222. The cooperation unit 222 passes the address conversion request included in the XML data to the message transmission / reception unit 231.
  • Step S33 The message transmission / reception unit 231 decodes an address translation request message. By decoding, at least the caller information and the address specified by the call are extracted. The message transmission / reception unit 231 passes the caller information to the XSLT processor 224 as call information 241. In addition, the message transmission / reception unit 231 passes the address to the user ID search unit 232.
  • Step S 34 The user ID search unit 232 issues a search request for a user ID using the address as a search key to the LDAP server 320. Then, the user ID search unit 232 acquires a user ID from the LDAP server 320 as a search result. The acquired user ID is passed to the presence acquisition control unit 233.
  • Step S 35 The presence acquisition control unit 233 outputs a presence acquisition request to the presence management server 310 via the linkage unit 222. Then, presence information 312 is returned from the presence management server 310.
  • Presence information 312 returned from the presence management server 310 is received by the linkage unit 222.
  • the cooperation unit 222 requests the XML parser 223 to analyze the received presence information 312. Then, the XML parser 223 analyzes presence information and passes the analysis result to the linkage unit 222.
  • the cooperation unit 222 passes the analyzed presence information to the presence acquisition control unit 233.
  • the presence acquisition control unit 233 generates a user presence 242 including information on a terminal device that can be used by the user from the analyzed presence information, and passes it to the XSLT processor 224.
  • the XSLT processor 224 selects one terminal device (destination candidate) that can be used by the user who should be the other party. At this time, if multiple terminal functions are implemented in one terminal device, such as a terminal device that can communicate with both VoIP and PHS via a wireless LAN, each function is treated as a different destination candidate. Is called. That is, a destination candidate is selected for each address that is the target of incoming processing.
  • the XSLT processor 224 analyzes the user presence 242 regarding the selected destination candidate. [Step S39] The XSLT processor 224 acquires the device selection logic information 60 and the current time information, and determines the priority of the destination candidate selected in step S37.
  • Step S40 The XSLT processor 224 determines whether or not the priorities have been determined for all the destination candidates. If priority determination has been completed for all destination candidates, processing power S is advanced to step S41. If there is a destination candidate whose priority has not been determined, the process proceeds to step S37.
  • Step S41 The XSLT processor 224 selects the destination candidate with the highest priority as the destination.
  • Step S42 The XSLT processor 224 generates XML data including the selected device identification information 243 specifying the destination address. Then, the XSLT processor 224 passes the generated XML data to the message transmission / reception unit 231.
  • Step S43 The message transmission / reception unit 231 transmits the XML data including the selected device identification information 243 to the SIP server 100 via the cooperation unit 222 as an address conversion result.
  • FIG. 14 is a diagram illustrating a first example of priority determination criteria.
  • Figure 14 shows the priority criterion 61 for office extension telephones (fixed telephones at their seats).
  • the ⁇ note> tag indicates the terminal device type "office extension".
  • the basic> tag indicates the priority application conditions defined in the substructure.
  • ⁇ Basic> tag is set to “open” when defining the priority at the time of login to the terminal device of the user's seat, and “c 1036” when defining the priority at the time of logout.
  • the priority is regarded as “0” (reference value).
  • the priority of the corresponding terminal device is set in the priority> tag. If a variable indicating the state is set in the ⁇ priority> tag, the priority for the corresponding state is set. In the example of Fig. 14, the variable atdesk is set to indicate whether or not you are present. The priority> tag is described. If "yes” is set in the variable atdesk, it indicates the presence status, and if "no" is set, it indicates the absence status. In the example shown in Fig. 14, the priority is “10” while being present.
  • the priority that is not set in the variable indicating the status is set to the priority that is applied when the status does not meet the conditions for other priority settings. In the example of FIG. 14, it is shown that the priority is “4” when the user is away.
  • FIG. 15 is a diagram illustrating a second example of the priority determination criterion.
  • FIG. 14 shows the priority criterion 62 of the ubiquitous telephone (V oIP). Note that ubiquitous telephone priority judgment standard 62, basic> tag is set to “open” to define the priority when the ubiquitous telephone is logged in to the wireless LAN environment, and the user is logged out. When defining the priority, “close S is set. In the example of FIG. 15, the power S is indicated to be the priority“ 7 ”when logging in.
  • FIG. 16 is a diagram illustrating a third example of the priority determination criterion.
  • FIG. 16 shows a priority criterion 63 for a ubiquitous telephone (PHS).
  • PHS ubiquitous telephone
  • the ubiquitous telephone priority judgment standard 63 tag> basic is set to “open” to define the priority when the ubiquitous telephone is within the communication range from the PHS base station. "Close” is set when defining the priority when PHS base station.
  • variable dayofweek that specifies the time zone is set to priority.
  • the tag is described.
  • the day of the week to which the priority is applied is specified by the variable dayofweek, and the time zone in which the priority is applied is specified by time.
  • the day of the week is indicated by 7-bit data. Each bit is associated with Sunday, Monday, Tuesday, Wednesday, Thursday, Friday and Saturday respectively.
  • the day of the week corresponding to the bit whose value is set to “1” is applicable.
  • the time indicates the start time and end time of the time zone to which the priority is applied.
  • the priority is set to “6” in the time zone from 8:00 to 20:00 from Monday to Friday. In other time zones, the priority is “3”.
  • the specific menu In the case of a call request from one user, the priority is added by “3”.
  • FIG. 17 is a diagram showing a fourth example of the priority determination criterion.
  • Figure 17 shows the priority criteria 64 for voicemail.
  • the priority of the voice mail is “5”.
  • the priority for each destination candidate is defined in such a data structure. According to this definition, the priority of each terminal device is determined, and the terminal device with the highest priority is the destination.
  • the priority criteria are defined with an easy-to-use component and easy-to-use structure, making it easy to change the priority. In other words, changing the program source code eliminates the need for complicated operations.
  • the address conversion server 200 does not need to acquire a user ID from the LDAP server 320.
  • the above processing functions can be realized by a computer.
  • a program that describes the processing contents of the functions that each server should have is provided.
  • the program describing the processing contents can be recorded on a computer-readable recording medium.
  • the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory.
  • Magnetic recording devices include hard disk drives (HDD), flexible disks (FD), and magnetic tapes.
  • Optical discs include DVD (Digital Versatile Disc), DVD-RAM (Random Access Memory), CD-ROM (Compact Disc Read Only Memory), CD-R (Recordable) / RW (Rewritable), and the like.
  • Magneto-optical recording media include MO (Magneto-Optical disk).
  • a computer that executes a program is, for example, a program recorded on a portable recording medium.
  • the program transferred from the program or server computer is stored in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program.
  • the computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention décrit le fait que pour être connecté au terminal qu'il appelle, le terminal de l'appelant doit émettre une requête d'appel qui va déclencher l'envoi d'une information de présence par l'intermédiaire d'une ligne de communication. Dans une première étape (S1), la requête d'appel est reçue par un dispositif de commande d’appels (3) et dans une deuxième étape (S2), une requête de conversion d'adresse est envoyée au convertisseur d'adresses (2). Dans une troisième étape (S3), le convertisseur d'adresses (2) envoie une requête d'acquisition d'information de présence au gestionnaire de présence (1) qui renvoie alors une information de présence. Dans la quatrième étape (S4), le convertisseur d'adresses (2) identifie le terminal appelé (5) en fonction de l'information de présence reçue et selon un critère de sélection prédéterminé et il transmet l'information correspondant à ce terminal (5). Dans la cinquième étape (S5), le dispositif de commande (3) appelle le terminal voulu (5).
PCT/JP2005/001237 2005-01-28 2005-01-28 Systeme et procede de gestion d'appels telephoniques Ceased WO2006080080A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2005/001237 WO2006080080A1 (fr) 2005-01-28 2005-01-28 Systeme et procede de gestion d'appels telephoniques
JP2007500392A JPWO2006080080A1 (ja) 2005-01-28 2005-01-28 電話管理システム、電話管理方法、および電話管理プログラム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2005/001237 WO2006080080A1 (fr) 2005-01-28 2005-01-28 Systeme et procede de gestion d'appels telephoniques

Publications (1)

Publication Number Publication Date
WO2006080080A1 true WO2006080080A1 (fr) 2006-08-03

Family

ID=36740115

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2005/001237 Ceased WO2006080080A1 (fr) 2005-01-28 2005-01-28 Systeme et procede de gestion d'appels telephoniques

Country Status (2)

Country Link
JP (1) JPWO2006080080A1 (fr)
WO (1) WO2006080080A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010067169A (ja) * 2008-09-12 2010-03-25 Ntt Comware Corp 通信システム及び方法とそのプログラム
JP2010533006A (ja) * 2007-03-01 2010-10-21 ソニー コンピュータ エンタテインメント アメリカ リミテッド ライアビリテイ カンパニー 仮想世界とコミュニケーションを取るためのシステムおよび方法
WO2012073416A1 (fr) * 2010-11-30 2012-06-07 日本電気株式会社 Processeur d'informations, procédé de traitement d'informations et programme de traitement d'informations
JP2014090502A (ja) * 2008-08-28 2014-05-15 Nec Corp 通信システム
JP2017157896A (ja) * 2016-02-29 2017-09-07 日本電信電話株式会社 着信先解決システム、着信先解決サーバおよび着信先解決方法
JP2022116497A (ja) * 2021-01-29 2022-08-10 Ｎｔｔテクノクロス株式会社 電話システム及び方法
JP7298953B1 (ja) 2022-03-01 2023-06-27 Ｎｅｃプラットフォームズ株式会社 駐車場管理システム及び方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003022250A (ja) * 2001-07-09 2003-01-24 Nec Corp セッション確立方法
JP2004153352A (ja) * 2002-10-29 2004-05-27 Hitachi Ltd マルチメディアコミュニケーションシステム
JP2004153317A (ja) * 2002-10-28 2004-05-27 Nippon Telegr & Teleph Corp <Ntt> 端末メディア選択方法及び発信方法及び通信メディア選択装置及び端末メディア選択システム
JP2004304666A (ja) * 2003-03-31 2004-10-28 Ntt Comware Corp 企業向けｉｐ電話通信サービス提供方法、および同方法を用いたアプリケーションサービス提供システム、ならびにそのプログラム、記録媒体
JP2004312559A (ja) * 2003-04-09 2004-11-04 Ntt Communications Kk 通信システム、呼制御装置、プレゼンス情報検出装置、着信先変更方法、着信先変更プログラム、およびプログラム記録媒体

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005236670A (ja) * 2004-02-19 2005-09-02 Nippon Telegr & Teleph Corp <Ntt> セッション確立、セッション確立処理装置及びプログラム
JP4335718B2 (ja) * 2004-03-19 2009-09-30 富士通株式会社 異種端末間データ転送方法、装置、プログラム及び記憶媒体

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003022250A (ja) * 2001-07-09 2003-01-24 Nec Corp セッション確立方法
JP2004153317A (ja) * 2002-10-28 2004-05-27 Nippon Telegr & Teleph Corp <Ntt> 端末メディア選択方法及び発信方法及び通信メディア選択装置及び端末メディア選択システム
JP2004153352A (ja) * 2002-10-29 2004-05-27 Hitachi Ltd マルチメディアコミュニケーションシステム
JP2004304666A (ja) * 2003-03-31 2004-10-28 Ntt Comware Corp 企業向けｉｐ電話通信サービス提供方法、および同方法を用いたアプリケーションサービス提供システム、ならびにそのプログラム、記録媒体
JP2004312559A (ja) * 2003-04-09 2004-11-04 Ntt Communications Kk 通信システム、呼制御装置、プレゼンス情報検出装置、着信先変更方法、着信先変更プログラム、およびプログラム記録媒体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ICHISHI T.: "Chujokyu User Gentei?! Oracle9i Tora no Ana Dai 11 Kai Application Kaihatsu (XML Database(1))", DB MAGAZINE, KABUSHIKI KAISHA SHOEISHA, vol. 13, no. 6, 1 September 2003 (2003-09-01), pages 175 - 179, XP003000469 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010533006A (ja) * 2007-03-01 2010-10-21 ソニー コンピュータ エンタテインメント アメリカ リミテッド ライアビリテイ カンパニー 仮想世界とコミュニケーションを取るためのシステムおよび方法
JP2014090502A (ja) * 2008-08-28 2014-05-15 Nec Corp 通信システム
US8929222B2 (en) 2008-08-28 2015-01-06 Lenovo Innovations Limited (Hong Kong) Communications system
JP2010067169A (ja) * 2008-09-12 2010-03-25 Ntt Comware Corp 通信システム及び方法とそのプログラム
WO2012073416A1 (fr) * 2010-11-30 2012-06-07 日本電気株式会社 Processeur d'informations, procédé de traitement d'informations et programme de traitement d'informations
JP2012119938A (ja) * 2010-11-30 2012-06-21 Nec Corp 情報処理装置、情報処理方法及び情報処理プログラム
US9319432B2 (en) 2010-11-30 2016-04-19 Nec Corporation Information processor, information processing method and non-transitory storage medium storing information processing program
JP2017157896A (ja) * 2016-02-29 2017-09-07 日本電信電話株式会社 着信先解決システム、着信先解決サーバおよび着信先解決方法
JP2022116497A (ja) * 2021-01-29 2022-08-10 Ｎｔｔテクノクロス株式会社 電話システム及び方法
JP7687829B2 (ja) 2021-01-29 2025-06-03 Ｎｔｔテクノクロス株式会社 システム及び方法
JP7298953B1 (ja) 2022-03-01 2023-06-27 Ｎｅｃプラットフォームズ株式会社 駐車場管理システム及び方法
JP2023127442A (ja) * 2022-03-01 2023-09-13 Ｎｅｃプラットフォームズ株式会社 駐車場管理システム及び方法

Also Published As

Publication number Publication date
JPWO2006080080A1 (ja) 2008-06-19

Similar Documents

Publication Publication Date Title
US10498863B2 (en) Providing access to information of multiple types via coordination of distinct information services
JP4607493B2 (ja) 拡張テレフォニーコンピュータユーザインタフェース
US7792253B2 (en) Communications involving devices having different communication modes
JP4548242B2 (ja) 音声ｉｐ電話方法と装置。
US8451991B2 (en) System and apparatus for managing calls
JP4944415B2 (ja) コミュニケーションシステム、プレゼンスサーバ及びそれらに用いるコミュニケーション方法
WO2006080080A1 (fr) Systeme et procede de gestion d&#39;appels telephoniques
CN101577767A (zh) 用于电信服务的实时语音至文本转换
EP3531677B1 (fr) Registre de dispositifs pour médier des sessions de communication
JP2007306515A (ja) 電話接続プログラム、電話接続方法および電話接続装置
JP3993024B2 (ja) Ｗｅｂ連携ボイスメールシステムおよびそのボイスメール聞取り方法
JP2010245676A (ja) 配車情報管理システム
JP2002171350A (ja) 通話録音システム
JP4283184B2 (ja) 折返し先管理装置、折返し先設定方法、及び、折返し先発信方法
HK1183188B (en) Methods for facilitating, managing and controlling incoming and outgoing calls from a telephone

Legal Events

Date Code Title Description
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: 2007500392

Country of ref document: JP

122 Ep: pct application non-entry in european phase

Ref document number: 05709463

Country of ref document: EP

Kind code of ref document: A1

WWW Wipo information: withdrawn in national office

Ref document number: 5709463

Country of ref document: EP