Communication method, device and system

Abstract

The embodiment of the invention provides a communication method, device and system, and relates to the technical field of communication. The method comprises: a terminal device establishing a plurality of transmission channels with a first network element; and sending the first field information to the first network element. Wherein the first field information comprises a pairing protocol field, the pairing protocol field comprises an identifier of the terminal equipment, and the pairing protocol field is used for indicating that a plurality of transmission channels in the terminal equipment are paired to form a redundant transmission channel. The multiple transmission channels between the terminal equipment and the first network element do not need to be statically configured, a chip of the terminal equipment does not need to be changed, automatic pairing can be performed through the first field information, a redundant transmission channel is formed, and redundant transmission is achieved.

Description

Technical Field

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

[0002] In 5G (5th generation mobile networks), data transmission between terminal devices and base stations is conducted wirelessly. Compared to wired transmission, the air interface in wireless transmission is more susceptible to interference, resulting in lower reliability. To improve air interface reliability and meet the high-reliability transmission requirements of certain service scenarios, multi-path redundancy transmission technology is typically employed. In multi-path redundancy transmission, terminal devices use multiple communication modules to establish packet data unit (PDU) connections with user plane function (UPF) network elements, with these PDU connections exhibiting paired redundancy. The terminal devices converge redundant paths through redundant transceiver modules, and the network side converges redundant paths through UPF network elements. Ultimately, this achieves transparent redundant transmission to external service devices and the data network, thereby improving the reliability of wireless transmission.

[0003] In establishing redundant transmission channels for multiple PDU connections, the network side needs to be aware of the pairing relationships between the multiple PDU connections, as well as the redundant transmission protocols used by the redundant transmission channels. Currently, the pairing relationships between multiple PDU connections are mainly indicated through static configuration or 5G signaling. However, static configuration is not flexible enough and is prone to errors in practical use; while indicating the pairing relationships between multiple PDU connections through 5G signaling relies heavily on the cooperation between 5G terminal chips and the 5G network, resulting in a complex ecosystem. Therefore, a simple and flexible method is urgently needed to achieve redundant transmission of multiple PDU paths. Summary of the Invention

[0004] This application provides a communication method, apparatus, and system. This solution can achieve redundant transmission of multiple PDU connections without relying on static network configuration or modification of terminal chips, enabling multiple subscribed users to dynamically form pairs when creating PDU connections, thus achieving simple and flexible multi-PDU connection redundancy.

[0005] The technical solution is as follows:

[0006] In a first aspect, embodiments of this application provide a communication method, the method comprising: a terminal device establishing multiple transmission channels with a first network element; the terminal device sending first field information to the first network element; the first field information including a pairing protocol field, the pairing protocol field including an identifier of the terminal device; the pairing protocol field being used to indicate that multiple transmission channels in the terminal device are paired to form redundant transmission channels.

[0007] In this application, the terminal device first establishes multiple transmission channels with the first network element, and then sends first field information to the first network element through these transmission channels. The first field information includes a pairing protocol field, which includes the identifier of the terminal device. This pairing protocol field instructs the multiple transmission channels in the terminal device to pair up to form redundant transmission channels. The multiple transmission channels between the terminal device and the first network element do not require static configuration or modification of the terminal device's chip; they can automatically pair up through the first field information to form redundant transmission channels, thus achieving redundant transmission.

[0008] In one possible implementation, the terminal device sends the first field information to the first network element, including: the terminal device receiving a first service message from the first device; the terminal device adding the first field information to the service message to obtain the first service message; and the terminal device sending the first service message to the first network element.

[0009] As an example, the terminal device adds the first field information to the first service message through the redundant protocol stack and pairing protocol stack in the terminal device.

[0010] In one possible implementation, the terminal device sends the first field information to the first network element, including: the terminal device receiving a second service message from the first network element, the second service message not carrying the first field information; and the terminal device sending a protocol message to the first network element based on the second service message, the protocol message including the first field information.

[0011] As an example, the first network element forwards the second service packet to the terminal device according to the forwarding rules of the service packet. For example, when the service packet type is a broadcast packet, the first network element forwards the downlink service packet to each PDU session, and the PDU session then forwards the downlink service packet to the terminal device. As another example, when the service packet type is a unicast packet, the first network element forwards the downlink service packet to a specific PDU session, and that PDU session then forwards the downlink service packet to the terminal device.

[0012] In one possible implementation, redundant transmission methods for multiple transmission channels include dual-transmission selective reception and load balancing.

[0013] As an example, in the case of redundant transmission mode with dual transmit and receive in multiple transmission channels, each transmission channel is used to send the same first field information.

[0014] As another example, in the case of redundant transmission of multiple transmission channels with load balancing, one of the multiple transmission channels is used to send the first field information.

[0015] In one possible implementation, when the redundant transmission mode of multiple transmission channels is dual-transmit selective-receive, the first field information also includes a redundancy protocol field. This redundancy protocol field is used to identify that the first field information is being transmitted redundantly. Specifically, the redundancy protocol field is used to remove duplicate data from the service message.

[0016] In one possible implementation, the method provided in this application further includes: a terminal device receiving a third service message from a first network element, the third service message carrying first field information; the terminal device stripping the pairing protocol field from the first field information; and the terminal device sending the third service message stripped of the pairing protocol field to the first device.

[0017] In one possible implementation, where the first field information includes a redundant protocol field, the method provided in this application embodiment further includes: the terminal device removing duplicate data from the third service message and stripping the redundant protocol field. The terminal device sends a third service message stripped of the pairing protocol field and the redundant protocol field to the first device.

[0018] Secondly, embodiments of this application provide a communication method, the method comprising: a first network element receiving redundant communication information, the redundant communication information being used to indicate that a terminal device is permitted to form a redundant transmission channel, the redundant communication information including the identifier of the terminal device and information on the redundant transmission method; the first network element receiving first field information from the terminal device, the first field information including a pairing protocol field, the pairing protocol field including the identifier of the terminal device, the pairing protocol field being used to indicate that multiple transmission channels of the terminal device are paired to form a redundant transmission channel.

[0019] In one possible implementation, the first network element receives first field information from the terminal device, including: the first network element receives a first service message from the terminal device, the first service message including the first field information.

[0020] In one possible implementation, the first network element receives first field information from the terminal device, including: the first network element sending a second service message to the terminal device, the second service message not carrying the first field information; and the first network element receiving a protocol message from the terminal device, the protocol message including the first field information.

[0021] In one possible implementation, the method provided in this application embodiment further includes: a first network element associating multiple transmission channels with a pairing protocol stack and a redundant protocol stack, the pairing protocol stack being used to strip the pairing protocol field from the third service message, the third service message carrying the first field information, and the redundant protocol stack being used to forward the third service message stripped of the pairing protocol field.

[0022] In one possible implementation, if the first field information includes a redundant protocol field, the redundant protocol stack is also used to perform redundancy deduplication on the third service message and remove the redundant protocol field.

[0023] In one possible implementation, the method provided in this application embodiment further includes: a first network element sending a pairing request message to a second network element, the pairing request message including the identifier of the terminal device and the identifiers of multiple transmission channels, the second network element being used to determine the network element that has completed the pairing of multiple transmission channels to form a redundant transmission channel.

[0024] In one possible implementation, when the network element that completes the pairing of multiple transmission channels to form a redundant transmission channel is the first network element, the method provided in this application embodiment includes: the first network element receiving a first response message from a second network element, the first response message being used to instruct the first network element to complete the pairing of multiple transmission channels to form a redundant transmission channel.

[0025] In one possible implementation, when the network element that completes the pairing of multiple transmission channels to form a redundant transmission channel is a third network element, the method provided in this application includes: a first network element receiving a second response message from a second network element, the second response message indicating that multiple transmission channels be migrated to the third network element; and the first network element sending indication information to the third network element, the indication information instructing the third network element to complete the pairing of multiple transmission channels to form a redundant transmission channel.

[0026] In one possible implementation, the method provided in this application further includes: a first network element receiving a third service message from a terminal device, the third service message including first field information; the first network element stripping the pairing protocol field from the first field information; and the first network element sending the third service message stripped of the pairing protocol field to a second device, the second device being used to provide data sent from the network device to the terminal device.

[0027] In one possible implementation, where the first field information includes a redundant protocol field, the method provided in this application embodiment further includes: the first network element removing duplicate data from the third service message and stripping the redundant protocol field. The first network element then sends the third service message stripped of the pairing protocol field and the redundant protocol field to the second device.

[0028] In one possible implementation, the method provided in this application further includes: a first network element receiving a fourth service message from a second device; the first network element adding first field information to the fourth service message; and the first network element sending the fourth service message with the added first field information to the terminal device.

[0029] Thirdly, embodiments of this application provide a communication device that can implement the methods in the first aspect or any possible implementation of the first aspect, and therefore can also achieve the beneficial effects of the first aspect or any possible implementation of the first aspect. This communication device can be a terminal device, or an apparatus that supports the terminal device in implementing the methods in the first aspect or any possible implementation of the first aspect, such as a chip applied in the terminal device. This device can implement the above methods through software, hardware, or hardware executing corresponding software.

[0030] Fourthly, embodiments of this application provide a communication device that can implement the methods in the second aspect or any possible implementation of the second aspect, and therefore can also achieve the beneficial effects of the second aspect or any possible implementation of the second aspect. This communication device can be a first network element, or it can be a device that supports the first network element in implementing the methods in the second aspect or any possible implementation of the second aspect, such as a chip applied in the first network element. This device can implement the above methods through software, hardware, or by hardware executing corresponding software.

[0031] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as described in any of the possible implementations of the first aspect.

[0032] Sixthly, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform a communication method as described in any of the possible implementations of the second aspect.

[0033] In a seventh aspect, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a communication method described in the first aspect or various possible implementations of the first aspect.

[0034] Eighthly, embodiments of this application provide a computer program product including instructions that, when executed on a computer, cause the computer to perform a communication method described in the second aspect or various possible implementations of the second aspect.

[0035] Ninthly, embodiments of this application provide a communication device for implementing various methods in various possible designs of any of the first or second aspects described above. The communication device may be the aforementioned terminal device, or a device comprising the aforementioned terminal device, or a component (e.g., a chip) applied in the terminal device. Alternatively, the communication device may be the aforementioned first network element, or a device comprising the aforementioned first network element, or the communication device may be a component (e.g., a chip) applied in the first network element. The communication device includes modules and units corresponding to the aforementioned methods; these modules and units may be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions.

[0036] It should be understood that the communication device described in aspect nine above may further include a bus and a memory, the memory being used to store code and data. Optionally, at least one processor communication interface and the memory are coupled to each other.

[0037] In a tenth aspect, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the methods described in the first aspect or any of the various possible designs of the first aspect. For example, the communication device may be a terminal device or a chip applied in a terminal device.

[0038] Eleventhly, embodiments of this application provide a communication device comprising: at least one processor. The at least one processor is coupled to a memory, and when the communication device is in operation, the processor executes computer execution instructions or programs stored in the memory to cause the communication device to perform any of the methods described in the second aspect or any of the various possible designs of the second aspect. For example, the communication device may be a first network element, or a chip applied to a first network element.

[0039] It should be understood that the memory described in any of the tenth to eleventh aspects can also be replaced by a storage medium, and the embodiments of this application do not limit this.

[0040] In one possible implementation, the memory described in any one of aspects ten to eleven can be a memory inside the communication device. Of course, the memory can also be located outside the communication device, but at least one processor can still execute computer execution instructions or programs stored in the memory.

[0041] In a twelfth aspect, embodiments of this application provide a communication device comprising one or more modules for implementing the method of any one of the first and second aspects described above. The one or more modules may correspond to the various steps in the method of any one of the first and second aspects described above.

[0042] In a thirteenth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods in the first aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wires. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0043] In a fourteenth aspect, embodiments of this application provide a chip system including a processor. The processor reads and executes a computer program stored in a memory to perform the methods of the second aspect and any possible implementation thereof. Optionally, the chip system may be a single chip or a chip module composed of multiple chips. Optionally, the chip system further includes a memory, which is connected to the processor via circuitry or wiring. Further optionally, the chip system includes a communication interface. The communication interface is used to communicate with other modules outside the chip.

[0044] In a fifteenth aspect, embodiments of this application provide a communication system comprising: a terminal device and a first network element. The terminal device is used to execute the method of the first aspect and any possible implementation thereof. The first network element is used to execute the method of the second aspect and any possible implementation thereof.

[0045] Optionally, the communication system may also include a second network element, which is used to select one first network element for the terminal device from a plurality of first network elements.

[0046] Any of the devices, computer storage media, computer program products, chips, or communication systems provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding solutions in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0047] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0048] Figure 2 This is a schematic diagram illustrating a PDU connection and session management provided in an embodiment of this application;

[0049] Figure 3 This is a schematic diagram of a multi-path redundant transmission architecture provided in an embodiment of this application;

[0050] Figure 4 This is a schematic diagram illustrating a static subscription configuration method for implementing paired redundant transmission of multiple PDU connections, as provided in an embodiment of this application.

[0051] Figure 5 This is a schematic diagram of a process for indicating the existence of paired redundant transmission between PDU connections via signaling, provided in an embodiment of this application.

[0052] Figure 6 This is a schematic flowchart of a communication method provided in an embodiment of this application;

[0053] Figure 7 Figure (a) is a schematic diagram of the specific structure of a terminal device provided in an embodiment of this application;

[0054] Figure 7 Figure (b) is a schematic diagram of the specific structure of another terminal device provided in an embodiment of this application;

[0055] Figure 7 Figure (c) is a schematic diagram of the specific structure of another terminal device provided in the embodiment of this application;

[0056] Figure 8 This application provides a frame structure for a service message carrying a pairing protocol field.

[0057] Figure 9 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0058] Figure 10 This is a schematic diagram of the frame structure of a pairing protocol message provided in an embodiment of this application;

[0059] Figure 11 This is a communication diagram between a terminal device and a data exchange device provided in an embodiment of this application;

[0060] Figure 12 This is a schematic diagram of a process for triggering redundancy pairing of multiple transmission channels by uplink data, provided in an embodiment of this application.

[0061] Figure 13 Figure (a) in this application is a schematic diagram of the communication structure before the PDU session association pairing protocol stack provided in an embodiment of this application;

[0062] Figure 13 Figure (b) is a schematic diagram of the communication structure after the PDU session association pairing protocol stack provided in an embodiment of this application;

[0063] Figure 14 This is a schematic diagram of a downlink data-triggered multi-transmission channel redundancy pairing process provided in an embodiment of this application;

[0064] Figure 15 This is a schematic diagram of a specific structure of the communication architecture after PDU pairing is completed, provided in an embodiment of this application;

[0065] Figure 16 This is a schematic diagram of a fully interconnected networking scenario between control plane network elements and user plane network elements provided in an embodiment of this application;

[0066] Figure 17 This is a schematic diagram of a process for triggering dynamic redundancy pairing of multiple transmission channels by uplink data, provided in an embodiment of this application.

[0067] Figure 18 This is a schematic diagram of a process for triggering dynamic redundancy pairing of multiple transmission channels for downlink data, provided in an embodiment of this application.

[0068] Figure 19 This is a schematic diagram of a communication device provided in an embodiment of this application;

[0069] Figure 20 This is a schematic diagram of the hardware structure of a communication device provided in an embodiment of this application;

[0070] Figure 21 This is a schematic diagram of a chip structure provided in an embodiment of this application. Detailed Implementation

[0071] The technical solutions of the embodiments of this application will be 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; "and / or" in this 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.

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

[0073] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0074] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0075] It should be understood that in this application, "at least one (item)" means one or more. "More than one" means two or more. "At least two (items)" means two or three or more. "And / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural.

[0076] The character " / " generally indicates that the preceding and following objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any single or multiple items. For example, "at least one of a, b, or c" can be expressed as: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0077] Both "...when" and "if" indicate that a corresponding action will be taken under certain objective circumstances. They are not time limits, nor do they require a judgment action to be taken when the action is taken, nor do they imply any other limitations.

[0078] The steps involved in the communication method provided in this application embodiment are merely examples. Not all steps are mandatory, nor are all contents of each piece of information or message mandatory. They can be added or removed as needed during use.

[0079] In this application, the same step or a step or message with the same function can be referenced and learned from each other in different embodiments.

[0080] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0081] like Figure 1 As shown, Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. The system includes: a terminal device 110, an access network 120, and one or more user plane network elements 130.

[0082] The terminal device 110 contains multiple subscriber identity module (SIM) cards. Multiple packet data unit (PDU) connections are established between the terminal device 110 and the user plane network element 130. These multiple PDU connections can be established between the terminal device 110 and the same user plane network element 130, or they can be established with different user plane network elements 130.

[0083] For example, terminal device 110 has SIM card 1 and SIM card 2. The terminal device uses SIM card 1 to establish a PDU connection with user plane network element A, and the terminal device uses SIM card 2 to establish a PDU connection with user plane network element A.

[0084] For example, terminal device 110 has SIM card 1 and SIM card 2. The terminal device uses SIM card 1 to establish a PDU connection with user plane network element A, and the terminal device uses SIM card 2 to establish a PDU connection with user plane network element B.

[0085] The access network 120 is used to connect the terminal device 110 to the user plane network element 130.

[0086] For example, terminal device 110 can send uplink data to user plane network element 130 via access network 120 based on PDU connection, and / or receive downlink data from user plane network element 130 via access network 120 based on PDU connection.

[0087] As an example, the uplink data sent by terminal device 110 may originate from other service devices, or the uplink data may be the terminal device 110's own data.

[0088] The user plane network element 130 corresponds to multiple PDU sessions. These multiple PDU sessions send downlink data to the terminal device 110 or receive uplink data from the terminal device 110 based on the multiple PDU connections between the user plane network element 130 and the terminal device 110.

[0089] For example, user plane network element 130 can send downlink data to terminal device 110 via access network 120 based on PDU connection, and / or receive uplink data from terminal device 110 via access network 120 based on PDU connection.

[0090] As an example, user plane network element 130 can receive downlink data from other service devices and then forward the downlink data to terminal device 110.

[0091] Optional, Figure 1 The system shown may further include: service equipment. The service equipment can be used to provide uplink data to terminal equipment 110, or to receive downlink data from terminal equipment 110. Alternatively, the service equipment can be used to provide downlink data to user plane network element 130, or to receive uplink data from user plane network element 130.

[0092] In the embodiments of this application, as shown below... Figure 1 The communication system shown can be applied to the current 5th generation (5G) network architecture as well as future communication network architectures, and this application embodiment does not limit it.

[0093] like Figure 2 The diagram shows a 5G network architecture, which includes: control plane, user equipment (UE), access network (AN) equipment, user plane function (UPF) network elements, and data network (DN).

[0094] For example, Figure 1 The network element or entity corresponding to the terminal device 110 in the middle can be Figure 2 The UE in the 5G network architecture shown. Figure 1 The network element or entity corresponding to access network 120 in the middle can be Figure 2 The AN device in the 5G network architecture shown. Figure 1 The network element or entity corresponding to user plane network element 130 in the middle can be Figure 2 The UPF network element in the 5G network architecture shown.

[0095] The control plane is used to control the UE's access to the network and provide PDU connection services to the UE. For example... Figure 2As shown, the control plane includes: access and mobility management function (AMF) network elements, session management function (SMF) network elements, network repository function (NRF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, unified data repository (UDR) network elements, network slice selection function (NSSF) network elements, network slice-specific authentication and authorization function (NSSAAF) network elements, and authentication server function (AUSF) network elements, etc.

[0096] The AMF network element mainly includes the following functions: connection management, mobility management, registration management, access authentication and authorization, reachability management, security context management, and other access and mobility-related functions.

[0097] Among them, SMF network elements are mainly used for session management, Internet Protocol (IP) address allocation and management of terminal devices, selection of manageable user plane functions, policy control and charging function interface endpoints, and downlink data notification, etc.

[0098] It should be noted that, Figure 1 This is merely an example of an SMF network element. Of course, it may include multiple SMF network elements, such as SMF network element 1 and SMF network element 2, but this application embodiment does not specifically limit this.

[0099] Among them, the PCF network element is used as a unified policy framework to guide network behavior, and provides policy rule information for control plane functional network elements, such as AMF network elements and SMF network elements.

[0100] The UDM network element mainly includes the following functions: unified data management, support for authentication trust letter processing in 3GPP authentication and key negotiation mechanisms, user identity processing, access authorization, registration and mobility management, subscription management, or short message management, etc.

[0101] Among them, the UDR network element is used for data storage, etc.

[0102] Among them, the AUSF network element is responsible for processing authentication requests from user equipment, ensuring that only legitimate users can access network services.

[0103] Among them, the NSSAAF network element is used for authentication and authorization in the network slicing environment.

[0104] Among them, the NSSF network element is responsible for the management and selection of network slices.

[0105] In this embodiment, the AN device can also be called a radio access network (RAN) device, used to provide network access functionality for authorized terminal devices in a specific area, and capable of using transmission tunnels with different quality of service according to the terminal device's level and service requirements. The access network can manage radio resources, provide access services for terminal devices, and thus complete the forwarding of control information and user data between the terminal devices and the core network.

[0106] For example, an AN device can be any type of communication device with wireless transceiver capabilities used to communicate with terminal devices. AN devices include, but are not limited to, evolved NodeBs (eNBs), next-generation NodeBs (gNBs) in NR systems, transmission reception points (TRPs), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G network, or network nodes constituting a gNB, such as baseband units (BBUs) or distributed units (DUs).

[0107] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical (PHY) layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and PHY layer functions. The AAU implements some PHY layer processing functions, radio frequency processing, and active antenna-related functions. Since RRC layer information ultimately becomes PHY layer information, or is derived from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered as being sent by the DU. It is understood that access network equipment can be one or more of the following: CU, DU, and AAU. In addition, the CU can be classified as an access network device in the access network, or it can be classified as an access network device in the core network (CN). This application does not limit this.

[0108] UPF network elements are gateways provided by operators, serving as gateways for communication between operator networks and data networks. They include functions such as packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, legitimate monitoring, uplink packet inspection, and downlink packet storage.

[0109] It should be noted that, Figure 2 The communication system architecture shown is merely an example of a single UPF network element. Of course, a communication system may include multiple UPF network elements, such as UPF network element 1 and UPF network element 2; this embodiment does not specifically limit this.

[0110] DN refers to a carrier network that provides data transmission services to terminal devices, such as the Internet and the Internet Protocol Multimedia Subsystem (IMS). For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can be considered terminal devices. A control server for these sensors is deployed within the DN, providing services to the sensors. The sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly.

[0111] Optional, such as Figure 2 The 5G network architecture shown may also include application function (AF) network elements and network exposure function (NEF) network elements.

[0112] Among them, the AF network element is used to provide application layer information for application data routing. It can interact with the policy framework or directly with the policy framework through the NEF network element to make policy decisions, request control, etc.

[0113] The NEF network element mainly includes the following functions: secure services and capabilities provided by the 3rd generation partnership project (3GPP) network functions; converting or translating information interacting with the AF network element and information interacting with internal network functions, such as the service identifier of the AF network element and internal 5G core network information such as data network name (DNN) and single network slice selection assistance information (S-NSSAI).

[0114] It should be noted that, Figure 2 In this context, AN devices, UPF network elements, AMF network elements, SMF network elements, NEF network elements, PCF network elements, UDM network elements, and AF network elements are merely names and do not constitute a limitation on the network elements themselves. In 5G networks and other future networks, the entities or devices corresponding to these network elements may also have other names, and this application embodiment does not specifically limit this.

[0115] For example, UDM network elements may also be replaced by home subscriber servers (HSS), user subscription databases (USD), or database network elements, etc. This will be explained in a unified manner here and will not be repeated below.

[0116] exist Figure 2 In the 5G network architecture shown, network elements can communicate with each other through the interfaces shown in the diagram. Some interfaces can be implemented using non-service interfaces. For example... Figure 1 As shown, terminal devices and AMF network elements can interact via the N1 interface, and the interaction messages can be referred to as N1 messages. Access network devices and AMF network elements can interact via the N2 interface, which can be used to send non-access stratum (NAS) information. Access network devices and UPF network elements can interact via the N3 interface, which can be used to transmit user plane data. SMF network elements and UPF network elements can interact via the N4 interface, which can be used to transmit information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages. UPF network elements and application servers can interact via the N6 interface, which can be used to transmit user plane data. UPF network elements can interact with each other via the N9 interface.

[0117] In the control plane, SMF network elements and PCF network elements can interact through the N7 interface; AMF network elements and UDM network elements can interact through the N8 interface; SMF network elements and UDM network elements can interact through the N10 interface; SMF network elements and AMF network elements can interact through the N11 interface; AMF network elements and PCF network elements can interact through the N15 interface; UDM network elements and UDR network elements can interact through the N35 interface; and UDR network elements and PCF network elements can interact through the N36 interface.

[0118] Between the control plane and AF and NEF network elements, UDM network elements and AF / NEF network elements can interact via the N52 interface; PCF network elements and AF / NEF network elements can interact via the N5 interface.

[0119] It should be understood that the network architecture applicable to the above embodiments of this application is merely an illustrative example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture that includes the functions of the above-mentioned network elements is applicable to the embodiments of this application.

[0120] It should also be understood that Figure 1 The AMF, SMF, UPF, and PCF network elements shown can be understood as network elements used to implement different functions, such as network slices that can be combined as needed. These network elements can be independent devices or integrated into the same device to implement different functions. They can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). This application does not limit the specific form of the above network elements.

[0121] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in 6G networks, some or all of the above-mentioned network elements may use the terminology from 5G, or may use other names, etc.

[0122] It should also be understood that Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0123] It should be understood that in the embodiments of this application, the UPF network element, AMF network element, SMF network element, NEF network element, UDM network element, and AF network element all belong to core network equipment. Core network equipment and access network equipment can be referred to as network equipment.

[0124] In the embodiments of this application, the terminal device 110 may also be referred to as user equipment, terminal device, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc. The terminal device can be a device that provides voice / data connectivity to the user, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. Currently, examples of terminal devices may include: mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops, PDAs, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a mobile network (PLMN), etc.

[0125] Furthermore, terminal devices can also be terminal devices in Internet of Things (IoT) systems. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network that enables human-machine interconnection and machine-to-machine interconnection. IoT technology can achieve massive connectivity, deep coverage, and low power consumption for terminal devices through technologies such as narrowband (NB).

[0126] In addition, terminal devices may also include smart printers, train detectors, etc. Their main functions include collecting data, receiving control information and downlink data from access network devices, and sending electromagnetic waves to transmit uplink data to access network devices.

[0127] It should be understood that a terminal device can be any device capable of accessing a network. Terminal devices and access network devices can communicate with each other using some form of air interface technology.

[0128] Alternatively, the terminal device can be used to act as an access network device. For example, the terminal device can act as a scheduling entity, providing sidelink signaling between terminal devices in V2X or D2D, etc. For instance, cellular phones and cars communicate with each other using sidelink signaling. Cellular phones and smart home devices communicate with each other without needing to communicate through access network devices.

[0129] In the embodiments of this application, based on such Figure 2 The 5G network architecture shown can provide data exchange services between terminal device 110 and user plane network element 130. This service is called packet data unit (PDU) connection service.

[0130] As an example, a UE initiates a PDU session establishment via the AN to request PDU connection services. The UPF network element can provide PDU connection services by maintaining the PDU session for the UE.

[0131] For example, the data exchange path between UE and DN is as follows: Figure 2 Path 1 in the path is also called the user plane path. For example... Figure 2 As shown, the network elements involved in the user plane path include: UE, (R)AN, UPF network elements, and data network.

[0132] As an example, to achieve data exchange between the UE and the DN network, the UE needs to use the PDU connection service provided by the mobile network to establish a DNN-based PDU session (signaling plane procedure). The establishment of the PDU session includes two basic processes: the UE registering with the mobile network and the UE requesting the network to establish a PDU session. These two processes belong to the signaling plane interaction procedure between the UE and the mobile network.

[0133] For example, the network elements involved in the UE registration process with the mobile network are such as... Figure 2The main network elements shown in path 2 include: UE, (R)AN, AMF, and UDM. The UE sends a registration request message to the AMF via (R)AN, which includes the UE's identifier. The AMF retrieves the UE's subscription data from the UDM based on the UE's identifier. After authentication and authorization, the UDM confirms that the UE is allowed to access the network. The AMF then sends a registration response message to the UE, completing the UE's registration and network access. The AMF also maintains the UE's registration and network access information and performs mobility management for the UE.

[0134] After completing registration and network access, the UE can request to establish a PDU session and obtain PDU connection services from the network. The network elements involved in the UE's request to establish a PDU session are as follows: Figure 2 The main network elements shown in path 2 include: UE, (R)AN, AMF network element, SMF network element and PCF network element.

[0135] For example, the UE sends a PDU session establishment request message to the AMF network element via (R)AN. The AMF network element selects the SMF network element to provide PDU session service for the UE and sends the PDU session establishment request message to the SMF network element. The SMF network element selects the corresponding UPF network element for the UE to establish a PDU session and establishes a PDU connection with the UE, i.e., the user plane transmission path.

[0136] Currently, data transmission between terminal devices and base stations typically uses wireless technology. However, wireless transmission is susceptible to air interface interference, resulting in lower reliability compared to wired transmission. Therefore, to improve the reliability of air interface transmission and meet the high-reliability transmission requirements of certain service scenarios, multi-path redundancy transmission technology is employed. For example... Figure 3 As shown, Figure 3 This is a schematic diagram of a multi-path redundant transmission architecture. In this architecture, the terminal device uses multiple communication modules or chips (e.g., communication module 1 and communication module 2, or communication chip 1 and communication chip 2) to establish multiple PDU connections with the UPF network element. These PDU connections form paired redundant transmission relationships. By converging redundant paths through the terminal device and the UPF network element, redundant transmission to external service equipment and the DN is achieved, improving the reliability of the wireless network transmission link.

[0137] In some related technologies, such as Figure 4 As shown, Figure 4 This is a flowchart illustrating a static subscription configuration method for implementing paired redundant transmission of multiple PDU connections. The method includes:

[0138] Step 401: The user subscribes to the multiple SIM cards on the terminal device for redundant transmission.

[0139] For example, a user signs up for two SIM cards (SIM card 1 and SIM card 2). When signing up for the account, the user signs up for the two SIM cards as a redundant transmission pair SIM card.

[0140] For example, the signing information when a user signs up for a SIM card may include: the identifier of the terminal device, such as the subscriber permanent identifier (SUPI), single network slice selection assistance information (S-NSSAI), data network name (DNN), whether there is redundant transmission, paired users, and the redundancy method, etc.

[0141] For example, a user signs up for SIM card 1 and SIM card 2. For instance, the subscription information 1 for SIM card 1 includes: SUPI1, S-NSSAI, DNN, redundant transmission (yes), and the paired user is SUPI2. The subscription information 2 for SIM card 2 includes: SUPI2, S-NSSAI, DNN, redundant transmission (yes), and the paired user is SUPI1.

[0142] For example, the terminal equipment can be user equipment (UE) or customer premises equipment (CPE).

[0143] After a user signs up and opens an account, the user can insert two paired SIM cards into a terminal device with redundant transmission capabilities. Then, the terminal device can use SIM card 1 and SIM card 2 to establish PDU connections and create a dual PDU session.

[0144] Step 402: The terminal device sends a message to the AMF network element requesting the creation of a PDU session. Correspondingly, the AMF network element receives the message from the terminal device requesting the creation of a PDU session.

[0145] The message requesting the creation of a PDU session includes the identification information of the SIM cards. For example, SUPI1 of SIM card 1 and SUPI2 of SIM card 2.

[0146] In one possible implementation, the terminal device sends a message requesting the creation of a PDU session for SIM card 1 to the AMF network element via RAN1. The terminal device also sends a message requesting the creation of a PDU session for SIM card 2 to the AMF network element via RAN2.

[0147] Step 403: The AMF network element determines the SMF network element based on the identification information of SIM card 1 and SIM card 2.

[0148] For example, the AMF network element determines the SMF network element based on SUPI1 of SIM card 1 and SUPI2 of SIM card 2.

[0149] Step 404: The AMF network element sends a message to the SMF network element requesting the creation of a PDU session. Correspondingly, the SMF network element receives the message from the AMF network element requesting the creation of a PDU session.

[0150] The message requesting the creation of a PDU session includes the identification information of the SIM cards. For example, SUPI1 of SIM card 1 and SUPI2 of SIM card 2.

[0151] Step 405: The SMF network element interacts with the UDM / UDR network element to request and obtain the contract information.

[0152] For example, an SMF network element sends a message to a UDM / UDR network element requesting to obtain subscription information. After receiving the message requesting to obtain subscription information, the UDM / UDR network element sends the subscription information to the SMF network element.

[0153] The contract information includes whether there is redundant transmission, paired users, and the redundancy method.

[0154] Step 406: The SMF network element sends an indication message to the UPF network element. Correspondingly, the UPF network element receives the indication message from the SMF network element.

[0155] The instruction information is used to instruct UPF network elements to create PDU sessions.

[0156] For example, the instruction information includes subscription information 1 for SIM card 1 and subscription information 2 for SIM card 2. The UPF network element creates PDU session 1 and PDU session 2 corresponding to SIM card 1 based on subscription information 1 and subscription information 2.

[0157] Step 407: The SMF network element configures a redundancy protocol for the UPF network element based on the subscription information.

[0158] For example, the SMF network element instructs the UPF network element to perform redundant transmission.

[0159] Step 408: The SMF network element modifies the PDU session configuration of SIM card 1 and SIM card 2 according to the redundancy protocol.

[0160] For example, PDU session 1 of SIM card 1 and PDU session 2 of SIM card 2 can be paired for redundant transmission.

[0161] Step 409: The SMF network element sends a response message to the terminal device. Correspondingly, the terminal device receives the response message from the SMF network element.

[0162] The response message is used to activate redundant transmission and carries the redundancy mode, so that terminal equipment and UPF network elements can directly use multiple communication paths to achieve highly reliable transmission according to the redundancy protocol.

[0163] according to Figure 4 As shown in the related technologies, the static configuration of SIM card pairings means that the redundant transmission relationship of the SIM cards issued to users is relatively fixed. Users must remember the redundant transmission relationship between their two SIM cards and generally cannot use them interchangeably with other SIM cards. In some scenarios, such as when users typically open multiple accounts, they may simultaneously possess both non-redundant and redundant transmission SIM cards, which can easily lead to the problem of using the wrong SIM card in actual use.

[0164] In other related technologies, such as Figure 5 As shown, Figure 5 This is a schematic diagram illustrating a process for indicating paired redundant transmission between PDU connections via signaling. The terminal device includes a redundancy module and multiple communication modules / chips (e.g., communication module / chip 1 and communication module / chip 2), with each communication module corresponding to a SIM card (e.g., communication module 1 corresponds to SIM card 1, and communication module 2 corresponds to SIM card 2). Specific methods include:

[0165] Step 501: Configure redundant pairings for terminal devices.

[0166] The terminal device has redundant transmission capabilities. Two SIM cards are inserted into the terminal device, such as SIM card 1 and SIM card 2. SIM card 1 and SIM card 2 are the two 5G SIM cards that the user signed up for.

[0167] For example, terminal devices can enable redundant transmission, configure the redundancy type and redundancy pair identifier.

[0168] In one possible implementation, a redundant module in the terminal device sends configuration information to communication module 1 and communication module 2.

[0169] Step 502: The terminal device initiates the network access signaling process and requests the creation of a PDU connection.

[0170] The process of a terminal device initiating network access signaling involves AMF network elements, SMF network elements, UPF network elements, and the data network authentication, authorization, and accounting (DN-AAA) system. Specific implementation methods include:

[0171] Step 5021: The terminal device sends a message to the AMF network element requesting the creation of a PDU session. Correspondingly, the AMF network element receives the message from the terminal device requesting the creation of a PDU session.

[0172] For example, communication module 1 in the terminal device sends a message to the AMF network element requesting SIM card 1 to create a PDU session. This message carries the identification information, redundancy indication, redundancy type, and redundancy pairing identifier of SIM card 1. Communication module 2 sends a message to the AMF network element requesting SIM card 2 to create a PDU session. This message carries the identification information, redundancy indication, redundancy type, and redundancy pairing identifier of SIM card 2.

[0173] Step 5022: The AMF network element determines the SMF network element based on the message requesting the creation of a PDU session.

[0174] For example, the AMF network element determines the SMF network element based on the identification information of SIM card 1 and SIM card 2.

[0175] Step 5023: The AMF network element sends a message to the SMF network element requesting the creation of a PDU session. Correspondingly, the SMF network element receives the message from the AMF network element requesting the creation of a PDU session.

[0176] The message requesting the creation of a PDU session includes the SIM card's identification information, redundancy indication, redundancy type, and redundancy pair identifier.

[0177] Optionally, the method further includes: step 5024, the SMF network element sends an authentication request message to DN-AAA. Correspondingly, DN-AAA receives the authentication request from the SMF network element.

[0178] The authentication request includes: SIM card identification information, redundancy indication, redundancy type, and redundancy pair identifier.

[0179] Step 5025: DN-AAA authenticates the terminal device based on the authentication request message.

[0180] Step 5026: DN-AAA sends an authentication response message to the SMF network element. Correspondingly, the SMF network element receives the authentication response message from DN-AAA.

[0181] The authentication response message includes: redundancy indication, redundancy type, and redundancy pair identifier.

[0182] Step 5027: The SMF network element determines the UPF network element based on the message requesting the creation of a PDU session.

[0183] If the UPF network element does not have a redundancy processing protocol stack for redundancy pairing, the method includes: step 5028, the SMF network element sends a first indication message to the UPF network element. The corresponding UPF network element receives the first indication message from the SMF network element.

[0184] The first instruction information is used to instruct the UPF network element to establish a redundant processing protocol stack.

[0185] For example, the first indication information includes the redundancy type and the redundancy pair identifier.

[0186] Step 5029: The SMF network element sends the second indication information to the UPF network element. Correspondingly, the UPF network element receives the second indication information from the SMF network element.

[0187] The second instruction information is used to instruct the UPF network element to create a PDU session.

[0188] For example, the UPF network element creates PDU session 1 corresponding to SIM card 1 and PDU session 2 corresponding to SIM card 2.

[0189] Step 503: The SMF network element sends a PDU session response message to the terminal device. Correspondingly, the terminal device receives the PDU session response message from the SMF network element.

[0190] For example, the SMF network element sends PDU session response messages to communication modules 1 and 2 of the terminal device.

[0191] according to Figure 5 As shown in the related technologies, during the PDU connection establishment process, signaling is used to indicate the pairing relationship between multiple PDU connections, thereby achieving dynamic pairing and redundant transmission among multiple subscribed users. This method relies heavily on the chips in the terminal equipment. For example, the communication module in the terminal equipment needs to send the signaling, requiring modification and upgrading of the terminal equipment's chips, making the implementation relatively complex.

[0192] Based on this, this application provides a communication method in which a terminal device first establishes multiple PDU connections with a UPF network element. Then, the terminal device adds field information to its uplink service messages during multipath transmission and sends these messages to the UPF network element, triggering the PDU session association pairing protocol stack in the UPF network element to facilitate the pairing of UPF network elements into redundant transmission paths. Alternatively, the UPF network element sends downlink service messages to the terminal device. After receiving a downlink service message without field information, the terminal device proactively sends an uplink protocol message containing the field information to the UPF network element, triggering the PDU session association pairing protocol stack in the UPF network element to facilitate the pairing of UPF network elements into redundant transmission channels. This method eliminates the need for static configuration of paired PDU connections and modification of the terminal device's chip, facilitating the formation of redundant transmission channels between the terminal device and the UPF network element.

[0193] In this application embodiment, the specific structure of the execution subject of a communication method is not particularly limited, as long as communication can be performed according to the communication method of this application by running a program that records the code of a communication method of this application embodiment. For example, the execution subject of a communication method provided in this application embodiment can be a functional module in a terminal device that can call and execute a program, or a communication device applied in a terminal device, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be disposed inside the terminal device or can be independent of the terminal device, and this application embodiment does not impose any restrictions. For example, the execution subject of a communication method provided in this application embodiment can be a functional module in a first network element that can call and execute a program, or a communication device applied in a first network element, such as a chip, chip system, integrated circuit, etc. These chips, chip systems, and integrated circuits can be disposed inside the first network element or can be independent of the first network element, and this application embodiment does not impose any restrictions.

[0194] The following embodiments describe a communication method using a terminal device and a first network element as examples. The first network element is, for instance, a terminal device and a first network element. Figure 1 The user plane network element 130 in the illustrated communication system is, for example, a UPF network element. Where there is no conflict, the solutions in the following embodiments can be combined.

[0195] In this embodiment of the application, the communication method includes three steps:

[0196] The first step is for network configuration personnel to configure redundant communication configuration information for the first network element through the control plane.

[0197] The configuration information includes a whitelist of devices that are allowed to perform redundant transmission and reception, the method used for redundant transmission, and the parameters of the redundant transmission protocol.

[0198] For example, a whitelist of devices that are allowed to send and receive redundantly includes the device's identifier, such as its media access control address (MAC).

[0199] For example, redundant transmission can be achieved through methods such as dual-transmission selective reception or load balancing.

[0200] The redundant transmission protocol parameters correspond to the method used for redundant transmission. For example, when the redundant transmission method is dual-transmission selective reception, the parameters include the protocol used for dual-transmission selective reception, such as high-availability seamless redundancy (HSR) or frame replication and elimination for reliability (FRER). When the redundant transmission method is load balancing, the parameters include the load balancing algorithm used.

[0201] The second step is for the terminal equipment to establish multiple transmission channels with the first network element and pair them to form redundant transmission channels.

[0202] The transmission channel is used for data transmission between the terminal device and the first network element. In this embodiment, the transmission channel is a PDU connection.

[0203] In one possible implementation, the terminal device requests to establish a PDU connection with the first network element, and a PDU connection is formed between the communication module in the terminal device and the PDU session corresponding to the UPF.

[0204] For example, a terminal device includes a first communication module and a second communication module. The terminal device requests to establish PDU connection 1 and PDU connection 2 with a first network element. Specifically, the first communication module establishes PDU connection 1 with PDU session 1, and the second communication module establishes PDU connection 2 with PDU session 2.

[0205] It is worth noting that the transmission channel between the terminal device and the first network element can also be called a PDU connection or a PDU path, which is not limited in the embodiments of this application.

[0206] In one possible embodiment of this application, the redundant transmission channel is composed of multiple transmission channel pairs triggered by uplink service messages forwarded by the terminal device.

[0207] like Figure 6 As shown, Figure 6 An embodiment of this application illustrates a communication method, which includes:

[0208] Step 601: The terminal device establishes multiple transmission channels with the first network element.

[0209] The transmission channel between the terminal device and the first network element is a PDU connection, and the PDU connection corresponds to the PDU session in the first network element or the terminal device.

[0210] For example, a transmission channel 1, i.e. PDU connection 1, is established between the terminal device and the PDU session 1 corresponding to the first network element, and a transmission channel 2, i.e. PDU connection 2, is established between the terminal device and the PDU session 2 corresponding to the first network element.

[0211] The terminal device includes a redundant protocol stack, a pairing protocol stack, and at least one communication module. The redundant protocol stack and the pairing protocol stack are used to add the first field information to the uplink service message. The communication module is used to send the uplink service message.

[0212] One possible implementation method, the specific structure of the terminal device is referenced. Figure 7 Figure (a) shows a redundant protocol stack, a paired protocol stack, and two communication modules. Each communication module corresponds to a PDU session of a terminal device, or each communication module is associated with a PDU session identifier.

[0213] For example, if communication module 1 is associated with PDU session 1, then communication module 1 can use PDU session 1 to send uplink service messages to the first network element. If communication module 2 is associated with PDU session 2, then communication module 2 can use PDU session 2 to send uplink service messages to the first network element.

[0214] Another possible implementation method, the specific structure of the terminal device is referenced. Figure 7 Figure (b) shows a redundant protocol stack, a paired protocol stack, and a communication module. This communication module is associated with the identifiers of two PDU sessions.

[0215] For example, a communication module is associated with PDU session 1 and PDU session 2. In the case of redundant transmission with dual transmit / receive capability, the communication module sends uplink service messages to the first network element through both PDU session 1 and PDU session 2. In the case of redundant transmission with load balancing capability, the communication module sends uplink service messages to the first network element through either PDU session 1 or PDU session 2.

[0216] Another possible implementation, the specific structure of the terminal device is referenced. Figure 7 Figure (c) shows a redundant transceiver device and two terminals. The redundant transceiver device includes a redundant protocol stack and a pairwise protocol stack. Each terminal is associated with an identifier of a PDU session, and the terminal can use the PDU session to send uplink service messages to the first network element.

[0217] For example, terminal 1 is associated with the identifier of PDU session 1, and terminal 1 can use PDU session 1 to send uplink service messages to the first network element. Terminal 2 is associated with the identifier of PDU session 2, and terminal 2 can use PDU session 2 to send uplink service messages to the first network element.

[0218] It is understood that there can be various forms of terminal devices, and no limitation is made in the embodiments of this application.

[0219] Step 602: The terminal device sends the first field information to the first network element. Correspondingly, the first network element receives the first field information from the terminal device.

[0220] In one possible implementation, the terminal device sends an uplink service message to the first network element, and the uplink service message carries the first field information.

[0221] In one possible embodiment of this application, the redundant transmission method of multiple transmission channels includes dual-transmission selective reception and load balancing. When the redundant transmission method of multiple transmission channels is dual-transmission selective reception, each transmission channel is used to transmit the same first field information. When the redundant transmission method of multiple transmission channels is load balancing, one of the multiple transmission channels is used to transmit the first field information.

[0222] As an example, in the case of redundant transmission with dual-transmit selective reception, each transmission channel is used to transmit the same uplink service message, and each uplink service message carries a first field information. The first field information includes a pairing protocol field and a redundancy protocol field.

[0223] The pairing protocol field includes the identifier of the terminal device, which indicates that multiple transmission channels in the terminal device are paired to form a redundant transmission channel. The redundancy protocol field is used to identify that the information in the first field is sent redundantly.

[0224] For example, the terminal device copies uplink service message 1 to obtain uplink service message 2. Uplink service message 1 is sent to the UPF network element via the first communication module, and uplink service message 2 is sent to the UPF network element via the second communication module. Both uplink service message 1 and uplink service message 2 carry a pairing protocol field (pairing tag) and a redundancy protocol field (redundancy tag).

[0225] refer to Figure 8 , Figure 8This application provides a frame structure for a service message carrying a pairing protocol field. The pairing protocol field includes: the Ethernet type of the pairing protocol field and the identifier of the pairing device. The Ethernet type of the pairing protocol field indicates that the service message contains the pairing protocol field. The identifier of the pairing device indicates that the PDU connections under the device corresponding to the identifier need to be paired to form a redundant transmission channel.

[0226] As another example, in a load-balanced redundant transmission mode, one of the multiple transmission channels is used to send uplink service messages, which carry a first field of information. This first field includes a pairing protocol field.

[0227] For example, the terminal device sends uplink service message 1 to the UPF network element through the first communication module according to the load balancing algorithm. Uplink service message 1 includes a pairing protocol field (pairing tag). Refer to the specific frame structure. Figure 8 .

[0228] In one possible embodiment of this application, the first field information is added to the uplink service message by the pairing protocol stack and the redundancy protocol stack in the terminal device.

[0229] As an example, when the redundant transmission mode is a dual-transmit selective-receive mode, the redundant protocol stack in the terminal device adds the redundant protocol field to the uplink service message, and the pairing protocol stack adds the pairing protocol field to the uplink service message.

[0230] As another example, in the case of redundant transmission using load balancing, the pairing protocol stack in the terminal device adds the pairing protocol field to the upstream service message.

[0231] Step 603: The first network element completes the pairing of multiple transmission channels based on the information in the first field.

[0232] In one possible implementation, the first network element obtains the identifier of the terminal device based on the first field information carried in the uplink service message, and uses the identifier of the terminal device to find the pair protocol stack and the redundant protocol stack, and associates multiple PDU sessions with the pair protocol stack and the redundant protocol stack.

[0233] For example, the first network element is a UPF network element, which includes PDU session 1 and PDU session 2. The UPF network element receives uplink service packets from terminal devices through the PDU connection corresponding to PDU session 1 and the PDU connection corresponding to PDU session 2. The uplink service packets carry a redundancy protocol field (redundancy tag) and a pairing protocol field (pairing tag). The UPF network element looks up the corresponding pairing protocol stack and redundancy protocol stack based on the terminal device identifier in the pairing tag. The UPF network element associates PDU session 1 and PDU session 2 with the pairing protocol stack and the redundancy protocol stack, respectively.

[0234] In one possible embodiment, before creating the pairing protocol stack, the first network element also needs to check whether redundant communication by the terminal device is allowed.

[0235] As an example, the first network element obtains the identifier of the terminal device. The terminal device is a device permitted for pairing. Based on the whitelist information of devices permitted for redundant communication in the redundant communication information, the first network element determines that the identifier of the terminal device is in the whitelist, and therefore determines that the terminal device is permitted to perform redundant communication. Subsequently, the first network element creates a pairing protocol stack for the identifier of the terminal device.

[0236] Optionally, the first network element can also create a redundant protocol stack for the identifier of the terminal device.

[0237] As another example, the first network element obtains the identifier of the terminal device. The terminal device is a device permitted to perform paired communication. Based on the whitelist information of devices allowed for redundant communication in the redundant communication information, the first network element determines that the identifier of the terminal device is not in the whitelist, and therefore determines that redundant communication is not permitted for the terminal device. After determining that redundant communication is not permitted for the terminal device, the first network element discards the uplink service message.

[0238] It is worth noting that if the first network element has already created the corresponding pairing protocol stack and redundant protocol stack for the identifier of the terminal device, then no verification is performed on whether the terminal device is allowed to perform redundant communication.

[0239] In another possible embodiment of this application, the redundant transmission channel is composed of multiple transmission channels paired up by the downlink service message forwarded by the first network element.

[0240] like Figure 9 As shown, Figure 9 This application illustrates another communication method provided by an embodiment of the present application, the method comprising:

[0241] Step 901: The terminal device establishes multiple transmission channels with the first network element.

[0242] Step 902: The first network element sends a second service message to the terminal device. Correspondingly, the terminal device receives the second service message from the first network element. The second service message does not carry the first field information.

[0243] The second service message is a downlink service message sent by the second service device to the first network element. Since the first network element has not triggered multi-transmission channel pairing, the downlink service message does not carry the first field information.

[0244] Step 903: The terminal device sends a protocol message to the first network element according to the second service message.

[0245] The protocol message includes the first field information.

[0246] In one possible implementation, the protocol messages are pair protocol messages. (See reference) Figure 10 , Figure 10 This is a schematic diagram of the frame structure of a pairing protocol message. The destination MAC address is a special MAC address used by the UPF network element to detect that the message is a pairing protocol message, and the source MAC address is the MAC address of the terminal device.

[0247] Step 904: The first network element completes the pairing of multiple transmission channels based on the information in the first field.

[0248] For the specific implementation method, please refer to step 603 above, which will not be repeated here.

[0249] The third step involves data interaction between the terminal device and the first network element based on the redundant transmission channel.

[0250] Case 1) The terminal device sends data to the first network element.

[0251] The method provided in this application includes:

[0252] Step 1: The terminal device sends a third service message to the first network element. Correspondingly, the first network element receives the third service message from the terminal device.

[0253] The third service message carries the information in the first field.

[0254] In one possible implementation, the terminal device receives a third service message from the first service device and adds pairing protocol fields and redundancy protocol fields to the third service message using a pairing protocol stack and a redundancy protocol stack. The first network element then sends the third service message to itself via a PDU session.

[0255] It is worth noting that the redundancy protocol field is optional. When the terminal device determines that the redundancy transmission mode is the dual-transmission selective-reception mode, the redundancy protocol stack adds the redundancy protocol field.

[0256] For example, taking the first network element as the UPF network element and the third service message as data message 1. After the redundant protocol stack in the terminal device receives data message 1 from the first service device, if the redundant transmission mode is dual-transmit selective reception, the redundant protocol stack copies data message 1 to obtain data message 2, adds a redundant tag to data message 1 and data message 2, and forwards data message 1 and data message 2 to the pairing protocol stack; if the redundant transmission mode is load balancing, the redundant protocol stack directly forwards data message 1 to the pairing protocol stack. The pairing protocol stack then adds a pairing tag to data message 1 and forwards it to the UPF network element through the first communication module and / or the second communication module.

[0257] When the redundant transmission method is load balancing, the method provided in this application embodiment further includes:

[0258] Step 2a: The pairing protocol field in the first field information of the first network element is stripped.

[0259] In one possible implementation, the first network element receives the third service message through a PDU session, and strips the pairing protocol field from the third service message through the pairing protocol stack in the first network element, and forwards it to the redundant protocol stack.

[0260] For example, taking the first network element as a UPF network element and the third service message as data message 1, PDU session 1 in the UPF network element receives data message 1 from the terminal device, removes the pair tag from data message 1 through the pair protocol stack, and forwards it to the redundant protocol stack.

[0261] Step 3a: The first network element sends a third service message stripped of the pairing protocol field to the second service device.

[0262] In one possible implementation, the redundant protocol stack in the first network element sends a third service message with the pairing protocol field stripped off to the second service device.

[0263] When the redundant transmission mode is dual-transmission selective reception, the method provided in this application embodiment further includes:

[0264] Step 2b: The first network element removes duplicate data from the third service message and strips redundant protocol fields;

[0265] In one possible implementation, the first network element receives the third service message through a PDU session, strips the pairing protocol field from the third service message using the pairing protocol stack in the first network element, and forwards it to the redundant protocol stack. The redundant protocol stack then removes duplicate data from the third service message and strips the redundant protocol field.

[0266] For example, taking the first network element as the UPF network element and the third service message as data packet 1. PDU session 1 in the first network element receives data packet 1 from the terminal device, and PDU session 2 receives data packet 2 from the terminal device. Data packet 2 is obtained by copying data packet 1. The pairwise protocol stack removes the pairwise tags from data packet 1 and data packet 2 and forwards them to the redundancy protocol stack. The redundancy protocol stack performs deduplication on data packet 1 and data packet 2 and removes redundant tags from both data packet 1 and data packet 2.

[0267] Step 3b: The first network element sends a third service message to the second service device, after the pairing protocol field and the redundancy protocol field have been stripped.

[0268] In one possible implementation, the redundant protocol stack in the first network element sends a third service message with the stripped pairing protocol field and redundant protocol field to the second service device.

[0269] Case 2) The first network element sends data to the terminal device.

[0270] The method provided in this application includes:

[0271] Step 1: The first network element sends a third service message to the terminal device. Correspondingly, the terminal device receives the third service message from the first network element.

[0272] The third service message carries the information in the first field.

[0273] In one possible implementation, the first network element receives a third service message from the second service device and adds pairing protocol fields and redundancy protocol fields to the third service message using a pairing protocol stack and a redundancy protocol stack. The first network element then sends the third service message to the terminal device via a PDU session.

[0274] It is worth noting that the redundancy protocol field is optional. When the first network element determines that the redundant transmission mode is the dual-transmit selective-receive mode, the redundant protocol stack adds the redundant protocol field.

[0275] For example, taking the first network element as the UPF network element and the third service message as data message 1. The UPF network element corresponds to PDU session 1 and PDU session 2, which are associated with a pairwise protocol stack and a redundant protocol stack. After the redundant protocol stack in the UPF network element receives data message 1 from the second service device, if the redundant transmission mode is dual-transmit selective reception, the redundant protocol stack adds a redundant tag to data message 1 and forwards data message 1 to the pairwise protocol stack; if the redundant transmission mode is load balancing, the redundant protocol stack directly forwards data message 1 to the pairwise protocol stack. The pairwise protocol stack then adds a pairwise tag to data message 1 and forwards it to the terminal device through PDU session 1 and / or PDU session 2.

[0276] When the redundant transmission method is load balancing, the method provided in this application embodiment further includes:

[0277] Step 2a: The terminal device strips the pairing protocol field from the first field information.

[0278] In one possible implementation, the terminal device receives the third service message through the communication module, and strips the pairing protocol field from the third service message through the pairing protocol stack in the terminal device, and forwards it to the redundant protocol stack.

[0279] For example, taking the first network element as the UPF network element and the third service message as data message 1, the first communication module in the terminal device receives data message 1 from the UPF network element, removes the pair tag from data message 1 through the pairing protocol stack, and forwards it to the redundant protocol stack.

[0280] Step 3a: The terminal device sends a third service message stripped of the pairing protocol field to the first service device.

[0281] In one possible implementation, the redundant protocol stack in the terminal device sends a third service message with the stripped pairing protocol field to the first service device.

[0282] When the redundant transmission mode is dual-transmission selective reception, the method provided in this application embodiment further includes:

[0283] Step 2b: The terminal device removes duplicate data from the third service message and strips redundant protocol fields;

[0284] In one possible implementation, the terminal device receives the third service message through the communication module, strips the pairing protocol field from the third service message using the pairing protocol stack in the terminal device, and forwards it to the redundant protocol stack. The redundant protocol stack then removes duplicate data from the third service message and strips the redundant protocol fields.

[0285] For example, taking the first network element as the UPF network element and the third service message as data message 1. The first communication module in the terminal device receives data message 1 from the UPF network element, and the second communication module receives data message 2 from the UPF network element. Data message 2 is obtained by copying data message 1. The pairwise protocol stack removes the pairwise tags from data message 1 and data message 2 and forwards them to the redundancy protocol stack. The redundancy protocol stack performs deduplication on data message 1 and data message 2 and removes redundant tags from them.

[0286] Step 3b: Send a third service message to the first device after removing the pairing protocol field and the redundancy protocol field.

[0287] In one possible implementation, the redundant protocol stack in the terminal device sends a third service message with the stripped pairing protocol field and redundant protocol field to the first service device.

[0288] In this embodiment of the application, the first network element can also be a data switching device. For example... Figure 11 As shown, this data switching device uses multiple transceiver ports to communicate with terminal devices. The transceiver ports (e.g., transceiver port 1 and transceiver port 2) function the same as the PDU session corresponding to the first network element. During data communication, the data switching device receives service messages with pairing protocol fields sent by the terminal devices. Based on the pairing protocol field indication, it pairs unpaired communication paths and creates corresponding pairing protocol stacks and redundancy protocol stacks. After pairing is completed, the pairing protocol stack and redundancy protocol stack complete the transmission of redundant service messages and the deduplication reception of redundant service messages. The specific implementation method is the same as that of the first network element described above, and will not be repeated here.

[0289] The specific implementation of the communication method provided in the embodiments of this application is described below. In the following embodiments, taking the terminal device as a redundant communication terminal device and the first network element as a UPF network element as an example, the redundant communication terminal device includes a redundant transceiver module, a first communication module, and a second communication module.

[0290] like Figure 12 As shown, Figure 12 This is a schematic diagram illustrating a process for triggering redundancy pairing of multiple PDU paths based on uplink data, as provided in an embodiment of this application.

[0291] exist Figure 12 In the illustrated embodiment, the UPF network element is a single entity, and no control plane participates in controlling the UPF network element. The specific method includes:

[0292] Step 1201: The UPF network element acquires redundant communication information.

[0293] For example, network configuration personnel can configure redundant communication information for UPF network elements through the configuration interface provided by the 5G network.

[0294] The redundant communication information is used to indicate to the terminal device that it is permitted to form a redundant transmission channel. The redundant communication information includes, but is not limited to: a whitelist of devices permitted to perform redundant communication, the redundant transmission method, and the parameter information corresponding to the redundant transmission method.

[0295] For example, the whitelist information of devices that are allowed to conduct redundant communication may include the identifier of the terminal device, such as the media access control address (MAC).

[0296] For example, redundant transmission methods can include dual-transmission selective reception or load balancing. When the redundant transmission method is dual-transmission selective reception, the corresponding parameter information includes the protocol used for dual-transmission selective reception, such as high-availability seamless redundancy (HSR) or frame replication and elimination for reliability (FRER). When the redundant transmission method is load balancing, the corresponding parameter information includes the load balancing algorithm used for load balancing.

[0297] Step 1202: The terminal device establishes a PDU connection with the UPF network element.

[0298] In one possible implementation, the first and second communication modules in the terminal device are respectively inserted with the subscribed SIM cards. After the terminal device is powered on, it uses the first and second communication modules to establish PDU connections with the UPF network element, thus establishing multiple PDU connections. The process of how the terminal device uses different communication modules to establish multiple PDU connections with the UPF network element can be found in the preceding description and will not be repeated here.

[0299] Step 1203: The first service device sends an uplink service message to the terminal device. Correspondingly, the terminal device receives the uplink service message from the first service device.

[0300] For example, the first business device could be a smart thermostat in a smart home system, which is responsible for monitoring the indoor temperature. When the smart thermostat detects that the indoor temperature exceeds the preset range, it will generate a data packet and send it to the terminal device (such as a smartphone).

[0301] Step 1204: The terminal device adds the first field information to the upstream business message.

[0302] For example, the redundant transceiver module in the terminal device adds the first field information to the uplink service message to obtain the first uplink service message.

[0303] The first field of information includes the pairing protocol field.

[0304] For example, such as Figure 8 As shown, Figure 8 This application provides a frame structure for a service message carrying a pairing protocol field. The pairing protocol field includes: the Ethernet type of the pairing protocol field and the identifier of the pairing device. The Ethernet type of the pairing protocol field indicates that the service message contains the pairing protocol field. The identifier of the pairing device indicates that the PDU connections under the device corresponding to the identifier need to be paired to form a redundant transmission channel.

[0305] Optionally, the first field information may also include a redundancy protocol field.

[0306] For example, see reference. Figure 8 The frame structure shown can also include a redundant protocol field in the upstream service message.

[0307] As an example, when the redundant transmission mode is a dual-transmit selective-receive mode, the first field information includes a pairing protocol field and a redundancy protocol field.

[0308] It is understandable that when the redundant transmission method is load balancing, the first field of information does not need to include the redundant protocol field.

[0309] Step 1205: The terminal device sends a first uplink service message (i.e., an uplink service message carrying the first field information) to the UPF network element. Correspondingly, the UPF network element receives the first uplink service message from the terminal device.

[0310] For example, the redundant transceiver module in the terminal device sends the uplink service message carrying the first field information to the first communication module and the second communication module, and then the first communication module and / or the second communication module sends the first uplink service message carrying the field information to the UPF network element.

[0311] In one possible implementation, when the redundancy mode is dual-transmit selective-receive, the redundant transceiver module copies the uplink service message carrying the first field information and sends a set of uplink service messages carrying the first field information to both the first and second communication modules. The first and second communication modules then send the uplink service messages carrying the first field information to the UPF network element.

[0312] In another possible implementation, when the redundancy method is load balancing, the redundant transceiver module determines the communication module (e.g., the first communication module or the second communication module) to send the uplink service message according to the load balancing algorithm, and then sends the uplink service message carrying the first field information to the UPF network element by the determined communication module (e.g., the first communication module or the second communication module).

[0313] In this embodiment, the UPF network element receives uplink service packets carrying field information from the terminal device through a PDU session. For example, the UPF network element corresponds to PDU session 1 and PDU session 2. When the redundancy mode is dual-transmit selective reception, the UPF network element receives uplink service packets carrying field information from the terminal device through PDU session 1 and PDU session 2. When the redundancy mode is load balancing, the UPF network element receives uplink service packets carrying field information from the terminal device through either PDU session 1 or PDU session 2. Specifically, when the terminal device sends an uplink service packet to the UPF network element through the first communication module, the UPF network element receives the uplink service packet through PDU session 1; when the terminal device sends an uplink service packet to the UPF network element through the second communication module, the UPF network element receives the uplink service packet through PDU session 2.

[0314] Step 1206: The UPF network element determines the pairing protocol stack corresponding to the identifier of the terminal device.

[0315] It is worth noting that if the UPF network element determines that PDU session 1 and PDU session 2 are not associated with the pairing protocol stack, then step 1206 can be: the UPF network element creates a pairing protocol stack corresponding to the identifier of the terminal device.

[0316] Before creating the pairing protocol stack, the UPF network element also needs to verify whether redundant communication by the terminal device is permitted. Specific implementation methods include:

[0317] Step 1: The UPF network element obtains the identifier of the terminal device. The terminal device is a device that is allowed to pair.

[0318] Step 2a: The UPF network element determines whether the terminal device is allowed to perform redundant communication.

[0319] In one possible implementation, the UPF network element determines that the identifier of the terminal device is in the whitelist of devices that are allowed to perform redundant communication based on the redundant communication information. If the identifier of the terminal device is in the whitelist, then the terminal device is allowed to perform redundant communication.

[0320] Step 3a: The UPF network element creates a pairing protocol stack for the identifier of the terminal device.

[0321] Optionally, the UPF network element can also create redundant protocol stacks for the identification of terminal devices.

[0322] Step 2b: The UPF network element determines that redundant communication by the terminal device is not allowed.

[0323] In one possible implementation, the UPF network element determines that the identifier of the terminal device is not in the whitelist of devices that are allowed to perform redundant communication based on the redundant communication information. If the identifier of the terminal device is not in the whitelist, then the terminal device is not allowed to perform redundant communication.

[0324] Step 3b: The UPF network element discards the uplink service message.

[0325] It is worth noting that if the UPF network element has already created the corresponding pairing protocol stack and redundant protocol stack for the identifier of the terminal device, then no verification is performed on whether the terminal device is allowed to perform redundant communication.

[0326] Step 1207: The UPF network element associates PDU session 1 and PDU session 2 with the pairing protocol stack.

[0327] In one possible implementation, the UPF network element obtains the identifier of the terminal device based on the first field information in the first uplink service message, finds the pairing protocol stack of the terminal device through the identifier, and associates the PDU session with the pairing protocol stack.

[0328] For example, such as Figure 13 As shown, Figure 13 Figure (a) shows the communication structure before the PDU session is associated with the pairing protocol stack, where the first and second communication modules in the terminal device are associated with the pairing protocol stack. Optionally, the first and second communication modules in the terminal device can also be associated with a redundant protocol stack. The UPF network element corresponds only to PDU session 1 and PDU session 2. Figure 13 Figure (b) shows the communication structure after the PDU session is associated with the protocol stack, where... Figure 13 The difference in the communication structure shown in Figure (a) is that PDU session 1 and PDU session 2 corresponding to the UPF network element are associated with a paired protocol stack. Optionally, the PDU session can also be associated with a redundant protocol stack.

[0329] Step 1208: The UPF network element processes the first uplink service message carrying the first field information to obtain the second uplink service message.

[0330] The message processing includes stripping the pairing protocol field and the redundant protocol field.

[0331] In one possible implementation, the pairwise protocol stack strips the pairwise protocol field from the uplink service message carrying the first field information and sends it to the redundancy protocol stack. When the redundancy transmission mode is dual-transmission selective reception, the redundancy protocol stack performs redundancy deduplication on the duplicate parts of the message according to the processing rules defined by the dual-transmission selective reception protocol, and strips the redundant protocol field. The redundancy protocol stack then forwards the processed message. When the redundancy transmission mode is load balancing, since the field information does not carry the redundant protocol field, the redundancy protocol stack directly forwards the first uplink service message stripped of the pairwise protocol field.

[0332] For example, when the redundant transmission mode is a dual-transmit selective-receive mode, after the UPF network element receives service packet 1 through PDU session 1 and service packet 2 through PDU session 2, the pairwise protocol stacks associated with PDU session 1 and PDU session 2 strip the pairwise protocol fields from service packets 1 and 2. Then, the redundant protocol stacks associated with PDU session 1 and PDU session 2 remove duplicate service packets, for example, removing service packet 1 or service packet 2. The redundant protocol stack then strips the redundant protocol fields from service packet 1 or service packet 2 and sends the service packet 1 or service packet 2 stripped of redundant protocol fields to the second service device.

[0333] For example, when the redundant transmission mode is load balancing, after PDU session 1 or PDU session 2 in the UPF network element receives service message 1, the pairwise protocol stack associated with PDU session 1 and PDU session 2 removes the pairwise protocol field from service message 1. Then, the redundant protocol stack associated with PDU session 1 and PDU session 2 sends service message 1, stripped of the pairwise protocol field, to the second service device.

[0334] Optionally, in this embodiment, after the UPF network element associates the PDU session with a paired protocol stack and a redundant protocol stack, the second service device can also send downlink data based on the UPF network element. Optionally, the method provided in this application embodiment may further include:

[0335] Step 1209: The second service device sends downlink service packets to the UPF network element. Correspondingly, the UPF network element receives the downlink service packets from the second service device.

[0336] Step 1210: The UPF network element adds the first field information to the downlink service message.

[0337] For example, the UPF network element adds the first field information to the downlink service message to obtain the first downlink service message.

[0338] Among them, adding the first field information to the UPF network element falls into two categories:

[0339] Scenario 1: When the redundancy mode is dual-transmit selective-receive, the redundant protocol stack associated with the PDU session in the UPF network element replicates the downlink service packets and adds the redundant protocol field to the downlink service packets. The pairing protocol stack associated with the PDU in the UPF network element then adds the pairing protocol field to the replicated downlink service packets.

[0340] In one possible implementation, the UPF determines the redundant transmission mode based on the parameter information corresponding to the redundant transmission mode. For example, when the redundant protocol is HSR or FRER, the redundant transmission mode is determined to be a dual-transmission selective-receive mode.

[0341] For example, when a UPF network element receives service message 1, it determines the redundant transmission mode to be dual-transmit selective-receive according to the HSR protocol. The redundant protocol stack in the UPF network element copies service message 1 to obtain service message 1 and service message 2. The redundant protocol stack then adds the redundant protocol fields to service message 1 and service message 2 respectively. The pairwise protocol stack in the UPF network element adds the pairwise protocol fields to service message 1 and service message 2 respectively.

[0342] Case 2: When the redundancy mode is load balancing, the pairing protocol stack associated with the PDU session in the UPF network element will add the pairing protocol field to the downlink service message.

[0343] In one possible implementation, UPF determines the redundant transmission method as load balancing based on a load balancing algorithm.

[0344] For example, when a UPF network element receives service message 1, it determines the redundant transmission mode to be load balancing based on the load balancing algorithm. The pairing protocol stack in the UPF network element then adds the pairing protocol field to service message 1.

[0345] Step 1211: The UPF network element sends a downlink service packet carrying the first field information to the terminal device. Correspondingly, the terminal device receives the first downlink service packet carrying the first field information from the UPF network element.

[0346] In one possible implementation, the UPF network element sends a downlink service message carrying the first field information to the terminal device via a PDU session. The first communication module and / or the second communication module in the terminal device receive the downlink service message carrying the first field information from the UPF network element.

[0347] For example, when the redundancy mode is dual-transmit selective reception, the first and second communication modules in the terminal device each receive two identical downlink service packets. For instance, the first communication module receives service packet 1, and the second communication module receives service packet 2. Alternatively, the first communication module receives service packet 2, and the second communication module receives service packet 1. Here, service packet 2 is a copy of service packet 1; or it could be that service packet 1 is a copy of service packet 2, which is not limited here.

[0348] For example, when the redundancy mode is load balancing, the first communication module or the second communication module in the terminal device receives service message 1 carrying the first field information. For instance, the first communication module receives service message 1, or the second communication module receives service message 1.

[0349] Step 1212: The terminal device processes the first downlink service message carrying the first field information to obtain the second downlink service message.

[0350] The specific implementation method is similar to step 1208, and will not be repeated here. The difference is that the downlink service message (i.e., the second downlink service message) processed in step 1212 is sent by the terminal device to the first service device, while the service message processed in step 1208 is sent by the UPF network element to the second service device.

[0351] In one possible implementation, the pairing protocol stack in the terminal device strips the pairing protocol field from the downlink service packet carrying the first field information and sends it to the redundancy protocol stack. When the redundancy transmission mode is dual-transmission selective reception, the redundancy protocol stack performs redundancy deduplication on the duplicate parts of the packet according to the processing rules defined by the dual-transmission selective reception protocol, and strips the redundant protocol field. Then, the redundancy protocol stack forwards the processed downlink service packet. When the redundancy transmission mode is load balancing, since the first field information does not carry the redundant protocol field, the redundancy protocol stack directly forwards the first downlink service packet stripped of the pairing protocol field.

[0352] It is understandable that, such as Figure 12 In the embodiment shown, after the uplink data triggers the pairing of multiple PDU paths for redundancy, the UPF network element can perform redundant transmission of uplink service packets. That is, steps 1204, 1205 and 1208 in the above embodiment can be regarded as the process of redundant transmission of uplink service packets.

[0353] like Figure 14 As shown, Figure 14 This is a schematic diagram illustrating a process for triggering redundancy pairing of multiple transmission channels for downlink data, provided in an embodiment of this application.

[0354] exist Figure 14In the illustrated embodiment, the UPF network element is a single entity, and no control plane participates in controlling the UPF network element. The specific method includes:

[0355] Steps 1401 to 1402 are the same as steps 1201 to 1202 in the above embodiments, and will not be repeated here.

[0356] Step 1403: The second service device sends downlink service packets to the UPF network element. Correspondingly, the UPF network element receives the downlink service packets from the second service device.

[0357] The second service device is used to provide downlink data.

[0358] Among them, several PDU sessions in the UPF network element have not yet been paired up. The specific communication structure is as follows: Figure 13 As shown in Figure (a).

[0359] Step 1404: The UPF network element sends downlink service packets to the terminal device. Correspondingly, the terminal device receives the downlink service packets from the UPF network element.

[0360] In one possible implementation, the UPF network element forwards downlink service packets to the PDU session according to the packet forwarding rules, and then forwards the downlink service packets to the terminal equipment.

[0361] For example, when the downlink service message type is a broadcast message, the UPF network element will forward the downlink service message to each PDU session. As another example, when the downlink service message type is a unicast message, the UPF network element will forward the downlink service message to a specific PDU session based on the address information (destination MAC address) in the downlink service message.

[0362] In one possible implementation, the terminal device receives downlink service messages from the UPF network element through a first communication module and / or a second communication module.

[0363] For example, when the downlink service message type is a broadcast message, each PDU session receives the downlink service message forwarded by the UPF network element and then sends the downlink service message to the terminal device. The communication module in the terminal device receives the downlink service message from the PDU session.

[0364] For example, if the downlink service message received by the UPF network element is a broadcast message, the UPF network element will forward the downlink service message to PDU session 1 and PDU session 2. PDU session 1 will forward the downlink service message to the first communication module of the terminal device. PDU session 2 will forward the downlink service message to the second communication module of the terminal device.

[0365] For example, when the downlink service message type is a unicast message, after a specific PDU session receives the downlink service message forwarded by the UPF network element, the PDU session sends the downlink service message to the terminal device, and the communication module in the terminal device corresponding to the PDU session receives the downlink service message from the PDU session.

[0366] For example, the downlink service message received by the UPF network element is a unicast message. Based on the destination MAC address in the downlink service message, the UPF network element forwards the downlink service message to PDU session 2. PDU session 2 then forwards the downlink service message to the second communication module of the terminal device.

[0367] It is worth noting that the downlink service message in step 1304 above does not carry the first field information.

[0368] Step 1405: The terminal device sends a pairing protocol message to the UPF network element. Correspondingly, the UPF network element receives the pairing protocol message from the terminal device.

[0369] For example, see reference. Figure 10 The diagram shows the frame structure of a pairing protocol message. The pairing protocol message includes a pairing field (Ethernet type) and a pairing device identifier. The pairing field (Ethernet type) indicates that the message contains pairing information, and the pairing device identifier indicates that the transmission channels under this device need to be paired to form redundant transmission channels.

[0370] In one possible implementation, the redundant transceiver module in the terminal device discards downlink service packets that do not carry the first field information, and then sends a pairing protocol message to the communication module that received the downlink service packet. The communication module then sends the pairing protocol message to the UPF network element.

[0371] For example, after receiving a downlink service packet from the UPF network element, the first communication module sends the downlink service packet to the redundant transceiver module. After determining that the downlink service packet does not carry any field information, the redundant transceiver module discards the downlink service packet and sends a pairing protocol packet to the first communication module. Finally, the terminal device sends the pairing protocol packet to the UPF network element through the first communication module.

[0372] Step 1406: The UPF network element pairs PDU session 1 and PDU session 2 to form a redundant transmission channel according to the pairing protocol message.

[0373] In one possible implementation, the UPF network element recognizes the message as a pairing protocol message based on the destination address in the pairing protocol message.

[0374] The pairing protocol message carries pairing field information, and the UPF network element completes the pairing of multiple transmission channels based on the pairing field information. For specific implementation details, refer to steps 1206 to 1207 in the above embodiment.

[0375] After the UPF network elements complete the transmission channel pairing, the communication structure is as follows: Figure 13 As shown in Figure (b), a redundant transmission channel is formed between the terminal device and the UPF network element. This communication structure can perform redundant transmission of uplink or downlink service messages. For specific implementation details, please refer to the above. Figure 12 The embodiments shown are not described in detail here.

[0376] like Figure 15 As shown, Figure 15 This is a schematic diagram illustrating a specific structure of the communication architecture after PDU pairing, provided as an embodiment of this application. (Combined with...) Figure 14 The communication structure shown divides the transmission of service messages between the terminal device and the UPF network element into two directions: uplink and downlink.

[0377] 1) Upward direction:

[0378] Step 1: The first service device sends a service message to the terminal device. The service message frame format is Ethernet frame format, such as... Figure 15 As shown, the service message includes payload, 802.1q (optional), SMAC, and DMAC.

[0379] Step 2: After receiving the service message, the terminal device processes it through the redundant protocol stack and adds redundant protocol fields to the message according to the redundant protocol rules.

[0380] For example, the business message after adding the redundant protocol field is as follows: Figure 15 As shown, it includes payload, redundant tag, 802.1q (optional), SMAC, and DMAC. Through the pairwise protocol stack, a pairwise protocol field is added to the business message. The business message with the pairwise protocol field added is as follows: Figure 15 As shown, it includes payload, redundant tag, pair tag, 802.1q (optional), SMAC, and DMAC. The pair protocol stack sends service packets to the communication module, which then sends service packets to the UPF network element.

[0381] Whether to add a redundant protocol field to the redundant protocol stack, and the number of communication modules sending service messages, depends on the redundant transmission method, as detailed above. Figure 11 or Figure 13 The embodiments shown are not described in detail here.

[0382] Step 3: After receiving service packets from the terminal device through the PDU session, the UPF network element removes the pairing tag from the service packets using the pairing protocol stack. The service packets after removing the pairing tag are as follows: Figure 15 As shown, it includes payload, redundant tag, 802.1q (optional), SMAC, and DMAC. Redundant tags are removed from the service packet using the redundant protocol stack. The service packet after removing redundant tags is as follows: Figure 15 As shown, it includes the payload, 802.1q (optional), SMAC, and DMAC.

[0383] Step 4: The UPF network element sends the service information to the second service device. The service information includes the payload, redundant tag, 802.1q (optional), SMAC, and DMAC.

[0384] 2) Downlink direction: The difference from the uplink direction is that in the downlink direction, the UPF network element is used to add field information to the service message, and the terminal device is used to strip the field information.

[0385] In one possible embodiment of this application, there may be multiple UPF network elements. For example... Figure 16 As shown, Figure 16 This illustration shows a full-mesh networking scenario between control plane network elements and user plane network elements, as provided in this application embodiment. In this scenario, a terminal device accesses the network and establishes a transmission channel. The creation process of a PDU session in a UPF network element is controlled by the control plane network element. For example, the control plane network element selects a UPF network element for the terminal device and creates a PDU session on the selected UPF network element. In this scenario, before the terminal device establishes multiple transmission channel pairs, the PDU session may be carried on different UPF network elements, thus requiring dynamic pairing of transmission channels.

[0386] like Figure 17 As shown, Figure 17 This is a schematic diagram illustrating a process for triggering dynamic redundancy pairing of multiple transmission channels based on uplink data, as provided in an embodiment of this application. Figure 17 In the illustrated embodiment, the UPF network elements include UPF1 and UPF2, and the specific method includes:

[0387] Steps 1701 to 1705 are similar to steps 1201 to 1205 in the above embodiment. The difference is that the terminal device needs to send uplink service messages carrying the first field information to both UPF1 and UPF2. The specific implementation method will not be described here.

[0388] Step 1706: UPF1 sends a pairing request message to the SMF network element. Correspondingly, the SMF network element receives the pairing request message from UPF1. Alternatively, UPF2 sends a pairing request message to the SMF network element. Correspondingly, the SMF network element receives the pairing request message from UPF2.

[0389] The pairing request message includes: the identifier of the pairing device and the identifier of the PDU session. The identifier of the pairing device is used to indicate the terminal devices that need to be paired, and the identifier of the PDU session is used to indicate the transmission channels that need to be paired.

[0390] Step 1707: The SMF network element checks whether the terminal device allows redundant communication based on the pairing request message.

[0391] Case 1) The SMF network element determines that the terminal device is allowed to perform redundant communication.

[0392] In one possible implementation, after receiving an uplink service message carrying field information, UPF1 or UPF2 determines that the identifier of the terminal device is in the whitelist of devices that are allowed to perform redundant communication based on the redundant communication information. If the whitelist information is correct, then the terminal device is allowed to perform redundant communication.

[0393] When redundant communication is permitted for terminal devices, the method provided in this application embodiment further includes: the SMF network element acquiring the redundant transmission mode and the parameter information corresponding to the redundant transmission mode in the redundant communication information.

[0394] It is worth noting that while obtaining the whitelist information of devices that are allowed to perform redundant communication, the SMF network element can also obtain the redundant transmission mode and the parameter information corresponding to the redundant transmission mode.

[0395] Case 2) The SMF network element determines that redundant communication by the terminal device is not allowed.

[0396] In one possible implementation, UPF1 or UPF2 determines that the terminal device's identifier is not in the whitelist of devices that are allowed to perform redundant communication based on the redundant communication information. If the whitelist information is not in the whitelist, then the terminal device is not allowed to perform redundant communication.

[0397] In cases where redundant communication by terminal devices is not permitted, the method provided in this application embodiment further includes:

[0398] Step 1: The SMF network element sends a first pairing response message to UPF1 or UPF2. Correspondingly, the UPF1 or UPF2 network element receives the first pairing response message from the SMF network element.

[0399] The first pairing response message is used to indicate the rejection of the pairing requests from UPF1 and UPF2.

[0400] Step 2: UPF1 and UPF2 discard the upstream business message based on the pairing feedback message.

[0401] Step 1708: SMF network element determines the target UPF network element.

[0402] The target UPF is the UPF network element indicated by the SMF network element for pairing transmission channels. For example, the SMF network element can determine UPF1 as the target UPF, or it can determine UPF2 as the target UPF.

[0403] Understandably, although there are multiple UPF network elements, in order to ensure that multiple transmission channels of the same terminal device can be paired on the same UPF network element, the SMF network element needs to select the same UPF network element for the PDU session corresponding to the transmission channel to be paired, based on the identifier of the paired device.

[0404] In one possible embodiment of this application, the UPF network element that sends the pairing request message to the SMF network element in step 1706 is the same UPF network element as the target UPF determined by the SMF network element in step 1708. For example, in step 1706, UPF1 sends a pairing request message to the SMF network element, and in step 1708, the SMF network element determines UPF1 as the target UPF; or, in step 1706, UPF2 sends a pairing request message to the SMF network element, and in step 1708, the SMF network element determines UPF2 as the target UPF. In this case, the method provided by this embodiment further includes:

[0405] Step 1709a: The SMF network element sends a second pairing response message to the target UPF. Correspondingly, the target UPF receives the second pairing response message from the SMF network element.

[0406] The second pairing response message is used to indicate that the PDU session pairing corresponding to the transmission channel is allowed.

[0407] In one possible implementation, the second pairing response message includes: the identifier of the paired device, the identifier of the PDU session, the redundant transmission mode, and the parameter information corresponding to the redundant transmission mode.

[0408] For example, UPF1 sends a pairing request message to the SMF network element. The SMF network element determines UPF1 as the target UPF based on the identifier of the pairing device. The SMF network element sends a second pairing response message to UPF1. UPF2 sends a pairing request message to the SMF network element. The SMF network element determines UPF2 as the target UPF based on the identifier of the pairing device. The SMF network element sends a second pairing response message to UPF2.

[0409] In one possible embodiment of this application, the UPF network element that sends the pairing request message to the SMF network element in step 1706 is not the same UPF network element as the target UPF determined by the SMF network element in step 1708. For example, in step 1706, UPF1 sends a pairing request message to the SMF network element, and in step 1708, the SMF network element determines UPF2 as the target UPF; or, in step 1706, UPF2 sends a pairing request message to the SMF network element, and in step 1708, the SMF network element determines UPF1 as the target UPF. In this case, the method provided by this embodiment further includes:

[0410] Step 1709b1: The SMF network element sends a third pairing response message to other UPF network elements. Correspondingly, the other UPF network elements receive the third pairing response message from the SMF network element.

[0411] Among them, other UPF network elements are UPF network elements that send pairing request messages to SMF network elements.

[0412] For example, if UPF1 sends a pairing request message to the SMF network element, then when the SMF network element determines that UPF2 is the target UPF, the SMF network element sends a third pairing response message to UPF1. Alternatively, if UPF2 sends a pairing request message to the SMF network element, then when the SMF network element determines that UPF1 is the target UPF, the SMF network element sends a third pairing response message to UPF2.

[0413] The third pairing response message is used to indicate that the PDU session corresponding to the transmission channel is migrated to the target UPF.

[0414] For example, if UPF1 sends a pairing request message to the SMF network element, and the SMF network element determines that UPF2 is the target UPF, the SMF network element sends a third pairing response message to UPF1 to instruct the PDU sessions in UPF1 to migrate to UPF2. Alternatively, if UPF2 sends a pairing request message to the SMF network element, and the SMF network element determines that UPF1 is the target UPF, the SMF network element sends a third pairing response message to UPF2 to instruct the PDU sessions in UPF2 to migrate to UPF1.

[0415] Step 1709b2: The SMF network element sends pairing instruction information to the target UPF. Correspondingly, the target UPF receives the pairing instruction information from the SMF network element.

[0416] Among them, the pairing indication information is used to indicate the pairing of PDU sessions in the target UPF.

[0417] In one possible implementation, the pairing indication information includes, but is not limited to: the identifier of the paired device, the identifier of the PDU session, the redundant transmission method, and the parameter information corresponding to the redundant transmission method.

[0418] Steps 1710 and 1711 are similar to steps 1206 and 1207 in the above embodiments. The difference is that in steps 1710 and 1711, a pair protocol stack and a redundant protocol stack are created for the target UPF, and the PDU session is associated with the pair protocol stack and the redundant protocol stack. The PDU session in the target UPF is migrated from other UPF network elements.

[0419] After associating the PDU session with the paired protocol stack and redundant protocol stack in the target UPF network element, the processing methods for uplink service messages sent by the first service device and downlink service messages sent by the second service device are as follows: Figure 12 The embodiments described herein will not be repeated here.

[0420] like Figure 18 As shown, Figure 18 This is a schematic diagram illustrating a process for triggering dynamic redundancy pairing of multiple transmission channels for downlink data, provided in an embodiment of this application. Figure 18 In the illustrated embodiment, the UPF network elements include UPF1 and UPF2. The specific method includes:

[0421] Steps 1801 to 1805 are the same as those described above. Figure 14 Steps 1401 to 1405 in the illustrated embodiment are similar, except that, Figure 18 In the illustrated embodiment, the second service device sends downlink service messages to UPF1 and UPF2, and both UPF1 and UPF2 send downlink service messages to the terminal device. The terminal device sends pairing protocol messages to UPF1 and UPF2.

[0422] Steps 1806 to 1811 are similar to steps 1706 to 1711 in the above embodiments, and will not be described again here.

[0423] The above mainly describes the solutions of the embodiments of this application from the perspective of interaction between various network elements. It is understood that each network element, such as a terminal or network device, includes corresponding structures and / or software modules to perform the above functions in order to achieve them. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0424] This application embodiment can divide functional units according to the terminal device and network device described above. For example, each function can be divided into separate functional units, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0425] The above combination Figure 6 and Figure 9 The methods described in the embodiments of this application have been explained. The communication apparatus provided in the embodiments of this application for executing the above methods is described below. Those skilled in the art will understand that the methods and apparatus can be combined with and referenced in each other, and the communication apparatus provided in the embodiments of this application can execute the steps performed by the network controller and the terminal in the above analysis method.

[0426] When using integrated units Figure 19 The communication device involved in the above embodiments is shown. The communication device 190 may include a communication module 1901 and a processing module 1902.

[0427] In an alternative implementation, the communication device 190 may further include a storage module 1903 for storing the program code and data of the communication device.

[0428] On one hand, the communication device 190 is a terminal device, or a chip applied in a terminal device. In this case, the communication module 1901 is used to support communication between the communication device and an external network element (e.g., a first network element). For example, the communication module 1901 is used to perform signal transmission and reception operations of the terminal device in the above method embodiment. The processing module 1902 is used to perform signal processing operations of the terminal device in the above method embodiment.

[0429] In one example, the communication module 1901 is used to perform the above embodiments. Figure 9 The receiving action in step 902 is performed by the terminal device. The communication module 1901 is used to perform the above-described embodiment. Figure 6 The sending action performed by the terminal device in step 602.

[0430] In one possible embodiment, the processing module 1902 is configured to perform the above embodiments. Figure 3 The processing action performed by the terminal device in step 302.

[0431] On the other hand, the communication device 190 is a first network element, or a chip applied in a first network element. In this case, the communication module 1901 is used to support communication between the communication device and an external network element (e.g., a terminal device). For example, the communication module 1901 is used to perform signal transmission and reception operations of the first network element in the above method embodiment. The processing module 1902 is used to perform signal processing operations of the first network element in the above method embodiment.

[0432] In one example, the communication module 1901 is used to perform the above embodiments. Figure 9 The transmission action performed by the first network element in step 902. Communication module 1901 is used to perform the above-described embodiment. Figure 6 The receiving action performed by the first network element in step 602.

[0433] The processing module 1902 can be a processor or controller, such as a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The communication module can be a transceiver, transceiver circuitry, or communication interface, etc. The storage module can be a memory.

[0434] When the processing module 1902 is a processor 2001 or a processor 2005, the communication module 1901 is a transceiver 2003, and the storage module 1903 is a memory 2002, the communication device involved in this application can be... Figure 20 The communication device shown.

[0435] Figure 20 This illustration shows a schematic diagram of the hardware structure of a communication device according to an embodiment of this application. The hardware structures of the terminal device and network device in this embodiment can be referenced as follows: Figure 20 The structure shown is that the communication device includes a processor 2001, a communication line 2004, and at least one transceiver. Figure 20 (The example shown is merely illustrative and includes a transceiver 2003.)

[0436] The processor 2001 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0437] The communication line 2004 may include a path for transmitting information between the aforementioned components.

[0438] Transceiver 2003 refers to any transceiver-like device used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0439] Optionally, the communication device may also include a memory 2002.

[0440] The memory 2002 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 2002 may exist independently and be connected to the processor 2001 via communication line 2004. The memory 2002 may also be integrated with the processor 2001.

[0441] The memory 2002 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 2001. The processor 2001 executes the computer execution instructions stored in the memory 2002, thereby implementing the communication method provided in the following embodiments of this application.

[0442] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0443] In a specific implementation, as one example, the processor 2001 may include one or more CPUs, for example... Figure 20 CPU0 and CPU1 in the CPU.

[0444] In a specific implementation, as one example, the communication device may include multiple processors, for example... Figure 20 Processors 2001 and 2002 are mentioned. Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0445] Figure 21 This is a schematic diagram of the structure of chip 210 provided in an embodiment of this application. Chip 210 includes one or more (including two) processors 2110 and communication interfaces 2130.

[0446] Optionally, the chip 210 also includes a memory 2140, which may include read-only memory and random access memory, and provides operation instructions and data to the processor 2110. A portion of the memory 2140 may also include non-volatile random access memory (NVRAM).

[0447] In some implementations, memory 2140 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0448] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 2140 (the operation instructions can be stored in the operating system).

[0449] One possible implementation is that the terminal and network devices have similar structures, and different devices can use different chips to achieve their respective functions.

[0450] The processor 2110 controls the processing operations of any terminal or network device. The processor 2110 can also be called a central processing unit (CPU).

[0451] Memory 2140 may include read-only memory and random access memory, and provides instructions and data to processor 2110. A portion of memory 2140 may also include NVRAM. For example, in an application, memory 2140, communication interface 2130, and memory 2140 are coupled together via bus system 2120, which may include, in addition to data bus, power bus, control bus, and status signal bus, etc. However, for clarity, in Figure 21 The general labeled all buses as Bus System 2120.

[0452] The methods disclosed in the embodiments of this application can be applied to or implemented by the processor 2110. The processor 2110 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in the processor 2110 or by instructions in the form of software. The processor 2110 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 2140. Processor 2110 reads the information in memory 2140 and, in conjunction with its hardware, completes the steps of the above method.

[0453] In one possible implementation, the communication interface 2130 is used to perform... Figure 6 The steps of receiving and transmitting data in the terminal device shown in the embodiment are illustrated. Processor 2110 is used to execute... Figure 6 The processing steps of the terminal device in the illustrated embodiment.

[0454] In one possible implementation, the communication interface 2130 is used to perform... Figure 9 The steps of receiving and transmitting data in the terminal device shown in the embodiment are illustrated. Processor 2110 is used to execute... Figure 9 The processing steps of the terminal device in the illustrated embodiment.

[0455] In one possible implementation, the communication interface 2130 is used to perform... Figure 6 The illustrated embodiment describes the receiving and transmitting steps of the first network element. Processor 2110 is used to execute... Figure 6 The steps for processing the first network element in the illustrated embodiment.

[0456] In one possible implementation, the communication interface 2130 is used to perform... Figure 9 The illustrated embodiment describes the receiving and transmitting steps of the first network element. Processor 2110 is used to execute... Figure 9 The steps for processing the first network element in the illustrated embodiment.

[0457] The communication module described above can be a communication interface of the device, used to receive signals from other devices. For example, when the device is implemented as a chip, the communication module is the communication interface used by the chip to receive or send signals from other chips or devices.

[0458] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 6 and Figure 9 Functions performed by terminal devices.

[0459] On the one hand, a computer-readable storage medium is provided, in which instructions are stored, which, when executed, implement as follows: Figure 6 and Figure 9 The function performed by the first network element.

[0460] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 6 and Figure 9 Functions performed by terminal devices.

[0461] On the one hand, a computer program product including instructions is provided, wherein the computer program product includes instructions that, when executed, implement such... Figure 6 and Figure 9 The function performed by the first network element.

[0462] On the one hand, a chip is provided for use in a computing network controller. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 6 and Figure 9 Functions performed by terminal devices.

[0463] On the one hand, a chip is provided for use in a network manager. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor. The processor is used to execute instructions to achieve, for example... Figure 6 and Figure 9 The function performed by the first network element.

[0464] This application provides a communication system, which includes a terminal device and a first network element. The terminal device is used to perform actions such as... Figure 6 The communication method shown. The first network element is used to perform, as... Figure 9 The communication method shown.

[0465] Optionally, the communication system provided in this application embodiment further includes a control plane network element, which is used to control the terminal equipment to access the network and provide PDU connection services to the terminal equipment. The control plane network element is also used to select the same first network element for multiple PDU sessions.

[0466] Optionally, the communication system provided in this application embodiment further includes a first service device and a second service device. The first service device is used to provide uplink service messages to the terminal device, and the second service device is used to provide downlink service messages to the first network element.

[0467] The explanations and beneficial effects of the relevant content in any of the communication devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0468] In this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0469] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0470] It should be understood that the processor mentioned in the embodiments of this application can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0471] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0472] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) is integrated into the processor.

[0473] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0474] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

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

[0476] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0477] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0478] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0479] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0480] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: establishing a plurality of transmission channels with a first network element; sending first field information to the first network element, the first field information comprising a pairing protocol field, the pairing protocol field comprising an identifier of a terminal device, the pairing protocol field being used to indicate that a plurality of the transmission channels in the terminal device are paired to form a redundant transmission channel.

2. The method of claim 1, wherein, The sending of the first field information to the first network element comprises: receiving a first service packet from a first device; adding the first field information to the service packet to obtain a first service packet; sending the first service packet to the first network element.

3. The method of claim 1, wherein, The sending of the first field information to the first network element comprises: receiving a second service packet from the first network element, the second service packet not carrying the first field information; sending a protocol packet to the first network element according to the second service packet, the protocol packet comprising the first field information.

4. The method according to any one of claims 1 to 3, characterized in that, The redundant transmission mode of the plurality of transmission channels comprises dual-transmission and load balancing; in the case where the redundant transmission mode of the plurality of transmission channels is the dual-transmission, each of the transmission channels is used to send the first field information; in the case where the redundant transmission mode of the plurality of transmission channels is the load balancing, one of the plurality of transmission channels is used to send the first field information.

5. The method of claim 4, wherein, In the case where the redundant transmission mode of the plurality of transmission channels is the dual-transmission, the first field information further comprises a redundant protocol field, the redundant protocol field being used to identify that the first field information is redundantly sent.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: receiving a third service packet from the first network element, the third service packet carrying the first field information; stripping the pairing protocol field in the first field information; sending the third service packet from which the pairing protocol field is stripped to a first device.

7. The method of claim 6, wherein, In the case where the first field information comprises a redundant protocol field, the method further comprises: removing duplicate data in the third service packet and stripping the redundant protocol field; sending the third service packet from which the pairing protocol field and the redundant protocol field are stripped to the first device.

8. A communication method characterized by comprising: The method comprises: receiving redundant communication information, the redundant communication information being used to indicate that a terminal device is allowed to form a redundant transmission channel, the redundant communication information comprising an identifier of the terminal device and information of a redundant transmission mode; receiving first field information from the terminal device, the first field information comprising a pairing protocol field, the pairing protocol field comprising the identifier of the terminal device, the pairing protocol field being used to indicate that a plurality of transmission channels of the terminal device are paired to form the redundant transmission channel.

9. The method of claim 8, wherein, The receiving of the first field information from the terminal device comprises: receiving a first service packet from the terminal device, the first service packet comprising the first field information.

10. The method of claim 8, wherein, The receiving of the first field information from the terminal device comprises: sending a second service packet to the terminal device, the second service packet not carrying the first field information; receiving a protocol packet from the terminal device, the protocol packet comprising the first field information.

11. The method according to any one of claims 8 to 10, characterized in that, The method further comprises: associating the plurality of transmission channels with a pairing protocol stack and a redundant protocol stack, the pairing protocol stack being configured to strip the pairing protocol field from a third service packet, the third service packet comprising the first field information, and the redundant protocol stack being configured to forward the third service packet from which the pairing protocol field is stripped.

12. The method of claim 11, wherein, In a case where the first field information comprises a redundant protocol field, the redundant protocol stack is further configured to remove duplicated data from the third service packet and to strip the redundant protocol field.

13. The method according to any one of claims 8 to 12, characterized in that, The method further comprises: sending a pairing request message to a second network element, the pairing request message comprising an identifier of the terminal device and identifiers of the plurality of transmission channels, the second network element being configured to determine a network element that is configured to pair the plurality of transmission channels to form redundant transmission channels.

14. The method of claim 13, wherein, In a case where the network element that is configured to pair the plurality of transmission channels to form redundant transmission channels is a first network element, the method comprises: receiving a first response message from the second network element, the first response message indicating that the first network element is configured to pair the plurality of transmission channels to form redundant transmission channels.

15. The method of claim 14, wherein, In a case where the network element that is configured to pair the plurality of transmission channels to form redundant transmission channels is a third network element, the method comprises: receiving a second response message from the second network element, the second response message indicating that the plurality of transmission channels are to be migrated to the third network element, the third network element having established the plurality of transmission channels with the terminal device; sending indication information to the third network element, the indication information indicating that the third network element is configured to pair the plurality of transmission channels to form redundant transmission channels.

16. The method according to any one of claims 8 to 15, characterized in that, The method further comprises: receiving a third service packet from the terminal device, the third service packet comprising the first field information; stripping a pairing protocol field from the first field information; sending the third service packet from which the pairing protocol field is stripped to a second device, the second device being configured to provide data transmitted by a network device to the terminal device.

17. The method of claim 16, wherein, In a case where the first field information comprises a redundant protocol field, the method further comprises: removing duplicated data from the third service packet and stripping the redundant protocol field; sending the third service packet from which the pairing protocol field and the redundant protocol field are stripped to the second device.

18. The method according to any one of claims 8 to 17, characterized in that, The method further comprises: receiving a fourth service packet from a second device; adding the first field information to the fourth service packet; sending the fourth service packet to which the first field information is added to the terminal device.

19. A communications device, characterized by The apparatus comprises a communication module and a processing module. The processing module is configured to perform the processing of the terminal device in the method of any one of claims 1 to 7, and the communication module is configured to perform the receiving or sending of the terminal device in the method of any one of claims 1 to 7; or The processing module is configured to perform the processing of the first network element in the method of any one of claims 8-18, and the communication module is configured to perform the receiving or sending of the first network element in the method of any one of claims 8-18.

20. A communication system, characterized by The system comprises a terminal device and a first network element. The terminal device is configured to implement the method of any one of claims 1-7, and the first network element is configured to implement the method of any one of claims 8-18.

21. The system of claim 20, wherein, The system further comprises a second network element, a first device, and a second device. The second network element is configured to select a network element that completes pairing of multiple transmission channels to form a redundant transmission channel, the first device is configured to send a first service packet to the terminal device, and the second device is configured to send a second service packet to the first network element.

22. A communications device, comprising: The communication device comprises a memory and a processor, the memory is configured to store instructions, the processor is configured to execute the instructions stored in the memory, and execution of the instructions stored in the memory causes the processor to implement the method of any one of claims 1-7. Alternatively, the method of any one of claims 8-18 is executed.

23. A chip, characterized by The chip comprises at least one processor and a communication interface, the communication interface is coupled with the at least one processor, the at least one processor is configured to run a computer program or instructions to implement the method of any one of claims 1-7, or to implement the method of any one of claims 8-18, and the communication interface is configured to communicate with other modules outside the chip.

24. A computer-readable storage medium, characterized in that, The computer readable storage medium stores instructions, and when the instructions are executed, the method of any one of claims 1-7 is implemented, or the method of any one of claims 8-18 is implemented.

Images