JP3945007B2 - Recording system and recording method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a recording system and a recording method capable of managing a data path by duplication.
[0002]
[Prior art]
In recent years, along with the increase in capacity of hard disks and the spread of digital music data such as CDs (Compact Discs), it has been proposed to store, for example, music data recorded on CDs on recording media such as hard disks. This is called, for example, a music server. By compressing and encoding music data by a predetermined method, for example, music data of about 1000 songs can be stored in a hard disk of several G (Giga) bytes.
[0003]
In this music server, attribute information relating to each stored music data, for example, information such as a song title and a player name can be recorded. This attribute information is acquired and recorded automatically or by manual input. The recorded attribute information is displayed as a list, for example, on a display unit provided in the music server. Based on this attribute information, the user can search and select a desired one from the music data stored in the music server and reproduce it. Since it is possible to search by a predetermined key or the like, it is very convenient.
[0004]
In such a music server, the stored music data can be copied and shared to other electronic devices such as a portable music data recording / reproducing apparatus (hereinafter referred to as a portable recording / reproducing apparatus). The user can select favorite data from a large number of music data stored in the music server, copy it to a portable recording / reproducing apparatus, and reproduce the music data at various places such as outdoors.
[0005]
By the way, since digital music data hardly deteriorates in sound quality due to a recording medium and can be easily duplicated completely, there is a risk that copyright may be threatened by unlimited copying. Conventionally, as a measure for copyright protection, copying (dubbing) of digital music data including copyright has been managed by SCMS (Serial Copy Management System). In this method, a predetermined flag is provided for digital music data, and copying as digital data is limited to, for example, one generation. SCMS is installed in digital interfaces such as DAT (Digital Audio Tape) and MD (Mini Disc) for consumer use.
[0006]
However, in this SCMS, there is a possibility that the data sharing property is remarkably limited due to the importance of copyright protection. For example, music data obtained by digital duplication cannot be transferred from the duplicated recording media to other recording media again, even for personal use, which is very inconvenient. there were.
[0007]
[Problems to be solved by the invention]
In order to solve this problem, a method has been proposed in which after the music data is duplicated, the music data cannot be reproduced at the duplication source. Such a data replication method is referred to as migration. At the movement source, the music data is returned again, and the unplayable state is solved. According to this, there is always only one piece of moved music data starting from, for example, a music server. Therefore, in this method, the copyright of the music data is protected even if copying is performed.
[0008]
If the movement of the music data is repeated, there is a possibility that the location of the data or the movement source may not be known. Therefore, in this method, it is necessary to grasp at least the movement destination of each moved data in the music server.
[0009]
In order to grasp the movement destination of music data, a method of storing device information of the movement destination of data in a music server can be considered. However, this method has a problem that music data must be moved one by one through the music server that is the starting point of the data movement, which is very inconvenient.
[0010]
For example, in this method, when data is moved between two portable recording / reproducing apparatuses, the music server cannot grasp the movement destination.
[0011]
Therefore, an object of the present invention is to provide a recording system and a recording method that can easily grasp a destination even if music data is repeatedly moved.
[0012]
[Means for Solving the Problems]
In order to solve the above-described problem, the present invention stores first and second electronic devices that store data and reproduces the stored data, and stores at least first data stored in the first electronic device. And copying means for moving or copying to the second electronic device. When data stored in the first electronic device is moved or copied to another predetermined electronic device, it is moved or copied to the first electronic device. In addition, the recording system is characterized in that the identifier of another electronic device to which data is moved or copied is stored relative to predetermined data, and the time of movement or copying is stored.
[0013]
Further, in order to solve the above-described problem, the present invention stores an identifier corresponding to the first electronic device when data is moved or copied from the first electronic device to the second electronic device. Device identifier storage means, destination data identifier storage means for storing an identifier corresponding to the second electronic device when the data is moved or copied from the first electronic device to the second electronic device, and the data A time storage means for storing a time when the electronic device is moved or copied from the first electronic device to the second electronic device; a source device identifier for the data moved or copied from the first electronic device to the second electronic device; A recording system comprising a destination device identifier and an adding means for adding time.
[0014]
In order to solve the above-described problem, the present invention stores first and second electronic devices that store data and reproduces the stored data, and data stored in the first electronic device. A copy step of moving or copying to at least a second electronic device, and moving to the first electronic device when data stored in the first electronic device is moved or copied to another predetermined electronic device Alternatively, the recording method is characterized in that an identifier of another electronic device to which data is moved or copied is stored relative to predetermined copied data, and a time of movement or copying is stored.
[0015]
Further, in order to solve the above-described problem, the present invention stores an identifier corresponding to the first electronic device when data is moved or copied from the first electronic device to the second electronic device. A device identifier storing step, a data storing device identifier storing step for storing an identifier corresponding to the second electronic device when the data is moved or copied from the first electronic device to the second electronic device, and the data A time storage step for storing a time at which the first electronic device is moved or copied from the first electronic device to data to be moved or copied from the first electronic device to the second electronic device. An additional step of adding an identifier, a movement destination device identifier, and a time is provided.
[0016]
As described above, according to the present invention, when data stored in the first electronic device is moved or copied to a predetermined other electronic device, the data is relative to the predetermined data moved or copied to the first electronic device. Since the identifier of the other electronic device to which the data is moved or copied is stored and the time of the movement or copying is stored, the data destination and time of the data are stored in the first electronic device. I can grasp it.
[0017]
In addition, according to the present invention, the source device identifier, the destination device identifier, and the time are added to the data that is moved or copied from the first electronic device to the second electronic device. The route of movement can be grasped.
[0018]
DETAILED DESCRIPTION OF THE INVENTION
The present invention will be described below. First, prior to the description of the embodiments, a configuration to which the present invention can be applied will be described in order to facilitate understanding. FIG. 1 schematically shows a music server to which the present invention is applied and a system using the music server. The music server 50 includes a server main body 51 and left and right speaker units 52L and 52R. The server main body 51 is provided with a display unit 53 made of, for example, an LCD (Liquid Crystal Display) panel, and a CD insertion unit 54 for inserting a CD.
[0019]
Although omitted in FIG. 1, an operation unit for the user to operate the functions of the server main body 51 is provided on the server main body 51. Further, for example, a signal receiving unit for receiving an infrared signal may be provided for remotely controlling the function of the server main body 51 with a remote commander. The server body 51 has a CPU and is controlled by a predetermined program stored in advance in, for example, a ROM.
[0020]
The user can set the CD 55 in the CD insertion unit 54 and perform a predetermined operation on the operation unit to reproduce the CD 55 and enjoy the reproduced music, for example, by the speaker units 52L and 52R. Further, when the CD 55 is CD text including text data, predetermined text data can be displayed on the display unit 53.
[0021]
The music server 50 has a large-capacity recording medium such as a hard disk inside. Based on a predetermined operation, the music data of the CD 55 set in the CD insertion section 54 can be recorded on this recording medium. At this time, it is possible to select a method of recording at a single speed that is the same as the playback speed of the CD 55 and a high-speed recording that performs recording at a speed higher than the playback speed. High-speed recording can be selected and executed by performing a billing process according to a predetermined procedure.
[0022]
In the music server 50, the music data is compressed and encoded by a predetermined method and recorded as compressed music data. For example, about 1000 songs can be stored in a hard disk having a capacity of 6 GBytes. A list of music items stored in the hard disk is displayed on the display unit 53, for example, and the user can select and play an arbitrary music based on this display. Further, since the hard disk can be randomly accessed, it is possible to continuously reproduce a large number of stored music data in an arbitrary order.
[0023]
Various methods can be used for compression coding. In this example, a method called ATRAC2 (Adaptive Tranform Acoustic Coding 2) is used. This is an extension of ATRAC, which is a compression coding method used for MD, and uses transforming coding and entropy coding by utilizing the masking effect based on auditory properties and the frequency dependence of the minimum audible limit. In combination, the audio data is compressed and encoded. With relatively small hardware, encoding / decoding can be performed at high speed while maintaining high sound quality.
[0024]
The music server 50 can be connected to an external system, for example, an Internet server 60 that is a server connected to the Internet, via a communication line 61 that is a public telephone line, for example. By connecting to the Internet server 60 from the music server 50 via the communication line 61, various information on the Internet can be obtained. The Internet server 60 has a database storing title information of commercially available music CDs, for example. By giving a predetermined key to this database, data accompanying the CD, for example, title information of the CD can be obtained.
[0025]
In addition, the Internet server 60 performs billing processing for the music server 50 according to the service. The above-described high-speed recording of the CD 55 is performed by the music server 50 communicating with the Internet server 60, and can be selected and executed.
[0026]
Here, the billing process is performed by the Internet server 60 having a lot of CD additional information, but this is not limited to this example. For example, this billing process may be performed by another server connected to the Internet. It is also possible to perform the billing process on a dedicated network other than the Internet, for example.
[0027]
The portable recording / reproducing apparatus 70 has a recording medium including a hard disk or a flash memory (flash RAM). Other recording media can be used as long as the music playback speed can be followed. By connecting the portable recording / reproducing apparatus 70 to the music server 50 via the connection line 71, the music data recorded on the music server 50 can be transferred to the portable recording / reproducing apparatus 70 and recorded on the recording medium. . At this time, on the music server 50 side, the transferred music data exists on the recording medium but cannot be reproduced. The recording medium used in the portable recording / reproducing apparatus 70 has a capacity of, for example, about 200 MBytes, and can store music data for several tens of songs.
[0028]
Here, when the above transfer method used in the present invention, that is, music data is transferred, the music data is recorded on the transfer destination recording medium, and the transferred music data is stored on the transfer source recording medium. The state that exists on the recording medium but cannot be reproduced is referred to as “movement”. In other words, the right to use music data is changed between devices by movement. By moving the music data in this way, unlimited copying of the music data can be prevented.
[0029]
In the above description, the music server 50 and the portable recording / reproducing apparatus 70 are connected by the connection line 71. However, this is not limited to this example. For example, the music server 50 and the portable recording / reproducing apparatus 70 can be provided with corresponding mounting portions, and the portable recording / reproducing apparatus 70 can be directly attached to the music server 50 to exchange data. Further, not only electrical connection but also an interface corresponding to IrDA (Infrared Data Association) for exchanging data by infrared signals, for example, may be provided on both sides to transfer music data by infrared signals.
[0030]
Furthermore, by providing a predetermined interface for the music server 50, information exchange with various media can be performed. For example, by providing an interface corresponding to the PC card 80, music data distributed by the PC card 80 can be taken into the music server 50, and data can be exchanged between the personal computer and the music server 50. Become. By providing a serial digital interface such as an optical cable, music data can be exchanged with another digital music data recording / reproducing apparatus such as the MD recorder 81, for example. In this example, the MD 82 is mounted on the MD recorder 81, and music data reproduced from the MD 82 is supplied to the music server 50. Similarly, an interface such as IEEE1394 can be provided, and for example, a set top box 83 for CATV (Cable Television) or satellite broadcasting can be connected.
[0031]
The PC card is a standard for a card-type peripheral device for a personal computer jointly established by PCMCIA (Personal Memory Card International Association) in the US and JEIDA (Japan Electronics Industry Promotion Association) in Japan. IEEE 1394 is an interface standard adopted by the American Institute of Electrical and Electronics Engineers.
[0032]
The music server 50 can have a WWW (World Wide Web) browser as a built-in application. By connecting to the Internet server 60 via the communication line 61, various contents on the Internet described in, for example, HTML (Hypertext Markup Language) can be searched and displayed on the display unit 53.
[0033]
With such a configuration, for example, the user can play back music data stored in the music server 50 and listen to it with the speaker units 52L and 52R, and set the CD 55 in the CD insertion unit 54 and set the CD 55 Can be played.
[0034]
Further, by performing communication between the music server 50 and the Internet server 60, the title information of the CD 55 set in the CD insertion unit 54 can be automatically obtained via the communication line 61. The obtained information is stored in the music server 50 and displayed on the display unit 53 as necessary.
[0035]
More specifically, user information such as a user ID is sent from the music server 50 to the Internet server 60. On the Internet server 60 side, verification processing and billing processing are performed based on the received user information. Also, media information is sent from the music server 50 to the Internet server 60. Based on the received media information, the Internet server 60 searches for additional information with respect to music data such as a song title, a player name, a composer / lyricist name, lyrics, and a jacket image. Then, the Internet server 60 returns predetermined information requested by the user to the music server 50.
[0036]
For example, TOC (Table Of Contents) information of CD 55 is sent to the Internet server 60 as media information. In the Internet server 60, a database is constructed in which additional information for the music data can be searched using the TOC information as a key. Additional information may be obtained by searching other WWW servers on the Internet. The Internet server 60 searches for additional information of the music data based on the received TOC information. This can be searched based on the time information of each piece of music recorded on the CD 55 included in the TOC, for example.
[0037]
Additional information obtained by the search is transmitted from the Internet server 60 to the music server 50. In the music server 50, the received additional information is displayed on the display unit 53. Note that by sending the additional information embedded in the HTML file, the additional information can be displayed on the music server 50 using the built-in WWW browser.
[0038]
If another URL (Uniform Resource Locator) on the Internet is described in the additional information, the music server 50 can access a homepage on the Internet indicated by the URL.
[0039]
Further, by communicating with the Internet server 60, the music data of the CD 55 set in the CD insertion unit 54 is recorded on the recording medium of the music server 50 at a speed higher than the prescribed playback speed of the CD 55, for example, one CD 55 Minute music data can be recorded in about 2 minutes. When communication with the Internet server 60 is not performed, recording is performed at a single reproduction speed equal to the specified reproduction speed.
[0040]
Furthermore, the music data stored in the music server 50 can be transferred to the portable playback device 71 and moved by connecting to the portable recording / playback device 70 via the connection line 71. The moved music data can be reproduced by the portable recording / reproducing apparatus 70 even when the connection by the connection line 71 is not made, and can be listened to by the headphones 72, for example. The music data that has been transferred and moved is in a state in which the music server 50 cannot reproduce the music data.
[0041]
FIG. 2 shows an example of the configuration of the music server 50. First, the music server 50 is provided with a RAM 5, a ROM 6, a flash RAM 7, and a CPU 8 which are coupled to each other via a bus, in the same manner as in the configuration of a normal personal computer. CPU 8 is connected to bus 40. The entire operation of the music server 50 is controlled by the CPU 8.
[0042]
The ROM 6 stores a program for controlling the operation of the music server 50 in advance. In the music server 50, an operation corresponding to the operation of the input means 1 described later is performed based on this program. In the RAM 5 and the flash RAM 7, a data area and a task area for executing a program are temporarily secured. Alternatively, the ROM 6 stores a program loader, and the program itself can be loaded into the flash RAM 7 by the program loader.
[0043]
The input unit 1 includes, for example, a push type key and a rotary type key. The input unit 1 is not limited to this, and may be a rotary push type key called a jog dial, a touch panel on an LCD, or the like. Of course, it is possible to use a switch mechanism that reacts when pressed. A signal corresponding to the operation of the input means 1 is supplied to the CPU 8 via the bus 40. The CPU 8 generates a control signal for controlling the operation of the music server 50 based on this signal. The music server 50 is operated according to this control signal.
[0044]
An infrared interface (IrDA I / F) driver 3 and / or a USB (Universal Serial Bus) driver 4 is connected to the bus 40. The keyboard 2 can communicate or connect to these drivers. By using the keyboard 2, it is possible to easily input, for example, a song name and an artist name corresponding to recorded music data. Alternatively, data transfer may be performed via the infrared interface driver 3 or the USB driver 4. The infrared interface 3 and the USB driver 4 can be omitted.
[0045]
The CD-ROM drive 9 is connected to the bus 40, and the above-described CD 55 is set in the CD-ROM drive 9. In the CD-ROM drive 9, music data is read from the set CD 55 at a specified reproduction speed. Further, the CD-ROM drive 9 can read the music data of the CD 55 at a speed higher than the prescribed reproduction speed, for example, 16 times or 32 times the prescribed reproduction speed.
[0046]
The CD-ROM drive 9 is not limited to this example, and may be compatible with other media storing music data, such as a magneto-optical disk or a DVD (Digital Versatile Disc). A drive corresponding to the memory card can also be used. Further, the data read from the CD-ROM drive 9 is not limited to music data. Image data, text data, program data, etc. can be read out.
[0047]
A hard disk drive HDD 10 is connected to the bus 40. In the HDD 10, music data read from the CD-ROM drive 9 is recorded.
As preprocessing for recording music data on the HDD 10, the music data read by the CD-ROM drive 9 is supplied to the compression encoder 12 via the bus 40 and the audio DRAM 11.
[0048]
In the compression encoder 12, for example, the music data is compression-encoded by the above-described ATRAC2. Note that two speeds of low speed and high speed are prepared for the compression speed of the music data by the compression encoder 12 based on the control of the CPU 8.
The low speed compression corresponds to a reproduction speed of 1 × speed in the CD-ROM drive 9. The compression speed is switched according to the reproduction speed by the CD-ROM drive 9, for example. In the compression encoder 12, for example, an encoding algorithm corresponding to the compression speed is driven.
[0049]
The change of the compression speed in the compression encoder 12 is not limited to this method. For example, it may be performed by switching the clock frequency of the compression encoder 12. Also, different hardware may be prepared for each. Further, in the compression encoder 12 capable of high-speed compression, it is possible to perform low-speed compression by thinning processing.
[0050]
The compressed music data compressed and encoded by the compression encoder 12 is recorded and stored in the HDD 10 via the DRAM 11.
[0051]
Here, the compressed music data compression-encoded by the compression encoder 12 is configured to be stored in the HDD 10, but the music data read from the CD-ROM drive 9 is directly recorded and stored in the HDD 10. You can also.
[0052]
In this example, an audio signal input from the microphone connected to the terminal 13 via the amplifier 14 and an audio signal input from the line input end 15 are supplied to the compression encoder 12 via the A / D converter 16. Is done. These audio signals can be compressed and recorded on the HDD 10. Further, an optical digital signal is supplied from the optical digital input end 17 to the compression encoder 12 via an IEC958 (International Electrotechnical Commission 958) encoder 18. An audio signal supplied as an optical digital signal can be compressed and recorded in the HDD 10. Of course, it is not necessary to have all these signal input means.
[0053]
In the above description, the compression encoder 12 uses ATRAC2 as an encoding algorithm, but this is not limited to this example. In other words, the compression encoder 12 can use any other encoding algorithm that compresses information. For example, an encoding algorithm such as ATRAC (trademark), MPEG (moving picture coding experts group), PASC (precision adaptive sub-band coding), TwinVQ (trademark), RealAudio (trademark), or LiquidAudio (trademark) may be used. .
[0054]
The modem 20 is connected to the bus 40. An external network 19 such as a public telephone line, CATV, or wireless communication is connected to the modem 20. The music server 50 can communicate via the external network 19 by the modem 20.
[0055]
The music server 50 is connected to, for example, the Internet via the external network 19, and communication is performed between the music server 50 and the remote Internet server 60. Request information from the music server 50 to the Internet server 60, media information that is information related to the CD 55 set in the CD-ROM drive 9, user ID and user information given in advance to each of the music servers 50, Various information such as billing information for the user is transmitted.
[0056]
These pieces of information are received by the Internet server 60, collation processing and billing processing are performed based on the received user information such as the user ID, and additional information of the music data is searched based on the received media information, and the music server Returned to 50.
[0057]
Here, an example in which additional information of music data is returned has been shown, but it is also possible to supply music data directly from the external network 19 based on a user request. That is, the user can download music data from the Internet server 60 using the music server 50. Also, music data can be returned in response to the media information. According to this, for example, a bonus track of a predetermined CD 55 can be acquired by distribution.
[0058]
The compressed music data compressed and encoded by the compression encoder 12 and recorded and stored in the HDD 10 is supplied to the compression decoder 21 via the bus 40 when it is read out for reproduction. The compressed music data is decompressed and encoded by the compression decoder 21 and is led to the terminal 24 via the D / A converter 22 and the amplifier 23. Then, it is supplied from the terminal 24 to the speaker units 52L and 52R, and music is reproduced. Although not shown in FIG. 2, two paths from the D / A converter 22 to the terminal 24 via the amplifier 23 are provided corresponding to the stereo output. Similarly, there are two terminals 24 corresponding to stereo.
[0059]
Note that the compression decoder 21 uses a decoding algorithm corresponding to the encoding algorithm in the compression encoder 12. Further, the compression decoder 21 and the compression encoder 12 described above may be software processing by the CPU 8 without having hardware.
[0060]
The LCD 26 constituting the display unit 53 is connected to the bus 40 via the LCD driver 25. A drawing control signal is supplied from the CPU 8 to the LCD driver 25 via the bus 40. Based on this signal, the LCD driver 25 drives the LCD 26 to perform a predetermined display.
[0061]
For example, an operation menu of the music server 50 is displayed on the LCD 26. The LCD 26 displays, for example, a title list of the compressed music data recorded and stored in the HDD 10. Further, on the LCD 26, for example, a folder and a jacket image corresponding to the compressed music data to be selected and reproduced are displayed.
[0062]
Based on the display of the LCD 26, the pointing music data as the input means 1 and the keyboard 2 are operated, and the instructed music data is controlled to be reproduced.
Further, it is possible to delete the selected music data and control the copying and movement of the selected music data to an external device based on the display of the LC 26. For example, when the input unit 1 is a touch panel provided on the LCD 26, the music server 50 can be operated by touching the touch panel according to the display on the LCD 26. As described above, the music data recorded and stored in the HDD 10 is managed and controlled by the user using the LCD 26 as an interface.
[0063]
In the first embodiment, IEEE1394 and a PC card are supported as an interface between the music server 50 and an external general information device. An IEEE 1394 interface 28 is connected to the bus 40 via an IEEE 1394 driver 29. Similarly, a PC card slot 31 is connected to the bus 40 via a PC card driver 30.
[0064]
The IEEE 1394 interface 28 enables data exchange between the music server 50 and, for example, a personal computer. In addition, the IEEE 1394 interface 28 can take in music data from satellite broadcast IRD (Integrated Reciever / Decorder), MD, DVD (Digital Versatile Disc: trademark), digital video, and the like. Furthermore, by installing a PC card in the PC card slot 31, it is easy to expand various peripheral devices such as an external storage device and other media drives, or a modem, a terminal adapter, a capture board, and the like.
[0065]
The interface 34 is an interface for exchanging music data and the like between the music server 50 and other corresponding recording / reproducing devices. For example, the portable recording / reproducing apparatus 70 shown in FIG. 1 is applied to the other recording / reproducing apparatus. The present invention is not limited to this, and the other recording / playback apparatus may be another music server 50.
[0066]
An interface 34 is connected to the bus 40 via an interface driver 33. Another corresponding recording / reproducing apparatus is provided with an interface 35 that is paired with the interface 34. By electrically connecting the interfaces 34 and 35 with a predetermined connection line 71, for example, music data recorded and stored in the HDD 10 can be transferred from the music server 50 to another recording / reproducing apparatus.
[0067]
FIG. 3 schematically shows a signal flow until the music data read by the CD-ROM drive 9 is recorded in the HDD 10. The music data read from the CD-ROM drive 9 is temporarily stored in the DRAM 11 as a buffer memory via the bus 40. Then, music data is read from the DRAM 11 at a predetermined timing and supplied to the compression encoder 12 via the bus 40. The compression encoder 12 is set to a predetermined compression speed in step S13 or step S14 described above. The music data is compression-encoded by the compression encoder 12 and once stored again in the DRAM 11 as a buffer memory. Then, the compressed music data read from the DRAM 11 at a predetermined timing is supplied to the HDD 10 via the bus 40 and recorded.
[0068]
FIG. 4 schematically shows a signal flow from when the compressed music data read from the HDD 10 is reproduced to be output to the terminal 24. The compressed music data read from the HDD 10 is temporarily stored in the DRAM 11 as a buffer memory via the bus 40. Then, the compressed music data is read from the DRAM 11 at a predetermined timing and supplied to the compression decoder 21 via the bus 40. The compressed music data is decompressed and encoded by the compression decoder 21, converted into music data, and supplied to the D / A converter 22. The music data is converted into an analog audio signal by the D / A converter 22, amplified by the amplifier 23, and output to the terminal 24 as a reproduction output. If a speaker is connected to the terminal 24, the music reproduced by the speaker can be enjoyed.
[0069]
FIG. 5 shows an example of the configuration of a portable recording / reproducing apparatus 70 used as another recording / reproducing apparatus. This portable recording / reproducing apparatus 70 has a configuration substantially equivalent to that of the music server 50 shown in FIG. Further, the portable recording / reproducing apparatus 70 is normally used as a single unit with the interface 34 on the music server 50 side and the interface 35 on the portable recording / reproducing apparatus 70 side separated.
[0070]
First, the portable recording / reproducing apparatus 70 is provided with a RAM 103, a ROM 104, and a CPU 105, which are coupled to each other by a bus, in the same manner as the configuration of a normal personal computer. Of course, a flash RAM may be provided as in the configuration of the music server 50 described above. The CPU 105 is connected to the bus 130. The CPU 105 controls the overall operation of the portable recording / reproducing apparatus 70.
[0071]
The ROM 104 stores in advance a program for controlling the operation of the portable recording / reproducing device 70. In the portable recording / reproducing apparatus 70, an operation corresponding to the operation of the input means 102 described later is performed based on this program. In the RAM 103, a data area and a task area for executing the program are temporarily secured.
[0072]
The input unit 102 includes, for example, a push type key and a rotary type key. The input means 102 is not limited to this, and may be a rotary push type key called a jog dial, a touch panel on an LCD, or the like. Of course, it is possible to use a switch mechanism that reacts when pressed. A signal corresponding to the operation of the input means 102 is supplied to the CPU 105 via the bus 130. The CPU 105 generates a control signal for controlling the operation of the portable recording / reproducing device 70 based on this signal.
The portable recording / reproducing apparatus 70 is operated according to this control signal.
[0073]
In the music server 50, the music data read from the HDD 10 and instructed to be transferred to the portable recording / reproducing device 70 is connected to the interface 34, the interface 35, and the connection line connecting the interface 34 and the interface 35. The data is transferred to the portable recording / reproducing apparatus 70 and supplied.
Further, when the music server 50 and the portable recording / reproducing apparatus 70 are provided with corresponding mounting portions, the interface 34 and the interface 35 are directly connected to transfer music data. Further, when an IrDA interface is provided, music data is transferred with an infrared signal.
[0074]
The music data transferred and supplied is recorded on the HDD 106 which is a music data recording medium of the portable recording / reproducing apparatus 70 via the bus 130 from the interface driver 101.
[0075]
In the portable recording / reproducing apparatus 70, the music data recording medium is not limited to the HDD 106, and for example, a flash RAM can be used. In addition, other recording medium media such as a magneto-optical disk can be used as long as they can follow the reproduction speed of music data. As a music data recording medium, for example, several tens of songs can be recorded by using a medium having a capacity of about 200 Mbytes.
[0076]
By the way, in this example, the music data transferred and recorded in the HDD 106 is already compressed and encoded in the music server 50 and is compressed music data. The portable recording / reproducing apparatus 70 is not limited to this example, and music data that has not been compression-encoded can be supplied and recorded in the HDD 106. For example, music data reproduced and read from the CD 55 set in the CD-ROM drive 9 of the music server 50 is supplied directly to the portable recording / reproducing apparatus 70 via the interface driver 101. In this case, however, it goes without saying that the number of recordable music data is greatly limited.
[0077]
As pre-processing for recording music data on the HDD 106, the supplied music data is temporarily stored in the audio DRAM 107 connected to the bus 130. Then, the music data is supplied to the compression encoder 108 via the bus 130. The compression encoder 108 compresses and encodes music data using an encoding algorithm equivalent to the compression encoder 12 in the music server 50 (ATRAC2 in this example). The compression-coded compressed music data is supplied to the DRAM 107 and temporarily stored again. Finally, the compressed music data stored in the DRAM 107 is read and recorded in the HDD 106.
[0078]
As described above, when the compressed music data stored in the HDD 10 in the music server 50 is instructed to move and transferred to the portable recording / reproducing device 70, the compressed music data in the HDD 10 exists on the HDD 10. However, playback is disabled. The moved compressed music data is returned to the recording medium of the movement source again, and can be reproduced at the movement source. At this time, the compressed music data is deleted from the destination recording medium.
[0079]
In this example, an audio signal input from the microphone connected to the terminal 109 via the amplifier 110 and an audio signal input from the line input end 111 are supplied to the compression encoder 108 via the A / D converter 112. Is done. These audio signals can be compressed and recorded on the HDD 106. Further, an optical digital signal is supplied from the optical digital input end 113 to the compression encoder 108 via the IEC958 encoder 114. An audio signal supplied as an optical digital signal can be compressed and recorded on the HDD 106. Of course, it is not necessary to have all of these signal input means, and it is possible to omit all of these signal input means if it is a portable playback device dedicated to playback. .
[0080]
The compressed music data is read from the HDD 106 for reproduction and supplied to the compression decoder 115 via the bus 130. The music data that has been subjected to compression encoding by the compression decoder 115 is led to the terminal 118 via the D / A converter 116 and the amplifier 117. For example, a headphone 72 is connected to the terminal 118. The user can listen to the reproduced music by wearing the headphones. Although omitted in FIG. 5, two paths from the D / A converter 116 to the terminal 118 via the amplifier 117 are provided corresponding to the stereo output. Similarly, there are two terminals 118 corresponding to the stereo.
[0081]
The LCD 120 is connected to the bus 130 via the LCD driver 119. A drawing control signal is supplied from the CPU 105 to the LCD driver 119 via the bus 130, and the LCD 120 is driven to perform a predetermined display. On the LCD 120, an operation menu of the portable recording / reproducing apparatus 70, a title list of music data recorded in the HDD 106, and the like are displayed. For example, a folder or a jacket image corresponding to music data to be selected and reproduced may be displayed on the LCD 120.
[0082]
Based on the display on the LCD 120, the pointing device as the input means 102 is operated to control the reproduction of the designated compressed music data. Further, erasure, copying, and movement control of the selected compressed music data can be performed based on the display of the LC 120. For example, the portable recording / reproducing apparatus 70 can be operated by touching a touch panel as the input unit 102 in accordance with the display on the LCD 120. In this manner, the compressed music data recorded on the HDD 106 is managed and controlled by the user using the LCD 120 as an interface.
[0083]
Although omitted in FIG. 5, the portable recording / reproducing apparatus 70 is driven by a battery power source. Therefore, a power supply unit using a general dry battery and a charging unit are provided. When the music server 50 and the portable recording / reproducing device 70 are directly connected by a connection line or a mounting unit, the charging unit is charged by being supplied with power from the music server 50 and transferring music data. Of course, it can also be charged by an external charging power source. The power source may have only one of the power source using a dry cell and the charging power source.
[0084]
FIG. 6 shows another example of the portable recording / reproducing apparatus 70 described above. In FIG. 6, the same parts as those in FIG. 5 described above are denoted by the same reference numerals, and detailed description thereof is omitted. In the portable recording / reproducing apparatus 70 ′ shown in FIG. 6, a switch circuit 200 is inserted between the HDD (or flash RAM) 106 ′ and the bus 130 in the configuration shown in FIG. One selection end 200 a of the switch circuit 200 is connected to the bus 130, and the other selection end 200 b is connected to the interface 35. The switch circuit 200 separates the HDD 106 ′ from the bus 130.
[0085]
When the compressed music data is transferred from the music server 50, the selection terminal 200b is selected in the switch circuit 200. The HDD 106 ′ and the bus 40 of the music server 50 are directly connected via the interfaces 34 and 35. The HDD 106 ′ appears as if it is a recording medium of the music server 50. The CPU 8 of the music server 50 can directly control the HDD 106 ′. It is possible to easily move or copy compressed music data between the music server 50 and the portable recording / reproducing apparatus 70.
[0086]
Next, the operation in this embodiment performed with the above-described configuration will be described. First, functions executed by the music server 50 alone will be described. FIG. 7 is a flowchart of an example of processing when recording music data of the CD 55 set in the CD-ROM drive 9 in the HDD 10 of the music server 50.
[0087]
In the first step S10, a request for recording the music data of the CD 55 on the HDD 10 by the user is awaited. For example, when a recording request is issued by the user using the input unit 1, the process proceeds to step S11. In step S11, it is determined whether the requested recording is high-speed recording or single-speed recording. For example, when the recording request is issued in step S10 described above, the user specifies both the recording method, that is, whether the recording is performed at high speed or 1 × speed.
[0088]
If it is specified in step S11 that recording is to be performed at high speed, the process proceeds to step S12, and the charging system is activated. Processing by the charging system will be described later. When the charging process is performed and the high-speed recording is permitted, the process proceeds to step S13, and the compression encoder 12 starts the high-speed compression process. Then, the process proceeds to step S15.
[0089]
On the other hand, if it is specified in step S11 that recording at 1 × speed is specified, the process proceeds to step S14, and the compression encoder 12 starts the low-speed compression process. Then, the process proceeds to step S15.
[0090]
In step S15, the CD-ROM drive 9 is driven at a predetermined speed based on the control of the CPU 8, and the music data recorded on the set CD 55 is read out. The read music data is compression encoded by the compression encoder 12 and transferred to the HDD 10 for recording.
[0091]
If the transfer of the compressed music data to the HDD 10 is completed in step S16, the transfer from the CD-ROM drive 9 to the HDD 10 is prohibited in the next step S17, and the compression encoder 12 is stopped in the next step S18. Is done.
[0092]
FIG. 8 is a flowchart showing an example of the billing process in step S12 of the flowchart of FIG. The billing process is performed by performing communication between the music server 50 and the Internet server 60. FIG. 8A shows processing at the music server 50, and FIG. 8B shows processing at the Internet server 60.
[0093]
When the accounting process is started, first, communication is started between the music server 50 and the Internet server 60 using a predetermined protocol in the first step S20 of FIG. 8A. If it is confirmed in step S21 that a connection is established and communication is possible, the process proceeds to step S22.
[0094]
In step S22, the TOC information of the CD 55 set in the CD-ROM drive 9 and transferred to the HDD 10 for recording is sent from the music server 50 to the Internet server 60. At the same time, high-speed recording information indicating that high-speed recording is performed is transmitted from the music server 50 to the Internet server 60.
[0095]
On the other hand, in FIG. 8B, the Internet server 60 waits for high-speed recording information and TOC information from the music server 50 (step S30). When such information is received, TOC information is searched in step S31. The CD 55 is specified by searching the TOC information.
[0096]
Then, billing processing is performed in the next step S32. Billing can be performed, for example, by debiting from an account based on a user's registered credit card number. The billing method is not limited to this. For example, the music server 50 is provided with a function of reading a prepaid card, the set billing amount is sent to the music server 50, and the user pays the billing amount with the prepaid card. A method is also conceivable. Further, based on the TOC information, the charge amount can be changed depending on the contents of the CD 55, or recording on the HDD 10 can be prohibited.
[0097]
In step S33, billing information is sent to the music server 50.
In FIG. 8A, the billing information is confirmed on the music server 50 side (step S23). On the Internet server 60 side as well, it is confirmed whether or not the billing information is received by the music server 50 (step S34).
[0098]
Returning to FIG. 8A, when the billing information is confirmed in step S23, the process proceeds to step S24, and the received billing information or the like is displayed on the display unit 53. In step S 25, the music data of CD 55 is read at high speed by the CD-ROM drive 9, compressed at high speed by the compression encoder 12, and recorded on the HDD 10. This step S25 corresponds to step S15 in FIG.
[0099]
By the way, in this embodiment, a cooperative operation is possible between the music server 50 and the portable recording / reproducing apparatus 70. For example, when music data is moved from the music server 50 to the portable recording / reproducing apparatus 70, a cooperative operation is performed between them. FIG. 9 shows a flowchart of an example of this movement.
[0100]
First, in the first step S40, it is determined whether or not the music server 50 and the portable recording / reproducing apparatus 70 are connected by the interfaces 34 and 35. For example, the connection is detected by exchanging a predetermined signal between the interfaces 34 and 35. Further, the present invention is not limited to this, and a switch mechanism may be provided at a portion where the music server 50 and the portable recording / reproducing device 70 are connected, and the connection can be detected by mechanical means.
[0101]
When the connection is confirmed, in the next step S41, it is determined whether or not the music data recorded and stored in the HDD 10 is requested to be moved to the portable recording / reproducing apparatus 70. For example, a list of compressed music data stored in the HDD 10 is displayed on the display unit 53, and a predetermined compressed music data is selected from the list display by a predetermined pointing device as the input unit 1 by the user. In addition, movement of the selected compressed music data to the portable recording / reproducing apparatus 70 is instructed.
[0102]
There are various ways of instructing movement. For example, a button for instructing movement is displayed on the display unit 53, and this button can be designated by a predetermined method. Further, for example, an icon indicating compressed music data is displayed, and this icon can be moved by a so-called drag and drop operation in which the icon is moved onto the icon indicating the mobile recording / reproducing device 70 of the moving destination. Of course, the movement may be instructed by operating a switch mechanism provided in the operation unit.
[0103]
If it is determined in step S41 that there is a request to move the compressed music data, the file size of the compressed music data designated for movement is checked in step S42. In the next step S43, the free capacity of the HDD 106 of the portable recording / reproducing apparatus 70 is checked. Then, the free space of the HDD 106 is compared with the file size of the compressed music data designated for movement checked in step S42. Based on the comparison result, it is determined whether or not the compressed music data designated for movement can be recorded in the HDD 106. If it is determined that recording is possible, the process proceeds to step S45, and the transfer of the compressed music data is started.
[0104]
On the other hand, if it is determined in step S43 that the HDD 106 of the portable recording / reproducing apparatus 70 has insufficient free space, the process proceeds to step S44. In step S44, the compressed music data already recorded on the HDD 106 is deleted so that the compressed music data designated for movement can be recorded on the HDD 106. Then, the process proceeds to step S45.
[0105]
The compressed music data is automatically deleted based on predetermined parameters of the compressed music data already recorded on the HDD 106. For example, in the portable recording / reproducing apparatus 70, it is conceivable that the number of times of reproduction is counted for each compressed music data recorded in the HDD 106, and the number of times of reproduction is deleted. It is also possible to delete the date recorded in the HDD 106 in order of oldest date.
[0106]
Furthermore, when automatically deleting, the compressed music data important for the user may be deleted. In order to prevent this, a warning can be displayed on the display unit 53 of the music server 50 or the LCD 120 of the portable recording / reproducing apparatus 70 and deleted after obtaining confirmation from the user. Furthermore, a list of compressed music data already recorded in the HDD 106 is displayed on the display unit 53 of the music server 50 or the LCD 120 of the portable recording / reproducing apparatus 70, and the user himself selects the compressed music data to be deleted. You can take a method.
[0107]
When the compressed music data for which movement has been designated is made recordable on the HDD 106 by the processing in steps S43 and S44 described above, the compression from the music server 50 to the portable recording / reproducing device 70 is performed in step S45. Transfer of music data is started. That is, the compressed music data read from the HDD 10 is supplied to the portable recording / reproducing apparatus 70 via the bus 40 and the interface 34. In the portable recording / reproducing device 70, the supplied compressed music data is recorded in the HDD 106 on the interface 35.
[0108]
The transferred compressed music data also exists in the HDD 10 on the music server 50 side as before the transfer. In this embodiment, reproduction of the corresponding compressed music data existing in the HDD 10 is prohibited (step S46). For example, a reproduction prohibition flag indicating reproduction prohibition is set for the compressed music data. Thereby, the corresponding compressed music data is virtually moved from the music server 50 to the portable recording / reproducing apparatus 70. Therefore, each piece of compressed music data is managed so that there is always only one, and illegal data duplication is prevented.
[0109]
In the next step S47, it is determined whether or not there is a request to move the next compressed music data. If it is desired to further move the compressed music data, the process returns to step S42. If there is no more data movement request, a series of movement processes are terminated.
[0110]
In the above description, it is described that one piece of compressed music data is moved in steps S42 to S46 in the flowchart of FIG. 9, but this is not limited to this example, and a plurality of pieces of compressed music data are moved together. You can also
[0111]
In the above description, the compressed music data that has been moved in the HDD 10 of the music server 50 that is the movement source in the process of step S46 has been described as being only prohibited from being reproduced. It is not limited to an example, and may be deleted.
[0112]
In the above description, the example in which the compressed music data is moved from the music server 50 to the portable recording / reproducing apparatus 70 has been described. However, the movement in the reverse direction, that is, the compressed music data recorded on the HDD 106 of the portable recording / reproducing apparatus 70 is described. Can be moved to the HDD 10 of the music server 50 according to the same process as the flowchart of FIG.
[0113]
At this time, the compressed music data moved from the music server 50 to the portable recording / reproducing apparatus 70 is moved again from the portable recording / reproducing apparatus 70 to the music server 50, so that the music server 50 reproduces the corresponding reproduction music flag. Is released. That is, the corresponding compressed music data can be played back again on the music server 50.
[0114]
By the way, in the present invention, when performing the above-mentioned movement, a unique identifier is assigned to each portable recording / reproducing apparatus 70 to which the music data is moved, and a unique identifier is also assigned to the music data. The music server 50 manages these identifiers. As a result, the music data is prevented from being moved or copied to an unauthorized terminal device, the copyright for the music data is protected, and the data destination is grasped.
[0115]
FIG. 10 shows an example of a device identifier management table in which identifiers of movement destination devices are recorded. Regardless of the music server 50 and the portable recording / reproducing apparatus 70, this device identifier management table is included in each device that is the source of movement. Registered in the device identifier management table is an identifier of a destination device that is permitted to exchange music data with itself.
[0116]
In addition, a nickname can be assigned to the destination device. The nickname can be input by the input unit 1 in the example of the music server 50. In this example, “mars” is assigned as a nickname to a device with an identifier “0010”, and “jupiter” is assigned to a device with an identifier “0020”. On the other hand, a device with the identifier “0030” is not given a nickname.
[0117]
On the other hand, each music data recorded in the music server 50 is given a unique music data identifier. Further, a movement flag indicating whether or not the music data has been moved is attached to each music data. The song data identifier can be acquired based on the data associated with the CD 55, for example, the CD number, which is obtained when the music data of the CD 55 is recorded in the HDD 10.
[0118]
FIG. 11 shows an example of a data management table in which song data identifiers and movement flags attached to each music data are managed. Regardless of the music server 50 and the portable recording / reproducing apparatus 70, this data management table is included in each device that is the source of movement. A unique music data identifier is assigned to each piece of music data.
The movement flag indicates whether or not the corresponding music data has been moved. If the movement flag is “1”, it indicates that the music data has been moved to the portable recording terminal 70. If the movement flag is “0”, the data has not been moved. Further, the music title may be assigned to each piece of music data.
[0119]
In the example of the music server 50, the music title can be input by the input unit 1. Also, if the CD 55 used to record the music data on the HDD 10 corresponds to CD text, the text data can be read and recorded on the HDD 10 for automatic registration. In addition, the song name is
It can also be obtained from the Internet server 60 via the communication line 61.
[0120]
Next, a first embodiment of the present invention will be described. In this first form, each device has only information on the destination of each music data. Each device, that is, each of the music server 50 and the portable recording / reproducing apparatus 70 has a data movement destination management table, an example of which is shown in FIG. The data movement destination management table is composed of a set of records including song data identifiers, movement destination device identifiers, and movement times.
[0121]
The data migration destination management table is updated in the following two cases. That is,
(1) When music data is moved between devices
(2) When the data movement destination management tables of both connected devices are collated when connecting each device
In these cases, the data migration destination management table is updated.
[0122]
First, the update accompanying the movement of the music data (1) will be described with reference to the flowchart shown in FIG. FIG. 13 shows a process in a case where the movement source device and the movement destination device are connected and the music data M recorded in the movement source device is moved to the movement destination device. FIG. 13A shows processing at the movement source device, and FIG. 13B shows processing at the movement destination device. The source device and the destination device may be either the music server 50 or the portable recording / reproducing device 70, respectively.
[0123]
First, the source device and the destination device are connected and the device identifiers are exchanged (steps S50 and S60). In the movement source device, predetermined music data M is selected by the user, and movement of the selected music data M to the movement destination device is instructed (step S51). In step S52, the identifier of the destination device is confirmed based on the device identifier management table.
[0124]
If the device identifier of the connected destination device is not in the device identifier management table of the source device (step S53), the process proceeds to step S56, and a movement non-permission notification is transmitted to the destination device. Then, it is notified that the music data M cannot be moved.
[0125]
On the other hand, if it is determined in step S53 that the device identifier of the connected destination device exists in the device identifier management table of the source device, the process proceeds to step S54. In step S54, the flag is checked based on the data management table of the source device. If the flag is “1” and the data has been moved to another device, the process proceeds to step S56, and a movement non-permission notification is issued to the destination device. On the other hand, if the flag is “0”, it is determined that the music data M can be moved, and the process proceeds to step S57.
[0126]
In step S57, an entry is created in the data migration destination management table in the migration source device, and a record of music data M is newly created. In this record, the music data identifier of the music data M, the device identifier of the movement destination device, and the movement time are recorded. If an entry for music data M already exists, the entry is overwritten.
[0127]
After the entry of the music data M in the data destination management table is created, the music data M is transmitted from the source device to the destination device (step S58). When the transmission is completed, in the next step S59, the flag of the music data M in the data management table is changed from “0” to “1”, and the flag is set. Thereby, a series of processes in the source device is completed.
[0128]
On the other hand, in the destination device, after exchanging the device identifier with the source device in step S60, the destination device waits for reception until some data is sent from the source device (step S61). When data from the source device is received, the content of the received data is determined. If the data content is a movement non-permission notification in step S56 in the process of the source device (step S63), the process in the destination device is terminated.
[0129]
On the other hand, if the data content is the music data M in step S58 in the process of the source device (step S64), the music data M is received and recorded. Then, the process proceeds to the next step S65. If a record of the music data M already exists in the data management table, the flag is changed from “1” to “0” and the flag is lowered. If there is no record of music data M in the data management table, a record of music data M is newly created and the flag is set to “0”.
[0130]
As described above, the same processing is performed even if any of the destination device and the source device is the music server 50. However, when the destination device is the music server 50, that is, when the music data M is migrated to the music server 50, the record corresponding to the music data M in the data management table of the source device is deleted. Also good.
[0131]
Next, update by collation of the data movement destination management table (2) will be described. First, the update of the data movement destination management table will be schematically described with reference to FIG. FIG. 14A is before update, and FIG. 14B is a data migration destination management table after update. In each of FIG. 14A and FIG. 14B, a table of movement source devices is shown on the left side, and a table of movement destination devices is shown on the right side.
[0132]
For example, when two portable recording / reproducing apparatuses 70 are connected to each other, first, the data movement destination management tables are checked with each other to search for a data identifier included in both. In the example of FIG. 14A, the data identifier [1108] is common to the two devices 70 connected to each other. If there is an identifier that both have in this way, the movement times in the record of the corresponding identifier of each of the connected devices 70 are compared with each other. As a result of the comparison, the content of the record with the older time is rewritten to the content of the new record. This process is repeated until there is no matching data identifier in both of the two connected devices 70.
[0133]
The update by collation of the data movement destination management table will be described in more detail using the flowcharts of FIGS. 15 and 16. FIG. 15 and FIG. 16 are flowcharts showing continuous processing, and symbols “A”, “B”, and “C” in the drawings indicate that the processing shifts to symbols corresponding to each other. 15A and 16A show processing of the movement source device, and FIGS. 15B and 16B show processing of the movement destination device. The source device and the destination device may be either the music server 50 or the portable recording / reproducing device 70, respectively.
[0134]
For example, when the devices are connected to each other, for example after music data transfer processing, the data transfer destination management table of each device is collated and updated. And collation is performed by comparing both records. First, the source device and the destination device are connected, and the device identifiers are exchanged (step S70 and step S100). That is, it transmits its own device identifier to each other and receives the device identifier transmitted from the other party. Then, in the movement source device and the movement destination device, it is confirmed that the received device identifier of the other party is registered in its own device identifier management table (step S71 and step S101). If the device identifier can be confirmed, the source device waits to receive data from the destination device (step S72).
[0135]
On the other hand, in the destination device, the record counter k is set to k = 1 (step S102). The record counter k is a counter corresponding to the record in the data movement destination management table. In the next steps S103, S104, S105, and S106, while incrementing the record counter k, the records of the data movement destination management table are retrieved one by one and transmitted from the movement destination device to the movement source device.
[0136]
One record includes a data identifier, a movement destination device identifier, and a movement time, as described above with reference to FIG. Therefore, the data identifier, the destination device identifier, and the movement time of the kth record are set to Rk. dataID, Rk. id, and Rk. As time, the data of the kth record can be expressed as (Rk.dataID, Rk.id, Rk.time).
[0137]
That is, the kth record is extracted in step S103, and the kth record is transmitted to the source device in step S104. In step S105, it is determined whether or not the transmitted kth record is the last record. If it is determined that the record is not the last record, the process proceeds to step S106, the record counter k is incremented by 1, and the process of step S103 is performed again. When the extraction of the last record is completed, an end notification is transmitted to the source device in step S107.
[0138]
On the other hand, the source device waits for communication from the destination device in the reception waiting state in step S72. When communication from the destination device is received, the communication content is determined in step S73. If the communication content is a record in the data migration destination management table from the migration destination device, the kth record is received in step S74, and in the next step S75, the received kth record is assigned to the array P [n] ( n = 1, 2, 3,... The storage process of the data movement destination management table in the data array [] is repeated until an end notification is received from the movement destination device.
[0139]
On the other hand, if it is determined in step S73 that the communication content from the destination device is the end notification transmitted in step S107, the end notification is received in step S76, and the process proceeds to the next step S77. In steps S77, S78, and S79, the first element P [1] of the array P [] is extracted. That is, the counter of the array P [] is set to n = 1 in step S77, and the nth (in this case, first) element P [n] is extracted from the array P [] in step S78.
[0140]
In the next step S79, the record counter m in the data migration destination management table of the migration source device is set to m = 1. Moving to FIG. 16, in steps S80, S81, S82, and S83, a record having a data identifier that matches the data identifier (P [n] .dataID) of element P [n] is the data migration destination management of the migration source device. Searched from the table.
[0141]
That is, in step S80, the mth record Rm is extracted from the data migration destination management table of the migration source device. Then, in the next step S81, it is compared whether or not the dataIDs match in the record Rm and the element P [n]. If they do not match, it is determined in step S82 whether the record Rm is the last record. If it is not the last record, the record counter m is incremented by 1 in step S83, It returns to step S80 again.
[0142]
If it is determined in step S82 that the record Rm is the last record, the process proceeds to step S89, and it is determined whether the element P [n] is the last element. If it is the last element, the process proceeds to step S90, an end notification is transmitted to the destination device, and a series of processes in the source device is ended. If it is determined in step S89 that the element P [n] is not the last element, the process increments the counter n of the array P [] by 1 in step S91 of FIG. 15, and the process returns to step S78 again.
[0143]
On the other hand, if it is determined in step S81 that the data IDs of the record Rm and the element P [n] match, the process proceeds to step S84.
In step S84, the movement time (Rm.time) recorded in the record Rm in the movement source device is compared with the movement time (Pn.time) recorded in the element P [n] in the movement destination device. .
[0144]
If it is determined in step S84 that the movement time (Rm.time) and the movement time (Pn.time) are the same, the process proceeds to step S89, and the next element is examined. If it is determined in step S84 that the movement time (Rm.time) recorded in the record Rm is newer than the movement time (Pn.time), the process proceeds to step S85, and the movement destination device is checked. A move destination device update request is transmitted, and a record Rm to be updated is transmitted. Then, the process proceeds to step S89, and the next element is examined.
[0145]
On the other hand, if it is determined in step S84 that the latest movement information recorded in the record Rm is older, in step S86, the element P [n]. A request is transmitted to the movement destination device to transmit the movement destination information of the data indicated by the dataID. In step S112, which will be described later, this transmission request is received by the movement destination device. In step S113, the movement destination device sends an element P [n]. A record Rk corresponding to dataID is transmitted.
[0146]
By receiving this transmitted record Rk at the source device, the element P [n]. The movement destination information of dataID is obtained, and the movement destination and movement time information of the record Rm are rewritten in the next step S88. Then, the process proceeds to step S89, and the next element is examined.
[0147]
On the other hand, as described above, in the movement destination device, after the completion notification is transmitted to the movement source device in step S107 in FIG. 15 assuming that all records of the data movement destination management table have been transmitted, In step S108, communication from the source device is awaited. Then, when communication from the source device is received, the content is determined in step S109.
[0148]
If the communication content is an end notification in step S90 described above, the process proceeds to step S114, and it is received that the process in the movement source device is completed, and a series of processing in the movement destination device is terminated.
[0149]
On the other hand, in step S109, if the communication content is the destination information update notification in step S85 described above (step S110), the record Rm transmitted together with the notification is received, and the process proceeds to step S111. In step S111, based on the received record Rm, in the data destination management table of the destination device, Rm. dataID = Rk. The record Rk that satisfies dataID is rewritten. Then, the process returns to step S108, and again waits for reception of communication from the source device.
[0150]
In step S109, if the communication content is a destination information transmission request in step S86 described above, element P [n]. A record Rk corresponding to dataID is transmitted. Then, the process returns to step S108, and again waits for reception of communication from the source device.
[0151]
Note that the same processing is performed when either the destination device or the source device is the music server 50. Further, the present invention is not limited to this, and the music server 50 may determine in advance that the operation of the movement source device is performed. In this case, the destination device connected to the music server 50 receives the destination information transmission request in step S112 and transmits the record Rk in the data destination management table of the destination device (step S113). , Rk. If the destination device does not have the right to use the data indicated by dataID, the record Rk may be deleted from the data destination management table of the destination device.
[0152]
Whether the ownership is present or not is determined in the destination device by referring to the Rk. This can be confirmed by examining the flag of the record having the data identifier that matches the dataID.
[0153]
FIG. 17 shows an example of the structure of music data that can be applied to such processing. A header 300 is attached to the music data body. The header includes a header 302 that is updated as the data moves, and a header 303 that does not change as the data moves. The header 302 includes a data ID 304 of the music data, a counter 305 storing the number of times of data movement, a time of movement of the data, and device IDs 306, 306, 306,. The movement time and the movement destination device ID 306 are additionally recorded each time this data is moved to indicate the movement route.
[0154]
Next, the display on the display unit 53 of the music server 50 of the movement destination of each music data based on the update of the data movement destination management table described above will be described. FIG. 18 shows an example of a music list window 310 that is displayed on the display unit 53 of the music server 50 and shows the destination of the music data. The music list window 310 is displayed on the music server 50 by a predetermined operation.
[0155]
The window 310 includes a song name display / selection unit 311, a movement mark display unit 312 that indicates whether or not the song data has moved to the terminal, and a destination terminal name display unit that displays the name of the terminal to which the song data has moved. 313 and a movement time display unit 314 that displays the time at which the song data has moved to the terminal indicated by the movement destination terminal name display unit 313. Also, in the window 310, the song name display / selection unit 311 can display all song names managed by the server by a scroll bar 316 and the like, and can select a specific song name according to a user instruction. Yes. The user can give these instructions using the operation unit of the music server 50 or the remote commander.
[0156]
In the music server 50, based on its own data management table, song names Mn (n = 1, 2,...) Corresponding to all song data identifiers Midn (n = 1, 2,...) Registered in the music server 50. ..) is displayed on the song name display / selection unit 311. Further, when the flag of the data identifier Midk (kε {1, 2,...}) Is set in the data management table, the movement mark 315 is displayed in the portion corresponding to the song name Mk of the movement mark display unit 312. Is displayed.
[0157]
Furthermore, the data movement destination management table is referenced, and the movement destination device (Rm.id) and movement time (Rm.time) are extracted from the record Rm (Midk = Rm.dataID) having the same identifier as the data identifier Midk. It is. Then, the extracted destination device (Rm.id) and the movement time (Rm.time) are respectively displayed in portions corresponding to the song name Mk in the destination terminal name display unit 313 and the movement time display unit 314. The Here, (mε {1, 2,...}).
[0158]
Furthermore, in this embodiment, the music data moved to each destination device can be displayed for each terminal. FIG. 19 shows an example of this display. FIG. 19A is an example of a destination device list window 320 that shows a list of destination devices, and FIG. 19B is an example of a song list window 330 by destination device that shows moved music data in a list for each destination device. It is.
[0159]
A destination device list window 320 shown in FIG. 19A displays all destination devices managed by the music server 50, and allows a specific destination device to be selected according to a user instruction.
[0160]
The destination device-specific song list window 330 shown in FIG. 19B has a destination device name display unit 331, a song name display unit 332, and a movement time display unit 333. The song name display unit 332 displays a list of all song names of music data that has been moved to the destination device displayed in the destination device name display unit 331. The movement time display unit 333 displays the time of movement to the movement destination device displayed in the movement destination device display unit 331 of each music data displayed in the song name display unit 332.
[0161]
If the user does not instruct anything, the movement destination device list window 320 is displayed on the display unit 53 of the music server 50. This is the default display. When the user designates a specific destination device name, for example, “jupiter” from the destination device names displayed in the destination device list window 320, the destination device-specific song list window 330 of the destination device is opened. .
[0162]
The destination device list window 320 refers to its destination device identifier management table in the music server 50, and displays names of all destination devices registered in this table, that is, nicknames.
[0163]
If the user selects a destination device in the destination device list window 320 and instructs display of the destination device-specific song list window 330, the music server 50 displays the destination device list on the song name display unit 332. The destination device name Tn (nε {1, 2,...}) Designated in the window 320 is displayed.
[0164]
Next, the music server 50 refers to its own data movement destination management table. And the record (Mm = 1, 2,...) Of the destination device identifier (Rm.id) of each record Rm matches the device identifier Tid of the destination device name displayed in the song name display unit 332 ( Rk (kε {1, 2,...}, Rk.id = Tid) is examined, and the music data identifier Rk.dataID and the movement time (Rk.time) are extracted for the records that match. The extracted music data identifier and moving time are displayed on the music name display unit 332 and the moving time display unit 333. At this time, for the music data identifier Rk.dataID, the data management table is referred to and the corresponding music name is displayed. Mn (nε {1, 2,...}, Midn = Rk.dataID) is displayed.
[0165]
Next, a second embodiment of the present invention will be described. In this second form, each device has a destination of each data and route information to that destination. Each device, that is, each of the music server 50 and the portable recording / reproducing apparatus 70 has a route information map 400, an example of which is shown in FIG.
[0166]
The route information map 400 is a collection of route information entries 401 corresponding to each music data. Each route information entry 401 includes a music data identifier 402, a movement counter 403, and a movement history 404. Each route information entry 401 is updated as appropriate. Here, the movement counter 403 represents the total number of movement histories 404. In the movement history 404, the movement time and the movement destination device identifier are recorded in the movement order.
[0167]
Each device updates its route information map 400.
(1) Update of route information entry 401 accompanying movement of music data between destination devices
(2) Update of the route information entry 401 performed by checking the route information map 400 of both connected devices when the destination devices are connected
There are these two cases. Note that one of the destination devices may be the music server 50. Hereinafter, each case will be described in order.
[0168]
First, (1) updating of the route information entry 401 accompanying the movement of music data will be described. FIG. 21 is a flowchart showing a process in the case where the destination device and the source device are connected and the music data M in the destination device is moved to the source device. FIG. 21A shows processing at the movement source device, and FIG. 21B shows processing at the movement destination device. The source device and the destination device may be either the music server 50 or the portable recording / reproducing device 70, respectively.
[0169]
First, the source device and the destination device are connected, and the device identifiers are exchanged (steps S200 and S220). In the movement source device, predetermined music data M is selected by the user, and movement of the selected music data M to the movement destination device is instructed (step S201). In step S202, the identifier of the destination device is confirmed based on the device identifier management table.
[0170]
If the device identifier of the connected destination device is not in the device identifier management table of the source device (step S204), the process proceeds to step S206, and a movement non-permission notification is transmitted to the destination device. Then, it is notified that the music data M cannot be moved.
[0171]
On the other hand, if it is determined in step S203 that the device identifier of the connected destination device exists in the device identifier management table of the source device, the process proceeds to step S204. In step S204, the flag is checked based on the data management table of the source device. If the flag is “1” and the data has been moved to another device (step S205), the process proceeds to step S206, and a movement non-permission notification is sent to the destination device. Is issued. On the other hand, if the flag is “0”, it is determined that the music data M can be moved, and the process proceeds to step S207.
[0172]
Next, in step S207, the data identifier Mid of the data M in the data management table of the destination device and each route information entry (En (n = {1, 2,...) In the route information map 400 of the destination device. }) Is sequentially compared with the data identifier (En.dataID (n = {1, 2,...}), And the path information entry Em (mε {1, 2,...) Corresponding to the data M. .., Em.dataID = Mid) If a route information entry Em corresponding to the data M is found in the route information map 400 of the movement destination device, the device identifier and movement time of the movement source device are route information. The entry Em is added to the movement history (Em'history), and the movement counter (Em.counter) is incremented by one.
[0173]
The updated path information entry Em is stored, for example, in the header 302 of the music data shown in FIG. 17 and transmitted to the destination device (step S208). Further, since the movement source device has no right to use the music data M, a flag of the record of the data M in the data management table of the movement source device is set (309).
[0174]
On the other hand, after the identifier exchange in step S220, the destination device is placed in a reception waiting state and waits for transmission from the source device (step S221). If the destination device receives the data M together with the header (step S224), the flag in the record of the data M in the data management table of the destination device is lowered in the next step S225. If there is no record of data M, a new record is created and the flag is lowered.
[0175]
Further, in the next step S226, the route information entry Ek (kε {1, 2,...}, Ek.dataID = Em.dataID corresponding to the data M in the route information map 400 ′ of the movement destination device). ) Is replaced with the contents of the header 302 of the received data M. At this time, if there is no entry corresponding to the data M in the route information map 400 ′ of the movement destination device, a new entry is created and the route information in the received header 302 is recorded.
[0176]
In the above description, the same applies even if either the destination device or the source device is the music server 50. However, when the destination device is the music server 50 (that is, when the data M is moved to the music server 50), the route information entry Em of the source device corresponding to the data M may be deleted. If the movement source device is the music server 50 (that is, when the data M is moved from the music server 50), the route of the movement destination device (that is, the music server 50) corresponding to the data M in step S207 described above. When the movement history is recorded in the information entry Em, the movement history so far may be once deleted and newly recorded.
[0177]
Next, (2) updating of the route information entry 401 performed by comparing the route information maps 400 of both connected devices when the destination devices are connected will be described. The route information map 400 of each device is collated and updated when the destination devices (or the destination device and the music server 50) are connected to each other, for example, after movement of music data. The collation is performed by comparing both the path information entries 401 with each other.
[0178]
FIG. 22 and FIG. 23 are flowcharts showing processing when the destination device and the source device are connected and the route information map 400 is collated and updated. FIG. 22 and FIG. 23 are flowcharts showing continuous processing, and symbols “A”, “B”, and “C” in the drawings indicate that the processing shifts to symbols corresponding to each other. 22A and 23A show the processing of the source device, and FIGS. 22B and 23B show the processing of the destination device. The source device and the destination device may be either the music server 50 or the portable recording / reproducing device 70, respectively.
[0179]
First, in step S300 and step S350, the destination device and the source device are connected, their own device identifiers are transmitted to each other, and the counterpart device identifier is received. Then, in each of the next step S301 and step S351, it is confirmed whether or not the received counterpart device identifier is registered in its own device identifier management table. If it can be confirmed, the source device is put in a state of waiting to receive data from the destination device.
[0180]
On the other hand, in the destination device, the counter k of the route information entry is set to k = 1 in step S352. In steps S353, S354, S355, and S356, the k-th path information entry Ek is extracted from the path information map 400 ′ of the destination device while incrementing the counter k by 1.
[0181]
In this process, in step S354, the data identifier (Ek.dataID) recorded in the extracted entry Ek and the movement time of the movement history corresponding to the movement counter (Ek.counter) recorded in the entry Ek (( E1.counter) th E1's time) is transmitted to the source device. The travel time ((E1.counter) th E1's time) is the latest travel history recorded last.
[0182]
The processes in steps S353, S354, S355, and S356 are repeated until the extracted entry Ek is determined to be the last entry in step S355. When the last entry Ek is extracted, the process proceeds to step S357, and an end notification is transmitted from the movement destination device to the movement source device. When the end notification is transmitted, the destination device is placed in a reception waiting state in step S358 of FIG.
[0183]
On the other hand, in the movement source device, when communication from the movement destination device is received, the communication content is determined in step S303. If the communication content is the content transmitted in step S354, the communication is received in step S304, and the content of the entry Ek received in the next step S305 is stored in the array Q []. This array Q [] is temporarily prepared. Then, the process is repeated again from step S303, and the contents of the received entry Ek are sequentially stored in the array Q [n] (n = 1, 2,...).
[0184]
On the other hand, if it is determined in step S303 that the communication content is the end notification transmitted in step S357, the communication is received in step S306, and the process proceeds to the next step S307. In step S307, the counter n of the array Q [] is set to 1, the element of the array Q [n] is compared with the path information entry Em of the source device, and the path matches the element of the array Q [n]. It is checked whether there is an information entry Em. Based on the result, the movement history of the route information entry Em of the source device is rewritten, and the data identifier (Q [n] .dataID) of the array Q [n] between the source device and the destination device. The exchange of history is performed.
[0185]
That is, in the destination device, the route information entry Ek is extracted in step S353. In the next step S354, Ek. The data ID and the latest movement history time are transmitted to the movement source device in the reception waiting state. In the source device, this information is received in step S304, the information received in step S305 is stored in the array Q [], and the next reception is awaited.
[0186]
On the other hand, in the destination device, it is determined whether or not the entry Ek is the last entry in step S355, and if it is not the last, the counter k is incremented by 1 (step S356), and the last entry Ek is extracted. The process is repeated until it is sent. When the last entry Ek is transmitted, an end notification is transmitted to the source device in step S357. Then, the destination device is placed in a reception waiting state (step S358).
[0187]
On the other hand, if it is determined in step S303 that the communication content from the destination device is the end notification transmitted in step S357 described above, the end notification is received in step S306, and the process proceeds to the next step S307. In steps S307, S308, and S309, the first element Q [1] of the array Q [] is extracted. That is, in step S307, the counter of the array Q [] is set to n = 1, and in step S308, the nth (in this case, first) element Q [n] is extracted from the array Q [].
[0188]
In the next step S309, the record counter n of the data migration destination management table of the migration source device is set to n = 1. Shifting to FIG. 23, in steps S310, S311, S312, and S313, a record having a data identifier that matches the data identifier (Q [n] .dataID) of element Q [n] is the data migration destination management of the migration source device. Searched from the table.
[0189]
That is, in step S310, the mth entry Em is extracted from the data migration destination management table of the migration source device. Then, in the next step S311, it is compared whether the entry Em and the element Q [n] have the same dataID. If they do not match, it is determined in step S312 whether the entry Em is the last record. If it is not the last record, the record counter m is incremented by 1 in step S313, The process returns again to step S310.
[0190]
If it is determined in step S312 that the entry Em is the last record, the process proceeds to step S319, and it is determined whether the element Q [n] is the last element. If it is the last element, the process proceeds to step S321, an end notification is transmitted to the destination device, and a series of processing in the source device is ended. If it is determined in step S319 that the element Q [n] is not the last element, the process increments the counter n of the array Q [] by 1 in step S320 of FIG. 15, and the process returns to step S308 again.
[0191]
On the other hand, if it is determined in step S311 that the data IDs of the entry Em and the element Q [n] match, the process proceeds to step S314. In step S314, the movement time (Em.time) recorded in the entry Em in the movement source device is compared with the movement time (Qn.time) recorded in the element Q [n] in the movement destination device. .
[0192]
If it is determined in step S314 that the movement time (Em.time) and the movement time (Qn.time) are the same, the process proceeds to step S319, and the next element is examined. If it is determined in step S314 that the movement time (Em.time) recorded in the entry Em is newer than the movement time (Qn.time), the process proceeds to step S315, and the movement destination device is checked. A move destination device update request is transmitted and an entry Em to be updated is transmitted. Then, the process proceeds to step S319, and the next element is examined.
[0193]
On the other hand, if it is determined in step S314 that the latest movement information recorded in the entry Em is older, in step S316, the element Q [n]. A request is transmitted to the movement destination device to transmit a history of data indicated by dataID. In step S362, which will be described later, this transmission request is received by the movement destination device. In step S363, the movement destination device transmits the element Q [n]. An entry Em corresponding to dataID is transmitted.
[0194]
By receiving this transmitted entry Em at the source device, the element Q [n]. A history of dataID is obtained, and in the next step S318, the movement destination and movement time information of the entry Em are rewritten. Then, the process proceeds to step S319, and the next element is examined.
[0195]
On the other hand, as described above, in the movement destination device, after all the records of the data movement destination management table have been transmitted to the movement source device in step S357 of FIG. In step S358, communication from the source device is awaited. Then, when communication from the source device is received, the contents are determined in step S359.
[0196]
If the communication content is an end notification in step S321 described above, the process proceeds to step S364, where it is received that the process in the source device has ended, and a series of processes in the destination device is ended.
[0197]
On the other hand, if the communication content is the history update notification in step S315 described above in step S359 (step S360), the entry Em transmitted with the notification is received, and the process proceeds to step S361. In step S361, based on the received entry Em, in the data destination management table of the destination device, Em. dataID = Ek. The entry Em that satisfies dataID is rewritten. Then, the process returns to step S358, and again waits for reception of communication from the source device.
[0198]
In step S359, if the communication content is a history transmission request in step S316 described above, element Q [n]. An entry Em corresponding to dataID is transmitted. Then, the process returns to step S358, and again waits for reception of communication from the source device.
[0199]
Note that the same processing is performed when either the destination device or the source device is the music server 50. Further, the present invention is not limited to this, and the music server 50 may determine in advance that the operation of the movement source device is performed. In this case, the destination device connected to the music server 50 receives the history transmission request in step S362 and transmits the entry Em in the data destination management table of the destination device (step S363). Ek. If the transfer destination device does not have the right to use the data indicated by dataID, the entry Em may be deleted from the data transfer destination management table of the transfer destination device.
[0200]
In order to confirm the presence or absence of ownership, the destination device is Ek. What is necessary is just to look at the flag of the record having the data identifier that matches the dataID.
[0201]
Finally, the contents and method of displaying the route and transfer destination of each data on the display device of the music server 50 based on the route information map 400 will be described. In this display, the music list window 310 and the movement destination device list window 320 described above with reference to FIGS. 18 and 19A are used, a history window whose example is shown in FIG. 24, and an example which is shown in FIG. A song list window for each source device is used. In the following description, the song list window and the movement source device list window are the same as described above, and detailed description thereof will be omitted.
[0202]
The history window 500 has a song name display portion 501 and a history display portion 502. The history display unit 502 displays the movement history of the song data displayed on the song name display unit 501 in the order of movement, and includes a destination device name display selection unit 503 and a movement time display unit 504. The destination device name display selection unit 503 can select a specific source device according to a user instruction. The movement time display unit 504 displays the time when the data displayed on the song name display unit 501 is moved with respect to the movement source device displayed by the movement destination device name display selection unit 503.
[0203]
The destination device-specific song list window 510 has a destination device name display unit 511, a song name display unit 512, and a movement time display unit 513. The song name display unit 512 displays all the songs that have been moved to the source device displayed in the destination device name display unit 511. It should be noted that not only simply being displayed, but also a specific song name may be selected according to a user instruction. In this case, the destination device-specific song list window 510 has a history button 514, and the song data selected by the user when the user selects a specific song name in the song name display section 512 and then presses the history button 514. The history window 500 is opened. The movement time display unit 513 displays the time at which each piece of music data displayed on the song name display unit 512 is moved to the movement source device displayed on the movement source device display unit 511.
[0204]
Next, a method for displaying the route of each music data and the destination of movement using the above-described windows will be described. If the user does not instruct anything, the music list window 310 and the movement source device list window 501 are displayed on the display unit 53 of the music server 50 as default displays.
[0205]
Among the songs displayed on the song name display / selection unit 311 of the song list window 310 by the user, a specific song that has been moved to the movement source device (a song having a movement mark 315 on the movement mark display unit 312), for example, When the song indicated by “title5” is selected and then the movement mark 315 of the movement mark display unit 312 in the same row is clicked, the history window 500 of the corresponding song opens.
[0206]
The user selects a specific source device name from the source device names displayed in the source device list window 320. Then, a song list window 510 for each destination device corresponding to the destination device is opened.
[0207]
Not limited to this, when the user selects a specific source device name, for example, “jupiter” from the source device names displayed in the destination device name display selection unit 503 of the history window 500, It is also possible to open the song list window 510 by destination device of the selected source device. Further, when the user selects a specific song name, for example, a song indicated by “title5”, from the source device names displayed in the song name display section 503 of the destination device-specific song list window 510, it corresponds. The music data history window 500 may be opened.
[0208]
A method of displaying each screen will be described. First, the song list window 310 will be described. The music server 50 refers to its own data management table. Then, the song name Mn (n = 1, 2,...) Corresponding to all the registered song data identifiers Midn (n = 1, 2,...) Are displayed as the song name display / selection unit 311 in the song list window 310. Is displayed.
[0209]
Further, the flag of the data identifier Midk (kε {1, 2,...}) In the data management table is checked. If the flag is set, the song name in the movement mark display unit 312 of the song list window 310 is displayed. A movement mark 315 is displayed for the portion corresponding to Mk.
[0210]
Furthermore, the latest movement of the route information entry Em (mε {1, 2,...}) (Midk = Em.dataID) having the same identifier as the data identifier Midk is referred to at this time. From the history 404, the movement source device ((Em.counter) th Em's id) and the movement time ((Em.counter) th Em's time) are extracted. And it displays on the part corresponding to the music title Mk in the movement destination apparatus name display part 313 and the movement time display part 314, respectively.
[0211]
Next, the movement source device list window 320 will be described. The music server 50 refers to its own device identifier management table and displays names of all registered devices (nickname).
[0212]
Next, the history window 500 will be described. The history window 500 is opened when the movement mark 315 of the music list window 310 is designated by the user. At this time, the song title display unit 501 displays the song title Mn (nε {1, 2,...}) Designated by the user in the song list window 310.
[0213]
Further, in the music server 50, the route information map 400 of its own is referred to, and the route information entry Em (mε {1, 2,...}, Midk = Em.dataID) having the same identifier as the identifier Midn of the music title Mn. The movement history 404) is displayed on the history display section 502 in order from the newest one.
[0214]
Finally, the destination device-specific song list window 510 will be described. The destination device-specific song list window 510 is opened when the source device name is selected and specified in the source device list window 320. At this time, the music name display unit 512 displays the source device name Tn (nε {1, 2,...}) Selected by the user in the source device list window 320.
[0215]
In addition, the music server 50 refers to its own information route map 400, and the movement source device identifier ((Em.counter) of the latest movement history 404 of each route information entry Em (m = 1, 2,...). th Em's id) and the entry (Ek (kε {1, 2,...}) in which the device identifier Tid of the source device displayed in the song name display unit 512 matches are examined. The song data identifier Ek.dataID and the movement time ((Ek.counter) th Ek'time) are taken out and displayed on the song name display section 512 and the movement time display section 513. However, the song data identifier Ek.dataID Refers to the data management table and displays the corresponding song title Mn (nε {1, 2,...}, Midn = Ek.dataID). That.
[0216]
In the above description, the source device and the destination device are fixedly described, but this is not limited to this example. In other words, since the source device or the destination device is in a symmetrical relationship with each other, either device may operate as the source device, and either device may operate as the destination device. The same applies to devices managed by the music server 50, for example.
[0217]
However, in actual operation, it is necessary to determine which is the movement destination and which is the movement source between the connected devices. For this purpose, for example, when the partner device identifiers are exchanged with each other, the partner device identifier is compared with the own device identifier. If the permutation of the device identifier is smaller than that of the other device, the device may be the source device, and if the device identifier is larger, the device may be the destination device. Such an arrangement is not limited to this example, and can be performed in various ways.
[0218]
In the above description, the data movement destination management table is created for managing the movement destinations of the music data. This is not limited to this example. For example, in the music server 50, for example, a movement data management table as shown in FIG. 26 may be created. This movement data management table is composed of a set of records that can be distinguished by device identifiers. In each record, the data identifier of the music data moving to the device indicated by the device identifier and the moving time of the data are paired and recorded. These data identifier and movement time can be extracted from the data movement destination management table. For example, when displaying by device using this movement data management table, the data moved to each device is rearranged and displayed in a predetermined order such as the order of movement time based on the contents of the table.
[0219]
【The invention's effect】
As described above, according to the present invention, there is an effect that each device can grasp a movement destination of music data and a movement route.
[0220]
In addition, according to the present invention, not only music data is moved between the music server and the portable recording / reproducing device, but also each device, particularly the music server, is able to move music data between portable recording / reproducing devices. There is an effect that it is possible to grasp the movement destination and movement route of each data.
[Brief description of the drawings]
FIG. 1 is a schematic diagram schematically showing a music server and a system using the music server according to the present invention.
FIG. 2 is a block diagram showing an example of the configuration of a music server.
FIG. 3 is a diagram schematically showing a signal flow until music data read by a CD-ROM drive is recorded on an HDD.
FIG. 4 is a diagram schematically showing a signal flow until compressed music data read from an HDD is reproduced and derived to a terminal.
FIG. 5 is a block diagram showing an example of the configuration of a portable recording / reproducing apparatus.
FIG. 6 is a block diagram showing another example of the portable recording / reproducing apparatus.
FIG. 7 is a flowchart of an example of processing when recording music data of a CD on the HDD in the music server.
FIG. 8 is a flowchart showing an example of billing processing when high-speed recording of CD music data on the HDD is performed.
FIG. 9 is a flowchart of an example of a process of moving music data according to the present invention.
FIG. 10 is a schematic diagram illustrating an example of a device identifier management table in which identifiers of movement destination devices are recorded.
FIG. 11 is a schematic diagram illustrating an example of a data management table in which music data identifiers and movement flags attached to music data are managed.
FIG. 12 is a schematic diagram illustrating an example of a data movement destination management table configured by a set of records including song data identifiers, movement destination device identifiers, and movement times;
FIG. 13 is a flowchart illustrating an example of processing when a source device and a destination device are connected and music data M recorded in the source device is moved to the destination device.
FIG. 14 is a schematic diagram for explaining updating of a data movement destination management table;
FIG. 15 is a flowchart for explaining update by collation of a data movement destination management table;
FIG. 16 is a flowchart for explaining update by collation of a data movement destination management table;
FIG. 17 is a schematic diagram showing an example of the structure of music data applicable to this embodiment.
FIG. 18 is a schematic diagram illustrating an example of a music list window displayed on the music server and indicating a destination of music data.
FIG. 19 is a schematic diagram illustrating an example in which music data moved to each destination device is displayed for each terminal.
FIG. 20 is a schematic diagram illustrating an example of a structure of a route information map.
FIG. 21 is a flowchart illustrating an example of processing when a destination device and a source device are connected and music data M in the destination device is moved to the source device.
FIG. 22 is a flowchart showing an example of processing when a destination device and a source device are connected and the mutual route information maps are collated and updated.
FIG. 23 is a flowchart illustrating an example of processing performed when a destination device and a source device are connected and a mutual route information map is collated and updated.
FIG. 24 is a schematic diagram illustrating an example of a history window for displaying a movement history of music data.
FIG. 25 is a schematic diagram illustrating an example of a song list window for each source device for displaying a list of source devices for music data;
FIG. 26 is a schematic diagram illustrating an example of a movement data management table.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Input means of music server, 8 ... CPU of music server, 9 ... CD-ROM drive, 10 ... Hard disk drive of music server, 11 ... DRAM as buffer memory of music server , 12 ... Music server compression encoder, 19 ... Communication line, 20 ... Modem, 21 ... Music server compression decoder, 26 ... Music server LCD, 34, 35 ... Interface 40 ... Bus, 50 ... Music server, 55 ... CD, 60 ... Internet server, 70 ... Portable recording / reproducing apparatus, 106 ... Hard disk drive or flash RAM of portable recording / reproducing apparatus 107 Buffer memory of portable recording / reproducing apparatus DRAM, 108... Compression encoder of portable recording / reproducing apparatus, 115... Compression decoder of portable recording / reproducing apparatus, 120... LCD of portable recording / reproducing apparatus, 130. 200: Switch circuit

Claims (10)

First and second electronic devices that store data and reproduce the stored data;
Copy means for moving or copying the data stored in the first electronic device to at least the second electronic device;
When the data stored in the first electronic device is moved or copied to a predetermined other electronic device, the data is relative to the predetermined data moved or copied to the first electronic device. A recording system characterized by storing an identifier of the other electronic device to be moved or copied as well as a time of the movement or copying. The recording system according to claim 1,
further,
Device identifier storage means for storing an identifier corresponding to the second electronic device when the data is moved or copied from the first electronic device to the second electronic device;
Information identifier storage means for storing an identifier corresponding to the data when the data is moved or copied from the first electronic device to the second electronic device;
Time storage means for storing a time at which the data is moved or copied from the first electronic device to the second electronic device;
Collating means for collating the first information identifier stored in the first electronic device or the second electronic device with the second information identifier stored in another electronic device;
The first information identifier and the second information identifier are updated by the collating means according to the comparison between the first information identifier and the second information identifier, and each information identifier is updated. And an update unit that updates the device identifier information in accordance with time information stored in a time storage unit corresponding to the recording system. The recording system according to claim 1,
When it is determined by the checking means that the first information identifier and the second information identifier match, the older one of the time information stored in the time storage means corresponding to each information identifier A recording system for updating device identifier information. The recording system according to claim 1,
The apparatus further comprises display means for displaying the predetermined data that has been moved or copied, the identifier of the other electronic device to which the data has been moved or copied, and the time of movement or copying in association with each other. A characteristic recording system. A source device identifier storage means for storing an identifier corresponding to the first electronic device when data is moved or copied from the first electronic device to the second electronic device;
A destination device identifier storage means for storing an identifier corresponding to the second electronic device when the data is moved or copied from the first electronic device to the second electronic device;
Time storage means for storing a time at which the data is moved or copied from the first electronic device to the second electronic device;
And an adding means for adding the source device identifier, the destination device identifier, and the time to the data to be moved or copied from the first electronic device to the second electronic device. Recording system. The recording system according to claim 5, wherein
A recording system, wherein the additional information added by the adding means is copied to the first electronic device. The recording system according to claim 5, wherein
A recording system, wherein the additional information added by the adding means is updated between the first electronic device and the second electronic device. The recording system according to claim 5, wherein
The recording system further comprising display means for displaying a list of the data and the destination device identifier based on the time. First and second electronic devices that store data and reproduce the stored data;
A copy step of moving or copying the data stored in the first electronic device to at least the second electronic device;
When the data stored in the first electronic device is moved or copied to a predetermined other electronic device, the data is relative to the predetermined data moved or copied to the first electronic device. A recording method characterized by storing an identifier of the other electronic device to be moved or copied as well as a time of the movement or copying. A source device identifier storage step for storing an identifier corresponding to the first electronic device when data is moved or copied from the first electronic device to the second electronic device;
A step of storing a destination device identifier for storing an identifier corresponding to the second electronic device when the data is moved or copied from the first electronic device to the second electronic device;
A time storage step for storing a time at which the data is moved or copied from the first electronic device to the second electronic device;
An additional step of adding the source device identifier, the destination device identifier, and the time to the data to be moved or copied from the first electronic device to the second electronic device. Recording method.

Images