JP4187582B2 - Karaoke request system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a karaoke request system, and more particularly, to a karaoke request system that provides a request history indicating member information of a member who has used karaoke and music information requested by the member in response to a request from a portable terminal.
[0002]
[Prior art]
In recent years, karaoke has been actively used to request a favorite song and enjoy singing while watching the lyrics displayed on the TV screen. Such a karaoke system includes a karaoke device that outputs audio, video, and lyrics of a song requested on a TV screen, and a karaoke management server that provides song data to the karaoke device. Specifically, the karaoke apparatus receives a predetermined music ID by a user's remote control operation, and transmits the received music ID to the karaoke management server. The karaoke management server provides music data to the karaoke device based on the music ID, outputs the music data by the karaoke device, and allows the user to sing the music outputted using the microphone.
[0003]
The karaoke management server manages a large amount of music data among commonly known music in order to provide music requested by the karaoke apparatus without omission. The karaoke device communicates with a karaoke management server that manages music data, and provides music requested by the user and the latest hit chart music.
[0004]
[Problems to be solved by the invention]
However, in the conventional karaoke system, when karaoke is used, karaoke is often used repeatedly with the same member among a plurality of members, and the same tune as previously sung by the user or other members is not sung. Therefore, there is a problem that there is no way other than relying on the user's memory to know what song was requested and sung and the member at that time. In addition, many karaoke users have a mobile terminal such as a mobile phone, and the mobile terminal stores address information such as the telephone number, name, and e-mail address of members who go to karaoke together. There are many cases.
[0005]
Accordingly, an object of the present invention is to provide a karaoke request system that provides a request history to a user in response to a request from the user's mobile terminal and can recognize a song requested by a member who has previously used karaoke. It is to be.
[0006]
[Means for Solving the Problems]
In order to solve the above problems, the present invention is a member using karaoke as described in claim 1. Address information to identify And a karaoke request system that provides a request history indicating the sung music information requested by a member, from a mobile terminal , Input using the address information stored in the mobile terminal Request receiving means for receiving the request history request, and a request transmission for adding an identification number for identifying a karaoke device to the request history request and transmitting the request history request to a karaoke management server that manages the request history And a request history providing means for receiving the request history from the karaoke management server and providing the request history to the portable terminal.
[0007]
In such a karaoke request system, a request history request is received from a portable terminal, an identification number for identifying a karaoke device is added to the request history request, and the request history request is transmitted to a karaoke management server that manages the request history. By receiving the request history from the karaoke management server, providing the request history to the mobile terminal and displaying it on the mobile terminal, the user recognizes the music previously requested by each member who used karaoke, You can avoid singing songs and songs sung by other members and request them at karaoke. The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[0008]
From the viewpoint of managing request history by using address information stored in a mobile phone, that is, address information for identifying a member, the present invention provides the request history as described in claim 2. It is good also as a structure which has the music information already sung for every address information to identify.
[0009]
In such a karaoke request system, the request history includes song information that has already been sung for each address information that identifies the member, thereby managing the request history requested for management using the member address information stored in the mobile phone. can do.
[0010]
Moreover, in order to solve said subject, this invention is a member using karaoke as described in Claim 3. Address information to identify And a karaoke request system that provides a request history indicating the sung music information requested by the member, and the mobile terminal searches for address information for identifying the member using the karaoke, Entered using the address information, A request means for requesting management of a request history of a member who uses the karaoke and browsing of the request history, and the karaoke apparatus receives the request from the request means of the portable terminal. , Entered using the address information Request receiving means for receiving the request history management request; and request transmitting means for adding an identification number for identifying a karaoke device to the management request and transmitting the management request to a karaoke management server for managing the music information. And the karaoke management server is based on the management request received from the karaoke device, The address information, A request history including music information indicating a song name and a singer name is generated, and the request history providing server has a transfer means for transferring the request history to a request history providing server, and the request history providing server receives the request received from the karaoke management server Request history management means for managing the history and request history providing means for providing the request history to the mobile terminal in response to a request from the request means of the mobile terminal.
[0011]
In such a karaoke request system, the mobile terminal searches for address information for identifying a member who uses karaoke, requests management of request history of the member who uses karaoke, and browses the request history. A request history management request is received from the request means of the portable terminal, an identification number for identifying the karaoke device is added to the management request, and the management request is transmitted to the karaoke management server that manages the music information. Based on the management request received from the device, a request history including the song information indicating the song name and singer name is generated, the request history is transferred to the request history providing server, and the request history providing server receives the request received from the karaoke management server. Manage history and request on request from mobile device By providing a history, users can recognize songs previously requested by each member who used karaoke, and can request karaoke while avoiding previously sung songs and songs sung by other members. . The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0013]
FIG. 1 is a configuration diagram of a karaoke request system according to a first embodiment of the present invention. In FIG. 1, a karaoke request system 10 is installed in a karaoke store, and a karaoke apparatus 20 that outputs a request history based on a request history request transmitted from a mobile phone 3 of a user, and a request from a user. It comprises a karaoke management server 40 that manages the request history and provides the request history to the karaoke apparatus 20. The karaoke apparatus 20 and the karaoke management server 40 are connected via a network 1 such as a dedicated network.
[0014]
The karaoke apparatus 20 includes a communication control processing unit 21 that controls transmission and reception of data, a request processing unit 22 that requests a request history from the karaoke management server 40, and a music output processing unit 24 that outputs music data requested by a user. , And a request processing device 200 that performs processing related to provision of a request history. In addition, the request processing device 200 includes a request history transmission / reception processing unit 23 that transmits the request history received from the karaoke management server 40 to the mobile phone 3, an infrared transmission / reception unit 25 that transmits and receives infrared rays 30 from the mobile phone 3, and karaoke management. The management request processing unit 26 requests the server 40 to manage the request history.
[0015]
The communication control processing unit 21 controls transmission / reception of infrared rays from a remote controller (not shown), and controls transmission / reception of data to / from the karaoke management server 40 via the network 1. The request processing unit 22 adds the identification number of the karaoke apparatus 20 to the request history request received from the mobile terminal 3, and requests the request history from the karaoke management server 40. The music output processing unit 24 outputs video, character information, and audio from the music data received from the karaoke management server 40. As a result, the user can sing along with the sound while watching the video and characters displayed on the screen.
[0016]
The request history transmission / reception processing unit 23 of the request processing device 200 transmits the request history received from the karaoke management server 40 to the mobile phone 3. The infrared transmission / reception unit 25 transmits / receives infrared rays 30 to / from the mobile phone 3, extracts request history request information, and provides the request history to the mobile phone 3. The management request processing unit 26 requests the karaoke management server 40 to register a request history. The request processing unit 22 adds a karaoke device identification number for identifying the karaoke device 20. The karaoke devices 20 installed in one or a plurality of karaoke shops may be different manufacturers, and the manufacturer is identified. It is to do. This is because the music ID assigned to the music is different for each manufacturer, and the karaoke device identification number is used to separately manage a table using the music name and singer name data for the music ID as a common key in the request history DB 46. . This table will be described in detail with reference to FIG. The request processing device 200 of the karaoke device 20 can be installed externally. Note that data transmission / reception between the karaoke apparatus 20 and the mobile phone 3 may be performed using not only the infrared rays 30 but also any wireless means such as Bluetooth or wireless LAN.
[0017]
The karaoke management server 40 is a server computer, and the following components are controlled by a CPU (central processing unit). The CPU performs processing in the karaoke request system 10 according to a program stored in the memory unit. The karaoke management server 40 mainly includes a communication control processing unit 41 that controls data transmission / reception, a request history provision processing unit 42 that provides a request history to the karaoke device 20, and a karaoke device that stores music data corresponding to the music ID. 20, the music provision processing unit 43 provided to the management unit 20, the request history management, that is, the management processing unit 44 that stores the request history, the music data DB 45 that stores the music data for the music ID, and the request history DB 46 that stores the request history. It consists of. The request history stored in the request history DB 46 will be described with reference to FIGS.
[0018]
The communication control processing unit 41 controls data transmission / reception with the karaoke apparatus 20 via the network 1. The request history provision processing unit 42 provides the request history to the karaoke apparatus 20 in response to the request transmitted from the karaoke apparatus 20. The music provision processing unit 43 provides music data corresponding to the music ID requested from the karaoke device 20 to the karaoke device 20. When receiving the request history management request from the karaoke device 20, the management processing unit 44 stores the request history in the request history DB 46 together with the karaoke device identification number for identifying the karaoke device 20.
[0019]
The mobile phone 3 includes an address search processing unit 31 that searches for address information that identifies members who use karaoke stored in the memory of the mobile phone 3, a management request processing unit 32 that requests management of request history, a request history And a request history request processing unit 33 for requesting. A screen displayed on the mobile phone 3 in the management request process and a screen for searching for address information will be described in detail with reference to FIG. 6, and a screen for requesting a request history will be described in detail with reference to FIG. Note that the present invention is not limited to the mobile phone 3 and can be applied to any mobile terminal having a function capable of inputting necessary information on the screen and transmitting it to the karaoke apparatus 20 such as PDA (Personal Digital Assistant).
[0020]
Below, a procedure until the request history is provided from the karaoke apparatus 20 to the mobile phone 30 and the request history is displayed on the screen of the mobile phone 30 in the karaoke request processing will be briefly described. In the present invention, as a premise for executing the karaoke request process, the management request processing unit 32 of the mobile phone 3 makes a request for managing the request history when the karaoke was used before, and the request history DB 46 stores the request history. Is stored. First, the user transmits an infrared ray 30 including a request history request from the mobile phone 3 to the karaoke apparatus 20. The karaoke apparatus 20 receives the infrared rays 30 by the infrared transmission / reception unit 25 and extracts a request history request. The request processing unit 22 adds a karaoke device identification number for identifying the karaoke device 20 to the request for the extracted request history, and transmits the request to the karaoke management server 40. The request history provision processing unit 42 of the karaoke management server 40 extracts the request history stored in the request history DB 46 in response to the received request, and transmits the request history to the predetermined karaoke apparatus 20. In the karaoke apparatus 20, the transmitted request history is provided to the mobile phone 30 and displayed on the screen of the mobile phone 30.
[0021]
As described above, the karaoke apparatus 20 receives the request history request from the portable terminal 30, adds the identification number for identifying the karaoke apparatus to the request history request, requests the karaoke management server 40 for the request history, and manages the karaoke management. By providing the request history received from the server 40 to the mobile phone 3 and displaying it on the screen of the mobile phone 3, the user recognizes the music previously requested by the user and the member, and the previously sung music and others You can request karaoke by avoiding songs sung by members. The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[0022]
Next, the procedure of the karaoke request process performed by the karaoke apparatus 20 will be described. FIG. 2 is a diagram showing a flowchart of karaoke request processing in the karaoke apparatus. In FIG. 2, first, in the process of step S <b> 10, the infrared transmitter / receiver 25 of the karaoke apparatus 20 determines whether or not the infrared ray 30 has been received from the mobile phone 3. If the infrared ray 30 is not received in the process of step S10, the process of step S10 is repeated. When the infrared ray 30 is received in the process of step S10, the infrared ray transmitting / receiving unit 25 adds a karaoke apparatus identification number for identifying the karaoke apparatus 20 to the received data, and generates request information in the process of step S11. In the process of step S <b> 12, the request processing unit 22 transmits the generated request information to the karaoke management server 40. In the process of step S <b> 13, the request history transmission / reception processing unit 23 receives a request history from the karaoke management server 40. In the process of step S <b> 14, the request history transmission / reception processing unit 23 transmits the request history to the mobile phone 3. Here, the received request history is displayed on the screen of the mobile phone 3. Thereby, the user can recognize from the request history displayed on the screen of the mobile phone 3 the members who have used karaoke before and the songs sung by each of the members. In addition, the user determines a song to be requested next based on the request history displayed on the screen of the mobile phone 3, and transmits a number (music ID) for identifying the song to the karaoke apparatus 20 from the remote controller.
[0023]
In step S15, the communication control processing unit 21 receives the music ID from the remote controller. In the process of step S <b> 16, the communication control processing unit 21 adds the karaoke device identification number to the music ID and transmits it to the karaoke management server 40. In the process of step S <b> 17, the music output processing unit 24 receives music data from the karaoke management server 40. In the process of step S18, the music output processing unit 24 executes an output process based on the received music data.
[0024]
Thus, the karaoke apparatus 20 requests the request history from the karaoke management server 40 in response to the request added to the infrared ray 30 from the mobile phone 3, and provides the request history received from the karaoke management server 40 to the mobile phone 3. By displaying on the screen of the mobile phone 3, the user recognizes the members who used karaoke before recognition and the songs sung by each of the members, and the songs sung by other members and the songs sung by other members You can request at karaoke. The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[0025]
Next, the procedure of the karaoke request process executed by the karaoke management server 40 will be described. FIG. 3 is a diagram showing a flowchart of karaoke request processing in the karaoke management server. In FIG. 3, first, in the process of step S <b> 30, the communication control processing unit 41 of the karaoke management server 40 determines whether a request history request has been received from the karaoke apparatus 20. If a request history request is received from the karaoke apparatus 20 in step S30, the request history provision processing unit 42 extracts a predetermined request history from the request history DB 46 in step S31. In step S32, the request history provision processing unit 42 provides the extracted request history to the karaoke apparatus 20. In the process of step S33, the music provision processing unit 43 determines whether or not a music ID (and karaoke device identification number) has been received, that is, whether or not a music data request has been received.
[0026]
If the request for music data is not received in the process of step S33, the process from step S30 is repeated. When a request for music data is received in the process of step S33, the music provision processing unit 43 extracts the music data for the music ID from the music data DB 45 and transmits it to the predetermined karaoke apparatus 20 in the process of step S34. In the process of step S <b> 35, the management processing unit 44 determines whether or not a management request has been received when the music data request is received from the karaoke apparatus 20 or after the music data is transmitted. If the management request is not received in the process of step S35, the karaoke request process is terminated. If a management request is received in the process of step S35, the management processing unit 44 in the process of step S36, the request history relating to the transmitted music data, for example, the music ID, member name and phone number, karaoke device identification number request Store in the history DB 46. If the request history request is not received from the karaoke apparatus 20 in the process of step S30, the process from step S33 is repeated.
[0027]
As described above, the karaoke management server 40 provides a request history to the karaoke device 20 in response to a request from the karaoke device 20, transmits music data to the karaoke device 20, and receives a management request from the karaoke device 20. In this case, the request history can be provided to the user's mobile phone 3 by storing and managing the request history in the request history DB 46.
[0028]
Next, a table stored in the request history DB 46 will be described. FIG. 4 is a diagram illustrating a table stored in the request history DB. A table 100 shown in FIG. 4 shows a request history stored based on a request transmitted from the management request processing unit 26 of the karaoke apparatus 20. In the table 100, an item indicating the user's membership number issued at the karaoke store where the karaoke apparatus 20 is installed, an item indicating the user's name and the mobile phone number of the mobile phone 3, and the sung music ID are shown. An item indicating the member name and mobile phone number at that time, an item indicating the date and time when the karaoke was used, an item indicating the number identifying the karaoke device 20, and an item indicating the number for identifying the request history It consists of and. For example, the table 100 includes a member number “10001”, a name, a mobile phone number “Utao Kusunoki, 090xxxxxxxx”, and song IDs “1111”, “2222”, “3333” sung by the user, “4444”, member's name, mobile phone number “Rikuyo Yasuto, 090xxxzzzz”, “Taro Yamada, 090yyyxxxx”, “Jiro Suzuki, 090zzzzyyy”, karaoke use date “April 10, 2003, 16: 48- 19:55 ”, the karaoke device identification number“ 99999 ”, and the request history number“ 12345 ”are stored.
[0029]
Next, a table related to the sung music ID stored in the request history DB 46 will be described. FIG. 5 is a diagram illustrating a table stored in the request history DB 46. A table 105 shown in FIG. 5 shows a table related to the sung music ID for each name (member name) and mobile phone number generated based on the table 100 shown in FIG. The table 105 includes an item indicating a name (member name) and a mobile phone number, an item indicating a request history number, an item indicating a song ID that has been sung, a song ID that has been sung, and a karaoke device identification number item in the table 100. Are composed of an item indicating the song name generated based on the manufacturer identified from, and an item indicating the singer name. For example, the table 105 includes a name (member name) and a mobile phone number “Urban Urao, 090xxxxxxxx”, a request history number “12345”, song IDs “111”, “2222”, “3333”, “4444”, the song names “aaaaaa”, “bbb”, “cccccc”, “dddddd” and the singer names “ΔΔΔΔ”, “□□□”, “××××” ”And“ ◇◇◇◇ ”are stored.
[0030]
When there is a request history request for the name and mobile phone number designated by the user's mobile phone 3 from the karaoke apparatus 20, the karaoke management server 40 generates a request history generated from necessary items in the tables 100 and 105. Is provided to the karaoke apparatus 20. In addition, it is not limited to the items shown in the tables 100 and 105 in FIGS. 4 and 5, but the points scored when singing at karaoke may be stored.
[0031]
Next, a screen displayed on the mobile phone 3 when requesting management of the request history will be described. FIG. 6 is a screen diagram displayed on the mobile phone in the management request process. Here, the screen to be displayed on the mobile phone 3 is created and managed by the karaoke management server 40 and provided to the mobile phone 3 via the mobile phone network in response to a request from the mobile phone 3. In addition, it is assumed that the user has registered for a service for managing a karaoke request history before using this screen. At this time, a request history management request can be easily made using the membership number managed by the karaoke shop.
[0032]
A screen 110 shown in FIG. 6A shows a screen for making a management request for a karaoke request history displayed on the mobile phone 3. On the screen 110, an input area 111 for inputting the name of the user of the mobile terminal 3, an input area 112 for inputting the mobile phone number of the user, and an input area for inputting the name and mobile phone number of the member of the karaoke. 113, an address search button 114 for searching for the member's name, mobile phone number, ie, address information, and a button 115 for transmitting to the karaoke apparatus 20 are displayed. For example, in the input area 111 of the screen 110, the user enters the user's name “Urban Utage”, the input area 112 has a mobile phone number “090xxxxxxxx”, and the input area 113 has “Taro Yamada, 090yyyyxxx”, “Jiro Suzuki” , 090zzzzyyyy ”. Here, when another member (member name, mobile phone number “Riku Hakuto, 090xxxxzzzz”) is to be input, when the address search button 114 is selected, a screen 120 shown in FIG. 6B is displayed. The
[0033]
A screen 120 shown in FIG. 6B is a screen for searching for members from a list of address information stored in the mobile phone 3. On the screen 120, a display selection area 121 indicating a list of address information and a determination button 122 for determining the selected address information are displayed. For example, when the member name and the mobile phone number “Land pattern 簾 登, 090xxxxzzzz” are selected from the display selection area 121, the address information portion is displayed in a shaded manner. When the determination button 122 is selected in this state, the address information of this member is displayed in the input area 113 shown in FIG.
[0034]
As described above, since the request history input operation can be performed using the address information stored in the mobile phone 3, a request history management request can be efficiently and easily performed.
[0035]
Next, a screen displayed on the mobile phone 3 when requesting a request history in the karaoke request process will be described. FIG. 7 is a screen diagram displayed on the mobile terminal in the karaoke request process. A screen 130 illustrated in FIG. 7 is a screen for requesting a request history displayed on the mobile phone 3. The screen 130 includes a selection area 131 for selecting a song list when the user sang before, a selection area 132 for selecting a song list of another member, an input area 133 for inputting the name of the member, A button 134 for searching the name of the member from the address information and a button 135 for transmitting the selected and input information to the karaoke apparatus 20 are displayed. For example, when the member name is input in the input area 133, when the address search button 134 is selected, a screen similar to the screen 120 shown in FIG. 6B is displayed, and the name of a predetermined member is selected from the screen. . It is also possible to set a plurality of screens 130 to be selectable. In this case, the request history of a plurality of members (including users) can be provided from the karaoke management server 40 to the karaoke apparatus 20 and displayed. it can. Further, when the member name “Land pattern Tono” is input in the input area 133, the selection area 132 is selected and the transmission button 135 is selected, a request history request is transmitted to the karaoke apparatus 20 by the infrared ray 3. In addition, the karaoke apparatus 20 receives a request history from the karaoke management server 40 in response to a request history request, and transmits the request history to the mobile phone 3 using infrared rays 3. In the mobile phone 3, the request history is displayed on the screen.
[0036]
Next, the request history displayed on the screen of the karaoke apparatus 20 will be described. FIG. 8 is a screen diagram showing a request history. A screen 140 shown in FIG. 8 is displayed on the screen of the mobile phone 3 and shows a request history transmitted from the karaoke management server 40 under the conditions requested from the mobile phone 3 (conditions set on the screen shown in FIG. 7). ing. The screen 140 includes the name and mobile phone number of the user who requested the management of the request history, the request history number, the date and time when karaoke was used, the display area 141 indicating the names and mobile phone numbers of other members, and the song that has been sung. A display area 142 indicating the ID, song name, and singer name is displayed.
[0037]
As described above, the karaoke request system 10 of the present invention transmits a request history management request and a request history request from the mobile phone 3 (mobile terminal) to the karaoke device 20, and the karaoke device 20 manages the request history in karaoke. Acquired from the server 40, transmits the request history to the mobile phone 3, and displays the request history on the screen of the mobile phone 3 as shown in FIG. 8, thereby recognizing the music previously requested by the user and the member. , Karaoke requests can be made avoiding previously sung songs and songs sung by other members. The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[0038]
Note that a part of the request history such as the acquired request history or the song name is stored in the mobile phone 3, and the request is stored with reference to the request history stored in the mobile phone 3 when the next karaoke is used. Good.
[0039]
Next, a karaoke request system according to a second embodiment of the present invention will be described. FIG. 9 is a block diagram of the karaoke request system according to the second embodiment of the present invention. In the karaoke request system 11 shown in FIG. 9, the same components as those of the karaoke request system 10 shown in FIG. Further, the mobile phone 3 shown in FIG. 9 has the same configuration as the mobile phone 3 shown in FIG. The karaoke request system 11 of the second embodiment of the present invention has a request history providing server 50. The request history providing server 50 is a server computer that performs service work as an ASP (Application Service Provider), and the following components are controlled by the CPU. The CPU performs processing in the karaoke request system 11 in accordance with a program stored in the memory unit. The request history providing server 50 mainly includes a communication control processing unit 51 that controls data transmission / reception, a request history providing processing unit 52 that provides a request history to the mobile phone 3, and a management processing unit 44 that manages the request history. The request management DB 46 stores the request history.
[0040]
The communication control processing unit 51 controls data transmission / reception with the karaoke management server 40 via the network 1. The communication control processing unit 51 controls data transmission / reception with the mobile phone 3 via the mobile phone network 2 and the base station 4. The request history provision processing unit 52 extracts a predetermined request history from the request history DB 46 and provides the request history to the mobile phone 3. The karaoke management server 40 also includes a request history transfer processing unit 47 that transfers data for managing the request history to the request history providing server 50. In particular, the request history transfer processing unit 47 generates a request history including song information indicating a song name and a singer name based on a request history management request, and transfers the request history to the request history providing server 50.
[0041]
Next, karaoke request processing executed in the karaoke request system 11 of the second embodiment of the present invention will be described. First, when a request history management request is transmitted from the management request processing unit 32 of the mobile phone 3 to the karaoke device 20, the karaoke device 2 transmits a request history management request to the karaoke management server 40. The karaoke management server 40 provides the request history providing server 50 with data for managing the request history. The management processing unit 44 of the request history providing server 50 stores the transmitted request history in the request history DB 46.
[0042]
As described above, in the state where the request history is managed, the request history request processing unit 33 of the mobile phone 3 provides the request history request to the request history providing server 50 via the base station 4 and the mobile phone network 2. . When the request history providing server 50 receives a request history request, the request history providing processing unit 52 extracts the request history stored in the request history DB 46, and the mobile phone 3 via the mobile phone network 2 and the base station 4. Provide request history to.
[0043]
In this way, the request history managed by the request history providing server 50 can be provided to the user's mobile phone 3 and displayed on the screen of the mobile phone 3 without the user being known by other members. You can browse the request history of a given member, recognize songs previously requested by users and members, and request at karaoke while avoiding previously sung songs and songs sung by other members .
[0044]
【The invention's effect】
As described above, according to the present invention, a request history request is received from a portable terminal, an identification number for identifying a karaoke device is added to the request history request, and a request history request is sent to the karaoke management server that manages the request history. By sending and receiving the request history from the karaoke management server, providing the request history to the mobile device and displaying it on the mobile device, the user recognizes the music that each of the members who previously used karaoke requested, You can avoid singing songs that were previously sung and songs sung by other members and request them at karaoke. The request history can also be used when the name of a song or singer that was previously sung cannot be remembered.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of a karaoke request system according to a first embodiment of the present invention.
FIG. 2 is a diagram showing a flowchart of karaoke request processing in the karaoke apparatus.
FIG. 3 is a diagram illustrating a flowchart of karaoke request processing in a karaoke management server.
FIG. 4 is a diagram showing a table stored in a request history DB.
FIG. 5 is a diagram showing a table stored in a request history DB.
FIG. 6 is a screen diagram displayed on the mobile terminal in the management request process.
FIG. 7 is a screen diagram displayed on the mobile terminal in the karaoke request process.
FIG. 8 is a screen diagram showing a request history.
FIG. 9 is a block diagram of a karaoke request system according to a second embodiment of the present invention.
[Explanation of symbols]
1 network
2 Mobile phone network
3 Mobile phone
4 base stations
10, 11 Karaoke request system
20 Karaoke equipment
21 Communication control processing unit
22 Request processing part
23 Request history transmission / reception unit
24 Music output processing section
25 Infrared reception processor
26 Management Request Processing Unit
31 Address search processing part
32 Management request processing part
33 Request history request processing part
40 Karaoke management server
41 Communication control processing unit
42, 52 Request history provision processing unit
43 Music provision processing section
44 Management processing section
45 Music data DB
46 Request history DB
47 Request history transfer processing part
50 Request history server
51 Communication control processing unit

Claims (3)

A karaoke request system that provides a request history indicating address information for identifying a member who uses karaoke and information on a song already requested by the member,
Request receiving means for receiving the request history request input from the mobile terminal using the address information stored in the mobile terminal ;
A request transmitting means for adding an identification number for identifying a karaoke device to the request history request, and transmitting the request history request to a karaoke management server that manages the request history;
A karaoke request system comprising: request history providing means for receiving the request history from the karaoke management server and providing the request history to the portable terminal.   The karaoke request system according to claim 1, wherein the request history includes sung music information for each address information for identifying the member. A karaoke request system that provides a request history indicating address information for identifying a member who uses karaoke and information on a song already requested by the member,
Mobile devices
Search means for searching for address information for identifying a member who uses the karaoke;
Input using the address information, management of request history of members using the karaoke, and request means for requesting browsing of the request history,
Karaoke equipment
Request receiving means for receiving the request history management request input using the address information from the request means of the mobile terminal;
Adding an identification number for identifying a karaoke device to the management request, and request transmitting means for transmitting the management request to a karaoke management server for managing the music information,
The karaoke management server
Based on the management request received from the karaoke device, it has a transfer means for generating a request history including the address information, song name, song information indicating a singer name, and transferring the request history to a request history providing server. ,
The above request history providing server
Request history management means for managing the request history received from the karaoke management server;
A karaoke request system comprising request history providing means for providing the request history to the portable terminal in response to a request from the request means of the portable terminal.

Images