KR20070096464A - Conference recording system and method using wireless voip terminal - Google Patents

Abstract

A system and method for recording a conference by using a terminal for a wireless voice packet network are provided to store a speaker, a talk start time, a talk end time, voice data, master comment, auxiliary conference data, etc., as synchronizing them with a proceeding conference by utilizing the XML. Mobile VoIP(Voice over Internet Protocol) terminals of each speaker are registered(100). When a master console initiates conference sessions(200), a registered terminal selects one of the initiated conference sessions and registers at the selected session to participate in the conference(300). Voice data transmitted from the registered VoIP terminal of the speaker participating in the conference is stored in a data storage unit by a recording control server(400). When different auxiliary data besides the voice data of the speaker should be recorded(500), the data is recorded in the data storage unit through the recording control server by using the master console(600).

Description

Conference recording system and method using wireless voice packet network terminal {Conference recording system and method using wireless VoIP terminal}

1 is a schematic diagram showing the concept of a conventional conference audio recording method.

2 is a main flowchart of a conference recording method according to the present invention;

3 to 7 is a block diagram of a conference recording apparatus according to the present invention.

FIG. 8 is a detailed processing flowchart of 100 steps of FIG. 2; FIG.

9 is a user interface example of the master console

FIG. 10 is a detailed process flow chart of step 200 of FIG.

FIG. 11 is a detailed process flow chart of 300 steps of FIG.

12 is a schematic diagram showing the concept of a conference voice recording method according to the present invention;

Fig. 13 is a conceptual configuration diagram of a wireless VoIP terminal used in the present invention.

14 is a detailed processing flowchart of 600 steps of FIG.

FIG. 15 is a conceptual diagram of a storage data structure in step 600 of FIG.

<Description of Major Drawing Numbers>

10A, B, C: wireless VoIP terminal, 20: wireless access point, 30: SIP server, 40: recording control server, 50: data storage, 60: master console, 55: conference related parameter, 57: recording related parameter, 81 : Start time of speaking, 82: End time of speaking

The present invention provides a system and method for recording voice data and auxiliary data during a voice conference or a voice call, using a wireless voice packet network (VoIP) terminal and SIP and XML technology, and a wireless VoIP terminal and a recording control device used therein. It is about.

A multi-party voice call / voice conference system, which is a system for multi-party meetings without attending a certain place, is being used by many companies and organizations. The recording method in the voice call / voice conference system stores the entire voice data (eg, voice binary data) from the beginning to the end of the conference as a whole.

That is, as shown in FIG. 1, even when the speakers A, B, and C talk to each other at a time interval, in the voice recording data, the voice data of each speaker is simply mixed and continuously stored in one voice channel.

When such a recording is made, it is only possible to presumably review who, what subject, what opinions, etc., will be presumed in the future during recording review or recording. Moreover, it would be more difficult for a person who did not attend the meeting to listen to the recorded data later and to write a complete transcript. In addition, it is impossible to partially search or extract only a necessary portion (for example, the contents of a specific speaker) from the recorded voice data by the computer.

In addition, when referring to video or other auxiliary materials during a meeting, it is essential to link recorded audio data with these conference auxiliary materials. However, since only voice is recorded, a single file of voice recording data and other auxiliary materials is used. Linkage is impossible.

Accordingly, the present inventors record and speak not only the contents of each speaker's remarks when recording a voice call or a voice conference, but also a recording method and device for later review, search, and partial extraction by recording three-dimensionally and effectively. To provide a study to complete the present invention.

Accordingly, an object of the present invention is to use a wireless VoIP terminal as a personal microphone, and when each speaker speaks, a conference recording system for synchronizing voice data for each speaker with the speaker ID, the speaking start time, and the speaking ending time and storing them in the data storage. And a method.

Another object of the present invention, by using the XML to synchronize the speaker, speech start time, speech end time, voice data, master comments, auxiliary conference data (for example, documents, slides, video material, etc.) It is to provide a conference recording system and method that can be stored in three-dimensional connection.

Another object of the present invention, when the speaker operates the terminal at the time of speaking, the data including the speaker ID, the start time of the talk, the voice data spoken by the speaker, the end time of speaking, and synchronized with the talk time for each speaker, the voice data To provide a VoIP terminal that can record.

It is another object of the present invention to provide a recording control apparatus which is included in the conference recording system and performs recording control to store voice data from an VoIP terminal and auxiliary data from outside in a data storage.

<Overview of invention>

When explaining the operation of the present invention as follows.

(1) For each speaker, the speaker ID for the SIP (session initiation protocol) address of the wireless VoIP terminal is registered in the recording control server.

(2) When the speaker speaks using the VoIP terminal as a microphone when speaking, the VoIP terminal outputs data including the speaker ID, speaking start time, voice data, and speaking end time.

(3) The recording control server receives the data and stores the data in the data storage, but stores the voice data in XML format by synchronizing according to the speaking time for each speaker ID.

(4) Separate auxiliary data (conference data such as photos, slides, documents, etc.) are stored in the data store through the user interface in the record control page using the master console, but synchronized to the voice data by speaker ID and speaking time. Save in XML form.

According to the present invention, each speaker speaks by utilizing a wireless VoIP terminal as a personal microphone. Each speaker must pre-register a wireless VoIP terminal provided for each person in the recording system of the present invention, and when a conference participant who speaks in a specific conference speaks by pressing a specific button of the terminal. When the voice data spoken by this participant is transmitted from the terminal by the operation of this button, it is transmitted to the recording system by classifying the voice data communication channel for each speaker using SIP, which is a connection establishment protocol.

The voice data transmitted from the terminal is stored in the recording system using XML. Unlike the existing method of storing voice data or image data, the voice, speech start time, speech end time, voice data, master comment, Auxiliary meeting materials (eg documents, slides, video footage, etc.) can be stored in three dimensions.

As described above, the present invention can store the contents of a teleconference, a meeting, a conference, a seminar, a lecture, and the like, and can be easily utilized for later review, search, and partial extraction. In other words, the present invention utilizes a wireless VoIP terminal and a back-end system to review the results of multilateral interactive actions such as conference and seminar contents by the purpose of auditing or reviewing by others. When you do this, help them to understand the situation and the contents.

In addition, since the client program related to the recording system can be installed in a PC, a mobile phone, or other VoIP phones, the same effect can be obtained. Implementing the function of a wireless VoIP terminal in the form of a personal microphone as a client function of a PC, a mobile phone, or other VoIP phones can achieve the same effect and be more widely used.

Composition and Action of the Invention

The configuration of the present invention will be described in detail with reference to FIGS. 2 and 3. FIG. 2 is a flowchart showing the configuration of the present invention in a method aspect, and FIG. 3 is a block diagram showing a system for implementing the processing flow of FIG. First, the configuration of the system of the present invention shown in FIG. 3 will be briefly described.

Wireless VoIP terminals 10A, B, and C are respectively assigned to a plurality of speakers, and voice data transmitted from these wireless VoIP terminals are received at a wireless access point 20 and transmitted to a recording control server 40. The data is recorded in the data storage 50 under the control of the recording control server. The VoIp terminal should register and register the ID of each speaker with respect to the SIP address of the terminal. The configuration and registration of the wireless VoIP terminal used in the present invention will be described later with reference to the method of the present invention.

The SIP server 30 divides the voice data communication channel for each speaker according to the SIP addresses of the VoIP terminals 10A, B, and C, and delivers them to the recording control server 40, and the recording control server 40 stores the data storage 50. ) To save the voice data. The SIP server 30 is a server that performs a session initiation protocol, which is a very simple text-based application layer control protocol that allows one or more participants to create, modify, and terminate a session together. These sessions include teleconferences over the Internet, telephone calls, visits, event notifications, instant messaging, and the like. SIP is based on a client / server architecture where clients initiate a call and the server responds to the call.

In order to implement the present invention, the SIP server 30 includes the components shown in FIG. In FIG. 4, the terminal authentication unit 31 receives a registration message transmitted from the VoIP terminal 10 to register the terminal and authenticates the corresponding VoIP terminal. The meeting list request receiving unit 32 requests the list of meeting information from the recording control server 40 by using the terminal registered with the speaker (multiple meetings can be established by the master console). Is received once (received messages are routed to the record control server). The message routing unit 33 routes the message authenticated by the terminal authentication unit 31 and the meeting list request message received from the terminal to the recording control server 40. The speaker-specific voice data channel 34 is a media channel for voice data transmission between the terminal 10 and the recording control server 40 separately for each speaker.

The recording control server 40 accesses the data storage 50 under the command of the master console 60 using the information received through the SIP server 30 to store or read the information. The recording control server 40 includes the components shown in FIG. The speaker ID mapping unit 41 performs a speaker ID mapping on the SIP address of the wireless VoIP terminal requesting registration to complete speaker registration for the terminal. The data storage controller 42 controls the data storage 50 to store and read voice data and auxiliary data. The meeting list request processing unit 43 receives a meeting list request message transmitted from a speaker using a terminal registered to the speaker from the SIP server 30, accesses and records the data storage through the data storage control unit 42. It takes the conference list from the control page and sends it to the terminal. The new meeting information assignment and ID grant unit 44 receives the meeting establishment request signal from the web browser of the master console 60 and accesses the record control page of the data store 50 through the data store control unit 42. It assigns information about the new conference to it, assigns it a conference ID, and stores it in the record control page of the data store 50. When the voice data transmission channel establishment unit 45 selects a conference ID from the terminal 10 and requests to participate in the conference, the media for voice data transmission between the terminal 10 and the recording control server 40 is divided by speaker. Open a channel. The XML storage processor 46 receives conference auxiliary data such as texts, images, documents, and the like other than voice data transmitted from the master console 60 and synchronizes the data to the data storage 50 in the form of XML. Three-dimensional meeting data storage using XML will be described later.

As in Figure 3, the apparatus of the present invention is controlled by the master console 60. The master console 60 is implemented as a device such as a PC or laptop connected to the network, and opens and closes the meeting by the meeting session establishment unit 61, and connects to the meeting established through the connection unit 62, and assists. The data transmission unit 63 allows the recording control server 40 to store the auxiliary conference data in various formats such as audio data, text, document, slide, and video in the data storage 50. The configuration of the master console 60 is shown in FIG. The detailed operation of each component will be made together while describing the method of the present invention.

As shown in Fig. 7, the data storage 50 of Fig. 2 stores and records the voice data transmitted from the terminal during the conference, as well as a recording control page for controlling the apparatus of the present invention. In FIG. 7, the data storage 50 includes a voice data storage 51, an XML file storage 52, and a recording control page storage 53. As shown in FIG.

In the above, the configuration and brief operation of the conference recording system according to the present invention has been described. Each of the above components may be physically distinct components, but it is apparent to those skilled in the art that the physical boundaries may be functional components that are not obvious. Specific operations and interrelationships of the above components will be apparent through the description of the conference recording method of the present invention described below.

First, the conference recording method of the present invention will be described in detail with reference to FIGS. 2 and 8 to 15.

Referring to Fig. 2, in the present invention, first, the wireless VoIP terminals 10A, 10B, and 10C of each speaker must be registered [100]. This is a procedure of registering the speaker ID for the session initiation protocol (SIP) address of the terminal with the recording control server 40. The registration procedure of the terminal is as shown in FIG. First, a registration message is created in a VoIP terminal [110]. In the present invention, the VoIP terminal can use the existing terminal as it is. Existing VoIP terminals have a setting menu for entering a SIP server, a UserID, a password, etc. and already stores a display name to be displayed externally. Before joining a conference using a wireless VoIP terminal, speaker registration must be done in advance. There are two modes of registration. That is, it is a mode of temporarily registering by pressing the Ad-hoc button and registering using SIP authentication information (UserID and Display name) predefined in the terminal. The former Ad-hoc registration mode and the latter registration mode can be achieved by selecting a specific key of the terminal. For example, these registration modes can be selected using the "* 01" and "* 02" keys of the terminal. An example of the message created in the terminal may be in the following format.

When the registration message is created in the terminal 10 [110], the message is transmitted to the SIP server 30 to perform terminal authentication, and when authenticated, the registration message is routed to the recording control server [120]. The recording control server 40 ends mapping of the speaker by storing mapping data in which speaker IDs are mapped to SIP addresses of wireless VoIP terminals [130]. As a result, the system recognizes the terminal as a specific speaker (ie, Hong Gil-dong).

Returning to FIG. 2 again, in the state where the terminal is registered, when the master console 60 opens a meeting session [200], the registered terminal (that is, the registered speaker) selects one of the opened meeting sessions and selects this meeting. Register to participate in [300]. Functions such as opening and closing the meeting session are made by the master console 60. The meeting master (or system operator, etc.) can access and operate the record control page using a web browser (Internet Explorer, etc.) from a regular PC. The record control page is stored in the data storage 50, and may be implemented in a web page format including a function of opening and closing a meeting and a function of storing a selected meeting as content. Fig. 9 illustrates the user interface of the recording control page. There are menus "New Meeting (New Meeting)" and "Existing Meeting" in the menu, so that you can open a new meeting or query an existing meeting. Fig. 9 shows a page when a new meeting is to be opened in the “New Meeting (New Meeting)” menu. The meeting related parameters 55 including the meeting name, the meeting type, the maximum number of participants, the storage mode and the VAD are shown in FIG. (record activity parameter 57) indicating whether or not voice activity detection is performed. Of course, the exemplary view of Fig. 9 shows an example of various implementations of the recording control page, and it is apparent that a person skilled in the art can arbitrarily modify the design in actual implementation.

Next, the master console 60 will be described in detail the process of opening a conference. Referring to FIG. 10, the recording control page stored in the recording control page storage unit 53 of the data storage 50 is accessed through the recording control server 40 from the web browser of the master console 60. [210]. In the recording control page displayed as shown in FIG. 9, a meeting establishment request is made, and information about the meeting is input [220]. Then, the recording control server 40 allocates the information about the new meeting, assigns the meeting ID, and stores the information in the recording control page storage unit 53 of the data storage 50 [2301].

Returning to Fig. 2, the speaker who has registered the VoIP terminal registers to participate in one of the conferences established on the record control page [300]. This is specifically illustrated in FIG. 11. In Fig. 11, the speaker presses a specific code (e.g., " * 03 ") to request a list of conference information from the recording control server 40 [310]. This request message is once sent to the SIP server 30 and then routed to the recording control server 40 [320]. When the record control server 40 transmits the list of conference information established in the record control page of the data storage 50 to the terminal [330], the terminal 10 selects a desired conference ID from the list of conference information and requests to join the conference. [340]. Accordingly, the recording control server 40 establishes a media channel for voice transmission for the conference session of the ID between the terminal 10 and the recording control server 40.

When the media channel is established between the recording control server 40 and the terminal 10 as described above, the voice data transmitted from the VoIP terminal registered to the speaker who participated in the conference is now stored in the data storage 50 by the recording control server 40. ) 400 (FIG. 2). At this time, as mentioned above, in the present invention, unlike the conventional conference recording, the statement of a specific speaker is recorded for each time zone. That is, the VoIP terminal 10 is registered for each speaker ID, and when the speaker speaks, the VoIP terminal 10 is operated so that the data related to the speaking start time and the speaking ending time are recorded together with the voice data by controlling the VoIP terminal registered with the speaker. This is possible because it is sent to 40). Therefore, the voice data for each speaker is stored in the data storage 50 together with the separate time information.

This will be described in detail. Referring to Fig. 12, the speaker activates a specific button of the registered VoIP terminal 10 at the start of speaking in the meeting 81, and turns off the button when speaking is finished. Therefore, the talk start time and talk end time and voice data, and the talker's ID can be transmitted from the terminal to the recording control server as data.

As a specific button to be activated in the wireless VoIP terminal 10 at the time of speaking, a "push-to-talk (PTT)" button or a "MUTE" button may be used. The speaker's method of speech can be divided into two categories as follows. 1) Speaker designation mode: Only those who have the right to speak have the opportunity to speak, and when the participant who has the right to speak gives the right to speak, the other participant who has the right to speak again has the next voice. At this time, the PTT button is used as a hot key when obtaining the right to speak and when the right to speak is given (for example, in FIG. 13, the "*" key is set as a hot key of the PTT button). 2) Free speech: In a conference set up so that everyone in the conference can speak freely, all voices of the wireless VoIP terminal are delivered freely. At this time, instead of the role of the PTT button, a hot key capable of acting as a MUTE for a while may be used (for example, in FIG. 13, the "#" key is set as a hot key of the MUTE button).

The PTT button or the MUTE button can be set as a hot key in the existing wireless VoIP terminal (see Fig. 13). Of course, it can be designed by installing a separate button outside the terminal, such as a radio PTT button.

FIG. 13 illustrates an example in which a PTT button / MUTE button is set as a hot key in an existing wireless VoIP terminal, and shows that *, #, etc. are set and used as hot keys while using the hardware of the existing wireless VoIP terminal as it is. In Fig. 13, the display of the right to speak is shown on the screen of the terminal, and it can be seen that the current state of the microphone is shown. For reference, the state of the right to speak is expressed as Free (free meeting), Idle (no one has the right to speak), Taken (anybody has the right to speak), Own (they have the right to speak), and the state of the microphone Is displayed as Active and Mute.

2, if it is necessary to record other auxiliary materials (conference aids such as text, photos, videos, etc.) in addition to the speaker's voice data [500], the master console 60 records these data. It should be recorded in the data storage 50 through the server 40 [600]. 14, the master console 60 accesses the opened recording control page using the conference ID [610]. Access to the meeting data (hereinafter referred to as "conference aids") other than voice data, such as text, image, related documents, and transmits to the recording control server at a time point for the meeting progress [620]. The record control server receives the corresponding data and data and stores the data in synchronization with the data storage 50 in the form of XML. According to the three-dimensional meeting data storage using XML, the XML and XML link information according to the "time", "meeting session", "speaker information" to the data transmitted in various forms such as voice, image, text, document, etc. To save in three dimensions.

As shown in Fig. 15, the following three kinds of XML schemas 1, 2, 3 and content 4 exist to record the contents of a conference in three dimensions.

(1) ConferenceInfo Schema-XML containing information about a meeting (meeting name, meeting start time, etc.) (meeting information XML of FIG. 15)

(2) ConferenceMembers Schema-XML containing information about conference participants who participated in one conference (conference participants terminal information, etc.)

(3) ConferenceScript Schema-XML containing scripts in chronological order about what happens in a meeting (Script.XML in Figure 15).

(4) Conference Contents-Contents in their own format that contain actual information (voice information) and auxiliary data information (conference aids such as photos, videos, slides, etc.) that occur at the conference. For example, abc_123.wav (saves audio information in Wav format), abc_121.pca (saves audio information in PCM / a), abc_ppt.ppt (powerpoint file uploaded to conference aid), abc_file. doc (Word file uploaded as a meeting aid), abc_file.mpg (video supplementary material viewed during the meeting), abc_file.jpg (image material viewed together during the meeting). Each of the materials in FIG. 15 has a 1-1-1 relationship with each other, and there may be several conference contents.

Each schema will be described in more detail. ConferenceInfo Schema stores information about conference information. The conference information is stored in the master console by accessing the related information generated by "Open new conference". Most are defined at the start of the meeting, and only </ end_time> is updated again at the end of the meeting. The following is an example program for this.

<conference_info>

   <conference_id> 91ABC123BCDDEE </ conference_id>

   <name> Q2 Earnings Meeting </ name>

   <comment> Meeting on Q2 2006 earnings analysis </ comment>

   <type> free_conference </ type>

   <max_participants> unlimited </ max_participants>

   <record_options>

         <record_codec> G.711 </ record_codec>

         <vad_mode> active </ vad_mode>

    </ record_options>

    <open_by> Jae Ho Yang </ open_by>

    <start_time> 2006-01-03 11:12:00 </ start_time>

</ conference_info>

Describe the ConferenceMembers Schema. When participants access the established conference, they are mapped with the speaker's registered information and stored according to the conferenceMembers schema. The program example below is based on the following assumptions: "Three participants have participated so far in the conference_id 91ABC123BCDDEE created earlier. The ID or UA_TYPE for each participant can also be defined for XML Schema."

<conference_members>

   <conference_id> 91ABC123BCDDEE </ conference_id>

   <members>

       <member id = SN11181 ua = standard> Jae Ho Yang </ member>

       <member id = SN10121 ua = ptt_mic> Choi Bo Young </ member>

       <member id = SN12011 ua = pc_soft> Kim Ji Hwan </ member>

   </ members>

</ conference_members>

ConferenceScript Schema is a Schema that has a table of contents of actual three-dimensional meeting contents. It has relative time information in accordance with the meeting time. The following is an example program.

<conference_script>

   <conference_id> 91ABC123BCDDEE </ conference_id>

<contents>

       <content source = SN11181 start = 00: 12: 00 end = 00: 12: 30

         offset1 = 0x0123 offset2 = 0x12FF type = audio format = wav>

                 sn11181_91EE_00.wav

      </ content>

      <content source = SN10121 start = 00: 13: 00 end = 00: 15: 02

        offset1 = 0x0011 offset2 = 0xE0FF type = audio format = wav>

                sn10121_91EE_02.wav

 </ content>

      <content source = SN10131 start = 00: 13: 00 end = 00: 20: 00

        type = video format = mpg> sn10131_91EE_03 (Company promotional video) .mpg

      </ content>

</ contents>

</ conference_script>

In the program example above, the above bold text indicates that "SN11181's remarks for 30 seconds at 00:12:00 are stored in WAV format at address 0x123 at address 0x123FF in the WAV format." And the bolded portion below means that "SN10131 links the content information about the video file reported during the meeting with the actual information of the video".

As described above, the method according to the present invention can be embodied as computer readable codes on a computer readable recording medium. The computer-readable recording medium includes all kinds of recording devices in which data that can be read by a computer system is stored. Examples of the recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and also include a carrier wave (for example, transmission through the Internet). The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

As described above, although the present invention has been described by way of limited embodiments and drawings, the present invention is not limited to the above-described embodiments, which can be variously modified and modified by those skilled in the art to which the present invention pertains. Modifications are possible. Therefore, the spirit of the present invention should be grasped by the claims described below, and all equivalent or equivalent modifications will belong to the scope of the present invention.

(1) Accurate speaker mapping in recorded contents

In the case of recording the entire voice conference of several people, it is not possible to know exactly who spoke by voice alone, and it is not possible to accurately extract only the contents of a specific speaker, but in the present invention, speaker mapping may be accurately performed in the recorded contents.

(2) Three-dimensional linkage of all auxiliary conference materials other than audio and video is possible.

When talking while looking at a specific slide screen or talking while looking at distributed reports, these auxiliary meeting materials can also be stored in three dimensions for increased usability. Therefore, it is possible to search for the contents of meetings through keywords, to simultaneously view the contents of meetings, and to simultaneously view the auxiliary meeting data synchronized with voice, as well as to rehearse or review details as needed, rather than simple text-based meeting results documents. Can only be searched and viewed.

Wherever a wireless LAN is available, teleconference is possible regardless of location, and one-click conference recording and enterprise-wide conference recording system can be easily implemented for these conferences.

Claims (19)

A conference recording system for controlling a data storage to receive and store voice data output from a wireless VoIP terminal that is registered for each speaker in a voice conference where a plurality of speakers speak and that is output from the speaker. The wireless VoIP terminal includes a terminal operating means for activating or deactivating the terminal by a corresponding speaker, and outputs data including a speaker ID, a speech start time, voice data spoken by the speaker, and speech end time. , The conference recording system includes a speaker ID mapping unit that performs speaker ID mapping on a SIP address of a wireless VoIP terminal registered with a speaker, and receives data output from the wireless VoIP terminal and synchronizes the speaker ID according to the talk time. And a recording control server including a data storage control unit for controlling the data storage to store the voice data in the data storage. The means for operating a wireless VoIP terminal according to claim 1, wherein A conference recording system using a wireless VoIP terminal, characterized in that the speaker presses the PTT button at the beginning of speech and at the end of speech. The means for operating a wireless VoIP terminal according to claim 1, wherein A conference recording system using a wireless VoIP terminal, characterized in that the MUTE button to stop the operation of the terminal when the speaker does not speak. The conference recording system of claim 1, wherein the conference recording system includes: And a SIP server having a speaker-specific voice data channel for transmitting voice data by distinguishing each speaker ID between the wireless VoIP terminal and the recording control server. The method of claim 1, wherein the conference recording system A conference session establishment unit for transmitting a conference establishment request signal to a record control server in order to establish a new conference on a record control page stored in a data storage; A connection section of the establishment meeting which can access the newly established meeting session; A conference using a wireless VoIP terminal further includes a master console including an auxiliary data transmission unit for storing various types of auxiliary conference data such as texts, documents, slides, and images other than voice data in a data storage through a record control page. Recording system. 6. The recording control server according to claim 5, wherein the recording control server Using the wireless VoIP terminal including an XML storage processing unit for receiving the instructions of the auxiliary data transmission unit of the master console to store the auxiliary conference data in the data storage in XML form, and to synchronize the speaker ID and voice data at the time of recording. Conference recording system. 5. The recording control server according to claim 4, wherein the recording control server Receives a request for opening a meeting from the master console and accesses the recording control page of the data storage through the data storage control unit. The new meeting information allocation and ID unit allocates information about the new meeting and assigns and stores a meeting ID thereto. Whether or not, A conference list request receiver for receiving a conference information list request message received from a VoIP terminal; Upon receiving the meeting information list request message, the conference recording system further includes a meeting list request processing unit which accesses the data storage through the data storage control unit, takes a meeting list from the record control page, and transmits the list to the terminal. . A wireless VoIP terminal that is registered for each speaker in a voice conference where a plurality of speakers speak and receives and transmits the speaker's speech. The wireless VoIP terminal has a built-in SIP address is registered to be mapped to the ID of the speaker, and includes a terminal operating means for operating or deactivating the terminal by the operation of the speaker, A wireless VoIP terminal for a conference recording system, characterized by outputting data including a speaker ID, a talk start time, a voice data spoken by a talker, and a talk end time. 9. The wireless VoIP terminal for a conference recording system according to claim 8, wherein said wireless VoIP terminal operating means is a PTT button which the speaker presses at the beginning of speech and at the end of speech. The wireless VoIP terminal for a conference recording system according to claim 8, wherein said wireless VoIP terminal operating means is a MUTE button for stopping operation of the terminal when the speaker does not speak. A wireless VoIP terminal that is registered for each speaker in a voice conference in which a plurality of speakers speak and receives the contents of the speaker, and a device that controls the data storage to receive and store voice data output from the wireless VoIP terminal in a data storage. , A speaker ID mapping unit that performs speaker ID mapping on the SIP address of the wireless VoIP terminal registered to the speaker; And a data storage control unit for receiving the data output from the wireless VoIP terminal and synchronizing according to the speaking time for each speaker ID to store the voice data in the data storage. The method of claim 11, Receives a request to open a meeting from the outside and accesses the recording control page of the data storage through the data storage control section. , A conference list request receiver for receiving a conference information list request message received from a VoIP terminal; And a meeting list request processing unit for receiving the meeting information list request message, accessing the data storage through the data storage control unit, and obtaining a meeting list from the recording control page and transmitting the meeting list to the terminal. The method of claim 11, An auxiliary storage data other than the voice data stored in the data storage through the data storage control unit is stored in the data storage in the form of XML, but further includes an XML storage processing unit for storing in synchronization with the speaker ID and recording time of the voice data. Conference recording control device. A conference recording method for receiving voice data output from a wireless VoIP terminal that is registered for each speaker in a voice conference where a plurality of speakers speak and receives the speaker's remarks and stores them in a data storage. Registering the terminal by mapping the speaker ID to the SIP address of the wireless VoIP terminal registered to each speaker; And storing the data transmitted from the VoIP terminal registered to the speaker in a data storage, and storing the voice contents according to the speaker IDs for each speaking time. The method of claim 14, wherein registering the terminal comprises: Creating a registration message in the VoIP terminal, When the registration message is created in the terminal, performing terminal authentication with this message, and if authentication is performed, storing the mapping data in which the speaker ID is mapped to the SIP address of the wireless VoIP terminal and completing the speaker registration. Conference recording method using a wireless VoIP terminal. 15. The method of claim 14, wherein the data transmitted from the VoIP terminal is A conference recording method using a wireless VoIP terminal, comprising a registered speaker's talk start time and talk end time, voice data, and speaker's ID. 15. The method of claim 14, further comprising storing ancillary materials (conference aids such as text, photos, videos, etc.) in addition to the speaker's voice data in a data storage, but storing them in XML format in synchronization with the speaker ID and recording time of the voice data. Also included, the conference recording method using a wireless VoIP terminal. The method of claim 14, Transmitting a request to open a meeting to the recording control server in order to open a new meeting on the record control page stored in the data storage; Accessing the newly established conference session by the step; And storing the auxiliary meeting data in various forms such as text, document, slide, video, etc. in addition to voice data in a data storage through a recording control page. A computer recording medium storing the conference recording method according to any one of claims 14 to 18.

Images