Server, system and method for providing media files for download by a user

Abstract

The invention relates to a server for providing media files for downloading by a user, which has an operating system in which the user is created, a media table stored in a memory, in which at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file, an identifier table stored in a memory, in which an identifier which can be assigned to an identifier carrier is assigned to the user, and an assignment table stored in a memory, in which the first media ID and / or the second media ID can be assigned to the identifier, and in which the first media ID is not assigned to the identifier, and in which a program routine is provided with which the user can change the assignment table and assign the first media ID to the identifier in the assignment table.

Description

Technical Field

[0001] This invention relates to a server that provides media files for users to download. Furthermore, it relates to a user interface for interacting with the server that provides media files for users to download. This invention also relates to a system. This invention further relates to a method for providing media files for users to download from a server. Additionally, this invention relates to a method for interacting with a server that provides media files for download via a user interface. Background Technology

[0002] WO 2015 / 104222A1, WO 2017 / 129349A1, DE 10 2011 056 420 A1, EP 3594833A1, WO 2015 / 078923 A1, and US 2018 / 0353869A1 all disclose a device for reproducing audio information. This device includes a speaker and a sensor capable of detecting characteristics or changes in characteristics of the environment within its environmental area. The corresponding device also includes a control unit that can control the speaker to reproduce the audio information if the sensor detects a specific characteristic or change in that characteristic within its environmental area, or if the control unit detects a specific characteristic change detected by the sensor. In these known devices, the sensor is designed as a reader communicating with a passive RFID transponder. These known devices are supplemented with an identifier carrier. In this system, the identifier carrier possesses properties that allow the sensor to determine whether the identifier carrier is within the sensor's environmental area or whether the identifier carrier alters characteristics of the sensor's environment that allow it to be detected in the surrounding area. In previously known systems, the identifier carrier incorporates an RFID transponder.

[0003] WO 2015 / 104222 proposes that the control unit of a device is designed to transmit specific characteristics or information containing defined changes in those specific characteristics to a specific server connected to the Internet. The server then assigns the identified specific characteristics or changes in those specific characteristics to specific audio information. The server transmits the data to the device, which has already assigned it to the specific characteristics or changes in those specific characteristics transmitted to it by the control unit.

[0004] DE 10 2011 056 420 A1 proposes that an identifier carrier, called an identification tag, contains network address data under which the media file can be located, such as a URL address and / or a predefined identification number, which can be used to uniquely identify the media file in a database. DE 10 2011 056 420 A1 proposes the use of blank playable objects. The use of blank playable objects should enable the use of media file content stored on other data carriers in a manner suitable for young children via a playback device. To this end, DE 10 2011 056 420 A1 proposes that a second media file be first stored in the memory of the playback device. For example, the second media file can be transferred from a data carrier such as a CD or DVD to the memory of the playback device. After or during the saving of the second media file, a blank RFID identification tag of the blank playable object is uniquely linked to the second media file. This is achieved by assigning information contained on the blank identification tag (e.g., the ID code of the blank identification tag) to the second media file in the playback device. If the playback device can be connected to a computer, appropriate computer software should be used for the linking.

[0005] WO 2017 / 129349A1 proposes that data packets transferred from external storage to the memory of a playback device can originate from a library of databases stored in the external storage. This library can be provided by an external service provider, such as an audiobook publisher or film distributor. WO 2017 / 129349A1 also proposes using recording software to record the data packets separately in the external storage. For designs where the external storage is part of a computer in a home network, WO 2017 / 129349A1 proposes that the recording software be executed by the processor of that computer. However, it is also proposed that the recording software be executed on an external computer (external device), such as a smartphone, tablet, laptop, or desktop computer or workstation, and that the resulting data packets be placed in an external storage device, such as a cloud, via a network, particularly and preferably via the Internet, from which the data packets are transferred to the storage device of the playback device. If the playback device requests data packets from the external storage, the external storage and the device can be designed such that it can be determined first whether a copy of the data packets is already stored in the playback device. Based on this, it can be determined whether and which data packets are transferred from the external storage to the playback device. In this way, with the help of the same identifier, different content can be accessed over time, such as content that changes regularly (like podcasts) or content that changes based on events.

[0006] WO 2017 / 129349 proposes using recording software to transfer data packets from a computer using the recording software to external storage. It proposes that the recording software either records content itself or imports other content and transfers all or part of this content to external storage (executed on another computer) over a network. The recording software assigns content to one or more specific identifiers or groups of identifiers. For this purpose, the recording software running on an external device determines one or more specific identifiers or groups of identifiers suitable for assignment through a connection to the playback device (directly or via an intermediate server) (once or repeatedly). The recording software running on the external device allows the user of the recording software to determine which identifier to assign the content to before or after recording or importing the content. WO 2017 / 129349 proposes an alternative whereby the establishment of the identifiers in question is determined by the fact that: - if the user of the recording software has an available identifier - the identifier is imported into the detection area of ​​the playback device. WO 2017 / 129349 also proposes an embodiment of storing the relationship between the user (or user group) of the recording software and one or more identifiers through user accounts. According to WO 2017 / 129349, the allocation of relevant identifiers to user accounts can be stored, for example, in external storage or in the same device used to execute the recording software, preferably in both locations. According to WO 2017 / 129349, the device executing the recording software can therefore determine "which identifier carriers belong to the user assigned to the user account" by assigning the identifier carriers in question to the user account. According to WO 2017 / 129349, content just generated by the recording software, whether generated by the recording itself or just imported, can therefore be assigned identifiers within the recording software. The data packet corresponding to the generated content (recorded content or imported content), along with additional information regarding which specific identifier or group of identifiers this data packet belongs to, is then transferred from the device executing the recording software to an external storage device in the cloud.

[0007] US2018 / 0353869 A1

[0021] proposes that a control device (e.g., a smartphone, tablet, or external computer, but not a playback device) can indirectly change the media or instructions to be executed through interaction with a playback device (in this case, an entertainment media device) or through interaction with a server.

[0054] proposes that the server can store a database that links device control information to identifier carrier identifiers. US2018 / 0353869 A1 proposes the possibility of using an external control unit, such as a smartphone or tablet (as a controller device).

[0218] proposes that such an external control unit can access the identifier carrier through the playback device and can read, write, or modify it; US2018 / 0353869 A1 works with a writable identifier carrier. Summary of the Invention

[0008] In this context, the object of the present invention is to provide a server and / or user interface through which the number of media files to be kept available and / or the amount of data exchanged between the server and the user interface can be reduced. Furthermore, part of the object of the present invention is to keep the technical requirements on playback devices low or to optimize their use, and to enable the system to be used optimally even under different data connection conditions.

[0009] This objective is achieved through the server, user interface, system, and method of the present invention, as well as the apparatus, computer program, data carrier signal, and computer-readable storage medium for data processing. Advantageous embodiments are provided in the dependent claims and the following description.

[0010] The advantages of this invention can be achieved by providing a server. Furthermore, providing a server implies providing goods that are themselves marketable, which is why this invention relates to servers. Regarding system limitations, the server may include a communication interface through which it can receive and transmit signals. Parts of the server can be used to receive certain signals through the communication interface, parse the structure of these signals, and extract the information contained within the signals. Parts of the server can also be used to transmit certain signals through the communication interface, these signals having a specific structure and containing information within that specific structure.

[0011] The present invention also relates to a user interface.

[0012] This invention also relates to a system comprising a server and a user interface executable on an external device, particularly a system having a server, a user interface, and an external device on which the user interface can be executed or on which software providing the user interface can be stored. The external device can be a smartphone, tablet, a wearable device such as a smartwatch, or a computer such as a laptop. In one embodiment of the invention, the server operator makes the user interface available to third parties, for example, in the form of software for an application or software running in a web browser, thereby allowing the software providing the user interface to execute on an external device owned by the third party. The advantages of the invention are realized in this type of use; for example, by providing the user interface, the server operator enables third parties to identify other media files using small amounts of data to be exchanged using existing identifier carriers.

[0013] Regarding system limitations, the user interface may include the fact that it can control external devices, possibly using other software components present on those devices, to receive and transmit signals through the external devices' communication interfaces. Parts of the user interface can be used to parse specific signals received through the communication interface regarding their structure and to identify the information contained within those signals. Parts of the user interface can also be used to transmit signals through the communication interface that have a specific structure and the information contained within that structure, so that the server receiving these signals can parse their structure and extract the information contained within them.

[0014] The present invention also relates to a system having a server and an identifier carrier, preferably to a system having a server, an identifier carrier and a user interface that can be executed on an external device, and particularly to a system having a server, an identifier carrier and a user interface and an external device on which the user interface can be executed or where software providing the user interface can be stored.

[0015] This invention also relates to a system having a server, an identifier carrier, and a playback device, preferably a system having a server, an identifier carrier, a playback device, and a user interface executable on an external device, and more particularly a system having a server, an identifier carrier, a playback device, a user interface, and an external device on which the user interface can be executed or on which software providing the user interface can be stored. Regarding system limitations, the playback device may include a communication interface through which it can receive and transmit signals. The playback device can be used to receive certain signals through the communication interface, parse the structure of these signals, and identify the information contained in the signals. The playback device can also transmit certain signals with a specific structure and containing information within that specific structure through the communication interface, so that the server receiving these signals can parse the structure of these signals and identify the information contained in the signals.

[0016] The server's communication interface is preferably designed to send signals to and receive signals from a communication network. The server's communication interface is preferably a connector, more preferably a cable connector for cables, through which the server can send signals to and receive signals from the Internet.

[0017] The user interface implemented on the external device is preferably designed to send signals to and receive signals from the communication network via the external device's communication interface. The external device's communication interface can be a cable connection for use with a cable, through which the external device can send signals to and receive signals from the Internet. The external device's communication interface is preferably a wireless communication interface, such as a WLAN antenna, Bluetooth antenna, or mobile radio antenna, through which the external device can send signals to and receive signals from the Internet.

[0018] The communication interface of the playback device is preferably designed to send signals to and receive signals from a communication network. The communication interface of the playback device can be a cable connection, through which the playback device can send signals to and receive signals from the Internet. Preferably, the communication interface of the playback device is a wireless communication interface, such as a WLAN antenna, Bluetooth antenna, or mobile radio antenna, through which the playback device can send signals to and receive signals from the Internet.

[0019] According to the present invention, a media table, an identifier table, and an allocation table are stored in the memory of a server. In a preferred embodiment, a user group table, a permission table, and a device identifier table are also provided, for example. A table is used to assign members of a first group of members, such as identifiers from a set of identifiers, to members of a second group of members, such as media files from a set of media files, regardless of how this is technically implemented, but preferably implemented in a database. In its simplest form, the table has a first column in which members of the first group are listed above and below each other, and a second column adjacent to the first column, wherein allocation is performed by listing the members of the first group to be allocated to members of the second group in the same row as the members of the second group listed in the second column. Information about the allocation from members of the first group to members of the second group can be obtained by reading the rows. However, the table can also be implemented, for example, in the form of a relational database or as part of a relational database. However, the table can also be implemented, for example, in the form of a pivot table or as part of a pivot table database. The invention is not limited to this form of table creation when the table is described in the following description with reference to columns and rows.

[0020] Therefore, the present invention also relates to an apparatus for data processing, including means for performing steps of one of the methods according to the present invention. Furthermore, the present invention relates to a computer program, particularly a computer program product, which includes commands that, when executed by a computer, cause the computer to perform one of the methods according to the present invention. Additionally, the present invention relates to a data carrier signal for transmitting the computer program [product]. The present invention also relates to a computer-readable storage medium, including commands that, when executed by a computer, cause the computer to perform one of the methods according to the present invention.

[0021] According to the invention, program routines are stored on a server. In preferred embodiments, for example, library routines, extended routines, stock routines, first standard routines, actual state routines, second standard routines, and stress routines are provided. In the context of the server description, routines stored on the server are understood to be objects according to the invention, thereby storing a sequence of instructions (commands) on the server, which, when read and executed by the server's processor, results in the actions attributed to that routine in the following description. In the context of the process description to be executed with a server or system, routines stored on the server mean performing the actions attributed to that routine in the following description.

[0022] According to the present invention, the user interface has UI modification routines. Preferred embodiments include, for example, UI library routines, UI extension routines, UI inventory routines, UI startup routines, UI locking routines, UI unlocking routines, UI current state routines, UI user maintenance routines, and UI player maintenance routines. In the context of the user interface description, if a sequence of instructions (commands) is stored in the software of the user interface, the routines of the user interface are understood to be, according to the present invention, that the sequence of instructions (commands)—if read and executed by a processor—contains the instructions attributed to that routine in the following description. In the context of the process description to be performed through the user interface, the user interface routines are understood to mean that the actions attributed to that routine in the following description are performed.

[0023] The server according to the present invention has an operating system. For example, the operating system may be Linux.

[0024] In an operating system, users can be created in a user management system. If a user is created in a user management system within a database of another operating system-based data management program, it is equivalent to a user created in the operating system. Preferably, more than 50 users, more than 100 users, and more than 100,000 users are created in the user management system within the operating system. In a preferred embodiment, each user, or each user created in the operating system, is identified in each case by a username assigned only once. The operating system may also provide users with the option to log in using single sign-on.

[0025] In a preferred embodiment, the user table is stored in the server's memory. Users created in the user management system are listed in the user table. Information such as passwords or credit status can be assigned to users in the user table. In a preferred embodiment, users in the user table can be assigned to one or more user groups. Additionally or alternatively, a user group table can be stored in the server's memory. In the user group table, users belonging to a group are assigned to the corresponding user group. Information such as passwords or credit status can be assigned to user groups in the user group table.

[0026] In a preferred embodiment, an administrator is created within the operating system. In this preferred embodiment, the administrator differs from a user in that an administrator can change the assignment of an identifier to another user in the identifier table. In this preferred embodiment, a user cannot change the assignment of an identifier to a user. Alternatively, the administrator differs from a user in that an administrator can assign any media ID from the media table to any ID from the ID table. In a preferred embodiment, if a media ID is assigned to a user in the permissions table or to their user group, then a user can only assign a media ID to an identifier in the assignment table.

[0027] In a preferred embodiment, device identifiers are assigned to users in the user table. Preferably, several device identifiers are assigned to users in the user table. In a preferred embodiment, device identifiers are assigned to user groups in the user group table. Multiple device identifiers are preferably assigned to user groups in the user group table. In a preferred embodiment, device IDs are assigned to user groups in the user group table. Preferably, several device IDs are assigned to user groups in the user group table. In a preferred embodiment, a locking attribute is assigned to the user or user group in the allocation of device IDs in the user table or user group table.

[0028] The device identifier is preferably a sequence of letters and / or numbers and / or special characters. The device identifier can be a unique identifier (UID), a universally unique identifier (UUID), or a globally unique identifier (GUID). If, according to a preferred embodiment, a playback device is provided as part of a system having a processor or memory chip according to the invention, the device identifier can be an identifier of the processor or memory chip.

[0029] The server according to the invention has a media table, wherein at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file. In a preferred embodiment, more than 50 media files with media IDs are assigned in the database, more than 100 media files with media IDs are preferably assigned, and more than 100,000 media files with media IDs are preferably assigned. References to “first media ID” and “second media ID” are used only for linguistic references to two different media IDs; “first media ID” is not “second media ID”. The use of the numbers “first” and “second” is not used to describe a rank or hierarchy between the first media ID and the second media ID.

[0030] Assigning a media ID to a media file in the media table can be achieved by assigning the media file's storage location to the media ID. The storage location can be a specified location on the storage of the server storing the particular media file. The storage location can also be a pointer, such as a Uniform Resource Locator (URL), which points to the actual storage location of the media file, for example, on a storage device on another server. Assigning a media ID to a media file in the media table can also be achieved by assigning the media file's filename to the media ID—provided that the media ID itself is not the media file's filename.

[0031] A media ID is an identifier for a media file. A media ID is preferably a sequence of letters and / or numbers and / or special characters. A media ID can be the filename of the media file or part of a filename, or contain the filename or part of a filename. A media ID can be a Unique Identifier (UID), a Universally Unique Identifier (UUID), or a Globally Unique Identifier (GUID).

[0032] In a preferred embodiment, the server has a media storage device for storing media files. The media files stored in the media storage device are particularly and preferably files having one of the following formats: AAC, AIF, AIFF, FLAC, MP3, M4A, M4B, WAV, OGA, OGG, OPUS, WMA. In a preferred embodiment, audio files, rather than video files, are stored in the media storage device. In a preferred embodiment, audio files are assigned media IDs in a media table, while no video files are used.

[0033] In one embodiment, media files stored in a media storage device may have different formats. In a preferred embodiment, media files stored in a media storage device have the same format. In alternative and preferred embodiments, media files stored in a media storage device have formats from a set of formats, wherein the set particularly and preferably includes no more than 20, particularly and preferably no more than 10, and particularly and preferably no more than 5 different formats.

[0034] In a preferred embodiment, all media files assigned to a media ID in the media table are stored in a media storage device. In an alternative embodiment, some of the media files associated with a media ID in the media table are stored in a media storage device, while in the media table, pointers are associated with the media IDs of media files associated with media IDs not stored in the media storage device.

[0035] More information can be assigned to the media ID in the media table. For example, metadata for the media file associated with the media ID can be stored in the media table. Metadata can be:

[0036] ● Information about the media file's content, such as composer / author, presenter, work, summary, and the media file's serial number in the series.

[0037] ● Categorization, such as assignment to style (popular, classic, R&B), theme (poetry, prose), language (German, English, local dialects), subgenre (e.g., detective stories, fairy tales), or release to specific age groups.

[0038] ●Information regarding music file length (playback time) or media file size (in KB or MB) or, for example, file format.

[0039] ●Information regarding chapters in a media file, chapter length, or the point in the media file that must be navigated to to reach the beginning of a chapter.

[0040] ● Information about the source of the media file assigned to the media ID, such as whether the media file was uploaded by a user and by which user, information about the recording medium that created the media file (as far as is known), and the path to the media file stored on the server (application, web browser, immediate upload).

[0041] ●Information regarding media IDs belonging to a series,

[0042] ●Information regarding identifier types

[0043] ●Version information, specifically and preferably a timestamp identifying the point in time when the media file was uploaded to the server.

[0044] ● Determine the release date when the media ID becomes available to users.

[0045] ●Information about the image file (filename, storage location) that can be used to display the media ID in the UI.

[0046] ●Information regarding popularity (frequency of purchasing this media ID), user feedback, user ratings, promotions, and rankings.

[0047] For example, there could be a name like "Benjamin Blümchen" The series, and the series "Benjamin Blümchen" can be assigned in the media table. A specific media ID. A series can be a set of media files, each storing a sequence of stories consisting of several sequences, such as "Benjamin Blümchen". A series of sequences.

[0048] The fact that the server in the operating state described in this invention has a media table in which at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file means that the server in this operating state recognizes the first media ID and the second media ID. This means that the server does not have to wait for the program routines described in more detail below to find the first media ID and / or the second media ID. In the operating state of the server according to the invention, the first media ID and the second media ID are stored in the media table and are therefore known to the server.

[0049] According to the present invention, an identifier table is stored in the server's memory. In the identifier table, identifiers that can be assigned to identifier carriers are assigned to users. Identifiers can be assigned to users directly. If, according to a preferred embodiment, a user is assigned to a user group in a user group table, the assignment of identifiers to users can also be accomplished by assigning the user's user group to an identifier in the identifier table.

[0050] In a preferred embodiment, an identifier type is assigned to a corresponding identifier in an identifier table. In a preferred embodiment, "Content Type" is provided as the identifier type. This identifier type can be used to convey that the identifier assigned to this identifier type was assigned to a media ID in an allocation table upon initial market launch. In a preferred embodiment of the "Content Type" identifier type, a "Series Type" identifier type can be provided. Besides or as an alternative to the "Content Type" identifier type, this identifier type can be assigned to an identifier in an identifier table. The "Series Type" identifier type can be used to express that the identifier assigned to this identifier type was assigned to a media ID in an allocation table upon its initial market launch, and that the associated media file is a series of media files. In a preferred embodiment of the "Series Type" identifier type, an identifier type assigned to a specific series can be provided, such as "Benjamin Blümchen". Identifier Type. The identifier type assigned to a specific series indicates that the identifier assigned to that type was already allocated a media ID in the allocation table upon initial market release, and the media file assigned to it is a media file specific to that series; in our example, the series "Benjamin Blümchen". In particular and preferably, the identifier type assigned to a specific series can be used to express a preference that the identifier assigned to that identifier type was already assigned a media ID in the allocation table when it was first launched to the market, and that media ID was assigned to a specific series in the media table (the specific series is entered in the media table); in our example, the series "Benjamin Blümchen".

[0051] In a preferred embodiment, a “creative type” is provided as an identifier type; this identifier type can be used to convey information that the identifier assigned to this identifier type was not assigned in the allocation table when the product was first launched to the market.

[0052] In a preferred embodiment, the server allows the identifier type to be changed. For example, an identifier initially assigned the "creative type" identifier type can be assigned the "content type" identifier type, particularly and preferably the "series type" identifier type, and particularly and preferably the identifier type assigned to a specific series.

[0053] In a preferred embodiment, a locking attribute is assigned to a user or user group identifier in an identifier table. The presence of the locking attribute can be used to restrict changes to the assignment of identifiers to users or user groups.

[0054] In a preferred embodiment, a device identifier is assigned to a user or user group in the identifier table. The existence of the device identifier can be used to combine the assignment of identifiers to users or user groups with the assignment of device identifiers. In a preferred embodiment, the device identifier assigned in the identifier table to the user or user group associated with the identifier can be the same device identifier assigned to a user or user group in the user table or user group table.

[0055] The identifier is preferably a sequence of letters and / or numbers and / or special characters. The media ID can be a unique identifier (UID), a universally unique identifier (UUID), or a globally unique identifier (GUID). If an identifier carrier is provided as part of a system with an RFID transponder according to a preferred embodiment, the identifier is preferably stored in the RFID transponder. In a preferred embodiment, a sequence of letters and / or numbers and / or special characters, preferably a unique identifier carrier (UID), a universally unique identifier carrier (UUID), or a globally unique identifier carrier (GUID), is stored in the RFID transponder. In this embodiment, the identifier is preferably a sequence of letters and / or numbers and / or special characters stored in the RFID transponder, or a sequence of letters and / or numbers and / or special characters obtained from a sequence of letters and / or numbers and / or special characters stored in the RFID transponder according to a conversion rule.

[0056] According to the present invention, the allocation table is stored in the server's memory. In the allocation table, a first media ID and / or a second media ID can be assigned to an identifier.

[0057] The allocation table can be designed such that only one media ID can be assigned to an identifier. If an identifier that has already been assigned a media ID (e.g., the second media ID) in the allocation file is to be assigned another media ID (e.g., the first media ID), then the assignment of the identifier to a media ID (e.g., the second media ID) is resolved (e.g., deleted), and the assignment of the identifier to another media ID (e.g., the first media ID) is performed in this manner.

[0058] The allocation table can be designed to assign several media IDs to an identifier. In one embodiment, two media IDs can be assigned to the identifier. In a particular and preferred embodiment, a hierarchy of the two media IDs can be stored in the allocation table of that embodiment. The hierarchy of media IDs can be generated by the storage location of the media IDs in the allocation table or by additional information stored in the allocation table. In a particularly simple embodiment, a hierarchy can be implemented using an allocation table with at least three columns, wherein:

[0059] ● An identifier was entered in the first column.

[0060] ● In the second column, the first media ID can be assigned to the identifier in the first column by writing the first media ID in the second column to the same row as the identifier in the first column, and

[0061] ● In the third column, the second media ID can be assigned to the identifier in the first column by writing the second media ID in the third column to the same row as the identifier in the first column.

[0062] This embodiment of the allocation table may include a media ID (in this case, the second media ID) written in a third column of the hierarchy, which is higher than the media ID written in the second column (in this case, the first media ID). In such an embodiment of the allocation table, the media ID written in the second column of the identifier row can be considered the default (default media ID). If no media ID is entered in the identifier row in the third column, the default media ID stored in the second column is used as the media ID assigned to the identifier. However, if a media ID is entered in the third column of the identifier row, then—even if a media ID was entered in the second column of the identifier row—the media ID entered in the third column of the identifier row is used as the identifier. In a preferred embodiment of this embodiment, the user can only enter in the third column using a program routine. This ensures that a specific identifier in the allocation table is always assigned a media ID.

[0063] In a preferred embodiment, a locking attribute is assigned to the allocation of media IDs in the identifier-to-allocation table. The presence of the locking attribute can be used to limit the possibility of changing the allocation of media IDs in the identifier-to-allocation table to specific users within a user group, such as the administrator of the user group.

[0064] In a preferred embodiment, a device identifier is assigned to an identifier associated with a media ID in an allocation table. The existence of the device identifier can be used to combine the assignment of an identifier to a media ID with the assignment to a device identifier. In a preferred embodiment, the device identifier assigned to both the identifier and the media ID in the allocation table can be a device identifier assigned to a user or user group in a user table or user group table.

[0065] Additionally or alternatively, device identifiers may be assigned to identifiers in a table.

[0066] In the operating state of the server according to the invention, the first media ID of the identifier is not assigned in the allocation table. The server knows the first media ID, specifically because it is assigned to the first media file in the media table, but the first media ID is not assigned to the identifier.

[0067] According to the present invention, a program routine is provided on the server, through which the user modifies the allocation table and assigns a first media ID to an identifier in the allocation table.

[0068] In a preferred embodiment, the program routine is triggered by receiving a change signal and includes a step of evaluating the change signal.

[0069] In a first embodiment, the structure of the change signal can be optionally modified such that the change signal contains an identifier to be reassigned in the allocation table and a media ID to be assigned to the identifier, i.e., a first media ID. In this embodiment, the program routine can be executed in such a way that the identifier and the first media ID are read from the change signal during the step of evaluating the change signal. In a subsequent step, the entry in the allocation table associated with the transmitted identifier is modified and the identifier is assigned the first media ID; in a preferred embodiment, this is a unique media ID by deleting any previously existing assignments to another media ID, or in another preferred embodiment, in addition to an existing media ID, but as a higher-level media ID.

[0070] In a further embodiment, the structure of the change signal can be chosen such that the change signal contains information about several identifiers and several media IDs, and also contains at least information that one of the identifiers contained in the change signal is assigned to one of the media IDs contained in the change signal. Preferably, the change signal in this embodiment includes an assignment to one of the media IDs contained therein for each identifier it contains. For example, the change signal may reflect the contents of a UI allocation table stored in an external device or a portion of the contents of a UI allocation table stored in an external device. In this embodiment, the program routine can be executed in such a way that, in the step of evaluating the change signal, it reads the identifiers, media IDs, and their assignments to the identifiers from the change signal. In a subsequent step, the program routine may modify the entry for each identifier transmitted in the change signal (for which a media ID is also transmitted in the change signal) in the server's allocation table and assign the corresponding identifier to the media ID communicating with the change signal; in a preferred embodiment, as a unique media ID and by deleting any previously existing assignments to another media ID, or in another preferred embodiment, in addition to an existing media ID, but as a higher-level media ID. In a preferred embodiment, the program routine can use the fact that the identifier in the change signal is not assigned to a media ID in the change signal to maintain the assignment to a media ID that may exist in the server allocation table. Alternatively, the program routine can use the fact that the identifier in the change signal is not assigned to a media ID in the change signal to cancel any assignment of that identifier to a media ID in the server allocation table. In a preferred embodiment, the program routine can check which identifiers in the server allocation table have been assigned to media IDs contained in the change signal, and in doing so, check which identifiers contained in the change signal have reported an assignment to a media ID different from the media ID assigned in the server allocation table, or an initial assignment to a media ID, if the media ID for the corresponding identifier has not yet been recorded in the server allocation table. If a difference is detected, the program routine can send an acknowledgment request signal containing the identifiers with different assignments. The invention can specify that if the server includes an acknowledgment signal in response to the sending of the acknowledgment request signal, the program routine only modifies the assignment in the server allocation table for those identifiers for which it has detected assignment differences. This embodiment allows the user to:

[0071] ● Maintain their own UI assignment table on external devices, where one identifier is assigned a media ID, or multiple identifiers, each with a media ID.

[0072] ● This UI allocation table can be modified offline, meaning without communicating with the server.

[0073] ● After establishing communication options with the server, the server and external devices are synchronized and allocated.

[0074] In a third embodiment, the structure of the change signal can be chosen such that it contains information about the identifier whose allocation in the allocation table is to be changed, but does not contain any information about the media ID. In this embodiment of the program routine, the change signal is received before the server sends the library signal. The structure of the library signal can be chosen such that it contains information about the media ID. In this embodiment of the program routine, the server remembers the media ID it sent with the library signal. In this embodiment, the program routine can be executed in such a way that the identifier is read from the change signal during the step of evaluating the change signal. If the server now receives the change signal, as provided in this embodiment of the program routine, which contains information about the identifier whose allocation in the allocation table will be changed, the entry in the allocation table associated with the transmitted identifier is changed in a subsequent step, and the identifier is assigned the media ID contained in the library signal and already stored by the server; in a preferred embodiment, as the unique media ID while simultaneously deleting any previously existing allocations to another media ID, or in another preferred embodiment, as a higher-level media ID in addition to an existing media ID.

[0075] Embodiments including the steps of receiving and evaluating the change signal are particularly suitable for systems according to the invention that simultaneously provide a user interface. The user interface, running on an external device, can be designed to generate change signals that are understandable to the server and transmitted by the external device.

[0076] As an alternative to an embodiment that uses a procedure routine that includes a step of receiving a change signal and a step of evaluating the change signal, an embodiment may allow the user to directly access the server, for example, via a Virtual Private Network (VPN) or remote desktop session, and generate the change signal directly on the server.

[0077] The execution of a program routine can begin when the server receives a change signal. Alternatively, the execution of a program routine can be triggered by events independent of the server and the user. For example, a program routine can execute at certain specific times (weekly, daily, hourly, minutely, or in significantly shorter time units). It can also execute within a defined time interval since the last execution of the program routine. This type of execution is particularly suitable for embodiments where a UI allocation table stored on an external device is synchronized with the server's allocation table during the execution of the program routine. Additionally or alternatively, the execution of a program routine can be triggered by events occurring on the server. For example, a user logged into the server can cause a program routine to be executed.

[0078] The method according to the invention for providing media files for a user to download from a server is executed on a server, preferably a server according to the invention, wherein the server is...

[0079] ●This involves creating the user's operating system.

[0080] ● A media table stored in memory, wherein at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file.

[0081] ● An identifier table stored in memory, in which identifiers that can be assigned to identifier carriers are assigned to users.

[0082] ● Equipped with an allocation table stored in memory, wherein:

[0083] i. An identifier can be assigned to at least the first media ID or the second media ID, and

[0084] ii. The first media ID was not assigned to the identifier.

[0085] According to the method of the present invention, a user executes a program routine provided on a server, through which the user modifies the allocation table and assigns a first media ID to an identifier in the allocation table.

[0086] Contrary to the process known from WO 2017 / 129349 A1, this invention allows users to initiate the assignment of identifiers to media IDs within the server, without uploading the media file associated with the media ID from the UI to the server in the same process. This reduces the amount of data that must be exchanged between the UI and the server. While the media file must still be uploaded according to WO 2017 / 129349 A1, this invention eliminates the need for such data.

[0087] Because, as is known in this invention from WO 2017 / 129349, in relation to the simultaneous uploading of media files (which has a long signal run time required for this), only a relatively short signal exchange occurs (resulting in a shorter signal run time), thus user interaction can occur more quickly. The speed at which media IDs are assigned to identifiers is also faster, allowing users to retrieve the media files assigned to the identifiers by media IDs and play them on playback devices more quickly.

[0088] Furthermore, this invention can reduce the amount of data on the server. Using the process known from WO 2017 / 129349 A1, users must upload media files. It can be assumed that, without considerable effort, the server cannot detect whether the content of the media file has not yet been stored on the server by another user as part of the media file uploaded by that user. Therefore, according to the process known from WO 2017 / 129349 A1, a separate media file must be maintained for each user, even if its content already exists in another media file on the server. This requires increasing the server's storage capacity. Using the process according to the invention, media files stored on the server can be made available to multiple users, i.e., by assigning corresponding media IDs to corresponding users. Although multiple users use the information stored in the media file, the media file only needs to be stored on the server once.

[0089] In a preferred embodiment, a user uses a program routine to assign a media ID to the ID of a media file stored on a server by another user, or to assign a pointer to a media ID. In a preferred embodiment, a user uses a program routine to assign a media ID to an identifier, and another user is listed in the media table as the user who uploaded the media file belonging to that media ID. In a preferred embodiment, for media files not stored on the server by the user, the user uses a program routine to assign a media ID to an ID using the program routine. In a preferred embodiment, a user uses a program routine to assign a media ID not listed in the media table to a user who has uploaded a media file belonging to that media ID.

[0090] In a preferred embodiment, the user uses a program routine to assign a media ID to an identifier (a second identifier), which is also assigned to another identifier (a first identifier) ​​in the identifier table, particularly and preferably without altering the media ID's assignment to the other identifier (a first identifier). In a preferred embodiment, the first media ID is assigned to another identifier (a first identifier) ​​in the identifier table, and is also assigned to another identifier (a first identifier) ​​after the program routine has been executed. On the one hand, this allows a user to assign the same media ID to several identifiers in his or hers. Furthermore, media IDs can be assigned to the respective identifiers of several users within the server, such as the media ID of a specific episode in a series; then, only one media file of that specific episode in the series must be kept available on the server, even if it is assigned to several users by its media ID.

[0091] In a preferred embodiment, the permission table is stored in the server's memory. In a preferred embodiment, media IDs are assigned to users in the permission table. Additionally or alternatively, media IDs are assigned to one or more users in the permission table. Additionally or alternatively, media IDs are assigned to user groups in the permission table. Additionally or alternatively, media IDs are assigned to user groups in the permission table.

[0092] In a preferred embodiment, the program routine checks whether the media ID to be assigned to the identifier when executing the program routine is assigned to a user or a user group in the permissions table. In a preferred embodiment, if the media file is assigned to a user or a user group in the permissions table, the program routine only assigns the media ID to the identifier.

[0093] In a preferred embodiment, the program routine checks whether the ID to be changed in the media ID allocation is already assigned to a user in the ID table or a user group to which the user belongs when the program routine is executed. In a preferred embodiment, if the identifier is already assigned to a user in the identifier table or a user group to which the user belongs, the program routine only assigns the media ID to the identifier.

[0094] In the preferred execution form, the program routine checks whether the ID to be changed in the allocation to the media ID during program routine processing is an ID of a specific ID type. In the preferred execution form, if the ID is of a certain ID type, the program routine only assigns the media ID to the ID. In the preferred execution form, the program routine checks...

[0095] ● Whether the media ID to be reassigned to the identifier in the allocation table belongs to a series, preferably a specific series of media IDs, and

[0096] ● In the allocation table, the identifier to be assigned to the media ID is an identifier of the "series type" identifier type, specifically and preferably an identifier of the identifier type of the series to which the media ID belongs.

[0097] For example, this embodiment allows the use of program routines to determine whether a media table belongs to the series "Benjamin Blümchen". The media ID is assigned only to the identifier type according to the ID table, belonging to "Benjamin Blümchen". Identifiers of the identifier type.

[0098] In a preferred embodiment, library routines are provided on a server. The library routines emit library signals. These library signals contain one or more media IDs. The library routines can...

[0099] ● Includes a step to read at least one media ID from the media table, specifically a step to read the media ID corresponding to the library standard from the media table, and / or

[0100] ●The step of reading at least one media ID from the permissions table, in particular the step of reading the media ID in the permissions table assigned to a specific user or according to the user group to which the specific user belongs in the user group table, in particular the step of reading the media ID corresponding to the library standard and assigned to a specific user in the permissions table or according to the user group to which the specific user belongs in the user group table.

[0101] In a preferred embodiment, the library signal includes one or more media IDs read in this manner.

[0102] In a preferred embodiment:

[0103] ● You can select a library standard so that when it is used in a library routine, all media IDs stored in the media table (library standard "all") and / or

[0104] ● You can select a library standard so that when used in library routines, it reads all media IDs stored in the media table, assigns them certain metadata in the media table, such as belonging to a specific series or certain categories, such as being assigned to a style (pop, classic, RnB), (library standard "certain metadata") and / or

[0105] ● You can select a library standard to read all media IDs (library standard "User Media ID") assigned to a specific user in the permissions table or to the user group to which a specific user belongs, and / or from the permissions table when using it in library routines.

[0106] ● You can select a library standard that, when applied in a library routine, reads all media IDs (library standard "New Media ID") stored in the media table that are not assigned to a specific user in the permissions table or to the user group to which a specific user belongs, and / or...

[0107] ● You can select a library standard such that when it is applied in a library routine, it reads all media IDs (library standard "Assigned Media IDs") that are assigned to a specific user in the permissions table or to the user group to which the specific user belongs based on the user group table, and that are assigned to identifiers in the allocation table that are assigned to a specific user in the identifier table or to the user group to which the specific user belongs based on the user group table.

[0108] ● You can select a library standard that, when applied in a library routine, reads all media IDs (library standard "Free Media ID") that are assigned to a specific user in the permissions table or to the user group to which the specific user belongs in the user group table, and that are not assigned to an ID in the allocation table but are assigned to a specific user in the ID table or to the user group to which the specific user belongs in the user group table.

[0109] First, identify all identifiers assigned to the user in the identifier table or to the user group in the user group table, and determine which of these identifiers was assigned to indicate the identifier type to which a particular series is assigned, so that all series in the identifier table to which the user is assigned an identifier can be identified.

[0110] Then, read all the media IDs stored in the media table and assign a membership to one of the series determined in this way in the media table.

[0111] Then, from the media IDs determined in this way, assign media IDs that are not assigned to the user in the permissions table or to the user group to which the user belongs according to the user group table.

[0112] In a preferred embodiment, the library routine is triggered by receiving a library request signal. This includes the step of evaluating the library request signal. In a preferred embodiment, the library request signal contains library criteria or information from which the server can derive library criteria when evaluating the library request signal.

[0113] In a preferred embodiment, the library signal containing the media ID in the library signal includes information about whether the media ID has been assigned to a user or a user group to which the user belongs in the server's permissions table.

[0114] In a preferred embodiment, the library signal has metadata stored in the media table for media IDs. The metadata included in the library signal may include:

[0115] ● Information about the media file's content, such as composer / author, presenter, work, summary, and the media file's serial number in the series.

[0116] ● Categorization, such as assignment to style (popular, classic, R&B), theme (poetry, prose), language (German, English, local dialects), subgenre (e.g., detective stories, fairy tales), or release to specific age groups.

[0117] ●Information regarding music file length (playback time) or media file size (in KB or MB) or, for example, file format.

[0118] ●Information regarding chapters in a media file, chapter length, or the point in the media file that must be navigated to to reach the beginning of a chapter.

[0119] ● Information about the source of the media file assigned to the media ID, such as whether the media file was uploaded by a user and by which user, information about the recording medium that created the media file (as far as is known), and the path to the media file stored on the server (application, web browser, immediate upload).

[0120] ●Information regarding media IDs belonging to a series,

[0121] ●Information regarding identifier types

[0122] ●Version information, specifically and preferably a timestamp identifying the time the media file was uploaded to the server.

[0123] ● Identify the publication date when the media ID becomes available to users.

[0124] ●Information about the image file (filename, storage location) that can be used to display the media ID in the UI.

[0125] ●Information regarding popularity (frequency of purchasing this media ID), user feedback, user ratings, promotions, and rankings.

[0126] In a preferred embodiment, an extension routine is provided on the server. In a preferred embodiment, a user can use the extension routine to modify the permissions table. The extension routine specifically and preferably enables the user to supplement the permissions table by assigning media IDs to themselves and / or their user groups. In a particular and preferred embodiment, a user can assign media IDs that were not previously assigned to them by executing the extension routine.

[0127] In a preferred embodiment, the extension routine is triggered by the step of the server receiving the extension signal and includes a step of evaluating the extension signal.

[0128] In a first embodiment, the extended signal includes users and / or user groups whose assignments will be changed in the permissions table, and media IDs to be assigned to users and / or user groups. In this embodiment, the extended routine may be performed such that, in the step of evaluating the extended signal, the users and / or user groups and the media IDs are read from the extended signal. In subsequent steps, the entries in the permissions table are changed and the media IDs in the permissions table are assigned to users and / or user groups.

[0129] In the second embodiment, the structure of the extended signal can be selected such that the extended signal contains information about the media ID to be assigned to the user. The assignment to the user is triggered by other circumstances, such as the extended signal received from the server being initiated by the user's login interface.

[0130] In a preferred embodiment, the server checks whether the extended signal contains a media ID that it has already sent in a previous library signal. In a preferred embodiment, if the extended signal contains a media ID that it has already sent in a previous library signal, preferably in a previous library signal that it has sent within a predetermined time window, then the server simply continues the extended routine.

[0131] In a preferred embodiment, the change signal is part of or immediately following the extended signal. This allows the user to tell the server which identifier in the allocation table the media ID contained in the extended signal will be assigned to.

[0132] In a preferred embodiment, the extended routine includes the step of receiving an enable signal from the server. The media ID can be assigned to a user or user group in the permissions table based on whether the server receives the enable signal. Similarly, assigning a media ID to an identifier in the allocation table as a result of a change signal can depend on whether the server receives a release signal. If assigning a media ID to an identifier in the allocation table (depending on the change signal) depends on the media ID being reassigned to an identifier (which is assigned to the user who assigned the identifier in the permissions table or the user group to which the user belongs), then assigning a media ID to an identifier in the allocation table (this is based on receiving a release signal from the change signal) can also be achieved by assigning the media ID to a user in the permissions table based on whether the server receives a release signal.

[0133] A release signal can include confirmation that a certain amount has been credited to the account. For example, a confirmation signal can be generated by... Account generation. This gives users the opportunity to purchase media IDs and associated media files or licenses, or to rent them for a period of time. However, it is also possible for users to want to exchange media files with each other. A release signal can therefore also be included in the permissions table as confirmation that the user to whom the media file was assigned agrees that the media file assigned to him is now also assigned to another user.

[0134] Extended routines may include steps to check a user's credit status. Assigning a media ID to a user in the permissions table can be done based on whether the user's credit status corresponds to or exceeds a predetermined value. The credit table can be stored in the server's memory. Credit status is assigned to users and / or—within the available range—user groups in the credit table. Credit status can also be assigned to users in the user table. Credit status can be a specific value, such as points or currency. As part of the extended routine, it can be determined whether the credit status is higher than a certain points or currency value. As part of the extended routine, after checking the credit status, further preparations can be made for changing the credit status, such as reducing the points or currency value. Credit status can also represent that a user has unlimited credit, for example, if the user is a member of a fixed-fee plan. Using a credit table allows a user to set a certain credit status on the server, such as reloading their "account". As a result, when executing extended routines, the user does not have to worry about the transmission of release signals that might otherwise be necessary. In other words, the user does not have to transmit for the allocation of a specific media file. Credit status also allows a user to gift a certain amount of credit to another user, or in other words, increase the credit status of the user receiving the gift.

[0135] In a preferred embodiment, an inventory routine is provided on the server. The inventory routine issues an inventory signal. The inventory signal contains one or more identifiers and / or one or more device identifiers. Furthermore, the inventory signal may contain information about whether a locking attribute is assigned to a corresponding identifier carrier or corresponding device identifier in an identifier table or allocation table. The inventory routine may have a step of reading at least one identifier from the identifier table, particularly a step of reading an identifier corresponding to an inventory criterion from the identifier table. In a preferred embodiment, the inventory signal contains one or more identifiers thus read. In a preferred embodiment, the inventory signal of an identifier also contains an identifier type stored for that identifier in the identifier table. The inventory routine may have a step of reading at least one device identifier from a user table and / or a user group table, particularly a step of reading a device identifier corresponding to an inventory criterion from the user table and / or user group table. In a preferred embodiment, the inventory signal contains one or more device identifiers read in this manner.

[0136] In a preferred embodiment:

[0137] ● You can select an inventory standard to read all identifiers stored in the identifier table when used in inventory routines, and assign these identifiers to a specific user or to the user group to which the specific user belongs based on the user group table (inventory standard "User Identifier") and / or

[0138] ● You can select an inventory standard to read all identifiers stored in the identifier table when used in inventory routines, assign these identifiers to a specific user or to the user group to which the specific user belongs based on the user group table, and assign a certain identifier type (inventory standard "specific user identifier") and / or

[0139] ● You can select an inventory standard to read all identifiers stored in the identifier table when used in inventory routines, assign these identifiers to specific users in the identifier table or to the user groups to which specific users belong based on the user group table, and assign media IDs (inventory standard "free user identifiers") and / or not assigned in the allocation table.

[0140] ● You can select an inventory standard to read all identifiers stored in the identifier table when used in inventory routines, assign these identifiers to a specific user in the identifier table, or to the user group to which a specific user belongs based on the user group table; and assign media IDs (inventory standard "variable user identifiers") in the allocation table that are different from the media IDs available at the time of querying.

[0141] ● You can select an inventory standard to read all identifiers stored in the identifier table when used in inventory routines, assign these identifiers to a specific user or to the user group to which the specific user belongs based on the user group table, and assign media IDs in the allocation table that are different from the media IDs available at the time of query, corresponding to the selection of a specific identifier type or a specific identifier type (inventory standard "Specific Type Variable User Identifier") and / or

[0142] ● You can select an inventory standard to read all device identifier carriers stored in the user table or user group table when used in the inventory routine. In the user table, these device identifier carriers are assigned to a specific user, or in the user group table, based on the user group to which the specific user belongs (inventory standard "user device identifier").

[0143] In a preferred embodiment, the inventory routine is triggered by receiving an inventory request signal and includes a step of evaluating the inventory request signal. In a preferred embodiment, the inventory request signal contains inventory criteria or information, which the server can use to form inventory criteria when evaluating the inventory request signal.

[0144] In a preferred embodiment, a first standard routine is provided on the server. The first standard routine includes:

[0145] ● Execute library routines and transmit library signals within those routines.

[0146] ● Waiting for an extended signal to be received, and executing an extended routine upon receiving the extended signal, particularly and preferably including a step of receiving an approval signal or a step of checking the user's credit status.

[0147] ● Waiting to receive a change signal and, upon receiving the change signal, executing the program routine according to the invention, which the user uses to change the allocation table and assign the media ID to an identifier in the allocation table.

[0148] In one embodiment of the first standard routine, the first standard routine includes executing an inventory routine, specifically executing the inventory routine before waiting to receive a change signal.

[0149] In a preferred embodiment of the first standard routine, this includes

[0150] ● Execute the library routine and transmit the library signal with the first media ID within the library routine.

[0151] ● Waiting to receive an extended signal containing the first media ID, and executing an extended routine upon receiving the extended signal, particularly and preferably including a step of receiving an approval signal or a step of checking the user's credit status.

[0152] ● Waiting to receive a change signal containing the first media ID, and upon receiving the change signal, executing the program routine according to the invention, in which the user uses the program routine to change the allocation table and allocate the first media ID to the identifier in the allocation table.

[0153] In a preferred embodiment, a real-state routine is provided on the server. The real-state routine causes the transmission of a real-state signal. The real-state signal includes:

[0154] ● One media ID or multiple media IDs

[0155] ● One or more identifiers

[0156] ●Information regarding assigning the corresponding media ID to the corresponding identifier.

[0157] The actual state routine may include the step of uploading the media ID in the allocation table to the identifier belonging to the user or the user group to which the user belongs.

[0158] In a preferred embodiment, the actual state routine is triggered by receiving an actual state request signal and includes a step of evaluating the actual state request signal.

[0159] In a preferred embodiment, a second standard routine is provided on the server. The second standard routine includes:

[0160] ● Execute library routines and transmit library signals within those routines.

[0161] ●Execute the current state procedure and transmit the actual state signal within the current state procedure.

[0162] ● Waiting to receive a change signal and, upon receiving the change signal, executing the program routine according to the invention, in which the user uses the program routine to change the allocation table and assign the first media ID to an identifier in the allocation table.

[0163] In a preferred embodiment, stress routines are provided on the server. In a preferred embodiment, users can utilize stress routines to modify the identifier table and / or the user table and / or the user group table. In particular and preferably, stress routines enable users in the identifier table to supplement the assignment of identifiers to themselves and / or their respective user groups. In particular and preferably, users can assign identifiers that were not assigned to them before the stress routine was executed by performing stress routines on the identifier table.

[0164] In particular and preferably, the stress routine enables a user in the user table or user group table to supplement the assignment of device identifiers to the user and / or the user group to which he / she belongs. In a particular and preferred embodiment, a user can assign a device identifier to himself or his / her user group that was not assigned to him / her before the execution of the stress routine by executing the stress routine in the user table or user group table.

[0165] In a preferred embodiment, the stress routine is triggered by the server receiving a load signal and includes a step of evaluating the load signal.

[0166] In a first embodiment, the stress signal includes users and / or user groups whose assignments will be changed in the identifier table, and identifiers to be assigned to users and / or user groups. In this embodiment, the stress routine can be executed such that, in the step of evaluating the stress signal, users and / or user groups and identifiers are read from the stress signal. In a subsequent step, entries in the identifier table are changed and identifiers in the identifier table are assigned to users and / or user groups. Before performing this step, the stress routine can check whether a locking attribute has been assigned to an identifier in an existing assignment to a user or user group that will now be changed. If a locking attribute has been assigned to an identifier in an existing assignment to a user or user group that is now to be changed, the entries in the identifier table will not be changed, and the identifiers in the identifier table will not be assigned to users and / or user groups. In this case, the server generates an error signal. Alternatively, when a locking attribute is identified, it can be checked whether the user initiating the change has special permissions, such as an administrator within a user group. If the user has special authorization to make the change, the change will be made despite the locking attribute.

[0167] Additionally or alternatively, the stress signal includes users and / or user groups whose assignments will be changed in a user table or user group table, and device identifiers to be assigned to users and / or user groups. In this embodiment, the stress routine may proceed such that, in the step of evaluating the stress signal, the users and / or user groups and device identifiers are read from the stress signal. In a subsequent step, the entries in the user table or user group table are changed, and the device identifiers in the user group or user group table are assigned to users and / or user groups. Before performing this step, the stress routine may check whether a locking attribute is assigned to the device identifier to an existing assignment of a user or user group that is now to be changed. If a locking attribute is assigned to the device identifier to be changed to an existing assignment of a user or user group, the entries in the user table or user group table will not be changed, and the identifiers in the user table or user group table will not be assigned to users and / or user groups. In this case, the server generates an error signal. Alternatively, when a locking attribute is identified, it may be checked whether the user initiating the change has special permissions, such as an administrator within a user group. If the user has special authorization to make the change, the change will be made despite the locking attribute.

[0168] In another embodiment, the structure of the stress signal can be selected such that the stress signal includes an identifier to be assigned to a user. The assignment to the user is caused by other circumstances, such as a stress signal received from the server being initiated by a user interface where the user is logged in. Alternatively, the structure of the stress signal can be selected such that the stress signal includes a device identifier to be assigned to the user. The assignment to the user originates from other circumstances, such as a load signal received from the server being initiated by a user interface where the user is logged in.

[0169] In a further embodiment, the pressure signal includes an identifier and a device identifier. In a preferred embodiment, the pressure signal is a playback device request signal. In this embodiment, the pressure routine can be performed such that, during the step of evaluating the pressure signal, the identifier and device identifier are read from the pressure signal.

[0170] According to the first alternative, the identifier table can be used in a subsequent step to determine which user or user group the stress signal will be assigned to, and in that subsequent step, the device identifier in the user table or user group table can be assigned to that user or user group. Before performing this step, the stress routine can check whether a lock attribute is assigned to an existing assignment of the device identifier to be changed to the user or user group. If a lock attribute is assigned to an existing assignment that assigns the device identifier to the user or user group to be changed, the entry in the user table or user group table will not be changed, and the identifier in the user table or user group table will not be assigned to a user or user group. In this case, the server generates an error signal.

[0171] According to the second alternative, in a subsequent step, the device identifier read from the load signal in the user table or user group table can be determined as to which user or user group it was assigned to, and in a subsequent step, the identifier in the identifier table is assigned to that user or user group. Before performing this step, the stress routine can check whether to assign the locking attribute to the identifier that is now to be changed to the existing assignment of the user or user group. If the locking attribute is assigned to the device identifier that is now to be changed to the existing assignment of the user or user group, the entry in the identifier table will not be changed, and no identifier from the identifier table will be assigned to the user and / or user group. In this case, the server generates an error signal.

[0172] In a preferred embodiment, the stress routine includes the step of receiving an enable signal from the server. The assignment of identifiers to users or user groups in the identifier table and / or the assignment of device identifiers to users or user groups in the user table and / or user group table can be performed based on whether the server receives an enable signal.

[0173] The stress routine may include a step of checking the user's credit status. The assignment of identifiers to users or user groups in the identifier table and / or the assignment of device identifiers to users or user groups in the user table and / or user group table can be performed based on whether the user's credit status has a predetermined value corresponding to or greater than a predetermined value.

[0174] In a preferred embodiment, a locking routine is provided on the server. The locking routine is triggered upon receiving a locking signal. The locking signal may include a user and / or user group, as well as an identifier and a locking indicator. If the server receives a locking signal with a user and / or user group, as well as an identifier and a locking indicator, it assigns the locking attribute to the identifier's allocation to a user or user group in the identifier table. Alternatively, the locking signal may include a user and / or user group, as well as a device identifier and a locking indicator. If the server receives a locking signal with a user and / or user group, as well as a device identifier and a locking indicator, it assigns the locking attribute to the identifier's allocation to a user or user group in the user table or user group table.

[0175] In a preferred embodiment, an unlock routine is provided on the server. The lock routine is triggered upon receiving an unlock signal. The unlock signal may include a user and / or user group, an identifier, and an unlock indicator. If the server receives an unlock signal with a user and / or user group, an identifier, and an unlock message, it removes the lock attribute assigned to the identifier in the user or user group table. The unlock signal may include a user and / or user group, a device identifier, and an unlock message. If the server receives an unlock signal with a user and / or user group, a device identifier, and an unlock indicator, it removes the lock attribute assigned to the identifier in the user table or user group table.

[0176] In a preferred embodiment, an update routine is provided on the server. The update routine is triggered by receiving a playback device status signal. The playback device status signal includes:

[0177] ● One or more identifiers

[0178] ● Version information assigned to the corresponding identifier in the playback device allocation table, particularly the timestamp assigned to the corresponding identifier in the playback device allocation table, and / or

[0179] ● The media ID assigned to the corresponding identifier in the playback device allocation table.

[0180] In a preferred embodiment where the playback device's actual status signal does not contain a media ID, receiving the playback device's actual status signal causes the server to check in the allocation table each identifier transmitted to it along with the playback device's actual status signal to determine which media ID that identifier is assigned to, and to check each media ID, thus determining which version information, specifically which timestamp, is assigned to that media ID in the media table. The server then checks whether the version information determined in this way corresponds to the version information of the identifier assigned to the media ID that the server determines in the allocation table, and uses the media ID to check the version information in the media table within the playback device's actual status signal. If the version information does not match, the server generates an update signal. The update signal may contain one or more identifiers.

[0181] In an alternative embodiment where the playback device's status signal includes a media ID, receiving the playback device's status signal causes the server to check, for each media ID transmitted to it in the playback device's status signal, which version information, and in particular which timestamp, is assigned to that media ID in the media table. The server then checks whether the version information determined in this way corresponds to the version information assigned to the media ID, for which the server determines the version information in the media table in the playback device's status signal. If the version information does not correspond, the server generates an indicator that requires an update indicator. The update signal may contain one or more identifiers.

[0182] In a preferred embodiment, a response routine is provided on the server. The response routine can be triggered by receiving a playback device request signal. The playback device request signal contains an identifier. In a preferred embodiment, the request signal contains a device identifier. In a preferred embodiment, the playback device request signal includes an indicator that needs to be updated.

[0183] If the server receives a playback device request signal with an indication that an update is needed, the server checks which media IDs have been assigned identifiers in the allocation table and generates a response signal. The response signal contains the media file and / or a pointer assigned to that media ID in the media table. The response signal preferably contains an identifier included in the playback device request signal, and preferably the media ID, and preferably version information associated with the media file in the media table, particularly and preferably a timestamp. When the control unit of the playback device receives the media file or pointer, along with the identifier assigned to the media file or pointer and the response signal, the control unit stores the media file in the playback device's memory and updates the playback device allocation table by assigning the location of the media file in the playback device's memory to an identifier in the playback device allocation table, or by assigning a pointer to an identifier in the playback device allocation table. In a preferred embodiment, the control unit may reset the triggered update notification. In a preferred embodiment, the control unit may assign version information, particularly a timestamp, to the identifier, which the server transmits to the control unit along with the media file.

[0184] In a preferred embodiment, the server has a user maintenance routine. The user maintenance routine can be triggered by receiving a user maintenance signal. The user maintenance signal may include a user and a user group. If the server receives a user maintenance signal, it assigns the user to a user group in a user group table. As part of the user maintenance routine, the server may check whether the user who received the user maintenance signal is authorized to make changes to the user group, for example, he / she is the administrator of the user group. In a preferred embodiment, if the user maintenance signal contains an email address, the server sends a message to that email address. This message may contain a confirmation link, by which the recipient of the email can confirm that he / she wishes to be assigned to a user group.

[0185] In a preferred embodiment, the server has a playback device maintenance routine. This routine can be affected by receiving a playback device maintenance signal. The playback device maintenance signal may include a user and / or user group, and a device identifier. If the server receives a playback device maintenance signal, it assigns the device identifier to a user and / or user group in a user table or user group table.

[0186] The system according to the invention has a server and an identifier carrier according to the invention, wherein the identifier carrier has an identifier readable by a reading device. In a preferred embodiment, the identifier has an RFID transponder. In this embodiment, the identifier may be stored in the RFID transponder. In a preferred embodiment, a sequence of letters and / or numbers and / or special characters, preferably a unique identifier (UID), a universally unique identifier (UUID), or a globally unique identifier (GUID), is stored in the RFID transponder. In such an embodiment, the identifier is preferably a sequence of letters and / or numbers and / or special characters stored in the RFID transponder or a sequence of letters and / or numbers and / or special characters obtained from a sequence of letters and / or numbers and / or special characters stored in the RFID transponder according to a conversion rule.

[0187] The user interface (UI) according to the invention can be implemented on an external device, preferably a computer, smartphone, tablet, or wearable device such as a smartwatch, other than a server. The operator of the server according to the invention can allow users to download the user interface and can license users to use the user interface. Several user interfaces can also be part of a system, for example, if a user interface with fewer interaction options is to be provided on a smartphone, in relation to a computer user interface with more interaction options. In a preferred embodiment, the user interface has a graphical user interface (GUI).

[0188] The user interface (UI) has a UI change routine. The UI change routine causes a change signal to be sent. In a first embodiment, the change signal includes the identifier to be changed in the server's allocation table and the media ID to be assigned to the identifier in the server's allocation table. In a second embodiment, the change signal may only include the media ID to be assigned to the identifier in the server's allocation table, for example, if the media ID-to-identifier assignment is caused by other circumstances, such as because the selected media ID is a series of media IDs, and the user is assigned only one identifier in the identifier table, which is an identifier type belonging to that series.

[0189] The method according to the present invention for interacting with a server that provides media files for download, and particularly for interacting with the server according to the present invention via a user interface, provides an implementation of a UI change routine that causes a transmission change signal, the change signal comprising:

[0190] ●Media ID or

[0191] ●Media ID and Identifier

[0192] The method according to the present invention for providing media files for a user to download from a server, wherein the server comprises:

[0193] ●This involves creating the user's operating system.

[0194] ● A media table stored in memory, wherein at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file.

[0195] ● An identifier table stored in memory, in which identifiers that can be assigned to identifier carriers are assigned to users.

[0196] ● and the allocation table stored in memory, where:

[0197] i. An identifier can be assigned to at least the first media ID or the second media ID; and

[0198] ii. The first media ID was not assigned to an identifier.

[0199] This causes a UI change routine to be executed on the user interface, which results in the sending of a change signal, which includes:

[0200] ●First Media ID or

[0201] ●First Media ID and Identifier

[0202] Furthermore, the server receives a change signal, executes a routine to change the allocation table, and assigns the first media ID to the identifier in the allocation table.

[0203] In a preferred embodiment, the user interface (UI) has UI library routines. In a preferred embodiment, the UI library routines have a step of receiving a library signal, the library signal including one or more identifiers. In a preferred embodiment, the UI library routines have a step of sending a library request signal. In a preferred embodiment, the step of sending the library request signal precedes the step of receiving the library signal.

[0204] Library request signals may include library standards. In a preferred embodiment:

[0205] ● You can select a library standard so that when it is used in the server's library routines, all media IDs (library standard "all") stored in the server's media table are read and / or

[0206] ● You can select a library standard so that when used in the server's library routines, it reads all media IDs stored in the server's media table, assigns them certain metadata in the media table, such as belonging to a specific series or category, such as being assigned to a style (pop, classic, RnB), (library standard "certain metadata") and / or

[0207] ● You can select a library standard to read all media IDs (library standard "User Media ID") assigned to a specific user in the server's permission table or to the user group to which the specific user belongs, and / or according to the server's user group table, when it is used in the server's library routines.

[0208] ● You can select a library standard that, when applied in a server-side library routine, reads all media IDs (library standard "New Media ID") stored in the server's media table that are not assigned to a specific user in the server's permissions table or to the user group to which a specific user belongs, and / or...

[0209] ● You can select a library standard that, when applied in the server's library routines, reads all media IDs (library standard "Assigned Media IDs") from the server's permissions table that are assigned to a specific user or to the user group to which the specific user belongs according to the server's user group table, and from the server's allocation table that are assigned to the identifiers assigned to a specific user or to the user group to which the specific user belongs according to the server's user group table.

[0210] ● You can select a library standard that, when applied in a server library routine, reads all media IDs (library standard "Free Media ID") that are assigned to a specific user in the server's permissions table or to the user group to which the specific user belongs according to the server's user group table, and that are not assigned in the server's allocation table but are assigned to a specific user in the server's identifier table or to the user group to which the specific user belongs according to the user group table.

[0211] ● You can select library standards so that they can be used in library routines on the server:

[0212] First, identify all identifiers assigned to the user in the server's identifier table or to the user group the user belongs to according to the server's user group table. Then, determine which of these identifiers points to the identifier type that indicates the assignment of this identifier to a certain series, in order to determine all series of identifiers assigned to the user in the server's identifier table.

[0213] Then, read all media IDs stored in the server's media table, including those assigned to one of such defined series in the server's media table.

[0214] Then, using the determined media ID, the media ID that has not been assigned to the user or the user group to which the user belongs according to the server's user group table (library standard "new media ID to known series").

[0215] In a preferred embodiment, the UI library routine is initiated through user interaction with a user interface. In a preferred embodiment, the UI library routine is characterized by creating a filter button within the UI's GUI. In a preferred embodiment, the user presses the filter button in the GUI to create a selection window, which provides the user with factors influencing the creation of library criteria. Alternatively, the user pressing the filter button directly results in the generation of a library request signal with specific library criteria. In this embodiment, "filter button" is an abbreviation for "for creating a library request signal with specific library criteria."

[0216] For example, a GUI might contain filter buttons with specific labels, such as "All," which, when pressed by a user, generate a library request signal with a library standard selected in such a way that, when used in a server's library routine, it reads all media IDs stored in the server's media table (library standard "All"). Similarly, a GUI might contain filter buttons with specific labels, such as "My," which, when pressed by a user, generate a library request signal with a library standard selected in such a way that, when used in a server's library routine, it reads all media IDs assigned to a specific user in the permissions table or, according to the user group to which the specific user belongs, from the server's user group table (library standard "User Media ID"). For example, a GUI might contain a filter button with a specific label, such as "Assigned." When a user presses it, a library request signal is generated with a library standard selected in such a way that, when used in a server's library routine, it reads from the server's permissions table all media IDs (library standard "Assigned Media ID") that are assigned to a specific user in the permissions table or to the user group to which the specific user belongs according to the server's user group table, and are assigned in the server's allocation table to the IDs assigned to a specific user or to the user group to which the specific user belongs according to the server's user group table. For example, a GUI might have a filter button with a specific label, such as "Available." When a user presses it, a library request signal is generated with a library standard selected in such a way that, when applied in a server's library routine, it reads from the server's permissions table all media IDs (library standard "Free Media ID") that are assigned to a specific user in the permissions table or to the user group to which the specific user belongs according to the server's user group table, and are not assigned in the server's allocation table to the IDs assigned to a specific user or to the user group to which the specific user belongs according to the server's user group table.

[0217] UI library routines may include steps that use a GUI to display the media ID contained in the library signal to the user. UI library routines may also include steps that use a GUI to present the selection of the media ID contained in the library signal to the user.

[0218] In the first embodiment, the user interface can be designed such that:

[0219] ● Users can preferably use the GUI to generate library queries that include at least one library standard.

[0220] ● The user interface can generate library request signals containing the library's standards based on the library query, and can also transmit the library request signals.

[0221] ●The user interface responds to library request signals by transmitting and receiving library signals, and

[0222] ● Display to the user - preferably via GUI - the media IDs contained in the library signal, preferably all media IDs contained in the library signal.

[0223] In this embodiment, the memory requirements and computational workload on external devices necessary for the user interface can be kept low. The step of reading media IDs that conform to the library standard is performed on the server, from the media table and / or permissions table and / or allocation table on the server. The user interface only displays the media IDs contained in the library signal (preferably all), because the library signal only contains media IDs that conform to the library standard after being evaluated by the server.

[0224] In a second embodiment, the user interface can be designed to generate a library request signal, wherein a library standard is selected such that when used in a library routine on the server, all media IDs (library standard "all") stored in the server's media table are read. If the server receives a library request signal with library standard "all", the server reads all media IDs from the media table as part of its library routine, generates a library signal containing the media IDs or media IDs read in this manner, and emits this library signal. In this embodiment, the UI library routine may include the step of presenting all media IDs contained in the library signal to the GUI user. However, in this embodiment, the UI library routine may also include the step of using the GUI to present the user with a selection of media IDs contained in the library signal. In such an embodiment, the user can use the user interface to select which media ID should be displayed by the library signal conveyed to the user interface. This may result in increased memory requirements and computational workload for the UI on external devices, but it can reduce the number of signals to be exchanged because changing the filter standard and displaying the media ID corresponding to this filter standard can be done directly in the user interface without generating and transmitting a new library request signal with the changed library standard. Displaying only the selection of media IDs can also be used to adapt the amount of information to the available display area.

[0225] The user interface can be designed so that it generates and transmits the library request signal as part of the UI startup routine. This simplifies the operation.

[0226] In a preferred embodiment, the UI change routine includes a step of selecting a media ID. By selecting a media ID, the user chooses a media ID within the UI, which becomes part of the change signal during the execution of the UI change routine.

[0227] In a preferred embodiment, as part of the library routines, a media ID or multiple media IDs are displayed to the user in the GUI, from which the user can select at least one media ID by interacting with the GUI. For example, a content button is displayed to the user in a screen view, and the corresponding content button is assigned a media ID within the UI. The user can select a media ID by pressing a content button in the screen view.

[0228] In a preferred embodiment, the selection of a media ID triggers a UI change routine. In an alternative embodiment, after the media ID is selected, a check is performed to determine whether the selected media ID has already been assigned to a user or a user group to which the user belongs. This test will determine whether:

[0229] ● The selected media ID has been assigned to a user or a user group to which the user belongs. In this case, a UI change routine can be triggered.

[0230] ● The selected media ID has not yet been assigned to a user or the user group to which the user belongs, and then a UI extension routine can be triggered in it.

[0231] In a preferred embodiment, a change signal is generated in the UI change routine, which includes the media ID selected in this manner. In a first variant of this embodiment, the change signal is sent by the UI without any further selection steps after the media ID is selected. This version allows for rapid reassignment changes. In this type of version, the change signal either does not contain an ID, or it contains an ID selected in the selection step prior to selecting the media ID. If the change signal does not contain an identifier, assigning the selected media ID to an identifier may result from other circumstances, such as the selected media ID being a series of media IDs, and the user being assigned only an identifier from an identifier table belonging to that series of identifier types.

[0232] In a second variant of this embodiment, the UI change routine includes a step of selecting an identifier prior to the step of generating a change signal. As part of the identifier selection step, the UI change routine may execute a UI inventory routine.

[0233] In a preferred embodiment, the user interface (UI) has a UI inventory routine. The UI inventory routine can be executed independently. The UI inventory routine can be executed as part of a UI change routine. In a preferred embodiment, the UI inventory routine includes a step of receiving an inventory signal, the inventory signal including one or more identifiers. In a preferred embodiment, the UI inventory routine includes a step of sending an inventory request signal. In a preferred embodiment, the step of sending the inventory request signal precedes the step of receiving the inventory signal.

[0234] The inventory request signal may include inventory criteria. In a preferred embodiment:

[0235] ● You can select an inventory criterion so that when it is applied in the server's inventory routine, all identifiers stored in the server's identifier table are read, and these identifiers are assigned to a specific user in the identifier table or to the user group to which the specific user belongs based on the server's user group table (inventory criterion: "user identifier") and / or

[0236] ● You can select an inventory criterion so that when it is applied in the server's inventory routine, all identifiers stored in the server's identifier table are read, and these identifiers are assigned to a specific user or to the user group to which the specific user belongs according to the server's user group table, and a certain identifier type (inventory criterion: "specific user identifier") and / or assigned in the identifier table.

[0237] ● You can select an inventory standard so that when applied in the server's inventory routine, it reads all identifiers stored in the server's identifier table, assigns these identifiers to a specific user in the identifier table, or assigns them to the user group to which the specific user belongs based on the server's user group table, and assigns media IDs (inventory standard: "free user identifier") and / or not assigned in the server's allocation table.

[0238] ● You can select an inventory criterion so that when applied in the server's inventory routine, all identifiers stored in the server's identifier table are read, and these identifiers are assigned to a specific user or to the user group to which the specific user belongs based on the server's user group table. Additionally, a media ID (inventory criterion: "variable user identifier") that differs from the one used during the query can be assigned in the server's allocation table.

[0239] ● You can select an inventory criterion to read all identifiers stored in the server's identifier table when applied in the server's inventory routine. These identifiers belong to a specific user or the user group a specific user belongs to according to the server's user group table. They can also be assigned media IDs in the server's allocation table that are different from the media IDs available at the time of query, corresponding to a specific identifier type or a specific ID type selection (Inventory Criterion: "Specific Type Variable User Identifier") and / or

[0240] ● You can select an inventory standard so that when it is applied in the server's inventory routine, all device identifiers stored in the server's user table or user group table are read and assigned to a specific user or the user group to which the specific user belongs (inventory standard: "user device identifier").

[0241] UI inventory routines may include steps that present the identifier contained in the inventory signal to the user via a GUI. UI inventory routines may also include steps that present the selection of the identifier contained in the inventory signal to the user via a GUI.

[0242] In the first embodiment, the user interface can be designed such that:

[0243] ●Users - preferably using the GUI - can generate inventory requests that include at least one inventory criterion.

[0244] ● The user interface can generate an inventory request signal containing the inventory criteria based on the inventory request, and can transmit the inventory request signal.

[0245] ●The user interface responds to the transmission and reception of inventory request signals, and

[0246] ● Display to the user – preferably using a GUI – the identifiers contained in the inventory request signal, preferably all identifiers contained in the inventory request signal.

[0247] In such an embodiment, the memory requirements on the external devices necessary for implementing the user interface, as well as the computational workload on those external devices, can be kept low. The step of reading the identifiers corresponding to the inventory criteria is performed on the server, from an identifier table, user table, or user group table on the server. The user interface presents only those identifiers contained in the inventory signal (preferably all identifiers), because the inventory signal only includes those identifiers that meet the inventory criteria after server evaluation.

[0248] In a second embodiment, the user interface can be designed to generate an inventory request signal, wherein the inventory criterion is selected such that when applied to the server's inventory routine, all identifiers stored in the server's identifier table are read, and these identifiers are assigned to a specific user or, according to the server's user group table, to the user group to which the specific user belongs (inventory criterion: "User ID"). If the server receives an inventory request signal with the inventory criterion "User ID", then, as part of its inventory routine, the server reads all identifiers stored in the server's identifier table, which are assigned to a specific user or, according to the server's user group table, to the user group to which the specific user belongs, and generates and sends an inventory signal containing the identifiers read in this manner. In this embodiment, the UI inventory routine may include the step of displaying all identifiers contained in the inventory signal to the user via a GUI. However, the UI inventory routine in this embodiment may also include the step of displaying a selection of identifiers contained in the inventory signal to the user via a GUI. In such an embodiment, the user can use the user interface to select which identifiers should be displayed by the inventory signal to the user interface. This will increase the memory requirements and computational load on the UI on external devices, but will reduce the number of signals to be exchanged, because the modification of inventory standards and the display of the identifiers corresponding to those standards can be done directly in the user interface without generating and sending new inventory request signals with modified inventory standards.

[0249] In a preferred embodiment, the UI change routine includes the step of executing a UI inventory routine. In a preferred embodiment, the step of executing the UI inventory routine is performed after the step of selecting a media ID. In a preferred embodiment, the media ID selected during the media ID selection step affects the formation of the inventory criteria. In a preferred embodiment, the UI specifies that, for a selected media ID assigned to a specific series, an inventory criterion is selected such that, when used in the server's inventory routine, all identifiers stored in the server's identifier table are read, these identifiers are assigned in the identifier table to a specific user or, according to the server's user group table, to the user group to which the specific user belongs, and a specific identifier type, i.e., the identifier type associated with the specific series, is assigned in the identifier table. With this version, the user can only select his / her identifiers belonging to the selected media ID series in the GUI. For example, if the user selects the series "Benjamin Blümchen". Using the sequence as the media ID, the inventory standard can be selected so that the inventory signal only contains the data assigned to the series "Benjamin Blümchen". The identifier.

[0250] In a preferred embodiment, the UI inventory routine and / or UI change routine includes a step of selecting an identifier. By selecting an identifier, the user selects an identifier within the UI, which becomes part of a change signal during the execution of the UI change routine.

[0251] In a preferred embodiment, as part of a UI inventory routine, particularly if this is part of a UI change routine, one or more identifiers are displayed to the user in the GUI, from which the user can select at least one identifier by interacting with the GUI. For example, identifier images are displayed to the user in a screen view, and corresponding identifier images are assigned to identifiers within the UI. The user can select an identifier by touching the identifier image in the screen view.

[0252] After selecting an identifier, the UI change routine may include a step of generating a change signal containing the selected media ID and the selected identifier. The UI can then transmit the change signal generated in this way.

[0253] In a preferred embodiment, the user interface (UI) has UI extension routines. A UI change routine causes the sending of an extension signal. The extension routine can be performed independently. The UI extension routine can be executed as part of a UI change routine. In a first embodiment, the extension signal contains the user and / or user group whose assignment will be changed in the server's permissions table, and the media ID to be assigned to the user and / or user group. In a second embodiment, the structure of the extension signal can be chosen such that the extension signal contains information about the media ID to be assigned to the user in the server's permissions table. The assignment to the user is then determined by other circumstances, such as when the server receives an extension signal initiated by the user interface upon user login.

[0254] If a check performed after selecting a media ID reveals that the selected media ID has not yet been assigned to a user or the user group to which the user belongs, a UI extension routine can be triggered.

[0255] In a preferred embodiment, the user is provided with the possibility of generating extended signals as part of a UI extension routine in the GUI within the context of a media ID that the user wants to assign to themselves or their user group. For example, the media ID and an action button can be displayed to the user in a screen view.

[0256] In the first embodiment, pressing the action button causes an extended signal to be generated and sent. This embodiment is particularly suitable for situations where a user can assign themselves a new media ID for free or where the user has a credit status on the server. The UI (preferably in a GUI) may request user confirmation before sending the extended signal, especially when assigning a selected media ID to the user results in a change in the user's credit status.

[0257] In the second embodiment, pressing the action button can cause the generation and transmission of an extended signal, as well as the first step of generating an enable signal. In one embodiment, where media IDs are assigned to users or user groups in the server's permission table based on whether the server receives an enable signal, pressing the action button can cause the first step of generating an enable signal, such as generating a start signal for a transmission routine, for example, for... The account start signal can be used to generate an enable signal. Alternatively, as an alternative to the parallel generation of extended signals, the transmission of extended signals, and the triggering of the first step for generating the enable signal, it can be stipulated that the step of triggering the first step for generating the enable signal is performed first, and the steps of generating and sending extended signals are only executed when the UI and / or the server receives the enable signal.

[0258] In a preferred embodiment, the library signal of the media ID included in the library signal contains information about whether the media ID has been assigned to a user or a user group to which the user belongs in the server's permissions table. This configuration allows the user to be shown, in the UI, and particularly and preferably in the GUI, whether a media ID already belongs to him / her. If the media ID is displayed to the user as a content button in the screen view, the content button for a media ID that already belongs to the user can look different from the content button for a media ID that does not yet belong to the user. For example, the content button for a media ID that already belongs to the user can be displayed as a check mark relative to the content button for a media ID that does not belong to the user. This configuration also allows checking whether the selected media ID has been assigned to the user or a user group to which the user belongs or does not belong when the media ID is selected.

[0259] In a preferred embodiment, the following actions are taken to prepare for executing the UI change routine:

[0260] ●Execute the UI inventory routine,

[0261] ● Select an identifier in the UI inventory routine associated with a specific collection.

[0262] ●Execute a UI library query, select the library standard so that when used in the server's library routines, it reads all media IDs stored in the server's media table. These IDs are assigned as metadata to the series in the media table.

[0263] ● Display the media IDs contained in the library signals to the user in the GUI, from which the user can select at least one media ID by interacting with the GUI.

[0264] Selecting a media ID causes a UI change routine to be executed. A change signal can be generated in the UI change routine, which includes the selected identifier and the selected media ID. In this way, users have the opportunity to inspect the identifier of a series, which media IDs are in the series (what sequences are in the series), and assign another or different media ID of this series to the identifier belonging to this series within the GUI.

[0265] In a preferred embodiment, the user interface has a UI startup routine. In a preferred embodiment, the UI startup routine includes a step of establishing a communication channel with the server. The communication channel is particularly and preferably via the Internet. In a preferred embodiment, the UI startup routine includes a step of identifying a user who is logged into the server.

[0266] In a preferred embodiment, the user interface has a UI locking routine. The UI locking routine issues a locking signal. The locking signal may include a user and / or a user group, as well as an identifier and a locking notification. Alternatively, the locking signal may include a user and / or a user group, as well as a device identifier and a locking notification.

[0267] When a user assigns a lock notification to an identifier or device identifier using the UI, preferably within the UI's GUI, a UI lock routine can be executed. In a preferred embodiment, the UI displays the identifier to the user and, within the context of displaying the identifier, provides interactive means, such as buttons or sliders, which the user can use to assign a lock notification to the identifier. In a preferred embodiment, the device identifier is displayed to the user along with the UI, and, within the context of displaying the device identifier, interactive options, such as buttons or sliders, are available for the user to assign a lock notification to the device identifier. Assigning a lock notification can trigger the generation and transmission of a lock signal.

[0268] In a preferred embodiment, the user interface has a UI unlock routine. The UI unlock routine sends an unlock signal. The unlock signal may include the user and / or user group, as well as an identifier and an unlock notification. Alternatively, the unlock signal may include the user and / or user group, as well as a device identifier and an unlock notification.

[0269] When a user unlocks an existing lock notification using the UI, preferably within the GUI of an identifier or device identifier, a UI unlock routine can be executed. In a preferred embodiment, the UI displays the identifier to the user and provides interactive means, such as a button or slider, within the context of displaying the identifier, allowing the user to unlock the lock associated with the identifier. In a preferred embodiment, the device identifier is displayed to the user along with the UI, and within the context of the device identifier's display, interactive options, such as a button or slider, can be used by the user to remove the lock notification assigned to the device identifier. Removing the lock notification can trigger the generation and transmission of an unlock signal.

[0270] In a preferred embodiment, the user interface has a UI identifier table or can generate a temporary UI identifier table. In a preferred embodiment, after generating and sending an inventory request signal with the inventory criterion "user identifier," the user interface writes all identifiers read from the received inventory signals into the UI identifier table. In a preferred embodiment, identifier types are assigned to corresponding identifiers in the UI identifier table. In a preferred embodiment, in all described embodiments, the UI identifier table is queried instead of the server identifier table. In this way, steps requiring a connection to the server in any situation can be advantageously performed, even if a connection cannot or should not be established, or if a connection cannot or should not be established at a sufficient speed or quality.

[0271] In a preferred embodiment, the user interface has a UI permission table or can generate a temporary UI permission table. In a preferred embodiment, after generating and sending a library request signal in which the library criterion is "all", the user interface writes all media IDs it has read from the received library signal into the UI permission table.

[0272] In a particularly preferred embodiment of this implementation:

[0273] ● Users (preferably using a GUI) can generate library requests that include at least one library standard.

[0274] ● The user interface reads all media IDs that conform to the library's standards from the UI permission table, and,

[0275] The user interface (preferably via GUI) displays all media IDs read from the UI permissions table to the user.

[0276] In such an embodiment, the memory requirements and computational workload on the external device required to implement the user interface are slightly higher because the UI permission table is stored in the external device's memory, and the computational workload for reading the media ID corresponding to another library standard must be maintained. However, in this way, steps that require a connection to the server in any case can be advantageously performed, even if a connection cannot or should not be established, or cannot or should not be established at a sufficient speed or quality.

[0277] In a preferred embodiment, the user interface (UI) has a UI actual state routine. In a preferred embodiment, the UI actual state routine includes a step of receiving an actual state signal, the actual state signal comprising:

[0278] ● One media ID or multiple media IDs

[0279] ● One or more identifiers

[0280] ●Information regarding assigning the corresponding media ID to the corresponding identifier.

[0281] In a preferred embodiment, the UI state routine includes a step of sending a state request signal. In this preferred embodiment, the step of sending the state request signal precedes the step of receiving the state signal. The state request signal may include a query criterion, such as an identifier.

[0282] UI real-state routines may include steps that present the user with information contained in real-state signals regarding the assignment of corresponding media IDs to corresponding identifiers via the GUI.

[0283] In the first embodiment, the user interface can be designed to enable

[0284] ●Users – preferably via GUI – can generate actual status queries containing at least one query criterion.

[0285] ● The user interface can generate a real-state request signal containing the query criteria based on this real-state request, and can transmit the real-state request signal.

[0286] ●The user interface responds to the transmission of the actual status request signal and receives the actual status signal.

[0287] ● Display to the user – preferably via a GUI – information, preferably all information, contained in the actual status signal regarding the assignment of the corresponding media ID to the corresponding identifier.

[0288] In such an embodiment, the memory requirements and computational workload on external devices necessary for the user interface can be kept low. The step of reading the media ID to identifier allocation from the allocation table matching the query criteria is performed on the server and from the allocation table on the server. The user interface presents the user with information contained in the actual status signal regarding the allocation of the corresponding media ID to the corresponding identifier (preferably all identifiers), because the actual status signal only contains information about the allocation corresponding to the query criteria after server evaluation.

[0289] In a second embodiment, the user interface can be designed to generate and send a real-state request signal with the query criterion "all". If the server receives a real-state request signal with the query criterion "all", as part of its real-state routine, the server reads all allocations of media IDs to identifiers belonging to a specific user or, according to a user group table, to a user group to which the specific user belongs, generates a real-state signal containing the read information about assigning the corresponding media ID to the corresponding identifier, and sends the real-state signal. The user interface can be configured to perform the generation of the real-state request signal, where the query criterion is "all", and transmit the real-state request signal as part of a UI startup routine. The user interface can present the information contained in the real-state signal about assigning the corresponding media ID to the corresponding identifier to the user. Alternatively, the user interface can write all the information contained in the real-state signal about assigning the corresponding media ID to the corresponding identifier to a UI allocation table.

[0290] In a preferred embodiment, the user interface has a UI allocation table or can generate a temporary UI allocation table. A media ID is assigned to at least one identifier in the UI allocation table. Preferably, the UI allocation table contains several identifiers, with at least one media ID assigned to a corresponding identifier in the UI allocation table. In a preferred embodiment, in all the described embodiments, the UI allocation table is queried instead of the server allocation table. In this way, steps requiring a connection to the server in any situation can be advantageously performed, even if a connection cannot or should not be established, or if a connection cannot or should not be established at a sufficient speed or quality.

[0291] In a preferred embodiment, the user interface has a UI user maintenance routine. The UI user maintenance routine can send user maintenance signals. These signals can include users and user groups. By sending a user maintenance signal, the server receiving the signal can be prompted to change the user's assignment to a user group in the user group table.

[0292] In a preferred embodiment, the user maintenance signal may include an email address. When the UI user maintenance routine is executed, the user may be prompted to enter their email address via the UI, such as through a UI GUI.

[0293] In a preferred embodiment, the user interface has a UI player maintenance routine. The UI player maintenance routine can cause a player maintenance signal to be issued. The player maintenance signal may include a user and / or user group, as well as a device identifier. By sending a player maintenance signal, a server receiving such a signal can change the allocation of the device identifier to the user and / or user group in a user table or user group table.

[0294] In a preferred embodiment, the system according to the invention has a device for reproducing media files, particularly for reproducing audio information. The device for playing media files is also called a playback device.

[0295] In a preferred embodiment, the playback device has

[0296] -Speaker or speaker connection

[0297] - A sensor that can detect properties or changes in properties of its environment within its environmental area, and

[0298] - The control unit can control the speaker or speaker connection to reproduce media files, especially audio information, if the sensor detects a specific property or a change in a specific property of the environment within its environmental area, or if the control unit detects a change in a specific property detected by the sensor.

[0299] In a preferred embodiment, the playback device has no display or display connection and is designed only for playing audio files, not for playing video files.

[0300] In a preferred embodiment, the playback device has a memory. In a preferred embodiment, an AV (Playback Device) allocation table is stored in the playback device's memory, and media IDs and / or media files can be assigned to identifiers through the AV allocation table in the playback device's memory. The assignment of media IDs and / or media files to identifiers in the AV allocation table in the playback device's memory can be limited to identifying the storage location of media files assigned to identifiers in the playback device's memory or another memory. In this way, the control unit of the playback device can determine which location in the playback device's memory or additional memory the media file is stored in by reading the AV allocation table in the playback device's memory, and then use the control unit to control speakers or speaker connections based on this. Media IDs and / or media files can also be assigned to IDs in the AV allocation table in the playback device's memory by storing pointers to media files in the AV allocation table. For example, such a pointer could be a URL. The control unit of the playback device can use reading such pointers to download or stream media files not stored in the playback device's memory from another storage location, such as from a server according to the invention.

[0301] In a preferred embodiment, the version information, preferably a timestamp, is an identifier in a playback device allocation table in the memory allocated to the playback device.

[0302] In a preferred embodiment, the identifier in the playback device allocation table in the memory to be updated for the playback device can be used.

[0303] In a preferred embodiment, a playback device update routine is provided in the playback device. The update routine sends a real-time status signal of the playback device. The real-time status signal of the playback device includes...

[0304] ● One or more identifiers

[0305] ● Version information assigned to the corresponding identifier in the playback device allocation table, particularly the timestamp assigned to the corresponding identifier in the playback device allocation table, and / or

[0306] ● The media ID assigned to the corresponding identifier in the playback device allocation table.

[0307] To generate the actual status signal of the playback device, the control unit of the playback device reads the playback device allocation table. In a preferred embodiment, the control unit in the device update routine reads the playback device allocation table completely. The actual status signal of the playback device then includes:

[0308] ● Any identifier stored in the playback device allocation table

[0309] ● Version information assigned to the corresponding identifier in the playback device allocation table, particularly the timestamp assigned to the corresponding identifier in the playback device allocation table, and / or

[0310] ● The media ID assigned to the corresponding identifier in the playback device allocation table.

[0311] In a preferred embodiment, the playback device update routine includes receiving an update signal. The update signal may contain one or more identifiers.

[0312] In a preferred embodiment of the playback device update routine, the control unit reads an update signal and modifies the playback device allocation table by assigning each identifier contained in the update signal to an update requirement. If the control unit later reads an entry for an identifier in the playback device allocation table, for example, to play a media file assigned to that identifier, and then determines that the identifier is associated with an update requirement, the control unit can execute a request routine to initiate it. Using the request routine, the control unit can load the media file from the server into the playback device's memory. This reduces the amount of communication between the playback device and the server. The playback routine does not download the media file to the identifier contained in the update signal until that media file is actually used in the playback device. Until then, the fact that a different / new media file with an identifier exists is stored in the playback device only by setting an update request.

[0313] In a preferred embodiment, the update signal includes one or more identifiers and a media file for each identifier. Thus, if the playback device receives an update signal indicating that the media file has changed for some identifier, the playback device can immediately update the media file stored therein.

[0314] In a preferred embodiment, the update signal includes one or more identifiers and a media ID for each identifier. In a preferred embodiment of the playback device update routine, the control unit reads the update signal and modifies the playback device allocation table by assigning the corresponding identifier contained in the update signal to the media ID sent to the identifier in the update signal. In a preferred embodiment, the control unit that has been assigned a new media ID allocates the update request.

[0315] In a preferred embodiment, a request routine is provided in the playback device. The request routine causes a playback device request signal to be sent. The playback device request signal includes an identifier. In a preferred embodiment, the request signal includes a device identifier of the playback device. In a preferred embodiment, the playback device request signal includes an indication that an update is needed.

[0316] In a preferred embodiment, a playback device request signal can be generated if the sensor detects a specific attribute or a change in a specific attribute within its environmental area, or if the control unit detects a change in a specific attribute determined by the sensor, particularly if the sensor recognizes the presence of an identifier carrier and identifies the identifier of the identifier carrier. In a preferred embodiment, the playback device request signal includes the identifier that the sensor has already read from the identifier carrier.

[0317] In a preferred embodiment, a playback device request signal is always generated if the sensor detects a specific attribute or a change in a specific attribute within its environmental area, or if the control unit detects a change in a specific attribute determined by the sensor, particularly if the sensor detects the presence of an identifier and identifies the identifier carrier. The playback device request signal may be sent with a delay, especially when the playback device does not have a communication channel to the server at the time the playback device request signal is generated.

[0318] In a preferred embodiment, the control unit checks in a request routine whether an entry for the sensor-identified identifier exists in the playback device allocation table. If no entry exists, or if an entry exists indicating an update is needed, the control unit generates a playback device request signal with an indication that an update is required.

[0319] If the server receives a playback device request signal indicating an update requirement, the server checks which media IDs have been assigned identifiers in the allocation table and generates a response signal. The response signal contains the media file and / or a pointer assigned to that media ID in the media table. The response signal preferably contains an identifier included in the playback device request signal, and preferably contains the media ID, and preferably contains version information associated with the media file in the media table, particularly and preferably a timestamp. When the control unit of the playback device with the response signal receives the media file or pointer and the identifier assigned to that media file or pointer, the control unit stores the media file in the playback device's memory and updates the allocation table by adding the identifier from the allocation table, allocating the storage location of the media file in the playback device's memory, or allocating a pointer to the identifier in the allocation table. In a preferred embodiment, the control unit may reset the set update request. In a preferred embodiment, the control unit of the identifier may assign version information, particularly a timestamp, which the control unit transmits to the control unit along with the media file. In a further embodiment, the control unit may assign a self-generated timestamp to the identifier.

[0320] This embodiment allows for maintaining the simplicity of the playback device in terms of both its structure and the software executed by the device's control unit. The playback device already operates within the system according to the invention if it can perform two core functions, namely...

[0321] - Read the identifier from the identifier carrier and execute the request routine. If an entry for the identifier already exists in the playback device allocation table stored in the playback device's memory, and in a preferred embodiment, there is no need to update the identifier to be assigned, the control unit is simply designed to provide information about the identifier assigned in the playback device allocation table to read the media file and use information about the media file, particularly about its storage location, to read or stream the media file from the storage location, thereby controlling the speaker or speaker connection. Alternatively, if the identifier read does not exist in the playback device allocation table in the device's memory, the identifier is written into the playback device allocation table in the device's memory, and a playback device request signal is generated.

[0322] -Execute the playback device update routine.

[0323] This embodiment therefore differs from the method selected in US2018 / 0353869 A1. There, under the heading "Remote Management of Controlled Object 120," a routine is described regarding how a user can directly access the device via an external device (e.g., a smartphone, tablet, or external computer, such as a laptop). In this routine, the possibility of adjusting information stored in an identifier carrier should be created. Therefore, in the process provided in US2018 / 0353869 A1, the device must be powerful enough to understand requests sent to it by an external device to change the information stored in the identifier carrier and translate them into a change routine to be executed, thereby actively intervening and changing the information stored in the identifier carrier. This places high demands on the device's programming and electrical equipment. However, as described above regarding the preferred embodiment, the system according to the invention and the server according to the invention make it possible to simply equip the playback device itself. In the inventor's preferred embodiment, complex computational steps, such as version information comparison, are outsourced to the server.

[0324] In one embodiment, media files stored in the memory of a playback device may have different formats. In a preferred embodiment, media files stored in the memory of a playback device have the same format. In an alternative embodiment, media files stored in the memory of a playback device have formats from a set of formats, which particularly and preferably include no more than 20, particularly and preferably no more than 10, particularly and preferably no more than 5 different formats.

[0325] In a preferred embodiment, a playback device startup routine is provided in the playback device. In a preferred embodiment, the playback device executes the playback device startup routine when the playback device is turned on, where being turned on is also understood to mean waking up from a power-saving state.

[0326] As part of the playback device's startup routine, the playback device can request the server to notify it of the current time. This allows the player to remain simple, as the player itself does not need a clock.

[0327] As part of the playback device startup routine, the playback device may request the server to notify it of the current firmware state or check whether the current firmware state is running on the playback device. In a preferred embodiment, as part of the playback device startup routine, the playback device transmits information about its firmware state to the server. The server checks whether the firmware version is up-to-date and, if necessary, transmits an updated firmware version to the playback device.

[0328] As part of the playback device startup routine, the player can also execute the playback device update routine.

[0329] In a preferred embodiment, the playback device has an operating element. In a preferred embodiment, the playback device executes a playback device update routine when the control element is activated, particularly and preferably when the control element is actuated in a certain way, particularly and preferably for a certain period of time. For example, if the control element is pressed for a period of time, such as more than 3 seconds.

[0330] The system according to the present invention has a server according to the present invention and a user interface according to the present invention.

[0331] The system according to the invention has a server according to the invention, a user interface according to the invention, and an external device on which the user interface can be executed.

[0332] The system according to the invention has a server and an identifier carrier according to the invention, wherein the identifier carrier has an identifier that can be read by a reading device.

[0333] The system according to the invention has a server and an identifier carrier according to the invention, wherein the identifier carrier has an identifier that can be read by a reading device, and a user interface according to the invention.

[0334] The system according to the invention has a server and an identifier carrier according to the invention, wherein the identifier carrier has an identifier that can be read by a reader, a user interface according to the invention, and an external device on which the user interface can be executed.

[0335] The system according to the present invention has a server and a playback device according to the present invention.

[0336] The system according to the present invention has a server according to the present invention, as well as a playback device and a user interface according to the present invention.

[0337] The system according to the invention has a server and a playback device according to the invention, as well as a user interface according to the invention and an external device on which the user interface can be executed.

[0338] The system according to the invention has a server and a player according to the invention, and an identifier carrier, wherein the identifier carrier has an identifier that can be read by a reading device.

[0339] The system according to the invention includes a server and a playback device according to the invention, an identifier carrier having an identifier that can be read by a reading device, and a user interface according to the invention.

[0340] The system according to the invention comprises a server and a playback device according to the invention, and an identifier carrier, wherein the identifier carrier has an identifier that can be read by a reading device, as well as a user interface according to the invention and an external device on which the user interface can be executed.

[0341] In a preferred embodiment, the signal containing the identifier includes a placeholder other than or in place of the identifier. In a preferred embodiment, change signals, inventory signals, actual status signals, pressure signals, lock signals, unlock signals, update signals, response signals, inventory request signals, extension signals, playback device actual status signals, and / or playback device request signals include a placeholder other than or in place of the identifier. If, in a preferred embodiment, the identifier is a long sequence of letters and / or numbers and / or special characters of a UID, UUID, or GUID or other type, it may be desirable to provide the user with a placeholder for presentation in the UI, preferably for presentation in the GUI, and for interaction with the UI, preferably for interaction with the GUI; the placeholder is preferably shorter than the sequence of letters and / or numbers and / or special characters of the identifier. The UI, particularly the GUI, may allow the user to select a placeholder for the identifier. This placeholder may be stored in an identifier table of the identifier.

[0342] In a preferred embodiment, the signal containing the device identifier includes a placeholder in addition to the device identifier or a placeholder for the device identifier. In a preferred embodiment, besides the identifier or a placeholder for the identifier, it also includes inventory signals, pressure signals, lock signals, unlock signals, player maintenance signals, inventory request signals, and / or playback device request signals. If, in a preferred embodiment, the device identifier is managed as a UID, UUID, or GUID, or as another type of long sequence of letters and / or numbers and / or special characters, it may be desirable for the user to represent it in the UI, preferably for representation in the GUI and interaction with the UI, preferably for interaction with the GUI, to specify a placeholder that is preferably shorter than the sequence of letters and / or numbers and / or special characters of the device identifier. The UI, particularly the GUI, allows the user to select a placeholder for the device identifier. This placeholder can be stored in a user table and / or user group table for the device identifier.

[0343] In a preferred embodiment, the signal containing the media ID includes a placeholder in addition to the media ID or a placeholder for the media ID. In a preferred embodiment, in addition to the media ID or a placeholder for the media ID, the following are placeholders: change signal, library signal, extension signal, release signal, real-state signal, update signal, response signal, library request signal, extension signal, real-state signal of the playback device, and playback device request signal. If, in a preferred embodiment, the media ID is managed as a UID, UUID, or GUID, or as another type of long sequence of letters and / or numbers and / or special characters, it may be desirable for the user to display a placeholder in the UI, preferably for use in the GUI, and for interaction with the UI, preferably for interaction with the GUI, to specify a placeholder that is preferably shorter than the sequence of letters and / or numbers and / or special characters of the media ID. The UI, particularly the GUI, allows the user to select a placeholder for the media ID. This placeholder can be stored in the media table of the media ID.

[0344] The invention is described in this specification within the context of signals that trigger queries from tables, primarily referring to users and their respective user groups and / or reference users and / or user groups according to a user group table. This is particularly true for extension signals, pressure signals, lock signals, unlock signals, and / or player maintenance signals. This version of the preferred embodiment is preferred because it is assumed that users are generally interested in being able to see all identifiers, media IDs, or device identifiers associated with them.

[0345] In these embodiments, but also as standalone embodiments, special embodiments are also possible, in which the signal queries only the user; then, the description in the signal context applies if the references to the user and the user group to which the user belongs, and / or the references to the user and / or user group, are changed to references to the (only) user and not to the user group; this is especially true for extended signals, loading signals, locking signals, unlocking signals, and / or playback device maintenance signals. Such special embodiments are useful if a user is particularly interested in assignments to themselves (preferably their own), but may also be particularly interested in assignments to another user who allows them to view their assignments, for example, if users within the same household are allowed to view each other's assignments. Therefore, the UI (preferably via a GUI) provides the user with the option to choose whether they wish to view all assignments affecting them and their user group, or only assignments to a specific user (not assignments to a user group). Embodiments where user groups are not intended to be created are also possible. The description in the signal context then applies if the references to the user and the user group to which the user belongs, and / or the references to the user and / or the user group, are changed to references to the user (only) and not to the user group, based on the user group table; this is especially true for extension signals, demand signals, lock signals, unlock signals, and / or playback device maintenance signals.

[0346] In these embodiments, but also as standalone embodiments, special embodiments are possible, in which the signal queries only the user; then, the description in the signal context applies when references to the user and the user group to which the user belongs, and / or references to the user and / or user group, are changed to references to the user group (only) instead of individual users, according to the user group table; this is especially true for extended signals, loading signals, locking signals, unlocking signals, and / or playback device maintenance signals. This special embodiment is useful if the user is particularly interested in the assignments to user groups. Therefore, the UI, preferably via a GUI, can provide the user with the option to choose whether they wish to view all assignments related to themselves and their user groups, or only assignments to user groups (no assignments to individual users). Embodiments that do not intend to use individual users and only user groups are also possible. In these embodiments, each user can be assigned to at least one user group, whereby such user groups can also consist of individual users. Then, the description in the signal context should apply, provided that the references to users and the user groups to which users belong, and / or the references to users and / or user groups, are changed to references to (only) user groups instead of users, based on the user group table; this is especially true for extended signals, load signals, lock signals, unlock signals, and / or playback device maintenance signals.

[0347] In this specification, the invention is used in the context of standards, particularly those included in request signals, primarily referring to users and their respective user groups according to a user group table and / or to the described user and / or user group. This is particularly true for library standards and library request signals containing library standards, inventory standards and inventory request signals containing inventory standards, inventory standards and query standards, and actual status request signals containing query standards. This embodiment is preferred because it is assumed that users are generally interested in being able to see all identifiers, media IDs, or device identifiers associated with them.

[0348] In these embodiments, but also as standalone embodiments, specific embodiments are also possible, in which the standard and the signal containing it only query the user; then, the description in the context of the standard and the signal containing them applies under the condition that references to the user and the user group to which the user belongs, and / or references to the user and / or user group, are changed to references to the (only) user and not to the user group; this is especially true for library standards and library request signals containing library standards, inventory standards and inventory request signals containing inventory standards, and query standards and actual status request signals containing query standards. This type of specific embodiment is useful if a user is particularly interested in an assignment to a user (preferably himself), but may also be particularly interested in assignments to another user who allows him to view his assignments, for example if users within the same household are allowed to view each other's assignments. Therefore, the UI, preferably via a GUI, provides the user with the option of whether he wants to view all assignments affecting him and his user group, or only assignments to a specific user (no assignments to a user group). Embodiments that do not intend to create user groups are also possible. Then, the description in the context of standards and the signals that contain them is valid under the condition that references to users and user groups to which users belong, and / or references to users and / or user groups, are changed to references to (only) users and not to user groups; this is especially true for library standards and library request signals that contain library standards, inventory standards and inventory request signals that contain inventory standards, query standards and actual status request signals that contain query standards.

[0349] In these embodiments, but also as standalone embodiments, special embodiments are also possible, in which the standard and the signal containing it query only user groups; then, the description in the context of the standard and the signal containing them applies when references to users and user groups to which users belong, and / or references to users and / or user groups, are changed to references to user groups (only) rather than references to individual users; this is especially true for library standards and library request signals containing library standards, inventory standards and inventory request signals containing inventory standards, and query standards and actual status request signals containing query standards. This type of special embodiment is useful if the user is particularly interested in assignments to user groups. Thus, the UI, preferably via a GUI, can provide the user with the option to view all assignments related to him and his user groups, or only assignments to user groups (without assignments to individual users). Embodiments that do not intend to use individual users and only user groups are also possible. In such embodiments, each user can be assigned to at least one user group, thereby such user groups can also consist of individual users. Then, the description in the context of standards and the signals that contain them applies when references to users and the user groups to which users belong, and / or references to users and / or user groups, are changed to references to (only) user groups and not to users, based on the user group table; this is especially true for library standards and library request signals that contain library standards, inventory standards and inventory request signals that contain inventory standards, query standards, and actual status request signals that contain query standards.

[0350] A reference to a user in a signal can be established by the fact that the user or information identifying the user is contained within the signal, for example, by placing it somewhere within the signal or by prefixing it with a keyword. However, a reference to a user in a signal can also be established by having a designated communication channel between the sender (e.g., the UI) and the receiver (e.g., the server) of the signal, which individually identifies each signal sent through this communication channel as originating from a specific user. The invention can then be implemented in such a way that the user from whom the signal originates serves as a reference to the user in the signal. For example, a user could establish a designated communication channel between the UI and the server, log in to the UI through this channel, and then log in to the server from the UI.

[0351] If this specification explains that devices (especially servers, external devices, playback devices) read information from tables, this can also be achieved by determining information from tables indirectly rather than directly, for example, through conversion or other intermediate steps, regardless of whether more information from other tables is used.

[0352] In a preferred embodiment, the playback device has a device identifier and means for transmitting signals dependent on the device identifier. The device identifier may be an identifier for a processor or memory chip. Alternatively, the device identifier may be an identifier provided separately from the processor or memory chip, such as a tag, like an RFID transponder, provided as part of the playback device. In a preferred embodiment, the device identifier is selected to uniquely identify the playback device relative to an external control unit, such as a server.

[0353] Devices used to transmit signals that depend on a device identifier can transmit wired signals, for example, if the playback device is connected to an external control unit via a cable. However, devices used to transmit signals that depend on a device identifier can also transmit radio signals, such as signals according to NFC, Bluetooth, or WLAN standards, for example, if the playback device is integrated into a radio network.

[0354] The provision of a device identifier and the possibility of transmitting signals dependent on the device identifier to, for example, an external control unit (e.g., a server) enable the pre-determining of further data traffic between the playback device and the external control unit and / or external storage to allow for defined permission dependencies. This description illustrates embodiments of the invention where a playback device is used to play content (particularly audiobooks, music or other audio information, images, video, or 3D information), but where data packets are transferred from external storage to the playback device's memory before playback. Depending on the chosen data system or data structure, the data packet may contain all or part of the content to be played. The provision of a device identifier and the possibility of transmitting signals dependent on the device identifier can now be used to request authorization checks indicating that a playback device with that device identifier is authorized to receive data packets and transfer them from the playback device to the external control unit and / or external storage.

[0355] This type of identifier for a playback device within a network or system can be used to bill users of the playback device for transmitting data packets to it. Therefore, the transmission of individual data packets, such as those required for playing an audiobook, can be billed separately. A uniform rate billing system is also conceivable. Alternatively, the likelihood of downloading such data packets could be linked to time or time periods, such as in the sense of "borrowing an audiobook."

[0356] This type of identification of a playback device within a network or system can also be used to transmit control information about the operation of the playback device to the playback device. This information is stored as data packets in external storage until the playback device logs into the system with the corresponding device identifier. For example, if such a playback device is integrated into a system designed to allow a third party (e.g., a parent) to limit the usage time of the playback device or the maximum volume of audio information played through a program (user interface) on the third party's smartphone or tablet, embodiments are conceivable where the limits generated on the smartphone or tablet are stored as data packets in external storage or an external control unit such as the cloud (server). The device identifier allows the third party to notify the external storage device or external control unit which playback device the data packet is intended for. If the playback device logs in using the device identifier, the data packet is then transmitted to the playback device.

[0357] In a preferred embodiment, the system according to the invention provides an external memory from which data packets can be transferred from the external memory to the memory of the playback device and / or from the playback device to the external memory if the sensor has a specific attribute within its environmental area or detects a change in that specific attribute, or if the control unit detects a change in that specific attribute detected by the sensor. For example, such an external storage device could be a “cloud.” The external memory is preferably designed such that it transmits data packets only after an authorization check, wherein a handshake method, encryption method, secret and public keys, or a combination of these techniques are further preferably used for the authorization check. A device identifier may also be used for the authorization check.

[0358] In a preferred embodiment, the system according to the invention includes an external control unit that can send data packets from a playback device to the external control unit if the sensor detects a specific attribute or a change in that attribute within its environmental area, or if the control unit detects a change in that attribute detected by the sensor. Such an external control unit may be, for example, a server. The server may be part of a local area network or the Internet.

[0359] In the method according to the present invention, a playback device is provided, the playback device having:

[0360] -Speaker or speaker connection

[0361] - A sensor that can determine the characteristics or changes in characteristics of its environment within a given area, and

[0362] - The control unit controls the speaker or speaker connection to reproduce music or narrated stories if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a change in a specific characteristic determined by the sensor.

[0363] The device includes a memory and a data set (media files) stored in the memory, as well as a receiving unit for a specific release signal, to provide a method for reproducing music or narrated stories on a playback device implemented in this way, wherein when the control unit receives the specific release signal, the control unit controls a speaker or speaker connection to reproduce the music or narrated stories based on the data set.

[0364] The method according to the invention allows data sets (media files) to be stored in the memory of the playback device, data sets which are blocked by the control unit. In a preferred embodiment, the control unit can control the speaker or speaker connection to reproduce audio information without relying on the data sets, even before the control unit receives a release signal.

[0365] In the context of the present invention concerning a system, the system may also include a playback device having:

[0366] -Speaker or speaker connection

[0367] - A sensor can determine the characteristics or changes in characteristics of an environment within a given area.

[0368] - The control unit controls the speaker or speaker connection to reproduce music or narrated stories if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a specific change in a characteristic determined by the sensor.

[0369] The device includes a memory and a data set (media files) stored in the memory, as well as a receiving unit for a specific release signal, to provide a method for reproducing music or narrated stories on a playback device implemented in this way, wherein when the control unit receives the specific release signal, the control unit controls a speaker or speaker connection to reproduce the music or narrated stories based on the data set.

[0370] The system also includes a computer, particularly a server, which has memory and data sets (media files) stored in the memory.

[0371] The computer has a control unit.

[0372] The system has a data connection (particularly preferably a communication / computer network) between the playback device and the computer, wherein the control unit of the playback device can only access a data set stored in the computer memory through the data connection after the computer's control unit receives a specific release signal, and the control unit controls the speaker or speaker connection to reproduce music or narrated stories.

[0373] This invention enables the management of playback permissions. If the data set upon which the control unit controls the speaker or speaker connection to reproduce music or narrated stories is based already exists in the control unit's memory, the control unit determines whether to control the speaker or speaker connection to reproduce music or narrated stories based on the data set based on a specific release signal received. If the data set is still on a computer, for example, stored on a server, then the data set stored in memory is only allowed to be accessed by the control unit of the playback device via a data connection when the computer's control unit receives a specific release signal.

[0374] In a preferred embodiment, the data set is already stored in the memory of the playback device, and the receiving unit for the specific release signal is a different component from the sensor also located in the playback device, which can determine the characteristics or changes in characteristics of its environment within its area. In a preferred embodiment, the sensor may be a reader for an RFID transponder, and the receiving unit for the specific release signal may be a receiving unit for an NFC signal, a receiving unit for a Bluetooth signal, or a receiving unit for a WLAN signal.

[0375] In a preferred embodiment, when the sensor detects a characteristic or a change in characteristic of the environment within its environmental area, it sends an identifier to the control unit, or when the sensor detects a characteristic or a change in characteristic of the environment within its environmental area, it sends a signal to the control unit, and the control unit determines the identifier from the sensor signal.

[0376] In a preferred embodiment, the playback device has an allocation table (hereinafter referred to as the AV allocation table) in which possible values ​​for identifiers are assigned to information about data groups (media files). The AV allocation table assigns the values ​​that an identifier can take to the information about the data group (media file). If the control unit obtains an identifier with a specific value from a sensor, or determines a specific value from a sensor signal, the control unit can read from the AV allocation table that the value of the identifier corresponds to specific information about the data group (media file). This specific information may, for example, be the filename of the data group or the storage location of the data group.

[0377] Receiving a specific release signal allows the control unit to modify the AV allocation table. In a preferred embodiment, a new value for an identifier is added to the AV allocation table, and new information about the data group is assigned to that new value. In an alternative embodiment, the control unit changes the information about the data group assigned to the value of the identifier. For example, the information about the data group corresponding to a value might have content such as "no data record," "unknown," or "blocked," in which case the control unit, upon receiving a specific release signal, might use this information to change, for example, the specific filename or information about the data group's storage location.

[0378] Another embodiment may include an AV allocation table that, in addition to assigning values ​​to identifiers to data groups, also contains status attributes for the corresponding data groups. The status attribute could be, for example, "active." Conversely, the status attribute could be "inactive" or "blocked." In such an embodiment, receiving a specific release signal can cause the control unit to change the status attribute, specifically from "inactive" to "active."

[0379] Another embodiment may be provided in which receiving a specific release signal can change the allocation of the possible value of the identifier to information (media ID) about a data group (media file) to the allocation of that value (identifier) ​​to information (media ID) about another data group (media file).

[0380] Another embodiment could be implemented where receiving a specific release signal could change the allocation of possible values ​​to information about a data group to an allocation of that value to information about both that data group and another data group. For example, possible values ​​for an identifier could be assigned to a series of information about a data group.

[0381] In a preferred embodiment, a specific release signal is assigned to a unique specific data group. Upon receiving this specific release signal, the control unit controls the speaker or speaker connection to reproduce music or narrated stories based on that specific data group. In a preferred embodiment, the control unit's control of the speaker or speaker connection to reproduce music or narrated stories based on other data groups stored in the control unit's memory is unaffected by receiving the specific release signal. If another data group is released for reproduction, it remains released. If another data group is blocked, it remains blocked until the control unit receives a specific release signal for that other data group.

[0382] In a preferred embodiment, the data set is stored in the memory of a system computer (preferably a server), which preferably has an allocation table. In a preferred embodiment, when a sensor detects a characteristic or change in a characteristic of its environment within its environmental area, it sends an identifier to the control unit, or when a sensor detects a characteristic or change in a characteristic of its environment within its environmental area, it sends a signal to the control unit, and the control unit determines the identifier from the sensor signal. In a preferred embodiment, the control unit uses the identifier to send a request to the computer to download the data set (AV request signal). The computer's allocation table preferably assigns information (media ID) about the data set (media file) for each possible identifier value. The allocation table assigns the possible values ​​that the identifier can take to the information about the data set (media file) (media ID). If the control unit sends a signal containing the identifier (AV request signal) to the computer, the computer can read the specific information (media ID) about the data set (media file) corresponding to the value of that identifier from the allocation table. This specific information may, for example, be the filename or storage location of the data set.

[0383] The specific release signal received by the computer can also be a change signal, allowing the computer to modify the allocation table. In a preferred embodiment, the computer adds a new value for the identifier to the allocation table and assigns new information about the data group to that new value in the allocation table. In an alternative embodiment, the computer preferably changes the information about the data group (media ID) assigned to the value of the identifier after receiving the change signal. For example, the information about the data group corresponding to a value could have the content "no data record," or "unknown," or "blocked," in which case the computer, after receiving the specific release signal, uses that information, for example, to change the specific filename or information about the storage location of the data group (media ID).

[0384] Another embodiment may include a computer allocation table that, in addition to assigning values ​​to identifiers to data groups, also contains status attributes for the corresponding data groups. The status attribute could be, for example, "activated." Conversely, the status attribute could be "inactive" or "blocked." In such an embodiment, receiving a specific release signal can cause the control unit to change the status attribute, specifically from "inactive" to "activated."

[0385] There may also be embodiments in which receiving a specific release signal, in particular a release signal configured as a change signal, can change the allocation of the possible value of the identifier to information (media ID) about a data group (media file) to the allocation of that value (the identifier) ​​to information (media ID) about another data group (another media file) in the computer.

[0386] Another embodiment could be implemented where receiving a specific release signal that changes the allocation of possible values ​​to information about a data group can be changed to the allocation of that value to information about another data group. For example, possible values ​​of an identifier could be assigned to a series of information about a data group.

[0387] In a preferred embodiment, a specific release signal, preferably a release signal configured as a change signal, is assigned to a unique specific data group. A specific data group stored in computer memory is only invoked by the control unit of the playback device via a data connection when the computer's control unit receives a specific release signal for that specific data group. In a preferred embodiment, the possibility of the control unit invoking another data group stored in computer memory is unaffected by receiving a specific release signal. If another data group is released for invocation, it remains released. If another data group is blocked, it remains blocked until the control unit receives a specific release signal for that other data group.

[0388] In a preferred embodiment, the computer is a server or a computer in a combination of computers forming a cloud.

[0389] In a preferred embodiment, the data connection is a direct wireless connection between the playback device and the computer, such as via WLAN or via Bluetooth or NFC. In another embodiment, the data connection is a connection via the Internet.

[0390] In a preferred embodiment, a generating unit for a specific release signal is connected to a receiving unit for that signal on the playback device, or the generating unit for a specific release signal is provided as part of the system. Such a generating unit can be a credit card reader as a sub-component, particularly preferably a credit card reader for reading credit card RFID tags. However, the credit card reader can also be an NFC reader capable of reading credit cards stored in a smartphone or microcontroller (e.g., in the "Apple Pay" system). The generating unit can make the generation of the specific release signal dependent on a confirmation signal sent by the credit card reader, particularly a confirmation signal for deducting a specific amount from the credit card. Such a generating unit may additionally or alternatively include other sub-components that can generate confirmation signals for successful payment flows, such as a successfully completed transfer from one bank account to another.

[0391] In a preferred embodiment, the present invention enables the management of playback licenses to allocate another set of data to an identifier associated with an identifier carrier. For example, there may be an implementation where the data set of the first set of a multi-episode audiobook is allocated to the identifier carrier. With the present invention, the data set of another set of the audiobook can now be allocated to that identifier carrier, where the invention allows for new allocations by controlling specific release signals (preferably specific release signals that change the signal format), for example, based on payment. Similarly, there are embodiments where, initially only the identifier carrier of the first set of a multi-episode audiobook was allocated, two or more sets of the audiobook can now be allocated, where new allocations can be made, for example, dependent on payment by controlling specific release signals.

[0392] A system can exist in which a consumer already possesses multiple identifier carriers, with each identifier carrier assigned to a corresponding data set. This invention now allows for the subsequent assignment of one of these identifier carriers to another data set, or the subsequent appending of an existing assignment relationship to a data set, providing an assignment relationship to both data sets. If the sale of identifier carriers is incorporated into such a system, this invention now allows for the modification or supplementation of existing identifier carriers via the internet and payment transactions that can be processed via the internet. This allows consumers to assign their desired new content to existing identifier carriers without having to order new ones.

[0393] In a preferred embodiment of the method, when the sensor determines a specific characteristic or a change in a specific characteristic of the environment in a region of its environment, or when the control unit determines a specific change in a characteristic determined by the sensor, the data packet is transferred from the external memory to the memory of the playback device and / or the data packet is transferred from the playback device to the external memory and / or the external control unit.

[0394] This understanding can, for example, be used to reduce communication time between toys, playback devices, and external storage. Thus, for example, it can be configured such that, initially, there is no communication connection between the toy or playback device and the external storage, when a sensor determines a specific characteristic or change in that characteristic in a region of its environment, or when a control unit determines a specific change in that characteristic determined by the sensor, the fact that the sensor determines a specific characteristic or change in that characteristic in a region of its environment, or the fact that the control unit determines a specific change in that characteristic determined by the sensor, is used as a trigger event to establish a communication channel between the toy or playback device and the external storage or external control unit.

[0395] This process also allows for the shutdown of existing communication channels when a specific event occurs. If the communication channel is wireless, for example, provided via radio, the radio connection can be disconnected upon reaching a specific event. This reduces radiation exposure to the user of the toy or playback device. A triggering event could be, for example, the removal of an identifier from the toy or playback device. Similarly, a triggering event could be the passage of a predetermined time interval (even after the identifier has been removed). These measures allow for a good balance between maximizing user comfort and minimizing radiation exposure, where maximizing comfort often requires a continuous communication channel between the external storage or control unit and the toy or playback device.

[0396] External storage can be located in an external computer, to which the toy or playback device connects via cable or wireless connection. Such a computer can be local, for example, within a home network where the toy or playback device is also located. However, external storage can also be storage connected to the toy or playback device via the internet, such as storage in a so-called "cloud."

[0397] To achieve the advantages of this invention, data packets need not always be transferred from external memory to the toy's memory when a sensor determines a specific characteristic or change in a specific characteristic of its environment in a certain area, or when a control unit determines a specific change in a characteristic determined by the sensor. Therefore, in a preferred embodiment, the toy or playback device can be equipped with a memory in which data packets can be stored, and the control unit of the toy or playback device is aware of which data packets are stored in the toy or playback device's memory. In a preferred embodiment of the method, data packets are transferred from external memory to the toy's memory only when a sensor determines a specific characteristic or change in a specific characteristic of its environment in a certain area, or when the control unit determines a specific change in a characteristic determined by the sensor, and when the control unit determines that the data packet to be transferred from external memory to the toy's memory is not already stored in the toy or playback device's memory. This reduces the amount of data exchanged between external memory and the toy's or playback device's memory.

[0398] One possible implementation involves storing data packets in external memory, which are then transferred from the external memory to the memory of the toy or playback device in various situations, such as when a sensor determines a specific characteristic or change in that characteristic in a region of its environment, or when the control unit determines a specific change in that characteristic determined by the sensor. Such data packets could, for example, be software updates for software used by the control unit. They could also be control data packets. For example, such control data packets can be used to determine the maximum volume at which the toy or playback device can reproduce audio information via a speaker or speaker connection. In a preferred embodiment, such control data packets can control the function of the control unit of the toy or playback device. Control data packets can, for example, be used to determine the duration for which the control unit can reproduce audio information, images, video, or 3D information, or execute software. This allows for the setting of usage time limits. Similarly, control data packets can be used to prevent the reproduction of specific audio information, images, video, or 3D information, or specific software. This prevention can be general, making the corresponding content impossible to reproduce at all, for example, to comply with age restrictions. However, this prevention can also be temporary, for example, to prevent only one type of content from being reproduced consistently within a specific time period.

[0399] In a preferred embodiment, data packets are transferred from the memory of the toy or playback device to external memory when the sensor determines a specific characteristic or change in that characteristic in a region of the environment, or when the control unit determines a specific change in the characteristic determined by the sensor. For example, it can be considered that the control unit of the toy or playback device performs statistics on its use, particularly on reproduced audio information or reproduced images, videos, or 3D information, or on the software executed (e.g., software typically used to reproduce the corresponding content). If such statistics are transferred as data packets to external memory, then, for example, parents with access to the external memory data can determine the frequency with which their child uses the content, the duration of access, and other statistical information, such as the software status of the control unit or the charging status of the toy or playback device's battery.

[0400] Data packets transferred from external storage to the memory of a toy or playback device can originate from a library of databases pre-stored in the external storage. This library can be provided by an external service provider, such as an audiobook publisher or film distributor. However, an implementation where recording software is used to separately record data packets in the external storage is also conceivable. The recording software can be executed by a processor that is part of an external computer, and the external storage belongs to that external computer. Such a solution is suitable for home networks. Alternatively, the recording software can execute on an external computer, such as a smartphone, tablet, laptop, desktop computer, or workstation, and the resulting data packets can be stored in an external storage device, such as the "cloud," via a network, particularly preferably the Internet, from which the data packets are transferred to the memory of the toy or playback device. This allows third parties to record voice notes, images, movie sequences, such as recording stories, and store them in the external storage. When a sensor determines a specific characteristic or change in a specific characteristic of its environment in a region, or when a control unit determines a specific change in a characteristic determined by the sensor, the corresponding data packet is transferred from the external storage to the memory of the playback device. The external storage can be used to replace existing recordings with new ones. When a toy or playback device requests a data packet from external storage, the external storage and playback device can be configured to first check whether a copy of the data packet is already stored in the toy or playback device. This check can be performed by the toy or playback device, or preferably by the external storage. Based on this, for example, it can be determined whether and which data packets should be transferred from the external storage to the toy or playback device. Thus, using the same identifier, different content can be accessed over time, such as content that changes regularly (like a so-called podcast) or content that changes based on events. In one embodiment, the toy or playback device is configured to automatically check at predetermined times whether the content assigned to a specific identifier has changed, and preferably automatically save the new content so that it can be provided more quickly the next time the identifier is identified. For this purpose, the toy or playback device sends an automatically requested message to the external storage. Thus, the external storage can process these requests differently than other requests, for example, regarding the priority of data transmission.

[0401] In the context of the embodiments described in more detail below, when an identifier set in the shape of an image is placed in the area of ​​a sensor's environment, the sensor determines a specific characteristic or change in a specific characteristic of that environment in that area, or the control unit determines a specific change in a characteristic determined by the sensor, which can be associated with the shape of the image in various ways. Thus, the image can, for example, take the form of a protagonist from a particular story. If the image with the identifier is placed in the area of ​​a sensor, the sensor determines a specific characteristic or change in a specific characteristic belonging to the image in the area of ​​its environment, or the control unit determines a specific change in a characteristic related to the image determined by the sensor, thereby allowing data packets to be downloaded from external memory to the memory of a playback device or toy in the context of that protagonist. For example, this allows downloading children's radio dramas. However, this embodiment also provides image shapes that do not select protagonists from famous stories as identifiers, such as so-called fantasy identifiers (identifiers of the "creative type"). Fantasy identifiers can also be modeled as objects or people, and can be further preferably made in multiples or individually, such as using 3D printing technology. When a sensor determines a specific characteristic or change in a specific characteristic in its environment that is associated with the fantasy identifier, or when a control unit determines a specific change in a characteristic determined by the sensor that is associated with the fantasy identifier, a data packet is transferred from external memory to the playback device memory, the data packet having been previously recorded by recording software. This allows, for example, parents or grandparents to tell stories to their children or grandchildren, or bedtime stories that children can hear, or, in the case of video or 3D recording, to see if they place the fantasy identifier in the sensor's environment.

[0402] Recording software can be used to transmit data packets to external storage. The recording software can record content or otherwise read content, transmit all or part of the content to external storage via a network, and assign the content to one or more specific identifiers or groups of identifiers. For this purpose, the recording software determines one or more relevant specific identifiers or groups of identifiers once or repeatedly through a connection with the toy or playback device (directly or via an intermediate server), allowing the user of the recording software to determine which identifiers should be assigned before or after recording or reading. This determination is preferably performed such that if the identifier is available to the user of the recording software, it is introduced into the identification area of ​​the toy or playback device. However, this can also be achieved by storing the relationship between the user (or group of users) of the recording software and one or more identifiers, for example, through user accounts. It can also be achieved by storing the relationship between user accounts and device identifiers and assigning the identifiers to device identifiers. Preferably, the assignment to user accounts can be achieved by using personal information related to the identifier but which can be transmitted separately in the recording software or other software that can be assigned to user accounts. Individual information can be, for example, alphanumeric codes, barcodes, or QR codes. Preferably, the aforementioned assignment possibilities are combined to provide maximum convenience to the user of the recording software. The allocation of user accounts can be stored, for example, in external storage or in the same device as the recording software, preferably in both locations. In particular, the recording software can be implemented such that it can allocate an identifier even without physical access to that identifier.

[0403] The recording software and external storage can be implemented such that the recording software can transmit user-requested authorization restrictions for a specific identifier or group of identifiers to the external storage, particularly for fantasy identifiers. These restrictions can be communicated to the toy or playback device via the control packets described above. However, they can also (e.g., additionally) be considered in the authorization check before sending the packets via the external storage.

[0404] For greater convenience, preferred recording software also provides the aforementioned possibilities to generate additional control data packets, such as those for limiting volume.

[0405] Alternatively, it is possible to persistently transfer data packets from external storage to the playback device's storage, preferably persistently for a certain period of time, or to stream them. For example, data packets used for radio broadcasting, television, or movie playback could be transferred in this way from external storage to the storage of a playback device or toy.

[0406] The playback device, in particular, utilizes the simplified operating concept described in WO 2015 / 104222A1 and WO 2017 / 129349A1. The basic idea is to use a sensor as part of the playback device, which determines specific characteristics or changes in specific characteristics of its environment within a given area, and a control unit that performs desired control when the sensor determines these specific characteristics or changes in specific characteristics within its environment. The playback device with this sensor and control unit, and the method of using such a sensor and control unit, makes operation particularly simple. According to the invention, to reproduce desired information, the environment is made to have characteristics that can be determined by the sensor, or the characteristics of the environment that can be determined by the sensor are changed, thereby allowing the desired information to be reproduced immediately or the software to run in a preferred embodiment of the invention.

[0407] One application area of ​​this invention is the reproduction of media files containing audio information, particularly music clips, read-aloud text, or a combination of music clips and read-aloud text. The audio information is particularly preferably reproduced for at least 10 seconds, preferably more than 15 seconds, particularly preferably more than 20 seconds, and most preferably more than 25 seconds. In a particularly preferred embodiment, the reproduction duration of the audio information is at least 30 seconds, particularly preferably more than 1 minute. For example, the reproduction of a radio drama according to the invention typically exceeds 5 minutes, sometimes reaching 30 minutes or even longer. The audio information to be reproduced according to the invention is particularly not a confirmation signal. In particular, the audio information to be reproduced is particularly not, for example, a confirmation tone when a first object has been correctly aligned relative to a second object. Preferably, the audio information to be reproduced is also not, for example, a clinking sound emitted when a first object is brought near or relative to a predetermined position of the second object. The audio information involved in this invention has a relatively long reproduction duration, such as in the case of music clips and read-aloud text. It is particularly preferred that the audio information is a non-periodic sequence given with different pitches during reproduction.

[0408] The speaker of the playback device according to the invention is particularly preferably a converter capable of converting electrical signals into mechanical vibrations (sound).

[0409] The playback device according to the invention, instead of a speaker, may also have a speaker connection, such as a Speakon-, XLR-, or, for example, a 6.35mm jack. The control unit controls the speaker by controlling the speaker connection; when the speaker is connected to the speaker connection, the control unit can control the speaker. The speaker connection can also be a transmitting unit that communicates with the speaker via a wireless network, such as Bluetooth or WLAN. However, it is preferred that the transmitting unit communicates with the speaker via Bluetooth, for example, instead of a WLAN wireless network. The playback device can also have a docking station compatible connection with a smartphone as a speaker connection or a display connection for reproducing images, videos, or 3D information. The smartphone docking station can be used to control the speaker or display to reproduce images, videos, or 3D information based on smartphone control commands. Because the playback device according to the invention has such a docking station compatible connection with a smartphone, and is connected to the docking station instead of the smartphone, the control unit of the playback device according to the invention can control the speaker or display connected to the docking station to reproduce images, videos, or 3D information. The docking station can be connected to the speaker or display via a cable to reproduce images, videos, or 3D information. In this specification, unless specific features of controlling speaker connections or display connections to reproduce images, videos, or 3D information are explicitly described, this invention describes the possibility of controlling speaker connections or other connections used for display to reproduce images, videos, or 3D information by means of preferred application areas of speaker control. Whenever this specification refers to controlling a speaker or display to reproduce images, videos, or 3D information, it also means controlling the speaker connection or display connection to reproduce images, videos, or 3D information.

[0410] In a preferred embodiment, the playback device of the present invention has at least two speakers, thereby enabling stereo reproduction of audio information.

[0411] The characteristic changes in the area of ​​the environment determined by the sensor are particularly preferably changes in electromagnetic wave characteristics. Electromagnetic waves can be generated, for example, by a reading device to communicate with a passive RFID transponder, and the electromagnetic waves are altered by placing the passive RFID transponder in the area of ​​the reading device's environment, as the presence of the passive RFID transponder changes the electromagnetic waves. This change in electromagnetic waves resulting from the introduction of the RFID transponder can be identified by the characteristic changes in the area of ​​the sensor's environment. Thus, the playback device of the present invention can determine the presence of a passive RFID transponder in a specific area of ​​the sensor's environment and reproduce audio information, for example, when a specific RFID transponder is already present in the area of ​​the sensor's environment, or when the sensor determines that a specific RFID transponder is present in that area. Similarly, it is preferable that the characteristics or characteristic changes in the area of ​​the environment determined by the sensor originate from an active RFID transponder.

[0412] Particularly preferred is the use of an identifier transmitted via electromagnetic waves. The control unit utilizes this identifier to identify data sets stored in the memory or on a server of the playback device of the present invention, and controls the speaker based on these data sets to reproduce audio information. In a preferred embodiment, the sensor is therefore a reading device for communicating with passive RFID transponders and / or active RFID transponders.

[0413] When a sensor determines a specific characteristic or change in a specific characteristic of its environment in a region, or when a control unit determines a specific change in a characteristic determined by the sensor, the control unit of the playback device can control the speaker to reproduce audio information. In a preferred embodiment, when the sensor determines a specific characteristic or change in a specific characteristic of its environment in a region, it generates a signal with a value that can be determined by the control unit. For example, it is conceivable that when the sensor determines a specific characteristic or change in a specific characteristic of its environment in a region, it generates only one signal, which is sent to the control unit. This allows the sensor to either have been evaluated, or to transmit a signal to the control unit when it determines a specific characteristic or change in a specific characteristic of its environment in a region, or to continuously send a signal with a specific value to the control unit, changing it to a specific additional value determined by the control unit when the sensor determines a specific characteristic or change in a specific characteristic of its environment in a region. Alternatively or additionally, the control unit performs an evaluation. In this embodiment, the sensor continuously sends measurement signals to the control unit. The control unit identifies the specific characteristic or change in a specific characteristic of the sensor's environment in a region from the measurement signals transmitted to it by the sensor, for example, by storing a numerical table. Here, a change in the characteristics of the sensor environment is understood not only as a one-time specific change, such as a one-time change in the direction of the magnetic field in the sensor environment, but also as a temporal sequence or a specific sequence of changes in characteristics within a region of the sensor environment, such as in the case of reading modulated waves or evaluating electromagnetic waves.

[0414] In a preferred embodiment, the control unit controls the speaker to reproduce audio information only when the sensor determines a specific characteristic change in a specific sequence of the environment within a region of the environment, or when the control unit determines a characteristic change in a specific sequence of the environment determined by the sensor. This change sequence can be a string, which may contain, for example, information about reproducing audio information at a specific location and an identifier (Kennungswort) at another specific location, serving a copyright protection or authentication purpose. If the string-type change sequence contains the audio information to be reproduced but does not contain the identifier, the control unit does not control the speaker. Instead of the identifier, the string can also be a sequence of commands from a (software) program executed by a control device for verification.

[0415] In a preferred embodiment, the playback device has a memory where data is stored, and the control unit controls the speaker to reproduce audio information based on this data. This data preferably contains audio information in a specific data format, such as MP3 or WAV. In one embodiment, the memory contains only data of a single audio message. Here, the playback device of the present invention is used to reproduce a single audio message in response to changes in characteristics or features in a region of the sensor environment, and the reproduction duration is preferably at least 10 seconds. In a preferred embodiment, data of different audio messages are stored in the memory. Preferably, when the sensor determines a specific characteristic or change in a specific characteristic of the environment in a region of its environment, or when the control unit determines a specific change in a characteristic determined by the sensor, the control unit controls the speaker to reproduce the first audio message (with a reproduction duration of at least 10 seconds) while controlling the speaker to reproduce the second audio message, with a reproduction duration of at least 10 seconds. Thus, the playback device can determine which audio messages among multiple audio messages to reproduce based on the influence of environmental characteristics or changes in the region of the sensor environment. For example, when a first RFID transponder is determined to be present in a region of the sensor environment, the playback device can reproduce the first audio message. When a second RFID transponder is determined to be present in a region of the sensor environment, the playback device can reproduce the second audio message.

[0416] In a preferred embodiment, audio information is stored as data groups having separately readable data sequences to reproduce, for example, an audiobook in chapter form or to control the reproduction of chapters of an audiobook. The data sequence of each data group can be read separately and used to control the speaker.

[0417] In a preferred embodiment, the playback device has a unit for receiving data from and / or sending data to the Internet, preferably an antenna for a wireless local area network (WLAN), mobile data transmission technology (such as LTE), UMTS or its predecessor or successor, or a socket for connecting to a local network, the cable also having Internet access, such as a socket for an Ethernet cable. The control unit, through the unit receiving data from the Internet, can download audio information to be reproduced, containing specific data formats, from the Internet. Thus, the playback device can play audio information not stored in the playback device before a sensor determines a specific characteristic or change in that characteristic in an area of ​​the environment, or before the control unit determines a specific change in that characteristic determined by the sensor. In this implementation, the control unit receives data from the Internet and continuously stores it in a memory, controlling the speaker to reproduce the audio information based on the data stored in the memory. Alternatively, the control unit directly uses the data received from the Internet to control the speaker to reproduce the audio information (so-called streaming), which also includes temporarily storing the data received from the Internet in an intermediate memory.

[0418] In embodiments where the data received from the Internet includes audio information in a specific data format, the control unit may also store the specific server address of the Internet-connected server in its memory and in a table. Specific characteristics or variations of specific characteristics are assigned specific identification numbers in this table. When the control unit identifies a specific characteristic or variation, it communicates with the specific server and uses the identification number assigned to the specific characteristic or variation to download a specific data set from the server and uses this data set to control the speaker to reproduce the audio information given by that data. For example, a music title as data in a specific data format can be stored on the server, and the corresponding music title or data containing that music title is stored in the server under a specific identification code. In a preferred embodiment, the playback device of the present invention has obtained an allocation table (AV allocation table) that assigns characteristics or variations of characteristics in a region of the sensor environment to several, multiple, or even all identification numbers, which are also applied to the server database. Thus, the control unit can selectively download data sets from the server. Alternatively, the width is equal to transmitting information containing the determined specific characteristics or variations of specific characteristics to a specific server connected to the Internet. The identified specific characteristics or variations of specific characteristics can be assigned to specific audio information on the server. The control unit can receive data from the server containing audio information to be reproduced. The server transmits the data to the playback device of the present invention, which corresponds to a specific characteristic or a specific characteristic variation transmitted to it by the control unit. This avoids the need to include an allocation table in the playback device, thereby increasing the flexibility of receiving specific data containing audio information based on specific characteristics or specific characteristic variations in a region of the sensor environment. This allows for an increase in the number of data sets stored in the server without adjusting the allocation table in the control unit of the playback device of the present invention.

[0419] In a preferred embodiment, the playback device has an antenna for a wireless local area network (WLAN). Particularly when the playback device of the present invention is intended to reproduce audio information for children, it is desirable to reduce electromagnetic waves generated around children. For this purpose, the WLAN antenna can be turned off.

[0420] Similarly, a playback device connected to a wireless LAN via a WLAN antenna can transmit the audio information to be reproduced to other participants in the network, such as streaming to a TV or another speaker.

[0421] In a preferred embodiment, the operating system of the control unit is Firefox OS. In another preferred embodiment, the operating system of the control unit can be activated through an update.

[0422] In a preferred embodiment, the control unit determines and records information about controlling the speaker, such as the frequency or sequence of playing specific audio information. Specifically, the control unit communicates this information to a server.

[0423] The system of this invention includes the playback device and the identifier carrier. When the identifier carrier is located in the area of ​​the sensor's environment, the identifier carrier possesses characteristics that the sensor can determine, or the identifier carrier can alter the characteristics of the sensor's environment. The basic idea of ​​this system is that when a specific identifier carrier is placed in the area of ​​the sensor's environment, the sensor can determine specific characteristics or changes in those characteristics of the environment, thereby enabling the control unit to control the speaker to reproduce audio information. In a particularly preferred embodiment, the identifier carrier remains in the area and triggers control of the speaker to reproduce audio information, thus eliminating the need for further operational commands.

[0424] The system concept of this invention greatly simplifies the operation of playback devices in reproducing audio information. It eliminates the need for CD players (which are known to damage CDs) or the complex speaker control mechanisms found in MP3 players. In the simplest embodiment of this invention, an identifier carrier is placed in an area of ​​the sensor environment where specific characteristics or changes in those characteristics can be identified, thereby automatically triggering the speaker, controlled by the control unit, to reproduce audio information.

[0425] In a preferred embodiment, the identifier carrier has an RFID transponder or antenna that can transmit and / or receive modulated waves. Thus, for example, the identifier carrier can communicate with the playback device via Bluetooth or NFC standards. In particular, the use of these technologies can provide a variety of communication possibilities between the identifier carrier and the playback device, especially allowing multiple identifiers. Thus, the playback device can select the audio information to be reproduced from multiple audio messages, for example, each audio message is assigned its own identifier, such as an allocation table stored in the playback device or server of this invention.

[0426] In a preferred embodiment, the identifier carrier has a magnet, and the playback device has a surface on which the magnet can be attached. Alternatively, the playback device may have a magnet, and the identifier carrier may have a surface on which the magnet can be attached. Thus, the identifier carrier and the playback device can be detachably connected. This ensures that movement of the playback device does not cause the identifier carrier to lose its relative position to the playback device.

[0427] In a preferred embodiment, the identifier carrier has a shape, particularly a human figure, an animal figure, or a fantasy character. Particularly preferred is a human figure with feet, in which magnets can be disposed, allowing the identifier carrier to stand on the playback device of the present invention.

[0428] In a preferred embodiment, a user can associate the identifier carrier with specific audio information based on its shape, color, surface texture, and / or material. When placed in an area of ​​the sensor's environment, the sensor can determine specific characteristics or changes in those characteristics, triggering a speaker to reproduce the audio information, which is content-associated with the user. The identifier carrier can be configured according to its design type and trigger the reproduction of audio information. For example, the design could have a Benjamin shape. The identifier carrier can take the form of a human figure, and the reproduced audio information could be an audio story starring Benjamin Blümchen. The identifier carrier can also be individually adjusted. For example, the identifier carrier could be shaped like a human figure, and the reproduced music could be audio information previously recorded by that person. The identifier carrier could also be shaped like a scientist, and the audio information could contain content discovered by that scientist. The figure could also be a composer or performer, and the audio information could contain content from that composer or performer. The identifier carrier can also trigger audio information from a piece of music, a set of music (album), or a playlist.

[0429] Alternatively or additionally, the identifier carrier may be designed as a sticker or module that can be attached to other objects.

[0430] In the method for reproducing music or oral stories according to the present invention, a playback device is provided, the playback device having:

[0431] -Speaker or speaker connection

[0432] - A sensor can determine the characteristics or changes in characteristics of an environment within a given area.

[0433] - The control unit controls the speaker or speaker connection to reproduce music or narrated stories if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a change in a specific characteristic determined by the sensor.

[0434] It also includes a memory and a data set stored in the memory, as well as a receiving unit for a specific release signal, to provide a method for reproducing music or narrated stories on a playback device implemented in this way, wherein when the control unit receives the specific release signal, the control unit controls a speaker or speaker connection to reproduce music or narrated stories based on the data set.

[0435] In the method for reproducing audio information and / or images, videos, or 3D information and / or executing software according to the present invention, a playback device is provided, the playback device having:

[0436] - Speakers or speaker connections, and / or displays for displaying images, videos, or 3D information, or connections to such displays and / or processors executing software.

[0437] - A sensor that can determine the characteristics or changes in characteristics of its environment within a given area, and

[0438] - The control unit, if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a change in a specific characteristic determined by the sensor, then

[0439] Controlling speakers or speaker connections to reproduce audio information, and / or

[0440] Control the display or display connection to reproduce images, video or 3D information and / or

[0441] Control the processor to execute software, and

[0442] It includes a memory and a data set stored in the memory, as well as a receiving unit for a specific release signal. When a specific release signal is received, the control unit...

[0443] Based on data group control, the speaker or speaker connection reproduces audio information, and / or

[0444] Based on data group control of displays or display connections to reproduce images, videos, or 3D information, and / or

[0445] The data group-based control processor executes the software.

[0446] In a preferred embodiment of the method according to the invention, when the control unit has not yet received a release signal, the control unit can...

[0447] Controlling speakers or speaker connections is not based on data set reproduction of audio information, and / or

[0448] Not based on data group control of the display or display connection to reproduce images, video or 3D information, and / or

[0449] The processor is not controlled by a data group to execute software.

[0450] In the method for reproducing music and oral stories according to the present invention, there is a system with a playback device, the playback device having:

[0451] -Speaker or speaker connection

[0452] - A sensor can determine the characteristics or changes in characteristics of an environment within a given area.

[0453] - The control unit controls the speaker or speaker connection to reproduce music or narrated stories if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a specific change in a characteristic determined by the sensor.

[0454] The system also includes a computer, particularly a server, which has memory and groups of data stored in the memory.

[0455] The computer has a control unit.

[0456] The system includes a data connection between the playback device and the computer. The playback device's control unit can only access a data set stored in the computer's memory via this data connection after the computer's control unit receives a specific release signal. The control unit then controls the speaker or speaker connection to reproduce music or narrated stories.

[0457] The device includes a memory and a data set stored in the memory, as well as a receiving unit for a specific release signal, to provide a method for reproducing music or a spoken story on a playback device implemented in this way, wherein when the control unit receives the specific release signal, the control unit controls a speaker or speaker connection to reproduce the music or spoken story based on the data set.

[0458] In the method for reproducing audio information and / or images, videos, or 3D information and / or executing software according to the present invention, a system having a playback device is provided, the playback device having:

[0459] - Speakers or speaker connections, and / or displays for displaying images, videos, or 3D information, or connections to such displays and / or processors executing software.

[0460] - A sensor that can determine the characteristics or changes in characteristics of its environment within a given area, and

[0461] - The control unit, if the sensor determines a specific characteristic or change in a specific characteristic of the environment within its area, or if the control unit determines a change in a specific characteristic determined by the sensor, then

[0462] Controlling speakers or speaker connections to reproduce audio information, and / or

[0463] Control the display or display connection to reproduce images, video or 3D information and / or

[0464] Control the processor to execute software, and

[0465] The system also includes a computer, which has memory and a set of data stored in the memory.

[0466] The computer has a control unit.

[0467] The system includes a data connection between the playback device and the computer. The playback device's control unit can only access a data set stored in the computer's memory via this data connection after the computer's control unit receives a specific release signal. The control unit then controls the speaker or speaker connection to reproduce music or narrated stories.

[0468] It includes a memory and a data set stored in the memory, as well as a receiving unit for a specific release signal. When a specific release signal is received, the control unit...

[0469] Based on data group control, the speaker or speaker connection reproduces audio information, and / or

[0470] Based on data group control of displays or display connections to reproduce images, videos, or 3D information, and / or

[0471] The data group-based control processor executes the software.

[0472] In a preferred embodiment, the method can be extended to include a sensor that is a reading device for communicating with a passive RFID transponder and / or an active RFID transponder.

[0473] In a preferred embodiment, the method can be extended to include an identifier carrier that has characteristics that can be determined by the sensor when it is in the region of the sensor's environment, or the identifier carrier can change the characteristics of the sensor's environment that are determined by the sensor in the region of its environment.

[0474] In a preferred embodiment, the method can be extended to include setting up an external computer or server and a communication path through which the toy can communicate with the external computer or server.

[0475] In a preferred embodiment, the method can be extended to include reproducing music, spoken stories, or audio information for at least 10 seconds.

[0476] In a preferred embodiment, the method can be extended to include a processor executing software that has not yet been stored in the playback device before the sensor determines the characteristics or changes in characteristics of the environment within its area.

[0477] In a preferred embodiment, the method can be extended to include a support on which an object can be permanently placed, wherein a sensor can determine a characteristic or characteristic change in a region at least above the support, and / or fasteners on which the object can be permanently secured, wherein a sensor can determine a characteristic or characteristic change in a region at least adjacent to the support.

[0478] In a preferred embodiment, the method can be extended, wherein the sensor is an inductive sensor, a magnetic field sensor, a capacitive sensor, a piezoelectric sensor, an electrochemical sensor, or a temperature sensor.

[0479] In a preferred embodiment, the method can be extended to include a sensor that is a reading device for communicating with a passive RFID transponder and / or an active RFID transponder.

[0480] In a preferred embodiment, the method can be extended to include an antenna in which the sensor transmits and / or receives modulated waves.

[0481] In a preferred embodiment, the method can be extended to allow the control unit to control a speaker or speaker connection to reproduce voice information for at least 10 seconds.

[0482] In a preferred embodiment, the method can be extended to allow the control unit to directly control the speaker or speaker connection, or the connection to displaying images, videos, or 3D information or such displays, or the processor executing the software.

[0483] In a preferred embodiment, the method can be extended by providing a housing within which a sensor is disposed, wherein the area of ​​the sensor’s environment in which the sensor is capable of determining its characteristics or changes in characteristics extends no more than 100 mm beyond the surface of the housing.

[0484] In a preferred embodiment, the method can be extended to include an operating element that an operator can use to influence the start of audio information reproduction by controlling a speaker or speaker connection via a control unit when the sensor determines a specific characteristic or a specific change in the characteristic of the environment within its area, or to control the display of or connection to an image, video, or 3D information to start the reproduction of the image, video, or 3D information, or to control the processor to execute software when the software is started.

[0485] In a preferred embodiment, the method can be extended by setting up an operating element to control a speaker or speaker connection, or to display images, videos, or 3D information, by using a sensor to determine a specific characteristic or a specific change in the characteristic of the environment within its area, or simply to execute a processor of software without requiring an operator to operate the operating element.

[0486] In a preferred embodiment, the method can be extended by providing an identifier carrier that has characteristics that can be determined by the sensor when it is in the area of ​​the sensor's environment, or that has characteristics that can be changed by the sensor when it is in the area of ​​the sensor's environment.

[0487] In a preferred embodiment, the method can be extended to enable the identifier carrier to have an RFID transponder or an antenna capable of transmitting and / or receiving modulated waves.

[0488] In a preferred embodiment, the method can be extended such that the reproduction of audio information lasts for at least 10 seconds. Attached Figure Description

[0489] The present invention will now be described in more detail with reference to the embodiments shown in the accompanying drawings. In the drawings:

[0490] Figure 1 A perspective view of a playback device that can be part of the system of the present invention is shown.

[0491] Figure 2 Showing according to Figure 1 The front view and identifier carrier of the playback device.

[0492] Figure 3 A schematic diagram of the system according to the present invention is shown.

[0493] Figure 4 Showing according to Figure 1 A schematic diagram of the playback device and a schematic diagram of the components installed inside the housing of the playback device.

[0494] Figure 5 A schematic diagram of a system according to the present invention, comprising a server, playback devices, and a communication network / computer network, is shown.

[0495] Figure 6 A schematic diagram of a system according to the invention is shown, comprising a server and a playback device, as well as external devices implemented as a smartphone and external devices implemented as a laptop computer, and a communication network / computer network.

[0496] Figure 7 This diagram illustrates the server and the user table, user group table, media table, identifier table, and permission table stored in the server's storage.

[0497] Figure 8 Showing the Figure 7 The diagrams supplement external devices in the form of smartphones and supplement communication / computer networks in the state of receiving changed signals.

[0498] Figure 9 The basis shown in another program routine step Figure 8 A schematic diagram,

[0499] Figure 10 The basis shown in another program routine step Figure 8 A schematic diagram,

[0500] Figure 11 Showing the Figure 7 The diagrams supplement external devices in the form of smartphones and supplement communication networks / computer networks in the state of transmitting library signals.

[0501] Figure 12 Showing the Figure 7 The diagrams supplement external devices in the form of smartphones and supplement communication / computer networks in the state of transmitting inventory signals.

[0502] Figure 13 This diagram illustrates the screen display of the GUI.

[0503] Figure 14 This diagram illustrates the screen display of the GUI.

[0504] Figure 15 This diagram illustrates the screen display of the GUI.

[0505] Figure 16 This diagram illustrates the screen display of the GUI.

[0506] Figure 17 This diagram illustrates the screen display of the GUI.

[0507] Figure 18 This diagram illustrates the screen display of the GUI.

[0508] Figure 19 This diagram illustrates the screen display of the GUI.

[0509] Figure 20 This diagram illustrates the screen display of the GUI.

[0510] Figure 21 This diagram illustrates the screen display of the GUI.

[0511] Figure 22 This is a schematic diagram showing the identifier image displayed on the screen of the GUI.

[0512] Figure 23 This is a schematic diagram showing the identifier image displayed on the screen of the GUI.

[0513] Figure 24 A schematic diagram showing the screen display window of the GUI.

[0514] Figure 25 A schematic diagram showing the screen display window of the GUI.

[0515] Figure 26 This is a schematic diagram showing the screen display window of the GUI. Detailed Implementation

[0516] Figure 1 A playback device 1 is shown that can be used as part of the system of the present invention. The playback device 1 has... Figure 1 The speaker is not shown in detail in the schematic diagram. The playback device 1 also has a slot 3 on its upper side 2. Inside the playback device 1, below the slot 3, is a sensor (not shown) capable of determining the characteristics or changes in characteristics of the environment within the area of ​​the slot 3, i.e., capable of reading passive RFID transponders (see [reference]). Figure 2 In addition, the playback device 1 also has a control unit (not shown) that controls the speaker to reproduce audio information when the sensor determines a specific characteristic of the environment or a change in that characteristic within the area of ​​the environment, or when the control unit determines a specific change in the characteristic determined by the sensor.

[0517] The playback device 1 has a first operating element 5 designed in an ear shape and a second operating element 6 also designed in an ear shape. Both operating elements 5 and 6 can tilt relative to the rest of the housing of the playback device 1 and pivot back. Figure 1 The basic position is shown. In addition, the playback device 1 also has a display 7.

[0518] Figure 2 The illustration shows a playback device 1 and an identifier carrier 8 disposed thereon. The identifier carrier 8, designed in a humanoid shape, has legs 9 and feet. Magnets (not shown) are provided in the feet of the humanoid identifier carrier 8. These magnets can interact with magnets disposed directly under the bottom surface 4 of the slot 3, so that the identifier carrier 8 is detachably fixed to the bottom surface 4 of the slot 3.

[0519] The operation of the playback device and the identifier carrier is as follows:

[0520] Figure 1The playback device shown is in a basic state, in which it does not reproduce audio information in the embodiment shown here. The sensor continuously or periodically monitors this area of ​​slot 3 for specific characteristics or changes in those characteristics. In the embodiment shown here, the sensor continuously monitors whether an RFID transponder is placed in this area of ​​slot 3. Figure 1 This is not the case in the operating state shown, therefore playback device 1 does not reproduce audio information.

[0521] exist Figure 2 In the illustrated operating state, the identifier carrier 8 is mounted on the playback device. The identifier carrier 8 is positioned on the bottom surface 4 of the slot 3 and is attached there by means of magnets located in its feet. The identifier carrier 8 has an RFID transponder (identifier) ​​(not shown). Since the identifier carrier 8 is now placed in an area of ​​the sensor environment monitored by the sensor, it now possesses specific characteristics determined by the sensor. The sensor identifies the presence of the RFID transponder in the identifier carrier 8 and notifies the control unit (not shown) with a signal. The control unit then controls the speaker to reproduce the audio information without activating another operating element.

[0522] The sensor reads an identifier from the RFID transponder of the identifier carrier 8 and sends the identifier to the control unit. The control unit assigns the identifier read by the sensor to a specific data set (media file) containing specific audio information in the memory (not shown) of the playback device 1, according to an allocation table (playback device (AV) allocation table) stored in the control unit. The control unit then controls the speaker to reproduce the audio information contained in the data set (media file) read from the memory by the control unit. This audio information is a piece of music, and its reproduction lasts at least 10 seconds.

[0523] Figure 3 The playback device 1 and the identifier carrier 8 which can be placed in the slot 3 of the playback device 1 are shown. Figure 1Base station 100 is also shown. Base station 100 has a protrusion 101 with a socket 102. A recess corresponding to the protrusion 101 is provided on the underside of the playback device 1 (not shown), into which a plug extends. When the playback device 1 is placed on the protrusion 101 with the recess provided on its underside, the plug (not shown) is inserted into the socket 102, thereby establishing an electrical connection between the playback device 1 and the base station 100. Base station 100 may have an electrical connection 103. A rectifier (not shown) may be provided in base station 100, which converts the alternating current on the plug of electrical connection 103 into direct current of a desired magnitude provided on the socket 102. Instead of the electrical connection on the plug (not shown) and socket 102, it is also conceivable to include a coil in base station 100 for contactless charging, particularly inductive charging, of the playback device 1, and the playback device 1 also has a corresponding coil (not shown).

[0524] Base station 100 may include several connectors or connections for connecting to other devices such as speakers, displays, or computers to play programs. Base station 100 may also include communication modules, such as those for WLAN, Bluetooth, NFC, or mobile communication networks.

[0525] Figure 3 External operating devices in the form of communication / computer network 110, server 111, and smartphone 112 are also shown.

[0526] Playback device 1 can communicate with server 111 via communication / computer network 110. Figure 3 Network 110 is shown as a cloud to illustrate that communication / computer network 110 can be implemented in different ways. Communication / computer network 110 can be individually cable-connected. For example, a network cable, such as an Ethernet cable, can be connected from playback device 1 to server 111. Similarly, the cloud symbol is also used for communication / computer network 110 with partially wired and partially wireless connections. Therefore, it is possible for playback device 1 to communicate with a router via a WLAN standard, and the router to be connected to an Internet node via a cable. In such an implementation, server 111 can also be connected to a router via a cable, and the router to (another) Internet node. Thus, playback device 1 can communicate with server 111 via the Internet. Communication / computer network 110 can also be partially or entirely a mobile communication network. Therefore, it is possible for playback device 1 to have an identification module for identifying and logging into the mobile communication network. This identification module can be used for authentication and authorization when logging into the mobile communication network.

[0527] Server 111 can be a "cloud server".

[0528] Server 111 may include software components capable of controlling and maintaining the database. Similarly, the software may manage communication with playback device 1, including security protocols and encrypting and decrypting data communications.

[0529] Smartphone 112 can communicate with server 111 and / or playback device 1 via communication / computer network 110. Preferably, smartphone 112 does not communicate directly with playback device 1; this allows the playback device to be configured very simply. In a possible implementation, only server 111 communicates with playback device 1. However, settings, such as setting the maximum volume, can be made on server 111 using smartphone 112. Server 111 can forward this setting change, altered through interaction with smartphone 112, as a control intervention via communication / computer network 110 to the control unit of playback device 1. Similarly, the following implementation is also possible: where smartphone 112 communicates directly with playback device 1 via communication / computer network 110, for example, bypassing server 111 to directly control playback device 1. Furthermore, there are implementations where smartphones communicate directly with playback device 1, for example, via Bluetooth or NFC.

[0530] Figure 4 A schematic diagram of the components connected in the playback device 1 in a preferred embodiment is shown. These connected components are shown in dashed lines to indicate that the corresponding spatial positions are possible spatial positions in the playback device 1, but other spatial positions are also possible.

[0531] Figure 4 The playback device 1 in the illustrated embodiment includes a sensor 120 that can determine characteristics or changes in characteristics of the environment in a region of its surroundings. The sensor 120 may be, for example, an RFID reader, an NFC reader, an infrared reader, or an optical sensor. The identifier carrier 8 may include an active or passive RFID transponder. In a possible embodiment, the identifier carrier 8 includes an active RFID transponder, and the sensor 120 is part of a read / write head through which the identifier carrier 8 can be written.

[0532] exist Figure 4 In the playback device 1, a magnet 121 is disposed under a support member of the playback device 1, and an identifier carrier 8 stands on the support member. The magnet 121 interacts with a magnet (not shown) in the foot of the identifier carrier 8, thereby holding the identifier carrier 8 on the support member of the playback device 1.

[0533] Playback device 1 has a control unit 130. Control unit 130 has a processor 131. Control unit 130 also has a memory 132, with processor 131 communicating with memory 132. The memory has a non-volatile read-only memory (ROM) 133 and a volatile or non-volatile read-write memory (RAM) 134. Playback device has a battery 135 with rechargeable electronics. A plug 136 in a recess 137 on the bottom of playback device 1 allows connection to a socket 102 of base station 100.

[0534] Operating elements 5 and 6 are connected to processor 131. Speaker 138 is connected to processor 131. Figure 4 A display (not shown) can be connected to processor 131. A 6.35mm jack 206 is connected to processor 131. A transmitting and receiving unit 139 for communication via a WLAN wireless network is connected to processor 131. The playback device also includes a gyroscope 140.

[0535] The program executed by processor 131 periodically polls signals emitted by sensor 120 and gyroscope 140. Sensor 120 is implemented as an RFID reader and sends an identifier it reads from an RFID transponder located in identifier carrier 8 to processor 131. Processor 131 checks whether an entry for that identifier exists in the AV allocation table stored in RAM 134. In the AV allocation table, identifiers are assigned information about data sets (media files). If processor 131 finds an entry corresponding to the identifier in the AV allocation table and thus finds information about the data set (media file), processor 131 checks whether the data set (media file) is also stored in RAM 134. If the data set (media file) is stored in RAM 134, processor 131 uses the data set (media file) to control speaker 138. The information about the media file stored in RAM 134 can be a media ID. This information can also be the storage location of the media file corresponding to the identifier in the playback device allocation table, for example, a storage location in RAM 134. This information can also be a pointer to an identifier in the playback device allocation table, such as a URL, from which the control unit 130 can stream media files to drive the speaker.

[0536] If processor 131 determines that there is no entry associated with the identifier in the allocation table, or although there is an entry associated with the identifier, it does not contain an allocation relationship (e.g., it does not contain information about the data group), or it contains an update prompt, then processor 131 generates an AV (Playback Device) request signal, which is transmitted to server 111 via WLAN wireless network through transmit / receive unit 139. In the AV request signal, processor 131 notifies server 111 of the identifier and requests that the data group associated with that identifier be downloaded to RAM 134. Processor 131 may also send the device identifier, i.e., its processor identifier, along with the AV request signal to server 111, thereby enabling itself to be identified on server 111.

[0537] In response to the AV request signal from processor 131, server 111 checks allocation table 313 stored on server 111 (see...). Figure 7 The server 111 checks if an entry exists in the allocation table 313 for the identifier. In allocation table 313, the identifier is assigned information about the data group, i.e., the media ID. If the server 111 finds an entry for the identifier and thus information about the data group (media file) in allocation table 313, the server 111 checks if the entry in allocation table 313 that assigns the identifier to the media ID is also assigned in media table 310. If the entry assigned the media ID there has a media file stored on the server, such as a media file stored in database server 305, the server 111 transmits that media file to playback device 1. If the entry assigned the media ID there is a pointer, the server 111 transmits that pointer to playback device 1. The processor 131 updates the AV allocation table in RAM 134 and assigns information about the downloaded data group or the downloaded pointer to the identifier. The processor 131 then uses this data group or pointer to drive speaker 138.

[0538] Figure 5 A playback device (playback device 1) for reproducing audio information is shown. Playback device 1 can communicate with server 111 via communication / computer network 110. Communication / computer network 110 has a wireless communication path 300, such as communication via WLAN. Playback device 1 can communicate with router 301 via communication path 300. Router 301 is connected to an Internet node (not shown) via a cable. The signal of playback device 1 can be transmitted from the Internet node (not shown) to another Internet node (not shown) via the Internet shown as cloud 302. Cloud gate 303 (symbolically shown as a door) is connected to the other Internet node (not shown) via a cable. Cloud gate 303 represents the entrance to server 111. Server 111 has cloud gate 303, a sub-server called cloud service 304, and database server 305.

[0539] If playback device 1 is turned on or awakened from sleep mode, a first routine is executed within playback device 1. As part of this first routine, playback device 1 reads the AV allocation table. After reading the AV allocation table, playback device 1 transmits the AV allocation table, the execution time in processor 131, and the firmware version for processor 131 to server 111 via communication / computer network 110. The internet address of cloud gate 303 is stored in playback device 1. Playback device 1 sends signals to cloud gate 303 via WLAN 300 and router 301, and via the internet 302. Signals arriving at cloud gate 303 are checked by cloud gate 303 to determine if they are valid. Here, the certificate belonging to the playback device and transmitted with the signal is verified.

[0540] After the cloud gate 303 checks whether the signal from the playback device 1 is valid, the cloud gate 303 allows the signal to pass through the cloud service sub-server 304.

[0541] Cloud service 304 verifies whether the time transmitted along with the signal from playback device 1 is correct. If incorrect, cloud service 304 sends a correction signal to playback device 1 to set the time. This correction signal is sent to playback device 1 via cloud gate 303, Internet 302, router 301, and WLAN 300.

[0542] In addition, cloud service 304 also checks the firmware version of playback device 1, which is also transmitted along with the signal. If cloud service 304 determines that a new firmware version exists for that specific playback device 1, then cloud service 304 retrieves the file with the corresponding new firmware version from database server 305. Cloud service 304 then pushes the updated firmware to playback device 1 through cloud gateway 303, Internet 302, router 301, and WLAN 300.

[0543] Cloud service 304 also examines all identifiers transmitted to it along with the signal from playback device 1 to determine whether these identifiers, also transmitted to it by playback device 1 via the signal, are up-to-date.

[0544] After this initial routine, the time, firmware, and AV allocation table in playback device 1 are all up-to-date.

[0545] Figure 6 As shown, smartphone 112 can communicate with server 111 via communication / computer network 110. Figure 6 It is also shown that the laptop computer 306 can communicate with the server 111 via the communication / computer network 110.

[0546] Users can log in to the cloud service and authenticate via smartphone (112) or laptop (306).

[0547] Figure 7 Server 111 is shown as a rectangle. Figure 7 User table 307, stored in the server's memory, is shown. User table 307 shows, for example, two users, Paul and Martin. User table 307 also shows the password "password 1" assigned to user Paul in the operating system of server 111 and the password "password 2" assigned to user Martin in the operating system of server 111.

[0548] Figure 7 The user group table 309, stored in the server's storage, is also shown. (Example) Figure 7 As shown, user group table 309 contains a user group named "Family 1". User group table 309 allows administrators to be assigned to user groups. Figure 7 In the example, user Paul is assigned as the administrator of user group "Family 1", and user Martin is assigned as member 1 of user group "Family 1". User group "Family 1" consists of only two users, namely users Paul and Martin. This makes another field "Member 2" in user group table 309 for user group "Family 1" empty. User group table 309 can also exceed... Figure 7 The illustrated implementation includes more columns, arranged in ascending order, allowing for the assignment of more members to a user group. The number of users a user group can have is determined by a preset number of columns.

[0549] Figure 7 The media table 310 stored in the memory of server 111 is also shown. Media table 310 has a column for media IDs. Figure 7 In the example, the media ID uses the alphanumeric sequence "Song 1", "Song 2", "Song 3", "Song 4", "Song 5", and "Song 6". However, UID, UUID, or GUID can also be used as the media ID. Media table 310 contains a column "Media File". The name of the media file can be entered in this column, such as "Song 1.mp3". However, pointers can also be stored in the "Media File" column, such as the pointer www.database.eu / Song 2.mp3. Media table 310 can be used to assign corresponding media IDs to media files. Figure 7 In this embodiment, the media ID "Song 1" is assigned to the media file "Song 1.mp3", the media ID "Song 2" is assigned to the media file "www.database.eu / Song 2.mp3", the media ID "Song 3" is assigned to the media file "Song 3.mp3", the media ID "Song 4" is assigned to the media file "Song 4.mp3", the media ID "Song 5" is assigned to the media file "Song 5.mp3", and the media ID "Song 6" is assigned to the media file "Song 6.mp3".

[0550] exist Figure 7 In this implementation, server 111 has media storage 311. Media storage 311 may be a database server 305. Server 111 may be configured to interpret the correspondence between a specific filename (here, "song1.mp3") and a media ID (here, "song1") in the media table 310 as a pointer to a media file named "song1.mp3" stored in the media storage 311 of server 111, corresponding to the media file named "song1.mp3" with the media ID "song1". If server 111 receives a request to provide the media file "song1.mp3" corresponding to the media ID "song1", then server 111 may access media storage 311 to provide that specific media file. Server 111 may be configured to interpret a corresponding pointer (here, for example, "www.database.eu / song2.mp3") as indicating that the specific media file is not stored in the storage of server 111, and in particular, is not stored in media storage 311. If server 111 receives a request to provide a media file corresponding to the media ID "song 2", in this embodiment server 111 provides a pointer, namely www.database.eu / song2.mp3.

[0551] exist Figure 7 In the illustrated embodiment, the identifier table 312 is stored in the memory of the server 111. The identifier table 312 has columns for "Identifier" and "User". Figure 7 In the implementation, the column "Identifiers" contains identifiers 200001, 200002, 200003, and 200004. In identifier table 312, identifier 200001 corresponds to user Paul, identifier 200002 corresponds to user Paul, identifier 200003 corresponds to user Martin, and identifier 200001 corresponds to user group family 1. Figure 7 In this implementation, the identifier is a 6-digit number. However, other implementations are also possible, where the identifier may be, for example, a UID, UUID, or GUID.

[0552] exist Figure 7 In this implementation, allocation table 313 is stored in the memory of server 111. Allocation table 313 has columns for "Identifier" and "Media ID". Figure 7 In the implementation method, in Figure 7 In the shown running state, identifier 200001 corresponds to media ID "Song 1", identifier 200002 corresponds to media ID "Song 5", identifier 200003 corresponds to media ID "Song 3", and identifier 200004 corresponds to media ID "Song 2". Figure 7 In this implementation, allocation table 313 also includes a column "Media ID2". Figure 7 The server 111 shown in the diagram only has identifier 200003 listed in the "Media ID 2" column, corresponding to the media ID "Song 4". Figure 7 In this implementation, server 111 may be configured to assign the media ID (here, the media ID "Song 4" corresponding to identifier 200003) filled in the "Media ID 2" column to the identifier when an item exists in the column "Media ID 2". Thus, the item in column "Media ID 2" is hierarchically higher than the item in column "Media ID". The item in column "Media ID" can be understood as the default media ID.

[0553] exist Figure 7 In this implementation, the permission table 314 is stored in the memory of server 111. The permission table 314 has columns for "User" and "Media ID". Figure 7 In the implementation method, in Figure 7 In the running state of server 111 shown, media IDs "Song 1" and "Song 5" are assigned to user Paul in permission table 314. In this running state, media IDs "Song 3" and "Song 4" are assigned to user "Martin". Media ID "Song 2" is assigned to user group "Family 1".

[0554] Figure 8 The steps of a program routine on a server according to the present invention are shown, which a user can use to modify allocation table 313, in which a first media ID is assigned to an identifier. Figure 8 The steps of the program routine shown according to the invention are the step of receiving a change signal 315 by server 111. Change signal 315 is a signal generated by smartphone 112. Change signal 315 is transmitted by smartphone 112 to server 111 via Internet 302 and received by the server. The program routine is implemented such that server 111 interprets change signal 315 as a change signal. This can be achieved through the signal form itself, wherein the signal form of the change signal is selected such that information indicating that the signal is a change signal is included in the header. However, server 111 can also identify a received signal as a change signal in such a way that the change signal is a signal sent to server 111 in response to, for example, a library signal issued by server 111. Figure 8In this implementation, the change signal 315 includes the information "Identifier = 200002" and "Media ID = Song 1". This can be achieved by storing the numerical sequence "200002" at a specific position in the change signal 315 and the character sequence "Song 1" at a second predetermined position in the change signal 315. When the server 111 analyzes the signal solely by its position within the signal, the information "Identifier = 200002" and "Media ID = Song 1" can be extracted from such a change signal 315 without necessarily having the terms "Identifier" and "Media ID" within the signal itself.

[0555] exist Figure 8 In the shown operating state, server 111 receives change signal 315. In this operating state, media ID "song 5" is assigned to identifier 200002 in allocation table 313.

[0556] Figure 9 The steps of the procedure routine according to the invention are shown, which follow... Figure 8 Following the step of receiving the change signal 315, as shown. Figure 9 In the steps shown, server 111 deletes the allocation relationship between media ID "Song 5" and identifier 200002 from allocation table 313. This is in Figure 9 This is illustrated by deleting "Song 5" from the media ID "Song 5" row in allocation table 313, which is identified by identifier 200002.

[0557] Figure 10 The steps of the procedure routine according to the invention are shown, which follow... Figure 9 Following the steps shown. Figure 10 In the steps shown, server 111 assigns the media ID "Song 1" to identifier 200002 in allocation table 313. This is achieved by the server writing "Song 1" in the "Media ID" column in the row of identifier 200002 in allocation table 313.

[0558] As a result, the program routine is executed ( Figure 8 , Figure 9 and Figure 23 The sequence shown changes the identifier 200002 to the media file "Song 5", which can also be called the second media ID. In the allocation of the media file "Song 1", it can also be called the first media ID. Here, the first media ID (here: media ID "Song 1") is used before the execution of the program routine. Figure 7 It will not be assigned to the identifier 200002.

[0559] Figure 11 The steps of the library routines on the server 111 according to the present invention are shown. Figure 11The steps of the library routine shown are the steps of sending library signal 316. In an earlier part of the library routine (not shown), server 111 receives a library request signal sent by smartphone 112 to server 111. This library request signal contains a library standard. This library standard is selected such that, when applied, all media IDs corresponding to user Paul in identifier table 312 (library standard "user media ID") are read from permission table 314, without displaying media IDs assigned to user group "Family 1" in permission table 312. Library signal 316 contains information about user Paul being assigned media IDs "Song 1", "Song 5", and "Song 6" in permission table 314. This... Figure 11 The symbol is shown in the middle by the correspondence between library signal 316 and the entry of permission table 314 as shown by the dashed line, which assigns the entry to user Paul.

[0560] Figure 12 The steps of the inventory routine on server 111 according to the present invention are shown. Figure 12 The step shown in the inventory routine is the step of sending inventory signal 317. In an earlier part of the inventory routine (not shown), server 111 receives an inventory request signal sent by smartphone 112. This inventory request signal contains an inventory criterion. This inventory criterion is selected such that when server 111 applies this criterion, all identifiers stored in the server's identifier table 312 and assigned to a specific user or user group are read from the identifier table 312, where the specific user belongs to a specific user group according to server 111's user group table 309 (inventory criterion "user-identifier"). The inventory signal contains information about user Paul or the user group to which user Paul belongs according to user group table 309 (user group: "Family 1"), which is assigned identifiers 200001, 200002, and 200004 in identifier table 312. This... Figure 12 The symbol is shown in the middle by the correspondence between inventory signal 317 and the entry of permission table 312, which is shown by the dashed line, to user Paul and family 1.

[0561] Figure 13 A screen display 400 is shown, as it is produced by a user executing a GUI as part of the UI on a smartphone 112. As part of the screen display 400, a filter button 401 is provided, which the user can operate by interacting with the touchscreen of the smartphone 112. A filter button bar 402 is also provided, which... Figure 13 The implementation has four predefined filter buttons 403, namely the predefined filter buttons 403 "All", "My", "Specified" and "Available".

[0562] If a user presses the filter button 403 "All" by interacting with the touchscreen of smartphone 112, the user generates a library request with a library standard that, in the application of the server's library routine, causes all media IDs stored in the server's media table to be read (library standard "All"). If the user presses the filter button 403 "My" by interacting with the touchscreen of smartphone 112, the user generates a library request with a library standard that, in the application of the server's library routine, causes all media IDs read from the server's permissions table to be assigned to a specific user in the server's permissions table or to the user group to which that specific user belongs according to the server's user group table (library standard "User Media ID"). If a user presses the filter button 403 "Specified" by interacting with the touchscreen of smartphone 112, the user generates a library request with a library standard that, in the application of the server's library routines, causes all media IDs read from the server's permissions table to be assigned to a specific user in the server's permissions table or to the user group to which that specific user belongs according to the server's user group table, and to an identifier in the server's allocation table, which is assigned to a specific user or to the user group to which that specific user belongs according to the server's user group table (library standard "Assigned Media ID"). If a user presses the filter button 403 "Available" by interacting with the touchscreen of smartphone 112, the user generates a library request with a library standard that, in the application of the server's library routines, causes all media IDs read from the server's permissions table to be assigned to a specific user in the server's permissions table or to the user group to which that specific user belongs according to the server's user group table, and to an identifier not assigned in the server's allocation table, which is assigned to a specific user or to the user group to which that specific user belongs according to the server's user group table (library standard "Free Media ID").

[0563] The user interface controls the smartphone 112 to send library request signals. For example... Figure 11 As shown, the smartphone 112 and user interface receive library signal 316 in response to the issuance of a library request signal. All media IDs contained in library signal 316 are displayed to the user via the GUI, i.e., on screen display 400. Figure 13 In this implementation, the filter button 403 "All" is pressed, which is circled in the figure. The media IDs "Song 1", "Song 2", "Song 3", "Song 4", "Song 5", and "Song 6" contained in the library signal 316 are displayed in the central window 404 of the screen display 400 as content buttons 405. These buttons can be operated by the user through interaction with the touch screen of the smartphone 112.

[0564] according to Figure 11The transmitted library signal 316 includes, in addition to the media IDs ("Song 1", "Song 5", "Song 6") contained in the library signal, information about how these media IDs ("Song 1", "Song 5", "Song 6") are assigned to user Paul in the permission table 314 of server 111. This assignment is communicated to user Paul through a checkmark on the content button 405 used for media IDs "Song 1", "Song 5", "Song 6" in the screen display 400, unlike the content button 405 used for media IDs "Song 2", "Song 3", "Song 4".

[0565] Figure 13 The screen display 400 shows the result after receiving library signal 316, which is provided by server 111 in... Figure 11 It was issued during operation. Figure 11 In the running state, media IDs “Song 1”, “Song 5”, and “Song 6” were assigned to user Paul in permission table 314.

[0566] Figure 14 The screen display 407 is shown, as can be generated by the user on the smartphone 112 by executing a GUI as part of the UI. When the user presses the content button 405 in the screen display 400, it reaches the screen display 407.

[0567] The media ID selected in screen display 407 is shown as media image 415. Screen display 407 also includes information about the series to which the media ID belongs, playback time, audio content type (“radio drama”), content summary, author, and a list of names. Figure 14 The screen display 407 shown has an action button 408.

[0568] Figure 15 The screen display 409 is shown, as can be generated by the user on the smartphone 112 by executing a GUI as part of the UI. The user presses the screen display 407 (participating in...). Figure 14 Action button 408 in the () can access screen display 409 (participate) Figure 15 The media ID selected in screen display 409 is displayed as media image 415.

[0569] After pressing action button 408 in screen display 407, the user interface executes the UI inventory routine (Inventarroutine) and generates an inventory request signal. In order to generate Figure 15 The screen shown displays that the 409 UI inventory routine generates an inventory request with an inventory criterion that, when applied in the server's inventory routine, reads all identifiers stored in the server identifier table assigned to user Paul or the user group (family 1) to which user Paul belongs.

[0570] The user interface controls the smartphone 112 to send inventory request signals. For example... Figure 12 As shown, the smartphone 112 and its user interface receive the inventory signal 317 in response to the transmission of the inventory request signal. All identifiers contained in the inventory signal 317 are displayed to the user via a GUI, i.e., on a screen display 409. In the central window 411 of the screen display 409, identifiers 200001, 200002, and 200004 contained in the inventory signal 317 are displayed as identifier images 412, which can be operated by the user through interaction with the touchscreen of the smartphone 112.

[0571] The screen display 409 includes a scroll button 410. The user can scroll through the series of identifier images 412 displayed in the central window 411 by manipulating the scroll button 410. The user interface notes in the background which identifier image 412 is located in the selection box 413 of the central window 411, or notes in the background the identifier assigned to the identifier image 412 displayed in the selection box 413.

[0572] Screen display 409 has an action button 414. When the user presses the action button 414, the user interface generates a change signal 315. In this change signal 315, the user interface writes the identifier of the identifier image 412, causing the identifier image 412 to appear in the selection box 413 at the moment the action button 414 is pressed. The user interface also writes the media ID assigned to the media image 415 in the GUI display on screen display 409 to the change signal 315. After generating the change signal 315 in this way, the user interface causes the smartphone 112 to send the change signal 315. Server 111 receives the change signal 315 and performs a combination. Figure 8 , Figure 9 , Figure 10 The program routine of this type. In this case, the identifier 200002 is assigned to the media ID "song 6".

[0573] Figure 16 Shown after receiving the library signal Figure 13 The screen displays a 400 error, indicating that the library signal was generated while server 111 was running and the media ID "Song 6" had not yet been assigned to user Paul in permissions table 314. Figure 16 As can be seen, the content button 405 for media ID "Song 6" is not checked.

[0574] Figure 17 Shown in Figure 16 After pressing the content button 405 for the media ID "Song 6" Figure 14The screen display is 407. This can be seen from the fact that media image 415 is not checked in screen display 407. Because the GUI is notified via library signal 316 that the media ID "Song 6" has not yet been assigned to user Paul in permission table 314, the GUI constructs action button 408 in a different way. Figure 17 In the implementation, the operation button 408 is used to generate a release signal, that is, to generate a start signal for the transfer routine, which is used for... The first step in account activation is to generate a release signal. The GUI can then be configured to redirect the user back to the initial state after this. Figure 16 The screen display. If updated according to Figure 16 The screen displays and assigns the media ID "Song 6" to user Paul in permissions table 314, then the user can... Figure 13 In the transformation, the screen displays 400 (with a checkmark in the content button 405).

[0575] Figure 18 The screen display 416 is shown, and may be generated by the user on the smartphone 112 by executing a GUI as part of the UI. The screen display 416 may be generated by the UI when running a startup routine, and especially after the user logs in.

[0576] The screen display 416 has seven windows 417, 418, 419, 420, 421, 422, and 423. The contents of these windows 417, 418, 419, 420, 421, 422, and 423 can be determined by executing various routines within the scope of the startup routines via the UI.

[0577] Window 417 is used to display to the user the identifier assigned to their specific type, i.e., the content type, in the identifier table. Figure 18 In this implementation, the user is "Ulika". Figure 18 In the selected embodiment, the user Ulika has not yet been assigned an identifier of type "content type" in identifier table 312. To determine the content displayed in window 417, a UI inventory routine is executed within the scope of the UI startup routine. Here, the UI automatically generates an inventory request with an inventory criterion selected to read all identifiers stored in the server's identifier table that are assigned to a specific user or the user group to which that user belongs and whose identifier type is "content type" in the identifier table, when applied in the server's inventory routine. Figure 18In this embodiment, in response to such a generated inventory request signal from the server, the UI obtains an inventory signal. This inventory signal can be used to notify the UI that there is no identifier of type "content type" assigned to the user "Ulika" in identifier table 312. The GUI can then display default text in window 417, such as "Oh no! You don't have Tony yet!".

[0578] Window 419 is used to display to the user the identifier of a specific type, namely the creative type, assigned to them in the identifier table. Figure 18 In this implementation, the user is "Ulika". Figure 18 In the selected embodiment, three identifiers of type "Creative Type" have been assigned to user Ulika in identifier table 312. To determine the content to be displayed in window 419, a UI inventory routine is executed within the scope of the UI startup routine. Here, the UI automatically generates an inventory request with inventory criteria within the scope of the UI startup routine. The inventory criteria are selected such that, when applied in the server's inventory routine, all identifiers stored in the server identifier table assigned to a specific user or to a user group according to the server user group table, and identifiers of type "Creative Type" assigned in the identifier table, are read. Figure 18 In this implementation, the UI receives an inventory signal from the server in response to the generated inventory request signal, which in turn notifies the UI of the three identifiers assigned to the user "Ulika". This is displayed by the GUI in window 419. Figure 18 It is also shown that in the GUI, representative terms and images can be used instead of the identifier itself—that is, instead of the UID, UUID, or GUID that might be used as an identifier. This makes the display of identifiers to the user much simpler. However, in the background, the UI records the identifiers assigned to the corresponding images and corresponding representative terms.

[0579] In window 419, the identifiers of type "creative type" assigned to the user in identifier table 312 are shown in the form of identifier image 412.

[0580] Window 418 is used to display a media ID to the user. This media ID has not yet been assigned to the user in the permissions table, but because it belongs to the same series, it may be one of the media IDs that can be assigned to the user. To determine the content displayed within window 418, a UI library routine is executed within the scope of the UI startup routine. Here, the UI automatically generates a library query with a library standard within the scope of the UI startup routine. This library standard is selected so that when it is applied in the server's library routine, it can...

[0581] First, determine all identifiers in the server identifier table assigned to the user, or the user group to which the user belongs according to the server user group table. From this, determine which identifier to send the instruction indicating that the identifier is assigned to a specific series of identifiers, thereby determining the complete series of identifiers assigned to the user in the server identifier table.

[0582] Then, it reads all media IDs stored in the server media table that have an allocation relationship with one of these defined series.

[0583] Then, from these media IDs, determine the media IDs that are not assigned to a specific user in the server permissions table or that belong to the user group according to the server user group table.

[0584] A library query can be sent as a library request signal. Figure 18 In one embodiment, in response to the library request signal thus generated, the UI receives a library signal from the server with a media ID, which is used by the UI to display "Song 1", "Song 3", and "Song 4" in window 418 of the GUI.

[0585] The media ID, displayed to the UI along with library signal 316, is shown as content button 405 in window 418. The user can access screen display 407 by interacting with the GUI, specifically by pressing content button 405. Since this selected library standard only displays the media ID of user Ulika, whose media ID has not yet been assigned in the permissions table, the user can access the library by pressing content button 405 in window 418. Figure 17 The screen displays error code 407.

[0586] Window 420 is used to display a device identifier to the user, which is assigned to the user in the user table or the user group table of the user's group. To determine what to display within window 420, a UI inventory routine is executed within the scope of the UI startup routine. Here, the UI automatically generates an inventory query with a library standard selected to read all device identifiers (inventory standard "User Device Identifier") assigned to the user or user group, stored in the user table or the user group table of the user's group, when applied in the server's inventory routine. The inventory query is issued as an inventory request signal. Figure 18 In one embodiment, in response to the resulting inventory request signal, the UI receives an inventory signal with a device identifier from the server. Figure 18It also demonstrates that in the GUI, representative terms and images can be used instead of the device identifier itself, i.e., it could be the identifier's UID, UUID, or GUID. This simplifies the display of the user's device identifier. However, the UI records the device identifier in the background, assigning it to the corresponding image and the appropriate representative term.

[0587] Window 421 allows users to start UI user maintenance routines.

[0588] Windows 422 and 423 can be used to provide users with further information or direct them to other screen displays in the GUI or even other user interfaces, such as an online store.

[0589] Each window 417, 418, 419, 420, 421, 422, and 423 has an action button 408. By operating the action button 408, the user can switch from the screen display 416 to other screen displays or other programs in the GUI, such as the GUI used for the online store.

[0590] For example, pressing the action button 408 (“Discover More”) in window 418 can direct the user to... Figure 13 The screen displays 400.

[0591] Figure 19 The screen display 424 is shown, as it is generated by the user on a laptop by executing the GUI as part of the UI. Figure 18 and Figure 19 As can be seen from the use of the same reference numerals, screen displays 416 and 424 differ in the spatial arrangement of windows 417, 418, 419, 420, 421, 422 and 423 and the corresponding sizes of windows 417, 418, 419, 420, 421, 422 and 423, but the content displayed within the windows is the same.

[0592] Figure 20 The screen display 425 is shown, as it is generated by the user on the smartphone 112 by executing the GUI as part of the UI. When the user... Figure 18 When the screen displays the identifier image 412 in the operation window 419 of screen 416, for example, it can reach Figure 20 The screen displays 425.

[0593] The selected identifier is displayed as identifier image 412 on screen display 425. Further information about the identifier of identifier image 412 is given in information window 426. When the identifier of identifier image 412 is, for example, an identifier of identifier type "content type" and here an identifier of identifier type of a specific series (e.g., "Benjamin Blümchen"), information about that series can be reproduced in information window 426.

[0594] The screen display 425 also has a window 427 and a filter button 428, in Figure 20 In one embodiment, the filter button 428 has three predefined filter buttons 428, namely the predefined filter button 428 "New Content", the predefined filter button 428 "My Content", and the predefined filter button 428 "Details".

[0595] If a user presses the filter button 428 "New Content" via the touchscreen of smartphone 112, a library query with a library criterion is generated for the user, which is selected when it is applied in the library routines on the server.

[0596] First, determine it in the server identifier table. Figure 20 In the server identifier table, which family is the identifier type selected as the identifier assigned to?

[0597] Then, it reads all the media IDs stored in the server media table that belong to that series.

[0598] Then, from the determined media IDs, the media IDs that are not assigned to a specific user in the server permissions table or to the user group to which that user belongs according to the server user group table are identified.

[0599] If a user presses the filter button 428 "My Content" via the touchscreen of smartphone 112, a library query with a library criterion is generated for the user, which is selected when it is applied in the library routines on the server.

[0600] First, determine it in the server identifier table. Figure 20 In the server identifier table, which family is the identifier type selected as the identifier assigned to?

[0601] Then, it reads all the media IDs stored in the server media table that belong to that series.

[0602] Then, from the determined media ID, the media ID assigned to a specific user in the server permissions table or to the user group to which that user belongs according to the server user group table is determined.

[0603] If the user presses the filter button 428 "Details" by interacting with the touchscreen of the smartphone 112, the GUI generates a screen display that gives further details of the identifier of the identifier image 412, such as the content of the media ID currently assigned to the identifier, or the content of the media file for which the media ID assigned the identifier_current(Kennung_momentan) is located.

[0604] If the user presses button 405, then, for example, screen display 407 may appear. Because in Figure 20 In the illustrated embodiment, window 427 displays a media ID that has not yet been assigned to the user in the permissions table 314, which the user can access by pressing the content button 405. Figure 17 The screen shown displays error code 407.

[0605] The screen display 425 also provides scroll buttons 410. This allows users to switch between different identifiers.

[0606] The GUI can generate borders for the screen display it generates or a portion thereof, or header lines 429 and footer lines 430 that are identical for all screen displays or portions thereof generated by the GUI. The header lines 429 and footer lines 430 for a GUI used in a smartphone may differ from those for a GUI used in a laptop.

[0607] The header line 429 may include, for example, a home button 431, which allows the user to navigate to screen displays 423 or 424. The header line 429 may also include an inbox button 432, which allows the user to access a view displaying information.

[0608] Figure 21 The screen display 432 is shown, as it is generated by the user on the smartphone 112 by executing the GUI as part of the UI. Figure 21 The screen displays 432, when the user is... Figure 18 When the user operates the action button 408 in the operation window 419 of the screen display 416, the user can reach the screen display 432, for example. The screen display 432 has windows 433, 434, and 435. The screen display 433 also has a filter button 436. When the user operates the filter button 436 "All" by interacting with the touch screen of the smartphone 112, the user generates an inventory request with inventory criteria selected as follows: when applied in the server inventory routine, all identifiers stored in the server identifier table that are assigned to a specific user or belong to a user group according to the user group table, and have a specific identifier type "Creative Type" in the identifier table.

[0609] The identifier, in the form of an identifier image 412, is displayed to the user in window 433. This identifier is contained in an inventory signal, which is sent to the UI in response to an inventory signal with a corresponding inventory standard having a filter button 436. Furthermore, the user can initiate a routine via supplementary screen 436, through which the user is assigned an additional identifier in the server identifier table.

[0610] Windows 434 and 435 enable the GUI to offer users further interactive possibilities.

[0611] As in Figure 21 In the selected implementation, the identifier image 412 format displays user group information 437 to the user within the identifier image. User group information 437 can indicate which user group the identifier is assigned to in the server identifier table. The display of user group information 437 provides the user with the relationship between the identifier in the identifier table and the user group where the current user is an administrator. Such user group information 437 can be as follows: Figure 21 The implementation shown is "My Family". User group information 437 can also be used for users in the identifier table whose names contain user groups that are not administrators. Figure 21 The implementation method is "Ulika".

[0612] exist Figure 21 In the implementation of the method, the identifier image 412 may also include the change symbol 438.

[0613] Figure 22 This illustrates another display possibility for identifier image 412. Figure 22 In this implementation, the identifier image 412 does not contain user group information 437, but shows a change symbol 438. According to... Figure 22 The embodiment of the identifier image 412 also includes an allocation button (Zuweisungsknopf) 439. By pressing the allocation button 439, the user can trigger a UI lock routine or a UI unlock routine.

[0614] Figure 23 A view of window 440 is shown, which may be part of a screen display not shown in detail. This screen display is accessible when the user clicks the change symbol 438. The selected identifier is reproduced for the user in window 440. An assignment button 439, implemented as a slide button, is also provided for the user. The assignment button 439, implemented as a slide button, can take... Figure 23 The location within or through user interaction with the GUI. Figure 24 The position within. From Figure 23 The position in the middle to Figure 24When the user slides the assignment button 439 in the middle position, the user can trigger the UI lock routine. Figure 24 The position shown has changed to Figure 23 When the indicated location is reached, the user can trigger the UI unlock routine.

[0615] Figure 23 , Figure 24 The window 440 contains an action button 408. By clicking the action button 408, the user can trigger a routine that changes the user group in the server and assigns the identifier shown in window 440 to the user group shown as the family symbol 441 in window 440.

[0616] Window 440 also has a scroll button 410. In a preferred embodiment, the scroll button 410 is used to scroll an identifier shown in window 433. In an alternative embodiment, the scroll button 410 is used to jump back. Figure 21 The screen displays 432.

[0617] Figure 25 The screen displays 442, when the user is pressing... Figure 18 Pressing the action button 408 in window 420 in screen display 416 accesses screen display 442. Screen display 442 has windows 443 and 444. Screen display 443 also has a filter button 446. When the user presses the filter button 446 "All" by interacting with the touchscreen of smartphone 112, the user generates an inventory request with an inventory criterion selected to read all device identifiers stored in the user table and user group table, which are assigned to a specific user or the user group to which the user belongs according to the user group table, when applied in the server inventory routine.

[0618] Identifiers are displayed to the user in window 443 as AV image 447. These identifiers are transmitted along with inventory signals, which are sent to the UI in response to an inventory request signal with a filter button 446 corresponding to the inventory criteria. Furthermore, with the aid of supplementary screen 448, the user may be able to initiate routines to assign other device identifiers in the server's user table or user group table.

[0619] The GUI window 444 provides users with the possibility of further interaction.

[0620] In such a state Figure 25In the selected form of the AV image (playback device image) 447 in the implementation, user group information 437 is provided to the user within the AV image. User group information 437 can indicate which user group is assigned the device identifier in the server's user group table. Here, the display of user group information 437 indicates the possibility that a device identifier is assigned to a user in the user group table, and the current user is the administrator of that user group. Figure 25 As shown, such user group information 437 could be "My Family". User group information 437 can be used to list user groups in the server's user group table where the current user is not an administrator. Figure 25 The implementation method is "Ulika".

[0621] exist Figure 21 In some implementations, the AV image 447 may also include a change symbol 438.

[0622] Figure 26 The diagram shows a window 460 that can be displayed to the user via the GUI when the user presses action button 408 in window 421. Window 460 has an input window 461 where the user can enter an email address. The user can initiate the UI user maintenance routine by pressing action button 408 "Send Invitation".

Claims

1. A server (111) for providing media files for users to download, having • Operating system, in which users create their own content. • A media table (310) stored in memory, in which at least one first media ID is assigned to a first media file and a second media ID is assigned to a second media file. • An identifier table (312) stored in memory, in which identifiers that can be assigned to the identifier carrier (8) are assigned to the user, and • An allocation table (313) is stored in memory, in which... i. Ability to assign the first media ID and / or the second media ID to the identifier, and ii. The first media ID is not assigned to the aforementioned identifier. The feature is that a program routine is provided on the server (111) so that a user can modify the allocation table (313) and assign the first media ID to the identifier in the allocation table (313).

2. The server according to claim 1, characterized in that, The server (111) is designed to trigger the program routine by receiving a change signal (315), and the program routine includes the step of analyzing the change signal (315).

3. The server according to claim 1 or 2, characterized in that, include • Permissions table (314), in which media IDs are assigned to users, and / or • Permissions table (314), in which users are assigned to media IDs, and / or • Permissions table (314), in which media IDs are assigned to user groups, and / or • Permissions table (314), in which user groups are assigned to media IDs.

4. The server according to claim 3, characterized in that, A library routine is provided on the server (111) that causes a library signal (316) to be issued, the library signal (316) containing one or more media IDs, and the library routine includes... • The step of reading at least one media ID corresponding to a library standard from the media table (310), and / or • The step of reading at least one media ID from the permission table (314), which is assigned to the user and corresponds to a library standard.

5. The server according to claim 4, characterized in that, The library standard is selected such that, when the library standard is applied in a library routine, all media IDs stored in the media table (310) are read, and / or The library standard is selected such that, when applied in a library routine, all media IDs stored in the media table (310) and assigned specific metadata in the media table (310) are read, wherein the specific metadata is assigned to the media ID so that the media ID is classified into a specific series or a specific category, and / or The library standard is selected such that, when applied in a library routine, all media IDs assigned to a specific user or user group in the permission table (314) are read from the permission table (314), wherein the specific user belongs to the user group according to the user group table (309), and / or The library standard is selected such that, when applied in a library routine, all media IDs stored in the media table (310) and not assigned to a specific user or user group in the permissions table (314), wherein the specific user belongs to the user group according to the user group table (309), and / or The library standard is selected such that, when applied in a library routine, all media IDs assigned to a specific user or user group in the permission table (314) are read from the permission table (314), wherein the specific user belongs to the user group according to the user group table (309) and is assigned to an identifier in the allocation table (313), wherein the identifier is assigned to the specific user or user group in the identifier table (312), wherein the specific user belongs to the user group according to the user group table (309), and / or • The library standard is selected such that, when the library standard is applied in the library routine, all media IDs assigned to a specific user or user group in the permission table (314) are read from the permission table (314), wherein the specific user belongs to the user group according to the user group table (309) and is not assigned to an identifier in the allocation table (313), wherein the identifier is assigned to a specific user or user group in the identifier table (312), wherein the specific user belongs to the user group according to the user group table (309).

6. The server according to claim 5, characterized in that, The specific metadata refers to the style.

7. The server according to claim 6, characterized in that, The style is described as pop, classic, or RnB.

8. A system having • The server (111) according to any one of claims 1 to 7, or • Identifier carrier (8) and server (111) according to any one of claims 1 to 7, wherein the identifier carrier (8) has an identifier that can be read by a reading device, or • Playback device (1) and server (111) according to any one of claims 1 to 7, or • Identifier carrier (8) and server (111) according to any one of claims 1 to 7, wherein the identifier carrier (8) has an identifier that can be read by a reading device and a playback device (1).

9. The system according to claim 8, characterized in that, The playback device (1) has: • Speaker (138) or speaker connection, • Sensor (120), which is capable of determining the characteristics of an area of ​​its environment or changes in the characteristics of that environment. • Control unit (130) for controlling the speaker (139) or speaker connection to play music or narrate a story when the sensor (120) determines a characteristic in the area of ​​its environment or a change in the characteristic of the environment, or when the control unit (130) determines a specific change in the characteristic determined by the sensor (120).

10. A method for providing media files for a user to download from a server (111), wherein, The server (111) includes: • Operating system, within which the user is created. • A media table (310) stored in memory, in which at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file. • An identifier table (312) stored in memory, in which identifiers that can be assigned to the identifier carrier (8) are assigned to the user, and • An allocation table (313) is stored in memory, in which... i. Able to assign an identifier to at least the first media ID or the second media ID, and ii. Do not assign the first media ID to the identifier. The feature is that the user executes a program routine set on the server (111), by means of which the user changes the allocation table (313) and assigns the first media ID to the identifier in the allocation table (313).

11. A method for interacting with a server (111) according to any one of claims 1 to 7 via a user interface, characterized in that, Execute the UI change routine that issues a change signal (315), wherein the change signal (315) includes Media ID, or • Media ID and identifier.

12. A method for providing media files for a user to download from a server (111), wherein, The server (111) includes • Operating system, within which the user is created. • A media table (310) stored in memory, in which at least a first media ID is assigned to a first media file and a second media ID is assigned to a second media file. • An identifier table (312) stored in memory, in which identifiers that can be assigned to the identifier carrier (8) are assigned to the user, and • An allocation table (313) is stored in memory, in which... i. Able to assign an identifier to at least the first media ID or the second media ID, and ii. Do not assign the first media ID to the identifier. The feature is that a UI change routine that issues a change signal (315) is executed on the user interface, wherein the change signal (315) includes First Media ID, or First media ID and identifier, The server receives the change signal (315) and executes a program routine after receiving the change signal (315), by means of which the user changes the allocation table (313) and assigns the first media ID to the identifier in the allocation table (313).

13. The method according to claim 12, characterized in that, • The server (111) sends a library signal (316), which contains one or more media IDs, and • Execute UI library routines in the user interface, which include receiving library signals (316) issued by the server. • A change signal (315) is generated and sent in the UI library routine, wherein the change signal (315) contains one of the media IDs contained in the library signal (316).

14. A data processing apparatus comprising means for performing the steps of the method according to any one of claims 10 to 13.

15. A computer program product, wherein, The computer program product includes instructions that, when executed by a computer, enable the computer to perform the method according to any one of claims 10 to 13.

16. A computer-readable storage medium comprising instructions that, when executed by a computer, enable the execution of the method according to any one of claims 10 to 13.

Images