Live broadcast stream pushing, creating, processing and pulling methods, devices and systems

Abstract

The invention provides a live broadcast stream pushing, creating, processing and pulling method, device and system, equipment, a medium and a program product. A specific embodiment of the live broadcast stream pushing method in the application comprises the steps of displaying digital rights management (DRM) encryption prompt information in response to a detected live broadcast stream creation operation; in response to the detected DRM encryption selection operation based on the DRM encryption prompt information, a live broadcast stream creation request is sent to the service end, and the live broadcast stream creation request comprises DRM encryption selection information; receiving a live broadcast stream creation result sent by the service end, wherein the live broadcast stream creation result comprises a live broadcast stream address and a DRM encryption state bound with the live broadcast stream address; and pushing live broadcast stream information to a streaming media platform based on the live broadcast stream address, the live broadcast stream information comprising common live broadcast stream data and a DRM encryption state. According to the embodiment, the encryption process transparency of the live broadcast platform is improved.

Description

Technical Field

[0001] This application relates to the field of live streaming technology, and in particular to a method, apparatus, system, device, medium, and program product for live streaming push, creation, processing, and pull. Background Technology

[0002] As the application scenarios of live streaming platforms continue to expand, they have become deeply integrated into high-value areas such as paid content distribution, course teaching, film premieres, and business presentations. In these scenarios, live streaming content often involves paid rights, intellectual property rights, or trade secrets. Therefore, the industry's requirements for the granularity of live stream permission management and the security of copyright protection are increasing, driving the upgrade of live streaming technology systems from basic content transmission to secure, controllable, and scenario-adaptable approaches to meet the differentiated management needs of live streams in different business scenarios.

[0003] Currently, mainstream live streaming platforms generally adopt standardized live stream generation and distribution mechanisms to support the stable operation of large-scale live streaming services. Under this mechanism, the platform generates a corresponding live stream identifier for each live stream request initiated by the broadcaster, which serves as the core basis for live stream data transmission and distribution. The broadcaster pushes the live stream based on this identifier. The platform then processes the received live stream and distributes the content to viewers who have passed basic permission verification, ensuring that viewers can access and watch the live stream normally. Summary of the Invention

[0004] This application provides a method, apparatus, system, device, medium, and program product for live streaming push, creation, processing, and pull, in order to solve the problem of low transparency in the encryption process of live streaming platforms.

[0005] One aspect of this application provides a live streaming method applied to a broadcaster, comprising: displaying Digital Rights Management (DRM) encryption prompt information in response to detecting a live stream creation operation; sending a live stream creation request to a business terminal in response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, the live stream creation request including DRM encryption selection information; receiving a live stream creation result sent by the business terminal, the live stream creation result including a live stream address and a DRM encryption status bound to the live stream address; and pushing live stream information to a streaming media platform based on the live stream address, the live stream information including ordinary live stream data and DRM encryption status.

[0006] Another aspect of this application provides a live stream creation method, applied to a business end, comprising: receiving a live stream creation request sent by a broadcaster, the live stream creation request including Digital Rights Management (DRM) encryption selection information; determining the DRM encryption status based on the DRM encryption selection information; generating a live stream address based on the DRM encryption status; binding the live stream address with the DRM encryption status to generate a live stream creation result; and sending the live stream creation result to the broadcaster.

[0007] Another aspect of this application provides a live streaming processing method applied to a streaming media platform, comprising: receiving live stream information pushed by a broadcaster based on a live stream address, the live stream information including ordinary live stream data and DRM encryption status; in response to determining that the DRM encryption status is enabled, obtaining encryption configuration information bound to the live stream address from the business side; and encrypting the ordinary live stream data based on the encryption configuration information to generate encrypted live stream data.

[0008] Another aspect of this application provides a live streaming pull method applied to the viewer's end, comprising: sending a query request to read the Digital Rights Management (DRM) encryption tag to the service end based on the live room identifier of the broadcaster's end; receiving the DRM encryption tag sent by the service end; in response to determining that the DRM encryption tag is enabled for DRM encryption, sending an encrypted live stream pull request to the streaming media platform based on the live stream address; receiving encrypted live stream data and encryption configuration information sent by the streaming media platform; and decrypting the encrypted live stream data based on the configuration information to obtain decrypted live stream data.

[0009] Another aspect of this application provides a live streaming device, installed on a broadcaster's end, comprising: a first display module configured to display Digital Rights Management (DRM) encryption prompt information in response to detecting a live stream creation operation; a first sending module configured to send a live stream creation request to a service terminal in response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, the live stream creation request including DRM encryption selection information; a first receiving module configured to receive a live stream creation result sent by the service terminal, the live stream creation result including a live stream address and a DRM encryption status bound to the live stream address; and a second sending module configured to push live stream information to a streaming media platform based on the live stream address, the live stream information including ordinary live stream data and DRM encryption status.

[0010] Another aspect of this application provides a live stream creation device, installed on a service end, comprising: a first receiving module configured to receive a live stream creation request sent by a broadcaster, the live stream creation request including Digital Rights Management (DRM) encryption selection information; a first determining module configured to determine a DRM encryption state based on the DRM encryption selection information; a first generating module configured to generate a live stream address based on the DRM encryption state; a second generating module configured to bind the live stream address to the DRM encryption state to generate a live stream creation result; and a first sending module configured to send the live stream creation result to the broadcaster.

[0011] Another aspect of this application provides a live streaming processing apparatus, set in a streaming media platform, comprising: a first receiving module configured to receive live stream information pushed by a broadcaster based on a live stream address, the live stream information including ordinary live stream data and DRM encryption status; an acquisition module configured to, in response to determining that the DRM encryption status is enabled, acquire encryption configuration information bound to the live stream address from a service terminal; and an encryption module configured to encrypt the ordinary live stream data based on the encryption configuration information to generate encrypted live stream data.

[0012] Another aspect of this application provides a live streaming device, installed at the viewer's end, comprising: a first sending module configured to send a query request to read the Digital Rights Management (DRM) encryption tag to a service terminal based on the live room identifier of the broadcaster's end; a first receiving module configured to receive the DRM encryption tag sent by the service terminal; a second sending module configured to, in response to determining that the DRM encryption tag is enabled for DRM encryption, send an encrypted live stream retrieval request to a streaming media platform based on the live stream address; a second receiving module configured to receive encrypted live stream data and encryption configuration information sent by the streaming media platform; and a decryption module configured to decrypt the encrypted live stream data based on the configuration information to obtain decrypted live stream data.

[0013] Another aspect of this application provides a live streaming management system, including: a broadcaster terminal, a service terminal, a streaming media platform, and a viewer terminal; the broadcaster terminal is configured to, in response to detecting a live stream creation operation, display Digital Rights Management (DRM) encryption prompt information; in response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, send a live stream creation request to the service terminal, the live stream creation request including DRM encryption selection information; receive a live stream creation result sent by the service terminal, the live stream creation result including a live stream address and a DRM encryption status bound to the live stream address; and, based on the live stream address, push live stream information to the streaming media platform, the live stream information including ordinary live stream data and a DRM encryption status; the service terminal is configured to, receive a live stream creation request sent by the broadcaster terminal, the live stream creation request including DRM encryption selection information; determine the DRM encryption status based on the DRM encryption selection information; generate a live stream address based on the DRM encryption status; and transmit the live stream... The system binds the stream address to the DRM encryption status to generate a live stream creation result; it then sends the live stream creation result to the broadcaster. The streaming media platform receives live stream information pushed by the broadcaster based on the live stream address. This live stream information includes ordinary live stream data and the DRM encryption status. In response to determining that the DRM encryption status is enabled, it retrieves the encryption configuration information bound to the live stream address from the business side. Based on the encryption configuration information, it encrypts the ordinary live stream data to generate encrypted live stream data. The viewer's end sends a query request to the business side to read the DRM encryption tag based on the broadcaster's live room identifier. It receives the DRM encryption tag sent by the business side. In response to determining that the DRM encryption tag is enabled, it sends an encrypted live stream retrieval request to the streaming media platform based on the live stream address. It receives the encrypted live stream data and encryption configuration information sent by the streaming media platform. Based on the configuration information, it decrypts the encrypted live stream data to obtain decrypted live stream data.

[0014] In another aspect of this application, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the live streaming push, creation, processing, and pull methods as described above.

[0015] In another aspect, this application provides a computer-readable storage medium having stored thereon computer program instructions that can be executed by a processor to implement the live streaming push, creation, processing, and pull methods as described above.

[0016] Another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the live streaming push, creation, processing, and pull methods as described above.

[0017] The solution provided in this application achieves technological breakthroughs through multi-dimensional innovation: First, a stream-level business identification mechanism is implemented, with the platform defining a unified mapping table. Each stream is bound to a business identifier, and only the matching stream address is returned when pulling a stream, resolving the confusion of attribution. Second, enhanced DRM interaction on the broadcaster side is achieved, with pop-up prompts for encryption functionality and UI annotations of encryption status when creating a stream, preventing misconfiguration. Third, a push-stream-room tagging Webhook linkage is implemented, where the streaming media listens for push-streaming and then calls back to the business side for tagging, supporting pre-tags and building a closed loop from push-streaming to pull-streaming. Fourth, a pull-stream-permission-terminal dynamic linkage is implemented, where the viewer first checks the tagging status, then loads the DRM component according to the device's capabilities, and only sends the encrypted stream after successful authorization verification. Fifth, exception handling and log auditing are implemented, with automatic retries for authorization failures, support for normal stream rollback, and log recording of all operations for easy traceability. Ultimately, this achieves refined authorization and secure distribution in high-value scenarios, improving copyright protection capabilities and user experience. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 A flowchart illustrating an embodiment of the live streaming method provided in this application; Figure 2 A diagram illustrating the DRM encryption prompt pop-up; Figure 3 A diagram illustrating the association between live stream URLs and DRM encryption status; Figure 4 A flowchart illustrating an embodiment of the live streaming creation method provided in this application; Figure 5 A flowchart illustrating an embodiment of the live streaming processing method provided in this application; Figure 6 A flowchart illustrating an embodiment of the live streaming pull method provided in this application; Figure 7 A schematic diagram of the structure of an embodiment of the live streaming device provided in this application; Figure 8 A schematic diagram of the structure of an embodiment of the live streaming creation apparatus provided in this application; Figure 9 A schematic diagram of the structure of an embodiment of the live streaming processing apparatus provided in this application; Figure 10 A schematic diagram of the structure of one embodiment of the live streaming device provided in this application; Figure 11 A schematic diagram of the structure of an embodiment of the live streaming management system provided in this application; Figure 12 This is a schematic diagram of the structure of a device suitable for implementing the solutions in the embodiments of this application; The same or similar reference numerals in the accompanying drawings represent the same or similar parts. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] In a typical configuration of this application, the terminal and the service network devices each include one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0022] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0023] Computer-readable media include permanent and non-permanent, removable and non-removable media, which can store information by any method or technology. Information can be computer program instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only optical disc (CD-ROM), digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0024] The solution provided in this application achieves technological breakthroughs through multi-dimensional innovation: First, a stream-level business identification mechanism is implemented, with the platform defining a unified mapping table. Each stream is bound to a business identifier, and only the matching stream address is returned when pulling a stream, resolving the confusion of attribution. Second, enhanced interaction with the broadcaster's DRM (Digital Rights Management) is achieved, with a pop-up prompting for encryption functionality and the UI (User Interface) indicating the encryption status when creating a stream, preventing misconfiguration. Third, a push-stream-room tagging Webhook linkage is implemented, where the streaming media listens for push-stream detection and then calls back to the business end for tagging, supporting pre-tags and building a closed loop from push-stream to pull-stream. Fourth, a pull-stream-permission-terminal dynamic linkage is implemented, where the viewer first checks the tagging status, then loads the DRM component according to the device's capabilities, and only sends the encrypted stream after successful authorization verification. Fifth, exception handling and log auditing are implemented, with automatic retries for authorization failures, support for normal stream rollback, and log recording of all operations for easy traceability. Ultimately, this achieves refined authorization and secure distribution in high-value scenarios, improving copyright protection capabilities and user experience.

[0025] In practical scenarios, the entity executing the above method can be a user device, a network device, or a device formed by integrating user devices and network devices through a network, or it can be an application running on the above devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and wristbands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server sets, or cloud computing-based computer sets. Here, the cloud consists of a large number of hosts or network servers based on cloud computing, where cloud computing is a type of distributed computing, consisting of a virtual computer composed of a group of loosely coupled computer sets.

[0026] Figure 1 A flowchart illustrating an embodiment of the live streaming method provided in this application is shown. The method includes at least the following processing steps: Step S101: In response to the detection of a live stream creation operation, a Digital Rights Management (DRM) encryption prompt message is displayed.

[0027] In this embodiment, when a live stream creation operation is detected, the broadcaster's client can display a DRM encryption prompt to guide the broadcaster to clarify whether to enable the copyright protection function.

[0028] The live stream creation operation can be the creation of a live stream, such as when a broadcaster clicks the "Create Live Stream" button in the live stream management backend. DRM encryption prompts can be used to ask users whether to enable DRM encryption. These prompts are primarily displayed as pop-ups, and their triggering logic is related to the live stream business type. If the business type corresponding to the broadcaster's upcoming live stream is a platform-preset high-value scenario (such as a business type requiring authorization), the pop-up will appear automatically; if it is a regular public live stream, the pop-up can be hidden and will only be triggered when the broadcaster manually switches the business type.

[0029] Figure 2 This image shows a schematic of a DRM encryption prompt pop-up. Figure 2 As shown, after the broadcaster clicks the "Create Live Stream" button, a DRM encryption prompt pop-up will appear on the broadcaster's end. The pop-up may include a description of the DRM encryption function and operation options. The DRM encryption function description could be something like, "Enabling DRM encryption will encrypt the video content of the live stream using DRM technology" (if unsure what DRM is, simply select "Enable"). The operation options may include "Enable" and "Disable," allowing the broadcaster to quickly make a selection.

[0030] Step S102: In response to detecting a DRM encryption selection operation based on DRM encryption prompt information, a live stream creation request is sent to the business end.

[0031] In this embodiment, when a DRM encryption selection operation based on DRM encryption prompt information is detected, the broadcaster can send a live stream creation request to the service provider.

[0032] DRM encryption selection information can indicate whether or not DRM encryption is enabled. For example, after the broadcaster clicks the enable or disable option in the DRM encryption prompt pop-up, the broadcaster's client can generate a live stream creation request based on the DRM encryption selection information and send the live stream creation request to the business side, ensuring that the broadcaster's encryption configuration intention is accurately conveyed to the business side.

[0033] Step S103: Receive the live stream creation result sent by the service terminal.

[0034] In this embodiment, the broadcaster can receive the live stream creation result sent by the service provider.

[0035] After processing the live stream creation request, the business side can return the live stream creation result to the broadcaster. This result can include the live stream address and the DRM encryption status bound to that address. Binding the DRM encryption status of each live stream to its address avoids the mis-association of encryption statuses caused by the traditional unified configuration at the live room level. The live stream address can be the storage address of the live stream on the streaming media platform. The DRM encryption status indicates whether DRM encryption is enabled. For example, the DRM encryption status can be identified by the `drm_enabled` field, where `drm_enabled=true` represents DRM encryption enabled, and `drm_enabled=false` represents DRM encryption disabled, facilitating subsequent identification and processing by both the broadcaster and the streaming media platform.

[0036] In some embodiments, the broadcaster can display the live stream address and DRM encryption status, providing an intuitive presentation of the live stream address and DRM encryption status. This allows the broadcaster to quickly identify the address and encryption configuration of each live stream, further reducing the risk of streaming operation errors due to unclear information.

[0037] Figure 3 This diagram illustrates the association between the live stream address and the DRM encryption status. (For example...) Figure 3 As shown, the broadcaster can display the live stream address and DRM encryption status in a card format in the management panel. The live stream address can be the full RTMP (Real-Time Messaging Protocol) address. The DRM encryption status can be distinguished by visual labels: a blue "DRM Encrypted Stream" label indicates that it is enabled, while a gray "Normal Live Stream" label indicates that it is disabled.

[0038] Step S104: Based on the live stream address, push the live stream information to the streaming media platform.

[0039] In this embodiment, the broadcaster can push live stream information to the streaming media platform based on the live stream address.

[0040] The broadcaster can configure the live stream address and audio / video parameters using a third-party streaming tool, and then click the "Start Streaming" button. The streaming tool can then push live stream information to the streaming media platform based on the live stream address, providing a clear basis for the platform's subsequent targeted processing (encryption or direct distribution). The live stream information can include regular live stream data and DRM encryption status. Regular live stream data can be encoded regular live stream audio and video frame data. The DRM encryption status indicates whether DRM encryption is enabled.

[0041] In some embodiments, the broadcaster's client can also display a service type selection interface; in response to detecting a service type selection operation based on the service type selection interface, it obtains service type selection information. The live stream creation request may also include service type selection information. By adopting a live stream address service identifier mechanism, each live stream is bound to a specific service type, resolving the issue of inconsistent live stream attribution and improving the accuracy of live stream distribution and platform management efficiency.

[0042] The broadcaster can access a service type selection interface. This interface can use a card-based layout. Each service type card can include a service identifier (biz_code), service type, etc. The mapping relationship between the service identifier and service type can be, for example, service identifier - service type. When the broadcaster clicks on a service type card, the card's border can turn blue and highlight it, displaying a selected checkmark icon.

[0043] The solution provided in this application achieves multi-dimensional technical effects by constructing a complete process on the broadcaster's end, including DRM encryption prompts, selection operations, request sending, result reception, and streaming. This is combined with binding the live stream address to the DRM encryption status, visual display, and a business type selection mechanism. Firstly, the DRM encryption prompt pop-up and selection operation allow broadcasters to clearly perceive the encryption function and accurately convey their configuration intentions, avoiding misconfigurations due to information opacity. Secondly, the stream address-encryption status binding design avoids the problem of misassociating encryption statuses in traditional live room configurations, and the intuitive card-style display on the management panel further reduces the risk of streaming operation errors. Thirdly, the binding of the business type selection interface with the biz_code solves the problem of confusing live stream ownership, improving distribution accuracy and platform management efficiency. Fourthly, the DRM encryption status is transmitted synchronously during streaming, providing a clear basis for subsequent targeted processing by the streaming media platform. Ultimately, this ensures accurate matching between broadcaster operations and DRM encryption, as well as business scenario requirements, supporting copyright protection and refined operation for high-value live streaming scenarios such as paid content distribution and course teaching.

[0044] Figure 4 A flowchart illustrating an embodiment of the live streaming creation method provided in this application is shown. The method includes at least the following processing steps: Step S401: Receive the live stream creation request sent by the broadcaster.

[0045] In this embodiment, the service terminal can receive a live stream creation request sent by the broadcaster terminal. The live stream creation request includes DRM encryption selection information.

[0046] After receiving the live stream creation request from the broadcaster, the business unit can perform identity verification, data integrity verification, and business validity verification. Once the verification is successful, the business unit can write the live stream creation request to the stream creation request log table for subsequent problem tracing and auditing.

[0047] Step S402: Determine the DRM encryption status based on the DRM encryption selection information.

[0048] In this embodiment, the business side can determine the DRM encryption status based on the DRM encryption selection information.

[0049] If the user chooses to enable DRM encryption, the DRM encryption status is "Enabled"; if the user chooses not to enable DRM encryption, the DRM encryption status is "Disabled". The DRM encryption selection information can indicate whether DRM encryption is enabled or disabled. The DRM encryption status can be used to identify whether DRM encryption is enabled. For example, the DRM encryption status can be identified by the `drm_enabled` field, where `drm_enabled=true` represents DRM encryption enabled, and `drm_enabled=false` represents DRM encryption disabled, facilitating subsequent identification and processing by the broadcaster and the streaming media platform.

[0050] Step S403: Generate the live stream address based on the DRM encryption status.

[0051] In this embodiment, the service provider can generate a live stream address based on the DRM encryption status.

[0052] In some embodiments, in response to determining that the DRM encryption status is enabled, encryption configuration information is generated, a live stream address is generated, and the encryption configuration information is bound to the live stream address; in response to determining that the DRM encryption status is disabled, a live stream address is generated. Differentiated operations are performed for encryption configuration generation and address binding, and address generation only, respectively, for DRM encryption enabled and DRM encryption disabled states. This adapts live stream address generation to encryption requirements, supporting both security management in encrypted scenarios and efficient generation in ordinary scenarios.

[0053] The encryption configuration information can include key and license server configuration information. When generating the key, mainstream encryption protocols supported by DRM can be used, including but not limited to HLS AES-128 (HTTP Live Streaming Advanced Encryption Standard-128), Widevine, and Fairplay. Based on the DRM encryption protocol type, the corresponding license server information, including but not limited to the license server address, authentication rules, and retry policies, can be obtained from the DRM configuration center.

[0054] Step S404: Bind the live stream address to the DRM encryption status to generate the live stream creation result.

[0055] In this embodiment, the service provider can bind the live stream address to the DRM encryption status to generate a live stream creation result.

[0056] The live stream creation result can include the live stream address and the DRM encryption status bound to that address. Binding the DRM encryption status of each live stream to its address avoids the mis-association of encryption statuses caused by the traditional unified configuration at the live room level. The live stream address can be the storage address of the live stream on the streaming media platform. The DRM encryption status can be used to indicate whether DRM encryption is enabled. For example, the DRM encryption status can be identified by the `drm_enabled` field, where `drm_enabled=true` represents DRM encryption enabled, and `drm_enabled=false` represents DRM encryption disabled, facilitating subsequent identification and processing by both the broadcaster and the streaming media platform.

[0057] Step S405: Send the live stream creation result to the broadcaster.

[0058] In this embodiment, the service terminal can send the live stream creation result to the broadcaster terminal.

[0059] In some embodiments, the live stream creation request may also include business type selection information. The business side can determine the business identifier corresponding to the selected business type based on the business type selection information; and write the business identifier and the live stream address into the live stream record table. By adopting the live stream address business identifier mechanism, each live stream is bound to a specific business type, solving the problem of confusing live stream attribution and improving the accuracy of live stream distribution and platform management efficiency.

[0060] In some embodiments, the service can receive a webhook callback request sent by the streaming media platform. The webhook callback request includes a live room identifier and a live stream address. It can query the DRM encryption status bound to the live stream address. In response to determining that the DRM encryption status is enabled, it can mark the DRM encryption flag of the live room identifier as enabled, thereby realizing the linkage between the push stream and the live room status.

[0061] The Webhook callback is triggered when the streaming media platform detects valid push data from the broadcaster. A dedicated Webhook receiving service is deployed on the business side to receive push event callbacks sent by the streaming media platform. When the streaming media platform detects push data from the broadcaster based on a specific stream address, it generates a network hook callback request. After receiving successful stream creation and DRM activation information, the business side can call the platform interface to mark the live stream's DRM encryption flag as enabled (drm_tag=1).

[0062] In some embodiments, in response to determining that the live stream identifier on the broadcaster's end is in the DRM encryption enabled whitelist, the business end can asynchronously tag the DRM encryption enabled flag of the live stream identifier to enable DRM encryption. By identifying whether the live stream identifier is in the DRM encryption enabled whitelist, the business end asynchronously tags eligible live stream identifiers to enable DRM encryption, enabling pre-setting and automated configuration of high-priority or specific live stream DRM encryption, improving the accuracy and efficiency of DRM encryption management. Pre-tagging is supported, allowing for the pre-marking of live streams that have not yet started broadcasting. Furthermore, multiple retries can be set to ensure effectiveness.

[0063] In some embodiments, in response to determining that tagging has failed or timed out, the business can send a normal live stream distribution instruction to the streaming media platform to distribute a backup stream, or send a live stream pause pull instruction to the viewer and display a pop-up message indicating that the live stream is being prepared, in order to avoid playback abnormalities caused by mismatch between the encrypted stream and the live stream tag.

[0064] In some embodiments, a request to obtain a live stream address is received from a viewer. This request includes a service identifier and user permission credentials. Upon determining that the user permission credentials have passed permission verification, the system queries the live stream record table based on the service identifier to obtain the live stream address and sends it to the viewer. Upon determining that the user permission credentials have failed permission verification, an insufficient permission message is sent to the viewer. By combining the service identifier and user permission credentials for permission verification, live stream addresses matching the service type are only sent to viewers with valid permissions, while insufficient permission messages are sent to viewers with invalid permissions. This achieves accurate distribution of live stream addresses and refined control of user permissions, preventing non-target users from accessing irrelevant live streams, and clearly providing feedback on permission status to improve user experience.

[0065] This application provides a live stream creation method that achieves multi-dimensional technical effects through a process of request verification, status determination, address generation, result return, and linked tagging: First, by verifying identity and business legitimacy, it ensures the compliance of the live stream creation entity and business type, avoiding illegal stream creation; Second, it dynamically determines the encryption status based on DRM selection information and business type, and generates a stream address by combining the key and authorization configuration, achieving strong binding between the stream address, encryption configuration, and business identifier, solving the problem of unclear business ownership of traditional stream addresses; Third, by using Webhook-linked tagging and whitelist pre-tags, it constructs a closed loop between pushing the stream and the live room status, ensuring that the live room tag and the stream encryption status are consistent when pulling the stream; Fourth, the fallback mechanism for tagging failure and audience permission verification not only ensure playback availability in abnormal scenarios, but also accurately control stream distribution permissions through business identifiers, improving copyright protection capabilities and platform management efficiency in high-value scenarios.

[0066] Figure 5 A flowchart illustrating an embodiment of the live streaming processing method provided in this application is shown. The method includes at least the following processing steps: Step S501: Receive live stream information pushed by the broadcaster based on the live stream address.

[0067] In this embodiment, the streaming media platform can receive live stream information pushed by the broadcaster based on the live stream address. The live stream information may include ordinary live stream data and DRM encryption status.

[0068] Streaming media platforms can deploy multi-regional push access nodes to receive live stream information pushed by broadcasters based on the live stream address. The access nodes can first verify the validity of the live stream address, and disconnect if it is invalid; then, based on the broadcaster's IP (Internet Protocol address) and node load, the live stream information is routed to the stream processing node through a consistent hashing algorithm, recording the access-processing-stream address routing relationship for easy subsequent streaming forwarding.

[0069] Step S502: In response to determining that the DRM encryption status is enabled, obtain the encryption configuration information bound to the live stream address from the business side.

[0070] In this embodiment, when the DRM encryption status is determined to be enabled, the streaming media platform can obtain the encryption configuration information bound to the live stream address from the service side.

[0071] The DRM encryption status in the live stream information is parsed. If `drm_enabled=true`, a request is sent to the DRM encryption configuration interface on the business side. After verifying the validity of the request, the business side returns the encryption configuration information. This encryption configuration information may include a key and authorization server configuration information. The key can be used for subsequent stream encryption, and the authorization server configuration information allows viewers to obtain decryption authorization.

[0072] Step S503: Encrypt the ordinary live stream data based on the encryption configuration information to generate encrypted live stream data.

[0073] In this embodiment, the streaming media platform can encrypt ordinary live stream data based on encryption configuration information to generate encrypted live stream data.

[0074] Encrypted live stream data can be generated by encrypting ordinary live stream data using the key in the encryption configuration information. Simultaneously, the streaming media platform can employ a dual-stream storage strategy, storing both ordinary and encrypted live stream data. The ordinary live stream data can serve as a backup stream, associated with the encrypted stream, and is in read-only mode by default, only distributed in exceptional circumstances.

[0075] In some embodiments, the streaming media platform can receive encrypted live stream retrieval requests sent by viewers based on the live stream address; and send encrypted live stream data and encrypted configuration information to viewers. By receiving encrypted live stream retrieval requests from viewers based on the live stream address and distributing encrypted live stream data and encrypted configuration information, the streaming media platform satisfies viewers' needs for retrieving and playing encrypted live streams.

[0076] After receiving a request to retrieve an encrypted live stream, the streaming media platform can verify the user's permissions and terminal compatibility with the business side. If the verification passes, it will send the encrypted live stream data and encryption configuration information to the viewer. If the verification fails, it will return a message indicating that the device does not support encryption or that the permissions are insufficient.

[0077] In some embodiments, in response to receiving a normal live stream distribution instruction from the service provider, the streaming media platform can send normal live stream data to the viewer. By responding to the normal live stream distribution instruction from the service provider and sending normal live stream data to the viewer, the streaming media platform provides a fallback playback solution for scenarios such as encrypted stream distribution anomalies, ensuring the continuity and availability of live streaming for the viewer.

[0078] In scenarios where tagging fails or times out, the business side can send a command to the streaming media platform to distribute the normal live stream. The streaming media platform can then update the stream distribution strategy for the corresponding live room, routing subsequent stream requests to the normal backup stream address. Simultaneously, the streaming media platform can also push a stream switching notification to viewers who have failed to retrieve the encrypted stream. Viewers can automatically switch to normal stream playback and receive a pop-up notification indicating that the encrypted service is temporarily unavailable and that the video quality has been switched to normal.

[0079] This application provides a live streaming processing method that achieves multi-dimensional technical effects through a process of stream reception, encryption configuration acquisition, stream encryption, and distribution: First, multi-regional access nodes and legality verification ensure the security of push streaming data and the stability of platform access, preventing illegal stream injection; Second, dynamic acquisition of encryption configuration based on DRM status and execution of stream encryption, combined with integrity verification, ensures the copyright security of high-value live streams and prevents illegal decryption; Third, dual-stream storage and abnormal stream switching provide a backup for encryption failure scenarios and ensure the real-time performance of encrypted streams through latency and resource monitoring, avoiding playback stuttering caused by encryption pressure; Fourth, permission and compatibility verification during stream pulling ensures that encrypted streams are only distributed to legally authorized viewers whose terminals support them, further strengthening copyright protection and improving user playback success rate.

[0080] Figure 6 A flowchart illustrating an embodiment of the live streaming pull method provided in this application is shown. The method includes at least the following processing steps: Step S601: Based on the live broadcast room identifier on the broadcaster's end, send a query request to the business end to read the digital rights management (DRM) encryption tag.

[0081] In this embodiment, the viewer can send a query request to the service terminal to read the Digital Rights Management (DRM) encrypted tag based on the live broadcast room identifier of the broadcaster.

[0082] After a viewer clicks on the live stream entry, the viewer's client can extract the live stream identifier from the live stream metadata, generate a DRM encryption tag query request, and send it to the business-side live stream DRM tag query interface. Additionally, the viewer's client can start a timeout timer; if there is no response after the timeout, it will automatically retry once. There is a preset number of failed retries, and by default, it is handled according to the normal stream retrieval logic.

[0083] Step S602: Receive the DRM encryption tag sent by the service terminal.

[0084] In this embodiment, the viewer can receive a DRM encryption tag sent by the service provider.

[0085] The business side can query the room tagging record table based on the live room identifier and return the DRM encrypted tag.

[0086] In step S603, in response to determining that the DRM encryption flag is enabled, an encrypted live stream pull request is sent to the streaming media platform based on the live stream address.

[0087] In this embodiment, when the DRM encryption flag is determined to be enabled, the viewer can send an encrypted live stream retrieval request to the streaming media platform based on the live stream address.

[0088] If the viewer confirms drm_tag=1, a terminal DRM compatibility check can be performed first to determine if the encryption protocol is supported. If not, a fallback is triggered, and a normal stream is retrieved; if supported, a request to obtain the live stream address is sent to the business side. After the business side verifies the permissions, it can return the live stream address. The viewer can then generate an encrypted live stream retrieval request and send it to the streaming media platform.

[0089] Step S604: Receive encrypted live stream data and encrypted configuration information sent by the streaming media platform.

[0090] In this embodiment, the viewer can receive encrypted live stream data and encrypted configuration information sent by the streaming media platform.

[0091] Viewers can parse the encrypted configuration information, initialize the corresponding DRM playback component, and cache the encrypted live stream data in a local playback buffer to prevent buffering caused by network fluctuations. The encrypted configuration information can include a key and authorization server configuration information. The key can be obtained through a subsequent authorization process, and the authorization server configuration information can be used to initiate authorization requests.

[0092] Step S605: Decrypt the encrypted live stream data based on the configuration information to obtain the decrypted live stream data.

[0093] In this embodiment, the viewer can decrypt the encrypted live stream data based on the configuration information to obtain the decrypted live stream data.

[0094] The DRM playback component on the viewer's end can perform a decryption process on the encrypted live stream data based on the encryption configuration information to obtain the decrypted live stream data. Specifically, the key in the encryption configuration information can be used to decrypt the encrypted live stream data.

[0095] Viewers can send the decrypted live stream data to the system playback kernel for playback, providing at least one of the following control functions: basic controls (such as play, pause, progress drag, volume adjustment, full-screen switching, etc.); DRM-specific controls (such as displaying a screen recording prohibition prompt); exception handling (such as pop-up prompts for decryption failure, automatic retry to obtain authorization, and triggering downgrade to pull the normal stream if retry fails).

[0096] In some embodiments, the viewer can send a live stream address acquisition request to the service provider, the live stream address acquisition request including a service identifier; and receive the live stream address sent by the service provider to solve the problem of the viewer acquiring a non-target stream.

[0097] In some embodiments, the viewer can send an authorization request to the authorization server based on the authorization server configuration information; retry sending the authorization request if no authorization credential is received from the authorization server; send a normal live stream fetch request to the streaming media platform if the authorization credential is not obtained after a preset number of retries; receive normal live stream data sent by the streaming media platform; and play the normal live stream data. By initiating an authorization request based on the authorization server configuration information, retrying when no authorization credential is received, and switching to fetching and playing the normal live stream after a preset number of retries, the viewer ensures that the viewer can still watch the live stream normally even if the authorization of the encrypted live stream fails, thus improving the stability of live streaming and the user experience.

[0098] For example, the viewer sends an authorization request to the authorization server. If no authorization credential is received within 3 seconds, the credential parsing is considered to have failed. In this case, a retry strategy of 3 times at 5-second intervals is adopted. If the retry still fails after 3 times, a normal live stream pull request is sent to the streaming media platform. After receiving and sending the normal stream data, the viewer can close the DRM component and switch to the normal playback kernel.

[0099] This application provides a live streaming pull method, which achieves multi-dimensional technical effects through a process of tag query, compatibility detection, pull decryption, and playback control: First, before pulling the stream, the room's DRM tag is queried and terminal compatibility is checked to avoid pushing encrypted streams to terminals that do not support DRM, thus improving the playback success rate. Second, based on the authorization server configuration, the key is obtained for decryption, and combined with data integrity verification, to ensure that the encrypted stream can only be viewed by legitimate users, strengthening the copyright protection of high-value content. Third, playback control and anomaly handling provide both a DRM-specific screen recording disabling function and authorization retry and downgraded pull to ensure playback availability in scenarios such as network fluctuations and authorization expiration. Fourth, the acquisition of the stream address associated with the service identifier accurately matches the stream of the service type required by the audience, solving the problem of traditional pull interfaces returning incorrect stream addresses, and improving the user viewing experience and the accuracy of platform stream distribution.

[0100] Figure 7 A schematic diagram of an embodiment of the live streaming device provided in this application is shown. This device embodiment is similar to... Figure 1 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0101] like Figure 7As shown, the live streaming device 700 of this embodiment may include: a first display module 701, a first sending module 702, a first receiving module 703, and a second sending module 704. The first display module 701 is configured to display Digital Rights Management (DRM) encryption prompt information in response to detecting a live stream creation operation; the first sending module 702 is configured to send a live stream creation request to the service terminal in response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, the live stream creation request including DRM encryption selection information; the first receiving module 703 is configured to receive a live stream creation result sent by the service terminal, the live stream creation result including a live stream address and a DRM encryption status bound to the live stream address; the second sending module 704 is configured to push live stream information to the streaming media platform based on the live stream address, the live stream information including ordinary live stream data and DRM encryption status.

[0102] In this embodiment, the specific processing of the first display module 701, the first sending module 702, the first receiving module 703, and the second sending module 704 in the live streaming device 700, and the resulting technical effects, can be found in the following references: Figure 1 The relevant descriptions of steps S101-S104 in the corresponding embodiments will not be repeated here.

[0103] In some optional implementations of this embodiment, the live streaming device 700 further includes a second display module configured to display the live stream address and DRM encryption status.

[0104] In some optional implementations of this embodiment, the live streaming device 700 further includes: a third display module configured to display a service type selection interface; and an acquisition module configured to acquire service type selection information in response to detecting a service type selection operation based on the service type selection interface, wherein the live stream creation request also includes the service type selection information.

[0105] Figure 8 A schematic diagram of a structure of an embodiment of the live streaming creation apparatus provided in this application is shown. This apparatus embodiment is similar to... Figure 4 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0106] like Figure 8As shown, the live stream creation device 800 of this embodiment may include: a first receiving module 801, a first determining module 802, a first generating module 803, a second generating module 804, and a first sending module 805. The first receiving module 801 is configured to receive a live stream creation request sent by the broadcaster, the request including Digital Rights Management (DRM) encryption selection information; the first determining module 802 is configured to determine the DRM encryption status based on the DRM encryption selection information; the first generating module 803 is configured to generate a live stream address based on the DRM encryption status; the second generating module 804 is configured to bind the live stream address to the DRM encryption status to generate a live stream creation result; and the first sending module 805 is configured to send the live stream creation result to the broadcaster.

[0107] In this embodiment, the specific processing of the first receiving module 801, the first determining module 802, the first generating module 803, the second generating module 804, and the first sending module 805 in the live streaming creation device 800, and the resulting technical effects, can be found in the following references: Figure 4 The relevant descriptions of steps S401-S405 in the corresponding embodiments will not be repeated here.

[0108] In some optional implementations of this embodiment, the first generation module 803 is further configured to: generate encryption configuration information in response to determining that the DRM encryption status is enabled, the encryption configuration information including a key and authorization server configuration information; generate a live stream address, and bind the encryption configuration information to the live stream address.

[0109] In some optional implementations of this embodiment, the first generation module 803 is further configured to: generate a live stream address in response to determining that the DRM encryption status is disabled.

[0110] In some optional implementations of this embodiment, the live stream creation request further includes service type selection information; and the live stream creation device 800 further includes: a second determining module, configured to determine the service identifier corresponding to the selected service type based on the service type selection information; and a writing module, configured to write the service identifier and the live stream address into the live stream record table.

[0111] In some optional implementations of this embodiment, the live streaming creation device 800 further includes: a second receiving module configured to receive a network hook callback request sent by a streaming media platform, the network hook callback request including a live streaming room identifier and a live streaming address; a query module configured to query the DRM encryption status bound to the live streaming address; and a first tagging module configured to, in response to determining that the DRM encryption status is enabled, tag the DRM encryption flag of the live streaming room identifier as enabled.

[0112] In some optional implementations of this embodiment, the live streaming creation device 800 further includes: a second tagging module, configured to asynchronously tag the DRM encryption enabled flag of the live streaming room identifier as enabled in response to determining that the live streaming room identifier of the broadcaster is in the DRM encryption enabled whitelist.

[0113] In some optional implementations of this embodiment, the live streaming creation device 800 further includes: a second sending module, configured to send a normal live streaming delivery instruction to the streaming media platform or a live streaming pause pull instruction to the viewer in response to determining that tagging has failed or timed out.

[0114] In some optional implementations of this embodiment, the live streaming creation device 800 further includes: a third receiving module configured to receive a live stream address acquisition request sent by a viewer, the live stream address acquisition request including a service identifier and a user permission credential; a third sending module configured to, in response to determining that the user permission credential has passed permission verification, query the live stream record table based on the service identifier to obtain the live stream address, and send the live stream address to the viewer; and a fourth sending module configured to, in response to determining that the user permission credential has failed permission verification, send an insufficient permission prompt message to the viewer.

[0115] Figure 9 A schematic diagram of a structure of an embodiment of the live streaming processing apparatus provided in this application is shown. This apparatus embodiment is similar to... Figure 5 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0116] like Figure 9 As shown, the live streaming processing device 900 of this embodiment may include: a first receiving module 901, an acquisition module 902, and an encryption module 903. The first receiving module 901 is configured to receive live streaming information pushed by the broadcaster based on the live streaming address, the live streaming information including ordinary live streaming data and DRM encryption status; the acquisition module 902 is configured to, in response to determining that the DRM encryption status is enabled, acquire encryption configuration information bound to the live streaming address from the service terminal; the encryption module 903 is configured to encrypt the ordinary live streaming data based on the encryption configuration information to generate encrypted live streaming data.

[0117] In this embodiment, the specific processing of the first receiving module 901, the acquisition module 902, and the encryption module 903 in the live streaming processing device 900, and the resulting technical effects, can be found in reference to [reference needed]. Figure 5 The relevant descriptions of steps S501-S503 in the corresponding embodiments will not be repeated here.

[0118] In some optional implementations of this embodiment, the live streaming processing device 900 further includes: a second receiving module configured to receive an encrypted live stream retrieval request sent by the viewer based on the live stream address; and a first sending module configured to send encrypted live stream data and encrypted configuration information to the viewer.

[0119] In some optional implementations of this embodiment, the live streaming processing device 900 further includes: a second sending module, configured to send ordinary live streaming data to the viewer in response to receiving an ordinary live streaming transmission instruction sent by the service terminal.

[0120] Figure 10 A schematic diagram of one embodiment of the live streaming device provided in this application is shown. This device embodiment is similar to... Figure 6 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0121] like Figure 10 As shown, the live streaming device 1000 of this embodiment may include: a first sending module 1001, a first receiving module 1002, a second sending module 1003, a second receiving module 1004, and a decryption module 1005. The first sending module 1001 is configured to send a query request to the service terminal to read the Digital Rights Management (DRM) encryption tag based on the live room identifier of the broadcaster; the first receiving module 1002 is configured to receive the DRM encryption tag sent by the service terminal; the second sending module 1003 is configured to, in response to determining that the DRM encryption tag is enabled, send an encrypted live stream retrieval request to the streaming media platform based on the live stream address; the second receiving module 1004 is configured to receive encrypted live stream data and encryption configuration information sent by the streaming media platform; and the decryption module 1005 is configured to decrypt the encrypted live stream data based on the configuration information to obtain decrypted live stream data.

[0122] In this embodiment, the specific processing of the first sending module 1001, the first receiving module 1002, the second sending module 1003, the second receiving module 1004, and the decryption module 1005 in the live streaming creation device 1000, and the resulting technical effects, can be found in the following references: Figure 6 The relevant descriptions of steps S601-S605 in the corresponding embodiments will not be repeated here.

[0123] In some optional implementations of this embodiment, the live streaming creation device 1000 further includes: a third sending module configured to send a live stream address acquisition request to the service terminal, the live stream address acquisition request including a service identifier; and a third receiving module configured to receive the live stream address sent by the service terminal.

[0124] In some optional implementations of this embodiment, the live streaming creation device 1000 further includes: a fourth sending module configured to send an authorization request to an authorization server based on authorization server configuration information; a fifth sending module configured to retry sending the authorization request in response to not receiving an authorization credential returned by the authorization server; a sixth sending module configured to send a normal live stream retrieval request to the streaming media platform in response to failing to obtain an authorization credential after retries of a preset number of times; a fourth receiving module configured to receive normal live stream data sent by the streaming media platform; and a playback module configured to play the normal live stream data.

[0125] Figure 11 A schematic diagram of an embodiment of the live streaming management system provided in this application is shown. The live streaming management system 1100 includes a broadcaster terminal 1101, a service terminal 1102, a streaming media platform 1103, and a viewer terminal 1104.

[0126] The broadcaster client 1101 is used to respond to the detection of a live stream creation operation by displaying a Digital Rights Management (DRM) encryption prompt; in response to the detection of a DRM encryption selection operation based on the DRM encryption prompt, it sends a live stream creation request to the business client, which includes DRM encryption selection information; it receives the live stream creation result sent by the business client, which includes the live stream address and the DRM encryption status bound to the live stream address; and based on the live stream address, it pushes live stream information to the streaming media platform, which includes ordinary live stream data and DRM encryption status.

[0127] In this embodiment, the specific operation of the broadcaster terminal 1101 can be referred to Figure 1 The relevant descriptions of steps S101-S104 in the corresponding embodiments will not be repeated here.

[0128] Business unit 1102 is used to receive a live stream creation request sent by the broadcaster. The live stream creation request includes Digital Rights Management (DRM) encryption selection information; determine the DRM encryption status based on the DRM encryption selection information; generate a live stream address based on the DRM encryption status; bind the live stream address with the DRM encryption status to generate a live stream creation result; and send the live stream creation result to the broadcaster.

[0129] In this embodiment, the specific operation of the service terminal 1102 can be referred to Figure 4 The relevant descriptions of steps S401-S405 in the corresponding embodiments will not be repeated here.

[0130] The streaming media platform 1103 is used to receive live stream information pushed by the broadcaster based on the live stream address. The live stream information includes ordinary live stream data and DRM encryption status. In response to determining that the DRM encryption status is enabled, it obtains the encryption configuration information bound to the live stream address from the business side. Based on the encryption configuration information, it encrypts the ordinary live stream data to generate encrypted live stream data.

[0131] In this embodiment, the specific operation of the streaming media platform 1103 can be referred to Figure 5 The relevant descriptions of steps S501-S503 in the corresponding embodiments will not be repeated here.

[0132] Viewer terminal 1104 is used to send a query request to read the Digital Rights Management (DRM) encryption tag to the business terminal based on the live room identifier of the broadcaster terminal; receive the DRM encryption tag sent by the business terminal; in response to determining that the DRM encryption tag is enabled, send an encrypted live stream pull request to the streaming media platform based on the live stream address; receive encrypted live stream data and encryption configuration information sent by the streaming media platform; and decrypt the encrypted live stream data based on the configuration information to obtain decrypted live stream data.

[0133] In this embodiment, the specific operation of the viewer terminal 1104 can be referred to Figure 6 The relevant descriptions of steps S601-S605 in the corresponding embodiments will not be repeated here.

[0134] Based on the same inventive concept, this application also provides an electronic device. The method corresponding to the electronic device can be the live streaming push, creation, processing, and pull methods in the foregoing embodiments, and its problem-solving principle is similar to that method. The electronic device provided in this application includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the methods and / or technical solutions of the foregoing embodiments of this application.

[0135] The electronic device can be a user device, or a device formed by integrating user devices and network devices through a network, or it can be an application running on the aforementioned devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and wristbands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server sets, or cloud computing-based computer sets, and can be used to implement some processing functions when setting an alarm clock. Here, the cloud consists of a large number of hosts or network servers based on cloud computing. Cloud computing is a type of distributed computing, consisting of a virtual computer composed of a group of loosely coupled computer sets.

[0136] Figure 12 The diagram illustrates the structure of an apparatus suitable for implementing the methods and / or technical solutions in the embodiments of this application. The apparatus 1200 includes a Central Processing Unit (CPU) 1201, which can perform various appropriate actions and processes based on a program stored in a Read Only Memory (ROM) 1202 or a program loaded from a storage portion 1208 into a Random Access Memory (RAM) 1203. The RAM 1203 also stores various programs and data required for system operation. The CPU 1201, ROM 1202, and RAM 1203 are interconnected via a bus 1204. An Input / Output (I / O) interface 1205 is also connected to the bus 1204.

[0137] The following components are connected to I / O interface 1205: an input section 1206 including a keyboard, mouse, touchscreen, microphone, infrared sensor, etc.; an output section 1207 including a cathode ray tube (CRT), liquid crystal display (LCD), LED display, OLED display, etc., and speakers, etc.; a storage section 1208 including one or more computer-readable media such as hard disk, optical disk, magnetic disk, semiconductor memory, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 1209 performs communication processing via a network such as the Internet.

[0138] In particular, the methods and / or embodiments in this application can be implemented as computer software programs. For example, the embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. When the computer program is executed by the central processing unit (CPU) 1201, it performs the functions defined in the methods of this application.

[0139] Another embodiment of this application provides a computer-readable storage medium having computer program instructions stored thereon, which can be executed by a processor to implement the methods and / or technical solutions of any one or more embodiments of this application described above.

[0140] Specifically, this embodiment may employ any combination of one or more computer-readable media. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device.

[0141] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.

[0142] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0143] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0144] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-specific system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0145] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0146] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, 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. For example, multiple units or page components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.

[0147] 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.

[0148] Furthermore, 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 in a combination of hardware and software functional units.

[0149] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in 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.

[0150] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

[0151] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in a device claim may also be implemented by a single unit or device through software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any specific order.

Claims

1. A live streaming method, applied to the broadcaster's end, comprising: In response to the detection of a live stream creation operation, a Digital Rights Management (DRM) encryption prompt message is displayed; In response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, a live stream creation request is sent to the service terminal, the live stream creation request including the DRM encryption selection information; Receive the live stream creation result sent by the service terminal, the live stream creation result including the live stream address and the DRM encryption status bound to the live stream address; Based on the live stream address, live stream information is pushed to the streaming media platform. The live stream information includes ordinary live stream data and the DRM encryption status.

2. The method according to claim 1, wherein, The method further includes: Display the live stream address and the DRM encryption status.

3. The method according to claim 1, wherein, The method further includes: Display the business type selection interface; In response to detecting a business type selection operation based on the business type selection interface, the service type selection information is obtained, and the live stream creation request also includes the service type selection information.

4. A live stream creation method, applied to the business side, including: Receive a live stream creation request sent by the broadcaster, wherein the live stream creation request includes Digital Rights Management (DRM) encryption selection information; Based on the DRM encryption selection information, the DRM encryption status is determined; Based on the DRM encryption status, a live stream address is generated; Bind the live stream address to the DRM encryption status to generate a live stream creation result; The live stream creation result is sent to the broadcaster's terminal.

5. The method according to claim 4, wherein, The process of generating a live stream address based on the DRM encryption state includes: In response to determining that the DRM encryption status is enabled, encryption configuration information is generated, which includes a key and authorization server configuration information; Generate the live stream address and bind the encryption configuration information to the live stream address.

6. The method according to claim 4, wherein, The process of generating a live stream address based on the DRM encryption state includes: In response to determining that the DRM encryption status is disabled, the live stream address is generated.

7. The method according to claim 4, wherein, The live stream creation request also includes business type selection information; as well as The method further includes: Based on the business type selection information, determine the business identifier corresponding to the selected business type; Write the service identifier and the live stream address into the live stream record table.

8. The method according to claim 5, wherein, The method further includes: Receive a network hook callback request sent by the streaming media platform, wherein the network hook callback request includes the live room identifier and the live stream address; Query the DRM encryption status bound to the live stream address; In response to determining that the DRM encryption status is enabled, the DRM encryption flag of the live room identifier is marked as enabled.

9. The method according to claim 8, wherein, The method further includes: In response to determining that the live stream identifier of the broadcaster is in the DRM encryption enabled whitelist, the DRM encryption enabled flag of the live stream identifier is asynchronously marked as enabled for DRM encryption.

10. The method according to claim 8, wherein, The method further includes: In response to a determination that the tagging has failed or timed out, a normal live stream delivery instruction is sent to the streaming media platform, or a live stream pause and pull instruction is sent to the viewer.

11. The method according to claim 7, wherein, The method further includes: Receive a request to obtain the live stream address sent by the viewer, wherein the request to obtain the live stream address includes the service identifier and the user permission credential; In response to determining that the user permission credential has passed the permission verification, the system queries the live stream record table based on the service identifier to obtain the live stream address and sends the live stream address to the viewer. In response to determining that the user's permission credentials have failed permission verification, an insufficient permission prompt message is sent to the viewer's terminal.

12. A live streaming processing method, applied to a streaming media platform, comprising: Receive live stream information pushed by the broadcaster based on the live stream address, the live stream information including ordinary live stream data and DRM encryption status; In response to determining that the DRM encryption status is enabled, the encryption configuration information bound to the live stream address is obtained from the business side; The ordinary live stream data is encrypted based on the encryption configuration information to generate encrypted live stream data.

13. The method according to claim 12, wherein, The method further includes: Receive encrypted live stream retrieval requests sent by viewers based on the live stream address; The encrypted live stream data and the encryption configuration information are sent to the viewer's terminal.

14. The method according to claim 12, wherein, The method further includes: In response to receiving a normal live stream distribution instruction from the service terminal, the normal live stream data is sent to the viewer terminal.

15. A live streaming pull method, applied to the viewer's end, comprising: Based on the live broadcast room identifier on the broadcaster's end, a query request to read the Digital Rights Management (DRM) encrypted tag is sent to the business end; Receive the DRM encryption tag sent by the service terminal; In response to determining that the DRM encryption flag is enabled for DRM encryption, an encrypted live stream retrieval request is sent to the streaming media platform based on the live stream address; Receive encrypted live stream data and encrypted configuration information sent by the streaming media platform; The encrypted live stream data is decrypted based on the configuration information to obtain decrypted live stream data.

16. The method according to claim 15, wherein, The method further includes: Send a live stream address acquisition request to the business terminal, wherein the live stream address acquisition request includes a business identifier; Receive the live stream address sent by the service terminal.

17. The method according to claim 15, wherein, The method further includes: Based on the authorization server configuration information, an authorization request is sent to the authorization server; If no authorization credential is received from the authorization server, the authorization request will be resent. If the authorization credential is not obtained after a preset number of retries, a normal live stream fetch request is sent to the streaming media platform; Receive ordinary live stream data sent by the streaming media platform; Play the aforementioned regular live stream data.

18. A live streaming device, installed at the broadcaster's end, comprising: The first display module is configured to display a Digital Rights Management (DRM) encryption prompt message in response to the detection of a live stream creation operation. The first sending module is configured to send a live stream creation request to the service terminal in response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, wherein the live stream creation request includes the DRM encryption selection information. The first receiving module is configured to receive the live stream creation result sent by the service terminal, the live stream creation result including the live stream address and the DRM encryption status bound to the live stream address; The second sending module is configured to push live stream information to the streaming media platform based on the live stream address. The live stream information includes ordinary live stream data and the DRM encryption status.

19. A live streaming creation device, installed on a business terminal, comprising: The first receiving module is configured to receive a live stream creation request sent by the broadcaster, the live stream creation request including Digital Rights Management (DRM) encryption selection information; The first determining module is configured to determine the DRM encryption status based on the DRM encryption selection information; The first generation module is configured to generate a live stream address based on the DRM encryption state; The second generation module is configured to bind the live stream address to the DRM encryption state and generate a live stream creation result. The first sending module is configured to send the live stream creation result to the broadcaster's terminal.

20. A live streaming processing device, installed on a streaming media platform, comprising: The first receiving module is configured to receive live stream information pushed by the broadcaster based on the live stream address. The live stream information includes ordinary live stream data and DRM encryption status. The acquisition module is configured to, in response to determining that the DRM encryption status is enabled, acquire encryption configuration information bound to the live stream address from the business side; The encryption module is configured to encrypt the ordinary live stream data based on the encryption configuration information to generate encrypted live stream data.

21. A live streaming pull device, installed at the viewer's end, comprising: The first sending module is configured to send a query request to the business side to read the digital rights management (DRM) encrypted tag based on the live room identifier on the broadcaster's end; The first receiving module is configured to receive the DRM encryption token sent by the service terminal; The second sending module is configured to send an encrypted live stream fetch request to the streaming media platform based on the live stream address in response to determining that the DRM encryption flag is enabled for DRM encryption. The second receiving module is configured to receive encrypted live stream data and encryption configuration information sent by the streaming media platform, wherein the encryption configuration information includes a key and authorization server configuration information; The decryption module is configured to decrypt the encrypted live stream data based on the configuration information to obtain decrypted live stream data.

22. A live streaming management system, comprising: The broadcaster's end, the business end, the streaming media platform, and the viewer's end; The broadcaster's terminal is used to display a Digital Rights Management (DRM) encryption prompt message in response to the detection of a live stream creation operation; In response to detecting a DRM encryption selection operation based on the DRM encryption prompt information, a live stream creation request is sent to the service terminal, the live stream creation request including the DRM encryption selection information; Receive the live stream creation result sent by the service terminal, the live stream creation result including the live stream address and the DRM encryption status bound to the live stream address; Based on the live stream address, live stream information is pushed to the streaming media platform. The live stream information includes ordinary live stream data and the DRM encryption status. The business terminal is used to receive a live stream creation request sent by the broadcaster terminal, and the live stream creation request includes Digital Rights Management (DRM) encryption selection information; Based on the DRM encryption selection information, the DRM encryption status is determined; Based on the DRM encryption status, a live stream address is generated; Bind the live stream address to the DRM encryption status to generate a live stream creation result; Send the live stream creation result to the broadcaster's terminal; The streaming media platform is used to receive live stream information pushed by the broadcaster based on the live stream address. The live stream information includes ordinary live stream data and DRM encryption status. In response to determining that the DRM encryption status is enabled, the system obtains encryption configuration information bound to the live stream address from the service terminal. The encryption configuration information includes a key and authorization server configuration information. Based on the encryption configuration information, the system encrypts the ordinary live stream data to generate encrypted live stream data. The viewer's terminal is used to send a query request to read the Digital Rights Management (DRM) encrypted tag to the business terminal based on the live room identifier of the broadcaster's terminal; Receive the DRM encryption tag sent by the service terminal; In response to determining that the DRM encryption flag is enabled for DRM encryption, an encrypted live stream retrieval request is sent to the streaming media platform based on the live stream address; The system receives encrypted live stream data and encryption configuration information sent by the streaming media platform, the encryption configuration information including a key and authorization server configuration information; decrypts the encrypted live stream data based on the configuration information to obtain decrypted live stream data; and plays the decrypted live stream data.

23. An electronic device, the electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-17.

24. A computer-readable medium having stored thereon computer program instructions that can be executed by a processor to implement the method as described in any one of claims 1-17.

25. A computer program product comprising a computer program that, when executed by a processor, implements the method as described in any one of claims 1-17.

Images