Cross-platform music resource searching system and searching method thereof

Abstract

The invention discloses a cross-platform music resource search system, which comprises a front end and a background, and is characterized in that the front end comprises a design interface and a search interface module and is used for receiving input information of a user; the background comprises a concurrent scheduling module and a resource integration module, and the concurrent scheduling module interacts with the search interface module and is used for concurrently requesting specified music resources from each available music resource library according to input information of a user; and the resource integration module is connected with all available music resource libraries of the current user side, is used for analyzing search results returned by the music resource libraries, classifying indexes and aggregating similar data according to categories, and is also connected with the design interface to open and call to the design interface. The invention also discloses a cross-platform music resource search method, the search method is based on the search system, and the technical scheme provided by the invention can realize cross-platform music resource search, realize integration of multiple types of music resources and improve interaction efficiency.

Description

Technical Field

[0001] This invention relates to the field of multimedia information processing technology, and in particular to a cross-platform music resource search method. Background Technology

[0002] With the development of music streaming, different music platforms possess scattered music resources. The search function of a single platform can only retrieve resources within that platform. Currently, most media players have fixed interfaces, simply integrating multiple applications. Their startup screen displays all available music platforms. When a user wants to play a track using an existing media player, they must first select a music platform from the startup screen, then navigate through the interface settings of that platform to finally play the desired audio file. If the desired audio file is not found on the currently selected platform, the user must return to the startup screen and select another platform to try again. This process is cumbersome and inefficient. Summary of the Invention

[0003] The main objective of this invention is to provide a cross-platform music resource search system and method that enables cross-platform and cross-type music resource search. This search method solves the problems of scattered music resources and low search efficiency in the prior art, and significantly improves the user experience.

[0004] To achieve the above objectives, this invention proposes a cross-platform music resource search system. The system is applied to the user end and includes a front-end and a back-end. The front-end includes: Design the interface; And, a search interface module, which is displayed on the design interface, responds to the user's search operation and is used to receive the user's input information; The backend includes: The concurrent scheduling module interacts with the search interface module and is used to concurrently request the specified music resources from each available music resource library based on the user's input information. The resource integration module connects to all available music resource libraries on the current user's end. It is used to parse the search results returned by each music resource library, classify and index them, and aggregate similar data by category. The resource integration module is also connected to the design interface so that it can be accessed by the design interface.

[0005] Optionally, the front end also includes a search standardization module, which is connected to the search interface module. The search standardization module is used to parse the user input information received by the search interface module and convert it into a standardized search request.

[0006] Optionally, the resource integration module includes a result parsing unit, which accesses all available music resource libraries on the current user terminal, receives the search results returned by each music resource library, and maps them into parsing results with a unified data structure.

[0007] Optionally, the resource integration module further includes a data cleaning unit, which interacts with the result parsing unit. The data cleaning unit is used to compare the parsing results one by one, and process invalid data, default data, abnormal data and duplicate data to generate a cleaning result.

[0008] Optionally, the resource integration module further includes a classification indexing unit, which interacts with the data cleaning unit. The classification indexing unit is used to establish index labels and classify the cleaning results according to the index labels to generate classification results.

[0009] Optionally, the resource integration module further includes an aggregation and sorting unit, which interacts with the data cleaning unit. The aggregation unit is used to construct weighted rules and calculate a comprehensive weight for the cleaning results based on the weighted rules to sort them.

[0010] This invention also provides a cross-platform music resource search method, which is based on the cross-platform music resource search system described above, and includes: S1: The user operates the user terminal and inputs information through the search interface module; S2: The concurrent scheduling module sends concurrent search requests to all available music resource libraries; S3: The resource integration module receives the search results returned by each music resource library, parses and classifies the index, aggregates similar data by category, and generates integration results; S4: The design interface is invoked and the integration result is parsed and displayed to the user.

[0011] Optionally, S1 includes: S11: The search standardization module pre-constructs a search standard format using one or more of the following fields: keywords, music type, target music platform, pagination parameters, and timeout threshold; S12: The user clicks the search interface module and enters information; S13: The search interface module receives information input by the user; S14: The search standardization module converts the information entered by the user into a standardized search request according to the search standard format.

[0012] Optionally, S3 includes: S31: The result parsing unit receives the search results returned by each music resource library and maps them into parsing results with a unified data structure; S32: The data cleaning unit processes the parsing results one by one to generate cleaning results; S33: The classification index unit has index tags established in advance according to at least two categories among single, album, artist, style and release time; S34: The classification index unit parses the cleaning results one by one, and adds index tags to each cleaning result according to the category to generate classification results.

[0013] Optionally, S3 further includes: S34: The aggregation and sorting unit is pre-defined with weighting rules based on one or more of the following indicators: keyword similarity, playback volume or popularity provided by the platform, platform-defined priority, and user preference. S35: The aggregation sorting unit calculates the comprehensive weight of each of the cleaning results one by one according to the weighting rules; S36: The aggregation sorting unit sorts all the cleaning results by their comprehensive weight from high to low, and makes them available for sequential access to the design interface.

[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: Cross-platform music resource search: The cross-platform music resource search system provided by this invention solves the problem of scattered music resources in the prior art by setting up a concurrent scheduling module in the background. This concurrent scheduling module supports concurrent and asynchronous request mechanisms and concurrently requests the specified music resources from each available music resource library in the form of redundant requests.

[0015] This invention enables the integration of multiple types of music resources and improves interaction efficiency: The cross-platform music resource search system provided by this invention sets up a resource integration module, which classifies and indexes the data of the same type and aggregates them by category to integrate multiple types of music resources, making it convenient for users and improving interaction efficiency. Attached Figure Description

[0016] The present invention will now be described in detail with reference to specific embodiments and accompanying drawings, wherein: Figure 1 This is a flowchart of the cross-platform music resource search method provided in this specific embodiment. Detailed Implementation

[0017] The solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] In the following description, references to "some embodiments" describe a subset of all possible embodiments; however, it is understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict. In the following description, the term "a plurality of" means at least two.

[0019] Furthermore, the use of terms such as "first" and "second" in this invention is for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Additionally, the technical solutions of the various embodiments can be combined with each other, but only on the basis of being achievable by those skilled in the art. When the combination of technical solutions is contradictory or impossible to implement, such a combination of technical solutions should be considered non-existent and not within the scope of protection claimed by this invention.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] Please see Figure 1 This specific embodiment provides a cross-platform music resource search system. The system is applied to a user terminal, which is specifically a mobile phone user terminal, an in-vehicle user terminal, other mobile device user terminals, or a computer user terminal, etc. The system includes a front-end and a back-end, and the front-end and the back-end interact.

[0022] The front end includes a design interface, a search interface module, and a search standardization module. The search interface module is displayed in the design interface and is open to users. Users can use the search interface module to perform search operations by touching the touch screen, clicking with a mouse, or clicking with a dedicated pen on the device. The search interface module responds to the user's search operation and is used to receive the user's input information. Users can enter the song name, artist name, album name, and related keywords of the song through the search interface. The search standardization module corresponds to the search interface module settings. It connects to the search interface module and parses the user input received by the search interface module, transforming it into a standardized search request. The search standardization module eliminates discrepancies between user input and system settings, facilitating system understanding of the user's input. It accurately extracts information such as song title, artist name, album name, and related keywords from the user's input. The formatted search request obtained after processing by the search standardization module also facilitates subsequent data processing by the system.

[0023] It is worth mentioning that the search standardization module set up here can be used as a basic module in specific applications and reused in any situation in the system that requires data format conversion. The introduction of the search standardization module further expands the applicability of the system, making it compatible with more types of music resource libraries and allowing users to make search requests in more diverse input forms.

[0024] In the cross-platform music resource search system provided in this specific embodiment, the backend includes a concurrent scheduling module and a resource integration module; The concurrent scheduling module interacts with the search standardization module. The concurrent scheduling module is used to concurrently request the specified music resources from each available music resource library based on the user's input information. Once the search interface module receives the user's input information, the user's input information can be further transformed into a standardized search request by the search standardization module. The concurrent scheduling module then interacts with the search standardization module. The standardized search request transmitted by the search standardization module can clearly understand the user's search intent. The concurrent scheduling module simultaneously sends requests to all available music resource libraries on the current user's end, making a wide range of search requests in the form of redundant requests.

[0025] The resource integration module connects to all available music resource libraries on the current user's end. It parses the search results returned by each music resource library, categorizes and indexes them, and aggregates similar data by category. The resource integration module also connects to the design interface for easy access. As mentioned earlier, the concurrent scheduling module simultaneously sends requests to all available music resource libraries on the current user's end. In practical scenarios, this setup often results in multiple music resource libraries responding to the user's input, returning multiple search results. These search results vary in structure due to factors such as library architecture and internal matching mechanisms. The system's resource integration module not only handles the search results returned by each music resource library but also parses and re-categorizes all search results, providing users with more complete, comprehensive, rich, and rigorous search results.

[0026] In this specific implementation, the resource integration module includes a result parsing unit, a data cleaning unit, a classification indexing unit, and an aggregation and sorting unit. The result parsing unit accesses all available music resource libraries on the current user's end, receives search results returned by each music resource library, and maps them into parsed results with a unified data structure. The data cleaning unit interacts with the result parsing unit, comparing the parsing results one by one and processing invalid data, default data, abnormal data, and duplicate data to generate cleaned results. The classification indexing unit interacts with the data cleaning unit, creating index labels and classifying the cleaned results according to the index labels to generate classification results. The aggregation and sorting unit interacts with the data cleaning unit, constructing weighted rules and calculating a comprehensive weight for the cleaned results based on these rules to sort them.

[0027] Based on the cross-platform music resource search system described above, this specific embodiment also provides a cross-platform music resource search method, which includes: S1: The user operates the user terminal and inputs information through the search interface module; Specifically, S1 includes the following sub-steps: S11: The search standardization module pre-constructs a search standard format using one or more of the following fields: keywords, music genre, target music platform, pagination parameters, and timeout threshold. S12: The user clicks the search interface module and enters the information "singer's name"; the search interface module allows the user to select the search type, such as single, album, artist, playlist, radio, podcast, etc.; while entering the information "singer's name", the user selects the search type as a combination of "single" and "album"; S13: The search interface module receives information input by the user; the search interface module supports extended functions such as fuzzy matching, pinyin search, and multilingual keywords, and allows users to limit the type of music resource library; S14: The search standardization module transforms the user-input information into a standardized search request according to the search standard format. In this specific implementation, a JSON request is used as an example to illustrate the specific method by which the search standardization module transforms the user-input information into a standardized search request: { "keyword": "singer's name", "types": ["song", "album"], "platforms": ["local", "netease", "sonyselect"], "pagination": {"page": 1, "size": 20}, "timeout": 5000 } S2: The concurrent scheduling module sends concurrent search requests to all available music resource libraries; If the current user client is connected to NetEase Cloud, the concurrent scheduling module sends a search request through NetEase Cloud's API interface. The cross-platform retrieval method provided in this specific embodiment sends a search request to NetEase Cloud's API interface through the following path: / openapi / music / basic / search / song / get / v2?keyword=singer_name&limit=30&offset=0 If the current user terminal accesses Sony Select, the concurrent scheduling module sends a search request through the Sony Select API interface. The cross-platform retrieval method provided in this specific embodiment sends a search request to the Sony Select API interface through the following path: / search / content / v1?keyword=singer name&type=1&pageNo=0&pageSize=30; If the current user terminal accesses a local database such as a USB flash drive, CD, or Bluetooth device, the concurrent scheduling module sends a search request through the local database interface. The cross-platform retrieval method provided in this specific embodiment sends a search request to the local database interface through the following path: SELECT * FROM songs WHERE artist LIKE '%singer's name%'; In practical use, the concurrent scheduling module supports a timeout discard mechanism. That is, the concurrent scheduling module pre-defines the search time, and for music resource libraries that do not return search results within the specified search time, the concurrent scheduling module will no longer wait for its search results.

[0028] S3: The resource integration module receives search results returned by various music resource libraries, parses and categorizes the index, aggregates similar data by category, and generates integration results; The specific S3 includes the following sub-steps: S31: The result parsing unit receives the search results returned by each music resource library and maps them into parsing results with a unified data structure; For example, for the search results returned by NetEase Cloud Music, the result parsing unit maps the fields {name, ar, al} returned by NetEase Cloud Music to data in the form of {title, artist, album} as the parsing result; For example, for the search results returned by Sony Select, the result parsing unit converts the results returned by Sony Select in the form of {discTitle, singer} into a unified structure as the parsing result; For example, for search results returned by the local database for USB flash drives, optical discs, Bluetooth devices, etc., the result parsing unit aligns and extracts ID3 tags, and fills in missing fields to form the parsing results; S32: The data cleaning unit processes the parsing results one by one, cleans up invalid data, default data, abnormal data and duplicate data, compares the parsing results from different sources, and if the similarity of the song title exceeds 0.9, the artists are the same, and the duration difference is less than 3 seconds, it is determined to be the same song and corresponding processing is performed to generate the cleaning result. Example implementation code: / / Example of song parsing result structure class SongParseResult { String songName; String artistName; long duration; / / Unit: seconds } / / Determine if they are the same song public boolean isSameSong(SongParseResult a, SongParseResult b) { / / 1. Song title similarity calculation (e.g., edit distance / vector similarity) double nameSimilarity = calcTextSimilarity(a.songName,b.songName); / / 2. Are the artists the same? boolean sameArtist = a.artistName != null &&a.artistName.equalsIgnoreCase(b.artistName); / / 3. Duration Difference Judgment long durationDiff = Math.abs(a.duration - b.duration); / / 4. Comprehensive Judgment Rules if (nameSimilarity>0.9&&sameArtist &&durationDiff<3) { return true; / / Determined to be the same song } return false;} S33: The category index unit pre-establishes index tags according to two categories: singles and albums; S34: The category index unit parses the cleaning results one by one, and adds index tags to each cleaning result according to the category to generate the category results; if the user searches again, the cached index can be directly called by querying the index tags to speed up the response and improve search efficiency. Example implementation code: / / Generate classification results based on index labels public Map<String, CategoryResult> generateCategoryResult( List <songparseresult>cleanResults) { Map<String, CategoryResult>categoryMap = new HashMap<>(); for (SongParseResult song : cleanResults) { List <indextag>tags = buildIndexTags(song); for (IndexTag tag : tags) { CategoryResult result = categoryMap.get(tag.tagValue); if (result == null) { result = new CategoryResult(); result.category = tag.tagValue; result.songList = new ArrayList<>(); categoryMap.put(tag.tagValue, result); } result.songList.add(song); } } return categoryMap; } / / Query index cache public CategoryResult searchByIndex(String keyword) { / / Retrieve directly from cache index return indexCache.get(keyword); } S34: The aggregation and sorting unit is pre-defined by a weighting rule based on one or more of the following indicators: keyword similarity, play count or popularity provided by the platform, platform-defined priority, and user preference. Among these, keyword similarity is determined by the similarity between search results and user input information, play count or popularity provided by the platform is updated periodically by each music resource library, and user preference is determined based on the statistical data of historical usage records in the user operation log. S35: The aggregation sorting unit calculates the comprehensive weight of each cleaning result according to the weighting rules; In practice, the comprehensive weight score is calculated as follows: Score = α × keyword similarity + β × platform-provided play count or popularity index + γ × platform-defined priority + δ × user preference.

[0029] S36: The aggregation sorting unit sorts all cleaning results by comprehensive weight, arranges them from high to low, and makes them available for sequential access to the design interface.

[0030] S4: The design interface calls the aggregation sorting unit and parses and displays the integrated results to the user.

[0031] The above description is merely a preferred embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent structural transformations made using the contents of the present invention's specification and drawings under the inventive concept of the present invention, or direct / indirect applications in other related technical fields, are included within the patent protection scope of the present invention.< / indextag> < / songparseresult>

Claims

1. A cross-platform music resource search system, the system being applied to a user terminal, comprising a front-end and a back-end, the front-end comprising: Design the interface; And, a search interface module, which is displayed on the design interface, responds to the user's search operation and is used to receive the user's input information; The background system is characterized by comprising: The concurrent scheduling module interacts with the search interface module and is used to concurrently request the specified music resources from each available music resource library based on the user's input information. The resource integration module connects to all available music resource libraries on the current user's end. It is used to parse the search results returned by each music resource library, classify and index them, and aggregate similar data by category. The resource integration module is also connected to the design interface so that it can be accessed by the design interface.

2. The cross-platform music resource search system as described in claim 1, characterized in that, The front end also includes a search standardization module, which is connected to the search interface module. The search standardization module is used to parse the user input information received by the search interface module and convert it into a standardized search request.

3. The cross-platform music resource search system as described in claim 1, characterized in that, The resource integration module includes a result parsing unit, which accesses all available music resource libraries on the current user terminal, receives the search results returned by each music resource library, and maps them into parsing results with a unified data structure.

4. The cross-platform music resource search system as described in claim 3, characterized in that, The resource integration module also includes a data cleaning unit, which interacts with the result parsing unit. The data cleaning unit is used to compare the parsing results one by one, and process invalid data, default data, abnormal data and duplicate data to generate a cleaning result.

5. The cross-platform music resource search system as described in claim 4, characterized in that, The resource integration module also includes a classification indexing unit, which interacts with the data cleaning unit. The classification indexing unit is used to establish index labels and classify the cleaning results according to the index labels to generate classification results.

6. The cross-platform music resource search system as described in claim 4, characterized in that, The resource integration module also includes an aggregation and sorting unit, which interacts with the data cleaning unit. The aggregation unit is used to construct weighted rules and calculate a comprehensive weight for the cleaning results based on the weighted rules to sort them.

7. A cross-platform music resource search method, said method being based on the cross-platform music resource search system as described in any one of claims 1-6, characterized in that, include: S1: The user operates the user terminal and inputs information through the search interface module; S2: The concurrent scheduling module sends concurrent search requests to all available music resource libraries; S3: The resource integration module receives the search results returned by each music resource library, parses and classifies the index, aggregates similar data by category, and generates integration results; S4: The design interface is invoked and the integrated result is parsed and displayed to the user.

8. The cross-platform music resource search method as described in claim 7, characterized in that, S1 includes: S11: The search standardization module pre-constructs a search standard format using one or more of the following fields: keywords, music type, target music platform, pagination parameters, and timeout threshold; S12: The user clicks the search interface module and enters information; S13: The search interface module receives information input by the user; S14: The search standardization module converts the information entered by the user into a standardized search request according to the search standard format.

9. The cross-platform music resource search method as described in claim 7, characterized in that, S3 includes: S31: The result parsing unit receives the search results returned by each music resource library and maps them into parsing results with a unified data structure; S32: The data cleaning unit processes the parsing results one by one to generate cleaning results; S33: The classification index unit has index tags established in advance according to at least two categories among single, album, artist, style and release time; S34: The classification index unit parses the cleaning results one by one, and adds index tags to each cleaning result according to the category to generate classification results.

10. The cross-platform music resource search method as described in claim 9, characterized in that, S3 further includes: S35: The aggregation and sorting unit is pre-defined with weighting rules based on one or more of the following indicators: keyword similarity, playback volume or popularity provided by the platform, platform-defined priority, and user preference. S36: The aggregation sorting unit calculates the comprehensive weight of each of the cleaning results one by one according to the weighting rules; S37: The aggregation sorting unit sorts all the cleaning results by their comprehensive weight from high to low, and makes them available for sequential access to the design interface.

Images