A data transmission method and related apparatus

Abstract

The application provides a data transmission method and related device. The method comprises: when a first device transmits service data to a second device, the first device generates check data of the service data based on a locally saved network coding rule through the service data. The check data is used for the second device to recover correct service data through the check data when an error occurs in the transmission of the service data. Then, the first device transmits the check data and the service data to the second device through a first data channel and a second data channel. Through the method, the fault tolerance and reliability of network transmission data are improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a data transmission method and related apparatus. Background Technology

[0002] In wireless communication systems, user equipment (UE) can establish protocol data unit (PDU) sessions with data network (DN) elements through user plane function (UPF) network elements. The PDU session provides data transmission services between the UE and the DN network elements.

[0003] Currently, network latency and / or jitter in the data transmission channel between user equipment and the data network can lead to significant delays or errors in the service data received by the user equipment. This prevents the user equipment from completing service functions in a timely manner, impacting user experience. Therefore, improving the fault tolerance and reliability of network data transmission is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a data transmission method and related apparatus, which improves the fault tolerance and reliability of network data transmission.

[0005] In a first aspect, this application provides a data transmission method, the method comprising: a first device receiving first extended reality service data; the first device generating verification data of the first extended reality service data based on the first extended reality service data; the first device sending the first extended reality service data and the verification data of the first extended reality service data to a second device through a first data channel and a second data channel; wherein, the verification data of the first extended reality service data is used by the second device to recover the first extended reality service data when receiving erroneous first extended reality service data; wherein, the first data channel and the second data channel are of any one of the following types: cellular data channel and non-cellular data channel.

[0006] Optionally, the cellular channel can also be called the 3GPP data channel, and the non-cellular channel can also be called the non-3GPP data channel.

[0007] Transmitting service data and verification data through two data channels, compared to using only one data channel, offers several advantages. First, it avoids slow transmission caused by network congestion. Second, if one data channel experiences a problem, the other can still transmit data normally.

[0008] The method provided in the first aspect solves the problem that when the first extended reality service data is erroneous, the second device can retrieve the correct first extended reality service data based on the verification data of the first extended reality service data. This resolves the issue of network jitter affecting the correct transmission of extended reality service data in extended reality services, improving the fault tolerance and reliability of network data transmission.

[0009] In conjunction with the first aspect, in one possible implementation, the first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device through a first data channel and a second data channel, specifically including: the first device sending the first extended reality service data to the second device through the first data channel; and the first device sending the verification data of the first extended reality service data to the second device through the second data channel.

[0010] Optionally, in other possible implementations, the first device sends verification data of the first extended reality service data to the second device through the first data channel; the first device sends the first extended reality service data to the second device through the second data channel.

[0011] Optionally, in other possible implementations, the first device mixes the first extended reality service data and its verification data. A portion of the first extended reality service data and its verification data are sent to the second device via the first data channel, while the other portion of the first extended reality service data and its verification data are sent to the second device via the second data channel. This method of transmitting service data and verification data through two data channels avoids the problem of slow transmission due to network congestion. Furthermore, if one data channel fails, the other data channel can still transmit data normally.

[0012] In conjunction with the first aspect, in one possible implementation, before the first device receives the first extended reality service data, the method further includes: the first device receiving and storing the network coding rules, wherein the network coding rules are used by the first device to generate verification data for the first extended reality service data based on one or more of the following: network coding type, coded sub-block number, K value, original data block number, and coded sub-block data length, wherein the K value is the number of data packets of the first extended reality service data required by the first device to generate the verification data of the first extended reality service data. This solves the problem that when the first extended reality service data contains errors, the second device can recover the correct first extended reality service data based on the verification data of the first extended reality service data.

[0013] In conjunction with the first aspect, in one possible implementation, the first device generates verification data for the first extended reality service data based on the first extended reality service data, specifically including: the first device acquiring k data packets within the first extended reality service data; the first device generating m verification packets based on the k data packets, where m is less than or equal to k.

[0014] In conjunction with the first aspect, in one possible implementation, before the first device generates verification data for the first extended reality service data based on the first extended reality service data, the method further includes: the first device sending a first message to the second device, the first message indicating that the first device has sent the verification data for the first extended reality service data.

[0015] Optionally, the first device can send a first message to the second device via either the first data channel or the second data channel. In this way, upon receiving the first message, the second device can determine that the first device has performed network coding.

[0016] In conjunction with the first aspect, in one possible implementation, the header of the first extended reality service data or the header of the first extended reality service data verification data further includes a first field, which indicates that the first device has sent the verification data of the first extended reality service data. Thus, the second device can know that the first device has performed network coding based on the first field.

[0017] In conjunction with the first aspect, in one possible implementation, before the first device sends the first extended reality service data and the verification data of the first extended reality service data through the first data channel and the second data channel, the method further includes: the first device establishing the first data channel and the second data channel with the second device based on the routing and switching off underlying ATSSS capability of the access service flow.

[0018] In conjunction with the first aspect, in one possible implementation, the first device establishes the first data channel and the second data channel with the second device based on the underlying ATSSS capabilities of the access service flow routing and switching. Specifically, this includes: the first device receiving a first PDU session establishment request sent by the second device, the first PDU session establishment request including first ATSSS Capabilities, the first ATSSS Capabilities containing information on network coding supported by the second device; the first device establishing the first data channel with the second device; the first device receiving a second PDU session establishment request sent by the second device, the second PDU session establishment request including second ATSSS Capabilities, the second ATSSS Capabilities containing information on network coding supported by the recipient of the first extended reality service data; and the first device establishing the second data channel with the second device.

[0019] Optionally, in one possible implementation, the first ATSSS Capabilities is set to ATSSS-LL with NC. In this way, the first and second devices can negotiate with the second device to obtain a first data channel and a second data channel based on the ATSSS capabilities, providing a foundation for subsequent transmission of service data and service data verification data.

[0020] In conjunction with the first aspect, in one possible implementation, before the first device transmits the first Extended Reality Service (APS) data and the verification data of the first APS data through the first data channel and the second data channel, the method further includes: the first device receiving a third PDU session establishment request sent by the second device, the third PDU session establishment request including indication information for performing network coding; the first device establishing the first data channel with the second device; the first device receiving a fourth PDU session establishment request sent by the second device, the fourth PDU session establishment request including indication information for performing network coding; and the first device establishing the second data channel with the second device. In this way, the first device and the second device can negotiate the first data channel and the second data channel with the second device without relying on APSSS capabilities, providing a foundation for subsequent transmission of service data and verification data of the service data.

[0021] Secondly, this application provides a data transmission method, the method comprising: a second device receiving first extended reality service data and verification data of the first extended reality service data sent by a first device through a first data channel and a second data channel; wherein, the verification data of the first extended reality service data is used by the second device to recover the first extended reality service data when receiving erroneous first extended reality service data; wherein, the first data channel and the second data channel are of any one of the following types: cellular data channel and non-cellular data channel.

[0022] Optionally, the cellular channel can also be called the 3GPP data channel, and the non-cellular channel can also be called the non-3GPP data channel.

[0023] Transmitting service data and verification data through two data channels, compared to using only one data channel, offers several advantages. First, it avoids slow transmission caused by network congestion. Second, if one data channel experiences a problem, the other can still transmit data normally.

[0024] The method provided in the second aspect solves the problem that when the first extended reality service data is erroneous, the second device can retrieve the correct first extended reality service data based on the verification data of the first extended reality service data. This resolves the issue of network jitter affecting the correct transmission of extended reality service data in extended reality services, improving the fault tolerance and reliability of network data transmission.

[0025] In conjunction with the second aspect, in one possible implementation, the second device receives first extended reality service data and verification data of the first extended reality service data sent by the first device through a first data channel and a second data channel. Specifically, this includes: the second device receiving the first extended reality service data sent by the first device through the first data channel; and the second device receiving the verification data of the first extended reality service data sent by the first device through the second data channel.

[0026] Optionally, in other possible implementations, the second device receives verification data of the first extended reality service data sent by the first device through the first data channel; the second device receives the first extended reality service data sent by the first device through the second data channel.

[0027] Optionally, in other possible implementations, the first device mixes the first extended reality service data and its verification data. The second device receives a portion of the first extended reality service data and its verification data sent by the first device through the first data channel. The second device also receives another portion of the first extended reality service data and its verification data sent by the first device through the first data channel. This method of transmitting service data and verification data through two data channels avoids the problem of slow transmission due to network congestion. Furthermore, if one data channel fails, the other data channel can still transmit data normally.

[0028] In conjunction with the second aspect, in one possible implementation, before the second device receives the first extended reality service data and the verification data of the first extended reality service data sent by the first device through the first data channel and the second data channel, the method further includes: receiving a first message sent by the first device, the first message being used to indicate that the first device has sent the verification data of the first extended reality service data.

[0029] Optionally, the second device can receive the first message sent by the first device through either the first data channel or the second data channel.

[0030] In conjunction with the second aspect, in one possible implementation, the header of the first extended reality service data or the header of the verification data of the first extended reality service data further includes a first field, which is used to indicate that the first device has sent the verification data of the first extended reality service data.

[0031] In conjunction with the second aspect, in one possible implementation, before the second device receives the first extended reality service data and the verification data of the first extended reality service data sent by the first device through the first data channel and the second data channel, the method further includes: the second device establishing the first data channel and the second data channel with the first device based on the routing and switching off underlying ATSSS capability of the access service flow.

[0032] Optionally, in one possible implementation, the first ATSSS Capabilities is set to ATSSS-LL with NC. In this way, the first and second devices can negotiate with the second device to obtain a first data channel and a second data channel based on the ATSSS capabilities, providing a foundation for subsequent transmission of service data and service data verification data.

[0033] In conjunction with the second aspect, in one possible implementation, the second device establishes the first data channel and the second data channel with the first device based on the underlying ATSSS capabilities of the access service flow routing and switching. Specifically, this includes: the second device sending a first PDU session establishment request to the first device, the first PDU session establishment request including first ATSSS Capabilities, the first ATSSS Capabilities containing information on network coding supported by the second device; the second device establishing the first data channel with the first device; the second device sending a second PDU session establishment request to the first device, the second PDU session establishment request including second ATSSS Capabilities, the second ATSSS Capabilities containing information on network coding supported by the second device; and the second device establishing the second data channel with the first device.

[0034] In conjunction with the second aspect, in one possible implementation, before the second device receives the first extended reality service data and the verification data of the first extended reality service data sent by the first device through the first data channel and the second data channel, the method further includes: the second device sending a third PDU session establishment request to the first device, the third PDU session establishment request including indication information for performing network coding; the second device establishing the first data channel with the first device; the second device sending a fourth PDU session establishment request to the first device, the fourth PDU session establishment request including indication information for performing network coding; and the second device establishing the second data channel with the first device.

[0035] Thirdly, this application provides another device, the device comprising: one or more processors and one or more memories; the one or more memories being coupled to the one or more processors, the one or more memories being used to store computer program code, the computer program code including computer instructions, the one or more processors invoking the computer instructions to cause the device to perform any of the methods provided in any possible implementation of any of the above aspects.

[0036] Fourthly, this application provides a chip or chip system, including a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method provided in any of the possible implementations of any of the above aspects.

[0037] Fifthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a device, cause the device to perform any of the methods provided in any possible implementation of any of the above aspects.

[0038] Sixthly, embodiments of this application provide a computer program product that, when run on a device, causes the device to perform any of the methods provided in any possible implementation of any of the above aspects.

[0039] For the beneficial effects of the second to sixth aspects, please refer to the description of the beneficial effects in the first aspect; the embodiments of this application will not be repeated here. Attached Figure Description

[0040] Figure 1 A schematic diagram illustrating a redundant transmission method provided in an embodiment of this application;

[0041] Figure 2 A schematic diagram of an architecture provided for an embodiment of this application;

[0042] Figure 3 A flowchart illustrating how a user equipment (e.g., user equipment 100) negotiates a cellular data channel with a UPF network element based on ATSSS technology, as provided in this application embodiment;

[0043] Figure 4 A flowchart illustrating how a user equipment (e.g., user equipment 100) negotiates a non-cellular data channel with a UPF network element based on ATSSS technology, as provided in this application embodiment;

[0044] Figure 5 A flowchart illustrating how a user equipment (e.g., user equipment 100) negotiates a cellular data channel with a UPF network element without relying on ATSSS technology, as provided in an embodiment of this application.

[0045] Figure 6 A flowchart illustrating how a user equipment (e.g., user equipment 100) negotiates a non-cellular data channel with a UPF network element without relying on ATSSS technology, as provided in an embodiment of this application.

[0046] Figure 7 A flowchart illustrating a method for transmitting service data between a user equipment 100 and a UPF network element based on a first data channel and a second data channel, provided in this application embodiment;

[0047] Figure 8 A schematic diagram illustrating a header format for first extended reality business data or a header format for verification data of first extended reality business data, provided for embodiments of this application;

[0048] Figures 9-11 This application provides a schematic diagram of the functional module for the second device to recover the correct first extended reality business data. Detailed Implementation

[0049] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0050] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0051] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0052] Currently, the industry has proposed a redundant transmission method. This involves the sending and receiving ends of the service data negotiating two data channels before transmission. When sending service data, the sending end simultaneously transmits the data to the receiving end through both channels, meaning the same service data is transmitted in both channels. This way, even if the service data transmitted in one channel encounters a problem, the service data transmitted in the other channel may be correct, allowing the receiving end to complete its normal business functions using the data transmitted from the other channel.

[0053] Optionally, redundant transmission can be achieved based on wireless communication technologies defined by the 3rd generation partnership project (3GPP) standards group, or non-3GPP wireless communication technologies.

[0054] Figure 1 An exemplary schematic diagram of redundant transmission is shown.

[0055] like Figure 1 As shown, the various functional units communicate with each other through interfaces. When 3GPP wireless communication technology is supported, the access network (AN) equipment can establish a control plane signaling connection with the access and mobility management function (AMF) network element through interface 2 (N2). User equipment (UE) can transmit control panel messages with the AMF network element through interface 1 (N1), and UE can support MPTCP and ATSSS-LL functions. The AN equipment can establish a user plane communication connection with the UPF through interface 3 (N3). The AMF network element can interact with the SMF network element through interface 11 (N11). The session management function (SMF) network element can interact with the policy control function (PCF) network element through interface 7 (N7), and the SMF network element can establish a user plane communication connection with the UPF network element through interface 4 (N4), and the UPF network element can support MPTCP proxy and PMF functions. UPF can interact with the data network (DN) to exchange user plane data through interface 6 (N6 for short).

[0056] When non-3GPP wireless communication technology is supported, the AN device can establish a control plane signaling connection with the AMF network element through N2. The AN device can establish a user plane communication connection with the UPF through N3 to establish a channel.

[0057] However, redundant transmission has two drawbacks. First, the sending end of the service data needs to transmit the same service data twice, doubling the data transmission requirements and increasing network load. Second, if the service data transmitted in both data channels encounters the same problem, such as both data channels losing the same data packets, then the receiving end of the service data will also be unable to complete normal service functions.

[0058] Based on this, embodiments of this application provide a transmission method, the method comprising: when a sending end sends service data to a receiving end, the sending end generates verification data for the service data based on locally stored network coding rules. The verification data is used by the receiving end to recover correct service data when errors occur in the service data transmission. Subsequently, the sending end sends the verification data and the service data to the receiving end through a first data channel and a second data channel.

[0059] The business data can be extended reality (XR) business data or other types of business data; this application does not limit this.

[0060] Optionally, the sending end sends the verification data and service data to the receiving end through the first data channel and the second data channel. Alternatively, the sending end can mix the service data and verification data together and send them to the receiving end through the first data channel and the second data channel, or it can separate the service data and verification data, sending the service data through the first data channel and the verification data through the second data channel.

[0061] The method provided in this application embodiment allows for a limited number of errors in the service data. The receiving end can still recover the correct service data from the verification data, improving the fault tolerance and reliability of network-transmitted service data. Furthermore, transmitting service data and verification data through two data channels, compared to transmitting both simultaneously through a single data channel, results in faster data transmission speeds and reduced data transmission latency.

[0062] Figure 2 This is a schematic diagram of an architecture provided for an embodiment of this application.

[0063] like Figure 2As shown, a user equipment (UE) and a UPF network element can establish a multi-access PDU session based on access technology 1 and access technology 2. The UE's service flow can then be transmitted to the UPF network element via access technology 1 and / or access technology 2. Similarly, the UPF network element can transmit the UPF network element's service flow to the UE via access technology 1 and / or access technology 2. A multi-access PDU session is defined in contrast to a single-access PDU session. A single-access PDU session refers to a PDU session that accesses the UPF network element using only one access technology, while a multi-access PDU session refers to a PDU session that accesses the UPF network element using at least two different access technologies.

[0064] Access technology 1 and access technology 2 can be any of the 3GPP wireless communication technologies or non-3GPP wireless communication technologies.

[0065] That is, access technology 1 can be a 3GPP wireless communication technology, and access technology 2 can also be a 3GPP wireless communication technology. Alternatively, access technology 1 can be a 3GPP wireless communication technology, and access technology 2 can also be a non-3GPP wireless communication technology. Alternatively, access technology 1 can be a non-3GPP wireless communication technology, and access technology 2 can also be a 3GPP wireless communication technology.

[0066] The following embodiments of this application illustrate the use of different access technologies 1 and 2. Compared to the case where access technologies 1 and 2 are the same, the advantage of using different access technologies 1 and 2 is that if one access technology malfunctions, the other access technology can still be used normally, thus avoiding the situation where two identical access technologies malfunction simultaneously and increasing fault tolerance.

[0067] In this embodiment, after acquiring Extended Reality Service (EPS) data, the UPF network element obtains verification data based on the EPS data. The UPF network element then sends the EPS data and the verification data to the User Equipment (UE) via Access Technology 1 and Access Technology 2. The verification data is used by the UE to recover the correct EPS data when it receives erroneous EPS data.

[0068] Here, if a frame of extended reality service data includes x data packets, and at least one of these x data packets is erroneous (e.g., the data in the data packet is incorrect or lost), then this frame of extended reality service data can be called erroneous extended reality service data.

[0069] Next, the technical terms involved in the embodiments of this application will be explained.

[0070] I. 3GPP Wireless Communication Technology

[0071] In some embodiments, 3GPP wireless communication technology may also be referred to as cellular communication technology. 3GPP wireless communication technology includes, but is not limited to, long term evolution (LTE) communication technology, fifth generation mobile communication technology (5G), and future mobile communication technologies.

[0072] II. Non-3GPP Wireless Communication Technology

[0073] In some embodiments, non-3GPP wireless communication technology may also be referred to as non-cellular communication technology. Non-3GPP wireless includes, but is not limited to, wireless local area network (WLAN) communication technology, Wi-Fi, and future mobile communication technologies.

[0074] III. Access traffic steering, switching, splitting, ATSSS (Access Traffic Steering, Switching, Splitting)

[0075] ATSSS technology supports two functions: MPTCP and ATSSS-LL (lowlayer). MPTCP is for multiplexing TCP packets, while ATSSS-LL is for multiplexing IP packets. ATSSS-LL can be used by user equipment or UPF network elements to select transmission paths for data packets based on traffic splitting modes and link status, and it supports multiplexing of both TCP and UDP services.

[0076] ATSSS technology supports the following steering modes: Active-Standby, smallest delay, load balancing, priority-based, redundancy, or future possible steering modes.

[0077] In the primary / standby traffic splitting mode, only one data channel is used for data transmission at a time. Specifically, in this mode, one transmission path can be designated as Active (3GPP access or Non-3GPP access), and the other as Standby. When the Active transmission path is available, all data in the service flow is transmitted to the peer through the Active transmission path. When the Active path is unavailable, all data in the service flow is switched to the Standby transmission path for transmission.

[0078] In the minimum latency offloading mode, the shortest latency transmission path can be selected to transmit service flow data. In this mode, the UE or UPF network element can monitor the transmission latency of the path in real time. For example, path monitoring can be implemented by a transport layer protocol (such as the MPTCP layer having the function of detecting RTT), or by the performance measurement function (PMF) module in the UPF network element.

[0079] In load balancing, service data can be distributed proportionally to different transmission paths. The distribution ratio can be determined based on the current load of the two transmission paths in the network. For example, a heavier-loaded path will receive a smaller distribution ratio, while a lighter-loaded path will receive a larger distribution ratio.

[0080] In priority-based traffic splitting mode, one transmission path can be designated as a high-priority path, and the other as a low-priority path. When the high-priority path is uncongested, all data in the service flow is transmitted through it. When the high-priority path becomes congested, some data in the service flow will be transmitted through the low-priority path. When the high-priority path is unavailable, all data in the service flow will be transmitted through the low-priority path.

[0081] The load balancing mode, priority mode, or redundant transmission mode mentioned above are traffic splitting modes that support packet-level splitting. Packet-level splitting means that different data packets of the same service flow are transmitted on different links or with different access technologies, thereby utilizing multi-link resources to increase the bandwidth of the service flow.

[0082] Possible future traffic offloading modes may include user preference-based offloading modes, offloading modes selected autonomously by user equipment or UPF network elements, and offloading modes based on QoS requirements, etc. This application does not specifically limit these modes.

[0083] The data transmission involved in the embodiments of this application may include the process of data transmission, data reception, or data interaction. For example, data transmission between a user equipment and a UPF network element may include the user equipment sending data to the UPF network element, or the UPF network element sending data to the user equipment, or the user equipment sending data to the UPF network element and receiving data from the UPF network element, or the UPF network element sending data to the user equipment and receiving data from the UPF network element.

[0084] IV. Access network equipment is mainly used to implement functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management.

[0085] Core network equipment mainly includes management equipment and gateway equipment. Management equipment is primarily used for terminal device registration, security authentication, mobility management, and location management. Gateway equipment is mainly used to establish channels with terminal devices and forward data packets between terminal devices and external data networks through these channels.

[0086] A data network can include network devices (such as servers, routers, etc.). Data networks are primarily used to provide various data services to user devices.

[0087] For example, the access network, core network, and data network in 5G will be used as examples for illustration.

[0088] The access network in 5G can be a radio access network (R)AN. The (R)AN equipment in a 5G system can be composed of multiple 5G-(R)AN nodes, which can include: 3GPP access networks and non-3GPP access networks.

[0089] The 5G core network (5G core / new generation core, 5GC / NGC) includes multiple functional units such as AMF network element, SMF network element, UPF network element, and PCF network element.

[0090] Among them, the AMF network element is mainly responsible for services such as mobility management and access management.

[0091] SMF network elements are mainly responsible for session management, dynamic host configuration protocol functions, and selection and control of user plane functions.

[0092] UPF network elements are mainly responsible for packet routing and forwarding, packet filtering, and performing quality of service (QoS) control functions when connecting to the DN and user plane.

[0093] The DN (Network Node) primarily provides services to user equipment, such as mobile operator services, internet services, or third-party services. The AUSF (Automatic User Equipment Frame) element is mainly responsible for authentication functions for terminal devices.

[0094] The PCF network element is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, and obtaining registration information related to policy decisions.

[0095] It should be noted that these functional units can work independently or be combined to implement certain control functions, such as access control and mobility management functions for terminal devices, including access authentication, security encryption, and location registration, as well as session management functions such as the establishment, release, and modification of user plane transmission paths.

[0096] The session management network element described in this application embodiment can be an SMF network element or other network elements that implement session management functions; the user plane network element can be a UPF network element or other network elements that implement user plane functions; the policy control network element can be a PCF network element or other network elements that implement policy control functions; and the mobility management network element can be an AMF network element or other network elements that implement mobility management functions, etc.

[0097] For ease of description, the embodiments of this application will be described below using the Session Management Network Element (SMF), the User Plane Network Element (UPF), the Policy Control Network Element (PCF), and the Mobility Management Network Element (AMF) as examples. This example does not limit the embodiments of this application.

[0098] V. Network Coding (NC)

[0099] The purpose of network coding is to improve the accuracy of business data transmission. Specific network coding methods can include erasure coding, fountain coding, Reed-Solomon coding, etc. The following embodiments of this application use erasure coding (EC) as an example for illustration.

[0100] The principles of network coding will be explained in detail below.

[0101] After receiving the service data to be transmitted, the sender of the service data obtains verification data based on the service data and preset network coding rules. This verification data is used by the receiver of the service data to recover the correct service data when erroneous data is received, thereby improving the accuracy of service data transmission.

[0102] After receiving the service data and its verification data, the sender transmits both to the receiver. During transmission, any x data items in the service data and verification data are allowed to be corrupted. The receiver can still recover the correct service data. The value of x depends on the specific network coding method.

[0103] For example, there are k data packets containing business data, and m data packets containing verification data are obtained based on the k data packets containing business data and preset network encoding rules.

[0104] During business data transmission, the sender transmits k data packets of business data and m data packets of checksum data to the receiver. If m of the k data packets are corrupted or lost, the receiver can still recover the correct k data packets of business data based on the m checksum data packets. Alternatively, if p of the k data packets are corrupted, and q of the m checksum data packets are corrupted, the receiver can still recover the correct k data packets of business data, where q + p = m.

[0105] This paper first describes how the user equipment (UE) negotiates multiple communication paths with the UPF network element. These multiple communication paths include at least two. The following embodiments illustrate how the UE negotiates two different communication paths with the UPF network element. In other embodiments, the UE and the UPF network element may also negotiate two identical communication paths; this application does not limit this approach.

[0106] The following embodiments of this application illustrate the process of obtaining a cellular data channel and a non-cellular data channel through negotiation between the user equipment and the UPF network element.

[0107] First, we will introduce how User Equipment 100 negotiates with UPF network elements based on ATSSS technology to obtain a cellular data channel and a non-cellular data channel.

[0108] Figure 3 A flowchart is shown of a user equipment (e.g., user equipment 100) negotiating a cellular data channel with a UPF network element based on ATSSS technology.

[0109] For example, the cellular data channel can be a data channel based on 5G technology (the data channel can also be called a communication path).

[0110] S3001, User Equipment 100 sends the first PDU session establishment request to the 5G base station (gNB).

[0111] The S3002 and 5G base stations send the first PDU session establishment request to the AMF network element.

[0112] S3003, the AMF network element sends the first PDU session establishment request to the SMF network element.

[0113] In one possible implementation, user equipment 100 sends a request to the SMF network element to establish or update a PDU session. This request includes ATSSS-LL with NC capability indication information, or in other words, indication information for performing network coding based on ATSSS-LL.

[0114] In some embodiments, the capability indication information of ATSSS-LL with NC can also be referred to as the first ATSSSCapabilities, and the value of the first ATSSSCapabilities is ATSSS-LL with NC.

[0115] For example, the user equipment 100 can encapsulate the request to establish or update a PDU session in a non-access stratum (NAS) transport message and send it to the AMF network element through the 5G base station, and then the AMF network element forwards the request to establish or update a PDU session to the SMF network element.

[0116] In one possible implementation, the ATSSS-LL capability indication information may be independent of the request to establish or update a PDU session. The ATSSS-LL with NC capability indication information may be sent directly from the user equipment 100 to the SMF network element, or it may be sent separately by the user equipment 100 to the SMF network element, such as first sending it to the AMF network element, which then forwards it to the SMF network element. This application embodiment does not specifically limit this.

[0117] It is understood that the user equipment 100 may also send ATSSS-LL with NC capability indication information to the SMF network element in any way according to the actual application scenario. The ATSSS-LL with NC capability indication indicates that the user equipment 100 supports the function of performing network coding based on ATSSS-LL technology. This application embodiment does not make specific limitations on this.

[0118] The PDU session described in the embodiments of this application can be a protocol data unit (PDU) session or a packet data unit (PDU) session.

[0119] One possible interpretation of the user equipment 100 described in this application embodiment supporting ATSSS-LLwith NC capability is that if user equipment 100 supports the ATSSS-LLwith NC function and enables the ATSSS-LLwith NC function of user equipment 100, then user equipment 100 can perform the method as described in the embodiments of this application based on ATSSS-LLwith NC.

[0120] In this embodiment, the indication information used to indicate ATSSS-LLwith NC capability can be referred to as ATSSS-LLwith NC capability indication information. When transmitting ATSSS-LLwith NC capability indication information between different network elements, the form and content of the ATSSS-LLwith NC capability indication information may differ or be the same. The ATSSS-LLwith NC capability indication information mentioned in this embodiment is used to illustrate the function of ATSSS-LLwith NC capability indication information and does not limit its specific form. For example, in subsequent embodiments, user equipment 100 may send ATSSS-LLwith NC capability indication information to SMF network elements, and SMF network elements may send ATSSS-LLwith NC capability indication information to PCF network elements, etc. The form and content of the ATSSS-LLwith NC capability indication information may be the same or different between different network elements.

[0121] S3004, the SMF network element sends the first PDU session establishment request to the PCF network element.

[0122] In this embodiment of the application, the SMF network element obtains the ATSSS-LLwith NC capability indication information of the user equipment 100, and can further combine the ATSSS-LLwith NC capability of the device (such as the UPF network element) that transmits data with the user equipment 100 to determine whether to send the ATSSS-LLwith NC capability indication information to the PCF network element.

[0123] For example, taking the device transmitting data with user equipment 100 as a UPF network element, the SMF network element can determine that the UPF supports ATSSS-LL with NC capability. For instance, the SMF network element selects the UPF based on its functions, including support for ATSSS-LL with NC. Alternatively, the SMF network element receives an ATSSS-LL with NC capability indication from the UPF network element. When both user equipment 100 and the UPF network element simultaneously support ATSSS-LL with NC capability, the SMF network element determines that the network's ATSSS capability supports ATSSS-LL with NC, and can then send an ATSSS-LL with NC capability indication to the PCF network element.

[0124] For example, SMF network elements can include ATSSS-LLwith NC capability indication information in the policy request message sent to PCF network elements.

[0125] S3005 and PCF network elements determine that user equipment 100 and UPF network elements can perform multi-path transmission of service data based on ATSSS-LL with NC.

[0126] In this embodiment of the application, the PCF network element can determine the multi-link transmission of service data (which may also be called multi-access traffic splitting, etc.) based on the ATSSS capability of the network sent by the SMF network element.

[0127] In one possible implementation, the PCF network element determines the aforementioned traffic splitting mode based on the traffic splitting modes supported by the ATSSS-LL function. The aforementioned traffic splitting mode can be any one or more of the traffic splitting modes mentioned above, especially supporting packet-level traffic splitting modes, that is, supporting the transmission of different data packets of the same service through different access technologies or different links. For example, the PCF network element determines the traffic splitting mode to be load balancing mode and sends the flow description information of the service data and the load balancing traffic splitting mode indication to the SMF network element. The flow description information of the aforementioned service data contains only the flow description information of one service flow, thus indicating that a packet-level traffic splitting mode is implemented for this service flow.

[0128] S3006, PCF network element sends a first message to SMF network element. The first message is used to indicate that user equipment 100 and UPF network element can perform multipath transmission of service data based on ATSSS-LL with NC.

[0129] For example, the first information may include ATSSS-LL with NC function indication information. For instance, this ATSSS-LL with NC function indication information is used to indicate multi-link transmission of service data based on the ATSSS-LL function and network coding.

[0130] For example, the first information may be characters or numbers, which are used to indicate the function indication information of ATSSS-LLwith NC. This application embodiment does not specifically limit this.

[0131] In one possible implementation, the first information may further include flow identification information of the service data, which is used to indicate the service data corresponding to the flow identification information of the service data, and to perform multi-link transmission of the service data based on the ATSSS-LL function and network coding.

[0132] In one possible implementation, if the first information does not explicitly indicate the flow identification information of the service data, the service data can be transmitted across multiple links based on the ATSSS-LL function and network coding for all possible service data.

[0133] Before the PCF network element sends the first message to the SMF network element, the SMF network element sends a request to the PCF network element to obtain the Policy and Charging Control Rule (PCC Rule) of the User Equipment 100. This request carries ATSSS-LLwith NC function indication information.

[0134] In response to the SMF network element's request to obtain the PCC Rule from User Equipment 100, the PCF network element sends a PCC Rule to the SMF network element. The PCC Rule includes relevant descriptive information about ATSSS-LLwith NC. This ATSSS-LLwith NC descriptive information may include network coding rules. The parameters of these network coding rules include one or more of the following: network coding type, coded sub-block number, K value, original data block number, and coded sub-block data length. The K value is the number of data packets of service data required to generate verification data based on the service data.

[0135] When an SMF network element receives a PCC Rule from a PCF network element, the SMF network element saves the network coding rules in the PCC Rule locally.

[0136] S3007, the SMF network element sends the first PDU session establishment request to the UPF network element.

[0137] In response to the first message sent by the PCF network element to the SMF network element, namely that the user equipment 100 and the UPF network element can perform multi-path transmission of service data based on ATSSS-LL with NC, the SMF network element sends a first PDU session establishment request to the UPF network element. The first PDU session establishment request is used to indicate whether the UPF network element can perform multi-link transmission of service data with the user equipment 100 based on the ATSSS-LL function and network coding.

[0138] In one possible implementation, the SMF network element can generate an N4Rule based on locally stored network coding rules, and the SMF network element sends a first PDU session establishment request to the UPF network element. The first PDU session establishment request may include the N4Rule.

[0139] In other possible implementations, the SMF network element can generate an N4 Rule based on locally stored network coding rules. The SMF network element then sends the first PDU session establishment request and the N4 Rule to the UPF network element respectively. The SMF network element may send the first PDU session establishment request and the N4 Rule to the UPF network element simultaneously, or it may send them at different times. This application embodiment does not limit this approach.

[0140] The SMF network element sends the N4 Rule to the UPF network element to inform the UPF network element of the parameter information of the network codes supported by the user equipment 100.

[0141] S3008, the UPF network element sends a second message to the SMF network element, which includes a PDU session establishment success message.

[0142] In one possible implementation, the UPF network element can send a PDU session establishment success message or a PDU session update reply message to the SMF network element. The PDU session establishment success message or PDU session update reply message carries indication information indicating multi-link transmission of service data based on ATSSS-LL function and network coding.

[0143] For example, a PDU session establishment success message or a PDU session update reply message may include character or number indication information to indicate multi-link transmission of service data based on ATSSS-LL function and network coding. This application embodiment does not specifically limit this.

[0144] In one possible implementation, the PDU session establishment success message or PDU session update reply message may also include the flow identification information of the service data, which is used to indicate the service flow corresponding to the flow identification information of the service data, and to perform multi-link transmission of the service data based on the ATSSS-LL function and network coding.

[0145] In other possible implementations, if the PDU session establishment success message or PDU session update reply message does not explicitly indicate the flow identification information of the service data, the task can be to perform multi-link transmission of service data based on the ATSSS-LL function and network coding for all possible service data.

[0146] S3009, the SMF network element sends third information to the AMF network element, including a PDU session establishment success message.

[0147] In response to the second message sent by the UPF network element, that is, the UPF network element confirms that the PDU session has been successfully established, the SMF network element generates an ATSSS Rule based on the network coding rules stored locally, and the SMF network element sends a third message to the UPF network element. The third message is used to inform the 5G base station (gNB) that the PDU session between user equipment 100 and the UPF network element has been successfully established.

[0148] In one possible implementation, the third message may carry the ATSSS Rule.

[0149] In other possible implementations, the third message may not carry the ATSSS Rule. The SMF network element can send the third message and the ATSSS Rule to the AMF network element separately. The SMF network element may send the third message and the ATSSS Rule to the AMF network element simultaneously, or the SMF network element may send the third message and the ATSSS Rule to the AMF network element at different times. This application embodiment does not limit this.

[0150] The S3010 and AMF network elements send third information to the 5G base station, including a PDU session establishment success message.

[0151] After receiving the third information sent by the SMF network element, the AMF network element sends the third information to the 5G base station (gNB), which includes a PDU session establishment success message.

[0152] If the third information carries an ATSSS Rule, the AMF network element only needs to send the third information to the 5G base station.

[0153] If the third message does not carry the ATSSS Rule, the AMF network element needs to send the third message and the ATSSS Rule to the 5G base station separately. The AMF network element may send the third message and the ATSSS Rule to the 5G base station simultaneously, or the AMF network element may send the third message and the ATSSS Rule to the 5G base station at different times. This application embodiment does not limit this.

[0154] S3011, the 5G base station sends third information to user equipment 100, including a PDU session establishment success message.

[0155] After receiving the third information sent by the AMF network element, the 5G base station sends the third information to the user equipment 100, which includes a PDU session establishment success message.

[0156] If the third information carries an ATSSS Rule, the 5G base station only needs to send the third information to the user equipment 100.

[0157] If the third message does not carry the ATSSS Rule, the 5G base station needs to send the third message and the ATSSS Rule to the user equipment 100 separately. The 5G base station may send the third message and the ATSSS Rule to the user equipment 100 simultaneously, or it may send them to the user equipment 100 at different times. This application embodiment does not limit this.

[0158] After receiving the third information sent by the 5G base station, the user equipment 100 confirms that the PDU session between the user equipment 100 and the UPF network element on the cellular mobile side has been successfully established. That is, the first data channel between the user equipment 100 and the UPF network element on the cellular mobile side has been successfully established, and the user equipment 100 and the UPF network element can transmit service data based on the first data channel.

[0159] The following describes how User Equipment 100 negotiates with UPF network elements based on ATSSS technology to obtain a non-cellular data channel and a non-cellular data channel.

[0160] Figure 4 A flowchart is shown of a user equipment (e.g., user equipment 100) negotiating a non-cellular data channel with a UPF network element based on ATSSS technology.

[0161] For example, the non-cellular data channel can be a data channel based on Wi-Fi technology.

[0162] S4001, User Equipment 100 sends a second PDU session establishment request to the Wi-Fi access device.

[0163] S4002, the Wi-Fi access device sends the second PDU session establishment request to the AMF network element.

[0164] S4003, the AMF network element sends the second PDU session establishment request to the SMF network element.

[0165] Optionally, when user equipment 100 sends a second PDU session establishment request to SMF network element through AMF network element, user equipment 100 may choose not to send ATSSS-LLwith NC capability indication information to SMF network element.

[0166] It should be noted that the PDU session identifier in the first PDU session establishment request is the same as the PDU session identifier in the second PDU session establishment request. Thus, the first data channel established through the first PDU session establishment request and the second data channel established through the second PDU session establishment request are used for transmitting service data between User Equipment 100 and the UPF network.

[0167] It should be noted that the SMF network element in S4003 and the SMF network element in S3003 are the same SMF network element.

[0168] S4004, the SMF network element sends the second PDU session establishment request to the PCF network element.

[0169] S4005 and PCF network elements determine that user equipment 100 and UPF network elements can perform multipath transmission of service data based on ATSSS-LL with NC.

[0170] S4006, the PCF network element sends a fourth message to the SMF network element. The fourth message is used to indicate that the user equipment 100 and the UPF network element can perform multipath transmission of service data based on ATSSS-LL with NC.

[0171] S4007, the SMF network element sends a second PDU session establishment request to the UPF network element.

[0172] S4008 and UPF network elements send the fifth message to SMF network elements, which includes a PDU session establishment success message.

[0173] S4009, the SMF network element sends the sixth message to the AMF network element, which includes a PDU session establishment success message.

[0174] The S4010 and AMF network elements send a sixth message to the 5G base station, which includes a PDU session establishment success message.

[0175] The S4011 and 5G base stations send the sixth message to the user equipment 100, which includes a PDU session establishment success message.

[0176] For the relevant descriptions of S4001-S4011, please refer to the detailed descriptions in S3001-S3011, only... Figure 4 The second PDU session establishment request in this embodiment is used to establish a second data channel between user equipment 100 and the UPF network element on the non-cellular mobile side. Figure 3 The first PDU session establishment request in the embodiment is used to establish a first data channel between user equipment 100 and UPF network element on the cellular mobile side. However, the principle is similar. The embodiment of this application will not elaborate on how to establish a second data channel between user equipment 100 and UPF network element on the non-cellular mobile side.

[0177] It should be noted that, Figure 3 The embodiment illustrates how to establish the first data channel on the cellular mobile side. Figure 4 The embodiment illustrates how to establish a second data channel on the non-cellular mobile side.

[0178] In other embodiments, the first data channel may also represent a data channel on the non-cellular mobile side, and the second data channel may also represent a data channel on the cellular mobile side. The embodiments of this application do not limit the types of the first data channel and the second data channel.

[0179] Figure 3 and Figure 4 The embodiments illustrate how to establish a cellular data channel and a non-cellular data channel based on ATSSS technology. This application also provides a method for establishing a cellular data channel and a non-cellular data channel without relying on ATSSS technology. For details, please refer to... Figure 5 and Figure 6 The relevant descriptions in the embodiments.

[0180] Figure 5 A flowchart is shown of a user equipment (e.g., user equipment 100) negotiating a cellular data channel with a UPF network element without relying on ATSSS technology.

[0181] For example, the cellular data channel can be a data channel based on 5G technology.

[0182] S5001, User Equipment 100 sends a third PDU session establishment request to the 5G base station (gNB).

[0183] The S5002 and 5G base stations send the third PDU session establishment request to the AMF network element.

[0184] S5003 and AMF network elements send the third PDU session establishment request to SMF network elements.

[0185] In one possible implementation, user equipment 100 sends a request to an SMF network element to establish or update a PDU session, the request including indication information that user equipment 100 supports network coding.

[0186] In one possible implementation, the indication information that the user equipment 100 supports network coding may be independent of the request to establish or update a PDU session. The indication information may be sent directly by the user equipment 100 to the SMF network element, or it may be sent separately by the user equipment 100 to the SMF network element, such as first sending it to the AMF network element, which then forwards it to the SMF network element. This application does not specifically limit this implementation.

[0187] It is understood that the user equipment 100 may also send indication information indicating that the user equipment 100 supports network coding to the SMF network element in any way according to the actual application scenario. The indication information indicating that the user equipment 100 supports network coding indicates that the user equipment 100 supports the function of network coding. This application embodiment does not specifically limit this.

[0188] The PDU session described in the embodiments of this application can be a protocol data unit (PDU) session or a packet data unit (PDU) session.

[0189] One possible understanding of the user equipment 100 supporting network coding described in the embodiments of this application is that the user equipment 100 supports network coding functionality, enabling the user equipment 100 to perform the methods as described in the embodiments of this application based on the network coding functionality.

[0190] In this embodiment of the application, when transmitting indication information indicating that user equipment 100 supports network coding between different network elements, the form and content of the indication information may be different or the same. The indication information indicating that user equipment 100 supports network coding mentioned in this embodiment of the application is used to illustrate the function of the indication information and does not limit its specific form. For example, in subsequent embodiments, user equipment 100 may send indication information indicating that user equipment 100 supports network coding to SMF network elements, SMF network elements may send indication information indicating that user equipment 100 supports network coding to PCF network elements, etc. The form and content of the indication information indicating that user equipment 100 supports network coding may be the same or different between different network elements.

[0191] S5004, the SMF network element sends the third PDU session establishment request to the PCF network element.

[0192] In this embodiment of the application, the SMF network element obtains the indication information that the user equipment 100 supports network coding, and can further combine the capabilities of the device that transmits data with the user equipment 100 (such as the UPF network element) to determine whether to send the indication information that the user equipment 100 supports network coding to the PCF network element.

[0193] For example, taking a UPF network element as the device transmitting data with user equipment 100, the SMF network element can determine that the UPF supports network coding capabilities. For instance, the SMF network element selects a UPF based on its functions, including support for network coding. Alternatively, the SMF network element receives indication information from the UPF network element that user equipment 100 supports network coding. When both user equipment 100 and the UPF network element support network coding, the SMF network element determines that the network supports network coding capabilities and can send this indication information to the PCF network element.

[0194] For example, an SMF network element can include indications that user equipment 100 supports network coding in a policy request message sent to a PCF network element.

[0195] S5005 and PCF network elements determine that user equipment 100 and UPF network elements can transmit service data based on network coding function.

[0196] In this embodiment of the application, the PCF network element can determine the user equipment 100 and can transmit service data based on the network coding capability sent by the SMF network element.

[0197] S5006, PCF network element sends a first message to SMF network element. The first message is used to indicate that user equipment 100 and UPF network element can transmit service data based on network coding function.

[0198] For example, the first information may include indication information for performing network coding functions. This indication information is used to instruct the transmission of service data based on network coding functions.

[0199] For example, the first information may be characters or numbers, which are used to indicate information for performing network coding functions. This application embodiment does not specifically limit this.

[0200] In one possible implementation, the first information may further include flow identification information of the business data, which is used to indicate that network coding is performed on the business data corresponding to the flow identification information of the business data.

[0201] In one possible implementation, if the first information does not explicitly indicate the flow identification information of the business data, network coding can be performed on all possible business data.

[0202] Before the PCF network element sends the first message to the SMF network element, the SMF network element sends a request to the PCF network element to obtain the Policy and Charging Control Rule (PCC Rule) of User Equipment 100. This request carries indication information for network coding functions.

[0203] In response to the SMF network element's request to obtain the PCC Rule from user equipment 100, the PCF network element sends a PCC Rule to the SMF network element. The PCC Rule includes descriptive information related to the network coding function. The network coding function may include network coding rules, and the parameters of these rules include one or more of the following: network coding type, coded sub-block number, K value, original data block number, and coded sub-block data length. The K value is the number of data packets of service data required to generate verification data based on the service data.

[0204] When an SMF network element receives a PCC Rule from a PCF network element, the SMF network element saves the network coding rules in the PCC Rule locally.

[0205] S5007, the SMF network element sends a third PDU session establishment request to the UPF network element.

[0206] In response to the first message sent by the PCF network element to the SMF network element, indicating that the user equipment 100 and the UPF network element can transmit service data based on the network coding function, the SMF network element sends a third PDU session establishment request to the UPF network element. The third PDU session establishment request is used to indicate whether the UPF network element can transmit service data with the user equipment 100 based on the network coding function.

[0207] Before the SMF network element sends the third PDU session establishment request to the PCF network element, the SMF network element also needs to generate the identifier of the currently negotiated data channel, i.e., the cellular-side data channel identifier, which can be represented by the source QFI. The source QFI is used to indicate that it can be a cellular-side data channel identifier.

[0208] SMF network elements can generate PDRs based on locally stored network coding rules. SMF network elements send third PDU session establishment requests to UPF network elements, and the third PDU session establishment requests may include PDRs.

[0209] The PDR includes network encoding rules and source QFI.

[0210] In other possible implementations, the SMF network element can generate a PDR based on locally stored network coding rules and sourceQFI. The SMF network element then sends the third PDU session establishment request and the PDR to the UPF network element respectively. The SMF network element can send the third PDU session establishment request and the PDR to the UPF network element simultaneously, or it can send them at different times. This application embodiment does not limit this approach.

[0211] The SMF network element sends the PDR to the UPF network element to inform the UPF network element of the parameter information of the network codes supported by the user equipment 100.

[0212] The S5008 and UPF network elements send a second message to the SMF network element, which includes a PDU session establishment success message.

[0213] In one possible implementation, the UPF network element can send a PDU session establishment success message or a PDU session update reply message to the SMF network element. The PDU session establishment success message or PDU session update reply message carries indication information for transmitting service data based on network coding function.

[0214] For example, a PDU session establishment success message or a PDU session update reply message may include characters or numbers, which are used to indicate information for transmitting service data based on network coding functions. This application embodiment does not specifically limit this.

[0215] In one possible implementation, the PDU session establishment success message or PDU session update reply message may also include flow identification information of the service data, which is used to indicate that network coding function is performed for the service flow corresponding to the flow identification information of the service data.

[0216] In other possible implementations, if the PDU session establishment success message or PDU session update reply message does not explicitly indicate the flow identification information of the service data, the task can be to perform network coding for all possible service data.

[0217] S5009, the SMF network element sends third information to the AMF network element, including a PDU session establishment success message.

[0218] In response to the second message sent by the UPF network element, namely the UPF network element confirming the successful establishment of the PDU session, the data channel between the user equipment 100 and the UPF network element on the cellular side is successfully established.

[0219] Then, the SMF network element generates a QoS rule based on the locally stored network coding rules, and sends a third message to the UPF network element. The third message is used to inform the 5G base station (gNB) that the PDU session between user equipment 100 and the UPF network element has been successfully established.

[0220] The QoS rule includes network coding rules and sourceQFI.

[0221] In one possible implementation, the third message may carry the QoS rule.

[0222] In other possible implementations, the third message may not carry the QoS rule, and the SMF network element can send the third message and the QoS rule to the AMF network element separately. The SMF network element may send the third message and the QoS rule to the AMF network element simultaneously, or the SMF network element may send the third message and the QoS rule to the AMF network element at different times. This application embodiment does not limit this.

[0223] The S5010 and AMF network elements send third information to the 5G base station, including a PDU session establishment success message.

[0224] After receiving the third information sent by the SMF network element, the AMF network element sends the third information to the 5G base station (gNB), which includes a PDU session establishment success message.

[0225] If the third information carries a QoS rule, the AMF network element only needs to send the third information to the 5G base station.

[0226] If the third message does not carry a QoS rule, the AMF network element needs to send the third message and the QoS rule to the 5G base station separately. The AMF network element may send the third message and the QoS rule to the 5G base station simultaneously, or it may send them at different times. This application embodiment does not limit this.

[0227] The S5011 and 5G base stations send third information to user equipment 100, including a PDU session establishment success message.

[0228] After receiving the third information sent by the AMF network element, the 5G base station sends the third information to the user equipment 100, which includes a PDU session establishment success message.

[0229] If the third information carries a QoS rule, the 5G base station only needs to send the third information to the user equipment 100.

[0230] If the third message does not carry a QoS rule, the 5G base station needs to send the third message and the QoS rule to the user equipment 100 separately. The 5G base station may send the third message and the QoS rule to the user equipment 100 simultaneously, or it may send them to the user equipment 100 at different times. This application embodiment does not limit this.

[0231] After receiving the third information sent by the 5G base station, User Equipment 100 confirms that the PDU session between User Equipment 100 and the UPF network element on the cellular mobile side has been successfully established. This means that the first data channel between User Equipment 100 and the UPF network element on the cellular mobile side has been successfully established, and User Equipment 100 and the UPF network element can transmit service data based on the first data channel. The data channel identifier for transmitting service data described in S5007 above refers to the identifier of the first data channel between User Equipment 100 and the UPF network element on the cellular mobile side; specifically, the source QFI is used to indicate the identifier of the first data channel between User Equipment 100 and the UPF network element on the cellular mobile side.

[0232] The following describes how User Equipment 100 negotiates with UPF network elements to obtain a non-cellular data channel and a non-cellular data channel based on ATSSS technology.

[0233] Figure 6 A flowchart is shown of a user equipment (e.g., user equipment 100) negotiating a non-cellular data channel with a UPF network element without relying on ATSSS technology.

[0234] For example, the non-cellular data channel can be a data channel based on Wi-Fi technology.

[0235] S6001, User Equipment 100 sends a fourth PDU session establishment request to the Wi-Fi access device.

[0236] S6002, the Wi-Fi access device sends the fourth PDU session establishment request to the AMF network element.

[0237] S6003, the AMF network element sends the fourth PDU session establishment request to the SMF network element.

[0238] Optionally, when user equipment 100 sends a fourth PDU session establishment request to SMF network element through AMF network element, user equipment 100 may not send an indication message to SMF network element indicating that user equipment 100 supports network coding.

[0239] It should be noted that the SMF network element in S6003 and the SMF network element in S5003 are the same SMF network element.

[0240] S6004, the SMF network element sends the fourth PDU session establishment request to the PCF network element.

[0241] S6005 and PCF network elements determine that user equipment 100 and UPF network elements can transmit service data based on network coding function.

[0242] S6006, PCF network element sends a fourth message to SMF network element. The fourth message is used to indicate that user equipment 100 and UPF network element can transmit service data based on network coding function.

[0243] S6007, the SMF network element sends a fourth PDU session establishment request to the UPF network element.

[0244] S6008 and UPF network elements send the fifth message to SMF network elements, which includes a PDU session establishment success message.

[0245] S6009, the SMF network element sends the sixth message to the AMF network element, which includes a PDU session establishment success message.

[0246] The S6010 and AMF network elements send a sixth message to the 5G base station, which includes a PDU session establishment success message.

[0247] S6011, the 5G base station sends the sixth message to the user equipment 100, which includes a PDU session establishment success message.

[0248] For the relevant descriptions of S6001-S6011, please refer to the detailed descriptions in S5001-S5011, only... Figure 6 The fourth PDU session establishment request in the embodiment is used to establish a second data channel between user equipment 100 and the UPF network element on the non-cellular mobile side. Figure 5 The third PDU session establishment request in the embodiment is used to establish the first data channel between the user equipment 100 and the UPF network element on the cellular mobile side. However, the principle is similar. The embodiment of this application will not elaborate on how to establish the second data channel between the user equipment 100 and the UPF network element on the non-cellular mobile side.

[0249] but Figure 5 and Figure 6 The difference is:

[0250] In S6001, user equipment 100 sends a fourth PDU session establishment request to the Wi-Fi access device. At the same time, user equipment 100 also needs to send source QFI to the Wi-Fi access device.

[0251] Optionally, if the fourth PDU session establishment request sent by the SMF network element to the PCF network element carries source QFI, then the user equipment 100 only needs to send the fourth PDU session establishment request to the Wi-Fi access device.

[0252] If the user equipment 100 does not include the source QFI in the fourth PDU session establishment request sent to the Wi-Fi access device, then the user equipment 100 needs to send the fourth PDU session establishment request and the source QFI to the Wi-Fi access device separately. The user equipment 100 may send the fourth PDU session establishment request and the source QFI to the Wi-Fi access device simultaneously, or it may send them at different times; this embodiment does not limit this.

[0253] Second, in S6007, before the SMF network element sends the fourth PDU session establishment request to the UPF network element, the SMF network element also needs to generate an identifier for the currently negotiated data channel, i.e., the non-cellular data channel identifier, which can be represented by Parity QFI. Parity QFI is used to indicate that it can be a non-cellular data channel identifier.

[0254] The SMF network element needs to send the fourth PDU session establishment request and Parity QFI to the PCF network element.

[0255] If the fourth PDU session establishment request sent by the SMF network element to the PCF network element carries Parity QFI, then the AMF network element only needs to send the fourth PDU session establishment request to the PCF network element.

[0256] If the fourth PDU session establishment request sent by the SMF network element to the PCF network element does not carry the Parity QFI, then the AMF network element needs to send the fourth PDU session establishment request and the Parity QFI to the PCF network element separately. The AMF network element may send the fourth PDU session establishment request and the Parity QFI to the PCF network element simultaneously, or the AMF network element may send the third PDU session establishment request and the Parity QFI to the PCF network element at different times. This application embodiment does not limit this.

[0257] 3. In S6007, after obtaining the Parity QFI, the SMF network element needs to modify the PDR. The PDR contains the network coding rules, source QFI, and Parity QFI.

[0258] In a possible implementation, the SMF network element sends the fourth PDU session establishment request and the modified PDR to the UPF network element respectively. The SMF network element may send the fourth PDU session establishment request and the modified PDR to the UPF network element simultaneously, or the SMF network element may send the fourth PDU session establishment request and the modified PDR to the UPF network element at different times. This application embodiment does not limit this.

[0259] The SMF network element sends the modified PDR to the UPF network element to inform the UPF network element of the types of the two communication paths currently created.

[0260] IV. In S6009, SMF network elements need to modify the QoS rule, which includes network coding rules, sourceQFI, and ParityQFI.

[0261] In one possible implementation, the sixth message may carry the modified QoS rule.

[0262] In other possible implementations, the sixth message may not carry the modified QoS rule. The SMF network element can send the sixth message and the modified QoS rule to the AMF network element separately. The SMF network element may send the sixth message and the modified QoS rule to the AMF network element simultaneously, or the SMF network element may send the sixth message and the modified QoS rule to the AMF network element at different times. This application embodiment does not limit this.

[0263] The SMF network element sends the modified QoS rule to the user equipment 100 through the AMF network element to inform the user equipment 100 of the types of the two communication paths currently created.

[0264] It should be noted that, Figure 5 The embodiment illustrates how to establish the first data channel on the cellular mobile side. Figure 6 The embodiment illustrates how to establish a second data channel on the non-cellular mobile side.

[0265] In other embodiments, the first data channel may also represent a data channel on the non-cellular mobile side, and the second data channel may also represent a data channel on the cellular mobile side. The embodiments of this application do not limit the types of the first data channel and the second data channel.

[0266] It should be noted that, Figures 3-4 , Figures 5-6 This application merely illustrates two methods for user equipment 100 to negotiate multiple communication paths with UPF network elements. Multiple communication paths can also be negotiated based on other methods, and this application does not limit the scope of these methods.

[0267] The foregoing Figures 3-4 , Figures 5-6 Two methods for user equipment 100 to negotiate multiple communication paths with UPF network elements are illustrated. As can be seen from the foregoing description, N4 Rule, ATSSS Rule, PCC Rule and pdr carry network coding rules. The specific enhancement information of N4 Rule, ATSSS Rule, PCC Rule and pdr is shown in Table 1.

[0268] Table 1

[0269]

[0270] Table 1 provides examples of specific enhancements to the N4 Rule, ATSSS Rule, PCC Rule, and PDR. The information name includes the ATSSS Rule ID, a unique identifier used to identify the ATSSS rule. The ATSSS Rule ID category is conditional, and the ATSSS Rule ID does not allow modification of the SMF within the PDU context. The scope of the ATSSS Rule ID is the PDU context. The information name also includes Rule Priority, which determines the order in which ATSSS rules are evaluated within the user equipment. The Rule Priority category is mandatory, and the Rule Priority allows modification of the SMF within the PDU context. The scope of the Rule Priority is the PDU context. The information name also includes a Traffic Descriptor, which defines the traffic descriptor component of the ATSSS rule. The Traffic Descriptor category is mandatory, and the scope of the Traffic Descriptor is the PDU context. The information name also includes an Application Descriptor, which identifies one or more application identifiers of the application that generates the traffic. The Application Descriptor category is optional, and the Application Descriptor allows modification of the SMF within the PDU context. The scope of the Application Descriptor is the PDU context. The information name also includes an IP descriptor, which identifies one or more 5-tuples of the IP communication destination. The IP descriptor category is optional, and the IP descriptor allows modification of the SMF within the PDU context. The scope of the IP descriptor is the PDU context. The information name also includes an access selection descriptor, which defines the access selection descriptor component of the ATSSS rule. The access selection descriptor category is mandatory, and the scope of the access selection descriptor is the PDU context. The information name also includes a redirection mode, which includes network coding, active standby, minimum latency, load balancing, and priority-based. Information about the redirection mode includes one or more of the following: network coding type, coded subblock number, K value, original data block number, and coded subblock data length. The K value is the number of packets of service data required to generate the checksum data. The redirection mode is used to determine the redirection mode applied to matching traffic and related parameters. The redirection mode category is mandatory, and the redirection mode allows modification of the SMF within the PDU context. The scope of the redirection mode is the PDU context. The information name also includes a steering mode indicator, which indicates automatic load balancing or UE-assisted operation if the steering mode is set to load balancing. The category of the steering mode indicator is selectable, and the steering mode indicator allows modification of the SMF within the PDU context. The scope of the steering mode indicator is the PDU context. The information name also includes a threshold, which indicates the maximum RTT and / or maximum packet loss rate. The category of the threshold is selectable, and the threshold allows modification of the SMF within the PDU context. The scope of the threshold is the PDU context.The information name also includes redirection functions, which are used to determine whether the MPTCP function or the ATSSS LLS function should be applied to the matching traffic. The category of the redirection function is optional. The redirection function allows modification of the SMF in the PDU context. The scope of the redirection function is the PDU context.

[0271] After the user equipment 100 negotiates and obtains multiple communication paths with the UPF network element, the user equipment 100 and the UPF network element can transmit service data based on the negotiated multiple communication paths.

[0272] Figure 7 An exemplary flowchart illustrates a method for transmitting service data between user equipment 100 and UPF network elements based on a first data channel and a second data channel.

[0273] S7001, The first device receives the first extended reality service data.

[0274] The first device can be the UPF network element described in the foregoing embodiments.

[0275] The first extended reality business data can be the business data described in the foregoing embodiments.

[0276] The first device receives the first extended reality service data sent by the provider of the extended reality service data.

[0277] It should be noted that the data transmission method provided in this application is applicable not only to extended real-world business data, but also to other business data. This application only uses extended real-world business data as an example for illustration and should not be construed as limiting the scope of the application.

[0278] S7002, The first device generates verification data for the first extended reality service data based on the first extended reality service data.

[0279] After receiving the first extended reality service data, the first device performs network encoding on the first extended reality service data based on the locally stored N4 rule or PDR to obtain the verification data of the first extended reality service data.

[0280] Specifically, after acquiring the service data, the first device obtains k data packets within a frame and their contents. Based on the contents of the k data packets and a preset encoding rule, the first device generates m checksum data packets, which serve as the checksum data for the k data packets within the frame. If the number of remaining data packets within a frame is less than k, empty IP packets are added to ensure that the number of remaining data packets within the frame is k. Based on the above method, the first device obtains the checksum data for the first extended real-time service data.

[0281] Before the first device receives the first extended reality service data, the method further includes: the first device receiving and saving network coding rules, the network coding rules being used by the first device to generate verification data of the first extended reality service data based on one or more of the network coding type, coding sub-block number, K value, original data block number, and coded sub-block data length, wherein the K value is the number of data packets of the first extended reality service data required to generate the verification data of the first extended reality service data.

[0282] S7003, the first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device through the first data channel and the second data channel.

[0283] The second device may be the user equipment 100 described in the foregoing embodiments.

[0284] The first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device through the first data channel and the second data channel, including the following four methods:

[0285] Method 1: The first device sends the first extended reality service data to the second device through the first data channel, and the first device sends the verification data of the first extended reality service data to the second device through the first data channel.

[0286] Method 2: The first device sends the verification data of the first extended reality business data to the second device through the first data channel.

[0287] Method 3: The first device simultaneously sends the first extended reality service data and its verification data to the second device through both the first and second data channels. That is, the first device does not distinguish between the first extended reality service data and its verification data; it mixes the two sets of data, sends a portion of the first extended reality service data and its verification data through the first data channel to the second device, and sends the remaining portion of the first extended reality service data and its verification data through the second data channel to the second device.

[0288] Method 4: The first device transmits the first extended reality service data and its verification data proportionally based on the transmission quality (e.g., transmission latency, packet loss rate, jitter rate) of the first and second data channels. That is, if the transmission quality of the first data channel is better than that of the second data channel, the first device will transmit most of the first extended reality service data and its verification data to the second device through the first data channel. The first device will transmit a small portion of the first extended reality service data and its verification data to the second device through the second data channel.

[0289] The second device receives first extended reality service data and verification data of the first extended reality service data sent by the first device through a first data channel and a second data channel. The verification data of the first extended reality service data is used by the second device to recover the first extended reality service data when it receives erroneous first extended reality service data.

[0290] The second device also needs to determine which data channel received the first extended reality service data and which data channel received the verification data of the first extended reality service data.

[0291] The second device can determine which data channel receives the first extended reality service data and which data channel receives the verification data of the first extended reality service data in any of the following ways.

[0292] Method 1: Before the first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device through the first data channel and the second data channel, the first device sends a first message to the second device through the SMF network element and the AMF network element. The first message is used to inform the second device that the first device has performed network coding function and the data type (service data or verification data) transmitted by the first data channel and the second data channel.

[0293] Method 2: Before the first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device via the first data channel and the second data channel, the first device adds a first field to the header of the first extended reality service data packet or the header of the first extended reality service data verification data packet. The first field indicates that the first device has sent the verification data of the first extended reality service data, and specifies the data type (service data or verification data) transmitted by the first data channel and the second data channel. Thus, if the header of the first extended reality service data packet also includes the first field, the second device can confirm that the data packet is the first extended reality service data packet based on this first field. Similarly, if the header of the first extended reality service data verification data packet also includes the first field, the second device can confirm that the data packet is the verification data packet of the first extended reality service data based on this first field.

[0294] Figure 8 An exemplary diagram is shown of the header format of the first extended reality business data or the header format of the verification data of the first extended reality business data.

[0295] Figure 8 The header shown includes, but is not limited to, the following fields: version, header length, type of service, total length, identifier, flag, fragment offset, lifetime, protocol, header checksum, source IP address, destination IP address, any field with variable length, and padding fields, etc.

[0296] The first device can add a first field to the service type field. The first field can be... Figure 8 The unused fields are shown.

[0297] It should be noted that the first device may add the first field to other fields, and this application embodiment does not limit this.

[0298] Method 3: Before the first device sends the first extended reality service data and the verification data of the first extended reality service data to the second device via the first data channel and the second data channel, the first device checks whether the format in the header of the first extended reality service data or the header of the verification data of the first extended reality service data is the same as the preset format in the ATSSS rule or QoS rule. The preset format can be a 5-tuple.

[0299] Thus, if the five-tuple in the header of the first extended reality service data packet has the same format as the five-tuple in the ATSSS rule or QoS rule, the second device can determine that the data packet is the first extended reality service data packet based on this first field. Similarly, if the five-tuple in the header of the checksum data of the first extended reality service data packet has the same format as the five-tuple in the ATSSS rule or QoS rule, the second device can determine that the data packet is the checksum data packet of the first extended reality service data based on this first field.

[0300] After the second device receives the first extended reality service data and the verification data of the first extended reality service data sent by the first device through the first data channel and the second data channel, if the first extended reality service data is erroneous, the second device needs to decode the erroneous first extended reality service data to recover the correct first extended reality service data.

[0301] The second device can recover the correct first extended reality business data through any of the following methods:

[0302] Figures 9-11 An exemplary diagram illustrates a functional module for the second device to recover and obtain the correct first extended reality business data.

[0303] Method 1: For example Figure 9 As shown, the second device's app integrates an SDK module with independent decoding capabilities. When the first data channel receiving module receives erroneous first extended reality service data, and the second data channel receiving module receives verification data for the first extended reality service data, the first data channel receiving module sends the erroneous first extended reality service data to the SDK module, and the second data channel receiving module sends the verification data for the erroneous first extended reality service data to the SDK module. Upon receiving both the erroneous first extended reality service data and the verification data for the first extended reality service data, the SDK module decodes the erroneous first extended reality service data based on preset encoding rules and the verification data, recovering the correct first extended reality service data. Afterward, the SDK module can send the correct first extended reality service data to the corresponding display block for display.

[0304] Method 2: For example Figure 10As shown, the first data channel receiving module has independent decoding capabilities. When the first data channel receiving module receives erroneous first extended reality service data, and the second data channel receiving module receives the verification data of the first extended reality service data, the second data channel receiving module sends the verification data of the erroneous first extended reality service data to the first data channel receiving module. Upon receiving both the erroneous first extended reality service data and the verification data of the first extended reality service data, the first data channel receiving module decodes the erroneous first extended reality service data based on preset encoding rules and the verification data, recovering the correct first extended reality service data. Afterwards, the first data channel receiving module can send the correct first extended reality service data to the corresponding display block for display.

[0305] Optionally, the second data channel data receiving module has separate decoding capabilities. This application does not limit this aspect.

[0306] Method 3: For example Figure 11 As shown, the display module of the second device has independent decoding capabilities. After the first data channel receiving module receives erroneous first extended reality service data, and the second data channel receiving module receives verification data for the first extended reality service data, the first data channel receiving module sends the erroneous first extended reality service data to the display module, and the second data channel receiving module sends the verification data for the erroneous first extended reality service data to the display module. Upon receiving both the verification data and the verification data for the first extended reality service data, the display module decodes the erroneous first extended reality service data based on preset encoding rules and the verification data, recovering the correct first extended reality service data. Afterwards, the display module can display the correct first extended reality service data.

[0307] In Method 1 to Method 3, the display module can be an application.

[0308] The first data channel data receiving module mentioned in Method 1 to Method 3 can be a module that receives data through the first data channel, and the second data channel data receiving module can be a module that receives data through the second data channel.

[0309] In other embodiments, the verification data of the first extended reality service data can be received through the first data channel data receiving module, and the first extended reality service data can be received through the second data channel data receiving module. This application does not limit this approach.

[0310] The various embodiments of this application can be combined arbitrarily to achieve different technical effects.

[0311] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0312] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0313] In summary, the above description is merely an embodiment of the technical solution of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made according to the disclosure of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data transmission method, characterized in that, The method includes: The first device receives the first extended reality service data; The first device generates verification data for the first extended reality service data based on the first extended reality service data; The first device mixes the first extended reality service data and the verification data of the first extended reality service data, sends a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data to the second device through the first data channel, and sends another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data to the second device through the second data channel. Wherein, the verification data of the first extended reality service data is used by the second device to recover the first extended reality service data when it receives erroneous first extended reality service data; The first data channel and the second data channel can be of any of the following types: cellular data channel and non-cellular data channel.

2. The method according to claim 1, characterized in that, Before the first device receives the first extended reality service data, the method further includes: The first device receives and saves network coding rules. The network coding rules are used by the first device to generate verification data of the first extended reality service data based on one or more of the following: network coding type, coding sub-block number, K value, original data block number, and coded sub-block data length. The K value is the number of data packets of the first extended reality service data required by the first device to generate the verification data of the first extended reality service data.

3. The method according to claim 1 or 2, characterized in that, The first device generates verification data for the first extended reality service data based on the first extended reality service data, specifically including: The first device acquires k data packets from the first extended reality service data; The first device generates m verification packets based on the k data packets, where m is less than or equal to k.

4. The method according to claim 1 or 2, characterized in that, Before the first device generates verification data for the first extended reality service data based on the first extended reality service data, the method further includes: The first device sends a first message to the second device, the first message being used to indicate that the first device has sent the verification data of the first extended reality service data.

5. The method according to claim 1 or 2, characterized in that, The header of the first extended reality service data or the header of the first extended reality service data verification data further includes a first field, which is used to indicate that the first device has sent the verification data of the first extended reality service data.

6. The method according to claim 1 or 2, characterized in that, Before the first device sends a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data to the second device through the first data channel, and before sending another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data to the second device through the second data channel, the method further includes: The first device establishes the first data channel and the second data channel with the second device based on the underlying ATSSS capability of the access service flow routing and switching.

7. The method according to claim 6, characterized in that, The first device establishes the first data channel and the second data channel with the second device based on the underlying ATSSS capability for routing and switching of access service flows, specifically including: The first device receives a first PDU session establishment request sent by the second device. The first PDU session establishment request includes a first ATSSS Capabilities, which contains information about network coding supported by the second device. The first device establishes the first data channel with the second device; The first device receives a second PDU session establishment request sent by the second device. The second PDU session establishment request includes a second ATSSS Capabilities, which contains information about the recipient of the first extended reality service data supporting network coding. The first device establishes the second data channel with the second device.

8. The method according to claim 1 or 2, characterized in that, Before the first device sends a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data to the second device through the first data channel, and before sending another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data to the second device through the second data channel, the method further includes: The first device receives a third PDU session establishment request sent by the second device, the third PDU session establishment request including indication information for performing network coding; The first device establishes the first data channel with the second device; The first device receives a fourth PDU session establishment request sent by the second device, the fourth PDU session establishment request including indication information for performing network coding; The first device establishes the second data channel with the second device.

9. A data transmission method, characterized in that, The method includes: The second device receives a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data sent by the first device through the first data channel. The second device receives another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data sent by the first device through the second data channel; Wherein, the verification data of the first extended reality service data is used by the second device to recover the first extended reality service data when it receives erroneous first extended reality service data; The first data channel and the second data channel can be of any of the following types: cellular data channel and non-cellular data channel.

10. The method according to claim 9, characterized in that, Before the second device receives a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data sent by the first device through the first data channel, and before the second device receives another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data sent by the first device through the second data channel, the method further includes: The system receives a first message sent by the first device, the first message indicating that the first device has sent verification data for the first extended reality service data.

11. The method according to claim 9 or 10, characterized in that, The header of the first extended reality service data or the header of the first extended reality service data verification data further includes a first field, which is used to indicate that the first device has sent the verification data of the first extended reality service data.

12. The method according to claim 9 or 10, characterized in that, Before the second device receives a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data sent by the first device through the first data channel, and before the second device receives another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data sent by the first device through the second data channel, the method further includes: The second device establishes the first data channel and the second data channel with the first device based on the underlying ATSSS capability of the access service flow routing and switching.

13. The method according to claim 12, characterized in that, The second device establishes the first data channel and the second data channel with the first device based on the underlying ATSSS capability for routing and switching of access service flows, specifically including: The second device sends a first PDU session establishment request to the first device. The first PDU session establishment request includes a first ATSSS Capabilities, which contains information about the network coding supported by the second device. The second device establishes the first data channel with the first device; The second device sends a second PDU session establishment request to the first device. The second PDU session establishment request includes a second ATSSS Capabilities, which contains information about network coding supported by the second device. The second device establishes the second data channel with the first device.

14. The method according to claim 9 or 10, characterized in that, Before the second device receives a portion of the first extended reality service data and a portion of the verification data of the first extended reality service data sent by the first device through the first data channel, and before the second device receives another portion of the first extended reality service data and another portion of the verification data of the first extended reality service data sent by the first device through the second data channel, the method further includes: The second device sends a third PDU session establishment request to the first device, the third PDU session establishment request including indication information for performing network coding; The second device establishes the first data channel with the first device; The second device sends a fourth PDU session establishment request to the first device, the fourth PDU session establishment request including indication information for performing network coding; The second device establishes the second data channel with the first device.

15. A device, characterized in that, The device includes: one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, the one or more memories are used to store computer program code, the computer program code including computer instructions, and the one or more processors invoke the computer instructions to cause the device to perform the method of any one of claims 1-8 or 9-14.

16. A chip or chip system, characterized in that, It includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as described in any one of claims 1-8 or 9-14.

17. A computer-readable storage medium storing instructions that, when executed on a device, cause the device to perform the method as described in any one of claims 1-8 or 9-14.

18. A computer program product, characterized in that, When the computer program product is run on the device, it causes the device to perform the method as described in claims 1-8 or any one of claims 9-14.

Images