Data transmission method and apparatus, and electronic device, storage medium and program product

Abstract

Disclosed in the present embodiment are a data transmission method and apparatus, and an electronic device and a computer storage medium. The method comprises: receiving a plurality of service flows; when the plurality of service flows have the same service identifier, on the basis of the service identifier and a destination address that are carried in the service flows having the same service identifier, and a pre-acquired mapping relationship between service identifiers and multicast addresses, determining a multicast address corresponding to the service identifier, and replacing the destination address in the service flows having the same service identifier with the multicast address corresponding to the service identifier, so as to obtain a multicast data flow; and transmitting the multicast data flow to a bearer network egress device, such that the bearer network egress device replaces the multicast address in the multicast data flow with the destination address on the basis of an identified and recorded mapping relationship between the multicast addresses and destination addresses, so as to obtain a unicast service flow.

Description

Data transmission method, device, electronic device, storage medium and program product

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 202410058066.X, application date January 15, 2024, and name “Data transmission method, device, electronic device and storage medium”, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application belongs to the technical field of transmission and bearing, and in particular relates to a data transmission method, device, electronic device, storage medium and program product. Background Art

[0004] In related technologies, the point-to-multipoint service of Internet vendors refers to the service of distributing the same unicast traffic to each user device. The point-to-multipoint service can be implemented through the bearer network of the operator network. Since the bearer network needs to transmit multiple copies of the same unicast traffic, the bearer network occupies a large amount of bandwidth. Summary of the Invention

[0005] Embodiments of the present application provide a data transmission method, apparatus, electronic device, storage medium, and program product.

[0006] An embodiment of the present application provides a data transmission method, which is applied to a bearer network ingress device, and includes:

[0007] Receive multiple business flows;

[0008] When the multiple service flows have the same service identifier, determining the multicast address corresponding to the service identifier according to the service identifier and the destination address carried in the service flow with the same service identifier and the pre-acquired mapping relationship between the service identifier and the multicast address, replacing the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier, and obtaining a multicast data stream;

[0009] The multicast data stream is transmitted to a bearer network egress device, so that the bearer network egress device replaces the multicast address in the multicast data stream with the destination address according to the identified and recorded mapping relationship between the multicast address and the destination address, thereby obtaining a unicast service stream.

[0010] In some embodiments, the replacing the destination address in the business flow with the same business identifier with the multicast address corresponding to the business identifier to obtain a multicast data stream includes: when the business flow with the same business identifier meets the set conditions, replacing the destination address in the business flow with the same business identifier with the multicast address corresponding to the business identifier to obtain a multicast data stream; wherein the set conditions include but are not limited to one of the following conditions: the number of destination addresses corresponding to the business flow with the same business identifier is greater than or equal to the set number, and the continuous reception time of the business flow with the same business identifier is greater than or equal to the first set time.

[0011] It can be seen that when the bearer network entry device determines that the number of destination addresses corresponding to business flows with the same business identifier is greater than or equal to the set number, or when it determines that the continuous reception time of business flows with the same business identifier is greater than or equal to the first set time, the destination address in the business flow will be replaced by a multicast address; when the number of destination addresses corresponding to business flows with the same business identifier is greater than or equal to the set number, it can be considered that there are more user devices corresponding to the business flows with the same business identifier, and when the continuous reception time of business flows with the same business identifier is greater than or equal to the first set time, it can be considered that the bearer network entry device can receive business flows with the same business identifier more stably. Therefore, the embodiment of the present application can convert business flows with the same business identifier into multicast data streams when it is necessary to send business flows with the same business identifier to a large number of users, or when business flows with the same business identifier are received more stably; when receiving business flows with the same business identifier, the business flows with the same business identifier will not be directly converted into multicast data streams immediately. Therefore, the network device forwarding overhead and signaling overhead in the process of converting business flows to multicast data streams can be reduced to a certain extent.

[0012] In some embodiments, replacing the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream includes: transmitting the service flow with the same service identifier to the bearer network exit device; after receiving the multicast join message sent by the bearer network exit device, replacing the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream.

[0013] It can be seen that the bearer network ingress device can convert the service flow into a multicast data flow after receiving the multicast join message sent by the bearer network egress device; since the bearer network ingress device can determine that the bearer network egress device has completed the preparation process for receiving the multicast data flow after receiving the multicast join message sent by the bearer network egress device, therefore, converting the service flow into a multicast data flow and sending the multicast data flow to the bearer network egress device via multicast can enable the bearer network egress device to receive the multicast data flow more reliably.

[0014] In some embodiments, the method also includes: when the destination address carried by the first business flow in the business flow with the same business identifier is a newly added destination address, the first business flow is transmitted to the bearer network exit device, and after waiting for a second set time period, the first business flow transmitted to the bearer network exit device is blocked; the newly added destination address is a destination address not included in the historical business flow received by the bearer network entry device; the bearer network exit device is used to establish a mapping relationship between the business identifier and the newly added destination address based on the received first business flow.

[0015] It can be seen that when the bearer network ingress device determines that the destination address carried by the first service flow is a newly added destination address, it will not immediately convert the first service flow into a multicast data flow, but can transmit the first service flow to the bearer network egress device. In this way, the bearer network egress device can determine the mapping relationship between the newly added destination address and the service identifier, and thus can replace the multicast address in the multicast data flow with the newly added destination address based on the mapping relationship between the newly added destination address and the service identifier, which is conducive to the sending of unicast service flows to user devices with the newly added destination addresses.

[0016] In some embodiments, the method also includes: when the traffic of the service flow with the first destination address within a set statistical period is lower than the traffic threshold, sending a notification message carrying the first destination address to the bearer network export device, and the notification message indicates a notification to stop replacing the multicast address in the multicast data stream with the first destination address.

[0017] It can be seen that if the traffic of the business flow with the first destination address within the set statistical period is lower than the traffic threshold, it can be considered that the traffic of the business flow with the first destination address within the set statistical period is stopped or interrupted. At this time, by sending a notification message carrying the first destination address to the bearer network export device, the bearer network export device can no longer convert the multicast data stream into the corresponding unicast business flow.

[0018] In some embodiments, the service identifier is located in an Internet Protocol Version 6 (IPv6) extension header of the service flow.

[0019] It can be seen that the bearer network ingress device can determine the service identifier of the service flow by analyzing the IPv6 extension header of the service flow, that is, the bearer network ingress device can determine the service identifier of the service flow relatively easily.

[0020] The present application also provides another data transmission method, which is applied to a bearer network egress device and includes:

[0021] receiving a multicast data stream sent by the bearer network ingress device; the bearer network ingress device is configured to determine, based on a service identifier and a destination address carried in a service flow having the same service identifier and a pre-acquired mapping relationship between the service identifier and the multicast address, the multicast address corresponding to the service identifier, and replace the destination address in the service flow having the same service identifier with the multicast address corresponding to the service identifier, thereby obtaining a multicast data stream;

[0022] According to the identified and recorded mapping relationship between the multicast address and the at least one destination address, the multicast address in the multicast data stream is replaced with a first destination address among the at least one destination address to obtain a unicast service stream; the first destination address is any one of the at least one destination address;

[0023] The unicast service flow is sent to a first user equipment, where the address of the first user equipment is the first destination address.

[0024] In some embodiments, before receiving the multicast data stream sent by the bearer network entry device, the method also includes: receiving at least one service stream; determining the mapping relationship between the multicast address and at least one destination address based on the service identifier and destination address carried in the at least one service stream, and the pre-acquired mapping relationship between the service identifier and the multicast address.

[0025] It can be seen that the bearer network export device can accurately determine the mapping relationship between the multicast address and at least one destination address based on the service identifier and destination address carried in at least one service flow, and the pre-acquired mapping relationship between the service identifier and the multicast address, thereby facilitating the conversion of the multicast data stream into a unicast service stream based on the mapping relationship between the multicast address and at least one destination address.

[0026] In some embodiments, before receiving the multicast data stream sent by the bearer network ingress device, the method also includes: the bearer network exit device receives a service flow with the same service identifier, and generates a multicast join message based on the service identifier of the service flow with the same service identifier, and the multicast join message is used to request the transmission of the multicast data stream with the service identifier; and sends the multicast join message to the bearer network ingress device.

[0027] It can be seen that the bearer network ingress device can convert the service flow into a multicast data flow after receiving the multicast join message sent by the bearer network egress device; since the bearer network ingress device can determine that the bearer network egress device has completed the preparation process for receiving the multicast data flow after receiving the multicast join message sent by the bearer network egress device, therefore, converting the service flow into a multicast data flow and sending the multicast data flow to the bearer network egress device via multicast can enable the bearer network egress device to receive the multicast data flow more reliably.

[0028] In some embodiments, the method further includes: upon receiving a first service flow and a first multicast data flow with the same service identifier, sending the first service flow to a second user equipment, where the address of the second user equipment is the destination address in the first service flow.

[0029] It can be seen that when the bearer network export device receives the first service flow and the first multicast data flow with the same service identifier, the first service flow can be sent to the second user device first. In this way, without the need to convert the multicast data flow into a unicast service flow, the second user device can receive the corresponding service flow more promptly, which is conducive to meeting the actual needs of the second user device.

[0030] The present application also provides a data transmission device, which is applied to a bearer network ingress device and includes:

[0031] A receiving module configured to receive multiple service flows;

[0032] A first processing module is configured to, when the multiple service flows have the same service identifier, determine, based on the service identifier and destination address carried in the service flow with the same service identifier and a pre-acquired mapping relationship between the service identifier and the multicast address, the multicast address corresponding to the service identifier, and replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream;

[0033] The second processing module is configured to transmit the multicast data stream to the bearer network egress device, so that the bearer network egress device replaces the multicast address in the multicast data stream with the destination address according to the mapping relationship between the identified and recorded multicast address and the destination address to obtain a unicast service stream.

[0034] The present application also provides another data transmission device, which is applied to a bearer network egress device and includes:

[0035] a third processing module configured to receive a multicast data stream sent by the bearer network ingress device; the bearer network ingress device being configured to determine, based on a service identifier and a destination address carried in a service stream having the same service identifier and a pre-acquired mapping relationship between the service identifier and the multicast address, the multicast address corresponding to the service identifier, and replace the destination address in the service stream having the same service identifier with the multicast address corresponding to the service identifier, thereby obtaining a multicast data stream;

[0036] a fourth processing module configured to replace the multicast address in the multicast data stream with a first destination address among the at least one destination address according to the identified and recorded mapping relationship between the multicast address and the at least one destination address, to obtain a unicast service stream; the first destination address being any one of the at least one destination address;

[0037] The sending module is configured to send the unicast service flow to a first user equipment, where the address of the first user equipment is the first destination address.

[0038] An embodiment of the present application further provides an electronic device, comprising a processor and a memory for storing a computer program that can be run on the processor; wherein the processor is configured to run the computer program to execute any one of the above-mentioned data transmission methods.

[0039] An embodiment of the present application further provides a computer storage medium having a computer program stored thereon, which implements any of the above-mentioned data transmission methods when executed by a processor.

[0040] An embodiment of the present application further provides a computer program product, including a computer program, which implements any of the above-mentioned data transmission methods when executed by a processor.

[0041] It can be seen that the bearer network ingress device can replace the destination address in the service flow with the same service identifier with a multicast address to obtain a multicast data stream, and transmit the multicast data stream to the bearer network egress device. Compared with the solution in the related art that requires transmitting multiple copies of the same unicast traffic through the bearer network, the multicast data stream transmitted by the bearer network ingress device to the bearer network egress device in the embodiment of the present application occupies less bandwidth, which is conducive to improving the effective utilization rate of the bandwidth of the bearer network.

[0042] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the technical solutions of the embodiments of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0044] FIG1 is a schematic diagram of a network structure for implementing data transmission of a point-to-multipoint service in the related art;

[0045] FIG2 is a flow chart of a data transmission method applied to a bearer network ingress device according to an embodiment of the present application;

[0046] FIG3 is a flow chart of a data transmission method applied to a bearer network egress device according to an embodiment of the present application;

[0047] FIG4 is a schematic diagram of a framework structure for transmitting data using a bearer network according to an embodiment of the present application;

[0048] FIG5 is a schematic diagram of another framework structure for transmitting data using a bearer network according to an embodiment of the present application;

[0049] FIG6 is a schematic structural diagram of a data transmission device applied to a bearer network ingress device according to an embodiment of the present application;

[0050] FIG7 is a schematic structural diagram of a data transmission device applied to a bearer network egress device according to an embodiment of the present application;

[0051] FIG8 is a schematic diagram of the composition structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] In related technologies, popular content in Internet services is usually point-to-multipoint services. Point-to-multipoint services refer to services that distribute the same unicast traffic to various user devices. For example, point-to-multipoint services can be video, games, finance, education, medical and other services; point-to-multipoint services can be top-level content (Over The Top, OTT) services or Internet Television (Interactive Personality TV, IPTV) services.

[0053] 1 , an OTT source 101 may provide OTT service data, an IPTV source 102 may provide IPTV service data, and a hybrid TV platform 103 may respectively form communication connections with the OTT source 101 and the IPTV source 102; the hybrid TV platform 103 may respectively form a communication connection with a broadband network gateway (BNG) 104, and the BNG 104 may be located in a network such as a content delivery network (CDN); illustratively, the BNG 104 may be implemented through a broadband remote access server (BRAS) or an IPTV service router (SR), the OTT source 101 may communicate with a home gateway (HG) 105 through the hybrid TV platform 103 and the BRAS, and the IPTV source 102 may communicate with the HR 105 through the hybrid TV platform 103 and the IPTV SR. IPTV CDN 106 can transmit IPTV video-on-demand (VOD) service data to HG 105. HG 105 can establish communication connections with a digital set-top box (STB) 107, a computer device 108, or a smartphone 109. Here, computer device 108 can be a personal computer (PC) or a laptop.

[0054] For point-to-multipoint services, there are a large number of user devices accessing. Point-to-multipoint services are usually carried in unicast mode. There are tens of thousands or even millions of identical redundant traffic in the network, which will occupy a large amount of network bandwidth. At the same time, due to bandwidth limitations, it is impossible to provide higher quality transmission content.

[0055] In related technologies, multicast, as a communication method parallel to unicast and broadcast, can transmit data packets to all devices in a multicast group by using a specific multicast address.

[0056] When a device sends data to a group of devices, it doesn't need to send the data to every device. Instead, it sends the data to a specific multicast address, where all devices participating in the multicast group can receive it. For the sending device, data only needs to be sent once to reach all recipients. Multicast technology facilitates a variety of network services, including live TV broadcasts, distance education, telemedicine, online radio, multimedia conferencing, video surveillance, and other Internet information services.

[0057] In some embodiments, when multicast data transmission is performed based on Protocol Independent Multicast (PIM), it is necessary to join the established multicast tree hop by hop; when multicast data transmission is performed based on the Point 2 Multiple Point (P2MP) Multiprotocol Label Switching (MPLS) protocol, it is necessary to establish a multicast label forwarding path; when multicast data transmission is performed based on the Bit Indexed Explicit Replication (BIER) protocol, it is not necessary to explicitly build a multicast tree, nor is it necessary for intermediate nodes to maintain any multicast flow status. However, regardless of the multicast protocol used, multicast data packets must be sent from the source end and received and processed by the receiving end.

[0058] In related technologies, business systems do not provide good support for multicast. Except for a small number of services such as live TV, business data is usually transmitted from point to multipoint through unicast messages. The upgrade cost of the head end of the business system and the massive terminal equipment is huge, and it is difficult to implement in a short period of time.

[0059] With the continuous development of fifth-generation mobile communication technology (5G) and vertical industries, various new services are constantly emerging, placing increasingly stringent demands on the bearer network for differentiated services.

[0060] Application-aware IPv6 Networking (APN6) based on IPv6 fully utilizes the multiple programmable spaces inherent in IPv6 packets, Segment Routing IPv6 (SRv6) packets based on the IPv6 forwarding plane, or Generalized Segment Routing over IPv6 (G-SRv6) packets. This extends the network's reach to applications, allowing application information and its requirements to be carried into the network from the source. This enables the network to effectively and cost-effectively perceive the differentiated needs of applications and provide corresponding application-level network services.

[0061] In the Internet Engineering Task Force (IETF), APN6 defines the protocol framework through the draft-li-apn-framework document, the message encapsulation format through the draft-li-apn-ipv6-encap document, and the forwarding option format through the draft-li-apn-header document, providing a technical foundation for Internet business information perception.

[0062] In related technologies, internet vendors' point-to-multipoint services require a large-scale upgrade of their service systems to enable them to support the encoding and distribution of multicast streams. Furthermore, internet vendors can address the pressure of unicast connections through other means, such as expanding servers, and lack the motivation to implement multicast upgrades. However, for network carriers, internet point-to-multipoint services place significant pressure on network bandwidth, and without generating additional revenue, they may squeeze bandwidth required by other services, forcing network expansion and increasing network investment costs.

[0063] In related technologies, point-to-multipoint services can be implemented through the carrier network's bearer network; internet service data distribution can be achieved through a two-tier CDN set up by the carrier network. The first tier of the two-tier CDN is located in the first tier content center, and the second tier is connected to the edge service node of the BRAS. While transmitting service data through the CDN alleviates traffic bandwidth pressure to a certain extent, there may still be thousands of identical unicast traffic flows between the edge service node and each user device, resulting in a significant level of redundant traffic. This issue urgently needs to be addressed from the network side, ensuring that point-to-multipoint internet service traffic is forwarded in a multicast manner.

[0064] In summary, in related technologies, point-to-multipoint services can be implemented through the bearer network of the operator's network. Since the bearer network needs to transmit multiple copies of the same unicast traffic, the bearer network occupies a large amount of bandwidth.

[0065] In response to the above technical problems, the technical solutions of the embodiments of the present application are proposed.

[0066] The following is a further detailed description of the embodiments of the present application in conjunction with the accompanying drawings and examples. It should be understood that the embodiments provided herein are merely for explaining the embodiments of the present application and are not intended to limit the embodiments of the present application. In addition, the embodiments provided below are partial embodiments for implementing the present application, rather than providing all embodiments for implementing the present application. In the absence of conflict, the technical solutions described in the embodiments of the present application can be implemented in any combination.

[0067] It should be noted that, in the embodiments of the present application, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a method or apparatus comprising a series of elements includes not only the elements explicitly stated, but also other elements not explicitly listed, or also includes elements inherent to the implementation of the method or apparatus. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other related elements (such as steps in the method or units in the apparatus, for example, a unit may be a portion of a circuit, a portion of a processor, a portion of a program or software, etc.) in the method or apparatus comprising the element.

[0068] The data transmission method provided in the embodiment of the present application includes a series of steps, but the data transmission method provided in the embodiment of the present application is not limited to the recorded steps. Similarly, the data transmission device provided in the embodiment of the present application includes a series of modules, but the device provided in the embodiment of the present application is not limited to including the modules explicitly recorded, and may also include modules that need to be set up to obtain relevant information or perform processing based on information.

[0069] An embodiment of the present application provides a data transmission method using a bearer network entry device. In the embodiment of the present application, the bearer network entry device may be an Internet Protocol (IP) bearer network entry provider edge (PE) device.

[0070] FIG2 is a flow chart of a data transmission method applied to a bearer network ingress device according to an embodiment of the present application. As shown in FIG2 , the process may include:

[0071] Step 201: Receive multiple service flows.

[0072] For example, the point-to-multipoint service provided by the Internet vendor can be forwarded to the operator's bearer network via unicast. The bearer network entry device or bearer network exit device in the operator's bearer network can activate application awareness technology to identify the received service flow. The bearer network exit device can be an IP bearer network exit PE device.

[0073] In some embodiments, Internet applications used for point-to-multipoint services within a certain range can be divided according to the application group identity document (ID). Different application group IDs can be assigned to different applications. For example, different application group IDs can be assigned to applications such as video, games, finance, education, and medical care. Of course, application group IDs can also be assigned to other applications. Furthermore, user group IDs can be assigned for specific services of each application. For example, referring to Table 1, the application group ID assigned to application A is 100, the application group ID assigned to application B is 101, the user group ID assigned to service a of application A is 1, the user group ID assigned to service b of application A is 2, and the user group ID assigned to service c of application B is 1.

[0074] Table 1

[0075] In some embodiments, the received service flow can be identified by other means, for example, by analyzing the contents of the message quintuple in the service flow, where the message quintuple includes the source address, destination address, source port, destination port, and protocol number.

[0076] Step 202: When multiple service flows have the same service identifier, determine the multicast address corresponding to the service identifier based on the service identifier and destination address carried in the service flow with the same service identifier, and the mapping relationship between the service identifier and the multicast address obtained in advance, replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier, and obtain a multicast data stream.

[0077] In an embodiment of the present application, the service identifier of each service flow can be determined by analyzing the content of each service flow in multiple service flows; illustratively, the service identifier of the service flow may include at least one of an application group ID and a user group ID.

[0078] In some embodiments, a network management system or controller may pre-plan a multicast address pool and allocate multicast addresses in the multicast address pool based on different specific service identifiers. After determining the mapping relationship between the service identifier and the multicast address, the network management system or controller may notify the mapping relationship between the service identifier and the multicast address to each edge device node of the IP bearer network. The edge device node of the IP bearer network may be a bearer network ingress device or a bearer network egress device. The edge device node may identify the multicast address corresponding to the service identifier in each service flow based on the mapping relationship between the service identifier and the multicast address, as well as the service identifier and destination address in each service flow.

[0079] Here, the mapping relationship between the service identifier and the multicast address is similar to the program table in IPTV live TV, but the mapping relationship does not need to be sent to each user device, but only needs to be notified to each edge device node of the IP bearer network.

[0080] For example, referring to Table 2, when the application group ID is 100 and the user group ID is 1, the multicast address is FF0E::1; when the application group ID is 100 and the user group ID is 2, the multicast address is FF0E::2; when the application group ID is 101 and the user group ID is 1, the multicast address is FF0E::3.

[0081] Table 2

[0082] Step 203: Transmit the multicast data stream to the bearer network egress device, so that the bearer network egress device replaces the multicast address in the multicast data stream with the destination address according to the identified and recorded mapping relationship between the multicast address and the destination address, thereby obtaining a unicast service stream.

[0083] In an embodiment of the present application, the bearer network entry device is responsible for converting the identified service flow into the corresponding multicast data flow. The bearer network entry device can forward the multicast data flow according to the ordinary IP multicast message, and the bearer network entry device can import the multicast data flow into the network side multicast bearer tunnel.

[0084] For example, the protocols supported by the network-side multicast bearer tunnel include but are not limited to PIM, P2MP MPLS, BIER, etc. The multicast message forwarding process in the IP bearer network can refer to the Border Gateway Protocol (BGP) Multicast Virtual Private Network (MVPN) architecture standard defined in RFC6513 and RFC6514 documents, as well as the BIER MVPN standard defined in RFC8556.

[0085] In an embodiment of the present application, the destination address may be the address of the user device that ultimately receives the service flow. The bearer network egress device is responsible for recording the mapping relationship between the service identifier of the identified service flow and the destination address. In some embodiments, the bearer network egress device may establish such a mapping relationship based on the initially sent unicast service flow. For example, the bearer network egress device may directly obtain the destination address through the IP message of the unicast service flow, thereby, in combination with the mapping relationship between the service identifier and the multicast address issued by the controller, an association may be established between the multicast address and the destination address. The bearer network egress device may replace the multicast address in the multicast data flow with the destination address based on the mapping relationship between the multicast address and the destination address, thereby sending the unicast service flow to the corresponding user device based on the destination address. If the bearer network egress device does not replace the multicast address in the multicast data flow with the destination address, and the access network of the user device does not support multicast services, the bearer network egress device cannot send the multicast data flow to the user device.

[0086] Exemplarily, each multicast address can form a mapping relationship with at least one destination address; referring to Table 3, when the application group ID is 100 and the user group ID is 1, the multicast address can be FF0E::1, and the destination addresses can be 2001::1 and 2001::2; when the application group ID is 100 and the user group ID is 2, the multicast address can be FF0E::1, and the destination address can be 2001::3; when the application group ID is 101 and the user group ID is 1, the multicast address can be FF0E::2, and the destination address can be 2001::2.

[0087] Table 3

[0088] In the embodiment of the present application, the bearer network egress device can convert the multicast address into the corresponding destination address based on the mapping relationship between the multicast address and the destination address, thereby converting the multicast data stream into a unicast service stream. The bearer network egress device can send each unicast service stream one by one to the user equipment corresponding to the destination address in a unicast manner.

[0089] In actual applications, steps 201 to 203 can be implemented based on the processor of the bearer network entry device. The above-mentioned processor can be at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a central processing unit (CPU), a controller, a microcontroller, and a microprocessor.

[0090] It can be seen that the bearer network ingress device can replace the destination address in the service flow with the same service identifier with a multicast address to obtain a multicast data stream, and transmit the multicast data stream to the bearer network egress device. Compared with the solution in the related art that requires transmitting multiple copies of the same unicast traffic through the bearer network, the multicast data stream transmitted by the bearer network ingress device to the bearer network egress device in the embodiment of the present application occupies less bandwidth, which is conducive to improving the effective utilization rate of the bandwidth of the bearer network.

[0091] In some embodiments of the present application, the service identifier may be located in an IPv6 extension header of the service flow. The IPv6 extension header may be an APN extension header.

[0092] For example, according to the IETF draft-li-apn-ipv6-encap document, when the service flow is an IPv6 packet, the IPv6 packet can carry the application-aware networking (APN) header information through the extended header Hop by Hop (HBH) option header, destination option header (Destination Option Header, DOH), and segment routing header (SRH) type-length-value (Type-Length-Value, TLV). In the APN header information, the encapsulation format of the APN ID can be the format defined in the draft-li-apn-header document; for example, the APN ID can include an application group ID (APP-Group-ID), a user group ID (USER-Group-ID), and a reserved (Reserve) field.

[0093] Illustratively, after obtaining the multicast data stream, the bearer network ingress device may further remove the IPv6 extension header carried in the multicast data stream.

[0094] It can be seen that the bearer network ingress device can determine the service identifier of the service flow by analyzing the IPv6 extension header of the service flow, that is, the bearer network ingress device can determine the service identifier of the service flow relatively easily.

[0095] In some embodiments, it is necessary to convert a service flow into a multicast data flow only when a service flow with the same service identifier needs to be sent to a large number of users, or when a service flow with the same service identifier is received relatively stably.

[0096] In some embodiments of the present application, the process of replacing the destination address in a service flow having the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data flow may include:

[0097] When a service flow with the same service identifier meets the set conditions, the destination address in the service flow with the same service identifier is replaced with the multicast address corresponding to the service identifier to obtain a multicast data flow;

[0098] Among them, the set conditions include but are not limited to one of the following conditions: the number of destination addresses corresponding to business flows with the same business identifier is greater than or equal to the set number, and the continuous reception time of business flows with the same business identifier is greater than or equal to the first set time.

[0099] Here, the set number and the first set time can be determined according to actual needs; for example, the set number can be 5000, 10000, 50000, etc., and the first set time can be 8 minutes, 10 minutes, 12 minutes, etc.

[0100] In some embodiments, when the bearer network ingress device determines that the service flow with the same service identifier meets the set conditions, it can block the service flow transmitted to the bearer network egress device. In this way, the conversion of unicast service flow to multicast data flow can be achieved more reliably.

[0101] In some embodiments, when a service flow with the same service identifier does not meet the set conditions, there is no need to replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier. Instead, the service flow with the same service identifier can be transmitted to the bearer network export device via unicast.

[0102] It can be seen that when the bearer network ingress device determines that the number of destination addresses corresponding to service flows with the same service identifier is greater than or equal to a set number, or when it determines that the continuous reception time of service flows with the same service identifier is greater than or equal to a first set time, it will replace the destination address in the service flow with a multicast address; when the number of destination addresses corresponding to service flows with the same service identifier is greater than or equal to a set number, it can be considered that there are many user devices corresponding to the service flows with the same service identifier, and when the continuous reception time of service flows with the same service identifier is greater than or equal to the first set time, it can be considered that the bearer network ingress device can receive service flows with the same service identifier more stably. Therefore, the embodiment of the present application can convert the service flow into a multicast data stream when it is necessary to send the service flow with the same service identifier to a large number of users, or when the service flow with the same service identifier is received more stably; the service flow with the same service identifier will not be directly converted into a multicast data stream when the service flow with the same service identifier is received. Therefore, the network device forwarding overhead and signaling overhead in the process of converting the service flow into the multicast data stream can be reduced to a certain extent, and the benefits of the process of converting the service flow into the multicast data stream can be improved.

[0103] In some embodiments of the present application, a process of replacing the destination address in a service flow having the same service identifier with a multicast address corresponding to the service identifier to obtain a multicast data flow may include:

[0104] Transmitting the service flow with the same service identifier to the bearer network egress device;

[0105] After receiving the multicast join message sent by the bearer network egress device, the destination address in the service flow with the same service identifier is replaced with the multicast address corresponding to the service identifier to obtain a multicast data flow.

[0106] In an embodiment of the present application, after receiving the identified service flow, the bearer network ingress device does not immediately convert the service flow into a multicast data flow, but can transmit the service flow with the same service identifier to the bearer network egress device.

[0107] After receiving the identified service flow, the bearer network egress device can simulate and generate the corresponding multicast group or multicast source group locally based on information such as the mapping relationship between the multicast address and the destination address.

[0108] Then, the bearer network egress device can query the multicast upstream according to the process defined in the RFC6513 document and the RFC6514 document, and send a multicast join message to the bearer network ingress device.

[0109] Here, the mapping relationship between the multicast address and the destination address may be issued by the management and control system.

[0110] If there are two or more multicast upstreams, the optimal one is selected according to the relevant definitions of the RFC6514 document. Alternatively, the primary and backup multicast upstreams can be selected according to the relevant definitions of the RFC9026 document, thereby introducing two multicast data streams. When the two multicast data streams reach the bearer network egress device, the bearer network egress device can discard one of the multicast data streams based on the reverse path forwarding (RPF) check rules.

[0111] In some embodiments, according to the relevant definitions of RFC6513 and RFC6514 documents, the bearer network ingress device needs to establish a multicast forwarding path after receiving the multicast join message sent by the bearer network egress device before the service flow can be converted into a multicast data flow. Otherwise, if the bearer network ingress device converts the service flow into a multicast data flow without receiving the multicast join message, it may cause packet loss of the multicast data flow on the bearer network egress side.

[0112] In some embodiments, after receiving the multicast join message, the bearer network ingress device may block the service flow transmitted to the bearer network egress device. In this way, the conversion of the unicast service flow to the multicast data flow can be achieved more reliably.

[0113] It can be seen that the bearer network ingress device can convert the service flow into a multicast data flow after receiving the multicast join message sent by the bearer network egress device; since the bearer network ingress device can determine that the bearer network egress device has completed the preparation process for receiving the multicast data flow after receiving the multicast join message sent by the bearer network egress device, therefore, converting the service flow into a multicast data flow and sending the multicast data flow to the bearer network egress device via multicast can enable the bearer network egress device to receive the multicast data flow more reliably.

[0114] In an embodiment of the present application, in order to identify the increase and decrease in the number of user devices receiving the service flow, the bearer network entry device can record a mapping table of service identifiers and destination addresses; each row in the mapping table of service identifiers and destination addresses includes a service identifier and destination address in a service flow.

[0115] Referring to Table 4, when the application group ID is 100 and the user group ID is 1, the destination addresses can be 2001::1 and 2001::2; when the application group ID is 100 and the user group ID is 2, the destination address can be 2001::3; when the application group ID is 101 and the user group ID is 1, the destination addresses can be 2001::2 and 2001::3.

[0116] Table 4

[0117] In some embodiments of the present application, the bearer network ingress device may determine a first service flow among service flows having the same service identifier. The first service flow may be any service flow among the service flows having the same service identifier.

[0118] When the bearer network entry device determines that the destination address carried by the first service flow is a newly added destination address, it may not block the unicast service flow corresponding to the newly added destination address, but may establish a mapping relationship between the service identifier and the newly added destination address. After transmitting the first service flow to the bearer network exit device, it may wait for a second set time period, and then block the first service flow transmitted to the bearer network exit device.

[0119] Here, the newly added destination address is a destination address that is not included in the historical service flow received by the bearer network ingress device.

[0120] Here, the second set time length can be determined according to actual needs. For example, the second set time length can be 8 minutes, 10 minutes, 12 minutes, etc.

[0121] It can be seen that when the bearer network ingress device determines that the destination address carried by the first service flow is a newly added destination address, it will not immediately convert the first service flow into a multicast data flow, but can transmit the first service flow to the bearer network egress device. In this way, the bearer network egress device can determine the mapping relationship between the newly added destination address and the service identifier, and thus can replace the multicast address in the multicast data flow with the newly added destination address based on the mapping relationship between the newly added destination address and the service identifier, which is conducive to the sending of unicast service flows to user devices with the newly added destination addresses.

[0122] It is understandable that when the number of user devices receiving service flows decreases, since the operations performed on the user devices only interact with the service system providing the service flows, the bearer network entry device and the bearer network exit device will not receive any signaling notifications. In this case, the bearer network entry device can periodically perform traffic statistics on the service flows and identify the reduction in the number of user devices receiving the service flows based on the traffic statistics results.

[0123] In some embodiments of the present application, the bearer network ingress device can determine the traffic of the business flow with the first destination address within a set statistical period; when the traffic of the business flow with the first destination address within the set statistical period is lower than the traffic threshold, it can be determined that the business flow reaching the first destination address is interrupted, and there is no need to convert the business flow with the first destination address into a multicast data stream; the bearer network ingress device can send a notification message carrying the first destination address to the bearer network egress device, and the notification message indicates a notification to stop replacing the multicast address in the multicast data stream with the first destination address.

[0124] Exemplarily, the notification message may be a BGP MVPN peer announcement, and the BGP MVPN peer announcement may be carried in extended BGP MVPN signaling.

[0125] Exemplarily, a new route type (Route Type) notification message may be extended according to the RFC6514 document. The new route type notification message is the notification message carrying the first destination address.

[0126] The notification message of the newly added route type can be reflected in Table 5. In Table 5, the route type field occupies one octet used by the Internet standard, the length field occupies one octet, and the length of the specific route type field is variable.

[0127] Table 5

[0128] Illustratively, the notification message carrying the first destination address may be a newly added routing type notification, and the Network Layer Reachability Information (NLRI) may be defined according to Table 6.

[0129] Table 6

[0130] In Table 6, the length of the Route Distinguisher (RD) field is 8 octets, the length of the Service Source Address Length field is 1 octet, and the length of the Service Source Address field is variable. The length of the Service User Address Length field is 1 octet, and the length of the Service User Address field is variable. The length of the Originator IP Length field is 1 octet, and the length of the Originator IP Address field is variable.

[0131] It can be seen that if the traffic of the business flow with the first destination address within the set statistical period is lower than the traffic threshold, it can be considered that the traffic of the business flow with the first destination address within the set statistical period is stopped or interrupted. At this time, by sending a notification message carrying the first destination address to the bearer network export device, the bearer network export device can no longer convert the multicast data stream into the corresponding unicast business flow.

[0132] FIG3 is a flow chart of a data transmission method applied to a bearer network egress device according to an embodiment of the present application. As shown in FIG3 , the process may include:

[0133] Step 301: Receive the multicast data stream sent by the bearer network entry device; the bearer network entry device is used to determine the multicast address corresponding to the service identifier based on the service identifier and destination address carried in the service flow with the same service identifier, and the pre-acquired mapping relationship between the service identifier and the multicast address, and replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain the multicast data stream.

[0134] Step 302: Based on the identified and recorded mapping relationship between the multicast address and at least one destination address, the multicast address in the multicast data stream is replaced with a first destination address among the at least one destination address to obtain a unicast service stream; the first destination address is any one of the at least one destination address.

[0135] Step 303: Send the unicast service flow to the first user equipment, where the address of the first user equipment is the first destination address.

[0136] In practical applications, steps 301 to 303 may be implemented based on a processor of a bearer network egress device, which may be at least one of an ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor.

[0137] It can be seen that the bearer network ingress device can replace the destination address in the service flow with the same service identifier with a multicast address to obtain a multicast data stream, and transmit the multicast data stream to the bearer network egress device. Compared with the solution in the related art that requires transmitting multiple copies of the same unicast traffic through the bearer network, the multicast data stream transmitted by the bearer network ingress device to the bearer network egress device in the embodiment of the present application occupies less bandwidth, which is conducive to improving the effective utilization rate of the bandwidth of the bearer network.

[0138] In some embodiments of the present application, the bearer network exit device may also receive at least one service stream before receiving the multicast data stream sent by the bearer network entry device; and determine the mapping relationship between the multicast address and at least one destination address based on the service identifier and destination address carried in the at least one service stream, and the pre-acquired mapping relationship between the service identifier and the multicast address.

[0139] It can be seen that the bearer network export device can accurately determine the mapping relationship between the multicast address and at least one destination address based on the service identifier and destination address carried in at least one service flow, and the pre-acquired mapping relationship between the service identifier and the multicast address, thereby facilitating the conversion of the multicast data stream into a unicast service stream based on the mapping relationship between the multicast address and at least one destination address.

[0140] In some embodiments of the present application, the bearer network egress device may also receive a service flow with the same service identifier before receiving the multicast data stream sent by the bearer network ingress device; generate a multicast join message based on the service identifier of the service flow with the same service identifier, and the multicast join message is used to request the transmission of the multicast data stream with the service identifier; and send the multicast join message to the bearer network ingress device.

[0141] It can be seen that the bearer network ingress device can convert the service flow into a multicast data flow after receiving the multicast join message sent by the bearer network egress device; since the bearer network ingress device can determine that the bearer network egress device has completed the preparation process for receiving the multicast data flow after receiving the multicast join message sent by the bearer network egress device, therefore, converting the service flow into a multicast data flow and sending the multicast data flow to the bearer network egress device via multicast can enable the bearer network egress device to receive the multicast data flow more reliably.

[0142] In some embodiments of the present application, the bearer network egress device may also send the first service flow to the second user device when receiving the first service flow and the first multicast data flow with the same service identifier, and the address of the second user device is the destination address in the first service flow.

[0143] In some embodiments, if a multicast entry established by a bearer network egress device has the same service identifier as an existing unicast service flow entry, the bearer network ingress device may determine whether it has received a multicast join message sent by the bearer network egress device. After the bearer network ingress device determines that it has received the multicast join message and establishes a multicast forwarding path, it may block the unicast data flow sent to the bearer network egress device. The type of data flow sent by the bearer network egress device to the user equipment can be a unicast service flow or a multicast data flow. For example, when the bearer network egress device stably sends data flows to the user equipment, it is not necessary to select a multicast mode or a unicast mode. When the bearer network egress device determines that a unicast data flow and a multicast data flow coexist, if the bearer network egress device has established a mapping relationship between a multicast address and a user address, and the bearer network ingress device has not blocked the unicast service flow, the bearer network egress device will, in the event of the coexistence of unicast data flows and multicast data flows, temporarily prioritize the unicast service flow for transmission.

[0144] In the first example, when the bearer network ingress device sends a unicast service flow to the bearer network egress device, no multicast data flow is generated, and the bearer network egress device can send the unicast service flow to the user equipment.

[0145] In the second example, after the bearer network ingress device blocks the unicast service flow transmitted to the bearer network egress device, the unicast service flow can be converted into a multicast data flow, and the bearer network egress device can receive the multicast data flow with the corresponding service identifier.

[0146] In the third example, when the bearer network ingress device converts a unicast service flow into a multicast data flow, if it determines that the destination address carried by the first service flow with the same service identifier is a newly added destination address, the unicast service flow and the multicast data flow coexist, and the unicast service flow can be preferentially forwarded. If the bearer network ingress device blocks the forwarding of the unicast service flow and can only receive the multicast data flow, the bearer network ingress device transmits the multicast data flow to the bearer network egress device.

[0147] In the fourth example, when the bearer network ingress device converts a unicast service flow into a multicast data flow, if the traffic of the service flow with the first destination address is lower than the traffic threshold within the set statistical period, it can be considered that the number of user devices receiving the service flow has decreased. In this case, the bearer network ingress device can notify the bearer network egress device through a message that the multicast data flow corresponding to the first destination address will no longer be converted into a unicast service flow, and the first destination address will be deleted. In the transient state before the bearer network egress device deletes the mapping relationship between the multicast address and the destination address, there will also be a situation where unicast data flow and multicast data flow coexist. In this transient state, unicast service flow forwarding is preferred. After the bearer network egress device receives the notification message carrying the first destination address, it can terminate the conversion of the multicast data flow into a unicast service flow with the first destination address.

[0148] It can be seen that when the bearer network export device receives the first service flow and the first multicast data flow with the same service identifier, the first service flow can be sent to the second user device first. In this way, without the need to convert the multicast data flow into a unicast service flow, the second user device can receive the corresponding service flow more promptly, which is conducive to meeting the actual needs of the second user device.

[0149] 4 and 5 , R1, R2, R3, R4, and R5 respectively represent different edge device nodes in the IP bearer network 401; terminal 1A, terminal 1B, terminal 2A, terminal 2B, terminal 3A, terminal 3B, and terminal 3C represent different user devices. For example, R4 and R5 are bearer network entry devices, and R1, R2, and R3 are bearer network exit devices.

[0150] 4 and 5 , when R4 and R5 receive a message carrying a service flow from server 402, they can determine the service identifier of the service flow from the APN extension header of the received message. This service identifier can be carried in the service flow when server 402 sends it, or it can be added to the service flow header by enterprise-side customer premises equipment (CPE).

[0151] Exemplarily, referring to Figure 5, the service flow sent by server 402 to R4 can carry the server address (SA), destination address, APN ID and data. For example, the destination address in the service flow sent by server 402 to R4 is 1A, and 1A is the destination address of terminal 1A.

[0152] 4 and 5 , after a service flow is transferred to IP bearer network 401, R4 and R5 can each determine whether the service flow can be converted into a multicast data flow. For example, R4 and R5 can determine whether the service flow can be converted into a multicast data flow based on the application group ID in the service flow and the predetermined applications capable of transmitting data flows via multicast. For example, after determining whether the service flow can be converted into a multicast data flow, each node in R4 and R5 can further determine the direction of the service flow. If the service flow is a data flow flowing from server 402 on the network side to the local data flow, it can determine that it is the bearer network entry device.

[0153] Any node among R4 and R5 can convert the service flow into a multicast data stream and send the multicast data stream to the bearer network exit device. For example, referring to Figure 5, R4 can send the multicast data stream to R1 and R2 through the bearer network 401. Exemplarily, the multicast data stream sent by R4 can carry the server address, multicast address and data, and the multicast address can be recorded as MCAST; exemplarily, the multicast data stream sent by R4 can also include the APN ID.

[0154] When a data stream flows out of IP bearer network 401, each node in R1, R2, and R3 can forward a unicast service stream with a service identifier to the corresponding user equipment. For example, each node in R1, R2, and R3 can determine whether it can receive the multicast data stream based on the application group ID in the service stream and the predetermined applications capable of transmitting data streams via multicast. For example, after determining whether it can receive the multicast data stream, each node in R1, R2, and R3 can determine the direction of the received multicast data stream. When it is necessary to convert the multicast data stream into a unicast service stream and send the unicast service stream to the user equipment, it can determine that it is the bearer network egress device.

[0155] 5 , the unicast service flow sent by R1 to terminal 1A may carry a server address, a destination address, an APN ID, and data. For example, the destination address carried in the unicast service flow sent by R1 to terminal 1A is 1A.

[0156] It should be noted that the roles of R1, R2, R3, R4 and R5 in the IP bearer network are not fixed and can play different roles according to the different directions of the service flow.

[0157] An embodiment of the present application proposes a method for a network device to adaptively convert a unicast service flow into a multicast data flow. Neither the head-end system nor the terminal system of the Internet service needs to be upgraded or modified for the multicast service. The edge device nodes of the operator's bearer network only need to use application-aware technology to identify the service flow and convert the unicast service flow into the multicast data flow.

[0158] By adopting the technical solution of the embodiment of the present application, there is no need to carry out large-scale multicast service modifications for different business systems. The redundant occupation of network bandwidth by the above-mentioned unicast business flow traffic can be greatly reduced, the IP bearer network bandwidth can be saved, the network resource utilization rate can be improved, and the operation of the original multicast bearer technology of the IP bearer network will not be affected. Only the edge device nodes of the IP bearer network need to be upgraded and modified.

[0159] The technical solution of the embodiment of the present application can adapt to the data transmission of point-to-multipoint services of various Internet service systems, does not require the service system to be aware of the multicast mode, and is easy to promote and apply in operator networks.

[0160] Those skilled in the art will understand that in the above-mentioned method of the specific implementation method, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0161] Based on the data transmission method proposed in the above embodiment, the embodiment of the present application also proposes a data transmission device.

[0162] FIG6 is a schematic structural diagram of a data transmission device applied to a bearer network ingress device according to an embodiment of the present application. As shown in FIG6 , the device may include:

[0163] Receiving module 601, configured to receive multiple service flows;

[0164] A first processing module 602 is configured to, when the multiple service flows have the same service identifier, determine, based on the service identifier and destination address carried in the service flows with the same service identifier and a pre-acquired mapping relationship between the service identifier and the multicast address, a multicast address corresponding to the service identifier, and replace the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream;

[0165] The second processing module 603 is configured to transmit the multicast data stream to the bearer network egress device, so that the bearer network egress device replaces the multicast address in the multicast data stream with the user address according to the mapping relationship between the identified and recorded multicast address and the user address, thereby obtaining a unicast service stream.

[0166] In some embodiments, the first processing module 602 is configured to replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain the multicast data flow, including:

[0167] When the service flow with the same service identifier meets the set conditions, replacing the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data flow;

[0168] Among them, the set conditions include at least one of the following: the number of destination addresses corresponding to the service flows with the same service identifier is greater than or equal to the set number, and the continuous reception time of the service flows with the same service identifier is greater than or equal to the first set time.

[0169] In some embodiments, the first processing module 602 is configured to replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain the multicast data flow, including:

[0170] Transmitting the service flow with the same service identifier to the bearer network egress device;

[0171] After receiving the multicast join message sent by the bearer network egress device, the destination address in the service flow with the same service identifier is replaced with the multicast address corresponding to the service identifier to obtain a multicast data flow.

[0172] In some embodiments, the first processing module 602 is further configured to transmit the first business flow in the business flows with the same business identifier to the bearer network exit device when the destination address carried by the first business flow is a newly added destination address, and after waiting for a second set time period, block the transmission of the first business flow to the bearer network exit device; the newly added destination address is a destination address not included in the historical business flow received by the bearer network entry device; the bearer network exit device is used to establish a mapping relationship between the business identifier and the newly added destination address based on the received first business flow.

[0173] In some embodiments, the first processing module 602 is further configured to send a notification message carrying the first destination address to the bearer network export device when the traffic of the service flow with the first destination address is lower than the traffic threshold within a set statistical period, and the notification message indicates a notification to stop replacing the multicast address in the multicast data stream with the first destination address.

[0174] In some embodiments, the service identifier is located in an IPv6 extension header of the service flow.

[0175] FIG7 is a schematic structural diagram of a data transmission device applied to a bearer network egress device according to an embodiment of the present application. As shown in FIG7 , the device may include:

[0176] The third processing module 701 is configured to receive a multicast data stream sent by the bearer network ingress device; the bearer network ingress device is configured to determine the multicast address corresponding to the service identifier based on the service identifier and destination address carried in the service stream with the same service identifier and a pre-acquired mapping relationship between the service identifier and the multicast address, and replace the destination address in the service stream with the same service identifier with the multicast address corresponding to the service identifier, thereby obtaining the multicast data stream;

[0177] a fourth processing module 702 configured to replace the multicast address in the multicast data stream with a first destination address among the at least one destination address based on the identified and recorded mapping relationship between the multicast address and the at least one destination address, to obtain a unicast service stream; the first destination address being any one of the at least one destination address;

[0178] The sending module 703 is configured to send the unicast service flow to a first user equipment, where the address of the first user equipment is the first destination address.

[0179] In some embodiments, the third processing module 701 is also configured to receive at least one service stream before receiving the multicast data stream sent by the bearer network entry device; determine the mapping relationship between the multicast address and at least one destination address based on the service identifier and destination address carried in the at least one service stream, and the pre-acquired mapping relationship between the service identifier and the multicast address.

[0180] In some embodiments, the third processing module 701 is further configured to receive a service flow with the same service identifier before receiving the multicast data stream sent by the bearer network ingress device; generate a multicast join message based on the service identifier of the service flow with the same service identifier, and the multicast join message is used to request the transmission of the multicast data stream with the service identifier; and send the multicast join message to the bearer network ingress device.

[0181] In some embodiments, the third processing module 701 is further configured to send the first service flow to a second user device when receiving a first service flow and a first multicast data flow with the same service identifier, and the address of the second user device is the destination address in the first service flow.

[0182] In actual applications, the receiving module 601 , the first processing module 602 , the second processing module 603 , the third processing module 701 , the fourth processing module 702 and the sending module 703 may all be implemented based on a processor.

[0183] It should be noted that the description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. For technical details not disclosed in the device embodiment of this application, please refer to the description of the method embodiment of this application for understanding.

[0184] It should be noted that, in the embodiment of the present application, if the above method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a terminal, server, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific combination of hardware and software.

[0185] Correspondingly, an embodiment of the present application further provides a computer program product, which includes computer-executable instructions, and the computer-executable instructions are used to implement any data transmission method provided in the embodiment of the present application.

[0186] Accordingly, an embodiment of the present application further provides a computer storage medium, on which computer executable instructions are stored. The computer executable instructions are used to implement any one of the data transmission methods provided in the above embodiments.

[0187] The embodiment of the present application further provides an electronic device. FIG8 is a schematic diagram of the composition structure of the electronic device provided in the embodiment of the present application. As shown in FIG8 , the electronic device 80 may include:

[0188] Memory 801, used to store executable instructions;

[0189] The processor 802 is configured to implement any one of the above-mentioned data transmission methods when executing the executable instructions stored in the memory 801.

[0190] The processor 802 may be at least one of an ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor.

[0191] The above-mentioned computer-readable storage medium / memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (Flash Memory), a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); it can also be various terminals including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0192] In some embodiments, the functions or modules included in the device provided in the embodiments of the present application can be used to execute the method described in the above method embodiments. The specific implementation can refer to the description of the above method embodiments. For the sake of brevity, it will not be repeated here.

[0193] The above description of the various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced with each other and will not be repeated herein for the sake of brevity.

[0194] The methods disclosed in the various method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0195] The features disclosed in the various product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0196] The features disclosed in the various method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0197] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0198] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are protected by this application.

Claims

1. A data transmission method, applied to an ingress device of a bearer network, the method comprising: Receiving a plurality of service flows; When the plurality of service flows have the same service identifier, determining a multicast address corresponding to the service identifier according to the service identifier and destination address carried in the service flows with the same service identifier, and a pre-acquired mapping relationship between the service identifier and the multicast address, and replacing the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream; Transmitting the multicast data stream to an egress device of the bearer network, so that the egress device of the bearer network replaces the multicast address in the multicast data stream with the destination address according to the identified and recorded mapping relationship between the multicast address and the destination address to obtain a unicast service flow.

2. The method according to claim 1, wherein, The replacing the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream includes: When the service flows with the same service identifier meet a set condition, replacing the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream; Wherein, the set condition includes but is not limited to one of the following conditions: the number of destination addresses corresponding to the service flows with the same service identifier is greater than or equal to a set number, or the continuous reception duration of the service flows with the same service identifier is greater than or equal to a first set duration.

3. The method according to claim 1, wherein, The replacing the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream includes: Transmitting the service flows with the same service identifier to the egress device of the bearer network; After receiving a multicast join message sent by the egress device of the bearer network, replacing the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream.

4. The method according to claim 1, wherein, The method further includes: When the destination address carried in a first service flow among the service flows with the same service identifier is a new destination address, transmitting the first service flow to the egress device of the bearer network, and blocking the first service flow transmitted to the egress device of the bearer network after waiting for a second set duration; the new destination address is a destination address not included in the historical service flows received by the ingress device of the bearer network; the egress device of the bearer network is used to establish a mapping relationship between the service identifier and the new destination address according to the received first service flow.

5. The method according to claim 1, wherein, The method further includes: When the traffic of the service flows with a first destination address is lower than a traffic threshold within a set statistical period, sending a notification message carrying the first destination address to the egress device of the bearer network, where the notification message indicates a notification to stop replacing the multicast address in the multicast data stream with the first destination address.

6. The method according to any one of claims 1 to 5, wherein The service identifier is located in the IPv6 extension header of the service flow.

7. A data stream transmission method, applied to an egress device of a bearer network, the method comprising: Receive the multicast data stream sent by the bearer network ingress device; The bearer network ingress device is used to determine the multicast address corresponding to the service identifier according to the service identifier and destination address carried in the service flows with the same service identifier, and the mapping relationship between the service identifier and the multicast address obtained in advance, replace the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier, and obtain a multicast data stream; According to the mapping relationship between the identified and recorded multicast address and at least one destination address, replace the multicast address in the multicast data stream with the first destination address among the at least one destination address to obtain a unicast service flow; The first destination address is any one of the at least one destination address; Send the unicast service flow to a first user device, and the address of the first user device is the first destination address.

8. The method according to claim 7, wherein, Before receiving the multicast data stream sent by the bearer network ingress device, the method further includes: Receive at least one service flow; According to the service identifier and destination address carried in the at least one service flow, and the mapping relationship between the service identifier and the multicast address obtained in advance, determine the mapping relationship between the multicast address and at least one destination address.

9. The method according to claim 7, wherein Before receiving the multicast data stream sent by the bearer network ingress device, the method further includes: Receive service flows with the same service identifier; Generate a multicast join message according to the service identifier of the service flows with the same service identifier, and the multicast join message is used to request the transmission of the multicast data stream with the service identifier; Send the multicast join message to the bearer network ingress device.

10. The method according to any one of claims 7 to 9, wherein, The method further includes: In the case of receiving a first service flow and a first multicast data stream with the same service identifier, send the first service flow to a second user device, and the address of the second user device is the destination address in the first service flow.

11. A data transmission device, which is applied to a bearer network ingress device, and the device includes: A receiving module, configured to receive multiple service flows; A first processing module, configured to, when the multiple service flows have the same service identifier, determine the multicast address corresponding to the service identifier according to the service identifier and destination address carried in the service flows with the same service identifier, and the mapping relationship between the service identifier and the multicast address obtained in advance, replace the destination address in the service flows with the same service identifier with the multicast address corresponding to the service identifier, and obtain a multicast data stream; A second processing module, configured to transmit the multicast data stream to a bearer network egress device, so that the bearer network egress device replaces the multicast address in the multicast data stream with the user address according to the identified and recorded mapping relationship between the multicast address and the user address, and obtains a unicast service flow.

12. A data transmission device, which is applied to a bearer network egress device, and the device includes: A third processing module, configured to receive the multicast data stream sent by the bearer network ingress device; The bearer network ingress device is configured to determine the multicast address corresponding to the service identifier according to the service identifier and destination address carried in the service flow with the same service identifier, and the mapping relationship between the service identifier and the multicast address obtained in advance, and replace the destination address in the service flow with the same service identifier with the multicast address corresponding to the service identifier to obtain a multicast data stream; The fourth processing module is configured to replace the multicast address in the multicast data stream with the first destination address among the at least one destination address according to the mapping relationship between the identified and recorded multicast address and the at least one destination address to obtain a unicast service flow; The first destination address is any one of the at least one destination address; The sending module is configured to send the unicast service flow to a first user device, and the address of the first user device is the first destination address.

13. An electronic device, comprising a processor and a memory for storing a computer program that can run on the processor; wherein, The processor is configured to run the computer program to execute the data transmission method according to any one of claims 1 to 10.

14. A computer storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 10 is implemented.

15. A computer program product, comprising a computer program, and when the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 10 is implemented.

Images