Methods, apparatus, storage media, and electronic devices for generating multimedia playlists
By allowing multiple accounts to jointly edit multimedia lists within multimedia application software, the problem of insufficient list sharing in existing technologies is solved, achieving greater sharing and flexibility.
Patent Information
- Application Number
- CN202011195180.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-10-30
- Publication Date
- 2025-10-31
- Estimated Expiration
- 2040-10-30
AI Technical Summary
In existing multimedia applications, multimedia lists can only be created and edited by the same account, lacking the ability for multiple accounts to edit together, resulting in insufficient list sharing.
The target account invites related accounts to jointly edit a multimedia list, generating and displaying shared information. The backend server updates and sends the updated list, supporting multiple accounts to edit together.
It enables multiple accounts to edit multimedia lists together, improving the list's sharing and flexibility.
Smart Images

Figure CN114443868B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, storage medium, and electronic device for generating a multimedia playlist. Background Technology
[0002] With the development of communication technology and the popularization of smart terminals, multimedia application software has developed rapidly. More and more users are using multimedia application software for leisure and entertainment. For example, users can use music software to listen to songs, use audiobook software to listen to books or listen to the radio, etc.
[0003] In current multimedia applications, after logging into their accounts, users can create multimedia playlists to save their favorite or interesting multimedia tracks. However, users can only edit the multimedia playlists they create, such as adding or deleting tracks.
[0004] In related technologies, the creation and editing of the same multimedia list can only be performed by the same account. Summary of the Invention
[0005] To address the technical problems existing in related technologies, embodiments of this application provide a method, apparatus, storage medium, and electronic device for generating multimedia lists, which can support multiple accounts to jointly edit a multimedia list, thereby improving the sharing of multimedia lists.
[0006] To achieve the above objectives, the technical solution of this application embodiment is implemented as follows:
[0007] In a first aspect, embodiments of this application provide a method for generating a multimedia playlist, including:
[0008] In response to the target account inviting a target associated account to jointly edit a first multimedia list, the shared information of the first multimedia list is presented to the target associated account; the shared information is generated based on the identification information of the target account and the identification information of the first multimedia list;
[0009] Receive the first multimedia list updated by the target associated account based on the shared information sent by the backend server, and display the updated first multimedia list.
[0010] Secondly, embodiments of this application also provide a method for generating a multimedia playlist, including:
[0011] In response to the operation of the target associated account jointly editing the first multimedia list, the first multimedia list obtained according to the shared information of the first multimedia list is displayed; the shared information includes the identification information of the target account and the identification information of the first multimedia list; the target account is the account that created the first multimedia list;
[0012] In response to the operation of updating the first multimedia list, the updated first multimedia list is displayed, and the updated first multimedia list is sent to the target account via a backend server.
[0013] In one optional embodiment, the step of responding to the operation of jointly editing the first multimedia list by the target associated accounts, and displaying the first multimedia list obtained based on the shared information of the first multimedia list, includes:
[0014] Upon receiving an invitation message to jointly edit a first multimedia list, the system displays information about the target account and the first multimedia list; the invitation message includes shared information about the first multimedia list; the information about the target account and the first multimedia list are obtained based on the shared information of the first multimedia list.
[0015] In response to the target associated account accepting the invitation to jointly edit the first multimedia list, the first multimedia list is displayed; the operation of accepting the invitation to jointly edit the first multimedia list is the operation of the target associated account jointly editing the first multimedia list.
[0016] In one alternative embodiment, the invitation message for jointly editing the first multimedia list is sent by a third-party social application based on shared information of the first multimedia list presented by the target account.
[0017] In one alternative embodiment, the operation of displaying the first multimedia list in response to the target associated account accepting an invitation to co-edit the first multimedia list includes:
[0018] In response to the invitation to co-edit the first multimedia list, if the number of accounts associated with the first multimedia list is less than a set number, the first multimedia list is displayed.
[0019] Thirdly, embodiments of this application also provide a method for generating a multimedia playlist, applied to a backend server, the method comprising:
[0020] Upon receiving an update request for the first multimedia list from the client corresponding to the target associated account, the first multimedia list is updated according to the update request; the target associated account is bound to the first multimedia list.
[0021] The updated content of the first multimedia list is sent to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list.
[0022] In an optional embodiment, after generating the binding relationship between the first multimedia list and the target account, the method further includes:
[0023] Upon receiving a request from the client corresponding to the target associated account to bind to the first multimedia list, a notification is sent to the client corresponding to the target account that created the first multimedia list, indicating that the target associated account has applied to jointly edit the first multimedia list; the request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the target associated account's application to jointly edit the first multimedia list.
[0024] Upon receiving a message from the client corresponding to the target account accepting the request from the target associated account to jointly edit the first multimedia list, a binding relationship is generated between the first multimedia list and the target associated account.
[0025] Fourthly, embodiments of this application also provide a multimedia playlist generation apparatus, comprising:
[0026] An information presentation unit is configured to, in response to an operation by which a target account invites a target associated account to jointly edit a first multimedia list, present the shared information of the first multimedia list to the target associated account; the shared information is generated based on the identification information of the target account and the identification information of the first multimedia list;
[0027] The first display update unit is used to receive the first multimedia list updated by the target associated account according to the shared information sent by the backend server, and to display the updated first multimedia list.
[0028] In one optional embodiment, the information presentation unit is specifically used for:
[0029] In response to a target account's instruction to share a first multimedia list, a selection of social applications is displayed.
[0030] In response to the target account selecting a target social application, a list of associated accounts of the target account in the selected target social application is displayed;
[0031] In response to the target account's operation of selecting a target associated account from the list of associated accounts, the shared information of the first multimedia list is sent to the target associated account through the target social application; the target account's operation of selecting a target associated account from the list of associated accounts is an operation in which the target account invites the target associated account to jointly edit the first multimedia list.
[0032] In an optional embodiment, the information presentation unit is further configured to:
[0033] In response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the shared information of the first multimedia list is displayed to the target associated account in the form of a QR code or NFC.
[0034] In an optional embodiment, the device further includes a list-type display unit for:
[0035] In response to an operation that creates a new multimedia list for a target account or an operation that modifies the multimedia list type for an existing first multimedia list, a selection of multimedia list types is displayed; the multimedia list types include those edited by multiple users.
[0036] In response to the target account confirming the selection of the multi-user collaborative editing type, the type of the first multimedia list is displayed as the multi-user collaborative editing type.
[0037] Fifthly, embodiments of this application also provide a multimedia playlist generation apparatus, comprising:
[0038] The list display unit is used to display the first multimedia list obtained based on the shared information of the first multimedia list in response to the operation of the target associated accounts jointly editing the first multimedia list; the shared information includes the identification information of the target account and the identification information of the first multimedia list; the target account is the account that created the first multimedia list;
[0039] The second display update unit is configured to display the updated first multimedia list in response to the operation of updating the first multimedia list;
[0040] The first list sending unit is used to send the updated first multimedia list to the target account via a backend server.
[0041] In one optional embodiment, the list display unit is specifically used for:
[0042] Upon receiving an invitation message to jointly edit a first multimedia list, the system displays information about the target account and the first multimedia list; the invitation message includes shared information about the first multimedia list; the information about the target account and the first multimedia list are obtained based on the shared information of the first multimedia list.
[0043] In response to the target associated account accepting the invitation to jointly edit the first multimedia list, the first multimedia list is displayed; the operation of accepting the invitation to jointly edit the first multimedia list is the operation of the target associated account jointly editing the first multimedia list.
[0044] In one alternative embodiment, the invitation message for jointly editing the first multimedia list is sent by a third-party social application based on shared information of the first multimedia list presented by the target account.
[0045] In an optional embodiment, the list display unit is further configured to:
[0046] In response to the invitation to co-edit the first multimedia list, if the number of accounts associated with the first multimedia list is less than a set number, the first multimedia list is displayed.
[0047] In an optional embodiment, the list display unit is further configured to:
[0048] In response to the operation of searching the first multimedia list for the target associated account, the information of the first multimedia list is displayed; the information of the first multimedia list is obtained based on the identification information of the target account or the identification information of the first multimedia list.
[0049] In response to the request to jointly edit the first multimedia list, if the target user accepts the request to jointly edit the first multimedia list, the first multimedia list is displayed.
[0050] Sixthly, embodiments of this application also provide a multimedia playlist generation apparatus, comprising:
[0051] The list update unit is used to receive an update request for the first multimedia list sent by the client corresponding to the target associated account, and update the first multimedia list according to the update request; the target associated account has a binding relationship with the first multimedia list;
[0052] The second list sending unit is used to send the updated content of the first multimedia list to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list.
[0053] In an optional embodiment, the apparatus further includes a first binding relationship generation unit, configured to:
[0054] Upon receiving a request from the client corresponding to the target associated account to bind to the first multimedia list, if the number of accounts currently bound to the first multimedia list is less than a set number, a binding relationship is generated between the first multimedia list and the target associated account; the request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the target associated account accepting an invitation to co-edit the first multimedia list or the target associated account applying to co-edit the first multimedia list.
[0055] The binding relationship between the first multimedia list and the target account is generated based on the identification information of the first multimedia list and the identification information of the target account.
[0056] In an optional embodiment, the apparatus further includes an identification information generation unit and an identification information sending unit.
[0057] The identification information generation unit is used to receive a multimedia list creation request sent by the client corresponding to the target account and generate identification information for the first multimedia list; the multimedia list creation request indicates the creation of a first multimedia list of the type of collaborative editing by multiple users;
[0058] The identification information sending unit is used to send the identification information of the first multimedia list to the client corresponding to the target account.
[0059] In one optional embodiment, the apparatus further includes a notification sending unit and a second binding relationship generation unit.
[0060] The notification sending unit is configured to receive a request from the client corresponding to the target associated account to bind the first multimedia list, and send a notification to the client corresponding to the target account that created the first multimedia list that the target associated account has applied to jointly edit the first multimedia list; the request to bind the first multimedia list is sent by the client corresponding to the target associated account in response to the operation of the target associated account applying to jointly edit the first multimedia list;
[0061] The second binding relationship generation unit is used to receive information sent by the client corresponding to the target account accepting the application of the target associated account to jointly edit the first multimedia list, and to generate a binding relationship between the first multimedia list and the target associated account.
[0062] In a seventh aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the multimedia list generation method of any of the first aspects described above.
[0063] Eighthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the multimedia list generation method of any of the second aspects described above.
[0064] In a ninth aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the multimedia list generation method of any of the third aspects described above.
[0065] In a tenth aspect, embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the computer program is executed by the processor, the processor causes the processor to implement the multimedia list generation method of any of the first aspects described above.
[0066] Eleventhly, embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program that can run on the processor, and when the computer program is executed by the processor, the processor causes the processor to implement the multimedia list generation method of any of the second aspects described above.
[0067] In a twelfth aspect, embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program executable on the processor, and when the computer program is executed by the processor, the processor implements the multimedia list generation method of any of the third aspects described above.
[0068] The multimedia list generation method, apparatus, storage medium, and electronic device provided in this application allow a target account to invite a target associated account to jointly edit a first multimedia list. This presents shared information about the first multimedia list to the target associated account, enabling the target associated account to update the first multimedia list based on this shared information. Upon receiving the updated first multimedia list from the backend server, the target account can display the updated list. This method supports multiple accounts jointly editing the same multimedia list, improving the sharing capabilities of multimedia lists. Attached Figure Description
[0069] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0070] Figure 1 An application scenario diagram illustrating a multimedia playlist generation method provided in this application embodiment;
[0071] Figure 2 An information interaction diagram illustrating a method for generating a multimedia playlist provided in an embodiment of this application;
[0072] Figure 3 An information interaction diagram illustrating another method for generating a multimedia playlist provided in this application embodiment;
[0073] Figure 4 A schematic diagram illustrating a display scenario of a target client provided in an embodiment of this application;
[0074] Figure 5 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0075] Figure 6 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0076] Figure 7 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0077] Figure 8 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0078] Figure 9 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0079] Figure 10 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0080] Figure 11 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0081] Figure 12 A schematic diagram illustrating a display scenario of an associated client provided in an embodiment of this application;
[0082] Figure 13 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0083] Figure 14 A schematic diagram illustrating another display scenario of an associated client provided in an embodiment of this application;
[0084] Figure 15 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0085] Figure 16 A schematic diagram illustrating another display scenario of an associated client provided in an embodiment of this application;
[0086] Figure 17 A schematic diagram illustrating another display scenario of an associated client provided in an embodiment of this application;
[0087] Figure 18 A schematic diagram illustrating another display scenario of a target client provided in an embodiment of this application;
[0088] Figure 19 A flowchart illustrating a method for generating a multimedia playlist provided in an embodiment of this application;
[0089] Figure 20 A flowchart illustrating another method for generating a multimedia playlist provided in an embodiment of this application;
[0090] Figure 21 A flowchart illustrating another method for generating a multimedia playlist provided in an embodiment of this application;
[0091] Figure 22 A structural block diagram of a multimedia playlist generation device provided in this application embodiment;
[0092] Figure 23 A structural block diagram of another multimedia list generation apparatus provided in an embodiment of this application;
[0093] Figure 24 A structural block diagram of another multimedia list generation apparatus provided in an embodiment of this application;
[0094] Figure 25 A structural block diagram of another multimedia list generation apparatus provided in an embodiment of this application;
[0095] Figure 26 A structural block diagram of another multimedia list generation apparatus provided in an embodiment of this application;
[0096] Figure 27 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;
[0097] Figure 28This is a schematic diagram of the structure of another electronic device provided in an embodiment of this application. Detailed Implementation
[0098] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0099] It should be noted that the terms "comprising" and "having" and their variations used in this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or device.
[0100] The terms "first" and "second" used in this document are for descriptive purposes only and should not be construed as indicating relative importance or implying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.
[0101] The word “exemplary” as used below means “serving as an example, embodiment, or illustration.” Any embodiment illustrated as an “exemplary” need not be construed as superior to or better than other embodiments.
[0102] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments.
[0103] Figure 1 This illustrates an application scenario of the multimedia playlist generation method provided in this application embodiment. See [link to relevant documentation]. Figure 1 As shown, the backend server 100 communicates with the terminal devices through the network 200. The network 200 can be, but is not limited to, a local area network, a metropolitan area network, or a wide area network. The number of terminal devices connected to the backend server 100 can be multiple. For example, the terminal devices can include the terminal device 300 corresponding to the target account that creates the multimedia list, and the terminal device 301 corresponding to the target associated account that receives the shared information of the multimedia list sent by the target account.
[0104] Terminal devices 300 and 301 can transmit communication data and messages to each other via network 200 and backend server 100. Terminal devices 300 and 301 can be portable devices (e.g., mobile phones, tablets, laptops), or computers, smart screens, or personal computers (PCs). Multimedia application clients can be installed on both terminal devices 300 and 301.
[0105] The backend server 100 can be a server for a multimedia application. The backend server 100 can be any device with network connectivity and data processing capabilities. For example, the backend server 100 can be a cloud server or a collection of servers consisting of one or more servers.
[0106] Target users can register target accounts through multimedia application clients installed on terminal device 300. These multimedia applications can be music applications, audiobook applications, radio applications, etc. When a target user registers a target account, the multimedia application client obtains the target account's identification information from the backend server 100. This identification information, such as the target account's ID, is assigned by the backend server 100 to uniquely identify the target account.
[0107] The multimedia application client logged in by the target account can be referred to as the target client. After logging into the target client based on the target account, the target user can create a multimedia playlist within the target client. Upon receiving the target user's request to create a multimedia playlist, the target client sends a multimedia playlist creation request to the backend server 100. The multimedia playlist creation request carries the identification information of the target account corresponding to the target user. Upon receiving the multimedia playlist creation request from the client corresponding to the target account, the backend server 100 generates the identification information of the multimedia playlist and sends this identification information to the terminal device 300. The identification information of the multimedia playlist is used to uniquely identify the multimedia playlist. For example, the identification information of the multimedia playlist can be the ID of the multimedia playlist, etc. The backend server 100 can also generate a binding relationship between the multimedia playlist and the target account based on the identification information of the target account and the identification information of the multimedia playlist.
[0108] To improve the sharing capabilities of multimedia lists, in this embodiment, after creating a multimedia list, a target user can invite friends to jointly edit the list. These friends can be referred to as target associated users. When the terminal device 300 receives the target user's invitation to target associated users to jointly edit the multimedia list, it can generate sharing information for the multimedia list based on the target account's identification information and the multimedia list's identification information, and then share this information with the target associated user's corresponding target associated account.
[0109] The target associated user can log in to the target associated account through a multimedia application client installed on terminal device 301. Upon receiving shared information about a multimedia list shared by the target user, the target associated account considers it to have received an invitation from the target user. Based on the shared information of the multimedia list, the target associated account can display the information of the inviting target user and the multimedia list to the target associated user, allowing the target associated user to decide whether to accept the invitation. If the target associated user accepts the invitation, terminal device 301 can send the acceptance information to backend server 100. Upon receiving the acceptance information, backend server 100 can generate a binding relationship between the target associated account and the multimedia list, and return a successful binding notification to terminal device 301. At this point, both the target user and the target associated user can jointly edit the multimedia list.
[0110] The above Figure 1 The application scenario described above is merely an example of one application scenario for implementing the embodiments of this application, and the embodiments of this application are not limited to the above. Figure 1 The application scenarios described.
[0111] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation steps as shown in the following embodiments or drawings, the method may include more or fewer operation steps based on conventional or non-inventive methods. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.
[0112] In one embodiment, a target user can proactively invite target associated users to jointly edit a multimedia playlist, a process that can be completed collaboratively by the target client, the backend server, and associated clients. Figure 2 An interactive flowchart of a multimedia playlist generation method is shown, such as... Figure 2 As shown, the method may include the following steps:
[0113] In step S201, the target client receives the operation to create a new multimedia list from the target account and displays the multimedia list types to choose from.
[0114] Optionally, a target user can apply to register a target account through a music application's client, referred to as the target client. Upon receiving the target user's request to register a target account, the target client sends a registration request to the backend server. The backend server, upon receiving the registration request, generates identification information for the target account based on the request and sends this information to the target client. Upon receiving the identification information from the backend server, the target client displays the completed registration to the target user.
[0115] It should be noted that, in the description of the embodiments of this application, the target client refers to the client that logs in to the target account, which can be any client of the music application. The target client is no different from other clients of the music application, and the process of other clients interacting with the backend server is the same as that of the target client.
[0116] The target client can create a new multimedia playlist based on the target user's actions, used to store multimedia tracks that the target user likes or is interested in. These multimedia tracks can be, but are not limited to, songs, music, other audio files—such as books, or video files. In this embodiment, a playlist in a music application is used as an example to describe in detail the method for generating a multimedia playlist.
[0117] In one embodiment, after receiving an operation from a target user to create a new multimedia list, the target client can generate a blank multimedia list. For example, the target user clicking on a music application installed on the target client can open a multimedia list such as... Figure 4 The application homepage shown is in Figure 4 In this context, the target client can open, based on the target user's click on "My," such as... Figure 5 The page shown. In Figure 5 In this context, the target client can leverage the user's action of clicking the "+" option next to "Custom Playlist" to open, for example... Figure 6 The page shown. In Figure 6 In the context of custom playlists, the target user can click the "Create New Playlist" option within the "Custom Playlists" section. Upon receiving this action, the target client generates a new playlist. The newly generated playlist will look like this: Figure 7 As shown.
[0118] The target client can set a name for a newly generated multimedia playlist based on the target user's actions, and can also set the type of the multimedia playlist. After receiving the target user's action to set the multimedia playlist type, the target client can display a selection of multimedia playlist types to the target user. For example, the target client can, based on the target user's actions, in... Figure 7 The page shown allows users to configure newly created playlists, such as editing the playlist name (e.g., naming it "Lu's playlist") and setting the playlist type. When the target user clicks "Playlist Type," the target client receives the user's instruction to set the multimedia playlist type and displays the available multimedia playlist types to the user. For example... Figure 8 As shown, the target client presents three playlist types to the target user: "Independent Playlist," "Couple Playlist," and "Friends Playlist." "Couple Playlist" and "Friends Playlist" are collaborative editing options, while "Independent Playlist" is an individual editing option.
[0119] In step S202, the target client receives confirmation from the target account that the multi-user collaborative editing type has been selected, and the multimedia list is displayed as a multi-user collaborative editing type.
[0120] For example, the target client is based on the target user from Figure 8 The operation of selecting one of the three playlist types shown allows the target user to use their chosen playlist type as the type of the newly generated playlist. Upon receiving the target user's selection, the target client displays the selected playlist type. When the target user selects "Independent Playlist," the client displays "Lu's playlist" as an independent playlist, indicating that only the target user can edit this playlist. When the target user selects "Couple Playlist," the client displays "Lu's playlist" as a couple playlist, indicating that two users can edit this playlist, and the two users editing the playlist can be a couple. When the target user selects "Friends Playlist," the client displays "Lu's playlist" as a friends playlist, indicating that two or more users can edit this playlist. Therefore, when the playlist type is set to "Couple Playlist" or "Friends Playlist," the currently displayed playlist type is for multi-user collaborative editing.
[0121] When the playlist type is a collaborative editing type, the specific display method can be as follows: Figure 9As shown, a "+" button next to a person's portrait or avatar indicates that the playlist is for collaborative editing, allowing more people to join. If the playlist is for individual editing, only one person's portrait or avatar will be displayed, indicating that only that person can edit the playlist.
[0122] In one embodiment, after receiving an operation from a target user to create a new multimedia list, the target client can display selectable multimedia list types to the target user. After receiving an operation from the target user confirming the selection of a multi-user collaborative editing type from among multiple selectable multimedia list types, the target client can display to the target user that the current multimedia list type is a multi-user collaborative editing type. For example, the target client can display the multi-user collaborative editing type based on the target user's selection of a new multimedia list type. Figure 6 Clicking the "Create New Playlist" option on the page shown will open... Figure 7 The page shown. In Figure 7 In the middle, the target client opens up options such as "Playlist Type" based on the target user's click on the "Playlist Type" option. Figure 8 The page shown. In Figure 8 In the process, after the target user selects "Couple Playlist", the target client can display the newly created playlist as a couple playlist.
[0123] In another embodiment, when creating a new playlist, the target client can set the playlist type to "Independent Playlist" based on the target user's actions. Alternatively, when creating a new multimedia playlist, the target client can select the individual editing type as the multimedia playlist type based on the target user's instructions. At any time after the multimedia playlist is created, if the target user wishes to modify the multimedia playlist type, they can do so through the multimedia playlist type settings page by entering an operation to modify the multimedia playlist type. The target client modifies the multimedia playlist type based on the target user's input. After receiving the target user's operation to modify the multimedia playlist type for an existing multimedia playlist, the target client displays the available multimedia playlist types to the target user. After receiving the target user's confirmation of selecting the multi-user collaborative editing type from among the multiple available multimedia playlist types, the target client can display to the target user that the current multimedia playlist type is the multi-user collaborative editing type.
[0124] For example, given a created playlist, if a target user clicks "Playlist Type" on the playlist's settings page, the target client receives the user's action to modify the playlist type and can display something like... Figure 8The page shown includes three playlist types to choose from. If the target user selects "Couple Playlist," the target client receives confirmation from the target user and displays the playlist as a couple playlist to the target user.
[0125] Optionally, based on the target user's action, the target client can also choose whether to make the created multimedia playlist public. If the target user chooses to make the playlist public, the target client can display the playlist as visible to everyone using the music application, or in other words, all registered users of the music application. Alternatively, if the target user chooses not to make the playlist public, the target client can display the playlist as private. If the multimedia playlist is private and is a individually edited playlist, it is only visible to the target user. If the multimedia playlist is private and is a collaboratively edited playlist, it is only visible to users who have a binding relationship with it and can edit the playlist; other registered users cannot see it.
[0126] For example, after creating a new playlist, the target client can open, based on the target user's actions, such as... Figure 7 The page shown Figure 7 The system displays that newly created playlists are public by default, meaning they are visible to everyone. Based on the target user's actions, the target client can change the playlist to private. When the target client, based on the target user's instructions, simultaneously sets the playlist to independent, it is only visible to the target user. When the target client, based on the target user's instructions, simultaneously sets the playlist to a couple's playlist, it is only visible to the target user and one other user invited by the target user to co-edit the playlist; others cannot see it. When the target client, based on the target user's instructions, simultaneously sets the playlist to friends' playlist, it is visible to the target user and multiple other users invited by the target user to co-edit the playlist; others cannot see it.
[0127] In step S203, the target client sends a multimedia playlist creation request to the backend server.
[0128] The associated client can send multimedia playlist creation requests, or other requests mentioned below, to the backend server based on the TCP or UDP protocol.
[0129] Step S203 can be executed after step S202, before step S202, or simultaneously with step S201. That is, the target client can send a multimedia list creation request to the backend server after receiving an operation from the target account to create a new multimedia list; alternatively, the target client can send a multimedia list creation request to the backend server after receiving a selection of the multimedia list type from the target account. The multimedia list creation request may include identification information of the target account, such as the target account ID.
[0130] In step S204, the backend server generates the identification information of the multimedia list based on the multimedia list creation request sent by the target client.
[0131] In step S205, the backend server sends the identification information of the multimedia list to the target client.
[0132] After receiving a multimedia playlist creation request from the target client, the backend server generates identification information for the multimedia playlist based on the request and sends the identification information to the target client.
[0133] Optionally, after receiving a multimedia playlist creation request from the target client, the backend server can first determine whether the request is valid. For example, the logic for this determination could be whether the target account is already a registered and valid account. The backend server can determine whether the target account is among the registered accounts based on the identifier information of the target account included in the multimedia playlist creation request. If it is, the target account is considered valid, and the backend server can confirm the multimedia playlist creation request as valid, generate valid and unique multimedia playlist identifier information, and send this identifier information, such as the multimedia playlist ID, to the target client. Upon receiving the multimedia playlist identifier information from the backend server, the target client stores the identifier information along with other information of the multimedia playlist, such as playlist type and playlist name. The target client can also generate shared information for the multimedia playlist based on the target account identifier information and the multimedia playlist identifier information. If the target account is not among the registered accounts, or if the account information is incorrect, the target account is not considered valid, and the backend server can confirm the multimedia playlist creation request as invalid and send a request failure message to the target client. After receiving a request failure message from the backend server, the target client can display a notification message to the target user indicating that the creation of a new multimedia list failed.
[0134] In step S206, the backend server generates a binding relationship between the multimedia list and the target account based on the identification information of the multimedia list and the identification information of the target account.
[0135] Steps S206 and S205 can be executed in the opposite order. After the backend server establishes the binding relationship between the multimedia list and the target account, the target account has the permission to edit the multimedia list.
[0136] In step S207, the target client receives an invitation from the target account to the target associated account to jointly edit the multimedia list.
[0137] In step S208, the target client sends the shared information of the multimedia list to the associated client.
[0138] In some embodiments, after receiving an instruction from the target user to share a multimedia playlist, the target client can display a list of selectable associated users to the target user. This list of associated users may be the target user's friend list within a music application. Upon receiving an instruction from the target user to select a target associated user from the associated user list, the target client treats this instruction as an invitation from the target account to the target associated account to jointly edit the multimedia playlist, and sends the multimedia playlist sharing information to the target associated user. The target associated user can be any friend from the target user's friend list, or a friend selected by the target user.
[0139] The multimedia list sharing information is generated based on the target account's identification information and the multimedia list's identification information. This information can be generated by the target client after receiving the multimedia list's identification information from the backend server, or by the target client after receiving an instruction from the target user to share the multimedia list, or by the backend server generating the information based on the target account's identification information and the multimedia list's identification information and then sending it to the target client.
[0140] In some embodiments, after receiving an instruction from a target user to share a multimedia list, the target client can display a selection of social applications to the target user. After receiving an instruction from the target user to select a target social application, the target client can display a list of associated users in the selected target social application. After receiving an instruction from the target user to select a target associated user from the list of associated users, the target client can send the sharing information of the multimedia list to the target associated user through the selected target social application.
[0141] For example, after setting a playlist as a friends playlist, the target client can open, based on the target user's actions, such as... Figure 9 The page shown is in Figure 9 In the process, the target user can invite friends to co-create playlists. When the target user clicks the "+" option on the page, the target client receives the user's instruction to share the playlist. Figure 10 The page shown displays a selection of social applications for the target user. Figure 10 The interface showcases three selectable social applications. Based on the target user's actions, the target client can choose from "Social Application 1," "Social Application 2," and "Social Application 3" to invite friends to co-create a playlist. If the target user selects "Social Application 1," the target client can retrieve the list of associated users from Social Application 1 and display it to the target user; alternatively, the target client can launch Social Application 1, which will then display the list of associated users from "Social Application 1," which could be the target user's friends list or contacts. Figure 11 As shown, in the associated user list of "Social Application 1", the target client can select associated users to invite to co-create the playlist based on the target user's actions. For example, the associated user list may display users A, B, C, and D. Based on the target user's actions, the target client can select user A and invite user A to co-create the playlist. The target client can then send the multimedia playlist sharing information to the target associated user, i.e., user A, through Social Application 1. This multimedia playlist sharing information can be in the form of a QR code, a URL (Uniform Resource Locator) link, or NFC (Near Field Communication) technology.
[0142] Optionally, the target user can also select multiple target associated users simultaneously from the associated user list. When the target client receives the user's selection of target associated users from the list, if the number of selected target associated users exceeds the set number allowed for co-editing in the current multimedia playlist type, the target client will prompt the user that too many target associated users have been selected, thus keeping the number of selected target associated users within the set number allowed for co-editing in the current multimedia playlist type. For example, if the target client sets the playlist as a couple playlist based on the user's instructions, only one friend can be invited to co-create the playlist. If the target client sets the playlist as a friend playlist based on the user's instructions, two or more friends can be invited to co-create the playlist.
[0143] In other embodiments, when a target client receives an invitation from a target account to a target associated account to jointly edit a multimedia playlist, it can display the shared information of the multimedia playlist to the target associated user in the form of a QR code. Here, the target associated account is the account corresponding to the target associated user. The target associated user can use the associated client to scan the QR code containing the shared information of the multimedia playlist displayed by the target client, thereby enabling them to jointly edit the multimedia playlist created by the target user. For example, based on the action of target associated user A clicking on the same music application, the associated client can open... Figure 4 The software homepage shown is in Figure 4 In this scenario, based on the target user A clicking the "Scan" icon, the associated client can scan the QR code in the target client and co-create a shared playlist using the QR code. Alternatively, based on the target user using a third-party social application, such as the scanning function of social application 1, the associated client can scan the QR code displayed on the target client and co-create a shared playlist using the QR code.
[0144] In other embodiments, when a target client receives an invitation from a target account to a target associated account to jointly edit a multimedia list, the target client can display the shared information of the multimedia list to the target associated user in NFC format. Specifically, an NFC card containing the shared information of the multimedia list is displayed on the target client's interface. The target associated user can use the NFC function in their associated client or terminal device to read the shared information of the multimedia list displayed by the target account and jointly edit the corresponding multimedia list with the target user.
[0145] Step S209: The associated client displays the target account information and multimedia list information obtained based on the shared information of the multimedia list.
[0146] In some embodiments, the target client sends the shared information of the multimedia playlist to the associated client of the target associated user. Upon receiving the shared information of the multimedia playlist from the target client, the associated client considers it as receiving an invitation message from the target client to co-edit the multimedia playlist. The associated client can obtain the target account information based on the target account identification information in the shared information of the multimedia playlist. For example, the associated client can obtain the target account name or the name or nickname of the target user corresponding to the target account based on the target account ID. The associated client can also obtain the multimedia playlist information based on the multimedia playlist identification information in the shared information of the multimedia playlist. For example, the associated client can obtain the playlist name or playlist co-creator information based on the playlist ID. The associated client can then display the obtained target account information and multimedia playlist information to the target associated user. The display interface can be as follows: Figure 12 As shown.
[0147] In other embodiments, the target client (the target user's music application client) sends the shared information of the multimedia playlist to the target associated user through a third-party social application, i.e., the target social application selected by the target user as described above. The third-party social application client corresponding to the target associated user receives the shared information of the multimedia playlist sent by the target user through the third-party social application and displays the shared information to the target associated user. Upon receiving the action of the target associated user clicking on the shared information, the third-party social application client corresponding to the target associated user launches the associated client (the target associated user's music application client) and sends an invitation message to the associated client to jointly edit the multimedia playlist. This invitation message includes the shared information of the multimedia playlist. Upon receiving the invitation message to jointly edit the multimedia playlist from the third-party social application client, the associated client can obtain the target account information and the multimedia playlist information based on the shared information of the multimedia playlist included in the invitation message, and display the target account information and the multimedia playlist information to the target associated user.
[0148] In other embodiments, the target client displays the shared information of the multimedia list to the target associated user in the form of a QR code. The target associated user can scan the QR code displayed by the target client using the scanning function of the associated client or a third-party social application. If the target associated user scans the QR code displayed by the target client using the associated client, the associated client recognizes the shared information of the multimedia list in the QR code, which is considered as receiving an invitation message to co-edit the multimedia list. The associated client can then obtain the target account information and the multimedia list information based on the shared information and display these information to the target associated user. If the target associated user scans the QR code displayed by the target client using a third-party social application, the third-party social application client recognizes the shared information of the multimedia list in the QR code, launches the associated client, and sends an invitation message to co-edit the multimedia list, which includes the shared information of the multimedia list. Upon receiving the invitation message to co-edit the multimedia list from the third-party social application client, the associated client can obtain the target account information and the multimedia list information based on the shared information included in the invitation message and display these information to the target associated user.
[0149] In other embodiments, the target client displays the shared information of the multimedia list to the target associated user via NFC. After enabling NFC on its terminal device, the target associated user can read the shared information of the multimedia list displayed by the target client. The terminal device then initiates an invitation message from the associated client to jointly edit the multimedia list, which includes the shared information of the multimedia list. Upon receiving the invitation message, the associated client can obtain the target account information and the multimedia list information based on the shared information included in the invitation message, and then display the target account information and the multimedia list information to the target associated user.
[0150] In some embodiments, the invitation message for co-editing a multimedia playlist received by the associated client may be sent by the user who created the multimedia playlist. In other embodiments, the invitation message may be sent by a user with editing permissions for the multimedia playlist. For example, user Lu creates a multimedia playlist of the type "Friends Playlist," and invites user A to co-edit the playlist. In this case, the invitation message for co-editing the multimedia playlist received by user A's music application client is sent by user Lu, who created the multimedia playlist. After accepting the invitation, user A gains editing permissions for the multimedia playlist. Then, user A can invite user B to co-edit the multimedia playlist. In this case, the invitation message for co-editing the multimedia playlist received by user B's music application client is sent by user A, who has editing permissions for the multimedia playlist.
[0151] In step S210, the associated client receives an invitation from the target associated account to jointly edit the multimedia list and generates a request to bind the multimedia list.
[0152] For example, target user Lu creates a couple's playlist and invites target associated user Tong to co-edit the playlist. The shared information for the playlist can be sent to Tong's associated client. Tong's associated client, upon receiving this information, can then... Figure 12 The interface displayed shows the target account's information and playlist information, allowing the target user Tong to decide whether to accept the invitation based on the displayed information. When the target user Tong clicks... Figure 12 When the "Confirm" option appears on the page, the associated client receives an invitation from the target associated account Tong to jointly edit the couple's playlist with the target user Lu, and generates a request to bind the couple's playlist.
[0153] For example, target user Lu creates a playlist for friends and invites target associated user A to co-edit the playlist. The playlist sharing information can be sent to target associated user A's associated client. Target associated user A's associated client receives the playlist sharing information and can then... Figure 14 The interface shown displays information about the target account and playlists, allowing the target user A to decide whether to accept the invitation based on the displayed information. When the target user A clicks... Figure 14 When the "Confirm" option appears on the page, the associated client receives an invitation from the target associated account A to jointly edit the friend's playlist with the target user Lu, and generates a request to bind the friend's playlist.
[0154] Step S211: The associated client sends a request to the backend server to bind the multimedia list.
[0155] The request to bind the multimedia list includes the identification information of the target associated account and the identification information of the multimedia list.
[0156] Step S212: If the number of accounts currently bound to the multimedia list is less than the set number, the backend server generates the binding relationship between the multimedia list and the target associated account.
[0157] After receiving a request from a related client to bind a multimedia list, the backend server, based on the multimedia list's identifier information in the request, can obtain the number of accounts bound to that multimedia list. It then determines whether the number of accounts currently bound to the multimedia list exceeds a set limit, which can be set according to the multimedia list type. When the number of bound accounts is less than the set limit, the target associated account of the target user is bound to the multimedia list, generating a binding relationship between the multimedia list and the target associated account. For example, if a target user creates a couple's playlist and shares it with three associated users, since the set limit for co-editing a couple's playlist is two, only one associated user can join the playlist after all three accept the invitation; the other two will be notified that the maximum number of accepted invitations has been reached. Similarly, if a target user creates a friends' playlist and sets the maximum number of accounts that can be bound to it to five, the limit is set to five. The target user shares the playlist with 3 associated users. Since the playlist can support up to 5 users to edit it together, all 3 associated users can join the playlist once they accept the invitation.
[0158] In step S213, the backend server sends a notification of successful binding to the associated client.
[0159] For example, the backend server can send a JSON / XML notification message to the associated client via the Xmpp protocol. This notification message carries the identification information of the multimedia list, informing the associated client that the target associated account has been successfully bound to the multimedia list.
[0160] In step S214, the associated client receives a notification from the backend server that the binding was successful and displays the multimedia list obtained based on the shared information of the multimedia list.
[0161] Upon receiving a successful binding notification, the associated client displays the content of the multimedia list invited for co-editing to the target associated user, such as... Figure 13 As shown or Figure 15 As shown.
[0162] In step S215, the backend server sends a notification to the target client that the target associated account has been successfully bound to the multimedia list.
[0163] For example, the backend server can send a JSON / XML notification message to the target client via the Xmpp protocol, informing the target client that the target associated account has been successfully bound to the multimedia list.
[0164] In step S216, the target client displays information about the target associated accounts jointly editing the multimedia list.
[0165] After the backend server generates the binding relationship between the multimedia list and the target associated account, it sends a notification to the target client that the binding between the target associated account and the multimedia list is successful. Upon receiving this notification, the target client displays information about the target associated account jointly editing the multimedia list.
[0166] For example, if the target associated user Tong clicks Figure 12 The "Confirm" option on the page triggers a request from the client to the backend server to bind the couple's playlist. After the backend server generates the binding relationship between the couple's playlist and the target account "Tong," it sends a notification to the target client that the binding between the target account "Tong" and the couple's playlist is successful. Upon receiving this notification, the target client can display... Figure 13 The page shown indicates that the target linked account Tong is jointly editing the couple's playlist, and it is currently in the state of being jointly created by the two people.
[0167] For example, if the target associated user A clicks... Figure 14 The "Confirm" option on the page triggers a request from the client to the backend server to bind the friend's playlist. After the backend server generates the binding relationship between the friend's playlist and the target account A, it sends a notification to the target client that the binding between account A and the friend's playlist is successful. Upon receiving this notification, the target client can display... Figure 15 The page shown indicates that the target associated account A is jointly editing this friend's playlist, and it is currently in a state of multiple people jointly creating this friend's playlist.
[0168] Step S217: The associated client receives the operation of updating the multimedia list of the target associated account.
[0169] After accepting an invitation from a target user to co-edit a multimedia playlist, the associated client can edit the playlist based on the target user's instructions. For example, after accepting an invitation from a target user to co-edit a friends' playlist, the associated client can perform editing operations such as adding songs, saving songs, deleting songs, and changing the playlist name based on the target user's instructions.
[0170] In step S218, the associated client sends an update request for the multimedia list to the backend server.
[0171] The associated client can send update requests or requests for binding multimedia lists to the backend server based on TCP or UDP protocols.
[0172] Step S219: The background server updates the multimedia list according to the update request.
[0173] In step S220, the backend server sends the updated multimedia list to the target client and associated clients.
[0174] After receiving an edit operation from the target associated user on the multimedia list, the associated client can send an update request for the multimedia list to the backend server. Upon receiving the update request, the backend server can update the multimedia list according to the update request and send the updated multimedia list after the edit operation to both the target client and the associated client.
[0175] For example, target user A, target associated user B, and target associated user C jointly create a playlist. After receiving an order from target associated user B to add the song "Boy" to the playlist, the associated client can send a request to the backend server to add the song "Boy" to the playlist. Upon receiving this request, the backend server can add the song "Boy" to the playlist, update the playlist, and send the updated playlist to the target client of target user A, the associated client of target associated user B, and the associated client of target associated user C, respectively.
[0176] In step S221, both the target client and the associated client display the updated multimedia list.
[0177] The multimedia list generation method provided in the above embodiments incorporates social features during the multimedia list creation process. This allows multiple accounts to collaboratively edit the same multimedia list, improving its sharing capabilities, efficiency, and making the creation process more engaging. After creating a multimedia list, a target user can invite multiple related users to collaboratively edit it, thereby expanding the social attributes of the multimedia list. This enables multiple users to jointly build the same multimedia list, increasing communication and interaction among users and enhancing the connection between the multimedia list and multiple users.
[0178] In another embodiment, the target associated user can actively request to jointly edit a multimedia list created by the target user, a process that can be jointly completed by the target client, the backend server, and the associated client. Figure 3 An interactive flowchart of another multimedia playlist generation method is shown, such as... Figure 3 As shown, the method may include the following steps:
[0179] Step S301: The associated client receives the operation of the target associated user searching the multimedia list.
[0180] Step S302: The associated client sends a search request for the target associated user to the backend server.
[0181] In step S303, the backend server searches the multimedia list based on the search request of the target associated user.
[0182] In step S304, the backend server sends the searched multimedia list results to the associated client.
[0183] Step S305: The associated client displays the searched multimedia list results.
[0184] In step S306, the associated client receives the operation of the target associated user selecting the multimedia list and displays the multimedia list information.
[0185] Based on instructions from the target user, the associated client can search for multimedia lists created by other users, such as the target user's multimedia list. Upon receiving an instruction from the target user to search for multimedia lists, the associated client can send a search request to the backend server. Upon receiving this request, the backend server can search for relevant multimedia lists and send information about all found multimedia lists to the associated client. After receiving the multimedia list results from the backend server, the associated client can display all found multimedia lists to the target user. When the target user selects a multimedia list, the associated client can display detailed information about that list. For example, the target user can select from a list... Figure 4 On the page shown, click the "Search Box" to search. Target users can search for playlists by entering the song, artist, lyrics, album, or the name or nickname of the playlist creator. When the associated client receives a search query from the target user... Figure 4 After entering the song name "Hi Maki" in the search box, a search request for "Hi Maki" is sent to the backend server. Upon receiving the request, the backend server searches for all playlists containing "Hi Maki" and sends the search result to the associated client. After receiving the search result from the backend server, the associated client can display the result to the target user, such as... Figure 16 The search results page shown is in Figure 16 The page displays six playlists: A, B, C, D, E, and F. After receiving a request from the target user to select playlist A, the associated client can display detailed information about playlist A to that user.
[0186] Optionally, the associated client receives the target associated user's... Figure 4 After entering the playlist name "Lu'splaylist" in the search box, a search request for "Lu's playlist" is sent to the backend server. Upon receiving the request, the backend server searches for playlist results corresponding to "Lu's playlist" and sends these results to the associated clients. After receiving the playlist results from the backend server, the associated clients can display the results to the target associated users as follows: Figure 17 The search results page shown is in Figure 17 The page displays a playlist titled "Lu's playlist" created by the target user, Lu. When the associated client receives an action from the target user clicking on "Lu's playlist," it can display detailed information about the playlist to the target user.
[0187] Step S307: The associated client receives the request from the target associated user to jointly edit the multimedia list.
[0188] Step S308: The associated client sends a request to the backend server to bind the multimedia list.
[0189] The request to bind the multimedia playlist carries the playlist's identifier information. The associated client receives the request from the target associated user to co-edit the multimedia playlist and sends a request to the backend server to bind the playlist. For example, on the page displaying details of the playlist "Lu's playlist" to the target associated user, the associated client has a "Request to Join" button. When the target associated user clicks the "Request to Join" button, the associated client receives the request from the target associated user to co-edit the playlist and sends a request to the backend server from the target associated user to bind the playlist.
[0190] In step S309, the backend server determines that the number of accounts currently bound to the multimedia list is less than a set number.
[0191] After receiving a request from a related client for a target user to co-edit a multimedia list, the backend server, based on the multimedia list's identifier information carried in the request, can obtain the number of accounts bound to that multimedia list. It then determines whether the number of accounts currently bound to the multimedia list exceeds a preset limit, which can be set according to the multimedia list type. If the number of bound accounts equals the preset limit, the backend server rejects the target user's request. If the number of bound accounts is less than the preset limit, the backend server approves the target user's request to co-edit the multimedia list.
[0192] In step S310, the backend server sends a notification to the target client that the target associated user has requested to jointly edit the multimedia list.
[0193] The target client is the client corresponding to the target account that created the multimedia playlist. The backend server can determine the target account that created the multimedia playlist based on the multimedia playlist's identifier information.
[0194] Step S311: The target client displays information to the target user regarding the target associated user's request to jointly edit the multimedia list.
[0195] Step S312: The target client receives a request from the target user to accept the request from the target associated user to jointly edit the multimedia list.
[0196] Step S313: The target client sends a message to the backend server that the target user has accepted the application.
[0197] For example, the associated client can, based on the instruction of the target associated user A, [do something]. Figure 4 Entering the playlist name "Lu's playlist" in the search box will find the playlist created by the target user Lu, also named "Lu's playlist". After receiving a request from the target user A to co-edit this playlist, the associated client can send this request to the backend server. Upon receiving the request from the associated client, the backend server determines that the number of accounts currently linked to this playlist is 3, which is less than the set number of 5. If so, it approves the request and sends it to the target client. After receiving this request, the target client can then... Figure 18 The interface shown displays information about the target associated account, allowing the target user Lu to decide whether to accept the application based on the displayed information. When the target user Lu clicks... Figure 18 When the "Confirm" option appears on the page, after the target client receives the request from the target user to accept the request from the target associated user A to jointly edit the friend's playlist, it can send a request to the backend server confirming the target user's acceptance of the request.
[0198] In step S314, the backend server generates a binding relationship between the multimedia list and the target associated account based on the message that the target user accepts the application from the target associated user.
[0199] After receiving a request from the target client that the target user has accepted the request from the target associated user to jointly edit the multimedia list, the backend server can bind the target associated user's target associated account to the multimedia list, thus generating a binding relationship between the multimedia list and the target associated account.
[0200] In step S315, the backend server sends a notification of successful binding to the associated client.
[0201] In step S316, the associated client receives a notification from the backend server that the binding was successful and displays the multimedia list.
[0202] After receiving notification from the target user that the application has been accepted, the associated client displays the content of the multimedia list to the target associated user, such as... Figure 15 As shown.
[0203] In step S317, the backend server sends a notification to the target client that the target associated account has been successfully bound to the multimedia list.
[0204] In step S318, the target client displays information about the target associated accounts jointly editing the multimedia list.
[0205] After the backend server generates the binding relationship between the multimedia list and the target associated account, it sends a notification to the target client that the binding between the target associated account and the multimedia list is successful. Upon receiving this notification, the target client displays information about the target associated account jointly editing the multimedia list.
[0206] Step S319: The associated client receives the operation of updating the multimedia list of the target associated account.
[0207] Once the target user accepts the request to jointly edit the multimedia playlist, the associated user can edit the multimedia playlist.
[0208] In step S320, the associated client sends an update request for the multimedia list to the backend server.
[0209] Step S321: The background server updates the multimedia list according to the update request.
[0210] In step S322, the backend server sends the updated multimedia list to the target client and associated clients.
[0211] After receiving an edit operation from the target associated user on the multimedia list, the associated client can send an update request for the multimedia list to the backend server. Upon receiving the update request, the backend server can update the multimedia list according to the update request and send the updated multimedia list after the edit operation to both the target client and the associated client.
[0212] In step S323, both the target client and the associated client display the updated multimedia list.
[0213] Based on the same inventive concept, this application also provides a method for generating a multimedia playlist, which is applied to a target client, or terminal device. For example... Figure 19 As shown, the method may include the following steps:
[0214] Step S1901: In response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the shared information of the first multimedia list is presented to the target associated account.
[0215] Specifically, the target client can send the shared information of the first multimedia list to the client corresponding to the target associated account, or the target client can display the shared information of the first multimedia list to the target associated account.
[0216] Step S1902: Receive the first multimedia list updated by the target associated account based on shared information sent by the backend server, and display the updated first multimedia list.
[0217] In one optional embodiment, in response to the target account inviting a target associated account to jointly edit a first multimedia list, the shared information of the first multimedia list is presented to the target associated account, including:
[0218] In response to a target account's instruction to share a first multimedia list, a selection of social applications is displayed.
[0219] In response to the target account selecting a target social application, a list of associated accounts of the target account in the selected target social application is displayed;
[0220] In response to the target account's action of selecting a target associated account from the associated account list, the shared information of the first multimedia list is sent to the target associated account via the target social application; the target account's action of selecting a target associated account from the associated account list is an action of the target account inviting the target associated account to jointly edit the first multimedia list.
[0221] In one optional embodiment, in response to the target account inviting a target associated account to jointly edit a first multimedia list, the shared information of the first multimedia list is presented to the target associated account, including:
[0222] In response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the shared information of the first multimedia list is displayed to the target associated account in the form of a QR code or NFC.
[0223] In an optional embodiment, before presenting the shared information of the first multimedia list to the target associated account in response to the target account inviting the target associated account to jointly edit the first multimedia list, the method further includes:
[0224] In response to an operation that creates a new multimedia list for a target account or modifies the multimedia list type for an existing multimedia list, a selection of multimedia list types is displayed; multimedia list types include those edited by multiple users.
[0225] In response to the target account confirming the selection of the multi-user collaborative editing type, the first multimedia list is displayed as the multi-user collaborative editing type.
[0226] Based on the same inventive concept, this application also provides a method for generating a multimedia list, which is applied to an associated client, or terminal device. For example... Figure 20 As shown, the method may include the following steps:
[0227] Step S2001: In response to the operation of the target associated accounts jointly editing the first multimedia list, the first multimedia list obtained based on the shared information of the first multimedia list is displayed.
[0228] In step S2002, in response to the operation of updating the first multimedia list, the updated first multimedia list is displayed, and the updated first multimedia list is sent to the target account through the background server.
[0229] In one alternative embodiment, in response to the operation of the target associated accounts jointly editing the first multimedia list, displaying the first multimedia list obtained based on the shared information of the first multimedia list includes:
[0230] Upon receiving an invitation message to jointly edit a first multimedia list, the system displays the target account's information and the information of the first multimedia list; the invitation message includes shared information about the first multimedia list; the target account's information and the information of the first multimedia list are obtained based on the shared information of the first multimedia list.
[0231] In response to the target associated account accepting the invitation to jointly edit the first multimedia list, the first multimedia list is displayed; the operation of accepting the invitation to jointly edit the first multimedia list is the operation of the target associated account jointly editing the first multimedia list.
[0232] In one alternative embodiment, the invitation message for co-editing the first multimedia list is sent by a third-party social application based on shared information from the first multimedia list presented by the target account.
[0233] In one alternative embodiment, in response to the target associated account accepting an invitation to co-edit a first multimedia list, displaying the first multimedia list includes:
[0234] In response to the invitation to co-edit the first multimedia list, if the number of accounts associated with the first multimedia list is less than a set number, the first multimedia list will be displayed.
[0235] In one alternative embodiment, in response to the operation of the target associated accounts jointly editing the first multimedia list, displaying the first multimedia list obtained based on the shared information of the first multimedia list includes:
[0236] In response to the operation of searching the first multimedia list for the target associated account, the information of the first multimedia list is displayed; the information of the first multimedia list is obtained based on the identification information of the target account or the identification information of the first multimedia list.
[0237] In response to the request to jointly edit the first multimedia list, if the target user accepts the request to jointly edit the first multimedia list, the first multimedia list is displayed.
[0238] Based on the same inventive concept, this application also provides a method for generating a multimedia playlist, which is applied to a backend server. For example... Figure 21 As shown, the method may include the following steps:
[0239] Step S2101: Receive an update request for the first multimedia list sent by the client corresponding to the target associated account, and update the first multimedia list according to the update request.
[0240] Step S2102: Send the updated content of the first multimedia list to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list.
[0241] In an optional embodiment, before receiving an update request for the first multimedia list sent by the client corresponding to the target associated account, and before updating the first multimedia list according to the update request, the method further includes:
[0242] Upon receiving a request from the client corresponding to the target associated account to bind to the first multimedia list, if the number of accounts currently bound to the first multimedia list is less than a set number, a binding relationship is generated between the first multimedia list and the target associated account. The request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the target associated account's acceptance of an invitation to co-edit the first multimedia list or the target associated account's application to co-edit the first multimedia list.
[0243] In an optional embodiment, before receiving an update request for the first multimedia list from a client of the target associated account, and before updating the first multimedia list according to the update request, the method further includes:
[0244] Upon receiving a multimedia playlist creation request from the client corresponding to the target account, the system generates identification information for the first multimedia playlist; the multimedia playlist creation request indicates the creation of a first multimedia playlist of a type that can be edited by multiple users.
[0245] The identification information of the first multimedia list is sent to the client corresponding to the target account, and the binding relationship between the first multimedia list and the target account is generated based on the identification information of the first multimedia list and the identification information of the target account.
[0246] In an optional embodiment, after generating the binding relationship between the first multimedia list and the target account, the above method further includes:
[0247] Upon receiving a request from the client corresponding to the target associated account to bind to the first multimedia list, a notification is sent to the client corresponding to the target account that created the first multimedia list, indicating that the target associated account has requested to jointly edit the first multimedia list; the request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the operation of the target associated account requesting to jointly edit the first multimedia list;
[0248] Upon receiving a message from the client corresponding to the target account accepting the request from the target associated account to jointly edit the first multimedia list, a binding relationship is generated between the first multimedia list and the target associated account.
[0249] and Figure 19 The multimedia playlist generation method shown is based on the same inventive concept. This application also provides a multimedia playlist generation device, which can be deployed in a terminal device. Since this device corresponds to the multimedia playlist generation method of this application, and the principle by which this device solves the problem is similar to that of the method, the implementation of this device can refer to the implementation of the above method; repeated details will not be elaborated further.
[0250] Figure 22 This illustration shows a schematic diagram of a multimedia playlist generation apparatus provided in an embodiment of this application. Figure 22 As shown, the multimedia list generation device includes: an information presentation unit 2201 and a first display update unit 2202; wherein,
[0251] The information presentation unit 2201 is used to respond to the operation of the target account inviting the target associated account to jointly edit the first multimedia list, and to present the shared information of the first multimedia list to the target associated account; the shared information is generated based on the identification information of the target account and the identification information of the first multimedia list;
[0252] The first display update unit 2202 is used to receive the first multimedia list updated by the target associated account according to the shared information sent by the backend server, and to display the updated first multimedia list.
[0253] In one optional embodiment, the information presentation unit 2201 is specifically used for:
[0254] In response to a target account's instruction to share a first multimedia list, a selection of social applications is displayed.
[0255] In response to the target account selecting a target social application, a list of associated accounts of the target account in the selected target social application is displayed;
[0256] In response to the target account's action of selecting a target associated account from the associated account list, the shared information of the first multimedia list is sent to the target associated account via the target social application; the target account's action of selecting a target associated account from the associated account list is an action of the target account inviting the target associated account to jointly edit the first multimedia list.
[0257] In an optional embodiment, the information presentation unit 2201 is further configured to:
[0258] In response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the shared information of the first multimedia list is displayed to the target associated account in the form of a QR code or NFC.
[0259] In one alternative embodiment, such as Figure 23 As shown, the multimedia list generation device may further include a list type display unit 2301, used for:
[0260] In response to an operation that creates a new multimedia list for a target account or modifies the multimedia list type for an existing multimedia list, a selection of multimedia list types is displayed; multimedia list types include those edited by multiple users.
[0261] In response to the target account confirming the selection of the multi-user collaborative editing type, the first multimedia list is displayed as the multi-user collaborative editing type.
[0262] and Figure 20 The multimedia playlist generation method shown is based on the same inventive concept. This application also provides a multimedia playlist generation device, which can be deployed in a terminal device. Since this device corresponds to the multimedia playlist generation method of this application, and the principle by which this device solves the problem is similar to that of the method, the implementation of this device can refer to the implementation of the above method; repeated details will not be elaborated further.
[0263] Figure 24 This illustration shows a schematic diagram of a multimedia playlist generation apparatus provided in an embodiment of this application. Figure 24 As shown, the multimedia list generation device includes: a list display unit 2401, a second display update unit 2402, and a first list sending unit 2403; wherein,
[0264] The list display unit 2401 is used to display the first multimedia list obtained based on the shared information of the first multimedia list in response to the operation of the target associated account jointly editing the first multimedia list; the shared information includes the identification information of the target account and the identification information of the first multimedia list; the target account is the account that created the first multimedia list;
[0265] The second display update unit 2402 is used to display the updated first multimedia list in response to the operation of updating the first multimedia list;
[0266] The first list sending unit 2403 is used to send an updated first multimedia list to the target account via a backend server.
[0267] In an optional embodiment, the list display unit 2401 is specifically used for:
[0268] Upon receiving an invitation message to jointly edit a first multimedia list, the system displays the target account's information and the information of the first multimedia list; the invitation message includes shared information about the first multimedia list; the target account's information and the information of the first multimedia list are obtained based on the shared information of the first multimedia list.
[0269] In response to the target associated account accepting the invitation to jointly edit the first multimedia list, the first multimedia list is displayed; the operation of accepting the invitation to jointly edit the first multimedia list is the operation of the target associated account jointly editing the first multimedia list.
[0270] In one alternative embodiment, the invitation message for co-editing the first multimedia list is sent by a third-party social application based on shared information from the first multimedia list presented by the target account.
[0271] In an optional embodiment, the list display unit 2401 is further configured to:
[0272] In response to the invitation to co-edit the first multimedia list, if the number of accounts associated with the first multimedia list is less than a set number, the first multimedia list will be displayed.
[0273] In an optional embodiment, the list display unit 2401 is further configured to:
[0274] In response to the operation of searching the first multimedia list for the target associated account, the information of the first multimedia list is displayed; the information of the first multimedia list is obtained based on the identification information of the target account or the identification information of the first multimedia list.
[0275] In response to the request to jointly edit the first multimedia list, if the target user accepts the request to jointly edit the first multimedia list, the first multimedia list is displayed.
[0276] and Figure 21The multimedia playlist generation method shown is based on the same inventive concept. This application also provides a multimedia playlist generation device, which can be deployed in a server. Since this device corresponds to the multimedia playlist generation method of this application, and the principle by which this device solves the problem is similar to that of the method, the implementation of this device can refer to the implementation of the above method; repeated details will not be elaborated further.
[0277] Figure 25 This illustration shows a schematic diagram of a multimedia playlist generation apparatus provided in an embodiment of this application. Figure 25 As shown, the multimedia list generation device includes: a list updating unit 2501 and a second list sending unit 2503; wherein,
[0278] The list update unit 2501 is used to receive an update request for the first multimedia list sent by the client corresponding to the target associated account, and update the first multimedia list according to the update request; the target associated account and the first multimedia list are bound together.
[0279] The second list sending unit 2502 is used to send the updated content of the first multimedia list to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list.
[0280] In one alternative embodiment, such as Figure 26 As shown, the above-mentioned device may further include an identification information generation unit 2601, an identification information sending unit 2602, a first binding relationship generation unit 2603, a notification sending unit 2604, and a second binding relationship generation unit 2605; wherein,
[0281] The identification information generation unit 2601 is used to receive a multimedia list creation request sent by the client corresponding to the target account and generate identification information for the first multimedia list; the multimedia list creation request indicates the creation of a first multimedia list of the type of collaborative editing by multiple users;
[0282] The identification information sending unit 2602 is used to send the identification information of the first multimedia list to the client corresponding to the target account;
[0283] The first binding relationship generation unit 2603 is used to receive a request from the client corresponding to the target associated account to bind to the first multimedia list. If the number of accounts currently bound to the first multimedia list is less than a set number, a binding relationship between the first multimedia list and the target associated account is generated. The request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the target associated account's acceptance of an invitation to co-edit the first multimedia list or the target associated account's application to co-edit the first multimedia list. The binding relationship between the first multimedia list and the target account is generated based on the identification information of the first multimedia list and the identification information of the target account.
[0284] The notification sending unit 2604 is used to receive a request from the client corresponding to the target associated account to bind the first multimedia list, and send a notification to the client corresponding to the target account that created the first multimedia list that the target associated account has applied to jointly edit the first multimedia list; the request to bind the first multimedia list is sent by the client corresponding to the target associated account in response to the operation of the target associated account applying to jointly edit the first multimedia list;
[0285] The second binding relationship generation unit 2605 is used to receive information from the client corresponding to the target account that accepts the application of the target associated account to jointly edit the first multimedia list, and to generate a binding relationship between the first multimedia list and the target associated account.
[0286] and Figure 19 The method for generating the multimedia list shown is based on the same inventive concept, and embodiments of this application also provide an electronic device. For example... Figure 27 As shown, for ease of explanation, only the parts related to the embodiments of this application are shown. For specific technical details not disclosed, please refer to the method embodiments section of this application. The electronic device can be any electronic device such as a mobile phone, tablet computer, POS (Point of Sales), in-vehicle computer, smart wearable device, or PC. Figure 1 The terminal device 301 shown is shown.
[0287] Figure 27 A structural block diagram of an electronic device provided in an embodiment of this application is shown. Figure 27 As shown, the electronic device includes: a radio frequency (RF) circuit 310, a memory 320, an input unit 330, a display unit 340, a sensor 350, an audio circuit 360, a wireless fidelity (WiFi) module 370, a processor 380, and other components. Those skilled in the art will understand that... Figure 27The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0288] The following is combined Figure 27 A detailed introduction to each component of the electronic device:
[0289] The RF circuit 310 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 380; in addition, it transmits uplink data to the base station.
[0290] The memory 320 can be used to store software programs and modules, such as the program instructions / modules corresponding to the multimedia list generation method and apparatus in the embodiments of this application. The processor 380 executes various functional applications and data processing of the electronic device by running the software programs and modules stored in the memory 320, such as the multimedia list generation method provided in the embodiments of this application. The memory 320 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs of at least one application, etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 320 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.
[0291] The input unit 330 can be used to receive numeric or character information input by the user, and to generate key signal inputs related to user settings and function control of the terminal.
[0292] Optionally, the input unit 330 may include a touch panel 331 and other input devices 332.
[0293] The touch panel 331, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 331), and perform corresponding operations according to a pre-set program, such as the user clicking on a shortcut icon of a function module. Optionally, the touch panel 331 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 380, and can also receive and execute commands from the processor 380. Furthermore, the touch panel 331 can be implemented using various types of touch technologies, such as resistive, capacitive, infrared, and surface acoustic wave.
[0294] Optionally, other input devices 332 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.
[0295] Display unit 340 can be used to display information input by the user or interface information displayed to the user, as well as various menus of the electronic device. Display unit 340 is the display system of the terminal device, used to present the interface.
[0296] The display unit 340 may include a display panel 341. Optionally, the display panel 341 may be configured as a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
[0297] Furthermore, the touch panel 331 can cover the display panel 341. When the touch panel 331 detects a touch operation on or near it, it transmits the information to the processor 380 to determine the type of touch event. Subsequently, the processor 380 provides a corresponding interface output on the display panel 341 according to the type of touch event.
[0298] Although Figure 27 In this embodiment, the touch panel 331 and the display panel 341 are two separate components to realize the input and output functions of the electronic device. However, in some embodiments, the touch panel 331 and the display panel 341 can be integrated to realize the input and output functions of the terminal.
[0299] The electronic device may also include at least one sensor 350, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 341 according to the ambient light level, and the proximity sensor can turn off the backlight of the display panel 341 when the electronic device is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that identify the posture of the electronic device (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometers, taps), etc. Other sensors that may be configured in the electronic device, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.
[0300] Audio circuit 360, speaker 361, and microphone 362 provide an audio interface between the user and the electronic device. Audio circuit 360 converts received audio data into electrical signals and transmits them to speaker 361, where speaker 361 converts them into sound signals for output. On the other hand, microphone 362 converts collected sound signals into electrical signals, which are received by audio circuit 360, converted into audio data, and then output to processor 380 for processing. The audio data is then transmitted via RF circuit 310 to, for example, another electronic device, or output to memory 320 for further processing.
[0301] WiFi is a short-range wireless transmission technology. Electronic devices using a WiFi module 370 can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 27 WiFi module 370 is shown, but it is understood that it is not a necessary component of an electronic device and can be omitted as needed without changing the nature of the invention.
[0302] The processor 380 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 320, and by calling data stored in the memory 320, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Optionally, the processor 380 may include one or more processing units; optionally, the processor 380 may integrate an application processor and a modem processor. The application processor mainly processes software programs such as the operating system, applications, and functional modules within the applications, such as the multimedia list generation method provided in this embodiment. The modem processor mainly processes wireless communication. It is understood that the modem processor may not be integrated into the processor 380.
[0303] Understandable. Figure 27 The structure shown is for illustrative purposes only; the electronic device may also include components that are more advanced than those shown. Figure 27 The more or fewer components shown, or having the same Figure 27 The different configurations shown. Figure 27 The components shown can be implemented using hardware, software, or a combination thereof.
[0304] and Figure 21 The method for generating the multimedia list shown is based on the same inventive concept. This application also provides an electronic device. This electronic device can be a server, such as... Figure 1 The server 100 is shown. In this embodiment, the structure of the electronic device can be as follows: Figure 28As shown, it includes a memory 131, a communication module 133, and one or more processors 132.
[0305] The memory 131 is used to store computer programs executed by the processor 132. The memory 131 may mainly include a program storage area and a data storage area. The program storage area may store the operating system and programs required to run instant messaging functions, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.
[0306] Processor 132 may include one or more central processing units (CPUs) or digital processing units, etc. Processor 132 is used to implement the above-described method for generating the multimedia list when it calls the computer program stored in memory 131.
[0307] The communication module 133 is used to communicate with the terminal device and obtain game data.
[0308] This application does not limit the specific connection medium between the memory 131, the communication module 133, and the processor 132 described above. This disclosure embodiment... Figure 28 The memory 131 and the processor 132 are connected via a bus 134, and the bus 134 is in Figure 28 The connections between other components are shown in thick lines only and are not intended to be limiting. The bus 134 can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 28 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0309] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the multimedia list generation method described in the above embodiments.
[0310] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.
[0311] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.
Claims
1. A method for generating a multimedia playlist, characterized in that, include: In response to an operation by which a target account invites a target associated account on a target social application to jointly edit a first multimedia list bound to a multimedia application, the shared information of the first multimedia list is presented to the target associated account. The shared information is generated based on the identification information of the target account and the identification information of the first multimedia list; After the target associated account accepts the invitation to jointly edit the first multimedia list, it receives a notification from the backend server that the target associated account and the first multimedia list have been successfully bound. After the client corresponding to the target associated account edits the first multimedia list based on the instruction of the target associated account and sends an update request for the first multimedia list to the backend server, it receives the first multimedia list updated by the target associated account according to the shared information sent by the backend server and displays the updated first multimedia list. The method further includes: after the associated client searches the first multimedia list based on an operation instruction from a target associated user, and receives an operation from the target associated user requesting to co-edit the first multimedia list, receiving a notification from the backend server after determining that the number of accounts currently bound to the first multimedia list is less than a set number, indicating that the target associated user has requested to co-edit the first multimedia list; and after receiving an operation from the target account accepting the target associated user's request to co-edit the first multimedia list, sending a message to the backend server indicating that the target account has accepted the request, so that the backend server generates a binding relationship between the first multimedia list and the target associated account of the target associated user, and sends a notification to the associated client that the first multimedia list and the target associated account have been successfully bound.
2. The method according to claim 1, characterized in that, In response to the target account's invitation to a target associated account to jointly edit a first multimedia list, the shared information of the first multimedia list is presented to the target associated account, including: In response to a target account's instruction to share a first multimedia list, a selection of social applications is displayed. In response to the target account selecting a target social application, a list of associated accounts of the target account in the selected target social application is displayed; In response to the target account's operation of selecting a target associated account from the list of associated accounts, the shared information of the first multimedia list is sent to the target associated account through the target social application; the target account's operation of selecting a target associated account from the list of associated accounts is an operation in which the target account invites the target associated account to jointly edit the first multimedia list.
3. The method according to claim 1, characterized in that, The step of responding to the target account's invitation to a target associated account to jointly edit the first multimedia list, and presenting the shared information of the first multimedia list to the target associated account, includes: In response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the shared information of the first multimedia list is displayed to the target associated account in the form of a QR code or NFC.
4. The method according to claim 1, characterized in that, Before presenting the shared information of the first multimedia list to the target associated account in response to the target account's invitation to the target associated account to jointly edit the first multimedia list, the method further includes: In response to an operation that creates a new multimedia list for a target account or an operation that modifies the multimedia list type for an existing first multimedia list, a selection of multimedia list types is displayed; the multimedia list types include those edited by multiple users. In response to the target account confirming the selection of the multi-user collaborative editing type, the type of the first multimedia list is displayed as the multi-user collaborative editing type.
5. A method for generating a multimedia playlist, characterized in that, include: After the target account invites a target associated account on the target social application to jointly edit the first multimedia list bound to the multimedia application, in response to the operation of the target associated account jointly editing the first multimedia list, the first multimedia list obtained according to the shared information of the first multimedia list is displayed; the shared information includes the identification information of the target account and the identification information of the first multimedia list; The target account is the account that created the first multimedia list; Receive a notification from the backend server that the target associated account and the first multimedia list have been successfully bound; Based on the instructions of the target associated account, the first multimedia list is edited, and an update request for the first multimedia list is sent to the backend server. The updated first multimedia list is sent to the target account through the backend server, and the updated first multimedia list sent by the backend server is displayed. The method further includes: searching for a multimedia list based on the operation instructions of the target associated account, and after receiving the operation of the target associated account requesting to jointly edit the multimedia list, sending a request to the backend server to bind the multimedia list; After the backend server determines that the number of accounts currently bound to the multimedia list is less than a set number, and after the target account that created the multimedia list accepts the request from the target associated account to jointly edit the multimedia list, it receives a notification from the backend server that the multimedia list has been successfully bound to the target associated account.
6. The method according to claim 5, characterized in that, In response to the operation of jointly editing the first multimedia list by the target associated accounts, the first multimedia list obtained based on the shared information of the first multimedia list is displayed, including: Upon receiving an invitation message to jointly edit a first multimedia list, the system displays information about the target account and the first multimedia list; the invitation message includes shared information about the first multimedia list; the information about the target account and the first multimedia list are obtained based on the shared information of the first multimedia list. In response to the target associated account accepting the invitation to jointly edit the first multimedia list, the first multimedia list is displayed; the operation of accepting the invitation to jointly edit the first multimedia list is the operation of the target associated account jointly editing the first multimedia list.
7. The method according to claim 5, characterized in that, In response to the operation of jointly editing the first multimedia list by the target associated accounts, the first multimedia list obtained based on the shared information of the first multimedia list is displayed, including: In response to the operation of searching the first multimedia list for the target associated account, the information of the first multimedia list is displayed; the information of the first multimedia list is obtained based on the identification information of the target account or the identification information of the first multimedia list. In response to an operation requesting joint editing of a first multimedia list, if the target account accepts the request to jointly edit the first multimedia list, the first multimedia list is displayed.
8. A method for generating a multimedia playlist, characterized in that, include: If a target account invites a target associated account on a target social application to jointly edit a first multimedia list in a multimedia application, and the target associated account accepts the joint editing of the first multimedia list, a notification that the target associated account and the first multimedia list are successfully bound is sent to the client corresponding to the target associated account and the client corresponding to the target account. After the client corresponding to the target associated account edits the first multimedia list based on the instruction of the target associated account, it receives an update request for the first multimedia list sent by the client corresponding to the target associated account, and updates the first multimedia list according to the update request. The target associated account is bound to the first multimedia list; The updated content of the first multimedia list is sent to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list; The method further includes: after the associated client searches for a multimedia list based on the operation instruction of a target associated user, and receives the operation of the target associated user requesting to jointly edit the multimedia list, receiving a request from the associated client to bind the multimedia list; After determining that the number of accounts currently bound to the multimedia list is less than a set number, a notification is sent to the target client where the target account that created the multimedia list is located, indicating that the target associated user has applied to co-edit the multimedia list. The target account that created the multimedia list accepts the application, a binding relationship is generated between the multimedia list and the target associated account of the target associated user, and a notification is sent to the associated client that the multimedia list and the target associated account have been successfully bound.
9. The method according to claim 8, characterized in that, Before receiving an update request for the first multimedia list sent by the client corresponding to the target associated account, and updating the first multimedia list according to the update request, the method further includes: Upon receiving a request from the client corresponding to the target associated account to bind to the first multimedia list, if the number of accounts currently bound to the first multimedia list is less than a set number, a binding relationship is generated between the first multimedia list and the target associated account; the request to bind to the first multimedia list is sent by the client corresponding to the target associated account in response to the target associated account accepting an invitation to co-edit the first multimedia list or the target associated account applying to co-edit the first multimedia list.
10. The method according to claim 8, characterized in that, Before receiving an update request for the first multimedia list from a client of the target associated account, and updating the first multimedia list according to the update request, the method further includes: Upon receiving a multimedia list creation request sent by the client corresponding to the target account, the system generates identification information for the first multimedia list; the multimedia list creation request indicates the creation of a first multimedia list of a type that can be edited by multiple users. The identification information of the first multimedia list is sent to the client corresponding to the target account, and a binding relationship between the first multimedia list and the target account is generated based on the identification information of the first multimedia list and the identification information of the target account.
11. A multimedia playlist generation device, characterized in that, include: The information presentation unit is used to respond to an operation in which a target account invites a target associated account on a target social application to jointly edit a first multimedia list bound to a multimedia application, and to present the shared information of the first multimedia list to the target associated account. The shared information is generated based on the identification information of the target account and the identification information of the first multimedia list; The first display update unit is configured to: receive a notification from the backend server that the target associated account and the first multimedia list have been successfully bound after the target associated account accepts the invitation to jointly edit the first multimedia list; and, after the client corresponding to the target associated account edits the first multimedia list based on the instructions of the target associated account and sends an update request for the first multimedia list to the backend server, receive the first multimedia list updated by the target associated account according to the shared information sent by the backend server, and display the updated first multimedia list. The device further includes: after the associated client searches the first multimedia list based on an operation instruction from a target associated user, and receives an operation from the target associated user requesting to co-edit the first multimedia list, receiving a notification from the backend server after determining that the number of accounts currently bound to the first multimedia list is less than a set number, indicating that the target associated user has requested to co-edit the first multimedia list; and after receiving an operation from the target account accepting the target associated user's request to co-edit the first multimedia list, sending a message to the backend server indicating that the target account has accepted the request, so that the backend server generates a binding relationship between the first multimedia list and the target associated account of the target associated user, and sends a notification to the associated client that the first multimedia list and the target associated account have been successfully bound.
12. A multimedia playlist generation device, characterized in that, include: The list display unit is used to display a first multimedia list obtained based on the shared information of the first multimedia list after the target account invites a target associated account on the target social application to jointly edit a first multimedia list bound to the multimedia application; the shared information includes the identification information of the target account and the identification information of the first multimedia list. The target account is the account that created the first multimedia list; The second display update unit is used to receive a notification from the backend server that the target associated account and the first multimedia list have been successfully bound. Furthermore, based on the instructions of the target associated account, the first multimedia list is edited, and an update request for the first multimedia list is sent to the backend server; The first list sending unit is used to send the updated first multimedia list to the target account through the backend server and display the updated first multimedia list sent by the backend server. Based on the operation instructions of the target associated account, after searching for a multimedia list and receiving the operation of the target associated account requesting to jointly edit the multimedia list, a request to bind the multimedia list is sent to the backend server. After the backend server determines that the number of accounts currently bound to the multimedia list is less than a set number, and after the target account that created the multimedia list accepts the request from the target associated account to jointly edit the multimedia list, it receives a notification from the backend server that the multimedia list has been successfully bound to the target associated account.
13. A multimedia playlist generation device, characterized in that, include: The list update unit is used to send a notification that the target associated account and the first multimedia list are successfully bound when the target account invites the target associated account to jointly edit the first multimedia list in the multimedia application, and the target associated accounts jointly edit the first multimedia list. And, after the client corresponding to the target associated account edits the first multimedia list based on the instruction of the target associated account, it receives an update request for the first multimedia list sent by the client corresponding to the target associated account, and updates the first multimedia list according to the update request; The target associated account is bound to the first multimedia list; The second list sending unit is used to send the updated content of the first multimedia list to the clients corresponding to each account that is bound to the first multimedia list, so that the clients corresponding to each account can display the updated first multimedia list according to the updated content of the first multimedia list. The device further includes: after the associated client searches for a multimedia list based on an operation instruction from a target associated user, and receives an operation from the target associated user requesting to jointly edit the multimedia list, receiving a request from the associated client to bind the multimedia list; After determining that the number of accounts currently bound to the multimedia list is less than a set number, a notification is sent to the target client where the target account that created the multimedia list is located, indicating that the target associated user has applied to co-edit the multimedia list. The target account that created the multimedia list accepts the application, a binding relationship is generated between the multimedia list and the target associated account of the target associated user, and a notification is sent to the associated client that the multimedia list and the target associated account have been successfully bound.
14. A computer-readable storage medium storing a computer program therein, characterized in that: When the computer program is executed by a processor, it implements the method of any one of claims 1-4, 5-7, or 8-10.
15. An electronic device, characterized in that, It includes a memory and a processor, wherein the memory stores a computer program that can run on the processor, and when the computer program is executed by the processor, it implements the method of any one of claims 1-4, 5-7, or 8-10.
Citation Information
Patent Citations
Multimedia playlist management method, multimedia playlist management device and multimedia playlist management system
CN105227355A
Creating a single playlist with multiple authors
CN106030574A
Network disk file collaboration and access control method, device and system
CN109684867A
Multimedia resource playing method and system, terminal equipment and server
CN110996145A
Data co-processing method, device and system
CN111553132A