Live streaming processing method, stream session identification processing method, device and equipment

Abstract

Embodiments of the present application provide a live streaming processing method, a stream session identifier processing method, an apparatus, a computer device, a computer readable storage medium, and a computer program product, and belong to the technical field of network live streaming. The live streaming processing method comprises: in response to a push streaming request carrying an external stream identifier, determining a stream session identifier corresponding to the external stream identifier through authentication; configuring an internal processing identifier of a live streaming corresponding to the push streaming request as the stream session identifier; and generating or forwarding stream data corresponding to the live streaming based on the stream session identifier. The external stream identifier is used for user side push streaming authentication, and the stream session identifier is used as an internal processing identifier of the live streaming in an edge computing node and a downstream processing link thereof. Embodiments of the present application can decouple the identifier used for user side push streaming authentication and the identifier used for the internal processing link, thereby reducing the risk of reuse or cross-game misuse of the external stream identifier after entering the internal processing link.

Description

Technical Field

[0001] This application relates to the field of network live streaming technology, and in particular to a live stream processing method, a stream session identifier processing method, an apparatus, a computer device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] In live streaming scenarios, the streaming end typically needs to access the stream based on a live stream identifier. Edge nodes, scheduling systems, recording systems, screenshot systems, transcoding systems, and content delivery networks in the live streaming service chain also need to access, process, distribute, or manage the live stream based on corresponding identifiers. When the live stream identifier flows between different systems, it may serve as both a user-side stream authentication identifier and a stream data identifier within the internal processing chain. In some live streaming systems, the external stream identifier used for user-side stream authentication may be permanently bound to the user account or the live stream entity and reused across multiple live stream sessions. If this external stream identifier continues from the user-side access chain into internal processing chains such as recording, screenshotting, transcoding, or content delivery networks, the internal processing chains may struggle to distinguish between different live stream sessions based on the identifier dimension. This could also lead to instability in internal stream data identification during reconnection, stream node switching, or session changes.

[0003] It should be noted that the above content is not necessarily prior art, nor is it intended to limit the scope of patent protection of this application. Summary of the Invention

[0004] This application provides a live stream processing method, a stream session identifier processing method, an apparatus, a computer device, a computer-readable storage medium, and a computer program product to solve or alleviate one or more of the technical problems mentioned above.

[0005] One aspect of this application provides a live stream processing method applied to an edge computing node, the method comprising: In response to a push request carrying an external stream identifier, authentication is performed to determine the stream session identifier corresponding to the external stream identifier; Configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier; Based on the stream session identifier, generate or forward the stream data corresponding to the live stream; The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

[0006] Optionally, determining the stream session identifier corresponding to the external stream identifier includes: Using the external stream identifier as the query key, query the mapping cache, which is used to store the mapping relationship between the external stream identifier and the stream session identifier; If a historical stream session identifier corresponding to the external stream identifier exists in the mapping cache, obtain the status information corresponding to the historical stream session identifier; When the status information indicates that the historical stream session identifier is in a reconnection waiting state, the historical stream session identifier is determined as the stream session identifier corresponding to the external stream identifier.

[0007] Optionally, obtaining the status information corresponding to the historical stream session identifier includes: Send a status query request for the historical stream session identifier to the stream name management center; Receive the status information returned by the stream name management center; Correspondingly, after determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier, the method further includes: Generate a reconnection event to characterize this push stream as a reconnection push stream; Send the reconnection event to the stream name management center.

[0008] Optionally, determining the stream session identifier corresponding to the external stream identifier further includes: If there is no historical stream session identifier corresponding to the external stream identifier in the mapping cache, or if the historical stream session identifier is not in a reconnection waiting state, a stream session identifier request is sent to the stream name management center. Receive the new flow session identifier returned by the flow name management center based on the flow session identifier request; The new stream session identifier is determined to be the stream session identifier corresponding to the external stream identifier; Write the mapping relationship between the external stream identifier and the new stream session identifier into the mapping cache.

[0009] Optionally, after sending a stream session identifier request to the stream name management center, the process also includes: If the new stream session identifier is not received within the preset timeout threshold, the stream session identifier request is resent; If the new stream session identifier is not received after resending the stream session identifier request, the push request is rejected and an alarm message is output.

[0010] Optionally, the mapping cache is a distributed cache cluster; Correspondingly, using the external stream identifier as the query key, querying the mapping cache includes: In the event that the push node corresponding to the live stream is switched, the distributed cache cluster is queried using the external stream identifier as the query key to obtain the historical stream session identifier corresponding to the external stream identifier.

[0011] Optionally, generating or forwarding stream data corresponding to the live stream based on the stream session identifier includes: Generate the stream data corresponding to the live stream based on the stream session identifier; The stream data carrying the stream session identifier is forwarded to the downstream processing system; The downstream processing system includes at least one of a recording system, a screenshot system, and a transcoding system.

[0012] Optionally, generating or forwarding the stream data corresponding to the live stream based on the stream session identifier includes: A distribution link establishment notification is sent to the content delivery network, the distribution link establishment notification carrying the stream session identifier, so that the content delivery network establishes a distribution link for the live stream based on the stream session identifier.

[0013] Optionally, after generating or forwarding the stream data corresponding to the live stream based on the stream session identifier, the method further includes: Generate a mapped state record containing the external stream identifier, the stream session identifier, the session identifier, and state information; Send the mapping status record to the stream name management center.

[0014] Optionally, the method further includes: If an interruption is detected in the live stream, an interruption event is generated; Send the interruption event to the stream name management center so that the state of the stream session identifier is updated based on the interruption event; The interruption events include active stop events that represent active shutdown, or network interruption events that represent network fluctuations.

[0015] Optionally, determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier includes: When the historical stream session identifier is in a reconnection waiting state and the current time is within a preset reconnection waiting time window, the historical stream session identifier is determined as the stream session identifier corresponding to the external stream identifier.

[0016] Another aspect of this application provides a method for processing a stream session identifier, applied to a stream name management center, the method comprising: Receive a stream session identifier request sent by an edge computing node, wherein the stream session identifier request is associated with an external stream identifier; Generate a stream session identifier based on the external stream identifier; Establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information; Send the streaming session identifier to the edge computing node; Based on the status events reported by the edge computing node, update the status information corresponding to the stream session identifier.

[0017] Optionally, a mapping relationship is established and stored between the external stream identifier, the stream session identifier, the session identifier, and the status information, including: In the case of generating the stream session identifier, the mapping relationship is established, and the status information is set to the generating state; Correspondingly, after sending the streaming session identifier to the edge computing node, the method further includes: If it is determined that the stream session identifier has been successfully sent, the status information is updated from the generating state to the active state.

[0018] Optionally, generating a stream session identifier based on the external stream identifier includes: Obtain the external stream identifier, current timestamp, and system internal key; Generate a verification code based on the external stream identifier, the current timestamp, and the system internal key; The stream session identifier is generated based on the verification code and the session number.

[0019] Optionally, a verification code is generated based on the external stream identifier, the current timestamp, and the system internal key, including: The external stream identifier, the current timestamp, and the system internal key are concatenated according to a preset format to obtain the data to be processed; The data to be processed is hashed using the HMAC-SHA256 algorithm to obtain digest data. The first 16 hexadecimal characters are extracted from the digest data to obtain the check code.

[0020] Optionally, the stream session identifier is generated based on the checksum and session number, including: Obtain the globally incrementing field number through atomic operations; Obtain the external flow identifier prefix corresponding to the external flow identifier; The external stream identifier prefix, the session number, and the checksum are combined to obtain the stream session identifier.

[0021] Optionally, generating a stream session identifier based on the external stream identifier includes: The stream session identifier is generated based on at least one of a random identifier generation algorithm, a snowflake algorithm, or a decentralized identifier generation algorithm.

[0022] Optionally, the status information includes a generation status, an active status, a reconnection waiting status, a failed status, and a recycling status.

[0023] Optionally, based on the status events reported by the edge computing node, the status information corresponding to the stream session identifier is updated, including: Upon receiving a network interruption event reported by the edge computing node, the status information corresponding to the stream session identifier is updated from active to reconnection waiting state. Keep the content delivery network distribution link corresponding to the stream session identifier in an active state.

[0024] Optionally, after updating the status information corresponding to the stream session identifier from an active state to a reconnection waiting state, the method further includes: If a reconnection event corresponding to the stream session identifier is received within the preset reconnection waiting time window, the status information corresponding to the stream session identifier is updated from the reconnection waiting state to the active state. The reconnection event is used to instruct the edge computing node to reuse the stream session identifier in the reconnection push stream.

[0025] Optionally, after updating the status information corresponding to the stream session identifier from an active state to a reconnection waiting state, the method further includes: If no reconnection event corresponding to the stream session identifier is received within the preset reconnection waiting time window, the status information corresponding to the stream session identifier will be updated from the reconnection waiting state to the failure state. Alternatively, upon receiving an active stop event reported by the edge computing node, the status information corresponding to the stream session identifier is updated to an invalid state.

[0026] Optionally, after updating the status information corresponding to the stream session identifier to an invalid state, the method further includes: If the duration during which the stream session identifier is in an invalid state reaches a preset recycling duration, the mapping relationship will be archived to cold storage. Update the status information corresponding to the stream session identifier to the recycling status.

[0027] Optionally, based on the status events reported by the edge computing node, the status information corresponding to the stream session identifier is updated, including: Receive the mapping status record or interruption event asynchronously reported by the edge computing node; Based on the mapping state record or the interruption event, update the mapping relationship and the state information in the persistent storage.

[0028] Optionally, the method further includes: Receive a status query request sent by the edge computing node, the status query request carrying a historical stream session identifier; Query the status information corresponding to the historical stream session identifier; Return the status information corresponding to the historical stream session identifier to the edge computing node; The status information is used to indicate whether the reuse of the historical stream session identifier is allowed.

[0029] Optionally, after sending the streaming session identifier to the edge computing node, the method further includes: The stream session identifier is sent to the configuration center of the downstream system so that the downstream system can establish a corresponding receiving channel based on the stream session identifier. The downstream system includes at least one of a recording system and a content distribution network.

[0030] Another aspect of this application provides a live stream processing apparatus applied to an edge computing node, the apparatus comprising: The determination module is used to determine the stream session identifier corresponding to the external stream identifier in response to a push request carrying an external stream identifier through authentication; The configuration module is used to configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier; The processing module is used to generate or forward the stream data corresponding to the live stream based on the stream session identifier; The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

[0031] Another aspect of this application provides a stream session identifier processing apparatus applied to a stream name management center, the apparatus comprising: The receiving module is used to receive a stream session identifier request sent by an edge computing node, wherein the stream session identifier request is associated with an external stream identifier; The generation module is used to generate a stream session identifier based on the external stream identifier; The storage module is used to establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information; The sending module is used to send the stream session identifier to the edge computing node; The update module is used to update the status information corresponding to the stream session identifier based on the status events reported by the edge computing node.

[0032] Another aspect of this application provides a computer device, including: At least one processor; and A memory that is communicatively connected to the at least one processor; Wherein: the memory stores instructions that can be executed 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 method as described above.

[0033] Another aspect of this application provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement the method described above.

[0034] Another aspect of this application provides a computer program product including a computer program that, when executed by a processor, implements the method described above.

[0035] The embodiments of this application employing the above technical solution may include the following advantages: After a push request carrying an external stream identifier passes authentication, a stream session identifier corresponding to the external stream identifier is determined, and the internal processing identifier of the live stream corresponding to the push request is configured as the stream session identifier. This allows the external stream identifier to be primarily used for user-side push authentication, while the stream session identifier is primarily used for internal processing in edge computing nodes and their downstream processing links. Furthermore, the edge computing node generates or forwards the stream data corresponding to the live stream based on the stream session identifier, enabling the downstream processing link to identify and process the live stream based on the internal processing identifier. Therefore, the continued use of the external stream identifier in the internal processing link can be reduced, mitigating the impact of external stream identifier reuse or cross-session mixing on the internal processing and session isolation of the live stream. Attached Figure Description

[0036] The accompanying drawings exemplify embodiments and form part of the specification, serving together with the textual description to explain exemplary implementations of the embodiments. The illustrated embodiments are for illustrative purposes only and do not limit the scope of the claims. Throughout the drawings, the same reference numerals refer to similar but not necessarily identical elements.

[0037] Figure 1 The diagram illustrates the operating environment of the live stream processing method and the stream session identifier processing method according to Embodiment 1 of this application. Figure 2 A flowchart illustrating a live stream processing method according to Embodiment 1 of this application is shown schematically. Figure 3Schematic illustration Figure 2 Flowchart of the sub-steps in step S200; Figure 4 Schematic illustration Figure 2 Flowchart of another sub-step in step S200; Figure 5 Schematic illustration Figure 2 Flowchart of the sub-steps in step S204; Figure 6 Schematic illustration Figure 2 Flowchart of another sub-step in step S204; Figure 7 The diagram illustrates the addition of a flowchart to the live stream processing method according to Embodiment 1 of this application; Figure 8 A flowchart illustrating a stream session identifier processing method according to Embodiment 2 of this application is shown schematically. Figure 9 Schematic illustration Figure 8 Flowchart of the sub-steps in step S802; Figure 10 Schematic illustration Figure 9 Flowchart of the sub-steps in step S902; Figure 11 Schematic illustration Figure 9 Flowchart of the sub-steps in step S904; Figure 12 Schematic illustration Figure 8 Flowchart of the sub-steps in step S808; Figure 13 The diagram illustrates a new flowchart of the streaming session identifier processing method according to Embodiment 2 of this application; Figure 14 Schematic illustration Figure 8 Flowchart of another sub-step in step S808; Figure 15 This schematically illustrates another additional flowchart of the streaming session identifier processing method according to Embodiment 2 of this application; Figure 16 The illustrations show application examples of Embodiments 1 and 2 of this application; Figure 17 The illustrations show application examples of Embodiments 1 and 2 of this application; Figure 18 The illustrations show application examples of Embodiments 1 and 2 of this application; Figure 19 The illustrations show application examples of Embodiments 1 and 2 of this application; Figure 20A block diagram of a live stream processing apparatus according to Embodiment 3 of this application is shown schematically; Figure 21 A block diagram of a streaming session identifier processing apparatus according to Embodiment 4 of this application is shown schematically; Figure 22 A schematic diagram of the hardware architecture of a computer device according to Embodiment 5 of this application is shown. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0039] It should be noted that the descriptions involving "first," "second," etc., in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature. Furthermore, the technical solutions of the various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0040] In the description of this application, it should be understood that the numerical labels before the steps do not indicate the order of the steps, but are only used to facilitate the description of this application and to distinguish each step, and therefore should not be construed as a limitation of this application.

[0041] First, a definition of the terminology used in this application is provided: A live stream can be a data stream that transmits audio and video content in real time. The live stream is usually pushed based on a persistent connection, so that the live stream can be transmitted continuously unless the broadcaster actively disconnects or there is an abnormal network interruption.

[0042] Live edge computing is a technology that pushes at least some of the processing in live stream access, processing, and distribution to the network edge. Live edge computing enables edge computing nodes to perform processes such as stream reception, stream data processing, status reporting, and distribution coordination closer to the streaming end or the viewer.

[0043] Edge computing nodes can be computing nodes located at the edge of live streaming access, streaming data processing, or content distribution. Edge computing nodes can receive push streaming requests and perform processing such as authentication, access, internal identifier configuration, streaming data generation, streaming data forwarding, interruption detection, and event reporting.

[0044] An external stream identifier can be a long-term identifier bound to a user account or live streaming entity, used for stream address identification and user-side stream authentication. In some embodiments, the external stream identifier can remain unchanged across multiple broadcasts or live sessions. The external stream identifier is used to complete stream authentication at the edge computing node's stream access point, and after authentication, it is no longer used as a stream data identifier in the system's internal processing link.

[0045] A stream session identifier is an internal processing identifier generated by the stream name management center at the start of a live stream session and bound to that session. The stream session identifier can embed an encrypted verification code and serve as an internal processing identifier in edge computing nodes and their downstream processing links. The stream session identifier expires when the corresponding live stream session ends and enters a recycling state after meeting the recycling conditions.

[0046] A live stream session can be the entire process of a broadcaster starting and ending a single broadcast. Live stream sessions can be defined by the establishment and termination of the stream, each corresponding to a stream session identifier. By associating live stream sessions with stream session identifiers, downstream processing links such as recording, screenshotting, transcoding, and content delivery networks can identify and process live streams at the session level.

[0047] Session identifiers can be used to identify live stream sessions. Session identifiers can be associated with stream session identifiers so that the stream name management center, edge computing nodes, or downstream systems can manage the live stream processing status based on the live stream session.

[0048] Status information can be used to characterize the lifecycle state corresponding to the stream session identifier. Status information can include states such as generation in progress, active, reconnection waiting, invalid, and reclaimed.

[0049] A flow name management center is a service system used to generate, store, and manage the mapping relationships between external flow identifiers, flow session identifiers, session identifiers, and status information. A flow name management center can be deployed on a single server, server cluster, cloud service platform, or virtualized computing instance.

[0050] A content delivery network (CDN) can be used to provide live stream distribution services to playback clients based on one or more distribution nodes. In this embodiment, the CDN can establish or maintain a live stream distribution link based on a stream session identifier, and the CDN does not need to be aware of external stream identifiers in its internal processing link.

[0051] HMAC-SHA256 is a key-based message authentication code algorithm. HMAC-SHA256 combines input data with an internal system key to perform a hash calculation, outputting a fixed-length irreversible digest used to generate a checksum in the stream session identifier.

[0052] Secondly, to facilitate understanding of the technical solutions provided in the embodiments of this application by those skilled in the art, the relevant technologies are described below: In current large-scale cloud live streaming platforms, the live stream typically goes through multiple processing links and business modules, from the broadcaster pushing the stream, edge node receiving the stream, origin server forwarding, recording and transcoding, to CDN distribution and playback. In order to uniquely identify the same live content throughout the entire link, the live streaming architecture adopts a fixed stream identifier mechanism. That is, after the broadcaster obtains the push address and authentication information, he can use the same stream identifier for pushing the stream for a long time. The internal modules of the system, such as recording, screenshotting, transcoding, and CDN distribution, are also processed based on this fixed stream identifier.

[0053] However, the live stream management technology based on fixed stream identifiers that the inventors are aware of has at least the following drawbacks: First, the end-to-end transparent transmission of fixed stream identifiers poses a long-term security risk. Live streaming systems typically use a mechanism where the user side and the system internally share the same stream identifier. Once this stream identifier is leaked in logs, monitoring platforms, or intermediate processing stages, third parties can use this historical stream identifier to construct streaming requests and directly obtain live content through the CDN. Because the CDN distribution chain still relies on fixed stream identifiers for resource location, even if the live streaming room has enabled security controls such as encryption and resource access permissions, it is still possible to bypass the business authentication mechanism and access live content, leading to resource leaks or reduced revenue for content creators.

[0054] Second, the reuse of fixed stream identifiers across sessions leads to a lack of session-level data isolation capabilities. During multiple consecutive or periodic live streams, the system consistently uses the same stream identifier to mark live data from different sessions, making it impossible for the system to distinguish the data ownership relationship between the current session and historical sessions based on the stream identifier. This easily leads to problems such as disorganized recording file archiving, incorrect playback resource associations, and inaccurate session-level statistics. The system needs to rely on the business layer for complex data compensation and manual maintenance, increasing platform management costs.

[0055] Third, edge nodes lack a standardized stream identifier conversion mechanism. Edge computing nodes are responsible for receiving and forwarding live streams. During the stream reception phase, they directly transmit the user-side fixed stream identifier without establishing a unified stream identifier conversion and isolation mechanism. The fixed stream identifier is continuously used from the very first stage of entering the system. Because edge nodes do not combine session information, session information, or dynamic identifier mechanisms to remap the stream data, the distributed capabilities of the edge computing architecture cannot coordinate with stream security management, making it difficult for the system to achieve session-level isolation and security control of live streams at the source.

[0056] To address this, this application provides a live stream processing technical solution. In this solution, by replacing the stream identifier at the edge node's entry point, external fixed stream identifiers are prevented from entering internal processing links such as recording, transcoding, and CDN, reducing the security risks caused by stream identifier leakage at the source and isolating the live stream from internal system links. By generating a stream session identifier containing an HMAC-SHA256 encrypted checksum based on "external stream identifier + timestamp + server key," the identifier corresponding to each live stream is unpredictable and unforgeable, thus preventing attackers from using historical stream identifiers to speculate or forge subsequent live stream links. By constructing a five-state lifecycle management mechanism including generation, active, reconnection waiting, failure, and recycling, the CDN link can be kept alive during brief broadcast interruptions, and the original stream session identifier can be reused within a preset time window, ensuring the continuity of live stream sessions and enabling seamless reconnection for viewers. By establishing local caches at edge nodes and maintaining status records in the central data center, a two-layer collaborative mechanism of rapid near-end response and remote status arbitration is formed. This ensures the consistency of stream identifier status, reduces the query pressure on the central data center, and improves processing efficiency and system scalability in large-scale distributed live streaming scenarios. See below for details.

[0057] Finally, for ease of understanding, an exemplary operating environment is provided below.

[0058] like Figure 1 As shown, the operating environment of this embodiment may include a streaming tool 10, an edge computing node 20, a stream name management center 30, a downstream processing system 40, and a content delivery network 50. The streaming tool 10 may initiate a streaming request carrying an external stream identifier to the edge computing node 20. The edge computing node 20 may communicate with the stream name management center 30 to obtain, query, or report the stream session identifier and its status information. The edge computing node 20 may also forward the stream data carrying the stream session identifier to the downstream processing system 40, or notify the content delivery network 50 to establish a distribution link based on the stream session identifier. The downstream processing system 40 may include at least one of a recording system, a screenshot system, and a transcoding system. The content delivery network 50 may include one or more CDN nodes or distribution services.

[0059] The streaming tool 10 can be a client program, broadcaster application, streaming software, streaming SDK, or other device or program module capable of generating streaming requests for initiating live streaming. The edge computing node 20 can be an edge server, edge server cluster, edge access gateway, live access node, or computing instance deployed with live access services. The stream name management center 30 can consist of one or more computing devices, which may include servers, server clusters, cloud computing service centers, or virtualized computing instances. The edge computing node 20, stream name management center 30, downstream processing system 40, and content delivery network 50 can communicate via a network. The network can include wired or wireless networks, such as fiber optic networks, Ethernet, cellular networks, Wi-Fi networks, or combinations thereof. It should be noted that the above devices and systems are exemplary, and the number and type of devices can be adjusted in different scenarios or according to different needs.

[0060] In some embodiments, Figure 1 The operating environment shown can be divided into a user access layer, a conversion and coordination layer, and a downstream processing layer according to the identifier flow path. The user access layer may include the streaming interface of the streaming tool 10 and the edge computing node 20. The streaming tool 10 can hold external stream identifiers and authentication information, and initiate streaming requests based on the external stream identifiers and authentication information. The external stream identifier is used for streaming authentication in the user access layer. After authentication is completed, it will not enter the internal modules of the system such as recording, screenshotting, transcoding, or content delivery network.

[0061] The conversion and coordination layer may include a stream identifier conversion module within the edge computing node 20 and a stream name management center 30. The stream identifier conversion module can be used to receive push requests, complete authentication, trigger stream session identifier requests, perform conversion from external stream identifiers to stream session identifiers, and generate or forward stream data using stream session identifiers. The stream name management center 30 can be used to generate, distribute, record, and maintain the lifecycle status of stream session identifiers.

[0062] The downstream processing layer may include a downstream processing system 40 and a content delivery network 50. The downstream processing system 40 and the content delivery network 50 can identify live streams or live sessions solely based on the stream session identifier, without using external stream identifiers as the identification basis in the internal processing chain. Through this three-layer architecture, a clear isolation relationship is formed between external stream identifiers and stream session identifiers.

[0063] In some embodiments, data such as external stream identifiers, stream session identifiers, session identifiers, status information, mapping status records, interruption events, and reconnection events can belong to system operation data generated during the operation of the live streaming link. When processing the above data, embodiments of this application can protect it using methods such as access control, transmission encryption, log anonymization, and storage period control. If the external stream identifier or session identifier is associated with a specific user account, it can be anonymized, hashed, or de-identified when used for status management, log analysis, or link tracing to reduce the risk of unnecessary data exposure.

[0064] Example 1 Figure 2 A flowchart illustrating a live stream processing method according to Embodiment 1 of this application is shown schematically. This live stream processing method can be applied to edge computing nodes. Figure 2 As shown, the live stream processing method may include steps S200 to S204.

[0065] S200, in response to a push request carrying an external stream identifier, authentication is performed to determine the stream session identifier corresponding to the external stream identifier.

[0066] S202, configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier.

[0067] S204, Generate or forward the stream data corresponding to the live stream based on the stream session identifier.

[0068] The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

[0069] In this embodiment, after receiving a streaming request, the edge computing node can first perform user-side streaming authentication based on the external stream identifier carried in the streaming request. The external stream identifier can be used to represent a streaming entry point, streaming address, or streaming authorization object that can be identified by the streaming end or business system. After the streaming request passes authentication, the edge computing node does not directly use the external stream identifier as the unique identifier of the internal processing link, but instead determines the streaming session identifier corresponding to the external stream identifier. Subsequently, the edge computing node configures the internal processing identifier of the live stream as the streaming session identifier, and generates or forwards the streaming data corresponding to the live stream based on the streaming session identifier. The edge computing node can act as the first processing node after the streaming data physically enters the live streaming system. After the streaming request passes authentication, the edge computing node can determine and configure the streaming session identifier in the same streaming processing stage, so that the external stream identifier is converted into the streaming session identifier at the streaming entry point. This conversion process can be automatically completed by the streaming identifier conversion module within the edge computing node, and the streaming tool and the broadcaster do not need to be aware of the generation and replacement process of the streaming session identifier. By moving the stream identifier conversion trigger point forward to the stream access point of the edge computing node, it is possible to prevent external stream identifiers from entering downstream modules such as recording, screenshotting, transcoding, and content delivery networks in a transparent manner. Therefore, external stream identifiers primarily serve as authentication for user-side push streams, while stream session identifiers primarily serve as identifiers for end-to-end processing within the system, thus creating identifier isolation at the source of stream data entering the system.

[0070] Through the above processing, the external stream identifier and the stream session identifier can each perform different technical functions. The external stream identifier is mainly for user-side push stream authentication, while the stream session identifier is mainly for internal identification, state management, and stream data connection in edge computing nodes and downstream processing links. In this way, when the live stream reconnects, push node switches, or session changes, the internal processing link can still identify the continuous processing relationship of the live stream based on the stream session identifier, thereby reducing the impact of coupling between the user-side push stream authentication identifier and the internal processing identifier.

[0071] The following combination Figure 2 The steps S200 to S204 and other related steps are further described.

[0072] Step S200 In response to a push request carrying an external stream identifier, authentication is performed to determine the stream session identifier corresponding to the external stream identifier.

[0073] Specifically, a push stream request may include at least one of the following: an external stream identifier, push stream authentication information, push stream protocol parameters, and push stream endpoint information. The edge computing node can perform authentication processing based on the external stream identifier and the push stream authentication information. If the push stream request passes authentication, the edge computing node further determines the stream session identifier corresponding to the external stream identifier.

[0074] If a push request fails authentication, the edge computing node can reject the request and return an error message to the push tool. This process prevents unauthorized push requests from entering subsequent internal processing links. This step is an optional handling method in the case of push authentication failure and is not a necessary limitation for determining the stream session identifier in this embodiment.

[0075] In optional embodiments, such as Figure 3 As shown, determining the stream session identifier corresponding to the external stream identifier includes: S300, using the external stream identifier as the query key, query the mapping cache, which is used to store the mapping relationship between the external stream identifier and the stream session identifier; S302, if a historical stream session identifier corresponding to the external stream identifier exists in the mapping cache, obtain the status information corresponding to the historical stream session identifier; S304, when the status information indicates that the historical stream session identifier is in a reconnection waiting state, the historical stream session identifier is determined as the stream session identifier corresponding to the external stream identifier.

[0076] The mapping cache stores the mapping relationship between external stream identifiers and stream session identifiers. Edge computing nodes can use the external stream identifier as a query key to check if a previously generated historical stream session identifier exists in the mapping cache. If a historical stream session identifier exists, it indicates that the external stream identifier may have been used to establish an internal processing identifier in a previous streaming or streaming interruption scenario. The edge computing node further obtains the status information corresponding to the historical stream session identifier to determine whether the historical stream session identifier can still be reused in the current streaming process.

[0077] When the status information indicates that the historical stream session identifier is in a reconnection waiting state, it can be assumed that the live stream corresponding to the historical stream session identifier may have experienced a short-term network fluctuation or interruption and is still in the lifecycle stage that allows reconnection. At this time, determining the historical stream session identifier as the stream session identifier corresponding to the current push request allows the push after reconnection to continue using the original internal processing identifier, thereby enabling edge computing nodes and downstream processing links to recognize the continuity of the live stream and reduce internal identifier switching caused by reconnection.

[0078] Mapping caches can be deployed locally on edge computing nodes, or in standalone caching services or distributed caching systems. If the mapping cache is a local cache on an edge computing node, the mapping relationships in the local cache can be configured with an expiration period, such as 10 minutes. This expiration period is used to control the residence time of local mapping relationships, reducing the long-term occupation of local resources by cached data. The above-mentioned local cache and expiration period do not constitute a limitation on the scope of protection of this application.

[0079] In some embodiments, the mapping cache of the edge computing node and the persistent state records of the flow name management center can form a two-layer collaborative structure combining near-end fast hit and remote authoritative arbitration. The edge computing node can quickly obtain the historical flow session identifier corresponding to the external flow identifier through the mapping cache, but before reusing the historical flow session identifier, the state information maintained by the flow name management center is still used as an important criterion. In other words, a hit result in the mapping cache is not directly equivalent to allowing reuse; the edge computing node only reuses the historical flow session identifier when the state information returned by the flow name management center indicates that the historical flow session identifier is in a reconnection waiting state. This approach reduces the risk of erroneous reuse caused by local cache residue.

[0080] In an optional embodiment, S302 "obtaining the status information corresponding to the historical stream session identifier" includes: sending a status query request for the historical stream session identifier to the stream name management center; and receiving the status information returned by the stream name management center. Correspondingly, S304 "after determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier" further includes: generating a reconnection event to characterize this push stream as a reconnection push stream; and sending the reconnection event to the stream name management center.

[0081] Specifically, after an edge computing node finds a historical stream session identifier in its mapping cache, it sends a status query request to the stream name management center. The status query request can carry the historical stream session identifier, as well as auxiliary information such as external stream identifiers or session identifiers. The stream name management center queries the persistent storage for status information based on the historical stream session identifier and returns the status information to the edge computing node. The edge computing node then determines whether the historical stream session identifier is reusable based on the returned status information.

[0082] After a historical stream session identifier is reused, the edge computing node can generate a reconnection event and send it to the stream name management center. The reconnection event informs the stream name management center that the live stream corresponding to the historical stream session identifier has been reconnected, thus restoring its status from a reconnection waiting state to an active state, or updating the corresponding status update time. Through status queries and reconnection event reporting, the real-time access processing of the edge computing node can be kept consistent with the status management of the stream name management center.

[0083] In optional embodiments, such as Figure 4 As shown, S200 "determining the stream session identifier corresponding to the external stream identifier" further includes: S400, if there is no historical stream session identifier corresponding to the external stream identifier in the mapping cache, or if the historical stream session identifier is not in a reconnection waiting state, a stream session identifier request is sent to the stream name management center; S402, Receive the new flow session identifier returned by the flow name management center based on the flow session identifier request; S404, the new stream session identifier is determined to be the stream session identifier corresponding to the external stream identifier; S406, Write the mapping relationship between the external stream identifier and the new stream session identifier into the mapping cache.

[0084] Specifically, when a historical flow session identifier does not exist in the mapping cache, it can be assumed that the current external flow identifier has not yet established an internal processing identifier in the cache accessible to the edge computing node. In this case, the edge computing node can send a flow session identifier request to the flow name management center to request the generation of a new flow session identifier. On the other hand, even if a historical flow session identifier exists in the mapping cache, if the status information of the historical flow session identifier is not in a reconnection waiting state, such as in an active state, an invalid state, or a recycled state, the historical flow session identifier can be left unused. Instead, a new flow session identifier can be requested or processed according to the status management strategy.

[0085] After receiving a new stream session identifier, the edge computing node can identify this new stream session identifier as the stream session identifier corresponding to the current external stream identifier, and write the mapping relationship between the external stream identifier and the new stream session identifier into the mapping cache. Therefore, when a short-term reconnection occurs or the streaming node switches to the same external stream identifier, the edge computing node can quickly locate the historical stream session identifier through the mapping cache, improving the efficiency of identifier determination.

[0086] In an optional embodiment, after S400 "sends a stream session identifier request to the stream name management center", the method further includes: Step S410: If the new stream session identifier is not received within the preset timeout threshold, resend the stream session identifier request; Step S412: If the new stream session identifier is not received after resending the stream session identifier request, the push request is rejected and an alarm message is output. The preset timeout threshold can be set as needed.

[0087] Specifically, after an edge computing node sends a flow session identifier request to the flow name management center, it can start a timeout period. If a new flow session identifier is not received within the preset timeout threshold, the edge computing node can resend the flow session identifier request to reduce the probability of access failure caused by short-term network fluctuations or request loss. If a new flow session identifier is still not received after resending, the edge computing node can reject the push request and output an alarm message. The alarm message can be used to indicate that the flow name management center is unavailable, the network is abnormal, or the identifier request link is abnormal.

[0088] The preset timeout threshold can be 200ms. This threshold limits the time edge computing nodes wait for the stream session identifier to return, preventing prolonged blocking of push stream access. Through timeout retries and failure alarms, push stream access latency can be controlled while ensuring the reliability of identifier requests.

[0089] In an optional embodiment, the mapping cache is a distributed cache cluster; S300 "query the mapping cache with the external stream identifier as the query key" includes: in the case of a switch of the push node corresponding to the live stream, querying the distributed cache cluster with the external stream identifier as the query key to obtain the historical stream session identifier corresponding to the external stream identifier.

[0090] Specifically, a distributed caching cluster can consist of multiple cache nodes and provide shared mapping query capabilities for multiple edge computing nodes. When the push node corresponding to a live stream is switched, the new edge computing node may not be able to access the local cache of the original edge computing node. In this case, by storing the mapping relationship between external stream identifiers and stream session identifiers through the distributed caching cluster, the switched edge computing node can still query the historical stream session identifiers corresponding to the external stream identifiers.

[0091] In some embodiments, the distributed caching cluster can be a distributed key-value caching cluster or other distributed caching systems that support key-value queries. The distributed caching cluster can store the mapping relationship between external stream identifiers and stream session identifiers, enabling the switching edge computing nodes to still query and reuse historical stream session identifiers that are in a reconnection waiting state when the stream from the same push entity switches between different edge computing nodes. This reduces the risk of session fragmentation caused by edge node switching.

[0092] In this optional embodiment, the sharing of mapping relationships is achieved through a distributed cache cluster, which can reduce the regeneration of internal processing identifiers caused by the switching of push nodes and improve the processing continuity in scenarios of reconnection or migration across edge nodes.

[0093] In an optional embodiment, S304 "determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier" includes: When the historical stream session identifier is in a reconnection waiting state and the current time is within a preset reconnection waiting time window, the historical stream session identifier is determined as the stream session identifier corresponding to the external stream identifier.

[0094] Specifically, the reconnection waiting state indicates that after a network interruption, the system is still waiting for the streaming end to resume streaming. To prevent expired historical stream session identifiers from being inappropriately reused, edge computing nodes can further determine whether the current time is within a preset reconnection waiting time window before reusing a historical stream session identifier. If the historical stream session identifier is in the reconnection waiting state and the current time is within the time window, the historical stream session identifier can be reused. If the current time exceeds the time window, the historical stream session identifier can not be reused.

[0095] The default reconnection waiting time window is 5 minutes, but it can also be dynamically configured based on the live stream type. For example, different live stream types, such as regular live streams, esports live streams, multi-person live streams, or other live stream types, have different tolerance levels for interruption recovery time and can be configured with different reconnection waiting time windows. By introducing time window constraints, short-term reconnection and reuse of internal identifiers can be allowed while preventing expired identifiers from remaining in a reusable state for an extended period.

[0096] In some embodiments, the preset reconnection wait time window can be dynamically read from the configuration data based on the live stream type. For example, for live events with frequent signal switching and requiring quick confirmation of interruption status, the preset reconnection wait time window can be configured to 30 seconds; for regular live streams, it can be configured to 5 minutes; and for long-duration conference live streams, it can be configured to 15 minutes. These time window parameters can be configured and distributed to adjust the reconnection waiting strategy across different live stream types.

[0097] Step S202 Configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier.

[0098] Specifically, after determining the stream session identifier, the edge computing node can configure the internal processing identifier of the live stream corresponding to the push request as that stream session identifier. The internal processing identifier can be written into the edge computing node's stream context, stream data encapsulation structure, internal routing information, log information, or downstream forwarding parameters. Subsequently, the edge computing node can use the stream session identifier as the internal processing identifier when generating stream data, forwarding stream data, reporting status events, notifying downstream systems, or establishing distribution links.

[0099] The streaming session identifier can be an identifier bound to a live session and can become invalid or reclaimed when the corresponding live session ends. This binding relationship allows the internal processing identifiers of different live sessions to be distinguished from each other, reducing the risk of data confusion between different sessions. This content is an optional implementation detail of the application method of the streaming session identifier and is not a necessary limitation of the claims.

[0100] Step S204Based on the stream session identifier, the corresponding stream data of the live stream is generated or forwarded.

[0101] Specifically, edge computing nodes can write a stream session identifier into the internal metadata, processing context, or forwarding control information of the stream data, and generate or forward audio and video stream data, slice data, encapsulated data, or internal processing messages corresponding to the live stream based on the stream session identifier. After receiving the stream data carrying the stream session identifier, the downstream processing system can identify the corresponding live stream or live session based on the stream session identifier and perform processes such as recording, screenshotting, transcoding, and distribution.

[0102] In optional embodiments, such as Figure 5 As shown, S204 "Generate or forward the stream data corresponding to the live stream based on the stream session identifier" may include: S500, Generate the stream data corresponding to the live stream based on the stream session identifier; S502, the streaming data carrying the streaming session identifier is forwarded to the downstream processing system; wherein the downstream processing system includes at least one of a recording system, a screenshot system, and a transcoding system.

[0103] Specifically, after receiving push streaming data, edge computing nodes can generate internal stream data corresponding to the live stream. This internal stream data can carry a stream session identifier. The method of carrying the stream session identifier can include writing it into the internal metadata, encapsulation information, forwarding control information, or downstream processing requests corresponding to the live stream. After the edge computing node forwards the stream data carrying the stream session identifier to the recording system, screenshot system, or transcoding system, the downstream processing system can establish corresponding processing tasks or associate the corresponding processing results with the live session based on the stream session identifier.

[0104] By passing the stream session identifier to the downstream processing system, the downstream processing system can identify the internal stream without relying on the external stream identifier, reducing the impact of changes in the push address or external identifier on the continuity of processing tasks such as recording, screenshotting, and transcoding.

[0105] In an optional embodiment, S204 "generating or forwarding the stream data corresponding to the live stream based on the stream session identifier" includes: S502, a distribution link establishment notification is sent to the content delivery network, the distribution link establishment notification carrying the stream session identifier, so that the content delivery network establishes a distribution link for the live stream based on the stream session identifier.

[0106] Specifically, after completing the push stream access and internal processing identifier configuration, the edge computing node can send a distribution link establishment notification to the content delivery network. This notification can carry a stream session identifier, or it can carry access node information, session identifier, or stream status information corresponding to the live stream. Upon receiving the distribution link establishment notification, the content delivery network can establish a distribution link for the live stream based on the stream session identifier.

[0107] In some embodiments, a content delivery network (CDN) can establish and maintain distribution links for live streams solely based on the stream session identifier. After the edge computing node completes the stream identifier conversion, the distribution link establishment notification, distribution link status maintenance information, and subsequent stream data forwarding information can all carry the stream session identifier, without carrying the external stream identifier as an internal processing identifier. In this way, the CDN does not need to be aware of the external stream identifier, thereby reducing the exposure scope of the external stream identifier in the internal links.

[0108] In some embodiments, the recording system, screenshot system, transcoding system, and content delivery network can index the live stream based on the stream session identifier. For example, the recording system can archive recording files for the corresponding session based on the stream session identifier, the screenshot system can associate screenshot results based on the stream session identifier, the transcoding system can establish transcoding tasks based on the stream session identifier, and the content delivery network can establish or maintain a distribution link based on the stream session identifier. Through this method, the downstream processing link can process live stream data on a session-by-session basis, reducing the risk of data confuse between different sessions.

[0109] By enabling the content delivery network to establish distribution links based on stream session identifiers, live streams can use a unified internal processing identifier in the access, processing, and distribution stages. This is beneficial for maintaining the correspondence between the distribution link and the internal stream state in scenarios such as reconnection, switching, or state updates.

[0110] In optional embodiments, such as Figure 6 As shown, after S204 "Generate or forward the stream data corresponding to the live stream based on the stream session identifier", it further includes: S600, Generate a mapping status record containing the external stream identifier, the stream session identifier, the session identifier, and status information; S602, send the mapping status record to the stream name management center.

[0111] Specifically, edge computing nodes can generate mapping status records after the push stream access is completed, the internal processing identifier is configured, the downstream link is established, or the stream data forwarding begins. The mapping status record can include the external stream identifier, stream session identifier, session identifier, and status information. The status information can indicate whether the current live stream is in an active state, a reconnection waiting state, or other lifecycle states. After the edge computing node sends the mapping status record to the stream name management center, the stream name management center can update the mapping relationships and status information in persistent storage accordingly.

[0112] In some embodiments, the status information in the mapping status record may include an active status. For example, when an edge computing node has generated or forwarded the stream data corresponding to the live stream based on the stream session identifier, and the live stream is in normal streaming processing, the edge computing node can generate a mapping status record with an active status and report it to the stream name management center. The stream name management center can associate and store the external stream identifier, stream session identifier, session identifier, and active status based on this mapping status record to connect the status data in the edge access, downstream processing, and content distribution links.

[0113] In this optional embodiment, by mapping status records and reporting, the flow name management center can keep abreast of the actual push status of the edge computing node and reduce the risk of inconsistency between the status of the center and the actual access status of the edge.

[0114] In optional embodiments, such as Figure 7 As shown, the method further includes: S700, if an interruption is detected in the live stream, an interruption event is generated; S702, send the interruption event to the stream name management center so that the state of the stream session identifier is updated based on the interruption event; The interruption events include active stop events that represent active shutdown, or network interruption events that represent network fluctuations.

[0115] Specifically, edge computing nodes can detect live stream interruptions based on factors such as disconnected streaming connections, active cessation of streaming by the streaming end, prolonged delays in data delivery, and network connection anomalies. If the interruption indicates that the streaming end actively terminated the live stream, an active stop event can be generated. If the interruption indicates network fluctuations, short-term link anomalies, or involuntary disconnections, a network interruption event can be generated. After the edge computing node sends the interruption event to the stream name management center, the stream name management center can update the status information corresponding to the stream session identifier based on the interruption event. Active stop events and network interruption events correspond to different status update strategies. For active stop events, the stream session identifier can enter an invalid state. For network interruption events, the stream session identifier can enter a reconnection waiting state, allowing subsequent streaming to reuse the stream session identifier within the reconnection waiting time window. By differentiating between interruption event types, the lifecycle management of the stream session identifier can be made more consistent with the actual state of the live stream.

[0116] Example 2 Figure 8 A flowchart illustrating a flow session identifier processing method according to Embodiment 2 of this application is shown schematically. This flow session identifier processing method can be applied to a flow name management center. Figure 8 As shown, the stream session identifier processing method may include steps S800 to S808.

[0117] Step S800: Receive a stream session identifier request sent by the edge computing node, wherein the stream session identifier request is associated with an external stream identifier.

[0118] Step S802: Generate a stream session identifier based on the external stream identifier.

[0119] Step S804: Establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information.

[0120] Step S806: Send the streaming session identifier to the edge computing node.

[0121] Step S808: Update the status information corresponding to the stream session identifier based on the status events reported by the edge computing node.

[0122] In this embodiment, the Stream Name Management Center is responsible for generating and managing stream session identifiers. When an edge computing node needs a new internal processing identifier, it can send a stream session identifier request to the Stream Name Management Center. The Stream Name Management Center generates a stream session identifier based on the external stream identifier and establishes a mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information. Subsequently, the Stream Name Management Center sends the stream session identifier to the edge computing node, enabling the edge computing node to perform internal processing of the live stream based on the stream session identifier. The Stream Name Management Center can also update the status information corresponding to the stream session identifier based on status events reported by the edge computing node.

[0123] By centralizing or unifying the processing of streaming session identifiers, multiple edge computing nodes, downstream processing systems, and content delivery networks can identify live streams based on a consistent mapping relationship, reducing the problems of conflict, inconsistency, or difficulty in tracking caused by decentralized identifier generation.

[0124] The following combination Figure 8 The steps S800 to S808 and other related steps are further described.

[0125] Step S800 It receives a stream session identifier request sent by an edge computing node, the stream session identifier request being associated with an external stream identifier.

[0126] Specifically, a stream session identifier application can carry an external stream identifier, as well as a session identifier, edge computing node identifier, application time, and streaming scenario information. After receiving the stream session identifier application, the stream name management center can generate a stream session identifier based on the external stream identifier. The external stream identifier can be used to determine the source relationship of the stream session identifier, and the session identifier can be used to indicate the live session corresponding to the stream session identifier.

[0127] Step S802 A stream session identifier is generated based on the external stream identifier.

[0128] Specifically, the stream name management center can generate stream session identifiers based on external stream identifiers and generation rules. Stream session identifiers should be able to establish a correspondence with live streams or live sessions within the internal processing chain. Stream session identifiers can be generated using checksums and session numbers, or through random identifier generation algorithms, snowflake algorithms, or decentralized identifier generation algorithms.

[0129] In optional embodiments, such as Figure 9 As shown, S802 "Generate a stream session identifier based on the external stream identifier" includes: S900, obtain the external stream identifier, current timestamp, and system internal key; S902, Generate a verification code based on the external stream identifier, the current timestamp, and the system internal key; S904, Based on the verification code and the session number, generate the stream session identifier.

[0130] Specifically, the current timestamp can reflect the generation time of the stream session identifier, and the internal system key can be used to participate in checksum generation to reduce the risk of the stream session identifier being predicted or forged externally. The internal system key can be stored on the server or stream name management center side and not exposed to the streaming tool, playback client, or external system. The checksum can be used as part of the stream session identifier to provide internal verification capabilities. The session sequence number can be used to represent the session order or generation order corresponding to the stream session identifier. By generating a checksum using the external stream identifier, the current timestamp, and the internal system key, and combining it with the session sequence number to generate the stream session identifier, the stream session identifier can simultaneously possess source correlation, temporal sequence, and internal verification capabilities, thereby supporting subsequent mapping management and state tracking.

[0131] In optional embodiments, such as Figure 10 As shown, S902 "Generate a verification code based on the external stream identifier, the current timestamp, and the system internal key" includes: S1000, the external stream identifier, the current timestamp, and the system internal key are concatenated according to a preset format to obtain the data to be processed; S1002, Hash the data to be processed based on the HMAC-SHA256 algorithm to obtain digest data; S1004, extract the first 16 hexadecimal characters from the digest data to obtain the check code.

[0132] Specifically, the preset format can be used to standardize the concatenation order and separation method of the external stream identifier, current timestamp, and internal system key. The stream name management center can perform HMAC-SHA256 hashing on the data to be processed to obtain digest data, and extract the first 16 hexadecimal characters from the digest data as a checksum. In some embodiments, the first 16 hexadecimal characters extracted from the digest data can correspond to 8 bytes of data. This checksum can be used to participate in the generation of the stream session identifier. By using the HMAC-SHA256 algorithm to generate the checksum, the checksum can be associated with the external stream identifier, generation time, and internal key, and the probability of different input data generating the same checksum can be reduced. Extracting the first 16 hexadecimal characters can achieve a balance between identifier length and verification capability.

[0133] In optional embodiments, such as Figure 11 As shown, S904 "Generate the stream session identifier based on the checksum and session number" includes: S1100, obtains the globally incrementing field number through atomic operations; S1102, Obtain the external flow identifier prefix corresponding to the external flow identifier; S1104, combine the external stream identifier prefix, the session number and the check code to obtain the stream session identifier.

[0134] Specifically, the Flow Name Management Center can obtain a globally auto-incrementing session number through atomic operations to avoid multiple flow session identifiers using the same session number in concurrent application scenarios. The external flow identifier prefix can be extracted from the external flow identifier or generated based on the type, business source, or preset rules of the external flow identifier. The Flow Name Management Center combines the external flow identifier prefix, session number, and checksum to obtain the flow session identifier.

[0135] In some embodiments, the stream session identifier can be generated in the format of "external stream identifier prefix_session sequence number_checksum". For example, the stream session identifier can be represented as "live_12345_003_a8f3c1e2e4b67891". Here, "live_12345" can represent a prefix extracted from or generated based on an external stream identifier, "003" can represent a globally incrementing session sequence number, and "a8f3c1e2e4b67891" can represent a 16-bit checksum extracted based on the HMAC-SHA256 digest. This format is merely an example and is not intended to limit the specific string form of the stream session identifier.

[0136] Obtaining a globally auto-incrementing session sequence number through atomic operations can reduce the risk of collisions when generating identifiers. By combining the external stream identifier prefix, session sequence number, and checksum, the stream session identifier can possess associativity, sequentiality, and verification capabilities.

[0137] In an optional embodiment, S802 "generating a stream session identifier based on the external stream identifier" includes: generating the stream session identifier based on at least one of a random identifier generation algorithm, a snowflake algorithm, or a decentralized identifier generation algorithm.

[0138] Specifically, in addition to generating stream session identifiers based on checksums and session sequence numbers, the stream name management center can also use random identifier generation algorithms, snowflake algorithms, or decentralized identifier generation algorithms to generate stream session identifiers. Random identifier generation algorithms can be used to generate internal identifiers that are difficult to predict. Snowflake algorithms can be used to generate distributed unique identifiers with time and node information. Decentralized identifier generation algorithms can be used to reduce dependence on a single central generation node.

[0139] In some embodiments, the random identifier generation algorithm can employ a random unique identifier generation method to generate stream session identifiers that do not contain business information and are not easily correlated or analyzed. The Snowflake algorithm can generate stream session identifiers based on machine identifiers, timestamps, and sequence numbers to adapt to high-concurrency identifier generation scenarios. Decentralized identifier generation algorithms can be used in live streaming content protection scenarios with high requirements for identifier tamper-proofing. The above alternative generation methods can be used alone or in combination with checksum generation methods to meet different deployment scales, concurrency levels, and security requirements.

[0140] The above generation methods can be selected based on the system deployment scale, concurrent generation volume, traceability requirements, and availability requirements. By providing multiple generation methods, the adaptability of the stream session identifier generation mechanism to different live streaming system architectures can be enhanced.

[0141] Step S804 Establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information.

[0142] Specifically, after the flow name management center generates a flow session identifier, it can establish a mapping relationship between external flow identifiers, flow session identifiers, session identifiers, and status information. This mapping relationship can be stored in a persistent storage system or synchronously written to a caching system. Persistent storage is used to permanently save the mapping relationship and status information, while the caching system is used to provide fast query capabilities for edge computing nodes.

[0143] In an optional embodiment, S804 "establishing and storing the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information" includes: In the case of generating the stream session identifier, the mapping relationship is established, and the status information is set to the generating state; Correspondingly, after sending the stream session identifier to the edge computing node, the method further includes: if it is determined that the stream session identifier has been successfully sent, updating the status information from the generating state to the active state.

[0144] Specifically, when a stream session identifier is newly generated but before successful reception by the edge computing node is confirmed, the stream name management center can set the status information to "generating". The "generating" status indicates that the stream session identifier has been created, but whether its corresponding live stream has entered the actual streaming processing chain needs further confirmation. Once the stream name management center determines that the stream session identifier has been successfully sent, or the edge computing node reports the mapping status record, the status information can be updated from "generating" to "active". By setting the "generating" status, the transition phase between identifier generation and actual activation can be distinguished, reducing the problem of unclear status caused by identifiers being generated but not successfully sent. By updating to "active" status after successful transmission, it can be indicated that the stream session identifier has entered the normal internal processing chain.

[0145] In an optional embodiment, the status information includes a generation status, an active status, a reconnection waiting status, a failed status, and a recycling status.

[0146] Specifically, the "generating" status indicates that the stream session identifier has been generated but not yet confirmed for use. The "active" status indicates that the live stream is being pushed or the internal processing link is operating normally. The "reconnection waiting" status indicates that after a network interruption, the system still allows the reuse of the stream session identifier for reconnection within a certain time window. The "invalid" status indicates that the stream session identifier is no longer allowed for new streaming processing or reconnection reuse. The "reclaimed" status indicates that the mapping relationship corresponding to the stream session identifier has been archived or is no longer involved in real-time queries.

[0147] In some embodiments, the active state can also indicate that the content delivery network distribution link corresponding to the streaming session identifier is in normal service. In the active state, edge computing nodes can continuously forward streaming data based on the streaming session identifier, and downstream processing systems and the content delivery network can perform recording, screenshotting, transcoding, caching, or distribution processing based on the same streaming session identifier.

[0148] By setting the above states, a lifecycle management mechanism for the stream session identifier can be formed, enabling the stream name management center to control the state transition of the stream session identifier based on the events reported by the edge computing nodes.

[0149] Step S806 The streaming session identifier is sent to the edge computing node.

[0150] Specifically, after the Stream Name Management Center generates a stream session identifier and establishes a mapping relationship, it can send the stream session identifier to the edge computing nodes. Upon receiving the stream session identifier, the edge computing nodes can configure it as the internal processing identifier for the live stream. The Stream Name Management Center can update its status after successful transmission, or it can wait for the edge computing nodes to report their mapping status records before updating its status.

[0151] In an optional embodiment, after S806 “sends the stream session identifier to the edge computing node”, the method further includes: sending the stream session identifier to the configuration center of the downstream system so that the downstream system establishes a corresponding receiving channel based on the stream session identifier; wherein the downstream system includes at least one of a recording system and a content delivery network.

[0152] Specifically, the stream name management center can send the stream session identifier to the configuration center of the downstream system. The configuration center of the downstream system can be a configuration service used to manage the configuration of downstream receiving channels, distribution channels, or processing tasks. The configuration center can establish receiving channels, distribution channels, or processing task configurations for the recording system, content delivery network, or other downstream systems based on the stream session identifier. In this way, when the edge computing node subsequently forwards stream data carrying the stream session identifier, the downstream system can process it based on the established receiving channel.

[0153] By sending the stream session identifier to the downstream system configuration center in advance or synchronously, the waiting time for the downstream system to temporarily create channels when receiving stream data can be reduced, and the coordination between the access link and the downstream processing link can be enhanced.

[0154] Step S808 Based on the status events reported by the edge computing node, update the status information corresponding to the stream session identifier.

[0155] Specifically, the status events reported by edge computing nodes can include mapping status records, interruption events, reconnection events, active stop events, network interruption events, etc. The flow name management center updates the status information corresponding to the flow session identifier based on different status events. The updated status information can be written to persistent storage or synchronized to the caching system for edge computing nodes to query.

[0156] In optional embodiments, such as Figure 12 As shown, S808 "updates the status information corresponding to the stream session identifier based on the status event reported by the edge computing node" includes: S1200, in the case of receiving a network interruption event reported by the edge computing node, updating the status information corresponding to the stream session identifier from an active state to a reconnection waiting state; S1202, keeping the content delivery network distribution link corresponding to the stream session identifier in an effective state.

[0157] Specifically, a network interruption event can indicate that the live stream is interrupted due to network fluctuations, short-term disconnection, or unintentional factors. Upon receiving a network interruption event, the stream name management center can update the status information corresponding to the stream session identifier from active to reconnection waiting. In the reconnection waiting state, the content distribution network link corresponding to the stream session identifier can remain active, allowing the streaming end to continue using the original distribution link when it resumes streaming within a short period.

[0158] By entering a reconnection waiting state in the event of a network outage and keeping the content distribution network distribution link active, the overhead of rebuilding the distribution link caused by short-term interruptions can be reduced, and the continuity of live stream recovery processing can be improved.

[0159] In an optional embodiment, after S1200 "updates the status information corresponding to the stream session identifier from the active state to the reconnection waiting state", the method further includes: if a reconnection event corresponding to the stream session identifier is received within a preset reconnection waiting time window, updating the status information corresponding to the stream session identifier from the reconnection waiting state to the active state; wherein, the reconnection event is used to instruct the edge computing node to reuse the stream session identifier in the reconnection push stream.

[0160] Specifically, after updating the status information to "reconnection waiting," the Stream Name Management Center can wait for the edge computing nodes to report reconnection events within a preset reconnection waiting time window. If a reconnection event corresponding to the stream session identifier is received within this time window, it indicates that the edge computing node has reused the stream session identifier in the reconnection push. At this time, the Stream Name Management Center can update the status information from "reconnection waiting" to "active."

[0161] By reconnecting to event-driven state recovery, the stream name management center can accurately identify whether the live stream has resumed streaming and reinstate the stream session identifier into active state management.

[0162] In an optional embodiment, after S1200 "updates the status information corresponding to the stream session identifier from the active state to the reconnection waiting state", the method further includes: if no reconnection event corresponding to the stream session identifier is received within a preset reconnection waiting time window, updating the status information corresponding to the stream session identifier from the reconnection waiting state to the invalid state; or, if an active stop event reported by the edge computing node is received, updating the status information corresponding to the stream session identifier to the invalid state.

[0163] Specifically, if a stream session identifier enters a reconnection waiting state and no corresponding reconnection event is received within a preset reconnection waiting time window, it can be considered that the live stream has not resumed streaming within the allowed time. In this case, the stream name management center can update the status information from the reconnection waiting state to the invalid state. On the other hand, if an edge computing node reports an active stop event, it indicates that the streaming end or the live streaming service side has actively terminated the streaming, and the stream name management center can update the status information corresponding to the stream session identifier to the invalid state.

[0164] The above state transitions can distinguish between short-term network interruptions and the end of a live stream. Short-term network interruptions can first enter a reconnection waiting state; if the stream is actively stopped or a reconnection timeout occurs, it enters an invalid state, thus preventing the reuse of ended or timed-out stream session identifiers.

[0165] After a stream session identifier becomes invalid, the stream name management center can return query results representing the invalidation status in response to the status query request from the edge computing node. Upon receiving the invalidation status, the edge computing node can choose not to reuse the corresponding historical stream session identifier, but instead request a new stream session identifier or reject push requests that do not meet the conditions.

[0166] In some embodiments, after a stream session identifier becomes invalid, the stream name management center can return invalidation status information for query requests related to that stream session identifier. Related downstream systems can then stop using that stream session identifier as a valid internal processing identifier based on this invalidation status information. If the pull-stream authentication link or content delivery network can obtain this invalidation status information, it can reject pull-stream requests initiated using that stream session identifier based on this invalidation status information. The specific entity that rejects the request can be determined based on the deployment method of the pull-stream authentication service, content delivery network, or scheduling system in the live streaming system.

[0167] In optional embodiments, such as Figure 13 As shown, after updating the status information corresponding to the stream session identifier to an invalid state, the process further includes: S1300, if the duration during which the stream session identifier is in an invalid state reaches a preset recycling duration, the mapping relationship is archived to cold storage; S1302, update the status information corresponding to the stream session identifier to the recycling status.

[0168] Specifically, an invalidation state indicates that the stream session identifier is no longer participating in real-time streaming or reconnection and reuse. If the stream session identifier remains in an invalidation state for a preset recycling period, the stream name management center can archive the corresponding mapping relationship to cold storage and update the status information to the recycling status. Cold storage can be used to save historical mapping relationships for subsequent troubleshooting, log tracing, or statistical analysis. The preset recycling period can be 24 hours.

[0169] By performing cold storage archiving and recycling status updates after a failure state, invalid data occupancy in real-time storage and caching systems can be reduced while retaining necessary historical traceability information.

[0170] In optional embodiments, such as Figure 14 As shown, S808 "updates the status information corresponding to the stream session identifier based on the status events reported by the edge computing node" includes: S1400, receive the mapping status record or interruption event asynchronously reported by the edge computing node; S1402, based on the mapping state record or the interruption event, update the mapping relationship and the state information in the persistent storage.

[0171] Specifically, edge computing nodes can asynchronously report mapping status records or interruption events. Asynchronous reporting reduces the waiting time for edge computing nodes during the main streaming process. After receiving the asynchronously reported data, the stream name management center can update the mapping relationships and status information in persistent storage. If a caching system is also used, the stream name management center can also synchronize the updated status to the caching system for faster subsequent queries.

[0172] By using asynchronous reporting and persistent updates, central-side state maintenance can be achieved without significantly increasing push stream access latency, thereby improving the real-time performance and reliability of state management.

[0173] In optional embodiments, such as Figure 15 As shown, the method further includes: S1500, receive a status query request sent by the edge computing node, the status query request carrying a historical stream session identifier; S1502, query the status information corresponding to the historical stream session identifier; S1504, return the status information corresponding to the historical stream session identifier to the edge computing node; wherein, the status information is used to indicate whether the reuse of the historical stream session identifier is allowed.

[0174] Specifically, after an edge computing node matches a historical flow session identifier in its mapping cache, it can send a status query request to the flow name management center. The flow name management center queries the corresponding status information based on the historical flow session identifier and returns the status information to the edge computing node. The edge computing node can then determine whether to reuse the historical flow session identifier based on the returned status information.

[0175] By using status query requests and status returns, edge computing nodes can make reuse decisions based on the lifecycle status maintained by the flow name management center, reducing the risk of inconsistency caused by relying solely on local cache for reuse judgments.

[0176] In some embodiments, the security isolation effect of the streaming session identifier can be verified through historical identifier pull verification. For example, in a test environment where encryption control is enabled in the live broadcast room, a pull request can be constructed using the historical identifier corresponding to the previous session, and the success rate of the pull request can be counted. When internal processing and distribution are performed using the streaming session identifier, a new streaming session identifier can be generated after a new session starts broadcasting, and the streaming session identifier corresponding to the previous session becomes invalid. The content delivery network distributes content based on the new streaming session identifier. This reduces the possibility of using the previous session identifier to continue hitting the valid distribution link of the current session.

[0177] In some embodiments, the effectiveness of session isolation can be verified through continuous multi-session live streaming. For example, multiple live streams can be conducted consecutively, and the recording files for each session can be queried by the recording system according to the stream session identifier. If each session's recording file corresponds one-to-one with its respective stream session identifier, it can be demonstrated that the stream session identifier can support the archiving and querying of recording files by session, reducing the risk of cross-session data confusion.

[0178] To make this application easier to understand, several exemplary applications are provided below. These application examples are only used to illustrate the implementation process of the embodiments of this application in live stream access, reconnection and reuse, and session end processing, and are not intended to limit the scope of protection of this application.

[0179] Application Example 1: Normal Live Broadcast Scenario.

[0180] S1, the streaming tool initiates a streaming request to the edge computing node based on the external stream identifier and authentication information. The external stream identifier can be a streaming identifier that is permanently bound to the user account or the live streaming entity, and is used for user-side streaming authentication.

[0181] S2, after receiving the push request, the edge computing node performs push authentication based on the external stream identifier and the authentication information. If the push request passes authentication, the edge computing node queries the mapping cache using the external stream identifier as the query key.

[0182] S3, if there is no historical stream session identifier corresponding to the external stream identifier in the mapping cache, the edge computing node sends a stream session identifier request to the stream name management center.

[0183] S4, the Flow Name Management Center generates a Flow Session Identifier based on the External Flow Identifier, and establishes a mapping relationship between the External Flow Identifier, the Flow Session Identifier, the Session Identifier, and the Status Information. The Status Information can be initially set to a generating state, and then updated to an active state after the Flow Session Identifier is successfully sent or the edge computing node reports the mapping status record.

[0184] S5, after receiving the stream session identifier, the edge computing node configures the internal processing identifier of the live stream corresponding to the push request as the stream session identifier, and writes the mapping relationship between the external stream identifier and the stream session identifier into the mapping cache.

[0185] S6, the edge computing node generates or forwards the streaming data corresponding to the live stream based on the streaming session identifier, and forwards the streaming data carrying the streaming session identifier to at least one downstream processing system among the recording system, screenshot system or transcoding system.

[0186] S7, the edge computing node can also send a distribution link establishment notification carrying the stream session identifier to the content delivery network, so that the content delivery network can establish a distribution link for the live stream based on the stream session identifier.

[0187] S8, the edge computing node generates a mapping status record containing the external flow identifier, the flow session identifier, the session identifier, and the active status, and sends the mapping status record to the flow name management center.

[0188] In the above application example, the external stream identifier is mainly used for user-side streaming authentication between the streaming tool and the edge computing node. After the streaming request is authenticated, the edge computing node configures the internal processing identifier of the live stream as the streaming session identifier during the streaming reception phase. Downstream processing links such as the recording system, screenshot system, transcoding system, and content delivery network can identify the live stream or live session based on the streaming session identifier, without needing to continue using the external stream identifier as the internal processing identifier. This reduces the risk of the external stream identifier being reused or mixed across sessions after entering the internal processing links.

[0189] Application Example 2: Reconnection and reuse scenario after network fluctuations.

[0190] S1, during the normal streaming process, the edge computing node forwards the streaming data corresponding to the live stream based on the streaming session identifier, and transmits the streaming session identifier to the downstream processing system or content delivery network.

[0191] S2, after the edge computing node detects that the live stream is interrupted due to network fluctuations, it generates a network interruption event and sends the network interruption event to the stream name management center.

[0192] S3, after receiving the network interruption event, the Stream Name Management Center updates the status information corresponding to the Stream Session Identifier from active to reconnection waiting state, and keeps the content delivery network distribution link corresponding to the Stream Session Identifier in an effective state.

[0193] S4. Within the preset reconnection waiting time window, the streaming tool re-initiates a streaming request carrying the same external stream identifier to the edge computing node.

[0194] S5, after the re-initiated push request passes authentication, the edge computing node queries the mapping cache using the external stream identifier as the query key to obtain the historical stream session identifier corresponding to the external stream identifier.

[0195] S6, the edge computing node sends a status query request for the historical flow session identifier to the flow name management center and receives the status information returned by the flow name management center.

[0196] S7, when the status information indicates that the historical stream session identifier is in a reconnection waiting state and the current time is within a preset reconnection waiting time window, the edge computing node determines the historical stream session identifier as the stream session identifier corresponding to this reconnection push.

[0197] S8, the edge computing node generates a reconnection event to characterize this push stream as a reconnection push stream, and sends the reconnection event to the stream name management center.

[0198] S9, the Stream Name Management Center updates the status information corresponding to the historical stream session identifier from the reconnection waiting state to the active state based on the reconnection event.

[0199] In the above application example, the edge computing node does not directly reuse the historical stream session identifier based solely on the mapping cache hit result, but further uses the status information maintained by the stream name management center as the basis for reuse. Through the near-end fast hit of the mapping cache and the remote status confirmation of the stream name management center, the same stream session identifier can be reused in reconnection scenarios after short-term network fluctuations, thereby improving the continuity of identification of the same live broadcast session in the internal processing link.

[0200] Application Example 3: Active stop broadcasting and tag recycling scenario.

[0201] S1, while the live stream is active, the edge computing node continuously forwards stream data based on the stream session identifier and reports mapping status records or status events to the stream name management center.

[0202] S2, after the edge computing node detects that the streaming end has actively stopped streaming, it generates an active stop event and sends the active stop event to the stream name management center.

[0203] S3, after receiving the active stop event, the Stream Name Management Center updates the status information corresponding to the Stream Session Identifier to the Failed state.

[0204] S4, after the stream session identifier becomes invalid, the stream name management center can return invalidation status information in response to the status query request sent by the edge computing node. After receiving the invalidation status information, the edge computing node will no longer reuse the corresponding historical stream session identifier.

[0205] S5, when the duration of the invalidation of the stream session identifier reaches the preset recycling duration, the stream name management center archives the mapping relationship between the external stream identifier, the stream session identifier, the session identifier and the status information to cold storage, and updates the status information corresponding to the stream session identifier to the recycling status.

[0206] S6 When a new live streaming request is initiated again using the same external stream identifier, the edge computing node can apply for a new stream session identifier from the stream name management center and configure the new stream session identifier as the internal processing identifier for the new live session.

[0207] In the above application example, the active termination event invalidates the stream session identifier corresponding to the current live broadcast session. Subsequent new live broadcast sessions can use a new stream session identifier as their internal processing identifier. By combining the invalidation and recycling states, the number of times the stream session identifier corresponding to the already ended live broadcast session continues to participate in the real-time reuse judgment can be reduced, while retaining the necessary historical mapping relationships for log tracing or problem investigation.

[0208] Application Example 4: Edge Node Switching Scenario.

[0209] S1, the push streaming tool initiates a push streaming request to the first edge computing node based on the external stream identifier and authentication information. After the push streaming request is authenticated, the first edge computing node obtains the corresponding stream session identifier and writes the mapping relationship between the external stream identifier and the stream session identifier into the distributed cache cluster.

[0210] S2, in the event of network fluctuations, scheduling switching, or changes in access links in the live stream, the streaming tool re-initiates a streaming request carrying the same external stream identifier to the second edge computing node.

[0211] S3, after the re-initiated push request passes authentication, the second edge computing node queries the distributed cache cluster using the external stream identifier as the query key to obtain the historical stream session identifier corresponding to the external stream identifier.

[0212] S4, the second edge computing node queries the flow name management center for the status information corresponding to the historical flow session identifier.

[0213] S5, when the historical stream session identifier is in a reconnection waiting state and the current time is within a preset reconnection waiting time window, the second edge computing node reuses the historical stream session identifier and continues to generate or forward the stream data corresponding to the live stream based on the historical stream session identifier.

[0214] In the above application example, the distributed caching cluster enables different edge computing nodes to share the mapping relationship between external stream identifiers and stream session identifiers; the stream name management center is used to confirm whether historical stream session identifiers can be reused. Through the above processing, even if the push stream access node is switched, the risk of fragmentation of processing identifiers within the same live broadcast session due to edge node switching can be reduced.

[0215] Application Example 5: Illegal Flow Identification Direct Access to Risk Isolation Scenarios (See details) Figure 16 .

[0216] S1, the streaming tool initiates a streaming request to the edge computing node based on the external stream identifier and authentication information. The external stream identifier can be a long-term bound fixed streaming identifier.

[0217] S2, after receiving the push request, the edge computing node performs authentication verification on the push request. The authentication verification may include at least one of authentication failure verification and stream name recycling status verification.

[0218] S3, if the streaming request fails authentication, the edge computing node generates an illegal streaming event and refuses to establish a live stream access link. The illegal streaming event may include an authentication failure event, an abnormal stream name access event, or an invalid stream name access event.

[0219] S4. After the push request is rejected, the edge computing node does not request or allocate a stream session identifier from the recording system, and does not generate a corresponding internal stream processing link.

[0220] S5, the edge computing node prevents the live stream from entering the recording system. Because the recording system has not obtained the corresponding stream session identifier, it does not perform recording processing on the live stream.

[0221] S6, the edge computing node further prevents the live stream from entering the screenshot / transcoding system. Because the screenshot / transcoding system lacks a corresponding internal processing link, it does not perform screenshot processing, transcoding processing, or related media processing.

[0222] S7. Since the live stream failed the connection verification of the edge computing node, the data stream corresponding to the live stream will no longer be transmitted to the downstream processing link, and therefore will not enter the recording / transcoding processing stage.

[0223] S8. In the case where the live stream does not generate a valid stream session identifier, the content delivery network does not establish a corresponding CDN distribution link and will not push the corresponding live stream content to the audience.

[0224] S9: Since viewers do not receive live data from the content delivery network, they are unable to watch the corresponding live content, thus isolating and blocking illegal streaming.

[0225] In the above application example, the edge computing node is located between the user-side streaming link and the internal live streaming processing link. By performing authentication failure verification and stream name recycling status verification during the streaming reception phase, it can block unauthorized streaming before it enters the internal system. Since unauthorized streaming cannot enter the recording system, screenshot / transcoding system, and CDN distribution link, it can reduce the amount of internal processing resources occupied by unauthorized stream data and reduce the impact of invalid stream names, forged stream names, or abnormal streaming behavior on the security and stability of the live streaming system.

[0226] Application Example 6: Scenario of cache reuse and dynamic stream name (stream session identifier) ​​reconstruction. See details in [link to relevant documentation]. Figure 17 .

[0227] S1, the edge computing node receives a push stream request sent by the broadcaster, the push stream request carrying a static stream name (external stream identifier). The static stream name can be a fixed push stream identifier that the broadcaster uses for a long time.

[0228] S2, the edge computing node performs flow authentication processing based on the static flow name and authentication information to verify the legality of the static flow name and authentication information.

[0229] S3, if the stream authentication fails, the edge computing node rejects the push request and returns authentication failure information to the broadcaster.

[0230] S4, if the flow authentication passes, the edge computing node queries the local mapping cache using the static flow name as the query key. The local mapping cache can cache the mapping relationship between static flow names and dynamic flow names, and set the cache validity period (TTL). For example, the TTL can be set to 10 minutes.

[0231] S5, if the local mapping cache is hit and the corresponding dynamic stream name is still valid, the edge computing node reuses the historical dynamic stream name in the cache and continues to mark the current live stream based on the historical dynamic stream name. Since it is not necessary to re-apply for dynamic stream names, the processing time in the stream connection stage can be reduced.

[0232] S6, if the local mapping cache misses or the dynamic stream name in the cache expires, the edge computing node sends a new dynamic stream name request to the stream name management center. The new dynamic stream name request process can have a timeout set, for example, 200ms.

[0233] S7, if the application to the Flow Name Management Center is successful, the Flow Name Management Center generates a new dynamic flow name and returns the new dynamic flow name to the edge computing node. The edge computing node writes the new dynamic flow name into its local mapping cache and updates the corresponding cache validity period (TTL). For example, the TTL can be reset to 10 minutes.

[0234] S8. If the application to the stream name management center fails, or fails after a preset number of retries, the edge computing node rejects the current push request to prevent live streams without a valid dynamic stream name mapping relationship from entering the subsequent internal processing link.

[0235] S9, the edge computing node performs internal processing and marking on the live stream based on the reused historical dynamic stream name or the newly applied dynamic stream name, and forwards the stream data carrying the dynamic stream name to at least one downstream system among the recording system, screenshot system, transcoding system or content delivery network CDN.

[0236] S10, the edge computing node reports the mapping status record to the stream name management center. The mapping status record may include static stream name, dynamic stream name, session identifier ID, and status information. The status information can be used to characterize the activity status of the live session corresponding to the current dynamic stream name.

[0237] S11. After the above processing is completed, the live stream enters the normal transmission state. The downstream system can identify the corresponding live session based on the dynamic stream name and perform recording, screenshotting, transcoding or content distribution processing.

[0238] In the above application example, edge computing nodes preferentially reuse historical dynamic stream names through local mapping caches. Only when the cache expires or a valid dynamic stream name does the node reapply for a new dynamic stream name from the stream name management center. This combination of a fast local cache hit mechanism and a remote dynamic stream name application mechanism reduces the processing overhead caused by repeated dynamic stream name generation and decreases latency during the live streaming access phase. Furthermore, using dynamic stream names to uniformly identify live streams in the downstream processing chain reduces the risk of internal stream identifier misuse between different live sessions.

[0239] Application Example 7: Dynamic Stream Name Generation and Distribution Scenario (see details) Figure 18 .

[0240] S1, the stream name management center receives a dynamic stream name request sent by the edge computing node. The dynamic stream name request may carry a static stream name, session information, or broadcaster identification information.

[0241] S2, the stream name management center obtains the corresponding static stream name and the current second-level timestamp based on the dynamic stream name application request. The second-level timestamp can be used to represent the time when the dynamic stream name was generated.

[0242] S3, after obtaining the static stream name and second-level timestamp, the stream name management center appends a system key. This system key can be stored on the server for security verification during the dynamic stream name generation process.

[0243] S4, the Stream Name Management Center performs HMAC-SHA256 hash calculation based on the static stream name, the second-level timestamp, and the system key to generate the corresponding hash result.

[0244] S5, the stream name management center extracts a checksum of a preset length from the hash result. For example, the first 16 bits can be extracted as the checksum corresponding to the dynamic stream name.

[0245] S6, the stream name management center generates a dynamic stream name based on the combination of the static stream name, the global field sequence number, and the checksum. The format of the dynamic stream name can be: {static prefix}_{auto-incrementing sequence number}_{16-bit checksum}.

[0246] S7. After generating dynamic flow names, the flow name management center performs an auto-increment operation on the global field sequence number. The auto-increment process of the global field sequence number can be implemented based on atomic operations to reduce the risk of sequence number conflicts in concurrent scenarios.

[0247] S8, the stream name management center establishes and writes the mapping relationship table. The mapping relationship table may include static stream names, dynamic stream names, session identifiers (IDs), and status information. The status information can initially be set to "generating".

[0248] S9, the flow name management center distributes the dynamic flow name to the edge computing node through the intranet interface. The dynamic flow name distribution process can be configured with a timeout threshold, such as 200ms; in the event of an initial distribution failure, a preset number of retries can be performed. For example, one retry can be performed.

[0249] S10, if the dynamic flow name is successfully sent to the edge computing node, the flow name management center updates the status information in the mapping table from the generating state to the active state, and returns the dynamic flow name to the edge computing node.

[0250] S11, if the second delivery of the dynamic flow name still fails, the flow name management center rejects the current push request and generates corresponding alarm information. The alarm information can be used for operation and maintenance monitoring or anomaly troubleshooting.

[0251] In the above application example, the stream name management center generates dynamic stream names based on static stream names, timestamps, system keys, and global session sequence numbers, and improves the uniqueness and security of dynamic stream names through hash checksums. Meanwhile, by using atomically incrementing session sequence numbers, mapping relationship state management, and a dynamic stream name distribution retry mechanism, the reliability of the dynamic stream name generation and distribution process can be improved, thereby reducing the risk of dynamic stream name conflicts, distribution failures, or internal processing link anomalies in high-concurrency live streaming scenarios.

[0252] Application Example 8: Dynamic Flow Name Lifecycle State Transition Scenario (see details) Figure 19 .

[0253] S1, the edge computing node receives the streaming request sent by the broadcaster and completes the streaming authentication. After the streaming authentication is successful, the edge computing node initiates a dynamic stream name application request to the stream name management center.

[0254] S2, the flow name management center generates the corresponding dynamic flow name and establishes a mapping relationship between static flow name, dynamic flow name, session identifier, and status information. The status information is initially set to "generating". This "generating" status indicates that the dynamic flow name has been generated but has not yet been officially activated.

[0255] S3, the flow name management center distributes the dynamic flow name to the edge computing node through the intranet interface. The dynamic flow name distribution process can be configured with a timeout threshold, such as 200ms.

[0256] S4, if the dynamic stream name is successfully delivered to the edge computing node, the stream name management center will update the corresponding status information from "generating" to "active". An active dynamic stream name can be used for normal access, forwarding, and downstream processing of the live stream.

[0257] S5, in the event that the dynamic stream name delivery times out or fails to be delivered, the stream name management center updates the corresponding status information from the generating state to the failed state, rejects the current push request, and generates corresponding alarm information.

[0258] S6, while the live stream is active, the edge computing node continuously forwards the stream data based on the dynamic stream name and transmits the dynamic stream name to the recording system, screenshot system, transcoding system or content delivery network.

[0259] S7. In the event that the live stream is interrupted due to network fluctuations, link anomalies, or a disconnection on the broadcaster's side, the edge computing node sends a disconnection event to the stream name management center. Upon receiving the disconnection event, the stream name management center updates the status information of the corresponding dynamic stream name from active to reconnection waiting.

[0260] S8. During the period when the dynamic stream name is in the reconnection waiting state, the stream name management center maintains the mapping relationship of the corresponding live session. The reconnection waiting state can be set with a preset waiting time, such as 5 minutes.

[0261] S9, if the current time is within the preset waiting time and the streamer re-initiates a push request with the same static stream name, the edge computing node queries the stream name management center for the status of the corresponding dynamic stream name.

[0262] S10, if the query result indicates that the corresponding dynamic stream name is still in the reconnection waiting state, the stream name management center will restore the corresponding status information from the reconnection waiting state to the active state, and allow the edge computing node to continue to reuse the original dynamic stream name for live stream processing.

[0263] S11, if no reconnection push request is received during the reconnection waiting period of the dynamic stream name, and the preset waiting time exceeds the specified time, the stream name management center will update the corresponding status information to an invalid status. Dynamic stream names in an invalid status are no longer allowed to participate in push streaming processing.

[0264] S12, after the dynamic stream name enters the invalid state, the stream name management center can return the information that the stream request was rejected to the broadcaster and trigger the corresponding abnormal alarm.

[0265] S13, when the dynamic stream name is in an invalid state for a preset retention period, such as 24 hours, the stream name management center will update the status of the corresponding dynamic stream name to the recycling state and perform dynamic stream name cleanup.

[0266] S14. After completing the dynamic stream name recycling, the stream name management center will archive the corresponding static stream name, dynamic stream name, session identifier, and status transition record to the log recording system for subsequent problem tracing, maintenance, or live broadcast behavior analysis.

[0267] In the above application example, the stream name management center manages the lifecycle of dynamic stream names in a unified manner through the generation, active, reconnection waiting, invalid, and recycling states. By introducing the reconnection waiting state in network fluctuation scenarios, the original dynamic stream name can be reused after a short-term interruption, improving the continuity of internal identifiers within live sessions. At the same time, the combination of invalid and recycling states can reduce the risk of invalid dynamic stream names occupying system resources for a long time or continuing to participate in business processing.

[0268] Example 3 Figure 20A block diagram of a live stream processing apparatus according to Embodiment 3 of this application is illustrated schematically. This apparatus can be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors to complete the embodiments of this application. The program module referred to in the embodiments of this application refers to a series of computer program instruction segments capable of performing a specific function. The following description will specifically introduce the functions of each program module in this embodiment.

[0269] like Figure 20 As shown, the device 2000 may include: a determining module 2010, a configuring module 2020, and a processing module 2030, wherein: The determination module 2010 is used to determine the stream session identifier corresponding to the external stream identifier in response to a push request carrying an external stream identifier and after authentication. Configuration module 2020 is used to configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier; Processing module 2030 is used to generate or forward stream data corresponding to the live stream based on the stream session identifier; The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

[0270] It should be noted that the live stream processing device of this embodiment can execute any of the live stream processing methods in Embodiment 1. The specific implementation method and technical effect can be referred to Embodiment 1, and will not be repeated here.

[0271] Example 4 Figure 21 A block diagram of a streaming session identifier processing apparatus according to Embodiment 4 of this application is shown schematically.

[0272] The device can be divided into one or more program modules. One or more program modules are stored in a storage medium and executed by one or more processors to complete the embodiments of this application. The program module referred to in the embodiments of this application refers to a series of computer program instruction segments capable of performing a specific function. The following description will specifically introduce the function of each program module in this embodiment. For example... Figure 21 As shown, the device 2100 may include: a receiving module 2110, a generating module 2120, a storage module 2130, a sending module 2140, and an updating module 2150, wherein: The receiving module 2110 is used to receive a stream session identifier request sent by an edge computing node, wherein the stream session identifier request is associated with an external stream identifier; Generation module 2120 is used to generate a stream session identifier based on the external stream identifier; Storage module 2130 is used to establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information; Sending module 2140 is used to send the streaming session identifier to the edge computing node; The update module 2150 is used to update the status information corresponding to the stream session identifier based on the status events reported by the edge computing node.

[0273] It should be noted that the streaming session identifier processing device of this embodiment can execute any of the streaming session identifier processing methods in embodiment two. The specific implementation method and technical effect can be referred to embodiment two, and will not be repeated here.

[0274] Example 5 Figure 22 This illustration schematically depicts a hardware architecture diagram of a computer device 10000 suitable for implementing the methods described above, according to Embodiment 5 of this application. In some embodiments, the computer device 10000 may be a rack server, blade server, tower server, or cabinet server (including standalone servers or server clusters composed of multiple servers), etc. Figure 22 As shown, the computer device 10000 includes, but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can be interconnected via a system bus. Wherein: The memory 10010 includes at least one type of computer-readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 10010 may be an internal storage module of a computer device 10000, such as the hard disk or memory of the computer device 10000. In other embodiments, the memory 10010 may also be an external storage device of the computer device 10000, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the computer device 10000. Of course, the memory 10010 may also include both the internal storage module and the external storage device of the computer device 10000. In this embodiment, the memory 10010 is typically used to store the operating system and various application software installed on the computer device 10000, such as the program code of the method described in Embodiment 1 or 2. Furthermore, the memory 10010 can also be used to temporarily store various types of data that have been output or will be output.

[0275] In some embodiments, processor 10020 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other chip. Processor 10020 is typically used to control the overall operation of computer device 10000, such as performing control and processing related to data interaction or communication with computer device 10000. In this embodiment, processor 10020 is used to run program code stored in memory 10010 or process data.

[0276] Network interface 10030 may include a wireless network interface or a wired network interface, which is typically used to establish a communication link between computer device 10000 and other computer devices. For example, network interface 10030 is used to connect computer device 10000 to an external terminal via a network, establishing a data transmission channel and communication link between computer device 10000 and the external terminal. The network may be an intranet, the Internet, Global System for Mobile Communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, or other wireless or wired networks.

[0277] It should be pointed out that, Figure 22 Only computer devices with components 10010-10030 are shown; however, it should be understood that it is not required to implement all of the shown components, and more or fewer components may be implemented instead.

[0278] In this embodiment, the method described in Embodiment 1 or 2 stored in memory 10010 can be further divided into one or more program modules and executed by one or more processors (such as processor 10020) to complete the embodiments of this application.

[0279] Example 6 This application also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements the methods described in any of the above embodiments.

[0280] In this embodiment, the computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the computer-readable storage medium may be an internal storage unit of a computer device, such as the hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Of course, the computer-readable storage medium may include both internal storage units and external storage devices of the computer device. In this embodiment, the computer-readable storage medium is typically used to store the operating system and various application software installed on the computer device, such as the program code of the method described in any of the above embodiments. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or will be output.

[0281] Example 7 This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods described in the above embodiments.

[0282] Obviously, those skilled in the art should understand that the modules or steps of the embodiments of this application described above can be implemented using general-purpose computer devices. They can be centralized on a single computer device or distributed across a network of multiple computer devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computer device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the embodiments of this application are not limited to any particular combination of hardware and software.

[0283] It should be noted that the above are merely preferred embodiments of this application and do not limit the scope of patent protection of this application. Any equivalent structural or procedural changes made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of this application.

Claims

1. A method for processing live streams, characterized in that, Applied to edge computing nodes, the method includes: In response to a push request carrying an external stream identifier, authentication is performed to determine the stream session identifier corresponding to the external stream identifier; Configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier; Based on the stream session identifier, generate or forward the stream data corresponding to the live stream; The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

2. The method according to claim 1, characterized in that, Determining the stream session identifier corresponding to the external stream identifier includes: Using the external stream identifier as the query key, query the mapping cache, which is used to store the mapping relationship between the external stream identifier and the stream session identifier; If a historical stream session identifier corresponding to the external stream identifier exists in the mapping cache, obtain the status information corresponding to the historical stream session identifier; When the status information indicates that the historical stream session identifier is in a reconnection waiting state, the historical stream session identifier is determined as the stream session identifier corresponding to the external stream identifier.

3. The method according to claim 2, characterized in that, Obtaining the status information corresponding to the historical stream session identifier includes: Send a status query request for the historical stream session identifier to the stream name management center; Receive the status information returned by the stream name management center; Correspondingly, after determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier, the method further includes: Generate a reconnection event to characterize this push stream as a reconnection push stream; Send the reconnection event to the stream name management center.

4. The method according to claim 2, characterized in that, Determining the stream session identifier corresponding to the external stream identifier further includes: If there is no historical stream session identifier corresponding to the external stream identifier in the mapping cache, or if the historical stream session identifier is not in a reconnection waiting state, a stream session identifier request is sent to the stream name management center. Receive the new flow session identifier returned by the flow name management center based on the flow session identifier request; The new stream session identifier is determined to be the stream session identifier corresponding to the external stream identifier; Write the mapping relationship between the external stream identifier and the new stream session identifier into the mapping cache.

5. The method according to claim 4, characterized in that, After sending a stream session identifier request to the stream name management center, the process also includes: If the new stream session identifier is not received within the preset timeout threshold, the stream session identifier request is resent; If the new stream session identifier is not received after resending the stream session identifier request, the push request is rejected and an alarm message is output.

6. The method according to claim 2, characterized in that, The mapping cache is a distributed cache cluster; Correspondingly, using the external stream identifier as the query key, querying the mapping cache includes: In the event that the push node corresponding to the live stream is switched, the distributed cache cluster is queried using the external stream identifier as the query key to obtain the historical stream session identifier corresponding to the external stream identifier.

7. The method according to claim 1, characterized in that, Generating or forwarding the stream data corresponding to the live stream based on the stream session identifier includes: Generate the stream data corresponding to the live stream based on the stream session identifier; The stream data carrying the stream session identifier is forwarded to the downstream processing system; The downstream processing system includes at least one of a recording system, a screenshot system, and a transcoding system.

8. The method according to claim 1, characterized in that, Generating or forwarding the stream data corresponding to the live stream based on the stream session identifier includes: A distribution link establishment notification is sent to the content delivery network, the distribution link establishment notification carrying the stream session identifier, so that the content delivery network establishes a distribution link for the live stream based on the stream session identifier.

9. The method according to claim 1, characterized in that, After generating or forwarding the stream data corresponding to the live stream based on the stream session identifier, the method further includes: Generate a mapped state record containing the external stream identifier, the stream session identifier, the session identifier, and state information; Send the mapping status record to the stream name management center.

10. The method according to claim 1, characterized in that, The method further includes: If an interruption is detected in the live stream, an interruption event is generated; Send the interruption event to the stream name management center so that the state of the stream session identifier is updated based on the interruption event; The interruption events include active stop events that represent active shutdown, or network interruption events that represent network fluctuations.

11. The method according to claim 2 or 3, characterized in that, Determining the historical stream session identifier as the stream session identifier corresponding to the external stream identifier includes: If the historical stream session identifier is in a reconnection waiting state and the current time is within a preset reconnection waiting time window, the historical stream session identifier will be determined as the stream session identifier corresponding to the external stream identifier.

12. A method for processing stream session identifiers, characterized in that, Applied to a stream name management center, the method includes: Receive a stream session identifier request sent by an edge computing node, wherein the stream session identifier request is associated with an external stream identifier; Generate a stream session identifier based on the external stream identifier; Establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information; Send the streaming session identifier to the edge computing node; Based on the status events reported by the edge computing node, update the status information corresponding to the stream session identifier.

13. The method according to claim 12, characterized in that, Establishing and storing the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information includes: In the case of generating the stream session identifier, the mapping relationship is established, and the status information is set to the generating state; Correspondingly, after sending the streaming session identifier to the edge computing node, the method further includes: If it is determined that the stream session identifier has been successfully sent, the status information is updated from the generating state to the active state.

14. The method according to claim 12, characterized in that, Generate a stream session identifier based on the external stream identifier, including: Obtain the external stream identifier, current timestamp, and system internal key; Generate a verification code based on the external stream identifier, the current timestamp, and the system internal key; The stream session identifier is generated based on the verification code and the session number.

15. The method according to claim 14, characterized in that, Based on the external stream identifier, the current timestamp, and the system internal key, a verification code is generated, including: The external stream identifier, the current timestamp, and the system internal key are concatenated according to a preset format to obtain the data to be processed; The data to be processed is hashed using the HMAC-SHA256 algorithm to obtain digest data. The first 16 hexadecimal characters are extracted from the digest data to obtain the check code.

16. The method according to claim 14, characterized in that, Based on the checksum and session number, the stream session identifier is generated, including: Obtain the globally incrementing field number through atomic operations; Obtain the external flow identifier prefix corresponding to the external flow identifier; The external stream identifier prefix, the session number, and the checksum are combined to obtain the stream session identifier.

17. The method according to claim 12, characterized in that, Generate a stream session identifier based on the external stream identifier, including: The stream session identifier is generated based on at least one of a random identifier generation algorithm, a snowflake algorithm, or a decentralized identifier generation algorithm.

18. The method according to claim 12, characterized in that, The status information includes the following states: generating, active, waiting for reconnection, invalid, and recycling.

19. The method according to claim 18, characterized in that, Based on the status events reported by the edge computing node, update the status information corresponding to the stream session identifier, including: Upon receiving a network interruption event reported by the edge computing node, the status information corresponding to the stream session identifier is updated from active to reconnection waiting state. Keep the content delivery network distribution link corresponding to the stream session identifier in an active state.

20. The method according to claim 19, characterized in that, After updating the status information corresponding to the stream session identifier from the active state to the reconnection waiting state, the process also includes: If a reconnection event corresponding to the stream session identifier is received within the preset reconnection waiting time window, the status information corresponding to the stream session identifier is updated from the reconnection waiting state to the active state. The reconnection event is used to instruct the edge computing node to reuse the stream session identifier in the reconnection push stream.

21. The method according to claim 19, characterized in that, After updating the status information corresponding to the stream session identifier from the active state to the reconnection waiting state, the process also includes: If no reconnection event corresponding to the stream session identifier is received within the preset reconnection waiting time window, the status information corresponding to the stream session identifier is updated from the reconnection waiting state to the failure state; or, Upon receiving an active stop event reported by the edge computing node, the status information corresponding to the stream session identifier is updated to an invalid state.

22. The method according to claim 21, characterized in that, After updating the status information corresponding to the stream session identifier to an invalid state, the process also includes: If the duration during which the stream session identifier is in an invalid state reaches a preset recycling duration, the mapping relationship will be archived to cold storage. Update the status information corresponding to the stream session identifier to the recycling status.

23. The method according to claim 12, characterized in that, Based on the status events reported by the edge computing node, update the status information corresponding to the stream session identifier, including: Receive the mapping status record or interruption event asynchronously reported by the edge computing node; Based on the mapping state record or the interruption event, update the mapping relationship and the state information in the persistent storage.

24. The method according to claim 12, characterized in that, The method further includes: Receive a status query request sent by the edge computing node, the status query request carrying a historical stream session identifier; Query the status information corresponding to the historical stream session identifier; Return the status information corresponding to the historical stream session identifier to the edge computing node; The status information is used to indicate whether the reuse of the historical stream session identifier is allowed.

25. The method according to claim 12, characterized in that, After sending the streaming session identifier to the edge computing node, the process further includes: The stream session identifier is sent to the configuration center of the downstream system so that the downstream system can establish a corresponding receiving channel based on the stream session identifier. The downstream system includes at least one of a recording system and a content distribution network.

26. A live stream processing device, characterized in that, The device, applied to edge computing nodes, includes: The determination module is used to determine the stream session identifier corresponding to the external stream identifier in response to a push request carrying an external stream identifier through authentication; The configuration module is used to configure the internal processing identifier of the live stream corresponding to the push request as the stream session identifier; The processing module is used to generate or forward the stream data corresponding to the live stream based on the stream session identifier; The external stream identifier is used for user-side push stream authentication, and the stream session identifier is used as the internal processing identifier of the live stream in the edge computing node and its downstream processing links.

27. A streaming session identifier processing device, characterized in that, The device, applied to a stream name management center, includes: The receiving module is used to receive a stream session identifier request sent by an edge computing node, wherein the stream session identifier request is associated with an external stream identifier; The generation module is used to generate a stream session identifier based on the external stream identifier; The storage module is used to establish and store the mapping relationship between the external stream identifier, the stream session identifier, the session identifier, and the status information; The sending module is used to send the stream session identifier to the edge computing node; The update module is used to update the status information corresponding to the stream session identifier based on the status events reported by the edge computing node.

28. A computer device, characterized in that, include: At least one processor; and 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 to 25.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 25.

30. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 25.

Images