WO2025242002A1 - 媒体播放方法、物联网系统、设备、介质及产品 - Google Patents

媒体播放方法、物联网系统、设备、介质及产品

Info

Publication number
WO2025242002A1
WO2025242002A1 PCT/CN2025/095457 CN2025095457W WO2025242002A1 WO 2025242002 A1 WO2025242002 A1 WO 2025242002A1 CN 2025095457 W CN2025095457 W CN 2025095457W WO 2025242002 A1 WO2025242002 A1 WO 2025242002A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
player
acquisition device
components
media
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/095457
Other languages
English (en)
French (fr)
Inventor
斯维
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2025242002A1 publication Critical patent/WO2025242002A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25808—Management of client data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/27—Server based end-user applications
    • H04N21/274—Storing end-user multimedia data in response to end-user request, e.g. network recorder
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals

Definitions

  • This application relates to the field of communication technology, and in particular to a media playback method, Internet of Things system, device, medium and product.
  • the media player is an important component of the converged device center and one of the mediums through which users directly communicate with the terminal. It can display various types of media data collected by terminal devices such as cameras, smart door locks, and smart robots on the user interface.
  • This application provides a media playback method, an Internet of Things system, a device, a medium, and a product.
  • embodiments of this application provide a media playback method, the method comprising: acquiring an access message of a media content acquisition device; sending a capability request according to the access message; receiving capability component information generated according to the capability request; matching and installing a capability component corresponding to the acquisition device according to the capability component information, wherein the capability component is configured to enable a player to play media content from the acquisition device.
  • embodiments of this application provide an electronic device, which includes at least a player and a player capability management system; the player capability management system is capable of matching the capabilities of a media content acquisition device and installing capability components corresponding to the acquisition device, so that the player can be used to play the media content.
  • embodiments of this application provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the media playback method as described in the first aspect.
  • embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the media playback method described in the first aspect.
  • embodiments of this application provide a computer program product, including a computer program or computer instructions, the computer program or computer instructions being stored in a computer-readable storage medium, a processor of a computer device reading the computer program or computer instructions from the computer-readable storage medium, and the processor executing the computer program or computer instructions to cause the computer device to perform the media playback method as described in the first aspect.
  • Figure 1 is a system architecture diagram of the media playback method provided in an embodiment of this application.
  • FIG. 2 is a system architecture diagram of the media playback method provided in another embodiment of this application.
  • Figure 3 is a platform system architecture diagram based on the Internet of Things provided in an embodiment of this application;
  • Figure 4 is a flowchart of a media playback method provided in an embodiment of this application.
  • Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
  • Figure 7 is a schematic diagram of a media playback interaction scenario based on the Internet of Things provided in an example of this application.
  • Figure 8 is a structural block diagram of a portion of the terminal implementing the media playback method of the embodiments of this application.
  • Figure 9 is a structural block diagram of a portion of the server implementing the media playback method of this application.
  • media players are a crucial component of converged device centers and one of the mediums for direct communication between users and terminals. They display various types of media data collected by media acquisition devices on the user interface.
  • media acquisition devices such as cameras, smart door locks, and smart robots all have audio and video acquisition and transmission capabilities, enabling them to display the collected audio and video data to users via a relay cloud platform.
  • the audio and video capabilities of different devices vary due to differences in hardware such as memory, CPU, and sensors, resulting in differences in encoding/decoding and transmission protocols. These differences necessitate the integration of various media players and playback mechanisms when adapting to different devices, leading to problems such as software bloat, poor compatibility, and high development difficulty.
  • IJKPlayer a lightweight video player: this player is configured at compile time to support protocols (such as Real-Time Streaming Protocol (RTSP), Hypertext Transfer Protocol (HTTP), Secure Socket Layer (SSL), etc.) and encodings (H.264, H.265 (highly compressed digital video codec standards), etc.), and then packaged into a shared library, which is integrated into the application as the playback kernel.
  • RTSP Real-Time Streaming Protocol
  • HTTP Hypertext Transfer Protocol
  • SSL Secure Socket Layer
  • H.264, H.265 highly compressed digital video codec standards
  • a camera device needs to support the RTSP protocol and H.264 encoding
  • a robot device needs to support the HTTP protocol and H.265 encoding.
  • both protocols and encodings need to be compiled into the player's shared library.
  • the user only uses the camera device, this will lead to functional redundancy in the software package.
  • VLC player provides a plugin system, but this system cannot integrate with external systems.
  • This plugin system provides a series of pre-installed plugins for use during the player's initial startup, but it cannot enable or disable corresponding plugins based on different device capabilities. Therefore, redundant startup plugins slow down application startup and consume application space. This leads to poor player compatibility, functional redundancy, and unnecessary space resource consumption. Therefore, how to reduce unnecessary space redundancy is a technical problem that urgently needs to be solved.
  • This application provides a media playback method, an IoT system, a device, a medium, and a product.
  • a capability management system By constructing a capability management system, user terminals can sense the access of media content acquisition devices and request capabilities from these devices to obtain capability component information. Based on this information, capability components are matched to determine which capability components the user terminal's player needs to play media content from the corresponding acquisition device, and then the relevant capability components are loaded.
  • This approach matches the capability components required by different acquisition devices and loads the corresponding components, avoiding unnecessary pre-installation of capability components, solving the problem of space redundancy, and optimizing the player's startup and loading speed.
  • loading all pre-set plugins during the initial startup phase of the player can cause slow startup speeds and redundancy due to loading too many unnecessary plugins.
  • This application's dynamic matching method matches and loads the corresponding capability components according to the sensed acquisition device, avoiding the installation of too many unnecessary redundant plugins. Furthermore, when switching between playback on different acquisition devices, the required capabilities are loaded based on dynamic matching, improving the response and loading speed when playing media data.
  • the player's encoding/decoding capabilities and supported transmission methods can be expanded through capability components, thereby ensuring compatibility with more types of acquisition devices and guaranteeing flexibility in expansion.
  • This application provides a media playback method, an Internet of Things system, a device, a medium, and a product, which aims to improve the adaptability to acquisition devices while reducing unnecessary space redundancy.
  • Figure 1 is a system architecture diagram of a media playback method provided in an embodiment of this application.
  • the system includes, but is not limited to, a server 110, a media acquisition device 120, and a user terminal 130.
  • Server 110 refers to a computer system that provides capability management services, media playback services, and interaction services with media acquisition device 120 to user terminal 130.
  • server 110 is equipped with a capability management system, which can identify and match capability components between user terminal 130 and media acquisition device 120, and assist user terminal 130 in installing capability components.
  • server 110 has higher requirements in terms of stability, security, and performance.
  • Server 110 can be a single high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a single high-performance computer (e.g., a virtual machine), or a combination of portions of multiple high-performance computers (e.g., virtual machines).
  • Server 110 can also communicate with media acquisition device 120 and/or user terminal 130 via wired or wireless means to exchange data.
  • Media acquisition device 120 refers to a device that collects media information such as audio and video data and can provide this media information to user terminal 130. It includes, but is not limited to, cameras, smart locks, smart robots, smart TVs, and other devices or apparatuses with audio and video acquisition capabilities. Media acquisition device 120 can also communicate with server 110 via wired or wireless means to exchange data.
  • User terminal 130 is a device that plays media information acquired by media acquisition device 120 to a user.
  • User terminal 130 is equipped with a player 131, which plays audio or video according to the media information.
  • User terminal 130 can take various forms, including desktop computers, laptops, PDAs (personal digital assistants), mobile phones, in-vehicle terminals, home theater terminals, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple devices can be connected via a local area network, sharing a single display device to work collaboratively, forming a single terminal.
  • User terminal 130 can also communicate with server 110 via wired or wireless means to exchange data.
  • Network 210 can be the Internet, the Internet of Things, a home area network, etc., without specific limitations.
  • User terminal 230 is a device that plays media information captured by media acquisition device 220 to a user.
  • User terminal 230 is equipped with player 231, which plays audio or video based on the media information.
  • User terminal 230 also has a capability management system 232; through the capability management system 232, user terminal 230 can obtain corresponding capability component information from media acquisition device 220 and perform capability matching. Based on the capability matching results, it acquires and installs capability components so that player 231 can be compatible with various media acquisition devices 220.
  • User terminal 230 includes various forms such as desktop computers, laptops, PDAs (personal digital assistants), mobile phones, in-vehicle terminals, home theater terminals, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple devices can be connected via a local area network, sharing a single display device to work collaboratively, forming a single terminal.
  • User terminal 230 can also communicate with network 210 via wired or wireless means to exchange data and interact with media acquisition device 210.
  • the embodiments of this application can be applied to various scenarios such as smart homes, multimedia convergence and interaction, smart campuses, and industrial production management.
  • Figure 3 is a platform system architecture diagram based on the Internet of Things provided in an embodiment of this application.
  • the scenario shown in Figure 3 includes:
  • Media acquisition devices refer to Internet of Things (IoT) devices with basic capabilities such as multimedia data acquisition, encoding/decoding, transmission, and playback. These devices store the acquired audio and video data locally using a specific encoding format or transmit it to a cloud platform, and can establish a device server through communication protocols. Media acquisition devices also store information about their own basic device capabilities.
  • IoT Internet of Things
  • the cloud platform and relay server act as the database and proxy.
  • the cloud platform's database stores the audio and video files from the media acquisition devices, enabling players to access and play these files through specific ports and IP addresses.
  • the cloud platform's capability component center is one method for deploying player plugins; it serves as a cloud-based database for uploading and downloading various capability components.
  • the relay server is used for data parsing, conversion, and transmission between media acquisition devices, user terminals, and the capability management system.
  • the user terminal receiving terminal device is the carrier of the player and the player capability management system. Users can see the access of the media acquisition device through the graphical system carried by the user terminal, and can view the audio and video data acquired by the media acquisition device through the device management process.
  • the capability management system is middleware that connects media acquisition devices and user terminals. Its main function is to retrieve the set of player capability components required by the media acquisition device when it is detected as connected, and then install the corresponding capability components into the player to provide device support.
  • a home security camera When a home security camera connects to the platform system, it reports the connection to the platform. Based on this connection message, the platform informs the user terminal of basic information such as the connected device identifier. Once the user terminal detects the home security camera's connection, it notifies the player's capability management system to match and load capability components.
  • the media player capability management system generates a capability request based on the identifier of the connected media acquisition device. The system then sends this request to the home security camera via a relay server. The home security camera, based on the request information carried in the request, returns the information of the various capability components it requires to the media player capability management system via the relay server.
  • the player capability management system matches the required capability components with the returned home security camera to determine the transmission protocols, codec protocols, function plugins, etc., supported by the camera. If the player capability management system finds a missing capability component locally, it requests the corresponding capability component from the cloud platform's capability component center. After matching and obtaining all the required capability components for the home security camera, the player capability management system installs all these components into the player, enabling the player to support the home security camera.
  • the player can obtain the audio and video data collected by the home camera through the cloud platform or directly and play it.
  • the player capability management system enables the user terminal to detect the access of media acquisition devices (such as home security cameras) and request the necessary capability component information from these devices. Based on this information, the system matches capability components to determine which components the user terminal's player needs to play media content from the corresponding acquisition device, and then loads the appropriate components.
  • This solution matches the required capability components for different acquisition devices and loads the corresponding components, avoiding unnecessary pre-installation of capabilities, resolving space redundancy issues, and optimizing the player's startup and loading speed.
  • the player matches and loads the corresponding capability components based on the detected acquisition device, avoiding the installation of too many unnecessary redundant plugins. Furthermore, it can retrieve missing capability components from the cloud platform, thus preventing excessive caching of capability components on the local capability management system and saving local space resources.
  • FIG 4 is a flowchart of a media playback method provided in an embodiment of this application.
  • This media playback method can be applied, but is not limited to, to a user terminal, user terminal 130 in the system provided in Figure 1, user terminal 230 in the system provided in Figure 2, or a user terminal in the platform system provided in Figure 3.
  • this media playback method includes, but is not limited to, the following:
  • Step 410 Obtain the access message from the media content acquisition device
  • Step 420 Send a capability request based on the access message
  • Step 430 Receive capability component information generated based on the capability request
  • Step 440 Match and install the capability components corresponding to the acquisition device according to the capability component information.
  • the capability components are configured to enable the player to play media content from the acquisition device.
  • media content refers to audio and video data streams.
  • Acquisition devices refer to devices that generate and transmit audio and video data streams, such as cameras, smart locks, and smart robots.
  • Access messages refer to messages obtained by the user terminal when the acquisition device establishes a communication connection with an IoT platform or user terminal, which indicate basic information about the acquisition device.
  • a capability request refers to a message used to request the required capability components of the accessed acquisition device.
  • the capability component information refers to information used to indicate which capability components the acquisition device needs.
  • the capability component information may be the identifier of each capability component.
  • matching based on capability component information means that the player capability management system obtains the capability components required by the acquisition device from a local or cloud server based on the capability component information.
  • Installing the capability components corresponding to the acquisition device means installing the capability components required by the acquisition device obtained in the matching phase into the player so that the player can support the corresponding acquisition device.
  • capabilities refers to the transmission protocols, encoding/decoding protocols, and various functional plugins supported by the media acquisition device, such as black-and-white filtering, screen flipping, night mode, and image filtering.
  • a capability component refers to a module or plugin that can implement the above capabilities; it can be a piece of encapsulated code, or a standalone software plugin or module.
  • Steps 410 to 440 above can be executed by a user terminal that has the player capability management system and the player installed, or they can be executed jointly by a user terminal that has the player installed and a player capability management system deployed separately through other terminals or servers.
  • the user terminal can sense the access of the media acquisition device and request the required capability component information from the acquisition device. Based on this capability component information, capability components are matched to determine which capability components the user terminal's player needs to play media content from the corresponding acquisition device, and the relevant capability components are loaded.
  • the required capability components for different acquisition devices are matched before loading the corresponding capability components, avoiding unnecessary pre-setting of capability components, solving the problem of space redundancy, and optimizing the player's startup loading speed.
  • the player matches and loads the corresponding capability components according to the sensed acquisition device, avoiding the installation of too many unnecessary redundant plugins.
  • steps 410 to 440 The above is a general description of steps 410 to 440.
  • the implementation process of steps 410 to 440 will be described in detail below.
  • step 410 the access message of the media content acquisition device is obtained.
  • the acquisition device reports an initialization event to the server.
  • This initialization event includes attributes such as device authentication type, access address, port, and device identifier.
  • the server Upon receiving the initialization event, the server sends an access message to the user terminal to notify it of the new acquisition device's access, and the server creates a device session in the database.
  • the server By using the server as a relay, messages exchanged between the user terminal and the acquisition device are translated, allowing both parties to seamlessly identify the information sent by the other.
  • a user terminal when a user terminal communicates directly with the acquisition device via the network, when a new acquisition device is accessed, the user terminal obtains the access message of the acquisition device by listening to it, thereby obtaining the basic device information of the acquisition device, such as the device identifier.
  • step 420 a capability request is sent based on the access message.
  • the user terminal generates a corresponding capability request based on the device identifier in the access message.
  • the capability request carries a message requesting the specified acquisition device to obtain its supported capability components. It should be noted that, in this application, the media acquisition device/capability components supported by the acquisition device are the same as the capability components required by the media acquisition device/acquisition device.
  • the user terminal In the presence of a relay server or a unified IoT platform (server), the user terminal sends a capability request to the server. After the server matches the capability request with the corresponding acquisition device, it converts the capability request into a capability acquisition instruction that the acquisition device can recognize and sends it to the corresponding acquisition device.
  • server matches the capability request with the corresponding acquisition device, it converts the capability request into a capability acquisition instruction that the acquisition device can recognize and sends it to the corresponding acquisition device.
  • step 430 capability component information generated based on the capability request is received.
  • step 430 when the player capability management system is located on the user terminal or electronic device side, step 430 includes:
  • the IoT platform sends a capability acquisition command based on the capability request
  • the IoT platform receives a capability model generated based on capability acquisition instructions
  • the IoT platform generates a response message based on the capability model, which includes capability component information.
  • the Internet of Things (IoT) platform refers to a unified platform for the Internet of Things, typically deployed on one or more servers.
  • the IoT platform serves as a message relay between data collection devices and user terminals.
  • step 430 includes:
  • the receiving and acquisition device generates a capability model based on the capability request
  • the player's capability management system is located on an IoT platform, there's no need to generate response messages for the user terminal based on the capability model. Instead, the IoT platform directly parses the capability model to obtain the corresponding capability component information, performs capability component matching, and acquires the capability components required by the acquisition device. The IoT platform then sends the matched capability components to the user terminal for the player to load.
  • step 440 includes:
  • matching the capability components required by the acquisition device refers to parsing the capability component information, determining the acquisition device capabilities (capability components) contained in the capability component information, and thus determining which capability components the acquisition device needs.
  • Finding capability components refers to searching for and retrieving the required capability components from the user terminal where the player is located, the IoT platform database, or the cloud-based capability component library.
  • Installing capability components refers to loading the retrieved capability components into the player, enabling the player to support the corresponding acquisition device and play the audio and video streams from that device.
  • locating and installing the capability components corresponding to the acquisition device includes at least one of the following:
  • the system searches the local component list to obtain the missing capability list. Based on the missing capability list, it sends a component request to obtain and install the capability components listed in the missing capability list.
  • the missing capability list includes the capability components required by the acquisition device that are missing from the local component list.
  • the local component list refers to the local capability component library on the user terminal where the player is located, or the local capability component library on the user terminal or server where the player capability management system is located.
  • the local component list contains all the capability components corresponding to the acquisition device, the required capability components are directly obtained from the local component list and loaded into the player.
  • the local component list does not contain all the capability components corresponding to all devices, then the available capability components are retrieved from the local component list, and the missing capability components are recorded in the missing capability list. After traversing the local component list, the missing capability components are retrieved from the cloud component library or the component library of the IoT platform. Finally, the capability components retrieved from the local component list and the capability components retrieved from other component libraries are loaded into the player.
  • the player can match and load corresponding capability components according to the detected IoT devices, avoiding the installation of too many unnecessary redundant plugins. Furthermore, this embodiment can obtain missing capability components from the cloud platform, thus avoiding excessive caching of capability components locally in the capability management system and saving local space resources.
  • the capability components in the missing capability list are added to the local component list. This expands the local component list to support more media acquisition devices.
  • Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. As shown in Figure 5, the electronic device includes at least a player and a player capability management system.
  • the player capability management system can be used to match the capabilities of media content acquisition devices and install the corresponding capability components for the acquisition devices, so that the player can be used to play media content.
  • the player capability management system is configured to acquire access information of the acquisition device and send capability requests corresponding to the acquisition device based on the access information, so that the IoT platform generates response information based on the capability requests;
  • the player capability management system is configured to install the capability components corresponding to the acquisition device based on the response information.
  • the player capability management system is configured to obtain capability component information based on response information, and to match and install the capability components corresponding to the acquisition device based on the capability component information.
  • the player capability management system is configured to be at least one of the following:
  • the missing capability list is obtained by searching the local component list based on the capability component information.
  • a component request is sent based on the missing capability list to obtain and install the capability components in the missing capability list.
  • the player capability management system is configured to add capability components from the missing capability list to the local component list.
  • the player capability management system is configured to load capability components corresponding to the acquisition device into the player.
  • the player capability management system includes at least a capability matching module and a capability loading module.
  • the capability matching module is capable of matching the capabilities of a media content acquisition device
  • the capability loading module is capable of installing capability components corresponding to the acquisition device.
  • the capability matching module is responsible for obtaining capability component information corresponding to the media acquisition device, matching the required capability components based on the capability component information, and obtaining capability components from at least one of a local component library, a cloud component library, and an IoT platform component library based on the matched capability components, and providing these capability components to the capability loading module.
  • the capability loading module is responsible for installing the capability components obtained by the capability matching module into the corresponding player.
  • the electronic device provided in this application is a hardware implementation corresponding to the media playback methods provided in the above embodiments.
  • the implementation details and beneficial effects are the same as those in the media playback methods provided in the above embodiments, and will not be repeated here.
  • FIG. 6 is a schematic diagram of an Internet of Things (IoT) system provided in an embodiment of this application.
  • the IoT system includes at least: a media acquisition device, an IoT platform, and an electronic device; wherein the media acquisition device and the IoT platform are communicatively connected, and the IoT platform and the media player are communicatively connected.
  • IoT Internet of Things
  • the media acquisition device is configured to acquire media content and send it to an IoT platform;
  • the IoT platform is configured to send media content to electronic devices and, in response to requests from the electronic devices, send response messages generated according to a capability model, where the capability model characterizes the capability components required to play media content from media acquisition devices.
  • the electronic device is configured to match the capability components required for playing media content from the media acquisition device, and the required capability components are loaded into the player of the electronic device.
  • the IoT system provided in this application is a system implementation method corresponding to the media playback methods provided in the above embodiments.
  • the implementation details and beneficial effects are the same as those of the media playback methods provided in the above embodiments, and will not be repeated here.
  • Method 1 The player and player capability management system are integrated as a whole, meaning they belong to the same software package. For ease of description, this whole is named the playback system. Multiple instances of the playback system are constructed, with each instance corresponding one-to-one with a different acquisition device. Each playback system instance establishes a connection with one acquisition device. For each pair of playback system instances and acquisition devices, the media playback method provided in any of the above embodiments of this application is executed once, so that the player in that playback system instance can match and install the capability components required by the corresponding acquisition device, thereby enabling the player to play the audio and video streams acquired by the corresponding acquisition device. Each playback system instance corresponds to a player window, used to play the audio and video streams acquired by the corresponding acquisition device to the user. Ultimately, the user can simultaneously view audio and video from multiple acquisition devices through a single electronic device.
  • the electronic device includes multiple players and a player capability management system. Each player corresponds one-to-one with a different acquisition device.
  • the player capability management system matches and installs capability components between the players and the acquisition devices, ensuring that each player supports its corresponding acquisition device.
  • Each player has a corresponding window for playing the audio and video streams captured by the corresponding acquisition device to the user.
  • the user can view audio and video from multiple acquisition devices simultaneously through a single electronic device.
  • an electronic device typically establishes a connection with a data acquisition device. Once the connection is established, a binding relationship is formed between the electronic device and the data acquisition device, and the bound electronic device corresponds to the primary account device.
  • main account device When other electronic devices also need to view the media content captured by this acquisition device, they send a request to the main account device. Upon receiving the request, if the main account device agrees, it initiates device sharing. The main account device sends a sharing command to the IoT platform. The IoT platform then sends a sharing push notification to the other electronic devices based on the sharing command. Other electronic devices receiving the sharing push notification can then match and install capability components with the media acquisition device, enabling their players to play the media content captured by the acquisition device.
  • the media acquisition device sharing can also be initiated by the main account device.
  • the media playback method of this application is described in general through some examples below. It should be understood that the following examples are for the purpose of better illustrating the media playback method of this application and are not intended to be specific or limiting.
  • FIG. 7 is a schematic diagram of a media playback interaction scenario based on the Internet of Things provided in an example of this application. As shown in Figure 7, the media playback process includes the following steps:
  • the unified IoT platform defines the initialization events that need to be reported when an IoT device accesses the platform. These events include the following attributes: device authentication type, access address, port, and device identifier.
  • the IoT device corresponds to a media acquisition device.
  • IoT devices After being powered on, IoT devices first perform a self-test, scanning their own hardware to obtain the supported capabilities. Once the self-test is complete, the IoT device saves all supported capabilities to its local database. Then, the IoT device sends a device access event to the unified IoT platform. Upon receiving the access event, the unified IoT platform creates a device session and saves it to its database. Simultaneously, the platform pushes a message to the user device informing them of the IoT device's access. At this point, the user device will see the online device card displayed as a green light and can click to access the device viewing and management page.
  • the player capability management system detects IoT device access and obtains IoT device capability components: In step 1), the IoT device accesses the unified IoT platform and reports an access event. The platform receives the event and pushes a message to the user device. At this time, the user device's background service listens for the device access message from the platform and notifies the player capability management system to start the device capability component loading process.
  • the player capability management system reads the device access message, parses the basic device information such as the device identifier, constructs a device capability request, and sends it to the unified IoT platform.
  • the platform queries the saved sessions in its database, matches the corresponding IoT device based on the device identifier, and sends a capability acquisition command to the IoT device.
  • the IoT device retrieves capability component information from its device database, creates a capability model, and returns the capability model to the unified IoT platform.
  • the unified IoT platform receives the capability model, parses it according to the device model definition, generates a response message, and returns the corresponding message to the player capability management system.
  • the response message includes the capability component information parsed from the capability model.
  • the player capability management system parses the IoT device capabilities contained in the response message field by field, caching each IoT device capability in a capability list. Once all fields have been parsed, the system uses the capability list to search for capability components in the local component repository (user component library). Found capability components are loaded into the player's launch list, while unfound capability components are added to a missing capability list. After all capability components have been searched, if any component is not recorded in the user component library, a request for the missing capability component is sent to the platform component library. The player capability management system sends the list of failed components to the platform component library, which searches for the corresponding capability component and returns the capability component file to the player capability management system one by one. The player capability management system then caches the capability component in the user component library and loads it into the player's launch list.
  • the capability list to search for capability components in the local component repository (user component library). Found capability components are loaded into the player's launch list, while unfound capability components are added to a missing capability list. After all capability components have been searched,
  • Player startup and use of capability components The player uses the capability components loaded by the player capability management system as playback capabilities, starting with modules such as encoding/decoding, transmission protocol, and output format (resolution, color gamut), and then uses them to present audio and video content to the user interface.
  • modules such as encoding/decoding, transmission protocol, and output format (resolution, color gamut)
  • the player capability management system enables user devices to sense the access of IoT devices and request the necessary capability component information from them. Based on this information, the system matches capability components to determine which components the user device's player needs to play media content from the corresponding IoT device, and then loads the appropriate components.
  • This solution matches the required capability components for different IoT devices, avoiding unnecessary pre-installation, resolving space redundancy issues, and optimizing player startup and loading speed.
  • the player matches and loads the corresponding capability components based on the sensed IoT device, avoiding the installation of too many unnecessary redundant plugins. Furthermore, it can retrieve missing capability components from the cloud platform, preventing excessive caching of capability components on the local capability management system and saving local space resources.
  • an IoT device when an IoT device adopts new capability components, such as a newly configured encoding/decoding method, an upgraded transmission protocol, or a newly built functional plugin, after connecting to the unified IoT platform and completing a self-test, the IoT device saves all capability components into its local database and uploads them to the platform's component library.
  • the platform's component library matches the uploaded capability components, selecting and retaining existing components while storing any new ones not yet present. This allows user devices to retrieve the new capability components from the platform's component library when subsequently matching and loading them with the IoT device's capabilities.
  • the player's codec capabilities and supported transmission methods can be expanded through capability components, thereby ensuring compatibility with more types of acquisition devices and guaranteeing flexibility in expansion. Furthermore, even with new capability components not present in the library, such as newly set codec methods, upgraded transmission protocols, or newly built functional plugins, updates can be performed only on the IoT device side, without requiring unified updates to the user device and platform databases, further improving scalability.
  • camera A's processor performance is 70% of camera B's, its encoding and decoding capabilities are lower, and its resolution is 2.5 megapixels, while camera B's resolution is 4 megapixels. Therefore, camera A uses H.264 encoding, which is more compatible with lower resolutions; camera A has 16MB of Flash memory and 64MB of RAM, while camera B has 128MB of Flash memory and 128MB of RAM. Therefore, camera A uses HTTP Live Streaming (HLS), a streaming media transmission protocol with lower requirements for sliding window size, while camera B uses the faster and more stable RTSP real-time streaming transmission protocol.
  • HLS HTTP Live Streaming
  • camera A lacks features such as night mode and screen flipping compared to camera B; these features are defined in camera A's device capability set.
  • the player component obtains the corresponding capability components of camera A through the media playback method provided in this application, it loads the corresponding capability components to implement effects such as black-and-white filtering and screen inversion.
  • FIG 8 is a structural block diagram of a portion of a terminal implementing the media playback method of this application embodiment.
  • the terminal includes: a radio frequency (RF) circuit 810, a memory 815, an input unit 830, a display unit 840, a sensor 850, an audio circuit 860, a wireless fidelity (WiFi) module 870, a processor 880, and a power supply 890, among other components.
  • RF radio frequency
  • the RF circuit 810 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 880; in addition, it transmits uplink data to the base station.
  • the memory 815 can be used to store software programs and modules.
  • the processor 880 executes various functional applications and data processing of the content terminal by running the software programs and modules stored in the memory 815.
  • the input unit 830 can be used to receive input numeric or character information, and to generate key signal inputs related to the settings and function control of the content terminal.
  • the input unit 830 may include a touch panel 831 and other input devices 832.
  • the display unit 840 can be used to display input or provided information, as well as various menus of the content terminal.
  • the display unit 840 may include a display panel 88.
  • Audio circuitry 860, speaker 861, and microphone 862 provide an audio interface.
  • the processor 880 included in the terminal can execute the media playback method of the previous embodiment.
  • the terminals used in this application include, but are not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, and aircraft. These embodiments can be applied to various scenarios, including but not limited to content recommendation and data filtering.
  • FIG. 9 is a structural block diagram of a portion of a server implementing the media playback method of this application.
  • the server can vary considerably depending on its configuration or performance, and may include one or more central processing units (CPUs) 922 (e.g., one or more processors) and a memory 932, and one or more storage media 930 (e.g., one or more mass storage devices) for storing application programs 99 or data 944.
  • the memory 932 and storage media 930 may be temporary or persistent storage.
  • the program stored in the storage media 930 may include one or more modules (not shown in the figure), each module including a series of instruction operations on the server.
  • the CPU 922 may be configured to communicate with the storage media 930 and execute the series of instruction operations in the storage media 930 on the server.
  • the server may also include one or more power supplies 926, one or more wired or wireless network interfaces 950, one or more input/output interfaces 958, and/or one or more operating systems 941, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • operating systems 941 such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.
  • the central processing unit 922 in the server can be used to execute the media playback method of the embodiments of this application.
  • This application also provides a computer-readable storage medium for storing program code for executing the media playback methods of the foregoing embodiments.
  • This application also provides a computer program product, which includes a computer program.
  • a processor of a computer device reads and executes the computer program, causing the computer device to perform the media playback method described above.
  • a capability management system is constructed, enabling user terminals to perceive the access of media content acquisition devices and request capabilities from these devices to obtain corresponding capability component information. Based on this information, capability components are matched to determine which capability components the user terminal's player needs to play media content from the corresponding acquisition device, and then the relevant capability components are loaded.
  • This approach matches the required capability components for different acquisition devices and loads the corresponding components, avoiding unnecessary pre-installation of capability components, solving the problem of space redundancy, and optimizing the player's startup and loading speed.
  • the player's encoding and decoding capabilities and supported transmission methods can be expanded via capability components, thereby ensuring compatibility with a wider range of acquisition devices and guaranteeing flexibility in expansion.
  • At least one (item) means one or more, and “more than” means two or more.
  • “And/or” is used to describe the relationship between related content, indicating that three relationships can exist. For example, “A and/or B” can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character “/” generally indicates that the preceding and following related content are in an “or” relationship. "At least one (item) of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one (item) of a, b, or c can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c", where a, b, and c can be single or multiple.
  • the disclosed systems, apparatuses, and methods can be implemented in other ways.
  • the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.
  • the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separate.
  • the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
  • the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
  • the integrated unit can be implemented in hardware or as a software functional unit.
  • the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application.
  • the aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Graphics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例提供了一种媒体播放方法、物联网系统、设备、介质及产品。该方法包括：获取媒体内容采集设备的接入消息(410)；根据所述接入消息发送能力请求(420)；接收根据所述能力请求生成的能力组件信息(430)；根据所述能力组件信息匹配并安装所述采集设备对应的能力组件，所述能力组件被配置为使播放器能够播放来自所述采集设备的媒体内容(440)。

Description

媒体播放方法、物联网系统、设备、介质及产品
相关申请的交叉引用
本申请基于申请号为202410642725.4、申请日为2024年05月22日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种媒体播放方法、物联网系统、设备、介质及产品。
背景技术
媒体播放器是融合设备中心重要的一环，也是用户与终端直接进行交流的媒介之一，它能够将摄像头、智能门锁、智能机器人等终端设备采集的各种类型媒体数据显示在用户界面上。
相关技术中，不同的媒体数据采集设备会因为硬件差异，产生编解码、支持的传输协议会有不同。在智慧家庭等多设备互联的物联网场景中，在用户终端需要集成各种不同的媒体播放器来支持不同的采集设备的音视频播放。目前通过在编译阶段将需要的各类协议和需要支持的功能写入程序中，或者预设置需要的各类插件进行安装实现支持不同的采集设备。这样会带来播放器适配性差，功能冗余，占用不必要的空间资源的问题。因此，如何减少不必要的空间冗余是亟待解决的技术问题。
发明内容
本申请实施例提供一种媒体播放方法、物联网系统、设备、介质及产品。
第一方面，本申请实施例提供一种媒体播放方法，所述方法包括：获取媒体内容采集设备的接入消息；根据所述接入消息发送能力请求；接收根据所述能力请求生成的能力组件信息；根据所述能力组件信息匹配并安装所述采集设备对应的能力组件，所述能力组件被配置为使播放器能够播放来自所述采集设备的媒体内容。
第二方面，本申请实施例提供了一种电子设备，所述电子设备至少包括：播放器和播放器能力管理系统；所述播放器能力管理系统能够用于匹配媒体内容采集设备的能力和安装所述采集设备对应的能力组件，以使所述播放器能够用于播放所述媒体内容。
第三方面，本申请实施例提供了一种物联网系统，所述系统至少包括：媒体采集设备，物联网平台，电子设备；所述媒体采集设备和所述物联网平台通信连接；所述物联网平台和所述媒体播放器通信连接；所述媒体采集设备被配置为采集媒体内容，并将所述媒体内容发送至所述物联网平台；所述物联网平台被配置为将所述媒体内容发送至所述电子设备，并响应所述电子设备的请求发送根据能力模型生成的响应消息，其中所述能力模型用于表征播放来自所述媒体采集设备的媒体内容所需的能力组件；所述电子设备被配置为能够匹配用于播放来自所述媒体采集设备的媒体内容所需的能力组件，并将所述所需的能力组件加载到所述电子设备的播放器。
第四方面，本申请实施例提供了一种电子设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如第一方面所述的媒体播放方法。
第四方面，本申请实施例提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行第一方面所述的媒体播放方法。
第五方面，本申请实施例提供了一种计算机程序产品，包括计算机程序或计算机指令，所述计算机程序或所述计算机指令存储在计算机可读存储介质中，计算机设备的处理器从所述计算机可读存储介质中读取所述计算机程序或所述计算机指令，所述处理器执行所述计算机程序或所述计算机指令，使得所述计算机设备执行如第一方面所述的媒体播放方法。
附图说明
图1是本申请一实施例提供的媒体播放方法所应用的系统架构图；
图2是本申请另一实施例提供的媒体播放方法所应用的系统架构图；
图3是本申请一实施例提供的基于物联网的平台系统架构图；
图4是本申请一实施例提供的媒体播放方法的流程图；
图5是本申请一实施例提供的电子设备的结构示意图
图6是本申请一实施例提供的物联网系统的示意图；
图7是本申请一示例提供的基于物联网的媒体播放交互场景的示意图；
图8是实现本申请实施例的媒体播放方法的终端的部分的结构框图；
图9是实施本申请实施例的媒体播放方法的服务器的部分的结构框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中，“示例性地”等词用于表示作为例子、例证或说明，不应被解释为比其它实施例或设计方案更优选或更具有优势。使用“示例性地”等词旨在以具体方式呈现相关概念。
相关技术中，媒体播放器是融合设备中心重要的一环，也是用户与终端直接进行交流的媒介之一，它能够将媒体采集设备采集的各种类型媒体数据显示在用户界面上。在智慧家庭终端系统中，摄像头、智能门锁、智能机器人等媒体采集设备都具有音视频采集传输能力，能够将自身采集的音视频数据通过中继云平台显示给用户查看。但是，不同设备之间所拥有的音视频能力会因为内存、CPU、传感器等硬件差异，产生编解码、传输协议的不同，这些差异性会导致在适配不同的设备时，需要集成各种不同的媒体播放器以及进行播放，从而带来软件臃肿、适配性差、开发难度大等问题。
相关技术中，不同的媒体数据采集设备会因为硬件差异，产生编解码、支持的传输协议会有不同。在智慧家庭等多设备互联的物联网场景中，在用户终端需要集成各种不同的媒体播放器来支持不同的采集设备的音视频播放。
目前通过在编译阶段将需要的各类协议和需要支持的功能写入程序中。例如IJKPlayer(一种轻量级视频播放器)：该播放器是编译时配置支持的协议(如实时流传输协议(Real Time Streaming Protocol，RTSP)、超文本传输协议(Hypertext Transfer Protocol，HTTP)、安全套接层(Secure Socket Layer，SSL)等)和编码(H.264、H.265(高度压缩数字视频编解码器标准)等)，然后打包成共享库，将共享库作为播放内核集成到应用中。这种方式会导致的问题就是拓展的灵活性会降低很多，同时容易出现冗余的配置项。比如：摄像头设备需要支持RTSP协议，H.264编码，机器人设备需要支持HTTP协议，H.265编码，这时候就需要将两个协议和编码都编译到播放器共享库中，但是如果用户只使用了摄像头设备，就会带来软件包的功能冗余。
或者预设置需要的各类插件进行安装实现支持不同的采集设备。例如VLC播放器提供了插件系统，但是该系统无法与外部系统联动。该插件系统提供了一系列预置的插件在播放器初启动阶段使用，同时也无法根据不同的设备能力启用或者关闭对应的插件，因此会出现冗余的启动时插件拖慢应用启动速度和占用应用空间。这样会带来播放器适配性差，功能冗余，占用不必要的空间资源的问题。因此，如何减少不必要的空间冗余是亟待解决的技术问题。
本申请实施例提供了一种媒体播放方法、物联网系统、设备、介质及产品，通过构建能力管理系统，使得用户终端能够对媒体内容的采集设备的接入进行感知，并且能够向采集设备进行能力请求，以得到采集设备对应的能力组件信息。从而基于能力组件信息进行能力组件的匹配，确定用户终端的播放器为了播放对应采集设备的媒体内容需要具备哪些能力组件，并进行相关能力组件的装载。通过上述方案，能够匹配不同采集设备所需的能力组件，再进行对应能力组件的装载，避免了不必要的能力组件的预置，解决了空间冗余的问题，并且能够优化播放器的启动加载速度。同时在相关技术中，播放器初始启动阶段就加载全部预设置的插件，会造成启动速度过慢，和加载过多不必要的插件导致冗余的问题；通过本申请的动态匹配的方式，播放器按照感知到的采集设备进行对应的能力组件匹配和装载，避免安装过多不必要的冗余插件，并且在不同的采集设备的播放进行切换时，根据动态匹配装载所需的能力，提升播放媒体数据时的响应和加载速度。在接入采用新的编解码能力和传输协议的采集设备时，能够通过能力组件扩展播放器的编解码能力和支持的传输方式，从而兼容更多种类的采集设备的接入，保证拓展的灵活性。
本申请实施例提供一种媒体播放方法、物联网系统、设备、介质及产品，旨在提高对采集设备的适配性的同时，减少不必要的空间冗余。
下面结合附图，对本申请实施例作进一步阐述。
图1是本申请一实施例提供的媒体播放方法所应用的系统架构图。如图1所示，该系统包括但不限于服务器110、媒体采集设备120、用户终端130等。
服务器110是指能对用户终端130提供能力管理服务、媒体播放服务、与媒体采集设备120交互服务的计算机系统。在本实施例中，服务器110装载了能力管理系统，能够实现对用户终端130和媒体采集设备120之间的能力组件识别、匹配，以及帮助用户终端130进行能力组件安装等功能。相对于用户终端130来说，服务器110在稳定性、安全性、性能等方面都要求更高。服务器110可以是网络平台中的一台高性能计算机、多台高性能计算机的集群、一台高性能计算机中划出的一部分(例如虚拟机)、多台高性能计算机中划出的一部分(例如虚拟机)的组合等。服务器110也可以以有线或无线的方式与媒体采集设备120和/或用户终端130进行通信，交换数据。
媒体采集设备120是指对音视频数据等媒体信息进行采集，并能够向用户终端130提供媒体信息的设备。它包括但不限于摄像头、智能门锁、智能机器人、智能电视、带音视频采集能力的其他设备或装置等。媒体采集设备120也可以以有线或无线的方式与服务器110进行通信，交换数据。
用户终端130是向用户播放媒体采集设备120采集到的媒体信息的设备。用户终端130安装有播放器131，播放器131用于根据媒体信息播放音频或视频。用户终端130包括桌面电脑、膝上型电脑、PDA(个人数字助理)、手机、车载终端、家庭影院终端、专用终端等多种形式。另外，它可以是单台设备，也可以是多台设备组成的集合。例如，多台设备通过局域网连接，公用一台显示设备进行协同工作，共同构成一个终端。用户终端130也可以以有线或无线的方式与服务器110进行通信，交换数据。
图2是本申请另一实施例提供的媒体播放方法所应用的系统架构图。如图2所示，该系统包括但不限于网络210、媒体采集设备220、用户终端230等。
网络210可以为互联网、物联网、家庭区域网等，在此不做具体限定。
媒体采集设备220是指对音视频数据等媒体信息进行采集，并能够向用户终端130提供媒体信息的设备。它包括但不限于摄像头、智能门锁、智能机器人、智能电视、带音视频采集能力的其他设备或装置等。媒体采集设备120也可以以有线或无线的方式与网络210进行通信，交换数据，以和用户终端230实现交互。
用户终端230是向用户播放媒体采集设备220采集到的媒体信息的设备。用户终端230安装有播放器231，播放器231用于根据媒体信息播放音频或视频。用户终端230还装载有能力管理系统232；通过能力管理系统232，用户终端230能够从媒体采集设备220获取对应的能力组件信息并进行能力匹配，基于能力匹配结果，进行能力组件的获取和安装，以使得播放器231能够适配各种媒体采集设备220。用户终端230包括桌面电脑、膝上型电脑、PDA(个人数字助理)、手机、车载终端、家庭影院终端、专用终端等多种形式。另外，它可以是单台设备，也可以是多台设备组成的集合。例如，多台设备通过局域网连接，公用一台显示设备进行协同工作，共同构成一个终端。用户终端230也可以以有线或无线的方式与网络210进行通信，交换数据，以和媒体采集设备210实现交互。
本申请实施例可以应用在智能家居、多媒体融合交互、智慧校园、工业生产管理等多种场景下。
图3为本申请一实施例提供的基于物联网的平台系统架构图。如图3所示的场景中，包括：
1)媒体采集设备：媒体采集设备指具备多媒体数据采集、编解码、传输、播放等基础能力的物联网(Internet of Things，IoT)设备。这些设备将采集的音视频数据通过一定的编码格式保存在本地存储或者传输给云平台，并且能够通过通信协议建立设备服务器。媒体采集设备还存储了自身所具备的设备基础能力组件信息。
2)云平台、中继服务器：云平台和中继服务器承担了数据库和代理的作用。云平台的数据库保存了媒体采集设备的音视频文件，能够让播放器通过特点特定的端口和IP地址获取音视频文件并播放。同时，云平台的能力组件中心是实现播放器插件部署的方式之一，云平台的能力组件中心即为提供各类能力组件上传和下载的云端数据库。中继服务器用于进行媒体采集设备与用户终端、能力管理系统之间的数据解析转换及相互传递。
3)用户终端：用户终端接收终端设备是播放器和播放器能力管理系统的载体，用户能够从用户终端携带的图形系统中看到媒体采集设备接的接入，通过设备管理流程可以查看媒体采集设备采集的音视频数据。
4)播放器能力管理系统：能力管理系统是连通媒体采集设备和用户终端的中间件。该系统的主要功能是当检测到媒体采集设备接入时，获取媒体采集设备所需要的播放器能力组件集合，然后将对应的能力组件安装到播放器中以提供设备支持。
示例性地，基于图3提供的平台系统架构，以家用监控场景为例。假设当前媒体采集设备为家用摄像头，播放器和播放器能力管理系统均设置在用户终端中。
当家用摄像头接入平平台系统后，家用摄像头会向平台上报接入消息。平台根据接入消息，向用户终端告知接入的设备标识等基础消息。用户终端监听到家用摄像头接入系统的消息后，则会通知播放器能力管理系统进行能力组件的匹配和装载。
播放器能力管理系统根据接入的媒体采集设备的标识，生成能力请求。播放器能力管理系统通过中继服务器向家用摄像头发送能力请求。家用摄像头根据能力请求中携带的请求信息，将自身所需的各个能力组件的信息通过中继服务器返回给播放器能力管理系统。
播放器能力管理系统与返回的家用摄像头所需的能力组件进行匹配，确定家用摄像头所支持的传输协议、编解码协议、功能插件等等。如果播放器能力管理系统发现本地缺失某个能力组件，则向云平台的能力组件中心请求对应的能力组件。播放器能力管理系统匹配并获取到家用摄像头所需的全部能力组件后，将这些能力组件全部装在至播放器中，使得播放器能够支持家用摄像头。
完成能力组件装载后，播放器通过云平台或者直接向家用摄像头获取其采集的音视频数据，并进行播放。
上述示例中，通过播放器能力管理系统，使得用户终端能够对媒体采集设备(如家用摄像头)的接入进行感知，并且能够向媒体采集设备请求得到其所需的能力组件信息。从而基于能力组件信息进行能力组件的匹配，确定用户终端的播放器为了播放对应采集设备的媒体内容需要具备哪些能力组件，并进行相关能力组件的装载。通过上述示例对应的方案，能够匹配不同采集设备所需的能力组件，再进行对应能力组件的装载，避免了不必要的能力组件的预置，解决了空间冗余的问题，并且能够优化播放器的启动加载速度。通过本示例的动态匹配的方式，播放器按照感知到的采集设备进行对应的能力组件匹配和装载，避免安装过多不必要的冗余插件。并且能够从云平台获取本地缺失的能力组件，这样避免过多的能力组件缓存在能力管理系统本地，节省本地空间资源。
图4是本申请一实施例提供的媒体播放方法的流程图。该媒体播放方法可以但不限应用于用户终端、如图1提供的系统中的用户终端130、如图2提供的系统中的用户终端230、或如图3提供的平台系统的用户终端中。如图4所示，该媒体播放方法至少包括但不限于：
步骤410、获取媒体内容采集设备的接入消息；
步骤420、根据接入消息发送能力请求；
步骤430、接收根据能力请求生成的能力组件信息；
步骤440、根据能力组件信息匹配并安装采集设备对应的能力组件，能力组件被配置为使播放器能够播放来自采集设备的媒体内容。
在步骤410中，媒体内容是指音视频数据流。采集设备是指生成并对外发送音视频数据流的设备，例如摄像头、智能门锁、智能机器人等。接入消息是指采集设备与物联网平台或用户终端建立通信连接时，用户终端获取的用于指示采集设备的基础信息的消息。
在步骤420中，能力请求是指用于向接入的采集设备请求获取采集设备的所需的能力组件的消息。
在步骤430中，能力组件信息是指用于指示采集设备需要哪些能力组件的信息，示例性地，能力组件信息可以是各个能力组件的标识。
在步骤440中，根据能力组件信息匹配是指播放器能力管理系统根据能力组件信息，从本地或者云端服务器获取采集设备所需的能力组件。安装采集设备对应的能力组件是指将匹配阶段获取的采集设备所需的能力组件安装至播放器中，以使播放器能够支持对应的采集设备。
在本申请中，能力是指媒体采集设备所支持的传输协议、编解码协议、各类功能插件，如黑白过滤、画面翻转、夜间模式、图像滤波等。能力组件是指能够实现上述能力的模块或插件，可以是一段封装好的代码，也可以是单独的软件插件或软件模块。
在上述步骤410至步骤440，可以是由安装有播放器能力管理系统及播放器的用户终端执行，也可以是由安装有播放器的用户终端和单独通过其他终端或服务器部署的播放器能力管理系统共同执行。
在上述步骤410至步骤440中，用户终端能够对媒体采集设备的接入进行感知，并且能够向采集设备请求得到其所需的能力组件信息。从而基于能力组件信息进行能力组件的匹配，确定用户终端的播放器为了播放对应采集设备的媒体内容需要具备哪些能力组件，并进行相关能力组件的装载。在本申请实施例中，能够匹配不同采集设备所需的能力组件，再进行对应能力组件的装载，避免了不必要的能力组件的预置，解决了空间冗余的问题，并且能够优化播放器的启动加载速度。通过本本申请实施例的动态匹配的方式，播放器按照感知到的采集设备进行对应的能力组件匹配和装载，避免安装过多不必要的冗余插件。
以上是对步骤410至步骤440的总体描述，下面对步骤410至步骤440的实施过程进行详细描述。
在步骤410中，获取媒体内容采集设备的接入消息。
在一实施例中，如在图1或图3提供的系统架构中，采集设备会向服务器上报初始化事件，其中，初始化事件包含设备认证类型、接入地址、端口、设备标识符等属性。服务器收到初始化事件后，向用户终端发送接入消息，以通知有新的采集设备接入，并且由服务器创建一个设备会话存在数据库中。通过服务器作为中继，对用户终端和采集设备之间交互的消息进行转换，让双方都能无障碍地识别对方发送的信息。
在另一实施例中，如在图2提供的系统架构中，当用户终端通过网络直接与采集设备通信时，在新的采集设备接入时，用户终端通过监听获取该采集设备的接入消息，从而得到该采集设备的基础设备信息，如设备标识符等。
在步骤420中，根据接入消息发送能力请求。
在一实施例中，用户终端根据接入消息中的设备标识符，生成对应的能力请求，能力请求中携带向指定采集设备获取其支持的能力组件的消息。需要说明的是，在本申请中，媒体采集设备/采集设备支持的能力组件，即媒体采集设备/采集设备所需要的能力组件。
在存在中继服务器或物联网统一平台(服务器)的情况下，用户终端将能力请求发送给服务器，服务器根据能力请求匹配到对应的采集设备后，根据能力请求转换为采集设备能够识别的能力获取指令发送给对应的采集设备。
在如图2提供的系统架构中，当用户终端通过网络直接与采集设备通信时，用户终端直接将能力请求发送给对应的采集设备。
在步骤430中，接收根据能力请求生成的能力组件信息。
在一实施例中，在播放器能力管理系统设置在用户终端或电子设备侧的情况下，步骤430包括：
物联网平台根据能力请求发送能力获取指令；
物联网平台接收根据能力获取指令生成的能力模型；
物联网平台根据能力模型，生成响应消息，其中，响应消息包括能力组件信息。
其中，物联网平台是指物联网统一平台，通常部署在一个或多个服务器中。物联网平台用于进行采集设备和用户终端之间的消息中转。
能力获取指令是指用于指示对应的采集设备发送自身能力模型的指令，其中，基于能力请求中携带的设备标识符确定目标采集设备。能力模型是指采集设备基于预设置的数据结构类型将自身各个能力组件的信息整合得到的数据组。
响应消息是指有物联网平台对能力模型进行解析得到能力模型中对应的能力组件信息后，生成的用户终端能够识别的规范数据。用户终端能够从响应消息中获取能力组件信息。
在上述实施例中，由于播放器能力管理系统设置在用户终端/电子设备侧，为了能够兼容不同的采集设备的信息交互，因此需要通过物联网平台进行消息中转，以使得用户终端与采集设备两端都能够识别对方发送的消息/指令。
在另一实施例中，在播放器能力管理系统设置在物联网平台(服务器)侧的情况下，步骤430包括：
接收采集设备根据能力请求生成的能力模型；
解析能力模型，得到能力组件信息。
由于播放器能力管理系统设置在物联网平台侧，因此能力匹配流程则由物联网平台和采集设备之间进行。此时，能力请求直接由物联网平台中的播放器能力管理系统向采集设备发送，采集设备根据能力请求生成自身的能力模型并返回至物联网平台中的播放器能力管理系统。
由于播放器能力管理系统设置在物联网平台，因此不需要再根据能力模型生成响应消息给用户终端。而是直接有物联网平台对能力模型进行解析得到对应的能力组件信息，并进行能力组件匹配，获取采集设备所需要的能力组件。物联网平台再将匹配得到的能力组件发送给用户终端，以供播放器进行能力组件装载。
在步骤440中，根据能力组件信息匹配并安装采集设备对应的能力组件，能力组件被配置为使播放器能够播放来自采集设备的媒体内容。
在一实施例中，步骤440包括：
根据能力组件信息，匹配采集设备所需的能力组件；
根据采集设备所需的能力组件，查找并安装采集设备对应的能力组件。
其中，匹配采集设备所需的能力组件是指对能力组件信息进行解析，确定能力组件信息中包含的采集设备能力(能力组件)，从而确定采集设备需要哪些能力组件。
查找能力组件是指从播放器所在的用户终端本地，或物联网平台数据库，又或者是云端能力组件库中搜索并获取所需要的能力组件。安装能力组件是指将获取的能力组件加载至播放器，以使播放器能够支持对应的采集设备并播放该采集设备的音视频流。
在一实施例中，查找并安装采集设备对应的能力组件，至少包括以下之一：
查找本地组件列表，将查找到的采集设备对应的能力组件加载进播放器；
查找本地组件列表，得到缺失能力列表，根据缺失能力列表发送组件请求，获取并安装缺失能力列表中的能力组件；其中，缺失能力列表包括本地组件列表中缺少的采集设备所需的能力组件。
本地组件列表是指播放器所在用户终端本地的能力组件库，又或者是播放器能力管理系统所在用户终端或服务器本地的能力组件库。
当本地组件列表具备采集设备对应的全部能力组件，则直接从本地组件列表获取所需的能力组件并加载进播放器中。
当本地组件列表不具备全集设备对应的全部能力组件，则从本地组件列表获取能够查找到的能力组件，并将缺失的能力组件记录至缺失能力列表中。再遍历完本地组件列表后，根据缺失能力列表向云端组件库或者物联网平台的组件库获取列表中确实的能力组件。最后，将从本地组件列表中获取的能力组件和从其他组件库获取的能力组件加载进播放器中。
上述实施例，播放器能够按照感知到的物联网设备进行对应的能力组件匹配和装载，避免安装过多不必要的冗余插件。并且本申请实施例能够从云平台获取本地缺失的能力组件，这样避免过多的能力组件缓存在能力管理系统本地，节省本地空间资源。
在一实施例中，在根据缺失能力列表获得列表中对应的能力组件后，将缺失能力列表中的能力组件添加到本地组件列表。从而对本地组件列表进行扩展，以使本地组件列表能够支持更多的媒体采集设备。
图5为本申请一实施例提供的电子设备的结构示意图。如图5所示，该电子设备至少包括：播放器和播放器能力管理系统。
播放器能力管理系统能够用于匹配媒体内容采集设备的能力和安装采集设备对应的能力组件，以使播放器能够用于播放媒体内容。
在一实施例中，播放器能力管理系统被配置为获取采集设备的接入信息，并根据接入信息发送采集设备对应的能力请求，以使物联网平台根据能力请求生成响应信息；
播放器能力管理系统被配置为根据响应信息安装采集设备对应的能力组件。
在一实施例中，播放器能力管理系统被配置为根据响应信息得到能力组件信息，并根据能力组件信息匹配和安装采集设备对应的能力组件。
在一实施例中，播放器能力管理系统被配置为至少以下之一：
根据能力组件信息查找本地组件列表，安装查找到的采集设备对应的能力组件；
根据能力组件信息查找本地组件列表得到缺失能力列表，根据缺失能力列表发送组件请求，获取并安装缺失能力列表中的能力组件。
在一实施例中，播放器能力管理系统被配置为将缺失能力列表中的能力组件添加到本地组件列表。
在一实施例中，播放器能力管理系统被配置为将采集设备对应的能力组件加载到播放器。
在一实施例中，播放器能力管理系统至少包括：能力匹配模块和能力装载模块；能力匹配模块能够匹配媒体内容采集设备的能力，能力装载模块能够安装采集设备对应的能力组件。其中，能力匹配模块负责获取媒体采集设备对应的能力组件信息，并且根据能力组件信息匹配得到媒体采集设备所需要的能力组件，以及根据匹配到能力组件从本地组件库、云端组件库、物联网平台组件库其中至少之一中获取能力组件，并将这些能力组件给到能力装载模块。能力装载模块负责将能力匹配模块获取的能力组件安装至对应的播放器中。
需要说明的是，本申请实施例提供的电子设备是与上述各实施例提供的媒体播放方法对应的硬件实施方式。其中，实施细节与有益效果均与上述各实施例提供的媒体播放方法对应，在此不做赘述。
图6为本申请一实施例提供的物联网系统的示意图。如图6所示，该物联网系统至少包括：媒体采集设备，物联网平台，电子设备；其中，媒体采集设备和物联网平台通信连接，物联网平台和媒体播放器通信连接。
媒体采集设备被配置为采集媒体内容，并将媒体内容发送至物联网平台；
物联网平台被配置为将媒体内容发送至电子设备，并响应电子设备的请求发送根据能力模型生成的响应消息，其中能力模型用于表征播放来自媒体采集设备的媒体内容所需的能力组件；
电子设备被配置为能够匹配用于播放来自媒体采集设备的媒体内容所需的能力组件，并将所需的能力组件加载到电子设备的播放器。
需要说明的是，本申请实施例提供的物联网系统是与上述各实施例提供的媒体播放方法对应的系统实施方式。其中，实施细节与有益效果均与上述各实施例提供的媒体播放方法对应，在此不做赘述。
在一实施例中，若一个电子设备需要同时播放多个采集设备采集的音视频流，则可以通过以下两种方式实现：
方式1：播放器和播放器能力管理系统为一个整体，可以理解为播放器和播放器能力管理系统属于同一个软件包。为方便描述，该整体命名为播放系统。构建多个播放系统的实例，多个播放系统实例与多个采集设备之间一一对应。每个播放系统实例分别与一个采集设备建立连接。针对每一对播放系统实例与采集设备，均会执行一次本申请上述任意实施例提供媒体播放方法，以使该播放系统实例中的播放器能够匹配并安装对应的采集设备所需的能力组件，从而播放器能够播放对应的采集设备采集的音视频流。每个播放系统实例对应有一个播放器窗口，用于向用户播放对应的采集设备采集的音视频流。最终用户能够通过一个电子设备同时查看多个采集设备对应的音视频。
方式2：电子设备包括多个播放器和一个播放器能力管理系统。多个播放器与多个采集设备一一对应。多个播放器通过一个播放器能力管理系统实现与采集设备之间的能力组件匹配和安装，以使每个播放器均能够支持与其对应的采集设备。每个播放器对应有一个窗口，用于向用户播放对应的采集设备采集的音视频流。最终用户能够通过一个电子设备同时查看多个采集设备对应的音视频。
在一实施例中，一个电子设备通常与一个采集设备建立连接。电子设备与采集设备之间建立连接后会形成绑定关系，绑定后的电子设备则对应为主账号设备。
当其他电子设备也需要查看该采集设备采集的媒体内容时，其他电子设备向主账号设备发起请求。主账号设备接收到请求后，若主账号设备同意请求，则会发起设备共享。主账号设备会向物联网平台发送共享指令。物联网平台会根据共享指令发送共享推送给其他电子设备。接收到共享推送的其他电子设备则能够与媒体采集设备之间进行能力组件匹配和安装，以使其他电子设备的播放器能够播放该媒体采集设备的媒体内容。
在其他实施例中，也可以由主账号设备主动发起媒体采集设备共享。
下面通过一些示例对本申请的媒体播放方法进行整体性的说明。可以理解的是，下述示例均是为了更好地对本申请的媒体播放方法进行示例性说明，并不做具体限定。
图7为本申请一示例提供的基于物联网的媒体播放交互场景的示意图。如图7所示，媒体播放流程包括以下步骤：
1)物联网设备接入物联网统一平台：首先，物联网统一平台定义了物联网设备接入时需要上报的初始化事件，该事件包括以下属性：设备认证类型、接入地址、端口、设备标识符。其中，本示例中的物联网设备对应媒体采集设备。
物联网设备接通电源之后首先进行自检，设备会扫描自身硬件获取自身所支持的能力组件。自检完成后，物联网设备会将所有的能力组件保存进设备本地数据库中。然后，物联网设备会向物联网统一平台发送设备接入事件，物联网统一平台收到接入事件将创建一个设备会话并保存到数据库中，同时平台向用户设备推送消息告知该物联网设备接入。此时，用户设备能够看到上线设备卡片显示为绿灯，同时能够点击进入设备查看和管理页面。
2)播放器能力管理系统检测物联网设备接入，获取物联网设备能力组件：在第1)步中，物联网设备接入物联网统一平台并上报了接入事件，平台收到事件并推送消息到用户设备上。此时，用户设备的后台服务监听到平台的设备接入消息，便会通知播放器能力管理系统启动设备能力组件装载流程。
首先，播放器能力管理系统会读取设备接入消息，解析接入消息中的设备基础信息，如设备标识符，然后构造设备能力请求，并能力请求发送到物联网统一平台。平台收到来自用户的请求后会查询数据中的保存的会话，根据设备标识符匹配到对应的物联网设备后，发送能力获取指令给物联网设备。之后，物联网设备收到获取能力的指令后会检索设备数据库查询能力组件信息，并创建能力模型，将能力模型返回给物联网统一平台。物联网统一平台收到能力模型后，按照物模型定义解析能力模型并生成响应消息，并将相应消息返回给播放器能力管理系统。其中，响应消息包括从能力模型中解析得到的能力组件信息。
3)播放器能力管理系统装载能力组件：在2)中，播放器能力管理系统获取到设备能力模型的响应消息后，即启动播放器能力组件装载流程。
首先，播放器能力管理系统会逐字段解析响应消息中包含的物联网设备能力，每次解析到一个物联网设备能力都会将其缓存到一个能力列表中。当所有字段都被解析完成之后，播放器能力管理系统使用能力列表去查找本地组件仓库(用户组件库)中的能力组件，将查找到的能力组件加载进播放器启动列表，未查找到的能力组件放入缺失能力列表中。所有能力组件查找完毕后，如果有用户组件库未记录的组件，则向平台组件库请求缺失的能力组件。播放器能力管理系统将失败的组件列表发送至平台组件库，平台组件库搜索对应的能力组件，将能力组件文件逐个返回给播放器能力管理系统，播放器能力管理系统将能力组件缓存进用户组件库的同时，将能力组件加载进播放器的启动列表。
4)播放器启动并使用能力组件：播放器将播放器能力管理系统加载的能力组件作为播放能力，从编解码、传输协议、输出格式(分辨率，色域)等模块开始依次序启用能力组件，最终用于呈现音视频内容到用户界面。
上述示例中，通过播放器能力管理系统，使得用户设备能够对物联网设备的接入进行感知，并且能够向物联网设备请求得到其所需的能力组件信息。从而基于能力组件信息进行能力组件的匹配，确定用户设备的播放器为了播放对应的物联网设备的媒体内容需要具备哪些能力组件，并进行相关能力组件的装载。通过上述示例对应的方案，能够匹配不同物联网设备所需的能力组件，再进行对应能力组件的装载，避免了不必要的能力组件的预置，解决了空间冗余的问题，并且能够优化播放器的启动加载速度。通过本示例的动态匹配的方式，播放器按照感知到的物联网设备进行对应的能力组件匹配和装载，避免安装过多不必要的冗余插件。并且能够从云平台获取本地缺失的能力组件，这样避免过多的能力组件缓存在能力管理系统本地，节省本地空间资源。
在另一示例中，当物联网设备采用了新的能力组件时，例如新设置的编解码方式、升级后的传输协议、新构建的功能插件等，物联网设备在接入物联网统一平台，并自检完成后，物联网设备会将所有的能力组件保存进设备本地数据库中，并将所有的能力组件上传至平台组件库中。平台组件库根据物联网设备上传的能力组件进行匹配，将已存在库中的能力组件择一保留，将库中未存在的新的能力组件进行存储。从而在后续用户设备进行与物联网设备的能力组件匹配和装载时，能够从平台组件库获取物联网设备的新的能力组件。
上述示例中，在接入采用新的编解码能力和传输协议的物联网设备(媒体采集设备)时，能够通过能力组件扩展播放器的编解码能力和支持的传输方式，从而兼容更多种类的采集设备的接入，保证拓展的灵活性。并且在新设置了编解码方式、升级后的传输协议、新构建的功能插件等库中不存在的新能力组件的情况下，能够只对物联网设备侧进行相关组件更新，不需要在用户设备、平台的数据库中统一更新，进一步提高可扩展性。
示例性地，假设存在摄像头A和摄像头B对比：摄像头A的处理器性能是摄像头B的70％，其编解码能力较低，分辨率为250万，摄像头B的分辨率为400万。因此摄像头A使用了对低分辨率更友好的H.264编码；摄像头A的Flash闪存为16MB，内存为64MB，而摄像头B的Flash为128MB，内存为128MB，因此，摄像头A采用了对滑动窗口大小要求更低的基于HTTP的流媒体传输协议(HTTP Live Streaming，HLS)，而摄像头B则采用更快更稳定的RTSP实时流传输协议。同时，摄像头A相对与摄像头B少了夜间模式、画面翻转等功能，这些功能都定义在摄像头A的设备能力集中。播放器组件通过本申请提供媒体播放方法获取摄像头A对应的能力组件之后，加载对应的能力组件来实现黑白过滤、画面倒置等效果。
图8为实现本申请实施例的媒体播放方法的终端的部分的结构框图。如图8所示，该终端包括：射频(Radio Frequency，简称RF)电路810、存储器815、输入单元830、显示单元840、传感器850、音频电路860、无线保真(wireless fidelity，简称WiFi)模块870、处理器880、以及电源890等部件。本领域技术人员可以理解，图8示出的终端结构并不构成对手机或电脑的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
RF电路810可用于收发信息或通话过程中，信号的接收和发送，特别地，将基站的下行信息接收后，给处理器880处理；另外，将设计上行的数据发送给基站。
存储器815可用于存储软件程序以及模块，处理器880通过运行存储在存储器815的软件程序以及模块，从而执行内容终端的各种功能应用以及数据处理。
输入单元830可用于接收输入的数字或字符信息，以及产生与内容终端的设置以及功能控制有关的键信号输入。在一些实施例中，输入单元830可包括触控面板831以及其他输入装置832。
显示单元840可用于显示输入的信息或提供的信息以及内容终端的各种菜单。显示单元840可包括显示面板88。
音频电路860、扬声器861，传声器862可提供音频接口。
在本实施例中，该终端所包括的处理器880可以执行前面实施例的媒体播放方法。
本申请实施例的终端包括但不限于手机、电脑、智能语音交互设备、智能家电、车载终端、飞行器等。本申请实施例可应用于各种场景，包括但不限于内容推荐、数据筛选等。
图9为实施本申请实施例的媒体播放方法的服务器的部分的结构框图。服务器可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上中央处理器(Central Processing Units，简称CPU)922(例如，一个或一个以上处理器)和存储器932，一个或一个以上存储应用程序99或数据944的存储介质930(例如一个或一个以上海量存储装置)。其中，存储器932和存储介质930可以是短暂存储或持久存储。存储在存储介质930的程序可以包括一个或一个以上模块(图示没标出)，每个模块可以包括对服务器中的一系列指令操作。更进一步地，中央处理器922可以设置为与存储介质930通信，在服务器上执行存储介质930中的一系列指令操作。
服务器还可以包括一个或一个以上电源926，一个或一个以上有线或无线网络接口950，一个或一个以上输入输出接口958，和/或，一个或一个以上操作系统941，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM等等。
服务器中的中央处理器922可以用于执行本申请实施例的媒体播放方法。
本申请实施例还提供一种计算机可读存储介质，计算机可读存储介质用于存储程序代码，程序代码用于执行前述各个实施例的媒体播放方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品包括计算机程序。计算机设备的处理器读取该计算机程序并执行，使得该计算机设备执行实现上述的媒体播放方法。
在本申请中，通过构建能力管理系统，使得用户终端能够对媒体内容的采集设备的接入进行感知，并且能够向采集设备进行能力请求，以得到采集设备对应的能力组件信息。从而基于能力组件信息进行能力组件的匹配，确定用户终端的播放器为了播放对应采集设备的媒体内容需要具备哪些能力组件，并进行相关能力组件的装载。通过上述方案，能够匹配不同采集设备所需的能力组件，再进行对应能力组件的装载，避免了不必要的能力组件的预置，解决了空间冗余的问题，并且能够优化播放器的启动加载速度。并且通过动态匹配的方式，能够通过能力组件扩展播放器的编解码能力和支持的传输方式，从而兼容更多种类的采集设备的接入，保证拓展的灵活性。
本申请的说明书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的内容，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“包含”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或装置不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或装置固有的其它步骤或单元。
应当理解，在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，用于描述关联内容的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联内容是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”，其中a，b，c可以是单个，也可以是多个。
应了解，在本申请实施例的描述中，多个(或多项)的含义是两个以上，大于、小于、超过等理解为不包括本数，以上、以下、以内等理解为包括本数。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机装置(可以是个人计算机，服务器，或者网络装置等)执行本申请各个实施例方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
还应了解，本申请实施例提供的各种实施方式可以任意进行组合，以实现不同的技术效果。
以上是对本申请的实施方式的说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请精神的条件下还可作出种种等同的变形或替换，这些等同的变形或替换均包括在本申请权利要求所限定的范围内。

Claims (17)

  1. 一种媒体播放方法，包括：
    获取媒体内容采集设备的接入消息；
    根据所述接入消息发送能力请求；
    接收根据所述能力请求生成的能力组件信息；
    根据所述能力组件信息匹配并安装所述采集设备对应的能力组件，所述能力组件被配置为使播放器能够播放来自所述采集设备的媒体内容。
  2. 根据权利要求1所述的方法，其中，所述根据所述能力组件信息匹配并安装所述采集设备对应的能力组件，包括：
    根据所述能力组件信息，匹配所述采集设备所需的能力组件；
    根据所述采集设备所需的能力组件，查找并安装所述采集设备对应的能力组件。
  3. 根据权利要求2所述的方法，其中，所述查找并安装所述采集设备对应的能力组件，至少包括以下之一：
    查找本地组件列表，将查找到的所述采集设备对应的能力组件加载进所述播放器；
    查找本地组件列表，得到缺失能力列表，根据所述缺失能力列表发送组件请求，获取并安装所述缺失能力列表中的能力组件；其中，所述缺失能力列表包括所述本地组件列表中缺少的所述采集设备所需的能力组件。
  4. 根据权利要求3所述的方法，其中，所述方法还包括：
    将所述缺失能力列表中的能力组件添加到所述本地组件列表。
  5. 根据权利要求1至4任一项所述的方法，其中，所述接收根据所述能力请求生成的能力组件信息，包括：
    物联网平台根据所述能力请求发送能力获取指令；
    接收根据所述能力获取指令生成的能力模型；
    根据所述能力模型，生成响应消息，其中，所述响应消息包括所述能力组件信息。
  6. 根据权利要求1至4任一项所述的方法，其中，所述接收根据所述能力请求生成的能力组件信息，包括：
    接收所述采集设备根据所述能力请求生成的能力模型；
    解析所述能力模型，得到所述能力组件信息。
  7. 一种电子设备，所述电子设备至少包括：
    播放器和播放器能力管理系统；
    所述播放器能力管理系统能够用于匹配媒体内容采集设备的能力和安装所述采集设备对应的能力组件，以使所述播放器能够用于播放所述媒体内容。
  8. 根据权利要求7所述的电子设备，其中：
    所述播放器能力管理系统被配置为获取所述采集设备的接入信息，并根据所述接入信息发送所述采集设备对应的能力请求，以使物联网平台根据所述能力请求生成响应信息；
    所述播放器能力管理系统被配置为根据所述响应信息安装所述采集设备对应的能力组件。
  9. 根据权利要求8所述的电子设备，其中：
    所述播放器能力管理系统被配置为根据所述响应信息得到能力组件信息，并根据所述能力组件信息匹配和安装所述采集设备对应的能力组件。
  10. 根据权利要求9所述的电子设备，其中：
    所述播放器能力管理系统被配置为至少以下之一：
    根据所述能力组件信息查找本地组件列表，安装查找到的所述采集设备对应的能力组件；
    根据所述能力组件信息查找本地组件列表得到缺失能力列表，根据所述缺失能力列表发送组件请求，获取并安装所述缺失能力列表中的能力组件。
  11. 根据权利要求10所述的电子设备，其中：
    所述播放器能力管理系统被配置为将所述缺失能力列表中的能力组件添加到所述本地组件列表。
  12. 根据权利要求11所述的电子设备，其中：
    所述播放器能力管理系统被配置为将所述采集设备对应的能力组件加载到所述播放器。
  13. 根据权利要求7至12任一项所述的电子设备，其中，所述播放器能力管理系统至少包括：
    能力匹配模块和能力装载模块；
    所述能力匹配模块能够匹配媒体内容采集设备的能力，所述能力装载模块能够安装所述采集设备对应的能力组件。
  14. 一种物联网系统，所述系统至少包括：
    媒体采集设备，物联网平台，电子设备；
    所述媒体采集设备和所述物联网平台通信连接；
    所述物联网平台和所述媒体播放器通信连接；
    所述媒体采集设备被配置为采集媒体内容，并将所述媒体内容发送至所述物联网平台；
    所述物联网平台被配置为将所述媒体内容发送至所述电子设备，并响应所述电子设备的请求发送根据能力模型生成的响应消息，其中所述能力模型用于表征播放来自所述媒体采集设备的媒体内容所需的能力组件；
    所述电子设备被配置为能够匹配用于播放来自所述媒体采集设备的媒体内容所需的能力组件，并将所述所需的能力组件加载到所述电子设备的播放器。
  15. 一种电子设备，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1至6任意一项所述的方法。
  16. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至6任意一项所述的方法。
  17. 一种计算机程序产品，包括计算机程序或计算机指令，所述计算机程序或所述计算机指令存储在计算机可读存储介质中，计算机设备的处理器从所述计算机可读存储介质中读取所述计算机程序或所述计算机指令，所述处理器执行所述计算机程序或所述计算机指令，使得所述计算机设备执行如权利要求1至6任意一项所述的方法。
PCT/CN2025/095457 2024-05-22 2025-05-16 媒体播放方法、物联网系统、设备、介质及产品 Pending WO2025242002A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410642725.4 2024-05-22
CN202410642725.4A CN121012945A (zh) 2024-05-22 2024-05-22 媒体播放方法、物联网系统、设备、介质及产品

Publications (1)

Publication Number Publication Date
WO2025242002A1 true WO2025242002A1 (zh) 2025-11-27

Family

ID=97724178

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/095457 Pending WO2025242002A1 (zh) 2024-05-22 2025-05-16 媒体播放方法、物联网系统、设备、介质及产品

Country Status (2)

Country Link
CN (1) CN121012945A (zh)
WO (1) WO2025242002A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180285856A1 (en) * 2017-03-29 2018-10-04 Samsung Electronics Co., Ltd. Method for providing payment service having plug-in service, and electronic device therefor
CN110798505A (zh) * 2019-09-27 2020-02-14 深圳市火乐科技发展有限公司 插件式物联网设备的管理方法及相关装置
CN111147337A (zh) * 2019-12-30 2020-05-12 深圳Tcl数字技术有限公司 第三方设备的配网方法、终端设备及计算机可读存储介质
CN114172925A (zh) * 2020-09-10 2022-03-11 华为技术有限公司 配网方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180285856A1 (en) * 2017-03-29 2018-10-04 Samsung Electronics Co., Ltd. Method for providing payment service having plug-in service, and electronic device therefor
CN110798505A (zh) * 2019-09-27 2020-02-14 深圳市火乐科技发展有限公司 插件式物联网设备的管理方法及相关装置
CN111147337A (zh) * 2019-12-30 2020-05-12 深圳Tcl数字技术有限公司 第三方设备的配网方法、终端设备及计算机可读存储介质
CN114172925A (zh) * 2020-09-10 2022-03-11 华为技术有限公司 配网方法及设备

Also Published As

Publication number Publication date
CN121012945A (zh) 2025-11-25

Similar Documents

Publication Publication Date Title
CN114461239B (zh) 软件升级系统和软件升级方法
CN107635027B (zh) 一种域名解析方法、介质、装置和计算设备
CN113242314B (zh) 跨端资源访问方法、装置、存储介质及电子设备
CN107222326A (zh) 用于设备间服务的访问方法、配置方法及装置
KR102502655B1 (ko) 연속성을 갖는 컨텐츠 재생 방법 및 이를 위한 전자 장치
CN115550391B (zh) 设备控制方法和电子设备
CN114390501A (zh) 数据传输的方法及电子设备
US9628567B2 (en) Methods and systems for efficient discovery of devices in a peer-to-peer network
WO2017156934A1 (zh) 智能互联方法和智能终端
CN113703849B (zh) 投屏应用打开方法和装置
CN112383617B (zh) 进行长连接的方法、装置、终端设备以及介质
CN114327317B (zh) 镜像投屏方法、装置及系统
WO2022042363A1 (zh) 一种共享库的复用方法及电子设备
CN115437719A (zh) 跨操作系统的调用方法、装置及电子设备
CN112261147A (zh) 高速率共存网络模式实现方法、设备、终端及存储介质
CN112052376A (zh) 资源推荐方法、装置、服务器、设备和介质
WO2025242002A1 (zh) 媒体播放方法、物联网系统、设备、介质及产品
CN117714279B (zh) 设备管理的方法、路由器及可读存储介质
WO2015196586A1 (zh) 虚拟桌面的配置、获取方法及装置
CN112351202B (zh) 多媒体数据交互方法、系统、装置、电子设备和存储介质
CN116366957A (zh) 一种虚拟化相机使能的方法、电子设备及协同工作系统
KR102072003B1 (ko) 디바이스들 간의 리소스 공유하는 방법 및 전자 디바이스
CN116033158A (zh) 投屏方法和电子设备
WO2022228214A1 (zh) 设备发现方法、系统及其电子设备
CN117135729B (zh) 多设备协同方法、系统及终端设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25807103

Country of ref document: EP

Kind code of ref document: A1