Data transmission method and equipment thereof

Abstract

The embodiment of the invention discloses a data transmission method and equipment thereof, which are used in an Ethernet packet transmission scene. The method comprises the steps that a first device receives a first message, the load data in the first message comprises filling redundant data, the first device deletes the filling redundant data, the first device generates a second message, and the second message comprises the filling redundant data; the load data in the second message is effective load data in the first message after the filling redundant data is deleted, and the first device sends the second message to a second device. In the embodiment of the invention, the first equipment deletes the filling redundant data in the first message, so that the filling redundant data does not need to be transmitted in air interface transmission, air interface resources are saved, and the air interface capacity is improved.

Description

[0001] This application is a divisional application. The application number of the original application is 202080101252.7, and the original application date is September 2, 2020. The entire contents of the original application are incorporated into this application by reference. Technical Field

[0002] The present application relates to the field of communications, and in particular to a data transmission method and device thereof. Background Art

[0003] In order to meet the requirements of Carrier Sense Multiple Access with Collision Detection (CSMA / CD) for collision detection and backoff retransmission mechanism, CSMA / CD has a minimum size limit for Ethernet messages, such as 64 bytes. Frames with a length of less than 64 bytes will be regarded by forwarding devices in the network as invalid frames that are abnormally terminated due to a collision.

[0004] In the field of industrial applications, the payload of the application layer message of industrial applications is usually small, such as 10 bytes or 20 bytes. In order to meet the minimum Ethernet frame size limit of industrial Ethernet, it is necessary to add a padding redundant field to the payload part of the message so that the size of the message is equal to or greater than 64 bytes.

[0005] In the process of message transmission, due to the addition of redundant padding, too many air interface resources will be occupied during air interface transmission, which is not conducive to improving the air interface capacity. Summary of the invention

[0006] The embodiment of the present application provides a data transmission method and device thereof, which is used to delete the padding redundant data in the message when transmitting Ethernet packets, so that there is no need to transmit the padding redundant data during air interface transmission, thereby saving air interface resources and improving air interface capacity.

[0007] A first aspect of an embodiment of the present application provides a data transmission method.

[0008] The first device receives a first message, the payload data in the first message includes padding redundant data, the first device deletes the padding redundant data, the first device generates a second message, the payload data in the second message is the effective payload data after the padding redundant data is deleted from the first message, and the first device sends the second message to the second device.

[0009] In an embodiment of the present application, the first device obtains a second message by deleting the padding redundant data in the received first message, and sends the second message to the second device. In this way, in subsequent air interface transmission, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0010] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device receives first indication information, and the first device deletes the padding redundant data, including: the first device deletes the padding redundant data according to the first indication information.

[0011] In the embodiment of the present application, redundant padding data is deleted through received indication information, thereby providing high execution efficiency of the first device and ensuring normal transmission of effective load data.

[0012] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation method, the first indication information is used to instruct the first network device to delete the padding redundant data, or the first indication information includes the length information of the padding redundant data, or the location information of the padding redundant data, or the first indication information includes the length information of the payload data of the first downlink message, or the location information of the payload data of the first message.

[0013] In the embodiment of the present application, the first indication information is described as being specifically used to indicate content, thereby improving the flexibility of the solution.

[0014] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device deletes the padding redundant data including: the first device deletes the padding redundant data according to the length field of the first message.

[0015] In the embodiment of the present application, the padding redundant data is deleted through the length field of the first message, thereby improving the flexibility of the first device in deleting the padding redundant data.

[0016] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device is a user plane network element UPF, the second device is a radio access network device RAN, and the first message is a downlink Ethernet message.

[0017] In the embodiments of the present application, specific implementation methods of the first device and the second device are explained to improve the feasibility of the solution.

[0018] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device generating the second message includes:

[0019] The first device encapsulates the third message according to the N3 tunnel protocol to obtain a fourth message, wherein the third message is the message after the redundant padding data is deleted from the first message; if the data length of the fourth message is less than the minimum frame length of Ethernet, the tunnel protocol redundant padding data is added to the N3 tunnel protocol header of the fourth message to obtain a second message, and the data length of the second message is greater than or equal to the minimum frame length of Ethernet; or,

[0020] If the first device determines that the data length of the encapsulated message obtained by the first device encapsulating the third message according to the N3 tunnel protocol is less than the minimum frame length of Ethernet, the first device encapsulates the third message according to the N3 tunnel protocol to obtain an encapsulated message, and adds the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated message to obtain a second message, and the data length of the second message is greater than or equal to the minimum frame length of Ethernet, wherein the third message is the message after the redundant filling data is deleted from the first message.

[0021] In an embodiment of the present application, a second message is obtained by adding tunnel protocol filler redundant data in the N3 tunnel protocol header of the fourth message, so that the data length of the second message is greater than or equal to the Ethernet minimum frame length, thereby reducing the risk of errors during Ethernet transmission.

[0022] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device is a radio access network device RAN, the second device is a user equipment UE, and the first message is a downlink message.

[0023] In the embodiments of the present application, specific implementation methods of the first device and the second device are explained to improve the feasibility of the solution.

[0024] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device is a user equipment UE, the second device is a radio access network device RAN, and the first message is an uplink Ethernet message.

[0025] In the embodiments of the present application, specific implementation methods of the first device and the second device are explained to improve the feasibility of the solution.

[0026] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device is a session management network element SMF, the second device is a user equipment UE, and the first message is a downlink Ethernet message.

[0027] In the embodiments of the present application, specific implementation methods of the first device and the second device are explained to improve the feasibility of the solution.

[0028] Based on the method of the first aspect of the embodiment of the present application, in a possible implementation manner, the first device is a user equipment UE, the second device is a session management network element SMF, and the first message is an uplink Ethernet message.

[0029] In the embodiments of the present application, specific implementation methods of the first device and the second device are explained to improve the feasibility of the solution.

[0030] A second aspect of an embodiment of the present application provides a data transmission method.

[0031] The third device sends first indication information to the fourth device, wherein the first indication information is used to delete padding redundant data of the first message, or the first indication information is used to add padding redundant data to the first message, the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of the payload data of the first message, or location information of the payload data of the first message.

[0032] In the embodiment of the present application, the first indication information is sent to the fourth device to instruct deletion of the redundant data filled in the first message, so that in the subsequent air interface transmission, there is no need to transmit the redundant data filled, thereby saving air interface resources and improving the air interface capacity.

[0033] Based on the method of the second aspect of the embodiment of the present application, in a possible implementation manner, when the first indication information is used to delete the padding redundant data of the first message,

[0034] The third device is a policy control network element PCF, the fourth device is a session management network element SMF, and the first message is an Ethernet message; or,

[0035] The third device is a session management network element SMF, the fourth device is a user plane network element UPF, and the first message is an Ethernet message; or,

[0036] The third device is a session management network element SMF, the fourth device is a user equipment UE, and the first message is an Ethernet message; or,

[0037] The third device is a session management network element SMF, and the fourth device is a radio access network device RAN; or,

[0038] The third device is a radio access network device RAN, and the fourth device is a user equipment UE.

[0039] In the embodiments of the present application, specific implementation methods of the third device and the fourth device are explained to improve the feasibility of the solution.

[0040] Based on the method of the second aspect of the embodiment of the present application, in a possible implementation manner, when the first indication information is used to add padding redundant data to the first message,

[0041] The third device is SMF, the fourth device is UPF, and the first message is an Ethernet message; or,

[0042] The third device is an SMF, the fourth device is a UE, and the first message is an Ethernet message; or,

[0043] The third device is SMF, and the fourth device is RAN.

[0044] In the embodiments of the present application, specific implementation methods of the third device and the fourth device are explained to improve the feasibility of the solution.

[0045] Based on the method of the second aspect of the embodiment of the present application, in a possible implementation, the third device is a policy control network element PCF, the fourth device is a session management network element SMF, and the fifth device is an application function network element AF. Before the third device sends the first indication information to the fourth device, the third device receives the second indication information of the fifth device, and the third device determines the first indication information according to the second indication information. The second indication information is used to indicate the length information of the redundant data filled, or the position information of the redundant data filled, or the second indication information is used to indicate the length information of the payload data of the first message, or the position information of the payload data of the first message.

[0046] In an embodiment of the present application, the first indication information is determined by the second indication information sent by the AF, that is, the information of filling redundant data in the first indication information is determined based on the information of filling redundant data in the second indication information sent by the AF, and the increase, decrease or deletion operation is determined for the filled redundant data, thereby improving the feasibility of the solution.

[0047] A third aspect of the embodiments of the present application provides a device.

[0048] A device comprising:

[0049] A receiving unit, configured to receive a first message, wherein the payload data in the first message includes padding redundant data;

[0050] A deletion unit is used to delete the redundant data;

[0051] A generating unit, configured to generate a second message, wherein the payload data in the second message is the effective payload data after redundant padding data is deleted from the first message;

[0052] A sending unit, used for sending a second message to a second device.

[0053] Optionally, the receiving unit is further used to receive first indication information;

[0054] The deleting unit is specifically used to delete the padding redundant data according to the first indication information.

[0055] Optionally, the first indication information is used to instruct the device to delete the padding redundant data, or the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of the payload data of the first downlink message, or location information of the payload data of the first message.

[0056] Optionally, the deleting unit is specifically configured to delete the padding redundant data according to the Length field of the first message.

[0057] Optionally, the device is a UPF, the second device is a RAN, and the first message is a downlink Ethernet message.

[0058] Optionally, the generating unit is specifically used to encapsulate the third message according to the N3 tunnel protocol to obtain a fourth message, wherein the third message is the message after the redundant padding data is deleted from the first message; if the data length of the fourth message is less than the minimum frame length of Ethernet, the tunnel protocol is added to the N3 tunnel protocol header of the fourth message to obtain the second message, and the data length of the second message is greater than or equal to the minimum frame length of Ethernet; or,

[0059] If the device determines that the data length of the encapsulated message obtained by the first device encapsulating the third message according to the N3 tunnel protocol is less than the minimum frame length of Ethernet, the generation unit is specifically used to encapsulate the third message according to the N3 tunnel protocol to obtain an encapsulated message, and add the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated message to obtain a second message, the data length of the second message is greater than or equal to the minimum frame length of Ethernet, wherein the third message is the message after the redundant filling data is deleted from the first message.

[0060] Optionally, the device is a RAN, the second device is a UE, and the first message is a downlink message.

[0061] Optionally, the device is a UE, the second device is a RAN, and the first message is an uplink Ethernet message.

[0062] Optionally, the device is an SMF, the second device is a UE, and the first message is a downlink Ethernet message.

[0063] Optionally, the device is a UE, the second device is an SMF, and the first message is an uplink Ethernet message.

[0064] The method performed by the device provided in the third aspect of the embodiment of the present application is similar to the method performed by the first device in the aforementioned first aspect, and will not be described in detail here.

[0065] A fourth aspect of the embodiments of the present application provides a device.

[0066] A device comprising:

[0067] A sending unit, used to send first indication information to a fourth device, wherein the first indication information is used to delete padding redundant data of a first message, or the first indication information is used to add padding redundant data to the first message, the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of payload data of the first message, or location information of payload data of the first message.

[0068] Optionally,

[0069] When the first indication information is used to delete the padding redundant data of the first message,

[0070] The device is a PCF, the fourth device is an SMF, and the first message is an Ethernet message; or,

[0071] The device is SMF, the fourth device is UPF, and the first message is an Ethernet message; or,

[0072] The device is an SMF, the fourth device is a UE, and the first message is an Ethernet message; or,

[0073] The device is SMF, and the fourth device is RAN; or,

[0074] The device is RAN, and the fourth device is UE.

[0075] Optionally,

[0076] When the first indication information is used to add redundant padding data to the first message,

[0077] The device is SMF, the fourth device is UPF, and the first message is an Ethernet message; or,

[0078] The device is an SMF, the fourth device is a UE, and the first message is an Ethernet message; or,

[0079] The device is SMF, and the fourth device is RAN.

[0080] Optionally, the device is a policy control network element PCF, the fourth device is a session management network element SMF, the fifth device is an application function network element AF, and the device further includes:

[0081] A receiving unit, configured to receive second indication information of a fifth device, where the second indication information is used to indicate length information of the padding redundant data, or location information of the padding redundant data, or the second indication information is used to indicate length information of the payload data of the first message, or location information of the payload data of the first message;

[0082] A determining unit is used to determine the first indication information according to the second indication information.

[0083] The method performed by the device provided in the fourth aspect of the embodiment of the present application is similar to the method performed by the third device in the aforementioned second aspect, and will not be described in detail here.

[0084] A fifth aspect of an embodiment of the present application provides a network device or a user equipment, including:

[0085] A processor, a memory and an input-output interface, wherein the processor and the memory are connected to the input-output interface; the memory is used to store program code; and when the processor calls the program code in the memory, the method provided in the first aspect or the second aspect of the present application is executed.

[0086] The sixth aspect of the embodiments of the present application provides a storage medium. It should be noted that the essence of the technical solution of the present application or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium for storing computer software instructions used for the above-mentioned device, which includes a program designed for executing the data transmission method in the first or second aspect above.

[0087] The storage medium includes: U disk, mobile hard disk, read-only memory (ROM, full name: Read-Only Memory), random access memory (RAM, full name: Random Access Memory), disk or CD and other media that can store program code.

[0088] A seventh aspect of the embodiments of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method as implemented in the first or second aspect of the present application.

[0089] Among them, the processor mentioned in any of the above places can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the program execution of the data transmission method in the first aspect or the second aspect mentioned above.

[0090] In the technical solution provided in the embodiment of the present application, the first device obtains a second message by deleting the padding redundant data in the received first message, and sends the second message to the second device, so that in the subsequent air interface transmission, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity. BRIEF DESCRIPTION OF THE DRAWINGS

[0091] Figure 1A schematic diagram of a communication network architecture provided for an embodiment of the present application;

[0092] Figure 2 A schematic diagram of a flow chart of a data transmission method provided in an embodiment of the present application;

[0093] Figure 3 Another schematic diagram of a data transmission method according to an embodiment of the present invention;

[0094] Figure 4 Another schematic diagram of a data transmission method according to an embodiment of the present invention;

[0095] Figure 5 Another schematic diagram of a data transmission method according to an embodiment of the present invention;

[0096] Figure 6 Another schematic diagram of a data transmission method according to an embodiment of the present invention;

[0097] Figure 7 A schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0098] Figure 8 Another schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0099] Fig. 9 A schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0100] Fig.10 A schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0101] Fig.11 A schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0102] Fig.12 A schematic diagram of the structure of a message in the data transmission method provided in an embodiment of the present application;

[0103] Fig.13 A schematic diagram of the structure of the device provided in the embodiment of the present application;

[0104] Fig.14 A schematic diagram of the structure of the device provided in the embodiment of the present application;

[0105] Fig.15 Another schematic diagram of the structure of the device provided in the embodiment of the present application;

[0106] Fig.16 Another schematic diagram of the structure of the device provided in the embodiment of the present application;

[0107] Fig.17 Another schematic diagram of the structure of the device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0108] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0109] See also Figure 1 , is a schematic diagram of the communication network architecture provided in an embodiment of the present application.

[0110] like Figure 1 As shown, the communication network architecture includes user equipment (User Equipment, UE) 101, radio access network (radio access network, RAN) 102, user plane function (user plane function, UPF) 103, data network (data network, DN) 104, access and mobility management function (access and mobility management function, AMF) 105, session management function (session management function, SMF) 106, policy control function (policy control function, PCF) 107, application function (application function, AF) network element, unified data management network element (unified data managenment, UDM) 108. Among them, UE101 and AMF105 communicate through the N1 interface, UE101 and RAN102 are connected, RAN102 and AMF105 are connected through the N2 interface, RAN102 and UPF103 are connected through the N3 interface, UPF103 and DN104 are connected through the N6 interface, UPF103 and SMF106 are connected through the N4 interface, PCF107 and AF are connected through the N5 interface, SMF106 and PCF107 are connected through the N7 interface, AMF105 and SMF106 are connected through the N11 interface, AMF105 and UDM108 are connected through the N8 interface, SMF106 and UDM108 are connected through the N10 interface, and UDM108 and PCF107 are connected through the N25 interface. It can be understood that the communication network architecture provided in this application is only an example. In actual application, each network unit or user equipment can be one or more, and the connection method is not limited to this, and is not specifically limited here.

[0111] In the embodiments of the present application, UE refers to a network terminal device, such as a mobile phone, an Internet of Things terminal device, etc.

[0112] RAN is equipment that provides wireless access for terminal devices, including but not limited to eNodeB, WiFi AP, WiMAX BS, etc.

[0113] AMF is mainly responsible for mobility management in mobile networks, such as user location update, user network registration, user switching, etc.

[0114] SMF is mainly responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting UPFs that provide message forwarding functions.

[0115] PCF is responsible for providing policies to AMF and SMF, such as Quality of Service (QoS) policy and slice selection policy.

[0116] UDM is used to store user data, such as contract information, authentication or authorization information.

[0117] AF is responsible for providing services to the 3GPP network, such as influencing service routing and interacting with PCF for policy control.

[0118] UPF is mainly responsible for processing user messages, such as forwarding and billing.

[0119] DN refers to the operator network that provides data transmission services to users, such as IP Multimedia Service and the Internet.

[0120] Apart from Figure 1 In addition to the network elements in the communication network architecture, the communication network architecture also includes a network exposure function (NEF) network element, which is a network element that opens the capabilities of the communication system to third parties, application functions AF, etc., and transmits information between third parties, application servers and the communication system.

[0121] Combine the following Figure 1 The communication system framework shown provides a detailed description of the data transmission method and device provided in the embodiment of the present application.

[0122] In the embodiments of the present application, according to different transmission protocols and usage scenarios, the data processing method provided in the embodiments of the present application has multiple implementation modes.

[0123] See also Figure 2, which is a flow chart of the data transmission method provided in an embodiment of the present application.

[0124] In step 201, a user equipment establishes a protocol data unit (PDU) session.

[0125] The PDU session is used to transmit user plane data between the UE and the application server.

[0126] Through step 201, an N3 tunnel is established between NG-RAN and UPF for the PDU session. N3 tunnel refers to the tunnel between UPF and RAN. It should be noted that this embodiment can be applied to the scenario of 5G system and industrial network intercommunication, and can also be applied to other network scenarios, which are not limited here. For the scenario of 5G system and industrial network intercommunication, the application server can be a production line controller or other industrial node in the industrial network.

[0127] In step 202, the application function network element sends an AF request message to the policy control network element.

[0128] When the application function network element needs to provide some service-related information to the core network, the application function network element sends an AF request message to the policy control network element. For example, after the PDU session between the user equipment and the application server is established, the application server triggers the application function network element to send the application function network element request message, where the application function network element is the control plane network element of the application server. The AF request message carries service description information and second indication information, and the second indication information is used to indicate information related to filling redundant data of the message of the service described by the service description information.

[0129] Specifically, in a possible implementation, the second indication information may indicate length information of the padding redundant data. Specifically, the length information of the padding redundant data may be the length of the padding redundant data (padding) in the payload (payload) field of the message.

[0130] Specifically, in a possible implementation, the second indication information may also indicate location information of the padded redundant data. Specifically, the location information of the padded redundant data may be the starting location and the ending location of the padded redundant data in the payload field of the message.

[0131] Specifically, in a possible implementation, the second indication information may also indicate the length information of the payload data of the message. Specifically, the length information of the payload data of the message may be the length of the payload data in the payload field of the message.

[0132] Specifically, in a possible implementation, the second indication information may also indicate the position information of the payload data of the message. Specifically, the position information of the payload data of the message may be the starting position and the ending position of the payload data in the payload field of the message.

[0133] It should be noted that, in actual application, the second indication information may include one or more of the length information of the padding redundant data, the position information of the padding redundant data, the length information of the effective load data, or the position information of the effective load data.

[0134] Specifically, in a possible implementation, the padding redundant data is added by the Ethernet message sending end at the Media Access Control (MAC) layer.

[0135] Specifically, in another possible implementation, the padding redundant data is added by the Ethernet message sending end at a high layer, where the high layer refers to a protocol layer above the MAC layer, such as an application layer.

[0136] The service description information includes (Data Network Name, DNN), application identifier or service filtering information (traffic filtering information). The service description information is used to indicate the application targeted by the second indication information. For example, if the service description information includes DNN, the second indication information applies to service messages of all applications of the DNN; if the service description information includes an application identifier, the second indication information applies to messages of applications corresponding to the application identifier; if the service description information includes service filtering information, the second indication information applies to messages corresponding to the service filtering information. The service filtering information is Ethernet message filtering information, which may specifically include at least one of the source MAC address, destination MAC address, VLAN identifier, etc. of the service message.

[0137] In actual application, the AF request message may be directly sent to the policy control network element, or may be first sent to the NEF and then forwarded by the NEF to the policy control network element, which is not limited here.

[0138] In step 203, the policy control network element sends a policy update message to the session management network element.

[0139] After receiving the AF request message sent by the session management network element, the policy control network element obtains the second indication information and the service data flow (SDF) template in the AF request message, generates the first indication information according to the second indication information, and carries the first indication information and the SDF template in the policy update message and sends it to the session management network element. The SDF template includes the application identifier or service filtering information received by the policy control network element in step 202, or the application identifier or service filtering information of one or more applications corresponding to the DN received in step 202. The first indication information is used to delete or add redundant filling data of the message of the service described by the SDF template.

[0140] Specifically, in a possible implementation manner, the policy update message includes a PCC rule, and the PCC rule further includes first indication information and an SDF template.

[0141] Specifically, in a possible implementation, the first indication information may also indicate the length information of the first padding redundant data. Specifically, the length information of the first padding redundant data may be the length of the padding redundant data in the payload field of the message.

[0142] Specifically, in a possible implementation, the first indication information may also indicate the location information of the first filling redundant data. Specifically, the location information of the first filling redundant data may be the starting position and the ending position of the filling redundant data in the payload field of the message.

[0143] Specifically, in a possible implementation, the first indication information may also indicate the length information of the payload data of the message. Specifically, the length information of the payload data of the message may be the length of the payload data in the payload field of the message.

[0144] Specifically, in a possible implementation, the first indication information may also indicate the position information of the payload data of the message. Specifically, the position information of the payload data of the message may be the starting position and the ending position of the payload data in the payload field of the message.

[0145] It should be noted that, in actual application, the first indication information may include one or more of the length information of the padding redundant data, the location information of the padding redundant data, the length information of the effective load data, or the location information of the effective load data. When the first indication information includes one or more of the above information, the device receiving the first indication information may add or delete the padding redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information may also include an indication to add or delete the padding redundant data, which is used to instruct the device receiving the first indication information to add or delete the padding redundant data according to the first indication information when receiving the service message. Alternatively, in a possible implementation, the first indication information only includes an indication to add or delete the padding redundant data, and the device receiving the first indication information adds or deletes the padding redundant data according to the first indication information when receiving the service message.

[0146] After the session management network element SMF receives the policy update message, SMF performs session management according to the policy update message.

[0147] Specifically, SMF binds the policy and charging control (PCC) rules obtained from the policy update message to an existing QoS flow (QoS Flow), or generates a new QoS Flow by deriving QoS parameters based on the parameters in the PCC rules and then binds the PCC rules to the QoS Flow. Among them, the PCC rules include the first indication information and the SDF template. Binding the PCC rules to the QoS Flow can be understood as applying the PCC rules to the QoS Flow, that is, one or more service flows corresponding to the SDF template in the PCC rules are bound to the QoS Flow. If multiple service flows are bound to the same QoS Flow, these service flows have the same QoS requirements, and the padding redundant data length information included in the first indication information is the same.

[0148] In step 204, the session management network element sends an N4 session modification request to the user plane network element.

[0149] The session management network element SMF obtains the first indication information and the SDF template in the policy update message, and generates a packet detection rule (Packet Detection Rule, PDR) and a forwarding action rule (Forwarding Action Rule, FAR) according to the PCC rule in the policy update message. The PDR includes the SDF template. Among them, the SDF template can also be replaced by an application identifier and a packet filter set (Packet Filer Set), and the packet filter set includes the service filtering information in the SDF template. In a possible implementation, the FAR includes the first indication information. The SMF sends the PDR and FAR to the user plane network element UPF through the N4 session modification request message. The UPF uses the PDR to detect the received data packet. When it matches the service filtering information, it performs the corresponding packet forwarding action according to the first indication information in the FAR, such as deleting or adding redundant padding data. In one possible implementation, when the service corresponding to the packet filter in the SDF template is a downlink service, the first indication information included in the FAR includes an indication for deleting redundant padding data; when the service corresponding to the packet filter in the SDF template is an uplink service, the first indication information included in the FAR includes an indication for adding redundant padding data.

[0150] In step 205, the session management network element sends an N1 interface session management message to the user equipment.

[0151] The session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS rule (QoS Rule) according to the PCC rule in the policy update message. The QoS rule includes a QoS Flow identifier and a packet filter set (Packet Filer Set) corresponding to the first indication information and the QoS Flow identifier. The SMF sends the QoS rule to the user equipment UE through the N1 interface session management information. Optionally, the first indication information may not be included in the QoS Rule, that is, the session management network element sends the first indication information and the corresponding QoS Flow identifier to the user equipment through the N1 interface session management message, indicating to the user equipment that the first indication information is for the QoS Flow identified by the QoS Flow identifier.

[0152] It should be noted that the N1 interface session management message here is sent by SMF to the wireless access network device through AMF, and then sent to the user device through the wireless access network device. The N1 interface session management message specifically carries the PDU session modification command, that is, the N1 interface session management message includes the PDU session modification command; the PDU session modification command includes the QoS Rule, and the QoS Rule includes the QoS Flow identifier and the first indication information, or the QoS Flow identifier and the first indication information included in the PDU session modification command, optionally, also includes the QoS Rule.

[0153] In one possible implementation, when the service corresponding to the packet filter in the packet filter set carried in the QoS Rule is an uplink service, the first indication information includes an indication for deleting the filling redundant data; when the service corresponding to the packet filter in the packet filter set carried in the QoS Rule is a downlink service, the first indication information includes an indication for adding the filling redundant data.

[0154] There is no limitation on the execution order of step 204 and step 205. It can be that after step 203, SMF initiates the PDU session modification process, and in the PDU session modification process, step 205 is executed first, and then step 204; it can also be that step 204 is executed first, and then step 205; it can also be that step 204 and step 205 are executed at the same time, which is not limited here.

[0155] It should be noted that the first indication information included in step 204 and step 205 may be different. For example, the first indication information in step 204 is used to indicate deletion of padding redundant data, and the first indication information in step 205 is used to indicate addition of padding redundant data; or, the first indication information in step 204 is used to indicate addition of padding redundant data, and the first indication information in step 205 is used to indicate deletion of padding redundant data.

[0156] In step 206, the user plane network element receives the first message.

[0157] The first message is an Ethernet message. When downlink data is transmitted, the user-plane network element will receive one or more downlink first messages, and the one or more first messages correspond to a QoS Flow identifier.

[0158] Specifically, in a possible implementation, the first message is in Ethernet II frame format. Figure 8As shown, the first message includes a preamble field, a start frame delimiter (SFD) field, a destination MAC address field, a source MAC address field, a type field, a data payload field, and a frame check sequence (FCS) field. The data payload field includes a valid payload field and a padding field.

[0159] Specifically, in a possible implementation, the first message is in Ethernet IEEE 802.3 frame format. Fig. 9 As shown, the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a length field, a logical link control (LLC) field, a data payload field, and an FCS field. The data payload field includes a payload field and a padding field.

[0160] In step 207, the user plane network element deletes the padding redundant data in the first message.

[0161] After receiving the first message, the user plane network element deletes the padding redundant data in the first message.

[0162] Specifically, the user plane network element detects the received first message, determines that the first message matches the PDR received in step 204 according to the PDR received in step 204, and deletes the padding redundant data according to the first indication information in the FAR received in step 204.

[0163] Specifically, when the first message is in Ethernet II frame format, the user plane network element deletes the padding redundant data in the first message according to the first indication information.

[0164] Specifically, when the first indication information includes length information of the padding redundant data, the user plane network element deletes the padding redundant data of the payload part in the first message according to the length information of the padding redundant data. Figure 8 or Fig. 9 The frame format in the first indication information can determine the end position of the padded redundant data, and then the starting position of the padded redundant data can be determined according to the length of the padded redundant data contained in the first indication information, and then the padded redundant data can be deleted according to the starting position and the end position.

[0165] Alternatively, when the first indication information includes location information of the redundant data to be filled, the user plane network element finds the starting and ending positions of the redundant data to be filled from the payload part of the first message according to the location information of the redundant data to be filled, and deletes the data from the starting position to the ending position.

[0166] Alternatively, when the first indication information includes the length information of the effective load data, the user plane network element deletes the data other than the effective load data in the load part of the first message according to the length information of the effective load data, that is, deletes the padding redundant data. Figure 8 or Fig. 9 The frame format in the first indication information can determine the end position of the padded redundant data, and then the starting position of the padded redundant data can be determined according to the length of the padded redundant data contained in the first indication information, and then the padded redundant data can be deleted according to the starting position and the end position.

[0167] Alternatively, when the first indication information includes the location information of the payload data, the user-side network element finds the starting position and ending position of the payload data from the payload part of the first message based on the location information of the payload data, and deletes the data outside the starting position to the end position of the payload data, that is, deletes the padding redundant data.

[0168] Specifically, when the first message is in Ethernet IEEE802.3 frame format, the user plane network element can determine the position of the redundant data to be filled in the first message according to the first indication information, and can also determine the position of the redundant data to be filled in the first message according to the first indication information. Fig. 9 The length field shown determines the position of the padding redundant data in the first message, and then deletes the padding redundant data in the first message according to the position of the padding redundant data in the first message. Specifically, according to the Length field, the data in the payload part of the first message except the effective load data corresponding to the Length field is deleted, that is, the padding redundant data is deleted.

[0169] It should be noted that, in actual application, the first indication information may only include one or more of the length information of the padded redundant data, the location information of the padded redundant data, the length information of the effective load data, or the location information of the effective load data. When the first indication information includes one or more of the above information, the user plane network element may delete the padded redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information may also include an indication to delete the padded redundant data, which is used to instruct the user plane network element to delete the padded redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information only includes an indication to delete the padded redundant data, and the user plane network element deletes the padded redundant data according to the first indication information.

[0170] In step 208, the user plane network element generates a second message, and sends the second message to the wireless access network device.

[0171] After deleting the redundant padding data of the first message, the user plane network element generates a second message, the payload data in the second message is the effective payload data after deleting the redundant padding data in the first message, and sends the second message to the wireless access network device.

[0172] Specifically, after the user plane network element deletes the padding redundant data of the first message, the first message from which the padding redundant data has been deleted is encapsulated according to the N3 tunnel protocol to obtain a second message. Specifically, in a possible implementation, the N3 tunnel protocol here may be a general packet radioservice tunneling protocol user plane (GTP-U) protocol. It can be understood that in actual application, other tunnel protocols may also be used, which are not specifically limited here. Optionally, before the user plane network element encapsulates the first message from which the padding redundant data has been deleted according to the N3 tunnel protocol to obtain the second message, the user plane network element also deletes the preamble field, SFD field, and FCS field in the first message. That is, the preamble field, SFD field, and FCS field in the first message are not transmitted between the user plane network element, the radio access network device, and the user device.

[0173] For example, if the first message format is Figure 8 If the Ethernet II frame format is shown in FIG. 1 and the first message includes a padding field, the format of the second message is Fig.10 As shown, the destination MAC address field, source MAC address field, type field and payload field of the second message are the same as the corresponding fields in the first message; and the N3 tunnel protocol header field includes Fig.10 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.10 The FSC field in the first message is different from that in the first message. Fig.10 The FCS field in the N3 MAC frame is calculated by the user plane network element based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.10 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.

[0174] If the first message format is Fig. 9 When the IEEE 802.3 frame format is shown, the format of the second message is Fig.11 As shown, the destination MAC address field, source MAC address field, Length field, LLC field and payload field of the second message are the same as the corresponding fields in the first message; and the N3 tunnel protocol header field includes Fig.11 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.11 The FSC field in the first message is different from that in the first message. Fig.11 The FCS field in the N3 MAC frame is calculated by the user plane network element based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.11 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field and payload field.

[0175] It should be noted that in the application scenario of small packet transmission, after the user plane network element deletes the redundant padding data of the first message, the data length of the entire message may be less than the minimum Ethernet frame length, for example, less than 64 bytes. Fig.10 or Fig.11 After the protocol header of the N3 tunnel protocol shown in , the data length of the second message will be greater than or equal to 64 bytes, so the Ethernet message that complies with the protocol must meet the Ethernet minimum frame length requirement. Among them, the data length of the first message is Figure 8 or Fig. 9 The message format shown in does not include the sum of the lengths of the remaining parts of the preamble field, the SFD field, and the FCS field. The data length of the second message is Fig.10 or Fig.11 The message format shown in does not include the sum of the lengths of the N3 MAC header field and the remaining part of the FCS field.

[0176] In the industrial packet scenario, the N3 tunnel protocol may adopt a simpler protocol stack. Fig.10 or Fig.11 The UDP, IP and GTP-U protocol layers shown in FIG. 1 are used, and other protocol layers are used, such as only the GTP-U layer is used, that is, the second message does not include Fig.10 or Fig.11 The P header field and UDP header field shown in, or the second message does not include Fig.10 or Fig.11The IP header field, UDP header field, and GTP-U header field shown in the figure, the data length of the second message may be less than 64 bytes. In this case, there are two ways:

[0177] Method 1: The user-side network element encapsulates the third message according to the N3 tunnel protocol to obtain a fourth message. If the data length of the fourth message is less than the minimum frame length of Ethernet, the tunnel protocol padding redundant data is added to the N3 tunnel protocol header of the fourth message to generate a second message. The data length of the second message is greater than or equal to the minimum frame length of Ethernet.

[0178] Method 2: If the user-plane network element determines that the data length of the encapsulated message obtained by encapsulating the third message according to the N3 tunnel protocol is less than the minimum frame length of Ethernet, the user-plane network element encapsulates the third message according to the N3 tunnel protocol to obtain an encapsulated message, and adds tunnel protocol padding redundant data to the N3 tunnel protocol header of the encapsulated message to generate a second message, and the data length of the second message is greater than or equal to the minimum frame length of Ethernet.

[0179] Optionally, before performing the operation of the above-mentioned method 1 or method 2, the user plane network element receives third indication information from the session management network element, and the third indication information is used to instruct the user plane network element to perform an Ethernet frame length check on the message to be sent in the N3 tunnel, and when the Ethernet frame length of the message is less than 64 bytes, add tunnel protocol padding redundant data. Specifically, in the step of the session management network element sending an N4 session modification request to the user plane network element, the third indication information can be carried in the N4 session modification request.

[0180] The third message in the above-mentioned method 1 and method 2 is the message after the padding redundant data is deleted from the first message. It should be noted that after the user-side network element deletes the padding redundant data in the first message, it can first generate a third message, and then generate a fourth message or the second message based on the third generated message. It can also not include the process of generating the third message, and directly operate on the first message after deleting the padding redundant data.

[0181] It should be noted that the N3 tunnel protocol refers to the tunnel protocol between the user plane network element and the access network node. In the present invention, the N3 tunnel protocol can be replaced by other tunnel protocols that may be used for transmitting data between the user plane network element and the access network node.

[0182] In step 209, the wireless access network device sends a fifth message to the user equipment.

[0183] After receiving the second message sent by the user plane network element, the wireless access network device removes the N3 tunnel protocol header in the second message, adds an air interface protocol header, generates a fifth message, and sends the fifth message to the user equipment.

[0184] For example, if the first message format is Figure 8 The Ethernet II frame format shown in Figure 1 shows the format of the fifth message. Fig.12 As shown, the destination MAC address field, source MAC address field, type field, and payload field of the fifth message are the same as the corresponding fields in the second message; Fig.12 The AN protocol header is also called an air interface protocol header, and may include, for example, a packet data convergence protocol (PDCP) header, a radio link control (RLC) header, and a MAC header.

[0185] If the first message format is Fig. 9 The IEEE 802.3 frame format shown in FIG. 1 is as follows: Figure 7 As shown, the destination MAC address field, source MAC address field, Length field, LLC field, and payload field of the fifth message are the same as the corresponding fields in the second message; Figure 7 The AN protocol header is also called an air interface protocol header, and can include, for example, a PDCP header, an RLC header, and a MAC header.

[0186] It should be noted that the way in which the wireless access network device sends a message to the user equipment is an air interface transmission method, which is not subject to the requirements of the minimum frame length of Ethernet. Therefore, after the N3 tunnel protocol header is stripped, the second message has a length of less than 64 bytes, that is, the length of the fifth message is less than 64 bytes and can also be transmitted. And because in the previous step, the padding redundant data of the payload part of the first message has been deleted, that is, the payload part of the fifth message does not include the padding redundant data, so during air interface transmission, air interface resources can be saved.

[0187] In a possible implementation manner, after the user equipment receives the fifth message, the application layer of the user equipment may directly obtain the payload data portion of the fifth message for use.

[0188] Alternatively, in a possible implementation, when the user device is an intermediate node in the network and needs to continue forwarding Ethernet frames to the next-hop node, the user device supplements the payload portion of the fifth message with redundant data to generate a sixth message, so that the data length of the sixth message is greater than or equal to 64 bytes. Optionally, in a possible implementation, if the user-plane network element encapsulates the first message from which the redundant data is deleted according to the N3 tunnel protocol to obtain the second message, and the user-plane network element also deletes the preamble field, SFD field, and FCS field in the first message, the user device also needs to supplement other fields to generate the sixth message, such as the FCS field, the preamble field, and the SFD field, which are not specifically limited here. The format of the sixth message may be the same as the format of the first message, that is, if the first message is Figure 8 The Ethernet II frame format shown in FIG. 1 is an Ethernet frame of the Ethernet II type. If the first message format is Fig. 9 3 frame format, the sixth message is also an IEEE 802.3 type Ethernet frame. Preferably, after the redundant data is added, the data length of the sixth message is the same as the data length of the first message. The data length of the first message or the sixth message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field in the sixth message. Optionally, the sixth message is the same as the first message.

[0189] Specifically, the user equipment may fill each bit of the redundant data in the sixth message with 0. It is understandable that the filling may be performed in other ways, as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0190] Specifically, in a possible implementation, the user equipment may supplement the redundant data in the payload part of the fifth message according to the first indication information to generate a sixth message, so that the data length of the sixth message is greater than or equal to 64 bytes.

[0191] Specifically, when the first indication information includes the length information of the padding redundant data, the user equipment fills the padding redundant data into the payload part of the fifth message according to the length information of the padding redundant data.

[0192] Alternatively, when the first indication information includes location information of the filled redundant data, the user equipment finds the starting position and the ending position of the filled redundant data to be filled from the payload part of the fifth message according to the location information of the filled redundant data, and fills the filled redundant data into the corresponding position.

[0193] Alternatively, when the first indication information includes the length information of the effective load data, the user equipment fills the redundant data into the payload part of the fifth message according to the length information of the effective load data.

[0194] Alternatively, when the first indication information includes the location information of the payload data, the user equipment finds the starting position and the ending position of the payload data from the payload part of the fifth message according to the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0195] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the user equipment determines to add padding redundant data based on the first indication information, and fills the fifth message with the padding redundant data based on the Ethernet minimum frame length specified by the protocol.

[0196] In step 210, the user equipment receives a seventh message, where the seventh message is an uplink Ethernet message.

[0197] The seventh message is an Ethernet message. When uplink data is transmitted, the user equipment obtains one or more uplink Ethernet messages, wherein the uplink Ethernet message is the seventh message. When the user equipment has a previous hop node, the user equipment receives the uplink Ethernet message sent by the previous hop node. When the user equipment does not have a previous hop node, the user equipment generates an uplink Ethernet message.

[0198] Specifically, in a possible implementation, the uplink Ethernet message is in Ethernet II frame format. Figure 8 As shown, the uplink Ethernet message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0199] Specifically, in a possible implementation, the uplink Ethernet message is in Ethernet IEEE802.3 frame format. Fig. 9 As shown, the uplink Ethernet message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a payload length field, an LLC field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0200] In step 211, the user equipment deletes the padding redundant data in the seventh message.

[0201] After obtaining the seventh message, the user equipment deletes the padding redundant data in the seventh message.

[0202] Specifically, when the seventh message is in Ethernet II frame format, the user equipment deletes the padding redundant data in the seventh message according to the first indication information.

[0203] Specifically, when the first indication information includes the length information of the padding redundant data, the user equipment deletes the padding redundant data in the payload part of the seventh message according to the length information of the padding redundant data.

[0204] Alternatively, when the first indication information includes location information of the redundant data to be filled, the user equipment finds the starting and ending positions of the redundant data to be filled from the payload part of the seventh message according to the location information of the redundant data to be filled, and deletes the data from the starting position to the ending position.

[0205] Alternatively, when the first indication information includes the length information of the effective load data, the user equipment deletes the data except the effective load data in the payload part of the uplink Ethernet message according to the length information of the effective load data, that is, deletes the padding redundant data.

[0206] Alternatively, when the first indication information includes the location information of the payload data, the user equipment finds the starting position and the ending position of the payload data from the payload part of the seventh message based on the location information of the payload data, and deletes the data outside the starting position to the ending position of the payload data, that is, deletes the padding redundant data.

[0207] Specifically, when the seventh message is in Ethernet IEEE802.3 frame format, the user equipment element can determine the position of the padded redundant data in the seventh message according to the first indication information, and can also determine the position of the padded redundant data in the seventh message according to the length field, and delete the padded redundant data in the seventh message according to the position of the padded redundant data in the seventh message. Specifically, according to the Length field, the data in the payload part of the seventh message except the effective load data corresponding to the Length field is deleted, that is, the padded redundant data of the seventh message is deleted.

[0208] In step 212, the user equipment generates an eighth message, and sends the eighth message to the wireless network device.

[0209] After deleting the padding redundant data of the seventh message, the user equipment generates an eighth message, and the payload data in the eighth message is the effective payload data after the padding redundant data is deleted in the seventh message.

[0210] Specifically, after the user equipment deletes the redundant padding data of the seventh message, it encapsulates the seventh message from which the redundant padding data has been deleted according to the air interface protocol to obtain the eighth message.

[0211] For example, if the seventh message format is Figure 8 The Ethernet II frame format shown in FIG. 1 and the seventh message includes a padding field, the format of the eighth message is Fig.12 As shown, the destination MAC address field, source MAC address field, type field, and payload field of the eighth message are the same as the corresponding fields in the received seventh message; Fig.12 The AN protocol header is also called an air interface protocol header, and can include, for example, a PDCP header, an RLC header, and a MAC header.

[0212] If the seventh message format is Fig. 9 When the IEEE802.3 frame format is shown, the format of the eighth message is Figure 7 As shown, the destination MAC address field, source MAC address field, Length field, LLC field, and payload field of the eighth message are the same as the corresponding fields in the received seventh message; Figure 7 The AN protocol header is also called an air interface protocol header, and can include, for example, a PDCP header, an RLC header, and a MAC header.

[0213] After generating the eighth message, the user equipment sends the eighth message to the wireless access network device.

[0214] Optionally, in addition to deleting the padding redundant data in the seventh message, the user equipment also deletes the preamble field, the SFD field, and the FCS field in the seventh message. That is, the preamble field, the SFD field, and the FCS field in the seventh message are not transmitted between the user equipment, the radio access network device, and the user plane network element.

[0215] It should be noted that the mode in which the user equipment sends a message to the wireless access network device is an air interface transmission mode, which is not subject to the requirements of the minimum frame length of Ethernet, so the data length of the uplink Ethernet message is less than 64 bytes and can also be transmitted. And because in the previous step, the padding redundant data of the payload part in the seventh message has been deleted, that is, the payload part of the eighth message does not include the padding redundant data, so during air interface transmission, air interface resources can be saved.

[0216] In step 213, the wireless access network device sends a ninth message to the user plane network element.

[0217] After receiving the eighth message sent by the user equipment, the wireless access network device removes the air interface protocol header in the eighth message, adds an N3 tunnel protocol header, generates a ninth message, and sends the ninth message to the user plane network element.

[0218] For example, if the seventh message format is Figure 8 The Ethernet II frame format shown in Figure 1 shows the format of the ninth message. Fig.10 As shown, the destination MAC address field, source MAC address field, type field and payload field of the ninth message are the same as the corresponding fields in the eighth message; and the N3 tunnel protocol header field includes Fig.10 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.10 The FSC field in the first message is different from that in the first message. Fig.10 The FCS field in the N3 MAC frame is calculated by the wireless access network device based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.10 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.

[0219] If the seventh message format is Fig. 9 When the IEEE 802.3 frame format is shown, the format of the ninth message is Fig.11 As shown, the destination MAC address field, source MAC address field, Length field, LLC field and payload field of the ninth message are the same as the corresponding fields in the eighth message; and the N3 tunnel protocol header field includes Fig.11 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.11 The FSC field in the first message is different from that in the first message. Fig.11 The FCS field in the N3 MAC frame is calculated by the wireless access network device based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.11 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field and payload field.

[0220] It should be noted that in the application scenario of industrial packet transmission, after the user device deletes the redundant padding data of the seventh message, the data length of the eighth message may be less than the minimum Ethernet frame length, for example, less than 64 bytes. Fig.10 or Fig.11After the protocol header of the N3 tunnel protocol shown in , the data length of the ninth message may be greater than or equal to 64 bytes, so the Ethernet message that complies with the protocol must meet the minimum frame length requirement of Ethernet. Among them, the data length of the seventh message is Figure 8 or Fig. 9 The message format shown in does not include the sum of the lengths of the remaining parts of the preamble field, the SFD field, and the FCS field. The data length of the ninth message is Fig.10 or Fig.11 The message format shown in does not include the sum of the lengths of the N3 MAC header field and the remaining part of the FCS field.

[0221] Specifically, the wireless access network device encapsulates the eighth message according to the N3 tunnel protocol to obtain the ninth message. Specifically, in a possible implementation, the N3 tunnel protocol here may be the GTP-U protocol. It is understandable that in actual application, it may also be other N3 tunnel protocols, which are not limited here. For example, in an industrial scenario, the N3 tunnel protocol may adopt a simpler protocol stack. For example, if the N3 tunnel protocol does not adopt Fig.10 or Fig.11 The UDP, IP and GTP-U protocol layers shown in FIG. 1 are used, and other protocol layers are used, such as only the GTP-U layer is used, that is, the ninth message does not include Fig.10 or Fig.11 The IP header fields and UDP header fields shown in, or the second message does not include Fig.10 or Fig.11 The IP header field, UDP header field, and GTP-U header field shown in the figure, the data length of the ninth message may be less than 64 bytes. In this case, there are two ways:

[0222] Method 1: The wireless access network device encapsulates the eighth message according to the N3 tunnel protocol to obtain the tenth message. If the data length of the tenth message is less than the minimum frame length of Ethernet, the tunnel protocol padding redundant data is added to the N3 tunnel protocol header of the tenth message to generate a ninth message. The data length of the ninth message is greater than or equal to the minimum frame length of Ethernet.

[0223] Method 2: If the wireless access network device determines that the data length of the encapsulated message obtained by encapsulating the eighth message according to the N3 tunnel protocol is less than the minimum frame length of Ethernet, the user-side network element encapsulates the eighth message according to the N3 tunnel protocol to obtain an encapsulated message, and adds tunnel protocol padding redundant data to the N3 tunnel protocol header of the encapsulated message to generate a ninth message, and the data length of the ninth message is greater than or equal to the minimum frame length of Ethernet.

[0224] Optionally, before performing the operation of the above-mentioned method 1 or method 2, the wireless access network device receives second indication information from the session management network element, where the second indication information is used to instruct the wireless access network device to perform an Ethernet frame length check on the message to be sent in the N3 tunnel, and when the Ethernet frame length of the message is less than 64 bytes, add tunnel protocol padding redundant data. Specifically, the second indication information can be carried when the session management network element sends a control plane message to the wireless access network device.

[0225] That is to say, in the above-mentioned method 1, the wireless access network device first generates the tenth message, and then generates the ninth message according to the tenth generated message. In the method 2, the process of generating the tenth message may not be included, and the ninth message may be directly generated according to the eighth message.

[0226] It should be noted that the N3 tunnel protocol refers to the tunnel protocol between the user plane network element and the access network node. In the present invention, the N3 tunnel protocol can be replaced by other tunnel protocols that may be used for transmitting data between the user plane network element and the access network node.

[0227] In step 214, the user plane network element adds padding redundant data of the ninth message.

[0228] After receiving the ninth message, the user plane network element removes the N3 tunnel protocol header and adds padding redundant data to generate an eleventh message, so that the data length of the eleventh message is greater than or equal to 64 bytes. Optionally,

[0229] If the user equipment deletes the preamble field, SFD field and FCS field in the seventh message in addition to the padding redundant data in the seventh message, the user plane network element also adds other fields to generate the eleventh message, such as the FCS field, the preamble field and the SFD field, which are not limited here. The format of the eleventh message is the same as that of the seventh message, that is, if the seventh message is Figure 8 The Ethernet II frame format shown in FIG. 11 is also an Ethernet frame of Ethernet II type. If the format of the seventh message is Fig. 9 , the eleventh message is also an IEEE 802.3 type Ethernet frame. Preferably, after the redundant data is added, the data length of the eleventh message is the same as the data length of the seventh message. The data length of the seventh message or the eleventh message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field. Optionally, the eleventh message is the same as the seventh message.

[0230] Specifically, the user equipment may fill each bit of the redundant data in the eleventh message with 0. It is understandable that filling may also be performed in other ways, as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0231] Specifically, in a possible implementation, the user plane network element may supplement the payload portion of the ninth message with the padding redundant data according to the first indication information to generate the eleventh message, so that the data length of the eleventh message is greater than or equal to 64 bytes. Specifically, when the first indication information includes length information of the padding redundant data, the user plane network element fills the padding redundant data into the payload portion of the ninth message according to the length information of the padding redundant data.

[0232] Alternatively, when the first indication information includes location information of the filling redundant data, the user-side network element finds the starting and ending positions of the filling redundant data to be filled from the payload part of the ninth message according to the location information of the filling redundant data, and fills the filling redundant data into the corresponding position.

[0233] Alternatively, when the first indication information includes the length information of the effective load data, the user plane network element fills the redundant data into the payload part of the ninth message according to the length information of the effective load data.

[0234] Alternatively, when the first indication information includes the location information of the payload data, the user-plane network element finds the starting and ending positions of the payload data from the payload part of the ninth message based on the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0235] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the user-side network element determines to add padding redundant data based on the first indication information, and fills the ninth message with padding redundant data based on the Ethernet minimum frame length specified by the protocol.

[0236] In step 215, the user plane network element sends an eleventh message.

[0237] The user plane network element sends the eleventh message to the next hop node.

[0238] In this embodiment, steps 206 to 209 are application scenarios for sending downlink messages, and steps 210 to 215 are application scenarios for sending uplink messages. In actual application, steps 206 to 209 can be implemented separately, and steps 210 to 215 can also be implemented separately or in combination, which is not limited here.

[0239] In an embodiment of the present application, the user plane device deletes the padding redundant data in the received downlink message so that the downlink message transmitted to the user device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0240] In an embodiment of the present application, the user equipment deletes the padding redundant data in the received uplink message so that the uplink message transmitted to the wireless access network device over the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0241] See also Figure 3 , which is another flow chart of an embodiment of the present application.

[0242] In step 301, a user equipment establishes a PDU session.

[0243] In step 302, the application function network element sends an AF request message to the policy control network element.

[0244] In step 303, the policy control network element sends a policy update message to the session management network element.

[0245] In step 304, the session management network element sends an N4 session modification request to the user plane network element.

[0246] In this embodiment, steps 301 to 304 are the same as those described above. Figure 2 The methods performed in step 201 to step 204 in the illustrated embodiment are similar and will not be described in detail herein.

[0247] In step 305, the session management network element sends an N2 interface session management message to the wireless access network device.

[0248] The session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS configuration file (QoS Profile) corresponding to the QoS Flow according to the PCC rule in the policy update message, and the QoS Profile rule includes the first indication information. The SMF sends the QoS Profile and the corresponding QosFlow identifier to the wireless access network device through the N2 interface session management message. Optionally, the first indication information may not be included in the QoS Profile, that is, the session management network element sends the first indication information and the corresponding QoS Flow identifier to the wireless access network device through the N2 interface session management message, indicating that the wireless access network device that the first indication information is for the QoS Flow identified by the QoS Flow identifier.

[0249] It should be noted that the N2 interface session management message here is sent by SMF to the wireless access network device through AMF.

[0250] There is no limitation on the execution order of step 304 and step 305. It can be that after step 303, SMF initiates the PDU session modification process, and in the PDU session modification process, step 305 is executed first, and then step 304; it can also be that step 304 is executed first, and then step 305; it can also be that step 304 and step 305 are executed at the same time, which is not limited here.

[0251] It should be noted that the first indication information included in step 304 and step 305 may be different. For example, the first indication information in step 304 is used to indicate deletion of padding redundant data, and the first indication information in step 305 is used to indicate addition of padding redundant data; or, the first indication information in step 304 is used to indicate addition of padding redundant data, and the first indication information in step 305 is used to indicate deletion of padding redundant data.

[0252] In step 306, the radio access network device sends a radio resource control (RRC) reconfiguration signaling to the user equipment.

[0253] The wireless access network device obtains the first indication information and the QoS Flow identifier in the N2 interface session management message, carries the first indication information and the QoS Flow identifier in the RRC reconfiguration signaling, and sends the RRC reconfiguration signaling to the user equipment.

[0254] In step 307, the user plane network element receives the first message.

[0255] In step 308, the user plane network element deletes the padding redundant data in the first message.

[0256] In step 309, the user plane network element generates a second message, and sends the second message to the wireless access network device.

[0257] In step 310, the wireless access network device sends a fifth message to the user equipment.

[0258] In step 311, the user equipment receives a seventh message, where the seventh message is an uplink Ethernet message.

[0259] In step 312, the user equipment deletes the padding redundant data in the seventh message.

[0260] In step 313, the user equipment generates an eighth message, and sends the eighth message to the wireless network device.

[0261] In step 314, the wireless access network device sends a ninth message to the user plane network element.

[0262] In step 315, the user plane network element adds padding redundant data of the ninth message.

[0263] In step 316, the user plane network element sends an eleventh message.

[0264] In this embodiment, steps 307 to 316 are the same as those described above. Figure 2 The methods performed in step 206 to step 215 in the illustrated embodiment are similar and will not be described in detail here.

[0265] In this embodiment, steps 307 to 310 are application scenarios for sending downlink messages, and steps 311 to 316 are application scenarios for sending uplink messages. In actual application, steps 307 to 310 can be implemented separately, and steps 311 to 316 can also be implemented separately or in combination, which is not limited here.

[0266] In an embodiment of the present application, the user plane device deletes the padding redundant data in the received downlink message so that the downlink message transmitted to the user device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0267] In an embodiment of the present application, the user equipment deletes the padding redundant data in the received uplink message so that the uplink message transmitted to the wireless access network device over the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0268] See also Figure 4 , is another flow chart of the data transmission method provided in an embodiment of the present application.

[0269] In step 401, the user equipment establishes a PDU session.

[0270] In step 402, the application function network element sends an AF request message to the policy control network element.

[0271] In step 403, the policy control network element sends a policy update message to the session management network element.

[0272] In this embodiment, steps 401 to 403 are the same as those described above. Figure 3 The methods performed in step 301 to step 303 in the illustrated embodiment are similar and will not be described in detail here.

[0273] In step 404, the session management network element sends an N2 interface session management message to the wireless access network device.

[0274] The session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS configuration file (QoS Profile) corresponding to the QoS Flow according to the PCC rule in the policy update message, and the QoS Profile rule includes the first indication information. The SMF sends the QoS Profile and the corresponding QosFlow identifier to the wireless access network device through the N2 interface session management message. Optionally, the first indication information may not be included in the QoS Profile, that is, the session management network element sends the first indication information and the corresponding QoS Flow identifier to the wireless access network device through the N2 interface session management message, indicating that the wireless access network device that the first indication information is for the QoS Flow identified by the QoS Flow identifier.

[0275] It should be noted that the N2 interface session management message here is sent by SMF to the wireless access network device through AMF.

[0276] In step 405, the session management network element sends an N1 interface session management message to the user equipment.

[0277] The session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS rule (QoS Rule) according to the PCC rule in the policy update message. The QoS rule includes a QoS Flow identifier and a packet filter set corresponding to the first indication information and the QoS Flow identifier. The SMF sends the QoS rule to the user equipment UE through the N1 interface session management information. Optionally, the first indication information may not be included in the QoS Rule, that is, the session management network element sends the first indication information and the corresponding QoS Flow identifier to the user equipment through the N1 interface session management message, indicating to the user equipment that the first indication information is for the QoS Flow identified by the QoS Flow identifier.

[0278] It should be noted that the N1 interface session management message here is sent by SMF to the wireless access network device through AMF, and then sent to the user device through the wireless access network device. The N1 interface session management message specifically carries the PDU session modification command, that is, the N1 interface session management message includes the PDU session modification command; the PDU session modification command includes the QoS Rule, and the QoS Rule includes the QoS Flow identifier and the first indication information, or the QoS Flow identifier and the first indication information included in the PDU session modification command, optionally, also includes the QoS Rule.

[0279] There is no limitation on the execution order of step 404 and step 405. It can be that after step 403, SMF initiates the PDU session modification process, and in the PDU session modification process, step 405 is executed first, and then step 404; or step 404 is executed first, and then step 405; or step 404 and step 405 are executed at the same time, which is not limited here.

[0280] It should be noted that the first indication information included in step 404 and step 405 may be different. For example, the first indication information in step 404 is used to indicate deletion of padding redundant data, and the first indication information in step 405 is used to indicate addition of padding redundant data; or, the first indication information in step 404 is used to indicate addition of padding redundant data, and the first indication information in step 405 is used to indicate deletion of padding redundant data.

[0281] It should be noted that, in this embodiment, the first indication information and the QoS Flow identifier may also be sent to the user equipment through the radio access network device RAN, that is, Figure 3 The method performed in step 306 in the illustrated embodiment is similar and will not be described in detail herein. When the first indication information and the QoS Flow identifier corresponding to the SDF template are sent to the user equipment via the RAN, step 405 is not performed.

[0282] In step 406, the user plane network element receives the first message.

[0283] In step 407, the user plane network element sends a twelfth message to the wireless access network device.

[0284] After receiving the first message, the user plane network element encapsulates the first message according to the N3 tunnel protocol to obtain the twelfth message. Specifically, in a possible implementation, the N3 tunnel protocol here can be the GTP-U protocol. It can be understood that in actual application, it can also be other tunnel protocols, which are not specifically limited here.

[0285] For example, if the first message format is Figure 8 If the Ethernet II frame format is shown in FIG. 1 and the first message includes a padding field, the format of the twelfth message is Fig.10 As shown, the destination MAC address field, source MAC address field, type field and payload field of the twelfth message are the same as the corresponding fields in the first message; and the N3 tunnel protocol header field includes Fig.10 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.10 The FSC field in the first message is different from that in the first message. Fig.10 The FCS field in the N3 MAC frame is calculated by the user plane network element based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.10 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.

[0286] If the first message format is Fig. 9 When the IEEE 802.3 frame format is shown, the format of the twelfth message is Fig.11 As shown, the destination MAC address field, source MAC address field, Length field, LLC field and payload field of the twelfth message are the same as the corresponding fields in the first message; and the N3 tunnel protocol header field includes Fig.11 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.11 The FSC field in the first message is different from that in the first message. Fig.11 The FCS field in the N3 MAC frame is calculated by the user plane network element based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.11 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field and payload field.

[0287] Optionally, before the user plane network element encapsulates the first message according to the N3 tunnel protocol to obtain the twelfth message, the user plane network element also deletes the preamble field, the SFD field, and the FCS field in the first message. That is, the preamble field, the SFD field, and the FCS field in the first message are not transmitted between the user plane network element, the wireless access network device, and the user equipment.

[0288] It should be noted that the N3 tunnel protocol refers to the tunnel protocol between the user plane network element and the access network node. In the present invention, the N3 tunnel protocol can be replaced by other tunnel protocols that may be used for transmitting data between the user plane network element and the access network node.

[0289] In step 408, the wireless access network device deletes the padding redundant data.

[0290] After receiving the twelfth message, the wireless access network device strips the N3 tunnel protocol header in the twelfth message and deletes the padding redundant data in the twelfth message.

[0291] Specifically, after receiving the twelfth message, the wireless access network device deletes the padding redundant data according to the first indication information received in step 404 .

[0292] Specifically, when the first message is in Ethernet II frame format, the wireless access network device deletes the padding redundant data in the twelfth message according to the first indication information.

[0293] Specifically, when the first indication information includes the length information of the padding redundant data, the wireless access network device deletes the padding redundant data in the payload part of the twelfth message according to the length information of the padding redundant data.

[0294] Alternatively, when the first indication information includes location information of the redundant data, the wireless access network device finds the starting and ending positions of the redundant data from the payload of the twelfth message according to the location information of the redundant data, and deletes the data from the starting position to the ending position.

[0295] Alternatively, when the first indication information includes the length information of the effective load data, the wireless access network device deletes the data except the effective load data in the load part of the twelfth message according to the length information of the effective load data, that is, deletes the padding redundant data.

[0296] Alternatively, when the first indication information includes the location information of the payload data, the wireless access network device finds the starting position and the ending position of the payload data from the payload part of the twelfth message according to the location information of the payload data, and deletes the data outside the starting position to the ending position of the payload data, that is, deletes the padding redundant data.

[0297] Specifically, when the first message is in Ethernet IEEE802.3 frame format, the wireless access network device can determine the position of the redundant data filled in the twelfth message according to the first indication information, and can also determine the position of the redundant data filled in the twelfth message according to the first indication information. Fig. 9 The length field shown in the figure determines the position of the padding redundant data in the twelfth message, and then deletes the padding redundant data in the twelfth message according to the position of the padding redundant data in the twelfth message. Specifically, according to the Length field, the data in the payload part of the twelfth message except the effective load data corresponding to the Length field is deleted, that is, the padding redundant data is deleted.

[0298] It should be noted that, in actual application, the first indication information may only include one or more of the length information of the padded redundant data, the location information of the padded redundant data, the length information of the effective load data, or the location information of the effective load data. When the first indication information includes one or more of the above information, the wireless access network device may delete the padded redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information may also include an indication to delete the padded redundant data, which is used to instruct the wireless access network device to delete the padded redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information only includes an indication to delete the padded redundant data, and the wireless access network device deletes the padded redundant data according to the first indication information.

[0299] In step 409, the wireless access network device sends a second message to the user equipment.

[0300] After deleting the redundant padding data of the twelfth message, the wireless access network device adds an air interface protocol header to generate a second message, and sends the second message to the user equipment.

[0301] For example, if the twelfth message format is Figure 8 The Ethernet II frame format shown in Figure 1 is as follows: Fig.12 As shown, the destination MAC address field, source MAC address field, type field, and payload field of the second message are the same as the corresponding fields in the twelfth message; Fig.12 The AN protocol header is also called an air interface protocol header, and can include, for example, a PDCP header, an RLC header, and a MAC header.

[0302] If the twelfth message format is Fig. 9 The IEEE 802.3 frame format shown in FIG. 1 is as follows: Figure 7 As shown, the destination MAC address field, source MAC address field, Length field, LLC field, and payload field of the second message are the same as the corresponding fields in the twelfth message; Figure 7 The AN protocol header is also called an air interface protocol header, and can include, for example, a PDCP header, an RLC header, and a MAC header.

[0303] It should be noted that the way in which the wireless access network device sends a message to the user equipment is an air interface transmission method, which is not subject to the requirements of the minimum frame length of Ethernet. Therefore, after the N3 tunnel protocol header is stripped, the length of the twelfth message is less than 64 bytes, that is, the length of the second message is less than 64 bytes and can also be transmitted. And because the padding redundant data of the payload part in the twelfth message has been deleted, that is, the payload part of the second message does not include the padding redundant data, air interface resources can be saved during air interface transmission.

[0304] In a possible implementation manner, after the user equipment receives the second message, the application layer of the user equipment may directly obtain the payload data portion of the second message for use.

[0305] Alternatively, in a possible implementation, when the user device is an intermediate node in the network and needs to continue forwarding Ethernet frames to the next-hop node, the user device supplements the payload portion of the second message with redundant data to generate a thirteenth message, so that the data length of the thirteenth message is greater than or equal to 64 bytes. Optionally, in a possible implementation, if the user-plane network element encapsulates the first message from which the redundant data is deleted according to the N3 tunnel protocol to obtain the twelfth message, and the user-plane network element also deletes the preamble field, SFD field, and FCS field in the first message, the user device also needs to supplement other fields to generate the thirteenth message, such as the FCS field, the preamble field, and the SFD field, which are not specifically limited here. Among them, the format of the thirteenth message may be the same as the format of the first message, that is, if the first message is Figure 8 The Ethernet II frame format shown in FIG. 1 is an Ethernet frame of the Ethernet II type. If the first message format is Fig. 9 3 frame format, the thirteenth message is also an IEEE 802.3 type Ethernet frame. Preferably, after the redundant data is added, the data length of the thirteenth message is the same as the data length of the first message. The data length of the first message or the thirteenth message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field in the 3rd message. Optionally, the thirteenth message is the same as the first message.

[0306] Specifically, the user equipment may fill each bit of the redundant data in the thirteenth message with 0. It is understandable that the filling may be performed in other ways, as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0307] Specifically, in a possible implementation, the user equipment may supplement the redundant data in the payload part of the twelfth message according to the first indication information to generate a thirteenth message, so that the data length of the thirteenth message is greater than or equal to 64 bytes.

[0308] Specifically, when the first indication information includes the length information of the padding redundant data, the user equipment fills the padding redundant data into the payload part of the twelfth message according to the length information of the padding redundant data.

[0309] Alternatively, when the first indication information includes location information of the filled redundant data, the user equipment finds the starting position and the ending position of the filled redundant data to be filled from the payload part of the twelfth message according to the location information of the filled redundant data, and fills the filled redundant data into the corresponding position.

[0310] Alternatively, when the first indication information includes the length information of the effective load data, the user equipment fills the redundant data into the payload part of the twelfth message according to the length information of the effective load data.

[0311] Alternatively, when the first indication information includes the location information of the payload data, the user equipment finds the starting position and the ending position of the payload data from the payload part of the twelfth message according to the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0312] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the user equipment determines to add padding redundant data based on the first indication information, and fills the twelfth message with the padding redundant data based on the Ethernet minimum frame length specified by the protocol.

[0313] In step 410, the user equipment receives a seventh message, where the seventh message is an uplink Ethernet message.

[0314] In step 411, the user equipment deletes the padding redundant data in the seventh message.

[0315] In step 412, the user equipment generates an eighth message, and sends the eighth message to the wireless network device.

[0316] Steps 410 to 412 are similar to the above Figure 2 The methods performed in step 210 to step 212 in the illustrated embodiment are similar and will not be described in detail herein.

[0317] In step 413, the wireless access network device adds redundant padding data to the eighth message.

[0318] After receiving the eighth message sent by the user equipment, the wireless access network device removes the air interface protocol header in the eighth message, adds padding redundant data to the eighth message, and adds the N3 tunnel protocol header to generate a ninth message, so that the data length of the ninth message is greater than or equal to 64 bytes. Exemplarily, if the seventh message format is Figure 8 The Ethernet II frame format shown in Figure 1 shows the format of the ninth message. Fig.10 As shown, the destination MAC address field, source MAC address field, type field and payload field of the ninth message are the same as the corresponding fields in the eighth message; and the N3 tunnel protocol header field includes Fig.10 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.10 The FSC field in the seventh message is different. Fig.10 The FCS field in the N3 MAC frame is calculated by the wireless access network device based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.10 The N3MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.

[0319] If the seventh message format is Fig. 9 When the IEEE 802.3 frame format is shown, the format of the ninth message is Fig.11 As shown, the destination MAC address field, source MAC address field, Length field, LLC field and payload field of the ninth message are the same as the corresponding fields in the eighth message; and the N3 tunnel protocol header field includes Fig.11 The N3 MAC header field, IP header field, UDP header field and GTP-U header field in the MAC header field. The N3 MAC header field refers to the MAC layer protocol header field used by the message to be transmitted in the layer 2 transmission network between the access network node and the user plane network element. Fig.11 The FSC field in the seventh message is different. Fig.11 The FCS field in the N3 MAC frame is calculated by the wireless access network device based on the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes Fig.11 N3 MAC header field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field and payload field.

[0320] Specifically, the wireless access network device encapsulates the eighth message according to the N3 tunnel protocol to obtain a ninth message. Specifically, in a possible implementation, the N3 tunnel protocol here may be a GTP-U protocol. It is understandable that in actual application, it may also be other N3 tunnel protocols, which are not specifically limited here.

[0321] It should be noted that the N3 tunnel protocol refers to the tunnel protocol between the user plane network element and the access network node. In the present invention, the N3 tunnel protocol can be replaced by other tunnel protocols that may be used for transmitting data between the user plane network element and the access network node.

[0322] The format of the ninth message is the same as that of the seventh message, that is, if the seventh message is Figure 8 The Ethernet II frame format shown in the figure is the Ethernet II frame format. The ninth message is also an Ethernet II type Ethernet frame. If the seventh message format is Fig. 9 The IEEE 802.3 frame format shown in FIG. 1 is the IEEE 802.3 frame format, and the ninth message is also an IEEE 802.3 type Ethernet frame. The data length of the seventh message or the ninth message is Figure 8 or Fig. 9 The sum of the lengths of all fields excluding the preamble field, SFD field, and frame check sequence field.

[0323] Specifically, the wireless access network device may fill each digit of the redundant data in the ninth message with 0. It is understandable that filling may be performed in other ways, as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0324] Specifically, in a possible implementation, the wireless access network may supplement the payload portion of the eighth message with the padding redundant data according to the first indication information to generate a ninth message, so that the data length of the ninth message is greater than or equal to 64 bytes. Specifically, when the first indication information includes length information of the padding redundant data, the wireless access network pads the padding redundant data into the payload portion of the eighth message according to the length information of the padding redundant data.

[0325] Alternatively, when the first indication information includes location information of the filling redundant data, the wireless access network finds the starting and ending positions of the filling redundant data to be filled from the payload part of the eighth message according to the location information of the filling redundant data, and fills the filling redundant data into the corresponding positions.

[0326] Alternatively, when the first indication information includes the length information of the effective load data, the wireless access network fills the redundant padding data into the payload part of the eighth message according to the length information of the effective load data.

[0327] Alternatively, when the first indication information includes the location information of the payload data, the wireless access network finds the starting position and the ending position of the payload data from the payload part of the eighth message according to the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0328] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the wireless access network determines to add padding redundant data based on the first indication information, and fills the eighth message with the padding redundant data based on the Ethernet minimum frame length specified by the protocol.

[0329] In step 414, the wireless access network device sends a ninth message to the user plane network element.

[0330] After generating the ninth message, the wireless access network device sends the ninth message to the user plane network element.

[0331] After receiving the ninth message, the user plane network element may strip the N3 tunnel protocol header in the ninth message, generate the fourteenth message, and send it to the next hop node.

[0332] Optionally, if the user equipment deletes the preamble field, SFD field and FCS field in the seventh message in addition to deleting the padding redundant data in the seventh message, the user plane network element further supplements other fields to generate the fourteenth message.

[0333] It should be noted that the format of the fourteenth message is the same as that of the seventh message, that is, if the seventh message is Figure 8 The Ethernet II frame format shown in FIG. 14 is also an Ethernet frame of Ethernet II type. If the format of the seventh message is Fig. 9 The IEEE 802.3 frame format shown in FIG. 14 is also an IEEE 802.3 type Ethernet frame. The data length of the seventh message or the fourteenth message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field. Optionally, the fourteenth message is the same as the seventh message.

[0334] In this embodiment, steps 406 to 409 are application scenarios for sending downlink messages, and steps 410 to 414 are application scenarios for sending uplink messages. In actual application, steps 406 to 409 can be implemented separately, and steps 410 to 414 can also be implemented separately or in combination, which is not limited here.

[0335] In an embodiment of the present application, the user plane device deletes the padding redundant data in the received downlink Ethernet message so that the downlink message transmitted to the user device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0336] In an embodiment of the present application, the user equipment deletes the padding redundant data in the received uplink Ethernet message, so that the uplink message transmitted to the wireless access network device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0337] See also Figure 5 , is another flow chart of the data transmission method provided in an embodiment of the present application.

[0338] In step 501, a user equipment establishes a PDU session.

[0339] The user equipment UE establishes a PDU session, which is used to transmit (Cellular Internet of Thinns, CIoT) packets through the control plane, that is, to transmit CIoT packets through (Non-Access-Stratum, NAS) messages.

[0340] It should be noted that this embodiment can be applied to the scenario where the 5G system and the industrial network are interconnected, and can also be applied to other network scenarios, which are not limited here. For the scenario where the 5G system and the industrial network are interconnected, the application server can be a production line controller or other industrial node in the industrial network.

[0341] In step 502, the application function network element sends an AF request message to the policy control network element.

[0342] In this embodiment, step 502 is the same as the above Figure 2 The method performed in step 202 in the illustrated embodiment is similar and will not be described in detail here.

[0343] In step 503, the policy control network element sends a policy update message to the session management network element.

[0344] After receiving the AF request message sent by the session management network element, the policy control network element obtains the first indication information and the service data flow SDF template in the AF request message, generates the first indication information according to the second indication information, and carries the first indication information and the SDF template in the policy update message and sends it to the session management network element. The SDF template includes the application identifier or service filtering information received by the policy control network element in step 502, or the application identifier or service filtering information of one or more applications corresponding to the DN received in step 502. The first indication information is used to delete or add redundant filling data of the message of the service described by the SDF template.

[0345] Specifically, in a possible implementation manner, the policy update message includes a PCC rule, and the PCC rule further includes first indication information and an SDF template.

[0346] Specifically, in a possible implementation, the first indication information may also indicate the length information of the first padding redundant data. Specifically, the length information of the first padding redundant data may be the length of the padding redundant data in the payload field of the message.

[0347] Specifically, in a possible implementation, the first indication information may also indicate the location information of the first filling redundant data. Specifically, the location information of the first filling redundant data may be the starting position and the ending position of the filling redundant data in the payload field of the message.

[0348] Specifically, in a possible implementation, the first indication information may also indicate the length information of the payload data of the message. Specifically, the length information of the payload data of the message may be the length of the payload data in the payload field of the message.

[0349] Specifically, in a possible implementation, the first indication information may also indicate the position information of the payload data of the message. Specifically, the position information of the payload data of the message may be the starting position and the ending position of the payload data in the payload field of the message.

[0350] It should be noted that, in actual application, the first indication information may include one or more of the length information of the padding redundant data, the location information of the padding redundant data, the length information of the effective load data, or the location information of the effective load data. When the first indication information includes one or more of the above information, the device receiving the first indication information may add or delete the padding redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information may also include an indication to add or delete the padding redundant data, which is used to instruct the device receiving the first indication information to add or delete the padding redundant data according to the first indication information when receiving the service message. Alternatively, in a possible implementation, the first indication information only includes an indication to add or delete the padding redundant data, and the device receiving the first indication information adds or deletes the padding redundant data according to the first indication information when receiving the service message.

[0351] After the session management network element receives the policy update message, the session management network element performs session management processing according to the policy update message.

[0352] Specifically, the session management network element binds the PCC rule obtained from the policy update message to the PDU session identifier. The PCC rule includes the first indication information and the SDF template. Binding the PCC rule to the PDU session identifier can be understood as applying the PCC rule to the PDU session, that is, one or more service flows corresponding to the SDF template in the PCC rule are bound to the PDU session, and the padding redundant data length information included in the first indication information is the same.

[0353] In step 504, the session management network element sends an N1 interface session management message to the user equipment.

[0354] The session management network element obtains the first indication information and SDF template in the policy update message, and the SMF sends the PDU session identifier and the first indication information corresponding to the SDF to the user equipment through the N1 interface session management information. Specifically, the N1 interface session management message carries the PDU session modification command, that is, the N1 interface session management message includes the PDU session modification command, and the PDU session modification command includes the PDU session identifier and the first indication information. It should be noted that the N1 interface session management message here is sent by the SMF to the wireless access network device through the AMF, and then sent to the user equipment through the wireless access network device.

[0355] It should be noted that, in this embodiment, the PDU session identifier and the first indication information may also be sent to the user equipment through the radio access network device RAN, that is, Figure 3The method performed in step 306 in the illustrated embodiment is similar and will not be described in detail here.

[0356] In step 505, the user plane network element receives the first message.

[0357] The first message is an Ethernet message. When downlink data is transmitted, the user-plane network element will receive one or more downlink first messages, and the one or more first messages correspond to a PDU session identifier.

[0358] Specifically, in a possible implementation, the first message is in Ethernet II frame format. Figure 8 As shown, the first message includes a preamble field, a start frame delimiter field (SFD) field, a destination MAC address field, a source MAC address field, a type field, a data payload field, and a frame check sequence (FCS) field. The data payload field includes a valid payload field and a padding field.

[0359] Specifically, in a possible implementation, the first message is in Ethernet IEEE 802.3 frame format. Fig. 9 As shown, the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a length field, a logical link control (LLC) field, a data payload field, and an FCS field. The data payload field includes a payload field and a padding field.

[0360] In step 506, the user plane network element sends a first message to the session management network element.

[0361] After receiving the first message, the user plane network element UPF forwards the first message to the session management network element, that is, sends the first message to the session management network element.

[0362] In step 507, the session management network element deletes the redundant padding data.

[0363] After receiving the first message, the session management network element deletes the padding redundant data in the first message.

[0364] Specifically, when the first message is in Ethernet II frame format, the session management network element SMF deletes the padding redundant data in the first message according to the first indication information.

[0365] Specifically, when the first indication information includes the length information of the padding redundant data, the session management network element deletes the padding redundant data of the payload part in the first message according to the length information of the padding redundant data. Figure 8 or Fig. 9 The frame format in the first indication information can determine the end position of the padded redundant data, and then the starting position of the padded redundant data can be determined according to the length of the padded redundant data contained in the first indication information, and then the padded redundant data can be deleted according to the starting position and the end position.

[0366] Alternatively, when the first indication information includes location information of the redundant data to be filled, the session management network element SMF finds the starting and ending positions of the redundant data to be filled from the payload part of the first message according to the location information of the redundant data to be filled, and deletes the data from the starting position to the ending position.

[0367] Alternatively, when the first indication information includes the length information of the payload data, the session management network element deletes the data other than the payload data in the payload part of the first message according to the length information of the payload data, that is, deletes the padding redundant data. Figure 8 or Fig. 9 The frame format in the first indication information can determine the end position of the padded redundant data, and then the starting position of the padded redundant data can be determined according to the length of the padded redundant data contained in the first indication information, and then the padded redundant data can be deleted according to the starting position and the end position.

[0368] Alternatively, when the first indication information includes the location information of the payload data, the session management network element finds the starting position and the ending position of the payload data from the payload part of the first message based on the location information of the payload data, and deletes the data outside the starting position to the ending position of the payload data, that is, deletes the redundant padding data.

[0369] Specifically, when the first message is in Ethernet IEEE802.3 frame format, the session management network element can determine the position of the first message filled with redundant data according to the first indication information, and can also determine the position of the first message filled with redundant data according to the first indication information. Fig. 9 The length field shown determines the position of the padding redundant data in the first message, and then deletes the padding redundant data in the first message according to the position of the padding redundant data in the first message. Specifically, according to the Length field, the data in the payload part of the first message except the effective load data corresponding to the Length field is deleted, that is, the padding redundant data is deleted.

[0370] It should be noted that, in actual application, the first indication information may only include one or more of the length information of the padding redundant data, the location information of the padding redundant data, the length information of the effective load data, or the location information of the effective load data. When the first indication information includes one or more of the above information, the user plane network element may delete the padding redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information may also include an indication to delete the padding redundant data, which is used to instruct the session management network element to delete the padding redundant data according to the first indication information. Alternatively, in a possible implementation, the first indication information only includes an indication to delete the padding redundant data, and the session management network element deletes the padding redundant data according to the first indication information.

[0371] Optionally, the session management network element deletes the preamble field, SFD field and FCS field in the first message in addition to deleting the padding redundant data, that is, the preamble field, SFD field and FCS field in the first message are not transmitted between the user session management network element and the user equipment.

[0372] In step 508, the session management network element sends a combined message of N1 and N2 to the access and mobility management network element.

[0373] After deleting the redundant padding data of the first message, the session management network element generates a second message and sends the second message to the mobility management network element AMF through a NAS message. The payload data in the second message is the effective payload data after the redundant padding data is deleted in the first message.

[0374] Specifically, in a possible implementation method, the session management network element sends a second message and a PDU session identifier to the AMF through a combined message of N1 and N2 (Namf_Communication_N1N2MessageTransfer service operation).

[0375] In step 509, the mobility management network element sends a downlink NAS transmission message to the wireless access network device.

[0376] After receiving the second message and the PDU session identifier, the mobility management network element sends a downlink NAS transmission message to the wireless access network device.

[0377] Specifically, the mobility management network element generates a downlink NAS transmission message, carries the second message and the PDU session identifier in the downlink NAS transmission message, and sends the downlink NAS transmission message to the wireless access network device.

[0378] In step 510, the radio access network device sends an RRC message to the user equipment.

[0379] After receiving the downlink NAS transmission message, the wireless access network device sends the downlink NAS message to the UE through an RRC message.

[0380] Specifically, in a possible implementation manner, the RAN sends the downlink NAS message to the UE through an RRC DL message.

[0381] In a possible implementation manner, after the user equipment receives the second message, the application layer of the user equipment may directly obtain the payload data portion of the second message for use.

[0382] Alternatively, in a possible implementation, when the user equipment is an intermediate node of the network and needs to continue forwarding Ethernet frames to the next-hop node, the user equipment supplements the payload portion of the second message with redundant data to generate a sixth message, so that the data length of the sixth message is greater than or equal to 64 bytes. Optionally, in a possible implementation, if the session management network element also deletes the preamble field, SFD field, and FCS field in the first message, the user equipment also supplements other fields to generate the sixth message, such as the FCS field, the preamble field, and the SFD field, which are not specifically limited here. The format of the sixth message is the same as the format of the first message, that is, if the first message is Figure 8 The Ethernet II frame format shown in FIG. 1 is an Ethernet frame of the Ethernet II type. If the first message format is Fig. 9 3 frame format, the sixth message is also an IEEE 802.3 type Ethernet frame. Preferably, after the redundant data is added, the data length of the sixth message is the same as the data length of the first message. The data length of the first message or the sixth message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field in the sixth message. Optionally, the sixth message is the same as the first message.

[0383] Specifically, the user equipment may fill each bit of the redundant data in the sixth message with 0. It is understandable that the filling may be performed in other ways, as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0384] Specifically, in a possible implementation, the user equipment may supplement the redundant data in the payload part of the second message according to the first indication information to generate a sixth message, so that the data length of the sixth message is greater than or equal to 64 bytes.

[0385] Specifically, when the first indication information includes the length information of the padding redundant data, the user equipment fills the padding redundant data into the payload part of the second message according to the length information of the padding redundant data.

[0386] Alternatively, when the first indication information includes location information of the filled redundant data, the user equipment finds the starting position and the ending position of the filled redundant data to be filled from the payload part of the fifth message according to the location information of the filled redundant data, and fills the filled redundant data into the corresponding position.

[0387] Alternatively, when the first indication information includes the length information of the effective load data, the user equipment fills the redundant data into the payload part of the second message according to the length information of the effective load data.

[0388] Alternatively, when the first indication information includes the location information of the payload data, the user equipment finds the starting position and the ending position of the payload data from the payload part of the fifth message according to the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0389] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the user equipment determines to add padding redundant data based on the first indication information, and fills the second message with the padding redundant data based on the Ethernet minimum frame length specified by the protocol.

[0390] In step 511, the user equipment receives a seventh message, where the seventh message is an uplink Ethernet message.

[0391] The seventh message is an Ethernet message. When uplink data is transmitted, the user equipment obtains one or more uplink Ethernet messages, wherein the uplink Ethernet message is the seventh message. When the user equipment has a previous hop node, the user equipment receives the uplink Ethernet message sent by the previous hop node. When the user equipment does not have a previous hop node, the user equipment generates an uplink Ethernet message.

[0392] Specifically, in a possible implementation, the uplink Ethernet message is in Ethernet II frame format. Figure 8 As shown, the uplink Ethernet message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0393] Specifically, in a possible implementation, the uplink Ethernet message is in Ethernet IEEE802.3 frame format. Fig. 9 As shown, the uplink Ethernet message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a payload length field, an LLC field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0394] In step 512, the user equipment deletes the padding redundant data.

[0395] After obtaining the seventh message, the user equipment deletes the padding redundant data in the seventh message.

[0396] Specifically, when the seventh message is in Ethernet II frame format, the user equipment deletes the padding redundant data in the seventh message according to the first indication information.

[0397] Specifically, when the first indication information includes the length information of the padding redundant data, the user equipment deletes the padding redundant data in the payload part of the seventh message according to the length information of the padding redundant data.

[0398] Alternatively, when the first indication information includes location information of the redundant data to be filled, the user equipment finds the starting and ending positions of the redundant data to be filled from the payload part of the seventh message according to the location information of the redundant data to be filled, and deletes the data from the starting position to the ending position.

[0399] Alternatively, when the first indication information includes the length information of the effective load data, the user equipment deletes the data except the effective load data in the payload part of the uplink Ethernet message according to the length information of the effective load data, that is, deletes the padding redundant data.

[0400] Alternatively, when the first indication information includes the location information of the payload data, the user equipment finds the starting position and the ending position of the payload data from the payload part of the seventh message based on the location information of the payload data, and deletes the data outside the starting position to the ending position of the payload data, that is, deletes the padding redundant data.

[0401] Specifically, when the seventh message is in Ethernet IEEE802.3 frame format, the user equipment element can determine the position of the padded redundant data in the seventh message according to the first indication information, and can also determine the position of the padded redundant data in the seventh message according to the length field, and delete the padded redundant data in the seventh message according to the position of the padded redundant data in the seventh message. Specifically, according to the Length field, the data in the payload part of the seventh message except the effective load data corresponding to the Length field is deleted, that is, the padded redundant data of the seventh message is deleted.

[0402] Optionally, in addition to deleting the padding redundant data in the seventh message, the user equipment also deletes the preamble field, SFD field and FCS field in the seventh message, that is, the preamble field, SFD field and FCS field in the seventh message are not transmitted between the user equipment and the session management network element.

[0403] In step 513, the user equipment sends an RRC message to the radio access network device.

[0404] After deleting the padding redundant data of the seventh message, the user equipment generates an eighth message, the payload data in the eighth message is the effective payload data after the padding redundant data is deleted in the seventh message, and sends the eighth message to the radio access network device RAN through an RRC message.

[0405] Specifically, the user equipment encapsulates the eighth message and the corresponding PDU session identifier in an uplink NAS message, and carries the uplink NAS message in an RRC message and sends it to the RAN.

[0406] In step 514, the radio access network device sends an uplink NAS message to the access and mobility management network element AMF.

[0407] After receiving the uplink NAS message sent by the user equipment, the radio access network device RAN forwards the uplink NAS message to the access and mobility management network element AMF.

[0408] In step 515, the access and mobility management network element AMF sends a combined message of N1 and N2 to the session management network element.

[0409] After receiving the uplink NAS message sent by the RAN, the access and mobility management network element AMF carries the NAS message in the combined message of N1 and N2 (Namf_Communication_N1N2MessageTransfer service operation) and sends it to the session management network element.

[0410] In step 516, the session management network element adds padding redundant data.

[0411] After receiving the eighth message carried in the NAS message, the session management network element adds padding redundant data to generate a ninth message, so that the data length of the ninth message is greater than or equal to 64 bytes. Optionally, if the user equipment deletes the preamble field, SFD field and FCS field in the seventh message in addition to the padding redundant data in the seventh message, the session management network element also adds other fields to generate the ninth message, such as the FCS field, the preamble field and the SFD field, which are not limited here. The format of the ninth message is the same as that of the seventh message, that is, if the seventh message is Figure 8 The Ethernet II frame format shown in the figure is the Ethernet II frame format. The ninth message is also an Ethernet II type Ethernet frame. If the seventh message format is Fig. 9 , the ninth message is also an IEEE 802.3 type Ethernet frame. Preferably, after the redundant data is added, the data length of the ninth message is the same as the data length of the seventh message. The data length of the seventh message or the ninth message is Figure 8 or Fig. 9 The sum of the lengths of the other fields except the preamble field, the SFD field and the frame check sequence field. Optionally, the ninth message is the same as the seventh message.

[0412] Specifically, the session management network element may fill each digit of the redundant data in the ninth message with 0. It is understandable that filling may be performed in other ways as long as the data length of the message after filling is greater than or equal to 64 bytes, which is not specifically limited here.

[0413] Specifically, in a possible implementation, the session management network element may supplement the payload portion of the eighth message with the padding redundant data according to the first indication information to generate a ninth message, so that the data length of the ninth message is greater than or equal to 64 bytes. Specifically, when the first indication information includes length information of the padding redundant data, the session management network element pads the padding redundant data into the payload portion of the eighth message according to the length information of the padding redundant data.

[0414] Alternatively, when the first indication information includes location information of the filling redundant data, the session management network element finds the starting and ending positions of the filling redundant data to be filled from the payload part of the eighth message according to the location information of the filling redundant data, and fills the filling redundant data into the corresponding position.

[0415] Alternatively, when the first indication information includes the length information of the effective load data, the session management network element fills the redundant padding data into the payload part of the eighth message according to the length information of the effective load data.

[0416] Alternatively, when the first indication information includes the location information of the payload data, the session management network element finds the starting position and ending position of the payload data from the payload part of the eighth message based on the location information of the payload data, and fills the redundant data to the position after the end position of the payload data and before the FCS field.

[0417] In an optional manner, when the first indication information only includes an indication to add padding redundant data, the session management network element determines to add padding redundant data according to the first indication information, and fills the eighth message with the padding redundant data according to the Ethernet minimum frame length specified in the protocol.

[0418] In step 517, the session management network element sends a ninth message.

[0419] The session management network element sends the ninth message to the next-hop node.

[0420] In this embodiment, steps 505 to 510 are application scenarios for sending downlink messages, and steps 511 to 517 are application scenarios for sending uplink messages. In actual application, steps 505 to 510 can be implemented separately, and steps 511 to 517 can also be implemented separately or in combination, which is not limited here.

[0421] In an embodiment of the present application, the user plane device deletes the padding redundant data in the received downlink message so that the downlink message transmitted to the user device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0422] In an embodiment of the present application, the user equipment deletes the padding redundant data in the received uplink message so that the uplink message transmitted to the wireless access network device over the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0423] See also Figure 6 , is another flow chart of the data transmission method provided in an embodiment of the present application.

[0424] In step 601, the user equipment establishes a PDU session.

[0425] In step 602, the application function network element sends an AF request message to the policy control network element.

[0426] In step 603, the policy control network element sends a policy update message to the session management network element.

[0427] In step 604, the session management network element sends a PDU session modification command to the user equipment.

[0428] In this embodiment, steps 601 to 604 are the same as those described above. Figure 5 The methods performed in steps 501 to 504 in the embodiment are similar and will not be described in detail here.

[0429] In step 605, the network capability opening function network element receives the first message.

[0430] The first message is an Ethernet message. When downlink data is transmitted, the NEF will receive one or more downlink first messages, and the one or more first messages correspond to a PDU session identifier.

[0431] Specifically, in a possible implementation, the first message is in Ethernet II frame format. Figure 8 As shown, the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0432] Specifically, in a possible implementation, the first message is in Ethernet IEEE 802.3 frame format. Fig. 9 As shown, the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a length field, an LLC field, a data load field, and an FCS field. The data load field includes a valid load field and a padding field.

[0433] In step 606, the NEF sends a first message to the session management network element.

[0434] After receiving the first message, the NEF forwards the first message to the session management network element, that is, sends the first message to the session management network element.

[0435] Specifically, in a possible implementation manner, the NEF forwards the first message to the SMF through an Nsmf_NIDD_Delivery request message.

[0436] In step 607, the session management network element deletes the redundant padding data.

[0437] In step 608, the session management network element sends a combined message of N1 and N2 to the access and mobility management network element AMF.

[0438] In step 609, the mobility management network element AMF sends a downlink NAS transmission message to the wireless access network device.

[0439] In step 610, the radio access network device sends an RRC message to the user equipment.

[0440] In step 611, the user equipment receives a seventh message, where the seventh message is an uplink Ethernet message.

[0441] In step 612, the user equipment deletes the padding redundant data.

[0442] In step 613, the user equipment sends an RRC message to the radio access network device.

[0443] In step 614, the wireless access network device sends an uplink NAS message to the access and mobility management network element.

[0444] In step 615, the access and mobility management network element sends a combined message of N1 and N2 to the session management network element.

[0445] In step 616, the session management network element adds padding redundant data.

[0446] In this embodiment, steps 607 to 616 are the same as those described above. Figure 5 The methods performed in steps 507 to 516 in the embodiment are similar and will not be described in detail here.

[0447] In step 617, the session management network element sends a ninth message.

[0448] After adding the padding redundant data to obtain the ninth message, the session management network element sends the ninth message to the NEF through the Nnef_SMContext_Delivery request message.

[0449] Specifically, after receiving the ninth message, the NEF sends the ninth message to the next hop node.

[0450] In this embodiment, steps 605 to 610 are application scenarios for sending downlink messages, and steps 611 to 617 are application scenarios for sending uplink messages. In actual application, steps 605 to 610 can be implemented separately, and steps 611 to 617 can also be implemented separately or in combination, which is not limited here.

[0451] In an embodiment of the present application, the user plane device deletes the padding redundant data in the received downlink message so that the downlink message transmitted to the user device at the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0452] In an embodiment of the present application, the user equipment deletes the padding redundant data in the received uplink message so that the uplink message transmitted to the wireless access network device over the air interface does not include the padding redundant data, that is, there is no need to transmit the padding redundant data, thereby saving air interface resources and improving air interface capacity.

[0453] The data transmission method in the embodiment of the present application is described above, and the device provided in the embodiment of the present application is described below.

[0454] See also Fig.13 , which is a structural diagram of the device provided in an embodiment of the present application.

[0455] A device comprising:

[0456] The receiving unit 1301 is configured to receive a first message, wherein the payload data in the first message includes padding redundant data;

[0457] A deleting unit 1302, used for deleting redundant padding data;

[0458] A generating unit 1303 is configured to generate a second message, wherein the payload data in the second message is the effective payload data after the padding redundant data is deleted from the first message;

[0459] The sending unit 1304 is configured to send a second message to a second device.

[0460] The method performed by each unit of the device in this embodiment is the same as the above Figures 2 to 6 The methods executed by each network device or user equipment are similar and will not be described in detail here.

[0461] See also Fig.13 , is another structural schematic diagram of the device provided in an embodiment of the present application.

[0462] A device comprising:

[0463] The receiving unit 1301 is configured to receive a first message, wherein the payload data in the first message includes padding redundant data;

[0464] A deleting unit 1302, used for deleting redundant padding data;

[0465] A generating unit 1303 is configured to generate a second message, wherein the payload data in the second message is the effective payload data after the padding redundant data is deleted from the first message;

[0466] The sending unit 1304 is configured to send a second message to a second device.

[0467] Optionally, the receiving unit 1301 is further configured to receive first indication information;

[0468] The deleting unit 1302 is specifically configured to delete the padding redundant data according to the first indication information.

[0469] Optionally, the first indication information is used to instruct the device to delete the padding redundant data, or the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of the payload data of the first downlink message, or location information of the payload data of the first message.

[0470] Optionally, the deleting unit 1302 is specifically configured to delete padding redundant data according to a length field of the first message.

[0471] Optionally, the device is a UPF, the second device is a RAN, and the first message is a downlink Ethernet message.

[0472] Optionally, the generating unit 1303 is specifically configured to encapsulate the third message according to the N3 tunnel protocol to obtain a fourth message, wherein the third message is the message after the redundant padding data is deleted from the first message; if the data length of the fourth message is less than the minimum frame length of Ethernet, the tunnel protocol redundant padding data is added to the N3 tunnel protocol header of the fourth message to obtain a second message, and the data length of the second message is greater than or equal to the minimum frame length of Ethernet; or,

[0473] If the device determines that the data length of the encapsulated message obtained by the first device encapsulating the third message according to the N3 tunnel protocol is less than the minimum frame length of Ethernet, the generation unit 1303 is specifically used to encapsulate the third message according to the N3 tunnel protocol to obtain an encapsulated message, and add the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated message to obtain a second message, the data length of the second message is greater than or equal to the minimum frame length of Ethernet, wherein the third message is the message after the redundant filling data is deleted from the first message.

[0474] Optionally, the device is a RAN, the second device is a UE, and the first message is a downlink message.

[0475] Optionally, the device is a UE, the second device is a RAN, and the first message is an uplink Ethernet message.

[0476] Optionally, the device is an SMF, the second device is a UE, and the first message is a downlink Ethernet message.

[0477] Optionally, the device is a UE, the second device is an SMF, and the first message is an uplink Ethernet message.

[0478] The method performed by each unit of the device in this embodiment is the same as the above Figures 2 to 6 The methods executed by each network device or user equipment are similar and will not be described in detail here.

[0479] See also Fig.14 , which is a structural diagram of the device provided in an embodiment of the present application.

[0480] A device comprising:

[0481] The sending unit 1401 is used to send first indication information to a fourth device, wherein the first indication information is used to delete padding redundant data of the first message, or the first indication information is used to add padding redundant data to the first message, the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of the payload data of the first message, or location information of the payload data of the first message.

[0482] The method performed by each unit of the device in this embodiment is the same as the above Figures 2 to 6 The methods executed by each network device are similar and will not be described in detail here.

[0483] See also Fig.15 , is another structural schematic diagram of the device provided in an embodiment of the present application.

[0484] A device comprising:

[0485] The sending unit 1501 is used to send first indication information to a fourth device, wherein the first indication information is used to delete padding redundant data of the first message, or the first indication information is used to add padding redundant data to the first message, the first indication information includes length information of the padding redundant data, or location information of the padding redundant data, or the first indication information includes length information of the payload data of the first message, or location information of the payload data of the first message.

[0486] Optionally, when the first indication information is used to delete redundant padding data of the first message,

[0487] The device is a PCF, the fourth device is an SMF, and the first message is an Ethernet message; or,

[0488] The device is SMF, the fourth device is UPF, and the first message is an Ethernet message; or,

[0489] The device is an SMF, the fourth device is a UE, and the first message is an Ethernet message; or,

[0490] The device is SMF, and the fourth device is RAN; or,

[0491] The device is RAN, and the fourth device is UE.

[0492] Optionally, when the first indication information is used to add padding redundant data to the first message,

[0493] The device is SMF, the fourth device is UPF, and the first message is an Ethernet message; or,

[0494] The device is an SMF, the fourth device is a UE, and the first message is an Ethernet message; or,

[0495] The device is SMF, and the fourth device is RAN.

[0496] Optionally, the device is a policy control network element PCF, the fourth device is a session management network element SMF, the fifth device is an application function network element AF, and the device further includes:

[0497] The receiving unit 1502 is used to receive second indication information of the fifth device, where the second indication information is used to indicate the length information of the padding redundant data, or the position information of the padding redundant data, or the second indication information is used to indicate the length information of the payload data of the first message, or the position information of the payload data of the first message;

[0498] The determining unit 1503 is configured to determine the first indication information according to the second indication information.

[0499] The method performed by each unit of the device in this embodiment is the same as the above Figures 2 to 6 The methods executed by each network device are similar and will not be described in detail here.

[0500] See also Fig.16 , which is a structural diagram of the device provided in an embodiment of the present application.

[0501] Processor 1601, memory 1602, bus 1605, interface 1604, processor 1601 is connected to memory 1602 and interface 1604, bus 1605 is respectively connected to processor 1601, memory 1602 and interface 1604, interface 1604 is used to receive or send data, processor 1601 is a single-core or multi-core central processing unit, or a specific integrated circuit, or one or more integrated circuits configured to implement an embodiment of the present invention. Memory 1602 can be a random access memory (RAM) or a non-volatile memory (non-volatile memory), such as at least one hard disk memory. Memory 1602 is used to store computer execution instructions. Specifically, the computer execution instructions may include program 1603.

[0502] In this embodiment, when the processor 1601 calls the program 1603, it can use Fig.16 The device in the above Figures 2 to 6 The operations performed by each network device in the illustrated embodiment will not be described in detail here.

[0503] See also Fig.17 , which is a structural diagram of the device provided in an embodiment of the present application.

[0504] Processor 1701, memory 1702, bus 1705, interface 1704, processor 1701 is connected to memory 1702 and interface 1704, bus 1705 is respectively connected to processor 1701, memory 1702 and interface 1704, interface 1704 is used to receive or send data, processor 1701 is a single-core or multi-core central processing unit, or a specific integrated circuit, or one or more integrated circuits configured to implement an embodiment of the present invention. Memory 1702 can be a random access memory (RAM) or a non-volatile memory (non-volatile memory), such as at least one hard disk memory. Memory 1702 is used to store computer execution instructions. Specifically, the computer execution instructions may include program 1703.

[0505] In this embodiment, when the processor 1701 calls the program 1703, it can use Fig.17 The device in the above Figures 2 to 6 The operations performed by the user equipment in the illustrated embodiment will not be described in detail here.

[0506] It should be understood that the processor mentioned in the network device or user equipment in the above embodiments of the present application, or the processor provided in the above embodiments of the present application, may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0507] It should also be understood that the number of processors in the network device or user equipment in the above embodiments of the present application can be one or more, and can be adjusted according to the actual application scenario. This is only an exemplary description and is not limited. The number of memories in the embodiments of the present application can be one or more, and can be adjusted according to the actual application scenario. This is only an exemplary description and is not limited.

[0508] It should also be noted that when the network device or user device includes a processor (or processing unit) and a memory, the processor in the present application can be integrated with the memory, or the processor and the memory can be connected through an interface, which can be adjusted according to the actual application scenario and is not limited.

[0509] An embodiment of the present application further provides a computer program or a computer program product including a computer program. When the computer program is executed on a computer, the computer will implement the method flow related to the network device or user equipment in any of the above method embodiments.

[0510] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a computer, the method flow related to the network device or the user device in any of the above method embodiments is implemented.

[0511] In the above Figure 2-Figure 6 In various embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0512] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0513] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, which is only to describe the distinction mode adopted by the objects of the same attributes when describing in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0514] The names of the messages / frames / information, modules or units, etc. provided in the embodiments of the present application are only examples, and other names may be used as long as the functions of the messages / frames / information, modules or units, etc. are the same.

[0515] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present invention. The singular forms of "a", "said" and "the" used in the embodiments of the present application are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that in the description of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0516] As used herein, the words “if” or “if” may be interpreted as “at the time of” or “when” or “in response to determining” or “in response to detecting”, depending on the context. Similarly, the phrases “if it is determined” or “if (stated condition or event) is detected” may be interpreted as “when it is determined” or “in response to determining” or “when detecting (stated condition or event)” or “in response to detecting (stated condition or event)”, depending on the context.

[0517] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A data transmission method, characterized in that: include: receiving first indication information from a control plane network element, where the first indication information is used to indicate adding padding redundant data; According to the first indication information, add padding redundant data in the first message to generate a second message; Send the second message.

2. The method according to claim 1, characterized in that Adding padding redundant data to the first message according to the first indication information to generate a second message includes: In the case where the data length of the first message is less than the Ethernet minimum frame length, the padding redundant data is added to the first message, and the data length of the second message is greater than or equal to the Ethernet minimum frame length.

3. The method according to claim 2, characterized in that The method further comprises: Perform an Ethernet frame length check on the first message.

4. The method according to claim 3, characterized in that The method further comprises: Receive third indication information, where the third indication information is used to instruct to perform an Ethernet frame length check on the first message.

5. The method according to claim 4, characterized in that Receiving third indication information includes: The third indication information is received from the control plane network element.

6. The method according to any one of claims 1 to 5, characterized in that Adding padding redundant data to the first message according to the first indication information to generate a second message includes: The padding redundant data is added to the tunnel protocol header of the first message.

7. The method according to any one of claims 1 to 6, characterized in that The first message is a message between a user plane network element and a wireless access network device.

8. The method according to any one of claims 1 to 7, characterized in that The method is executed by a user plane network element, or the method is executed by a radio access network device.

9. The method according to any one of claims 1 to 6, characterized in that The first message is a message between a wireless access network device and a user equipment.

10. The method according to any one of claims 9 or 1 to 6, characterized in that: The method is executed by a user equipment, or the method is executed by a radio access network device.

11. The method according to any one of claims 1 to 10, characterized in that The first indication information includes the length information of the redundant padding data, or the position information of the redundant padding data, or the first indication information includes the length information of the payload data of the second message, or the position information of the payload data of the second message.

12. The method according to any one of claims 1 to 10, characterized in that The control plane network element is a session management function network element.

13. A communication device, characterized in that: It comprises a processor and an input / output interface, wherein the processor is connected to the input / output interface; when the processor calls the program code, the method according to any one of claims 1 to 12 is executed.

14. A computer storage medium, characterized in that: The computer storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 12.

15. A computer program product, characterized in that When the method is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 12.

Images