WO2022047675A1 - 一种数据传输方法及其设备 - Google Patents

一种数据传输方法及其设备 Download PDF

Info

Publication number
WO2022047675A1
WO2022047675A1 PCT/CN2020/113070 CN2020113070W WO2022047675A1 WO 2022047675 A1 WO2022047675 A1 WO 2022047675A1 CN 2020113070 W CN2020113070 W CN 2020113070W WO 2022047675 A1 WO2022047675 A1 WO 2022047675A1
Authority
WO
WIPO (PCT)
Prior art keywords
packet
data
redundant
padding
indication information
Prior art date
Application number
PCT/CN2020/113070
Other languages
English (en)
French (fr)
Inventor
余芳
于峰
李岩
倪慧
陈中平
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/113070 priority Critical patent/WO2022047675A1/zh
Priority to EP20951922.2A priority patent/EP4191909A4/en
Priority to CN202080101252.7A priority patent/CN115699629A/zh
Publication of WO2022047675A1 publication Critical patent/WO2022047675A1/zh
Priority to US18/177,458 priority patent/US20230209399A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0097—Relays

Definitions

  • the present application relates to the field of communications, and in particular, to a data transmission method and device thereof.
  • CSMA/CD Carrier Sense Multiple Access with Collision Detection
  • the payload of the application layer message of the industrial application is usually small, for example, 10 bytes or 20 bytes.
  • the size of the message is equal to or greater than 64 bytes.
  • the embodiments of the present application provide a data transmission method and a device thereof, which are used to delete redundant padding data in a packet during Ethernet packet transmission, so that in air interface transmission, the padding redundant data does not need to be transmitted, saving energy
  • the air interface resources are increased, and the air interface capacity is improved.
  • a first aspect of the embodiments of the present application provides a data transmission method.
  • the first device receives the first packet, the payload data in the first packet includes redundant padding data, the first device deletes the redundant padding data, the first device generates a second packet, and the payload data in the second packet is: The payload data filled with redundant data is deleted from the first packet, and the first device sends the second packet to the second device.
  • the first device obtains the second packet by deleting redundant data in the received first packet, and sends the second packet to the second device, so that in subsequent air interface transmissions, the first device obtains the second packet. , there is no need to transmit and fill redundant data, which saves air interface resources and improves air interface capacity.
  • the first device receiving the first indication information, and deleting the redundant padding data by the first device includes that the first device deletes the redundant padding data according to the first indication information. remaining data.
  • the filling redundant data is deleted according to the received indication information, which provides high execution efficiency of the first device and ensures normal transmission of payload data.
  • the first indication information is used to instruct the first network device to delete the redundant padding data, or the first indication information includes the length of the redundant padding data information, or, the location information of the filling redundant data, or, the first indication information includes length information of the payload data of the first downlink packet, or, the location information of the payload data of the first packet.
  • the first indication information is specifically used to indicate the content, which improves the flexibility of the solution.
  • deleting the redundant padding data by the first device includes: the first device deleting the redundant padding data according to the length field of the first packet.
  • the redundant padding data is deleted through the length field of the first packet, which improves the flexibility of the first device to delete the redundant padding data.
  • the first device is a user plane network element UPF
  • the second device is a radio access network device RAN
  • the first packet is a downlink Ethernet packet .
  • the generating of the second packet by the first device includes:
  • the first device encapsulates the third packet according to the N3 tunnel protocol to obtain a fourth packet, wherein the third packet is a packet after the first packet is deleted and filled with redundant data; if the data length of the fourth packet is less than Ethernet minimum frame length, then add tunnel protocol to fill redundant data in the N3 tunnel protocol header of the fourth packet to obtain a second packet, and the data length of the second packet is greater than or equal to the Ethernet minimum frame length; or,
  • the first device determines that the data length of the encapsulated packet obtained by the first device encapsulating the third packet according to the N3 tunneling protocol is smaller than the minimum Ethernet frame length, the first device encapsulates the third packet according to the N3 tunneling protocol to obtain Encapsulate the packet, and add the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated packet to obtain a second packet, and the data length of the second packet is greater than or equal to the minimum frame length of the Ethernet, wherein the third packet Delete the message filled with redundant data for the first message.
  • the second packet is obtained by adding the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the fourth packet, so that the data length of the second packet is greater than or equal to the minimum frame length of the Ethernet. During Ethernet transmission, the risk of errors is reduced.
  • the first device is a radio access network device RAN
  • the second device is a user equipment UE
  • the first packet is a downlink packet.
  • the first device is a user equipment UE
  • the second device is a radio access network device RAN
  • the first packet is an uplink Ethernet packet.
  • the first device is a session management network element SMF
  • the second device is a user equipment UE
  • the first packet is a downlink Ethernet packet.
  • the first device is a user equipment UE
  • the second device is a session management network element SMF
  • the first packet is an uplink Ethernet packet.
  • a second aspect of the embodiments of the present application provides a data transmission method.
  • the third device sends first indication information to the fourth device, where the first indication information is used to delete redundant padding data in the first packet, or the first indication information is used to add redundant padding data to the first packet , the first indication information includes length information of the padded redundant data, or, the position information of the padded redundant data, or, the first indication information includes the length information of the payload data of the first packet, or, the first packet Location information for the payload data.
  • the redundant padding data does not need to be transmitted, which saves air interface resources , which increases the air interface capacity.
  • the third device is the policy control network element PCF
  • the fourth device is the session management network element SMF
  • the first packet is an Ethernet packet
  • the third device is the session management network element SMF
  • the fourth device is the user plane network element UPF
  • the first packet is an Ethernet packet
  • the third device is the session management network element SMF
  • the fourth device is the user equipment UE
  • the first packet is an Ethernet packet
  • the third device is the session management network element SMF, and the fourth device is the radio access network device RAN; or,
  • the third device is a radio access network device RAN
  • the fourth device is a user equipment UE.
  • the third device is SMF
  • the fourth device is UPF
  • the first packet is an Ethernet packet
  • the third device is SMF
  • the fourth device is UE
  • the first packet is an Ethernet packet
  • the third device is the SMF and the fourth device is the RAN.
  • the third device is the policy control network element PCF
  • the fourth device is the session management network element SMF
  • the fifth device is the application function network element AF.
  • 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 padded redundant data, or the position information of the padded redundant data, or, the second indication information is used to indicate the length information of the payload data of the first packet, or, Location information of payload data of the first packet.
  • the first indication information is determined by the second indication information sent by the AF, that is, according to the information of filling the redundant data in the second indication information sent by the AF, the information of the filling of the redundant data in the first indication information is further determined. information and determine the addition, subtraction or deletion operations for filling redundant data, which improves the achievability of the solution.
  • a third aspect of the embodiments of the present application provides a device.
  • a device comprising:
  • a receiving unit configured to receive a first message, where the payload data in the first message includes padding redundant data
  • Delete unit used to delete fill redundant data
  • a generating unit is used to generate a second message, and the load data in the second message is the payload data after deleting the filling redundant data in the first message;
  • the sending unit is configured to send the second message to the second device.
  • the receiving unit is further configured to receive the first indication information
  • the deletion unit is specifically configured to delete the filling redundant data according to the first indication information.
  • the first indication information is used to instruct the device to delete the redundant padding data, or, the first indication information includes length information of the redundant padding data, or, the location information of the redundant padding data, or, the first indication information includes The length information of the payload data of the first downlink packet, or the location information of the payload data of the first packet.
  • the deletion unit is specifically configured to delete the padding redundant data according to the Length field of the first packet.
  • the device is a UPF
  • the second device is a RAN
  • the first packet is a downlink Ethernet packet.
  • the generating unit is specifically configured to encapsulate the third packet according to the N3 tunnel protocol to obtain a fourth packet, wherein the third packet is a packet after the first packet is deleted and filled with redundant data; if the fourth packet is If the data length of the packet is less than the minimum Ethernet frame length, add the tunnel protocol to the N3 tunnel protocol header of the fourth packet to fill redundant data to obtain the second packet, and the data length of the second packet is greater than or equal to the minimum Ethernet frame length. frame length; or,
  • the generating unit is specifically configured to encapsulate the third packet according to the N3 tunneling protocol to obtain Encapsulate the packet, and add the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated packet to obtain a second packet, and the data length of the second packet is greater than or equal to the minimum frame length of the Ethernet, wherein the third packet Delete the message filled with redundant data for the first message.
  • the device is a RAN
  • the second device is a UE
  • the first message is a downlink message.
  • the device is a UE
  • the second device is a RAN
  • the first packet is an uplink Ethernet packet.
  • the device is an SMF
  • the second device is a UE
  • the first packet is a downlink Ethernet packet.
  • the device is a UE, the second device is an SMF, and the first packet is an uplink Ethernet packet.
  • the method performed by the device provided in the third aspect in the embodiment of the present application is similar to the method performed by the first device in the foregoing first aspect, and details are not described herein again.
  • a fourth aspect of the embodiments of the present application provides a device.
  • a device comprising:
  • the sending unit is configured to send the first indication information to the fourth device, wherein the first indication information is used to delete the padding redundant data of the first packet, or the first indication information is used to add padding redundancy to the first packet the remaining data, the first indication information includes length information of the padded redundant data, or, the position information of the padded redundant data, or, the first indication information includes the length information of the payload data of the first packet, or, the first packet The location information of the payload data of the text.
  • the device is PCF
  • the fourth device is SMF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UPF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UE
  • the first packet is an Ethernet packet
  • the device is SMF and the fourth device is RAN; or,
  • the device is the RAN, and the fourth device is the UE.
  • the device is SMF
  • the fourth device is UPF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UE
  • the first packet is an Ethernet packet
  • the device is SMF and the fourth device is RAN.
  • 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
  • the device further includes:
  • the receiving unit is configured to receive second indication information of the fifth device, where the second indication information is used to indicate the length information of the padded redundant data, or the position information of the padded redundant data, or the second indication information is used to indicate the first length information of the payload data of a message, or position information of the payload data of the first message;
  • a determining unit configured to determine the first indication information according to the second indication information.
  • the method performed by the device provided in the fourth aspect in the embodiment of the present application is similar to the method performed by the third device in the foregoing second aspect, and details are not described herein again.
  • a fifth aspect of the embodiments of the present application provides a network device or user equipment, including:
  • a processor, a memory, and an input-output interface, the processor and the memory are connected to the input-output interface; the memory is used to store program codes; the processor executes the first aspect or the first aspect of the present application when calling the program codes in the memory The method provided by the embodiment of the second aspect.
  • a sixth aspect of the embodiments of the present application provides a storage medium.
  • the technical solution of the present invention is essentially or a part that contributes to the prior art, or all or part of the technical solution can be produced by software.
  • the computer software product is stored in a storage medium for storing computer software instructions for the above-mentioned device, which includes a program for executing the data transmission method designed in the above-mentioned first aspect or the second aspect.
  • the storage medium includes: U disk, mobile hard disk, read-only memory (English abbreviation ROM, English full name: Read-Only Memory), random access memory (English abbreviation: RAM, English full name: Random Access Memory), magnetic disk or CD-ROM and other media that can store program codes.
  • a seventh aspect of the embodiments of the present application provides a computer program product including instructions, which, when run on a computer, causes the computer to execute the method according to the implementation of the first aspect or the second aspect of the present application.
  • the processor mentioned in any of the above may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more An integrated circuit for controlling program execution of the data transmission method in the first aspect or the second aspect.
  • CPU Central Processing Unit
  • ASIC application-specific integrated circuit
  • the first device obtains the second packet by deleting the redundant data filled in the received first packet, and sends the second packet to the second device, so that in the subsequent In the transmission of the air interface, the redundant data does not need to be transmitted, which saves the resources of the air interface and improves the capacity of the air interface.
  • FIG. 1 is a schematic diagram of a communication network architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 3 is another schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 4 is another schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 5 is another schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 6 is another schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 8 is another schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a message in a data transmission method provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • FIG. 15 is another schematic structural diagram of a device provided by an embodiment of the application.
  • FIG. 16 is another schematic structural diagram of the device provided by the embodiment of the application.
  • FIG. 17 is another schematic structural diagram of a device provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a communication network architecture according to an embodiment of the present application.
  • the communication network architecture includes a user equipment (User Equipment, UE) 101, a radio access network (RAN) 102, a user plane function (UPF) 103, a data network ( data network, DN) 104, access and mobility management function (AMF) 105, session management function (SMF) 106, policy control function (PCF) 107 , application function (application function, AF) network element, unified data management network element (unified data management, UDM) 108.
  • UE User Equipment
  • RAN radio access network
  • UPF user plane function
  • AMF access and mobility management function
  • SMF session management function
  • PCF policy control function
  • application function application function, AF
  • UDM unified data management network element
  • UE101 and AMF105 communicate through N1 interface
  • UE101 and RAN102 are connected
  • RAN102 and AMF105 are connected through N2 interface
  • RAN102 and UPF103 are connected through N3 interface
  • UPF103 and DN104 are connected through N6 interface
  • UPF103 and SMF106 are connected through N4 interface
  • PCF107 and AF It is connected through N5 interface
  • SMF106 and PCF107 are connected through N7 interface
  • AMF105 and SMF106 are connected through N11 interface
  • AMF105 and UDM108 are connected through N8 interface
  • SMF106 and UDM108 are connected through N10 interface
  • UDM108 and PCF107 are connected through N25 interface.
  • the communication network architecture provided in this application is only an example. In the actual application process, each network unit or user equipment may be one or more, and the connection method is not limited to this. limited.
  • UE refers to network terminal equipment, such as a mobile phone, an Internet of Things terminal equipment, and the like.
  • RAN is a device that provides wireless access for terminal devices, including but not limited to eNodeB, WiFi AP, WiMAX BS, etc.
  • AMF is mainly responsible for the mobility management in the mobile network, such as user location update, user registration network, user handover and so on.
  • SMF is mainly responsible for session management in the mobile network, such as session establishment, modification and release. Specific functions include assigning IP addresses to users, and selecting UPFs that provide packet forwarding functions.
  • PCF is responsible for providing policies to AMF and SMF, such as Quality of Service (QoS) policies, slice selection policies, and so on.
  • QoS Quality of Service
  • UDM is used to store user data, such as subscription information, authentication or authorization information.
  • the AF is responsible for providing services to the 3GPP network, such as influencing service routing, interacting with the PCF for policy control, and so on.
  • UPF is mainly responsible for processing user packets, such as forwarding and accounting.
  • DN refers to an operator network that provides data transmission services for users, such as IP Multi-media Service, Internet, etc.
  • the communication network architecture also includes a network capability 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. , to transfer information between third parties, application servers and communication systems.
  • NEF network capability exposure function
  • the data processing methods provided in the embodiments of the present application have various implementation manners. Hereinafter, various cases will be described respectively.
  • FIG. 2 is a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • step 201 the user equipment establishes a protocol data unit (Protocl Data Unit, PDU) session.
  • PDU Protocol Data Unit
  • the PDU session is used to transmit user plane data between the UE and the application server.
  • N3 tunnel is established between the NG-RAN and the UPF for the PDU session.
  • N3 tunnel refers to the tunnel between UPF and RAN.
  • the application server can be a production line controller or other industrial node in the industrial network.
  • step 202 the application function network element sends an AF request message to the policy control network element.
  • the application function network element 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 (AF request) message to the policy control network element, for example, the establishment of the PDU session between the user equipment and the application server is completed. After that, the application server will trigger the application function network element to send the application function network element request message, wherein 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, where the second indication information is used to indicate information related to redundant data filling of packets of the service described by the service description information.
  • the second indication information may indicate length information of the padding redundant data.
  • the length information of the redundant padding data may be the length of the redundant data (padding) in the payload field of the packet.
  • the second indication information may further indicate location information for filling redundant data.
  • the position information of the redundant data padding may be the start position and the end position of the redundant data padding in the payload field of the message.
  • the second indication information may further indicate length information of payload data of the packet.
  • the length information of the payload data of the packet may be the length of the payload data in the packet payload field.
  • the second indication information may also indicate location information of payload data of the packet.
  • the location information of the payload data of the message may be the start location and the end location of the payload data in the payload field of the message.
  • the second indication information may include one of length information of the padded redundant data, position information of the padded redundant data, length information of the payload data, or position information of the payload data, or multiple.
  • the padding redundant data is added at a media access control (Media Access Control, MAC) layer by the sending end of the Ethernet packet.
  • Media Access Control Media Access Control
  • the redundant padding data is added by the sending end of the Ethernet packet at a high layer, where the high layer refers to a protocol layer above the MAC layer, such as an application layer.
  • the service description information includes (data network name, 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 a DNN, the second indication information is applicable to service packets of all applications of the DNN; if the service description information includes an application identifier, the second indication information is applicable to the application identifier corresponding to the application. message; if the service description information includes service filtering information, the second indication information is applicable to the message corresponding to the service filtering information.
  • the service filtering information is Ethernet packet filtering information, which may specifically include at least one of a source MAC address, a destination MAC address, and a VLAN identifier of the service packet.
  • the AF request message may be directly sent to the policy control network element, or may be sent to the NEF first, and then forwarded to the policy control network element by the NEF, which is not specifically limited here.
  • step 203 the policy control network element sends a policy update message to the session management network element.
  • the policy control network element After the policy control network element receives 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 (Service Data Flow, SDF) template in the AF request message, and according to the second indication The information generates first indication information, and the first indication information and the SDF template are carried in the policy update message, and sent 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 padding data of the packet of the service described by the SDF template.
  • the policy update message includes a PCC rule
  • the PCC rule further includes first indication information and an SDF template.
  • the first indication information may further indicate the length information of the first padding redundant data padding the redundant data.
  • the length information of the first padding redundant data padding redundant data may be the length of the padding redundant data (padding) in the packet payload (payload) field.
  • the first indication information may further indicate the location information of the redundant data filled with the first filled redundant data.
  • the position information of the first filling redundant data filling redundant data may be a start position and an ending position of the filling redundant data in the payload field of the message.
  • the first indication information may further indicate length information of payload data of the packet.
  • 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.
  • the first indication information may also indicate location information of payload data of the packet.
  • the location information of the payload data of the message may be the start location and the end location of the payload data in the payload field of the message.
  • the first indication information may include one of length information of the padded redundant data, position information of the padded redundant data, length information of the payload data, or position information of the payload data, or If the first indication information includes one or more of the above information, the device that receives the first indication information may add or delete the filling redundant data according to the first indication information. Or, in a possible implementation manner, the first indication information may further include an indication to add or delete padding redundant data, which is used to instruct the device receiving the first indication information to The first indication information adds or deletes filling redundant data. Or, in a possible implementation manner, the first indication information only includes an indication to add or delete the filling redundant data, and the device that receives the first indication information will receive the service message according to the first indication Indicates information to add or delete padding redundant data.
  • the SMF After the session management network element SMF receives the policy update message, the SMF performs session management according to the policy update message.
  • the SMF binds the Policy and Charging Control (PCC) rule obtained from the policy update message to an existing QoS flow (QoS Flow), or derives QoS according to the parameters in the PCC rule After the parameters generate a new QoS Flow, the PCC rules are bound to the QoS Flow.
  • PCC Policy and Charging Control
  • the PCC rule includes first indication information and an SDF template, and binding the PCC rule to the QoS Flow can be understood as applying the PCC rule to the QoS Flow, that is, one or more service flows corresponding to the SDF template in the PCC rule are all Binding 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 length information of the padding redundant data included in the first indication information is the same.
  • step 204 the session management network element sends an N4 session modification request to the user plane network element.
  • 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 SDF template is included in the PDR.
  • 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.
  • 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 packets, and when it matches the service filtering information, performs corresponding packet forwarding actions according to the first indication information in the FAR, such as deleting redundant padding data or adding redundant padding data.
  • the first indication information included in the FAR includes an instruction to delete the filling redundant data; when the packet filter in the SDF template When the corresponding service is an uplink service, the first indication information included in the FAR includes an indication of adding padding redundant data.
  • step 205 the session management network element sends an N1 interface session management message to the user equipment.
  • 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, and the QoS rule includes a QoS Flow identifier, and also includes the first indication information and The QoS Flow identifies the corresponding Packet Filer Set.
  • the SMF sends the QoS rules to the user equipment UE through the N1 interface session management information.
  • 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 that the user equipment should
  • the first indication information is for the QoS Flow identified by the QoS Flow identification.
  • 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.
  • 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 include the QoS Rule.
  • the first indication information 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 instruction to delete and fill redundant data; When the service corresponding to the packet filter in the packet filter set is a downlink service, the first indication information includes an indication of adding padding redundant data.
  • step 204 and step 205 The execution order of step 204 and step 205 is not limited. It can be that the SMF initiates the PDU session modification process after step 203. In the PDU session modification process, step 205 is performed first, and then step 204 is performed; or step 204 can be performed first, and then step 205 can be performed; or step 204 can be performed at the same time and step 205, which is not specifically limited here. 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 instruct deletion of redundant padding data, and the first indication information in step 205 is used to instruct adding redundant padding data. Alternatively, the first indication information in step 204 is used to instruct adding redundant padding data, and the first indication information in step 205 is used to instruct deletion of redundant padding data.
  • step 206 the user plane network element receives the first packet.
  • the first packet is an Ethernet packet.
  • the user plane network element When the downlink data is transmitted, the user plane network element will receive one or more downlink first packets, and the one or more first packets correspond to a QoS Flow identifier.
  • the first packet is in an Ethernet II frame format.
  • the first packet includes a preamble field, a Start Frame Delimiter (SFD) field, a destination MAC address field, a source MAC address field, a type field, and a data payload. field, the Frame Check Sequence (FCS) field.
  • the data payload field includes a payload field, and also includes a padding field.
  • the first packet is in an Ethernet IEEE 802.3 frame format.
  • the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a length field, and a Logic Link Control (LLC) field, Data payload field, FCS field.
  • LLC Logic Link Control
  • the data payload field includes a payload field, and also includes a padding field.
  • step 207 the user plane network element deletes the padding redundant data in the first packet.
  • the user plane network element After the user plane network element receives the first packet, the user plane network element deletes the padding redundant data in the first packet.
  • the user plane network element detects the received first packet, and determines, according to the PDR received in step 204, that the first packet matches the PDR received in step 204, and determines that the first packet matches the PDR received in step 204, according to the FAR received in step 204.
  • the first indication information deletes padding redundant data.
  • the user plane network element deletes the padding redundant data in the first packet according to the first indication information.
  • the user plane network element deletes the redundant padding data in the payload part of the first packet according to the length information of the redundant padding data.
  • the user plane network element may determine the end position of the redundant padding data according to the frame format in FIG. 8 or FIG. 9 , and then determine the redundant padding data length according to the length of the redundant padding data included in the first indication information. The starting position of the data, and then the filling redundant data can be deleted according to the starting position and the ending position.
  • the user plane network element finds the starting position and the starting position of filling redundant data from the payload part of the first packet according to the location information for filling redundant data. End position, delete the data from the start position to the end position.
  • the user plane network element deletes the data except the payload data in the payload part of the first packet according to the length information of the payload data, that is, Remove padding redundant data.
  • the user plane network element may determine the end position of the redundant padding data according to the frame format in FIG. 8 or FIG. 9 , and then determine the redundant padding data length according to the length of the redundant padding data included in the first indication information. The starting position of the data, and then the filling redundant data can be deleted according to the starting position and the ending position.
  • the user plane network element finds out the start location and the end location of the payload data from the payload part of the first packet according to the location information of the payload data , and delete the data beyond the start position of the payload data to the end position, that is, delete the redundant data padding.
  • the user plane network element can determine the position of the filling redundant data in the first packet according to the first indication information, and can also determine the position of the filling redundant data in the first packet according to the first indication
  • the Length field determines the position of the redundant padding data in the first packet, and then deletes the redundant padding data in the first packet according to the position of the redundant padding data in the first packet.
  • the data other than the payload data corresponding to the Length field in the payload part of the first packet is deleted according to the Length field, that is, the padding redundant data is deleted.
  • the first indication information may only include one of the length information of the padded redundant data, the position information of the padded redundant data, the length information of the payload data, or the position information of the payload data. Or more, when the first indication information includes one or more of the above information, the user plane network element may delete the filled redundant data according to the first indication information. Or, in a possible implementation manner, the first indication information may further include an indication that the redundant padding data is to be deleted, for instructing the user plane network element to delete the redundant padding data according to the first indication information. Or, in a possible implementation manner, the first indication information only includes an indication that the redundant padding data is to be deleted, and the user plane network element deletes the redundant padding data according to the first indication information.
  • step 208 the user plane network element generates a second packet, and sends the second packet to the wireless access network device.
  • the user plane network element After the user plane network element deletes the redundant padding data of the first packet, the user plane network element generates a second packet, and the payload data in the second packet is after the redundant padding data in the first packet is deleted. The payload data is sent, and the second packet is sent to the wireless access network device.
  • the user plane network element after the user plane network element deletes the redundant padding data of the first packet, it encapsulates the first packet from which the redundant padding data is deleted according to the N3 tunneling protocol to obtain the second packet.
  • the N3 tunneling protocol here may be a general packet radio service tunneling protocol user plane (general packet radio service tunneling protocol user plane, GTP-U) protocol. It can be understood that in practice, In the application process, other tunnel protocols may also be used, which are not specifically limited here.
  • the user plane network element before the user plane network element encapsulates the first packet with redundant data deleted according to the N3 tunneling protocol, and before obtaining the second packet, the user plane network element also deletes the preamble field in the first packet. , SFD field and FCS field. 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 radio access network equipment and the user equipment.
  • the format of the first packet is the Ethernet II frame format shown in FIG. 8, and the first packet includes a padding field
  • the format of the second packet is as shown in FIG. 10, where the second packet is
  • the destination MAC address field, source MAC address field, type field and payload field of the message are the same as the corresponding fields in the first message; and the N3 tunneling protocol header field includes the N3 MAC header field and the IP header field in Figure 10. , UDP header fields, and GTP-U header fields.
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 10 is different from the first packet.
  • the FCS field in Figure 10 is calculated by the user plane network element according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header field in Figure 10 , IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.
  • the format of the first packet is the IEEE 802.3 frame format shown in Figure 9
  • the format of the second packet is as shown in Figure 11, wherein the destination MAC address field, source MAC address field, Length field, The LLC field and the payload field are the same as the corresponding fields in the first message; and the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field, and GTP-U header field in FIG. 11 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 11 is different from the first packet.
  • the FCS field in Figure 11 is calculated by the user plane network element according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header field in Figure 11 , IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field, and payload field.
  • the data length of the entire packet may be smaller than the minimum Ethernet frame length, for example, less than 64 bytes.
  • the data length of the second packet will be greater than or equal to 64 bytes. Therefore, the Ethernet packet conforming to the protocol must meet the minimum Ethernet frame length requirements.
  • the data length of the first message is the sum of the lengths of the remainder of the message format excluding the preamble field, the SFD field and the FCS field in the message format shown in FIG. 8 or FIG. 9
  • the data length of the second message is The sum of the lengths of the remaining parts of the N3MAC header field and the FCS field is not included in the message format shown in FIG. 10 or FIG. 11 .
  • the N3 tunneling protocol may use a more simplified protocol stack.
  • the N3 tunneling protocol does not use the UDP, IP, and GTP-U protocol layers shown in FIG. 10 or FIG. 11
  • the GTP-U layer is used, for example, only the GTP-U layer is used, that is, the second packet does not include the P header field and the UDP header field shown in Figure 10 or Figure 11, or the second packet does not include Figure 10 or
  • the data length of the second packet may be less than 64 bytes. In this case, there are two ways:
  • Mode 1 The user plane network element encapsulates the third packet according to the N3 tunneling protocol to obtain the fourth packet. If the data length of the fourth packet is less than the minimum Ethernet frame length, the N3 tunneling protocol header of the fourth packet The tunnel protocol is added to fill redundant data to generate a second packet, and the data length of the second packet is greater than or equal to the minimum frame length of the Ethernet.
  • Method 2 If the user plane network element determines that the data length of the encapsulated packet obtained by encapsulating the third packet according to the N3 tunnel protocol is smaller than the minimum Ethernet frame length, the user plane network element will perform the encapsulation of the third packet according to the N3 tunnel protocol. An encapsulated packet is obtained by encapsulation, and the tunnel protocol padding redundant data is added to the N3 tunnel protocol header of the encapsulated packet to generate a second packet, and the data length of the second packet is greater than or equal to the minimum Ethernet frame length.
  • the user plane network element receives third indication information from the session management network element before performing the operation in the above-mentioned manner 1 or manner 2, where the third indication information is used to indicate that the user plane network element is sending the message over the N3 tunnel.
  • the Ethernet frame length of the packets is checked. When the Ethernet frame length of the packets is less than 64 bytes, the tunnel protocol is added to fill redundant data.
  • the third indication information may be carried in the N4 session modification request.
  • the third packet in the above methods 1 and 2 is the packet after the first packet is deleted and filled with redundant data. It should be noted that after the user plane network element deletes the filled redundant data in the first packet, the A third packet is generated, and then a fourth packet or a second packet is generated according to the third generated packet. The process of generating the third packet may not be included, and the process is directly performed on the first packet after deleting the redundant data operate.
  • the N3 tunneling protocol refers to the tunneling protocol between the user plane network element and the access network node
  • the N3 tunneling protocol in the present invention may be used for other possible transmissions between the user plane network element and the access network node. Tunneling protocol replacement for data.
  • step 209 the wireless access network device sends a fifth packet to the user equipment.
  • the wireless access network device After the wireless access network device receives the second packet sent by the user plane network element, the wireless access network device strips the N3 tunnel protocol header in the second packet, and adds the air interface protocol header to generate a fifth packet , and send the fifth packet to the user equipment.
  • the format of the first packet is the Ethernet II frame format shown in FIG. 8
  • the format of the fifth packet is as shown in FIG. 12 , wherein the destination MAC address field and the source MAC address of the fifth packet are Field, type field and payload field are all the same as the corresponding fields in the second message;
  • the AN protocol header in Figure 12 is also called the air interface protocol header, exemplary, and can specifically include, packet data convergence protocol (packet data convergence protocol, PDCP) header, Radio Link Control (Radio Link Control, RLC) header and MAC header.
  • packet data convergence protocol packet data convergence protocol
  • RLC Radio Link Control
  • the format of the first packet is the IEEE 802.3 frame format shown in Figure 9
  • the format of the fifth packet is shown in Figure 7, wherein the destination MAC address field, source MAC address field, Length field, LLC of the fifth packet
  • the fields and payload fields are the same as the corresponding fields in the second message;
  • the AN protocol header in FIG. 7 is also called the air interface protocol header, which may specifically include a PDCP header, an RLC header, and a MAC header.
  • the wireless access network device sends packets to the user equipment through air interface transmission, which is not limited by the minimum frame length of Ethernet. Therefore, after stripping the N3 tunnel protocol header, the length of the second packet is If it is less than 64 bytes, that is, the length of the fifth packet is less than 64 bytes, it can also be transmitted. And because in the previous steps, the redundant padding data in the payload part of the first packet has been deleted, that is to say, the payload part of the fifth packet does not include redundant padding data, so the air interface can be saved during air interface transmission. resource.
  • the application layer of the user equipment may directly acquire and use the payload data part of the fifth packet.
  • the user equipment when the user equipment is an intermediate node of the network and needs to continue to forward the Ethernet frame to the next hop node, the user equipment supplements and fills the load part of the fifth packet with redundant data. , and generate a sixth packet, so that the data length of the sixth packet is greater than or equal to 64 bytes.
  • the user plane network element if the user plane network element encapsulates the first packet with the redundant data deleted according to the N3 tunneling protocol and obtains the second packet, the user plane network element also encapsulates the second packet.
  • the user equipment also needs to supplement other fields to generate the sixth message, such as the FCS field, the preamble field and the SFD field, which is not limited here.
  • the format of the sixth packet may be the same as that of the first packet, that is, if the first packet is the Ethernet II frame format shown in FIG. 8 , the sixth packet is also the Ethernet Ethernet For the type II Ethernet frame, if the first packet format is the IEEE 802.3 frame format shown in FIG. 9 , the sixth packet is also an IEEE 802.3 type Ethernet frame.
  • the data length of the sixth packet is the same as the data length of the first packet after the padding redundant data is supplemented.
  • the data length of the first message or the sixth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the sixth packet is the same as the first packet.
  • the user equipment may fill each bit of the redundant data padding in the sixth packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the user equipment may supplement and fill redundant data in the payload part of the fifth packet according to the first indication information to generate a sixth packet, so that the data length of the sixth packet is greater than or equal to 64 bytes.
  • the user equipment fills the redundant padding data into the payload part of the fifth packet according to the length information of the redundant padding data.
  • the user equipment finds the starting position of the redundant data filling to be filled from the load part of the fifth packet according to the position information of the redundant data filling And the end position, fill the redundant data to the corresponding position.
  • the user equipment fills the payload part of the fifth packet with the redundant padding data according to the length information of the payload data.
  • the user equipment finds out the start location and the end location of the payload data from the payload part of the fifth message according to the location information of the payload data, and The padding redundant data is filled to the position after the end position of the payload data and before the FCS field.
  • the user equipment determines to add redundant padding data according to the first indication information, and according to the Ethernet minimum frame specified by the protocol long, the fifth packet is filled with redundant data.
  • step 210 the user equipment receives a seventh packet, where the seventh packet is an uplink Ethernet packet.
  • the seventh packet is an Ethernet packet.
  • the user equipment When uplink data is transmitted, the user equipment will acquire one or more uplink Ethernet packets, where the uplink Ethernet packet is the seventh packet.
  • the user equipment When the user equipment has a previous hop node, the user equipment receives an uplink Ethernet packet sent by the previous hop node.
  • the user equipment When the user equipment does not have a previous hop node, the user equipment generates an uplink Ethernet packet.
  • the upstream Ethernet packet is in an Ethernet Ethernet II frame format.
  • the upstream Ethernet packet includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • the upstream Ethernet packet is in an Ethernet IEEE802.3 frame format.
  • the upstream Ethernet packet 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 payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • step 211 the user equipment deletes the redundant padding data in the seventh packet.
  • the user equipment After the user equipment acquires the seventh packet, the user equipment deletes the padding redundant data in the seventh packet.
  • the user equipment deletes the padding redundant data in the seventh packet according to the first indication information.
  • the user equipment deletes the redundant padding data in the payload part of the seventh packet according to the length information of the redundant padding data.
  • the user equipment finds the start position and the end position of the filled redundant data from the load part of the seventh packet according to the position information of the filled redundant data. , delete the data from the start position to the end position.
  • the user equipment deletes the data except the payload data in the payload part of the uplink Ethernet message according to the length information of the payload data, that is, deletes the padding. redundant data.
  • the user equipment finds out the start position and the end position of the payload data from the payload part of the seventh packet according to the position information of the payload data, and Delete the data beyond the start position to the end position of the payload data, that is, delete the padding redundant data.
  • the user equipment element may determine the position of the padding redundant data in the seventh packet according to the first indication information, and may also determine according to the length (Length) field
  • the position of the padding redundant data in the seventh packet is deleted, and the padding redundant data in the seventh packet is deleted according to the position of the padding redundant data in the seventh packet.
  • the data except the payload data corresponding to the Length field in the payload part of the seventh packet is deleted according to the Length field, that is, the redundant padding data of the seventh packet is deleted.
  • step 212 the user equipment generates an eighth packet, and sends the eighth packet to the wireless network device.
  • the user equipment After deleting the redundant padding data of the seventh packet, the user equipment generates an eighth packet, and the payload data in the eighth packet is the payload data after deleting the redundant padding data in the seventh packet.
  • the user equipment after deleting the redundant padding data of the seventh packet, the user equipment encapsulates the seventh packet from which the redundant padding data is deleted according to the air interface protocol, to obtain the eighth packet.
  • the format of the eighth packet is as shown in FIG. 12, wherein the eighth packet is The destination MAC address field, source MAC address field, type field, and payload field of the message are the same as the corresponding fields in the received seventh message;
  • the AN protocol header in FIG. 12 is also called the air interface protocol header, an exemplary Yes, it may specifically include the PDCP header, the RLC header, and the MAC header.
  • the format of the eighth packet is the IEEE802.3 frame format shown in FIG. 9, the format of the eighth packet is as shown in FIG. 7, wherein the destination MAC address field, source MAC address field, and Length field of the eighth packet are , LLC field and payload field are the same as the corresponding fields in the received seventh message;
  • the AN protocol header in Fig. 7 is also called the air interface protocol header, exemplary, specifically may include, PDCP header, RLC header and the MAC header.
  • the user equipment After generating the eighth packet, the user equipment sends the eighth packet to the wireless access network device.
  • the user equipment in addition to deleting the redundant padding data in the seventh packet, the user equipment also deletes the preamble field, the SFD field and the FCS field in the seventh packet. That is, the preamble field, the SFD field, and the FCS field in the seventh packet are not transmitted between the user equipment, the radio access network equipment, and the user plane network element.
  • the method of sending packets from the user equipment to the wireless access network equipment is the air interface transmission method, which is not limited by the minimum frame length of Ethernet. Therefore, the data length of the uplink Ethernet packet is less than 64 bytes. transmission. And because in the previous steps, the padding redundant data in the payload part of the seventh packet has been deleted, that is to say, the payload part of the eighth packet does not include padding redundant data, so during air interface transmission, the air interface can be saved. resource.
  • step 213 the wireless access network device sends the ninth packet to the user plane network element.
  • the wireless access network device After the wireless access network device receives the eighth packet sent by the user equipment, the wireless access network device strips the air interface protocol header in the eighth packet, and adds the N3 tunnel protocol header to generate the ninth packet, and send it to the wireless access network device.
  • the user plane network element sends the ninth packet.
  • the format of the ninth packet is as shown in FIG. 10 , wherein the destination MAC address field and the source MAC address of the ninth packet are The field, type field and payload field are the same as the corresponding fields in the eighth message; and the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field and GTP-U header field in Figure 10 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 10 is different from the first packet.
  • the FCS field in Figure 10 is calculated by the radio access network device according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header in Figure 10 field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.
  • the format of the ninth packet is as shown in Figure 11, wherein the destination MAC address field, source MAC address field, Length field, The LLC field and the payload field are the same as the corresponding fields in the eighth packet; and the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field and GTP-U header field in FIG. 11 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 11 is different from the first packet.
  • the FCS field in Figure 11 is calculated by the radio access network device according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header in Figure 11 field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field, and payload field.
  • the data length of the eighth packet may be less than the minimum Ethernet frame length, for example, less than 64 bytes.
  • the data length of the ninth packet may be greater than or equal to 64 bytes.
  • Minimum frame length requirements the data length of the seventh message is the sum of the lengths of the remainder of the message format excluding the preamble field, the SFD field and the FCS field in the message format shown in FIG. 8 or FIG. 9
  • the data length of the ninth message is The sum of the lengths of the remainder of the N3 MAC header field and the FCS field is not included in the message format shown in FIG. 10 or FIG. 11 .
  • the wireless access network device encapsulates the eighth packet according to the N3 tunneling protocol to obtain the ninth packet.
  • the N3 tunneling protocol here may be the GTP-U protocol. It can be understood that in the actual application process, it may also be other N3 tunneling protocols, which is not specifically limited here.
  • the N3 tunneling protocol may use a more simplified protocol stack. Exemplarily, if the N3 tunneling protocol does not use the UDP, IP and GTP-U protocol layers shown in FIG. 10 or FIG.
  • the ninth packet does not include the IP header field and the UDP header field shown in Figure 10 or Figure 11, or the second packet does not include Figure 10
  • the data length of the ninth packet may be less than 64 bytes, in this case, there are two ways:
  • Mode 1 The wireless access network device encapsulates the eighth packet according to the N3 tunnel protocol to obtain the tenth packet. If the data length of the tenth packet is less than the minimum Ethernet frame length, the N3 tunnel protocol of the tenth packet is used. The tunnel protocol is added to the header to fill redundant data to generate a ninth packet, and the data length of the ninth packet is greater than or equal to the minimum frame length of the Ethernet.
  • Method 2 If the wireless access network device determines that the data length of the encapsulated packet obtained by encapsulating the eighth packet according to the N3 tunnel protocol is smaller than the minimum frame length of the Ethernet, the user plane network element according to the N3 tunnel protocol. The packet is encapsulated to obtain an encapsulated packet, and the tunnel protocol padding redundant data is added to the N3 tunnel protocol header of the encapsulated packet to generate a ninth packet, and the data length of the ninth packet is greater than or equal to the minimum Ethernet frame length.
  • the wireless access network device receives second indication information from the session management network element before performing the operation in the above-mentioned manner 1 or manner 2, where the second indication information is used to indicate that the wireless access network equipment is in the N3
  • the Ethernet frame length of the packets sent by the tunnel is checked.
  • the tunnel protocol is added to fill in redundant data.
  • the second indication information may be carried when the session management network element sends the control plane message to the wireless access network device.
  • the wireless access network device in the above method 1 first generates the tenth packet, and then generates the ninth packet according to the tenth generation packet.
  • the eighth message generates the ninth message.
  • the N3 tunneling protocol refers to the tunneling protocol between the user plane network element and the access network node
  • the N3 tunneling protocol in the present invention may be used for other possible transmissions between the user plane network element and the access network node. Tunneling protocol replacement for data.
  • step 214 the user plane network element adds the padding redundant data of the ninth packet.
  • the user plane network element strips the N3 tunnel protocol header and adds padding redundant data to generate the eleventh packet, so that the data length of the eleventh packet is greater than or equal to It is equal to 64 bytes.
  • the user plane network receives the ninth packet
  • the user plane network element strips the N3 tunnel protocol header and adds padding redundant data to generate the eleventh packet, so that the data length of the eleventh packet is greater than or equal to It is equal to 64 bytes.
  • the user plane network also supplements other fields to generate the eleventh message, such as the FCS field, the preamble field and the SFD field, which are not specifically limited here.
  • the format of the eleventh packet is the same as that of the seventh packet, that is to say, if the seventh packet is the Ethernet II frame format shown in Figure 8, the eleventh packet is also of Ethernet II type.
  • the eleventh packet is also an IEEE 802.3 type Ethernet frame.
  • the data length of the eleventh packet is the same as the data length of the seventh packet.
  • the data length of the seventh message or the eleventh message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the eleventh packet is the same as the seventh packet.
  • the user equipment may fill each bit of the redundant data padding in the eleventh packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the user plane network element may supplement and fill redundant data in the payload part of the ninth packet according to the first indication information to generate an eleventh packet, so that the eleventh packet is The data length of the text is greater than or equal to 64 bytes.
  • the user plane network element pads the redundant padding data into the payload part of the ninth packet according to the length information of the redundant padding data.
  • the user plane network element finds the filled redundant data to be filled from the load part of the ninth packet according to the location information of the filled redundant data. Start position and end position, fill the filling redundant data to the corresponding position.
  • the user plane network element fills the payload portion of the ninth packet with redundant padding data according to the length information of the payload data.
  • the user plane network element finds out the start location and the end location of the payload data from the payload part of the ninth packet according to the location information of the payload data. , and fill the padding redundant data to the position after the end position of the payload data and before the FCS field.
  • the user plane network element determines to add redundant padding data according to the first indication information, and according to the Ethernet protocol specified Minimum frame length, the ninth packet is filled with redundant data.
  • step 215 the user plane network element sends the eleventh packet.
  • the user plane network element sends the eleventh packet to the next hop node.
  • steps 206 to 209 are application scenarios for sending downlink packets
  • steps 210 to 215 are application scenarios for sending uplink packets.
  • steps 206 to 209 may be implemented independently, and steps 210 to 215 may also be implemented independently, or may be implemented in combination, which is not specifically limited here.
  • the user plane device deletes the redundant padding data in the received downlink packet, so that the downlink packet transmitted to the user equipment on the air interface does not include the redundant padding data, that is, the redundant padding data does not need to be transmitted , which saves air interface resources and improves air interface capacity.
  • the user equipment deletes the padding redundant data in the received uplink packet, so that the uplink packet transmitted to the wireless access network device on the air interface does not include the padding redundant data, that is, the padding does not need to be transmitted. Redundant data saves air interface resources and improves air interface capacity.
  • FIG. 3 is another schematic flowchart of an embodiment of the present application.
  • step 301 the user equipment establishes a PDU session.
  • step 302 the application function network element sends an AF request message to the policy control network element.
  • step 303 the policy control network element sends a policy update message to the session management network element.
  • step 304 the session management network element sends an N4 session modification request to the user plane network element.
  • steps 301 to 304 are similar to the methods performed in steps 201 to 204 in the aforementioned embodiment shown in FIG. 2 , and details are not described herein again.
  • step 305 the session management network element sends an N2 interface session management message to the wireless access network device.
  • the session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS profile (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 QoS Flow identifier to the wireless access network device through the N2 interface session management information.
  • 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 first indication information of the radio access network device is the QoS Flow identified by the QoS Flow identifier.
  • N2 interface session management message here is sent by the SMF to the wireless access network device through the AMF.
  • step 304 and step 305 are not limited. It can be that the SMF initiates a PDU session modification process after step 303. In the PDU session modification process, step 305 is performed first, and then step 304 is performed; or step 304 may be performed first, and then step 305 may be performed; or step 304 may be performed at the same time and step 305, which is not specifically limited here.
  • the first indication information included in step 304 and step 305 may be different.
  • the first indication information in step 304 is used to instruct deletion of redundant padding data
  • the first indication information in step 305 is used to instruct adding redundant padding data.
  • the first indication information in step 304 is used to instruct adding redundant padding data
  • the first indication information in step 305 is used to instruct deletion of redundant padding data.
  • the radio access network device sends radio resource control (Radio Resource Control, RRC) reconfiguration signaling to the user equipment.
  • RRC Radio Resource Control
  • 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 information to the user equipment. make.
  • step 307 the user plane network element receives the first packet.
  • step 308 the user plane network element deletes the redundant padding data in the first packet.
  • step 309 the user plane network element generates a second packet, and sends the second packet to the wireless access network device.
  • step 310 the wireless access network device sends a fifth packet to the user equipment.
  • step 311 the user equipment receives a seventh packet, where the seventh packet is an uplink Ethernet packet.
  • step 312 the user equipment deletes the padding redundant data in the seventh packet.
  • step 313 the user equipment generates an eighth packet, and sends the eighth packet to the wireless network device.
  • step 314 the wireless access network device sends a ninth packet to the user plane network element.
  • step 315 the user plane network element adds the padding redundant data of the ninth packet.
  • step 316 the user plane network element sends the eleventh packet.
  • steps 307 to 316 are similar to the methods performed in steps 206 to 215 in the aforementioned embodiment shown in FIG. 2 , and details are not described herein again.
  • steps 307 to 310 are application scenarios for sending downlink packets
  • steps 311 to 316 are application scenarios for sending uplink packets.
  • steps 307 to 310 may be implemented independently, and steps 311 to 316 may also be implemented independently, or may be implemented in combination, which is not specifically limited here.
  • the user plane device deletes the redundant padding data in the received downlink packet, so that the downlink packet transmitted to the user equipment on the air interface does not include the redundant padding data, that is, the redundant padding data does not need to be transmitted , which saves air interface resources and improves air interface capacity.
  • the user equipment deletes the padding redundant data in the received uplink packet, so that the uplink packet transmitted to the wireless access network device on the air interface does not include the padding redundant data, that is, the padding does not need to be transmitted. Redundant data saves air interface resources and improves air interface capacity.
  • FIG. 4 is another schematic flowchart of the data transmission method provided by the embodiment of the present application.
  • step 401 the user equipment establishes a PDU session.
  • step 402 the application function network element sends an AF request message to the policy control network element.
  • step 403 the policy control network element sends a policy update message to the session management network element.
  • steps 401 to 403 are similar to the methods performed in steps 301 to 303 in the foregoing embodiment shown in FIG. 3 , and details are not described herein again.
  • step 404 the session management network element sends an N2 interface session management message to the wireless access network device.
  • the session management network element obtains the first indication information and the SDF template in the policy update message, and generates a QoS profile (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 QoS Flow identifier to the wireless access network device through the N2 interface session management information.
  • 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 first indication information of the radio access network device is the QoS Flow identified by the QoS Flow identifier.
  • N2 interface session management message here is sent by the SMF to the wireless access network device through the AMF.
  • step 405 the session management network element sends an N1 interface session management message to the user equipment.
  • 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, and the QoS rule includes a QoS Flow identifier, and also includes the first indication information and QoS Flow identifies the corresponding packet filtering set.
  • the SMF sends the QoS rules to the user equipment UE through the N1 interface session management information.
  • 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 that the user equipment should
  • the first indication information is for the QoS Flow identified by the QoS Flow identification.
  • 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.
  • 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 include the QoS Rule.
  • step 404 and step 405 are not limited. It can be that the SMF initiates a PDU session modification process after step 403. In the PDU session modification process, step 405 is executed first, and then step 404 is executed; or step 404 can be executed first, and then step 405 can be executed; or step 404 can be executed at the same time and step 405, which is not specifically limited here.
  • the first indication information included in step 404 and step 405 may be different.
  • the first indication information in step 404 is used to instruct deletion of redundant padding data
  • the first indication information in step 405 is used to instruct adding redundant padding data.
  • the first indication information in step 404 is used to instruct adding redundant padding data
  • the first indication information in step 405 is used to instruct deletion of redundant padding data.
  • the first indication information and the QoS Flow identifier may also be sent to the user equipment through the radio access network device RAN, which is similar to the method performed in step 306 in the above-mentioned embodiment shown in FIG. 3 . , and details are not repeated here.
  • step 405 is not performed.
  • step 406 the user plane network element receives the first packet.
  • step 407 the user plane network element sends a twelfth packet to the wireless access network device.
  • the user plane network element After receiving the first packet, the user plane network element encapsulates the first packet according to the N3 tunneling protocol to obtain a twelfth packet.
  • the N3 tunneling protocol here may be the GTP-U protocol. It can be understood that in the actual application process, it may also be other tunneling protocols, which are not specifically limited here.
  • the format of the twelfth packet is as shown in FIG. 10, where the tenth
  • the destination MAC address field, source MAC address field, type field and payload field of the two messages are the same as the corresponding fields in the first message
  • the N3 tunnel protocol header field includes the N3 MAC header field, IP header field, UDP header field, and GTP-U header field.
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 10 is different from the first packet.
  • the FCS field in Figure 10 is calculated by the user plane network element according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header field in Figure 10 , IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.
  • the format of the first packet is the IEEE 802.3 frame format shown in Figure 9
  • the format of the twelfth packet is as shown in Figure 11, wherein the destination MAC address field, source MAC address field, Length of the twelfth packet field, LLC field and payload field are the same as the corresponding fields in the first message
  • the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field and GTP-U header field in Figure 11 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 11 is different from the first packet.
  • the FCS field in Figure 11 is calculated by the user plane network element according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header field in Figure 11 , IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field, and payload field.
  • the user plane network element before the user plane network element encapsulates the first packet according to the N3 tunneling protocol to obtain the twelfth packet, the user plane network element also deletes the preamble field, the SFD field and the FCS field in the first packet. That is, the preamble field, the SFD field, and the FCS field in the first packet are not transmitted between the user plane network element, the radio access network device, and the user equipment.
  • the N3 tunneling protocol refers to the tunneling protocol between the user plane network element and the access network node
  • the N3 tunneling protocol in the present invention may be used for other possible transmissions between the user plane network element and the access network node. Tunneling protocol replacement for data.
  • step 408 the radio access network device deletes padding redundant data.
  • the wireless access network device After the wireless access network device receives the twelfth packet, the wireless access network device strips the N3 tunneling protocol header in the twelfth packet, and deletes the padding redundant data in the twelfth packet.
  • the wireless access network device after receiving the twelfth packet, deletes the filling redundant data according to the first indication information received in step 404 .
  • the wireless access network device deletes the redundant padding data in the twelfth packet according to the first indication information.
  • the wireless access network device deletes the redundant padding data in the payload part of the twelfth packet according to the length information of the redundant padding data .
  • the wireless access network device finds the start of the filled redundant data from the payload part of the twelfth packet according to the location information of the filled redundant data. position and end position, delete the data from the start position to the end position.
  • the wireless access network device deletes the data except the payload data in the payload part of the twelfth packet according to the length information of the payload data , i.e. remove padding redundant data.
  • the wireless access network device finds the starting location and the starting location of the payload data from the payload part of the twelfth packet according to the location information of the payload data. end position, and delete the data beyond the start position of the payload data to the end position, that is, delete the filling redundant data.
  • the wireless access network device can determine the position of the twelfth packet filled with redundant data according to the first indication information, and can also determine the position in the twelfth packet according to the The Length field shown in 9 determines the position of the filling redundant data in the twelfth message, and then deletes the filling in the twelfth message according to the position of the filling redundant data in the twelfth message.
  • redundant data Specifically, the data other than the payload data corresponding to the Length field in the payload part of the twelfth packet is deleted according to the Length field, that is, the padding redundant data is deleted.
  • the first indication information may only include one of the length information of the padded redundant data, the position information of the padded redundant data, the length information of the payload data, or the position information of the payload data. Or more, when the first indication information includes one or more of the above information, the wireless access network device may delete the filled redundant data according to the first indication information. Or, in a possible implementation manner, the first indication information may further include an indication that the redundant padding data is to be deleted, for instructing the wireless access network device to delete the redundant padding data according to the first indication information. Or, in a possible implementation manner, the first indication information only includes an indication that the redundant padding data is to be deleted, and the wireless access network device deletes the redundant padding data according to the first indication information.
  • step 409 the wireless access network device sends the second packet to the user equipment.
  • the wireless access network device adds an air interface protocol header after deleting the redundant data filled in the twelfth packet to generate a second packet. and send the second packet to the user equipment.
  • the format of the twelfth packet is the Ethernet II frame format shown in Figure 8
  • the format of the second packet is shown in Figure 12, wherein the destination MAC address field, source MAC
  • the address field, type field, and payload field are the same as the corresponding fields in the twelfth packet;
  • the AN protocol header in FIG. 12 is also called the air interface protocol header, which is exemplary and may specifically include the PDCP header and the RLC header. and the MAC header.
  • the format of the twelfth packet is the IEEE 802.3 frame format shown in Figure 9
  • the format of the second packet is shown in Figure 7, wherein the destination MAC address field, source MAC address field, Length field, The LLC field and the payload field are the same as the corresponding fields in the twelfth packet;
  • the AN protocol header in FIG. 7 is also called the air interface protocol header, which is exemplary and may specifically include the PDCP header, the RLC header, and the MAC header. .
  • the wireless access network device sends packets to the user equipment through air interface transmission, which is not limited by the minimum frame length of Ethernet. Therefore, after stripping the N3 tunnel protocol header, the twelfth packet is If the length is less than 64 bytes, that is, the length of the second packet is less than 64 bytes, it can also be transmitted. In addition, because the redundant padding data in the payload portion of the twelfth packet has been deleted, that is to say, the payload portion of the second packet does not include redundant padding data, so air interface resources can be saved during air interface transmission.
  • the application layer of the user equipment may directly acquire and use the payload data part of the second packet.
  • the user equipment when the user equipment is an intermediate node of the network and needs to continue to forward the Ethernet frame to the next hop node, the user equipment supplements and fills the load part of the second packet with redundant data. , and generate the thirteenth packet, so that the data length of the thirteenth packet is greater than or equal to 64 bytes.
  • the user plane network element encapsulates the first packet with the redundant data deleted according to the N3 tunnel protocol, before obtaining the twelfth packet, the user plane network element
  • the preamble field, SFD field, and FCS field in the first packet are also deleted, and the user equipment needs to add other fields to generate the thirteenth packet, such as the FCS field, the preamble field, and the SFD field.
  • the format of the thirteenth packet may be the same as that of the first packet, that is, if the first packet is the Ethernet II frame format shown in FIG. 8, the thirteenth packet is also the Ethernet II frame format. If the first packet format is the IEEE 802.3 frame format shown in Figure 9, the thirteenth packet is also an IEEE 802.3 type Ethernet frame.
  • the data length of the thirteenth packet is the same as the data length of the first packet.
  • the data length of the first message or the thirteenth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the thirteenth packet is the same as the first packet.
  • the user equipment may fill each bit of the redundant data padding in the thirteenth packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the user equipment may supplement and fill redundant data in the payload part of the twelfth packet according to the first indication information to generate the thirteenth packet, so that the thirteenth packet is The data length is greater than or equal to 64 bytes.
  • the user equipment fills the redundant padding data into the payload part of the twelfth packet according to the length information of the redundant padding data.
  • the user equipment finds the starting point of the redundant data filling to be filled from the load part of the twelfth packet according to the location information of the redundant data filling. Position and end position, fill the redundant data to the corresponding position.
  • the user equipment fills the payload part of the twelfth packet with the redundant padding data according to the length information of the payload data.
  • the user equipment finds out the start position and the end position of the payload data from the payload part of the twelfth message according to the position information of the payload data, And fill the redundant data to the position after the end position of the payload data and before the FCS field.
  • the user equipment determines to add redundant padding data according to the first indication information, and according to the Ethernet minimum frame specified by the protocol long, the twelfth packet is filled with redundant data.
  • step 410 the user equipment receives a seventh packet, where the seventh packet is an uplink Ethernet packet.
  • step 411 the user equipment deletes the padding redundant data in the seventh packet.
  • step 412 the user equipment generates an eighth packet, and sends the eighth packet to the wireless network device.
  • Steps 410 to 412 are similar to the methods performed in steps 210 to 212 in the aforementioned embodiment shown in FIG. 2 , and details are not described herein again.
  • step 413 the wireless access network device adds the padding redundant data of the eighth packet.
  • the wireless access network device After the wireless access network device receives the eighth packet sent by the user equipment, the wireless access network device strips the air interface protocol header in the eighth packet, adds padding redundant data in the eighth packet, and The N3 tunnel protocol header is added to generate the ninth packet, so that the data length of the ninth packet is greater than or equal to 64 bytes.
  • the format of the seventh packet is the Ethernet II frame format shown in FIG. 8
  • the format of the ninth packet is as shown in FIG.
  • the destination MAC address field and the source MAC address of the ninth packet are The field, type field and payload field are the same as the corresponding fields in the eighth message; and the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field and GTP-U header field in Figure 10 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 10 is different from the seventh packet.
  • the FCS field in Figure 10 is calculated by the wireless access network device according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header in Figure 10 field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, type field, and payload field.
  • the format of the ninth packet is as shown in Figure 11, wherein the destination MAC address field, source MAC address field, Length field, The LLC field and the payload field are the same as the corresponding fields in the eighth packet; and the N3 tunneling protocol header field includes the N3 MAC header field, IP header field, UDP header field and GTP-U header field in FIG. 11 .
  • the N3 MAC header field refers to the protocol header field of the MAC layer used for packet transmission in the Layer 2 transmission network between the access network node and the user plane network element.
  • the FSC field in Figure 11 is different from the seventh packet.
  • the FCS field in Figure 11 is calculated by the radio access network device according to the effective length of the N3 MAC frame, where the effective length of the N3 MAC frame includes the N3 MAC header in Figure 11 field, IP header field, UDP header field, GTP-U header field, destination MAC address field, source MAC address field, length field, and payload field.
  • the wireless access network device encapsulates the eighth packet according to the N3 tunneling protocol to obtain the ninth packet.
  • the N3 tunneling protocol here may be the GTP-U protocol. It can be understood that in the actual application process, it may also be other N3 tunneling protocols, which is not specifically limited here.
  • the N3 tunneling protocol refers to the tunneling protocol between the user plane network element and the access network node
  • the N3 tunneling protocol in the present invention may be used for other possible transmissions between the user plane network element and the access network node. Tunneling protocol replacement for data.
  • the format of the ninth packet is the same as that of the seventh packet, that is to say, if the seventh packet is the Ethernet II frame format shown in Figure 8, the ninth packet is also the Ethernet type of Ethernet II. frame, if the format of the seventh packet is the IEEE 802.3 frame format shown in Figure 9, the ninth packet is also an Ethernet frame of the IEEE 802.3 type.
  • the data length of the seventh message or the ninth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the wireless access network device may fill each bit of the redundant data padding in the ninth packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the wireless access network may supplement and fill redundant data in the payload part of the eighth packet according to the first indication information to generate a ninth packet, so that the The data length is greater than or equal to 64 bytes.
  • the wireless access network pads the redundant padding data into the payload part of the eighth packet according to the length information of the redundant padding data.
  • the wireless access network finds the filled redundant data to be filled from the load part of the eighth packet according to the location information of the filled redundant data. Start position and end position, fill the filling redundant data to the corresponding position.
  • the radio access network fills the payload portion of the eighth packet with redundant padding data according to the length information of the payload data.
  • the radio access network finds out the start location and the end location of the payload data from the payload part of the eighth packet according to the location information of the payload data , and fill the padding redundant data to the position after the end position of the payload data and before the FCS field.
  • the wireless access network determines according to the first indication information that redundant padding data is to be added, and according to the Ethernet protocol specified The minimum frame length, and the eighth packet is filled with redundant data.
  • step 414 the wireless access network device sends a ninth packet to the user plane network element.
  • the wireless access network device After generating the ninth packet, the wireless access network device sends the ninth packet to the user plane network element.
  • the user plane network element may strip off the N3 tunnel protocol header in the ninth packet, generate a fourteenth packet, and send it to the next hop node.
  • the user plane network element also adds other fields.
  • the fourteenth message is generated.
  • the format of the fourteenth packet is the same as that of the seventh packet, that is, if the seventh packet is the Ethernet II frame format shown in Figure 8, the fourteenth packet is also For an Ethernet frame of Ethernet II type, if the format of the seventh packet is the IEEE 802.3 frame format shown in Figure 9, the fourteenth packet is also an Ethernet frame of the IEEE 802.3 type.
  • the data length of the seventh message or the fourteenth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the fourteenth packet is the same as the seventh packet.
  • steps 406 to 409 are application scenarios for sending downlink packets
  • steps 410 to 414 are application scenarios for sending uplink packets.
  • steps 406 to 409 may be implemented independently, and steps 410 to 414 may also be implemented independently, or may be implemented in combination, which is not specifically limited here.
  • the user plane device deletes the redundant padding data in the received downlink Ethernet packet, so that the downlink packet transmitted to the user equipment on the air interface does not include the redundant padding data, that is, it does not need to transmit the redundant padding data. data, saving air interface resources and improving air interface capacity.
  • the user equipment deletes the redundant padding data in the received uplink Ethernet packet, so that the uplink packet transmitted to the wireless access network device on the air interface does not include the redundant padding data, that is, no transmission is required. Filling redundant data saves air interface resources and increases air interface capacity.
  • FIG. 5 is another schematic flowchart of the data transmission method provided by the embodiment of the present application.
  • step 501 the user equipment establishes a PDU session.
  • the user equipment UE establishes a PDU session, and the PDU session is used for transmitting (Cellular Internet of Thinns, CIoT) packets through the control plane, that is, transmitting CIoT packets through a (Non-Access-Stratum, NAS) message.
  • CIoT Cellular Internet of Thinns
  • NAS Non-Access-Stratum
  • this embodiment can be applied to a scenario in which a 5G system and an industrial network communicate with each other, and can also be applied to other network scenarios, which is not specifically limited here.
  • the application server can be a production line controller or other industrial node in the industrial network.
  • step 502 the application function network element sends an AF request message to the policy control network element.
  • step 502 is similar to the method performed in step 202 in the aforementioned embodiment shown in FIG. 2 , and details are not repeated here.
  • step 503 the policy control network element sends a policy update message to the session management network element.
  • the policy control network element 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, and generates the first indication information according to the second indication information , and the first indication information and the SDF template are carried in the policy update message, and sent 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 padding data of the packet of the service described by the SDF template.
  • the policy update message includes a PCC rule
  • the PCC rule further includes first indication information and an SDF template.
  • the first indication information may further indicate the length information of the first padding redundant data padding the redundant data.
  • the length information of the first padding redundant data padding redundant data may be the length of the padding redundant data (padding) in the packet payload (payload) field.
  • the first indication information may further indicate the location information of the redundant data filled with the first filled redundant data.
  • the position information of the first filling redundant data filling redundant data may be a start position and an ending position of the filling redundant data in the payload field of the message.
  • the first indication information may further indicate length information of payload data of the packet.
  • the length information of the payload data of the packet may be the length of the payload data in the packet payload field.
  • the first indication information may also indicate location information of payload data of the packet.
  • the location information of the payload data of the message may be the start location and the end location of the payload data in the payload field of the message.
  • the first indication information may include one of length information of the padded redundant data, position information of the padded redundant data, length information of the payload data, or position information of the payload data, or If the first indication information includes one or more of the above information, the device that receives the first indication information may add or delete the filling redundant data according to the first indication information. Or, in a possible implementation manner, the first indication information may further include an indication to add or delete padding redundant data, which is used to instruct the device receiving the first indication information to The first indication information adds or deletes filling redundant data. Or, in a possible implementation manner, the first indication information only includes an indication to add or delete the filling redundant data, and the device that receives the first indication information will receive the service message according to the first indication Indicates information to add or delete padding redundant data.
  • the session management network element 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.
  • the session management network element binds the PCC rule obtained from the policy update message with the PDU session identifier.
  • the PCC rule includes first indication information and an SDF template, and 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 services corresponding to the SDF template in the PCC rule
  • the streams are all bound to the PDU session, and the length information of the padding redundant data included in the first indication information is the same.
  • step 504 the session management network element sends an N1 interface session management message to the user equipment.
  • the session management network element obtains the first indication information and the SDF template in the policy update message, and the SMF sends the PDU session identifier corresponding to the SDF and the first indication information to the user equipment through the N1 interface session management information.
  • the N1 interface session management message Carrying a PDU session modification command that is, the N1 interface session management message includes a PDU session modification command
  • the PDU session modification command includes a PDU session identifier and first indication information.
  • 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.
  • the PDU session identifier and the first indication information may also be sent to the user equipment through the radio access network device RAN, which is similar to the method performed in step 306 in the embodiment shown in FIG. 3 above. , and details are not repeated here.
  • step 505 the user plane network element receives the first packet.
  • the first packet is an Ethernet packet.
  • the user plane network element When downlink data is transmitted, the user plane network element will receive one or more downlink first packets, where the one or more first packets correspond to a PDU session identifier.
  • the first packet is in an Ethernet II frame format.
  • the first packet includes a preamble field, a Start Frame Delimiter (SFD) field, a destination MAC address field, a source MAC address field, a type field, and a data field.
  • SFD Start Frame Delimiter
  • FCS Frame Check Sequence
  • the data payload field includes a payload field, and also includes a padding field.
  • the first packet is in an Ethernet IEEE 802.3 frame format.
  • the first message includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a length field, and a Logic Link Control (LLC) field, Data payload field, FCS field.
  • LLC Logic Link Control
  • the data payload field includes a payload field, and also includes a padding field.
  • step 506 the user plane network element sends the first packet to the session management network element.
  • the user plane network element UPF After receiving the first packet, the user plane network element UPF forwards the first packet to the session management network element, that is, sends the first packet to the session management network element.
  • step 507 the session management network element deletes the filling redundant data.
  • the session management network element After the session management network element receives the first packet, the session management network element deletes the padding redundant data in the first packet.
  • the session management network element SMF deletes the redundant padding data in the first packet according to the first indication information.
  • the session management network element deletes the redundant padding data in the payload part of the first packet according to the length information of the redundant padding data.
  • the session management network element SMF can determine the end position of the redundant padding data according to the frame format in FIG. 8 or FIG. 9 , and then can determine the redundant padding data according to the length of the redundant padding data included in the first indication information. The starting position of the remaining data, and then the filling redundant data can be deleted according to the starting position and the ending position.
  • the session management network element SMF finds the starting position for filling redundant data from the payload part of the first packet according to the location information for filling redundant data. and the end position, delete the data from the start position to the end position.
  • the session management network element deletes the data except the payload data in the payload part of the first packet according to the length information of the payload data, that is, Remove padding redundant data.
  • the session management network element SMF can determine the end position of the redundant padding data according to the frame format in FIG. 8 or FIG. 9 , and then can determine the redundant padding data according to the length of the redundant padding data included in the first indication information. The starting position of the remaining data, and then the filling redundant data can be deleted according to the starting position and the ending position.
  • the session management network element finds the start location and the end location of the payload data from the payload part of the first packet according to the location information of the payload data , and delete the data beyond the start position of the payload data to the end position, that is, delete the redundant data padding.
  • the session management network element can determine the position in the first packet where the redundant data is filled according to the first indication information, and can also determine the position in the first packet to fill the redundant data according to The displayed length (Length) field determines the position of the redundant padding data in the first packet, and then deletes the redundant padding data in the first packet according to the position of the redundant padding data in the first packet.
  • the data other than the payload data corresponding to the Length field in the payload part of the first packet is deleted according to the Length field, that is, the padding redundant data is deleted.
  • the first indication information may only include one of the length information of the padded redundant data, the position information of the padded redundant data, the length information of the payload data, or the position information of the payload data. Or more, when the first indication information includes one or more of the above information, the user plane network element may delete the filled redundant data according to the first indication information. Or, in a possible implementation manner, the first indication information may further include an indication that the redundant padding data is to be deleted, for instructing the session management network element to delete the redundant padding data according to the first indication information. Or, in a possible implementation manner, the first indication information only includes an indication that the redundant padding data is to be deleted, and the session management network element deletes the redundant padding data according to the first indication information.
  • the session management network element deletes the preamble field, the SFD field and the FCS field in the first packet in addition to the deletion of the filling redundant data. That is, the preamble field, the SFD field and the FCS field in the first packet are not transmitted between the user session management network element and the user equipment.
  • step 508 the session management network element sends a combined message of N1 and N2 to the access and mobility management network element.
  • the session management network element After the session management network element deletes the redundant data filled in 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 the NAS message, where the second message is The payload data is the payload data after the redundant data padding is deleted in the first packet.
  • the session management network element sends the second message and the PDU session identifier to the AMF through a combined message (Namf_Communication_N1N2MessageTransfer service operation) of N1 and N2.
  • step 509 the mobility management network element sends a downlink NAS transmission message to the wireless access network device.
  • the mobility management network element After the mobility management network element receives 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.
  • the mobility management network element generates a downlink NAS transmission message, carries the second packet and the PDU session identifier in the downlink NAS transmission message, and sends the downlink NAS transmission message to the wireless access network device.
  • step 510 the radio access network device sends an RRC message to the user equipment.
  • the radio access network device After receiving the downlink NAS transmission message, the radio access network device sends the downlink NAS message to the UE through an RRC message.
  • the RAN sends the downlink NAS message to the UE through an RRC DL message.
  • the application layer of the user equipment may directly acquire and use the payload data part of the second packet.
  • the user equipment when the user equipment is an intermediate node of the network and needs to continue to forward the Ethernet frame to the next hop node, the user equipment supplements and fills the load part of the second packet with redundant data. , and generate a sixth packet, so that the data length of the sixth packet is greater than or equal to 64 bytes.
  • the session management network element also deletes the preamble field, the SFD field and the FCS field in the first packet, the user equipment also needs to supplement other fields to generate the sixth packet. , such as the FCS field, the preamble field and the SFD field, which are not specifically limited here.
  • the format of the sixth packet is the same as that of the first packet, that is, if the first packet is the Ethernet II frame format shown in Figure 8, the sixth packet is also the Ethernet II frame format.
  • Type of Ethernet frame if the first packet format is the IEEE 802.3 frame format shown in Figure 9, the sixth packet is also an IEEE 802.3 type Ethernet frame.
  • the data length of the sixth packet is the same as the data length of the first packet after the padding redundant data is supplemented.
  • the data length of the first message or the sixth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the sixth packet is the same as the first packet.
  • the user equipment may fill each bit of the redundant data padding in the sixth packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the user equipment may supplement and fill redundant data in the payload part of the second packet according to the first indication information to generate a sixth packet, so that the data length of the sixth packet is greater than or equal to 64 bytes.
  • the user equipment fills the redundant padding data into the payload part of the second packet according to the length information of the redundant padding data.
  • the user equipment finds the starting position of the redundant data filling to be filled from the load part of the fifth packet according to the position information of the redundant data filling And the end position, fill the redundant data to the corresponding position.
  • the user equipment fills the payload portion of the second packet with the redundant padding data according to the length information of the payload data.
  • the user equipment finds out the start location and the end location of the payload data from the payload part of the fifth message according to the location information of the payload data, and The padding redundant data is filled to the position after the end position of the payload data and before the FCS field.
  • the user equipment determines to add redundant padding data according to the first indication information, and according to the Ethernet minimum frame specified by the protocol long, the second packet is filled with redundant data.
  • step 511 the user equipment receives a seventh packet, where the seventh packet is an uplink Ethernet packet.
  • the seventh packet is an Ethernet packet.
  • the user equipment When uplink data is transmitted, the user equipment will acquire one or more uplink Ethernet packets, where the uplink Ethernet packet is the seventh packet.
  • the user equipment When the user equipment has a previous hop node, the user equipment receives an uplink Ethernet packet sent by the previous hop node.
  • the user equipment When the user equipment does not have a previous hop node, the user equipment generates an uplink Ethernet packet.
  • the upstream Ethernet packet is in an Ethernet Ethernet II frame format.
  • the upstream Ethernet packet includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • the upstream Ethernet packet is in an Ethernet IEEE802.3 frame format.
  • the upstream Ethernet packet 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 payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • step 512 the user equipment deletes the padding redundant data.
  • the user equipment After the user equipment acquires the seventh packet, the user equipment deletes the padding redundant data in the seventh packet.
  • the user equipment deletes the padding redundant data in the seventh packet according to the first indication information.
  • the user equipment deletes the redundant padding data in the payload part of the seventh packet according to the length information of the redundant padding data.
  • the user equipment finds the start position and the end position of the filled redundant data from the load part of the seventh packet according to the position information of the filled redundant data. , delete the data from the start position to the end position.
  • the user equipment deletes the data except the payload data in the payload part of the uplink Ethernet message according to the length information of the payload data, that is, deletes the padding. redundant data.
  • the user equipment finds out the start position and the end position of the payload data from the payload part of the seventh packet according to the position information of the payload data, and Delete the data beyond the start position to the end position of the payload data, that is, delete the padding redundant data.
  • the user equipment element may determine the position of the padding redundant data in the seventh packet according to the first indication information, and may also determine according to the length (Length) field
  • the position of the padding redundant data in the seventh packet is deleted, and the padding redundant data in the seventh packet is deleted according to the position of the padding redundant data in the seventh packet.
  • the data except the payload data corresponding to the Length field in the payload part of the seventh packet is deleted according to the Length field, that is, the redundant padding data of the seventh packet is deleted.
  • the user equipment in addition to deleting the redundant padding data in the seventh packet, the user equipment also deletes the preamble field, the SFD field and the FCS field in the seventh packet. That is, the preamble field, the SFD field and the FCS field in the seventh packet are not transmitted between the user equipment and the session management network element.
  • step 513 the user equipment sends an RRC message to the radio access network device.
  • the user equipment After deleting the redundant padding data of the seventh packet, the user equipment generates an eighth packet, and the payload data in the eighth packet is the payload data after deleting the redundant padding data in the seventh packet, and The eighth packet is sent to the radio access network device RAN through an RRC message.
  • the user equipment encapsulates the eighth packet and the corresponding PDU session identifier in an uplink NAS message, and carries the uplink NAS message in an RRC message to send to the RAN.
  • step 514 the wireless access network device sends an uplink NAS message to the access and mobility management network element AMF.
  • the radio access network device RAN After the radio access network device RAN receives the uplink NAS message sent by the user equipment, the radio access network device forwards the uplink NAS message to the access and mobility management network element AMF.
  • step 515 the access and mobility management network element AMF sends a combined message of N1 and N2 to the session management network element.
  • the access and mobility management network element AMF 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 (Namf_Communication_N1N2MessageTransfer service operation) of N1 and N2, and sends it to the session management network element.
  • step 516 the session management network element adds padding redundant data.
  • the session management network element After the session management network element receives the eighth packet carried in the NAS message, the session management network element adds padding redundant data to generate a ninth packet, so that the data length of the ninth packet is greater than or equal to 64 bytes, which can be Optionally, if the user equipment deletes the preamble field, SFD field, and FCS field in the seventh packet in addition to deleting the redundant data in the seventh packet, the session management network element also adds other fields to generate The ninth packet, such as the FCS field, the preamble field and the SFD field, is not specifically limited here.
  • the format of the ninth packet is the same as that of the seventh packet, that is, if the seventh packet is the Ethernet II frame format shown in Figure 8, the ninth packet is also of the Ethernet II type.
  • the ninth packet is also an Ethernet frame of the IEEE802.3 type.
  • the data length of the ninth packet is the same as the data length of the seventh packet.
  • the data length of the seventh message or the ninth message is the sum of the lengths of other fields except the preamble field, the SFD field and the frame check sequence field in FIG. 8 or FIG. 9 .
  • the ninth packet is the same as the seventh packet.
  • the session management network element may fill each bit of the redundant data filling in the ninth packet with 0. It can be understood that the padding can also be performed in other ways, as long as the data length of the packet after padding is greater than or equal to 64 bytes, which is not specifically limited here.
  • the session management network element may supplement and fill redundant data in the payload part of the eighth packet according to the first indication information to generate a ninth packet, so that the ninth packet is The data length is greater than or equal to 64 bytes.
  • the session management network element fills the redundant padding data into the payload part of the eighth packet according to the length information of the redundant padding data.
  • the session management network element finds the filled redundant data to be filled from the load part of the eighth packet according to the location information of the filled redundant data. Start position and end position, fill the filling redundant data to the corresponding position.
  • the session management network element fills the payload portion of the eighth packet with redundant padding data according to the length information of the payload data.
  • the session management network element finds the start location and the end location of the payload data from the payload part of the eighth packet according to the location information of the payload data , and fill the padding redundant data to the position after the end position of the payload data and before the FCS field.
  • the session management network element determines to add redundant padding data according to the first indication information, and according to the Ethernet protocol specified Minimum frame length, fill the eighth packet with redundant data
  • step 517 the session management network element sends the ninth packet.
  • the session management network element sends the ninth packet to the next hop node.
  • steps 505 to 510 are application scenarios for sending downlink messages
  • steps 511 to 517 are application scenarios for sending uplink messages.
  • steps 505 to 510 may be implemented independently, and steps 511 to 517 may also be implemented independently, or may be implemented in combination, which is not specifically limited here.
  • the user plane device deletes the redundant padding data in the received downlink packet, so that the downlink packet transmitted to the user equipment on the air interface does not include the redundant padding data, that is, the redundant padding data does not need to be transmitted , which saves air interface resources and improves air interface capacity.
  • the user equipment deletes the padding redundant data in the received uplink packet, so that the uplink packet transmitted to the wireless access network device on the air interface does not include the padding redundant data, that is, the padding does not need to be transmitted. Redundant data saves air interface resources and improves air interface capacity.
  • FIG. 6 is another schematic flowchart of the data transmission method provided by the embodiment of the present application.
  • step 601 the user equipment establishes a PDU session.
  • step 602 the application function network element sends an AF request message to the policy control network element.
  • step 603 the policy control network element sends a policy update message to the session management network element.
  • step 604 the session management network element sends a PDU session modification command to the user equipment.
  • steps 601 to 604 are similar to the method performed by steps 501 to 504 in the foregoing embodiment of FIG. 5 , and details are not described herein again.
  • step 605 the network element of the network capability exposure function receives the first message.
  • the first packet is an Ethernet packet.
  • the NEF When downlink data is transmitted, the NEF will receive one or more downlink first packets, where the one or more first packets correspond to a PDU session identifier.
  • the first packet is in an Ethernet II frame format.
  • the first packet includes a preamble field, an SFD field, a destination MAC address field, a source MAC address field, a type field, a data payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • the first packet is in an Ethernet IEEE 802.3 frame format.
  • the first packet 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 payload field, and an FCS field.
  • the data payload field includes a payload field, and also includes a padding field.
  • step 606 the NEF sends the first packet to the session management network element.
  • the NEF After receiving the first packet, the NEF forwards the first packet to the session management network element, that is, sends the first packet to the session management network element.
  • the NEF forwards the first packet to the SMF through the Nsmf_NIDD_Delivery request message.
  • step 607 the session management network element deletes the filling redundant data.
  • step 608 the session management network element sends a combined message of N1 and N2 to the access and mobility management network element AMF.
  • step 609 the mobility management network element AMF sends a downlink NAS transmission message to the wireless access network device.
  • step 610 the radio access network device sends an RRC message to the user equipment.
  • step 611 the user equipment receives a seventh packet, where the seventh packet is an uplink Ethernet packet.
  • step 612 the user equipment deletes the padding redundant data.
  • step 613 the user equipment sends an RRC message to the radio access network device.
  • step 614 the wireless access network device sends an uplink NAS message to the access and mobility management network element.
  • step 615 the access and mobility management network element sends a combined message of N1 and N2 to the session management network element.
  • step 616 the session management network element adds padding redundant data.
  • steps 607 to 616 are similar to the method performed by steps 507 to 516 in the aforementioned embodiment of FIG. 5 , and details are not described herein again.
  • step 617 the session management network element sends the ninth packet.
  • the session management network element After adding the filling redundant data to obtain the ninth packet, the session management network element sends the ninth packet to the NEF through the Nnef_SMContext_Delivery request message.
  • the NEF after receiving the ninth packet, the NEF sends the ninth packet to the next hop node.
  • steps 605 to 610 are application scenarios for sending downlink messages
  • steps 611 to 617 are application scenarios for sending uplink messages.
  • steps 605 to 610 may be implemented independently, and steps 611 to 617 may also be implemented independently, or may be implemented in combination, which is not specifically limited here.
  • the user plane device deletes the redundant padding data in the received downlink packet, so that the downlink packet transmitted to the user equipment on the air interface does not include the redundant padding data, that is, the redundant padding data does not need to be transmitted , which saves air interface resources and improves air interface capacity.
  • the user equipment deletes the padding redundant data in the received uplink packet, so that the uplink packet transmitted to the wireless access network device on the air interface does not include the padding redundant data, that is, the padding does not need to be transmitted. Redundant data saves air interface resources and improves air interface capacity.
  • FIG. 13 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • a device comprising:
  • a receiving unit 1301, configured to receive a first packet, where the payload data in the first packet includes padding redundant data;
  • Deleting unit 1302 for deleting filling redundant data
  • the generating unit 1303 is used to generate a second message, and the payload data in the second message is the payload data after the redundant data is deleted and filled in the first message;
  • the sending unit 1304 is configured to send the second packet to the second device.
  • each unit of the device in this embodiment is similar to the method performed by each network device or user equipment in the foregoing FIG. 2 to FIG. 6 , and details are not described herein again.
  • FIG. 13 is another schematic structural diagram of the device provided by the embodiment of the present application.
  • a device comprising:
  • a receiving unit 1301, configured to receive a first packet, where the payload data in the first packet includes padding redundant data;
  • Deleting unit 1302 for deleting filling redundant data
  • the generating unit 1303 is used to generate a second message, and the payload data in the second message is the payload data after the redundant data is deleted and filled in the first message;
  • the sending unit 1304 is configured to send the second packet to the second device.
  • the receiving unit 1301 is further configured to receive the first indication information
  • the deletion unit 1302 is specifically configured to delete the filling redundant data according to the first indication information.
  • the first indication information is used to instruct the device to delete the redundant padding data, or, the first indication information includes length information of the redundant padding data, or, the location information of the redundant padding data, or, the first indication information includes The length information of the payload data of the first downlink packet, or the location information of the payload data of the first packet.
  • the deletion unit 1302 is specifically configured to delete the padding redundant data according to the length field of the first packet.
  • the device is a UPF
  • the second device is a RAN
  • the first packet is a downlink Ethernet packet.
  • the generating unit 1303 is specifically configured to encapsulate the third packet according to the N3 tunneling protocol to obtain a fourth packet, wherein the third packet is a packet after the first packet is deleted and filled with redundant data;
  • the data length of the fourth packet is less than the minimum Ethernet frame length, then the tunnel protocol is added to the N3 tunnel protocol header of the fourth packet to fill redundant data to obtain the second packet, and the data length of the second packet is greater than or equal to the Ethernet minimum frame length; or,
  • the generating unit 1303 is specifically configured to encapsulate the third packet according to the N3 tunneling protocol Obtain the encapsulated packet, and add the tunnel protocol to fill redundant data in the N3 tunnel protocol header of the encapsulated packet to obtain a second packet.
  • the data length of the second packet is greater than or equal to the minimum Ethernet frame length.
  • the third packet The message is the message after the first message is deleted and filled with redundant data.
  • the device is a RAN
  • the second device is a UE
  • the first message is a downlink message.
  • the device is a UE
  • the second device is a RAN
  • the first packet is an uplink Ethernet packet.
  • the device is an SMF
  • the second device is a UE
  • the first packet is a downlink Ethernet packet.
  • the device is a UE, the second device is an SMF, and the first packet is an uplink Ethernet packet.
  • each unit of the device in this embodiment is similar to the method performed by each network device or user equipment in the foregoing FIG. 2 to FIG. 6 , and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of a device provided by an embodiment of the present application.
  • a device comprising:
  • the sending unit 1401 is configured to send first indication information to the fourth device, where the first indication information is used to delete the padding redundant data of the first packet, or the first indication information is used to add padding to the first packet Redundant data, the first indication information includes the length information of the padded redundant data, or, the position information of the padded redundant data, or, the first indication information includes the length information of the payload data of the first packet, or, the first The location information of the payload data of the message.
  • each unit of the device in this embodiment is similar to the method performed by each network device in the aforementioned FIG. 2 to FIG. 6 , and details are not repeated here.
  • FIG. 15 is another schematic structural diagram of the device provided by the embodiment of the present application.
  • a device comprising:
  • the sending unit 1501 is configured to send first indication information to the fourth device, wherein the first indication information is used to delete the padding redundant data of the first packet, or the first indication information is used to add padding to the first packet Redundant data, the first indication information includes the length information of the padded redundant data, or, the position information of the padded redundant data, or, the first indication information includes the length information of the payload data of the first packet, or, the first The location information of the payload data of the message.
  • the device is PCF
  • the fourth device is SMF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UPF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UE
  • the first packet is an Ethernet packet
  • the device is SMF and the fourth device is RAN; or,
  • the device is the RAN, and the fourth device is the UE.
  • the device is SMF
  • the fourth device is UPF
  • the first packet is an Ethernet packet
  • the device is SMF
  • the fourth device is UE
  • the first packet is an Ethernet packet
  • the device is SMF and the fourth device is RAN.
  • 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
  • the device further includes:
  • the receiving unit 1502 is configured to receive second indication information of the fifth device, where the second indication information is used to indicate the length information of the filled redundant data, or, the position information of the filled redundant data, or, the second indication information is used to indicate length information of the payload data of the first packet, or location information of the payload data of the first packet;
  • the determining unit 1503 is configured to determine the first indication information according to the second indication information.
  • each unit of the device in this embodiment is similar to the method performed by each network device in the aforementioned FIG. 2 to FIG. 6 , and details are not repeated here.
  • FIG. 16 is a schematic structural diagram of the device provided by the embodiment of the present application.
  • the processor 1601 is connected to the memory 1602 and the interface 1604.
  • the bus 1605 is respectively connected to the processor 1601, the memory 1602, and the interface 1604.
  • the interface 1604 is used to receive or send data.
  • the processor 1601 be a single-core or multi-core central processing unit, or be a specific integrated circuit, or be one or more integrated circuits configured to implement embodiments of the invention.
  • the memory 1602 may be random access memory (RAM), or may be non-volatile memory (non-volatile memory), such as at least one hard disk memory.
  • Memory 1602 is used to store computer-implemented instructions. Specifically, the program 1603 may be included in the computer-executed instructions.
  • the device in FIG. 16 can perform the operations performed by the respective network devices in the foregoing embodiments shown in FIG. 2 to FIG. 6, and details are not repeated here.
  • FIG. 17 is a schematic structural diagram of the device provided by the embodiment of the present application.
  • the processor 1701 is connected to the memory 1702 and the interface 1704.
  • the bus 1705 is respectively connected to the processor 1701, the memory 1702, and the interface 1704.
  • the interface 1704 is used to receive or send data.
  • the processor 1701 be a single-core or multi-core central processing unit, or be a specific integrated circuit, or be one or more integrated circuits configured to implement embodiments of the invention.
  • the memory 1702 may be random access memory (RAM), or may be non-volatile memory (non-volatile memory), such as at least one hard disk memory.
  • Memory 1702 is used to store computer-implemented instructions. Specifically, the program 1703 may be included in the computer-executed instructions.
  • the device in FIG. 17 can perform the operations performed by the user equipment in the foregoing embodiments shown in FIG. 2 to FIG. 6, and details are not repeated here.
  • the processor mentioned in the network device or user equipment in the above embodiments of the present application may be a central processing unit (central processing unit, CPU), or may be other General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the number of processors in the network device or user equipment in the above embodiments of the present application may be one or more, and may be adjusted according to actual application scenarios. limited.
  • the number of memories in this embodiment of the present application may be one or multiple, and may be adjusted according to actual application scenarios, which is merely illustrative and not limiting.
  • a network device or user equipment includes a processor (or a processing unit) and a memory
  • the processor in this application may be integrated with the memory, or the processor and the memory may be connected through an interface, It can be adjusted according to the actual application scenario and is not limited.
  • the embodiments of the present application also provide a computer program or a computer program product including a computer program, when the computer program is executed on a computer, the computer program will enable the computer to implement the network device in any of the above method embodiments. Or a method flow related to the user equipment.
  • Embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a computer, implements a method flow related to a network device or user equipment in any of the above method embodiments.
  • FIGS. 2 to 6 may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented in software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • wire eg, coaxial cable, fiber optic, digital subscriber line (DSL)
  • wireless eg, infrared, wireless, microwave, etc.
  • the computer-readable storage medium may be any available medium that can be stored by a computer, or a data storage device such as a server, data center, etc., which includes one or more available media integrated.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.
  • the words “if” or “if” as used herein may be interpreted as “at” or “when” or “in response to determining” or “in response to detecting.”
  • the phrases “if determined” or “if detected (the stated condition or event)” can be interpreted as “when determined” or “in response to determining” or “when detected (the stated condition or event),” depending on the context )” or “in response to detection (a stated condition or event)”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例公开了一种数据传输方法及其设备，用于以太网小包传输场景下。本申请实施例方法包括：第一设备接收第一报文，所述第一报文中的载荷数据包括填充冗余数据，所述第一设备删除所述填充冗余数据，所述第一设备生成第二报文，所述第二报文中的载荷数据为所述第一报文中删除所述填充冗余数据后的有效载荷数据，所述第一设备向第二设备发送所述第二报文。本申请实施例中，第一设备通过删除第一报文中的填充冗余数据，使得在空口传输中，不需要传输填充冗余数据，节省了空口资源，提高了空口容量。

Description

一种数据传输方法及其设备 技术领域
本申请涉及通信领域，尤其涉及一种数据传输方法及其设备。
背景技术
为满足带有冲突检测的载波侦听多路访问(Carrier Sense Multiple Access with Collision Detection，CSMA/CD)对碰撞检测和退避重传机制的要求，CSMA/CD对以太网报文有最小大小的限制，如限制在64字节，长度小于64字节的帧会被网络中的转发设备认为是由于冲突而异常中止的无效帧。
在工业应用领域，工业应用的应用层报文的有效载荷通常较小，例如10字节或者20字节。为满足工业以太网的对最小以太帧大小的限制，需要在报文的载荷部分增加填充冗余字段，以使得报文的大小等于或者大于64字节。
而在报文传输的过程中，由于增加了填充冗余部分，在空口传输时，会占用过多的空口资源，不利于提升空口容量。
发明内容
本申请实施例提供了一种数据传输方法及其设备，用于在以太网小包传输时，通过删除报文中的填充冗余数据，使得在空口传输中，不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例的第一方面提供一种数据传输方法。
第一设备接收第一报文，第一报文中的载荷数据包括填充冗余数据，第一设备删除填充冗余数据，第一设备生成第二报文，第二报文中的载荷数据为第一报文中删除填充冗余数据后的有效载荷数据，第一设备向第二设备发送第二报文。
本申请实施例中，第一设备通过将接收到的第一报文中的填充冗余数据删除得到第二报文，并将第二报文发送给第二设备，这样在后续的空口传输中，不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备接收第一指示信息，第一设备删除填充冗余数据包括，第一设备根据第一指示信息删除填充冗余数据。
本申请实施例中，通过接收的指示信息对填充冗余数据进行删除，提供了高第一设备的执行效率，并且保证了有效载荷数据的正常传输。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一指示信息用于指示第一网络设备删除填充冗余数据，或，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一下行报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
本申请实施例中，说明了第一指示信息具体用于指示的内容，提升了方案的灵活性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备删除填充冗余数据包括：第一设备根据第一报文的长度字段删除填充冗余数据。
本申请实施例中，通过第一报文的长度字段删除填充冗余数据，提升了第一设备删除填充冗余数据的灵活性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备为用户面网元UPF，第二设备为无线接入网设备RAN，第一报文为下行以太报文。
本申请实施例中，说明了第一设备和第二设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备生成第二报文包括：
第一设备根据N3隧道协议对第三报文进行封装得到第四报文，其中，第三报文为第一报文删除填充冗余数据后的报文；若第四报文的数据长度小于以太网最小帧长，则在第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长；或者，
若第一设备确定第一设备根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则第一设备根据N3隧道协议对第三报文进行封装得封装报文，并在封装报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长，其中，第三报文为第一报文删除填充冗余数据后的报文。
本申请实施例中，通过在第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，使得第二报文的数据长度大于或者等于以太网最小帧长，这样在以太网传输的过程中，降低了发生错误的风险。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备为无线接入网设备RAN，第二设备为用户设备UE，第一报文为下行报文。
本申请实施例中，说明了第一设备和第二设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备为用户设备UE，第二设备为无线接入网设备RAN，第一报文为上行以太报文。
本申请实施例中，说明了第一设备和第二设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备为会话管理网元SMF，第二设备为用户设备UE，第一报文为下行以太报文。
本申请实施例中，说明了第一设备和第二设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第一方面的方法，在一种可能的实现方式中，第一设备为用户设备UE，第二设备为会话管理网元SMF，第一报文为上行以太报文。
本申请实施例中，说明了第一设备和第二设备的具体实现方式，提升了方案的可实现性。
本申请实施例第二方面提供了一种数据传输方法。
第三设备向第四设备发送第一指示信息，其中，第一指示信息用于删除第一报文的填 充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
本申请实施例中，通过想第四设备发送第一指示信息，用于指示删除第一报文的填充冗余数据，使得在后续空口传输中，不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
基于本申请实施例第二方面的方法，在一种可能的实现方式中，当第一指示信息用于删除第一报文的填充冗余数据时，
第三设备为策略控制网元PCF，第四设备为会话管理网元SMF，第一报文为以太报文；或者，
第三设备为会话管理网元SMF，第四设备为用户面网元UPF，第一报文为以太报文；或者，
第三设备为会话管理网元SMF，第四设备为用户设备UE，第一报文为以太报文；或者，
第三设备为会话管理网元SMF，第四设备为无线接入网设备RAN；或者，
第三设备为无线接入网设备RAN，第四设备为用户设备UE。
本申请实施例中，说明了第三设备和第四设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第二方面的方法，在一种可能的实现方式中，当第一指示信息用于在第一报文增加填充冗余数据时，
第三设备为SMF，第四设备为UPF，第一报文为以太报文；或者，
第三设备为SMF，第四设备为UE，第一报文为以太报文；或者，
第三设备为SMF，第四设备为RAN。
本申请实施例中，说明了第三设备和第四设备的具体实现方式，提升了方案的可实现性。
基于本申请实施例第二方面的方法，在一种可能的实现方式中，第三设备为策略控制网元PCF，第四设备为会话管理网元SMF，第五设备为应用功能网元AF。在第三设备向第四设备发送第一指示信息之前，第三设备接收第五设备的第二指示信息，第三设备根据第二指示信息确定第一指示信息。其中，第二指示信息用于指示填充冗余数据的长度信息，或者，填充冗余数据的位置信息，或者，第二指示信息用于指示第一报文的有效载荷数据的长度信息，或者，第一报文的有效载荷数据的位置信息。
本申请实施例中，通过AF发送的第二指示信息确定第一指示信息，即根据AF发送的第二指示信息中的填充冗余数据的信息，进而确定第一指示信息中填充冗余数据的信息并确定针对填充冗余数据执行增减或删除操作，提升了方案的可实现性。
本申请实施例第三方面提供了一种设备。
一种设备，包括：
接收单元，用于接收第一报文，第一报文中的载荷数据包括填充冗余数据；
删除单元，用于删除填充冗余数据；
生成单元，用于生成第二报文，第二报文中的载荷数据为第一报文中删除填充冗余数 据后的有效载荷数据；
发送单元，用于向第二设备发送第二报文。
可选地，接收单元还用于接收第一指示信息；
删除单元具体用于根据第一指示信息删除填充冗余数据。
可选地，第一指示信息用于指示设备删除填充冗余数据，或，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一下行报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
可选地，删除单元具体用于根据第一报文的Length字段删除填充冗余数据。
可选地，设备为UPF，第二设备为RAN，第一报文为下行以太报文。
可选地，生成单元具体用于根据N3隧道协议对第三报文进行封装得到第四报文，其中，第三报文为第一报文删除填充冗余数据后的报文；若第四报文的数据长度小于以太网最小帧长，则在第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长；或者，
若设备确定第一设备根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则生成单元具体用于根据N3隧道协议对第三报文进行封装得封装报文，并在封装报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长，其中，第三报文为第一报文删除填充冗余数据后的报文。
可选地，设备为RAN，第二设备为UE，第一报文为下行报文。
可选地，设备为UE，第二设备为RAN，第一报文为上行以太报文。
可选地，设备为SMF，第二设备为UE，第一报文为下行以太报文。
可选地，设备为UE，第二设备为SMF，第一报文为上行以太报文。
本申请实施例中第三方面提供的设备所执行的方法与前述第一方面中第一设备所执行的方法类似，具体此处不再赘述。
本申请实施例第四方面提供了一种设备。
一种设备，包括：
发送单元，用于向第四设备发送第一指示信息，其中，第一指示信息用于删除第一报文的填充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
可选地，
当第一指示信息用于删除第一报文的填充冗余数据时，
设备为PCF，第四设备为SMF，第一报文为以太报文；或者，
设备为SMF，第四设备为UPF，第一报文为以太报文；或者，
设备为SMF，第四设备为UE，第一报文为以太报文；或者，
设备为SMF，第四设备为RAN；或者，
设备为RAN，第四设备为UE。
可选地，
当第一指示信息用于在第一报文增加填充冗余数据时，
设备为SMF，第四设备为UPF，第一报文为以太报文；或者，
设备为SMF，第四设备为UE，第一报文为以太报文；或者，
设备为SMF，第四设备为RAN。
可选地，设备为策略控制网元PCF，第四设备为会话管理网元SMF，第五设备为应用功能网元AF，设备还包括：
接收单元，用于接收第五设备的第二指示信息，第二指示信息用于指示填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第二指示信息用于指示第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息；
确定单元，用于根据第二指示信息确定第一指示信息。
本申请实施例中第四方面提供的设备所执行的方法与前述第二方面中第三设备所执行的方法类似，具体此处不再赘述。
本申请实施例第五方面提供一种网络设备或者用户设备，包括：
处理器、存储器以及输入输出接口，该处理器、该存储器与该输入输出接口连接；该存储器，用于存储程序代码；该处理器调用该存储器中的程序代码时执行本申请第一方面或第二方面实施方式提供的方法。
本申请实施例第六方面提供一种存储介质，需要说明的是，本发的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产口的形式体现出来，该计算机软件产品存储在一个存储介质中，用于储存为上述设备所用的计算机软件指令，其包含用于执行上述第一方面或第二方面中为数据传输方法所设计的程序。
该存储介质包括：U盘、移动硬盘、只读存储器(英文缩写ROM，英文全称：Read-Only Memory)、随机存取存储器(英文缩写：RAM，英文全称：Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请实施例第七方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如本申请第一方面或第二方面实施方式的方法。
其中，上述任一处提到的处理器，可以是一个通用中央处理器(Central Processing Unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制上述第一方面或第二方面中数据传输方法的程序执行的集成电路。
本申请实施例提供的技术方案中，第一设备通过将接收到的第一报文中的填充冗余数据删除得到第二报文，并将第二报文发送给第二设备，使得在后续的空口传输中，不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
附图说明
图1为本申请实施例提供的通信网路架构示意图；
图2为本申请实施例提供的数据传输方法一个流程示意图；
图3为本申请实施例提供的数据传输方法另一流程示意图；
图4为本申请实施例提供的数据传输方法另一流程示意图；
图5为本申请实施例提供的数据传输方法另一流程示意图；
图6为本申请实施例提供的数据传输方法另一流程示意图；
图7为本申请实施例提供的数据传输方法中报文的一个结构示意图；
图8为本申请实施例提供的数据传输方法中报文的另一结构示意图；
图9为本申请实施例提供的数据传输方法中报文的一个结构示意图；
图10为本申请实施例提供的数据传输方法中报文的一个结构示意图；
图11为本申请实施例提供的数据传输方法中报文的一个结构示意图；
图12为本申请实施例提供的数据传输方法中报文的一个结构示意图；
图13为本申请实施例提供的设备的一个结构示意图；
图14为本申请实施例提供的设备的一个结构示意图；
图15为本申请实施例提供的设备的另一结构示意图；
图16为本申请实施例提供的设备的另一结构示意图；
图17为本申请实施例提供的设备的另一结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
请参阅图1，为本申请实施例提供的通信网络架构示意图。
如图1所示，该通信网络架构包括用户设备(User Equipment，UE)101、无线接入网络(radio access network，RAN)102、用户面网元(user plane function，UPF)103、数据网络(data network，DN)104、接入和移动管理网元(access and mobility management function，AMF)105、会话管理网元(session management function，SMF)106、策略控制网元(policy control function，PCF)107、应用功能(application function，AF)网元、统一数据管理网元(unified data managenment，UDM)108。其中，UE101和AMF105通过N1接口通信，UE101和RAN102连接，RAN102和AMF105通过N2接口连接，RAN102和UPF103通过N3接口连接，UPF103和DN104通过N6接口连接，UPF103和SMF106通过N4接口连接，PCF107和AF通过N5接口连接，SMF106和PCF107通过N7接口连接，AMF105和SMF106通过N11接口连接，AMF105和UDM108通过N8接口连接，SMF106和UDM108通过N10接口连接，UDM108和PCF107通过N25接口连接。可以理解的是，本申请提供的通信网络架构只是一种示例，在实际应用过程中，各个网络单元或者用户设备可以是一个也可以是多个，连接方式也不仅限于此，具体此处不做限定。
本申请实施例中，UE指的是网络终端设备，如手机、物联网终端设备等。
RAN为终端设备提供无线接入的设备，包括但不限于eNodeB、WiFi AP、WiMAX BS等。
AMF主要负责移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。
SMF主要负责移动网络中的会话管理，如会话建立、修改、释放。具体功能如为用户 分配IP地址、选择提供报文转发功能的UPF等。
PCF负责向AMF、SMF提供策略，如服务质量(Quality of Service，QoS)策略、切片选择策略等。
UDM用于存储用户数据，如签约信息、鉴权或者授权信息。
AF负责向3GPP网络提供业务，如影响业务路由、与PCF之间交互以进行策略控制等。
UPF主要负责对用户报文进行处理，如转发、计费等。
DN指的是为用户提供数据传输服务的运营商网络，如IP多媒体业务(IPMulti-media Service)、因特网(Internet)等。
除了图1中的网元外，该通信网络架构还包括，网络能力开放功能(network exposure function，NEF)网元，它是一种向第三方、应用功能AF等开放通信系统的能力的网元，在第三方、应用服务器与通信系统之间传递信息。
下面结合图1所示通信系统框架对本申请实施例提供的数据传输方法及其装置进行详细的描述。
本申请实施例中，根据不同的传输协议和使用场景，本申请实施例提供的数据处理方法有多种实施方式。下面，对多种情况分别进行描述。
请参阅图2，为本申请实施例提供的数据传输方法一个流程示意图。
在步骤201中，用户设备建立协议数据单元(Protocl Data Unit，PDU)会话。
该PDU会话用于在UE与应用服务器之间传输用户面数据。
通过步骤201，NG-RAN与UPF之间为该PDU会话建立了N3隧道。N3隧道是指UPF和RAN之间的隧道。需要说明的是，本实施例可以应用于5G系统和工业网络互通的场景，还可以应用于其它网络场景，具体此处不做限定。对于5G系统和工业网络互通的场景，该应用服务器可以是工业网络中的产线控制器或者其他工业节点。
在步骤202中，应用功能网元向策略控制网元发送AF请求消息。
当应用功能网元需要向核心网提供一些与业务相关的信息时，应用功能网元向策略控制网元发送AF请求(AF request)消息，比如，用户设备和应用服务器之间的PDU会话建立完成后，应用服务器会触发应用功能网元发送该应用功能网元请求消息，其中应用功能网元为应用服务器的控制面网元。该AF请求消息中携带了业务描述信息以及第二指示信息，该第二指示信息用于指示该业务描述信息描述的业务的报文的填充冗余数据相关的信息。
具体的，在一种可能的实现方式中，该第二指示信息可以指示填充冗余数据的长度信息。具体的，该填充冗余数据的长度信息可以是报文载荷(payload)字段中的填充冗余数据(padding)的长度。
具体的，在一种可能的实现方式中，该第二指示信息还可以指示填充冗余数据的位置信息。具体的，该填充冗余数据的位置信息可以是报文的载荷字段中的填充冗余数据的起始位置和结束位置。
具体的，在一种可能的实现方式中，该第二指示信息还可以指示报文的有效载荷数据的长度信息。具体的，该报文的有效载荷数据的长度信息可以是报文载荷字段中的有效载荷数据的长度。
具体的，在一种可能的实现方式中，该第二指示信息还可以指示报文的有效载荷数据的位置信息。具体的，该报文的有效载荷数据的位置信息可以是报文的载荷字段中有效载荷数据的起始位置和结束位置。
需要说明的是，在实际应用过程中，第二指示信息可以包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个。
具体的，在一种可能的实现方式中，该填充冗余数据是以太报文发送端在媒体介入控制(Media Acess Control，MAC)层添加的。
具体的，在另一种可能的实现方式中，该填充冗余数据是以太报文发送端在高层添加的，该高层是指MAC层以上的协议层，例如应用层。
该业务描述信息包括(数据网络名称，Data Network Name，DNN)，应用标识或者业务过滤信息(traffic filtering information)。其中，该业务描述信息用于表示第二指示信息针对的应用。例如，如果业务描述信息中包括DNN，则第二指示信息适用于该DNN的所有的应用的业务报文；如果业务描述信息中包括应用标识，则第二指示信息适用于应用标识对应的应用的报文；如果业务描述信息中包括业务过滤信息，则第二指示信息适用于业务过滤信息对应的报文。其中，业务过滤信息为以太报文过滤信息，具体可以包括业务报文的源MAC地址，目的MAC地址，VLAN标识等中的至少一项。
在实际应用过程中，该AF请求消息可以是直接发给策略控制网元的，也可以是先发给NEF，再由NEF转发给策略控制网元的，具体此处不做限定。
在步骤203中，策略控制网元向会话管理网元发送策略更新消息。
策略控制网元在接收到会话管理网元发送的AF请求消息之后，策略控制网元获取AF请求消息中的第二指示信息和业务数据流(Service Data Flow，SDF)模板，根据该第二指示信息生成第一指示信息，并将该第一指示信息和SDF模板携带在策略更新消息中，发送给会话管理网元。其中，SDF模板包括策略控制网元在步骤202中收到的应用标识或者业务过滤信息，或者在步骤202中收到的DN对应的一个或多个应用的应用标识或者业务过滤信息。其中，第一指示信息用于删除或者增加该SDF模板描述的业务的报文的填充冗余数据。
具体的，在一种可能的实现方式中，该策略更新消息中包括PCC规则，该PCC规则进一步包括了第一指示信息和SDF模板。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示第一填充冗余数据填充冗余数据的长度信息。具体的，该第一填充冗余数据填充冗余数据的长度信息可以是报文载荷(payload)字段中的填充冗余数据(padding)的长度。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示第一填充冗余数据填充冗余数据的位置信息。具体的，该第一填充冗余数据填充冗余数据的位置信息可以是报文的载荷字段中的填充冗余数据的起始位置和结束位置。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示报文的有效载荷数据的长度信息。具体的，该报文的有效载荷数据的长度信息可以是报文载荷字段中的有效载 荷数据的长度。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示报文的有效载荷数据的位置信息。具体的，该报文的有效载荷数据的位置信息可以是报文的载荷字段中有效载荷数据的起始位置和结束位置。
需要说明的是，在实际应用过程中，第一指示信息可以包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个，当第一指示信息包含了上述信息中的一个或者多个时，则接收到该第一指示信息的设备可以根据该第一指示信息对填充冗余数据进行增加或者删除。或者，在一种可能的实现方式中，该第一指示信息还可以包含要增加或者删除填充冗余数据的指示，用于指示接收到该第一指示信息的设备在接收到业务报文时根据第一指示信息对填充冗余数据进行增加或者删除。或者，在一种可能的实现方式中，该第一指示信息只包含要增加或者删除填充冗余数据的指示，则接受到该第一指示信息的设备在接收到业务报文时根据该第一指示信息，增加或者删除填充冗余数据。
当会话管理网元SMF接收到策略更新消息之后，SMF根据策略更新消息执行会话管理。
具体的，SMF将从策略更新消息中获取的策略和计费控制(Policy and Charging Control，PCC)规则与某个现有的QoS流(QoS Flow)绑定，或者根据PCC规则中的参数派生QoS参数生成新的QoS Flow后将PCC规则与该QoS Flow绑定。其中，PCC规则中包括第一指示信息和SDF模板，将PCC规则与QoS Flow绑定可以理解为将PCC规则应用到该QoS Flow，即PCC规则中的SDF模板对应的一个或多个业务流都绑定到该QoS Flow，若多个业务流绑定到同一个QoS Flow，则这些业务流具有相同的QoS需求，且第一指示信息中包括的填充冗余数据长度信息相同。
在步骤204中，会话管理网元向用户面网元发送N4会话修改请求。
会话管理网元SMF获取策略更新消息中的第一指示信息和SDF模板，根据策略更新消息中的PCC规则，生成数据包检测规则(Packet Detection Rule，PDR)和转发动作规则(Forwarding Action Rule，FAR)，PDR中包括SDF模板。其中，SDF模板也可以由应用标识以及包过滤集合(Packet Filer Set)替代，包过滤集合中包括了SDF模板中的业务过滤信息。在一种可能的实现方式中，FAR中包括第一指示信息。SMF将该PDR和FAR通过N4会话修改请求消息发送给用户面网元UPF。UPF使用PDR检测接收到的数据包，当与业务过滤信息匹配的时候，根据FAR中的第一指示信息执行相应的包转发动作，如删除填充冗余数据或添加填充冗余数据。在一种可能的实现方式中，当SDF模板中的包过滤器对应的业务为下行业务时，FAR中包括的第一指示信息包含删除填充冗余数据的指示；当SDF模板中的包过滤器对应的业务为上行业务时，FAR中包括的第一指示信息包含增加填充冗余数据的指示。
在步骤205中，会话管理网元向用户设备发送N1接口会话管理消息。
会话管理网元获取策略更新消息中的第一指示信息和SDF模板，根据策略更新消息中的PCC规则，生成QoS规则(QoS Rule)，QoS规则中包括QoS Flow标识，还包括第一指示信息和QoS Flow标识对应的包过滤集合(Packet Filer Set)。SMF通过N1接口会话管理信息将QoS规则发送给用户设备UE。可选的，第一指示信息也可以不包括在QoS Rule 中，也就是说，会话管理网元通过N1接口会话管理消息向用户设备发送第一指示信息以及对应的QoS Flow标识，指示用户设备该第一指示信息是针对该QoS Flow标识所标识的QoS Flow。
需要说明的是，这里的N1接口会话管理消息是SMF通过AMF发送给无线接入网络设备的，再通过无线接入网设备发送给用户设备的。N1接口会话管理消息具体携带PDU会话修改命令，也就是说，N1接口会话管理消息中包括PDU会话修改命令；PDU会话修改命令中包括QoS Rule，QoS Rule中包括QoS Flow标识和第一指示信息，或者，PDU会话修改命令中包括的QoS Flow标识以及第一指示信息，可选的，还包括QoS Rule。
在一种可能的实现方式中，当QoS Rule中携带的包过滤集合中的包过滤器对应的业务为上行业务时，第一指示信息包含删除填充冗余数据的指示；当QoS Rule中携带的包过滤集合中的包过滤器对应的业务为下行业务时，第一指示信息包含增加填充冗余数据的指示。
步骤204和步骤205的执行顺序不做限定。可以是，SMF在步骤203之后，发起PDU会话修改流程，在PDU会话修改流程中，先执行步骤205，再执行步骤204；也可以先执行步骤204，再执行步骤205；也可以同时执行步骤204和步骤205，具体此处不做限定。需要说明的是，步骤204和步骤205中包括的第一指示信息可以不同，比如，步骤204第一指示信息用于指示删除填充冗余数据，步骤205中第一指示信息用于指示增加填充冗余数据；或者，步骤204第一指示信息用于指示增加填充冗余数据，步骤205中第一指示信息用于指示删除填充冗余数据。
在步骤206中，用户面网元接收第一报文。
第一报文为以太报文，当下行数据传输时，用户面网元会接收到下行的一个或者多个第一报文，该一个或者多个第一报文对应一个QoS Flow标识。
具体的，在一种可能的实现方式中，该第一报文为以太网Ethernet II帧格式。具体的，如图8所示，该第一报文中包含了前导码字段，起始帧分隔符(Start Frame Delimiter，SFD)字段，目的MAC地址字段，源MAC地址字段，类型字段，数据载荷字段，帧校验序列(Frame Check Sequence，FCS)字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
具体的，在一种可能的实现方式中，该第一报文为以太网IEEE 802.3帧格式。具体的，如图9所示，该第一报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，长度字段，逻辑链路控制(Logic Link Control，LLC)字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
在步骤207中，用户面网元删除第一报文中的填充冗余数据。
用户面网元在接收到第一报文之后，用户面网元删除第一报文中的填充冗余数据。
具体的，用户面网元检测收到的第一报文，根据在步骤204中接收到的PDR，确定第一报文匹配步骤204中接收到的PDR，根据在步骤204中接收到的FAR中的第一指示信息删除填充冗余数据。
具体的，当第一报文为以太网Ethernet II帧格式时，用户面网元根据第一指示信息删除第一报文中的填充冗余数据。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户面网元根据填 充冗余数据的长度信息，将第一报文中载荷部分的填充冗余数据删除。示例性的，用户面网元根据图8或图9中的帧格式，可以确定填充冗余数据的结束位置，再根据第一指示信息中包含的填充冗余数据的长度，可以确定填充冗余数据的起始位置，进而可以根据该起始位置和结束位置，删除填充冗余数据。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户面网元根据填充冗余数据的位置信息，从第一报文的载荷部分找到填充冗余数据的起始位置和结束位置，将起始位置开始到结束位置的数据删除。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户面网元根据有效载荷数据的长度信息，将第一报文的载荷部分中除了有效载荷数据之外的数据删除，即删除填充冗余数据。示例性的，用户面网元根据图8或图9中的帧格式，可以确定填充冗余数据的结束位置，再根据第一指示信息中包含的填充冗余数据的长度，可以确定填充冗余数据的起始位置，进而可以根据该起始位置和结束位置，删除填充冗余数据。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户面网元根据有效载荷数据的位置信息，从第一报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将有效载荷数据起始位置到结束位置之外的数据删除，即删除填充冗余数据。
具体的，当第一报文为以太网IEEE802.3帧格式时，用户面网元可以根据第一指示信息确定填充冗余数据在第一报文中的位置，还可以根据如图9所示的长度(Length)字段确定填充冗余数据在第一报文中的位置，进而根据填充冗余数据在第一报文中的位置，删除第一报文中的填充冗余数据。具体的，根据Length字段将第一报文的载荷部分中除了Length字段对应的有效载荷数据之外的数据删除，即删除填充冗余数据。
需要说明的是，在实际应用过程中，第一指示信息可以只包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个，当第一指示信息包含了上述信息中的一个或者多个时，则用户面网元可以根据该第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息还可以包含要删除填充冗余数据的指示，用于指示用户面网元根据第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息只包含要删除填充冗余数据的指示，则用户面网元根据该第一指示信息，删除填充冗余数据。
在步骤208中，用户面网元生成第二报文，并向无线接入网络设备发送第二报文。
用户面网元在删除了第一报文的填充冗余数据之后，用户面网元生成第二报文，该第二报文中的载荷数据为第一报文中删除了填充冗余数据之后的有效载荷数据，并向无线接入网络设备发送第二报文。
具体的，用户面网元删除了第一报文的填充冗余数据之后，根据N3隧道协议对删除了填充冗余数据的第一报文进行封装，得到第二报文。具体的，在一种可能的实现方式中，这里的N3隧道协议可以是通用分组无线业务隧道协议用户面(general packet radio service tunneling protocol user plane，GTP-U)协议，可以理解的是，在实际应用过程中，还可以是其他隧道协议，具体此处不做限定。可选的，用户面网元在根据N3隧道协议对删除了填充冗余数据的第一报文进行封装，得到第二报文之前，用户面网元还删除第一报文中的前导码字段、SFD字段以及FCS字段。即第一报文中的前导码字段、SFD字段以 及FCS字段不在用户面网元、无线接入网设备以及用户设备之间传输。
示例性的，若第一报文格式为图8所示的以太网Ethernet II帧格式，且第一报文包括填充字段，则第二报文的格式为图10所示，其中，第二报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与第一报文中的相应的字段相同；而N3隧道协议头字段包括图10中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图10中的FSC字段与第一报文不同，图10中的FCS字段是用户面网元根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图10中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段。
若第一报文格式为图9所示的IEEE 802.3帧格式时，第二报文的格式为图11所示，其中，第二报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第一报文中的相应的字段相同；而N3隧道协议头字段包括图11中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图11中的FSC字段与第一报文不同，图11中的FCS字段是用户面网元根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图11中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、长度字段以及有效载荷字段。
需要说明的是，在小包传输的应用场景下，用户面网元删除了第一报文的填充冗余数据之后，整个报文的数据长度可能会小于以太网最小帧长，例如小于64字节。但是在增加了图10或图11中所示的N3隧道协议的协议头之后，第二报文的数据长度会大于或等于64字节，因此符合协议规定的以太网报文需满足以太网最小帧长的要求。其中，第一报文的数据长度是图8或图9中所示的报文格式中不包括前导码字段、SFD字段和FCS字段的剩余部分的长度之和，第二报文的数据长度是图10或图11中所示的报文格式中不包括N3MAC头字段和FCS字段的剩余部分的长度之和。
在工业小包场景下，示例性的，N3隧道协议可能采用更简化的协议栈，示例性的，若N3隧道协议不采用图10或图11中所示的UDP、IP以及GTP-U协议层，而采用其它的协议层，如，仅采用GTP-U层，即第二报文不包括图10或图11中所示的P头字段以及UDP头字段，或第二报文不包括图10或图11中所示的IP头字段、UDP头字段以及GTP-U头字段，第二报文的数据长度可能会小于64字节，此时，有两种方式：
方式一：用户面网元根据N3隧道协议对第三报文进行封装得到第四报文，若第四报文的数据长度小于以太网最小帧长，则在第四报文的N3隧道协议头中增加隧道协议填充冗余数据生成第二报文，第二报文的数据长度大于或者等于以太网最小帧长。
方式二：若用户面网元确定其根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则用户面网元根据N3隧道协议对第三报文进行封装得封装报文，并在该封装报文的N3隧道协议头中增加隧道协议填充冗余数据生成第二报文，第二报文的数据长度大于或者等于以太网最小帧长。
可选的，用户面网元在执行上述方式一或方式二的操作之前，从会话管理网元接收第 三指示信息，该第三指示信息用于指示用户面网元在对将在N3隧道发送的报文进行以太帧长度检查，当报文的以太帧长度小于64字节时，增加隧道协议填充冗余数据。具体的，可以在会话管理网元向用户面网元发送N4会话修改请求的步骤中，通过在N4会话修改请求携带该第三指示信息。
上述方式一和方式二中第三报文为第一报文删除填充冗余数据后的报文，需要说明的是，用户面网元删除第一报文中的填充冗余数据后，可以先生成第三报文，再根据第三生成报文生成第四报文或第二报文，也可以不包括生成第三报文的过程，直接针对删除填充冗余数据后的第一报文进行操作。
需要说明的是，N3隧道协议是指用户面网元与接入网节点之间的隧道协议，本发明中N3隧道协议可以被其他可能用于用户面网元与接入网节点之间的传输数据的隧道协议替代。
在步骤209中，无线接入网络设备向用户设备发送第五报文。
无线接入网络设备在接收到用户面网元发送的第二报文之后，无线接入网络设备将第二报文中的N3隧道协议头剥除，并添加空口协议头，生成第五报文，并将第五报文发送给用户设备。
示例性的，若第一报文格式为图8所示的以太网Ethernet II帧格式，第五报文的格式如图12所示，其中，第五报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与第二报文中的相应的字段相同；图12中的AN协议头又称为空口协议头，示例性的，具体可以包括，分组数据汇聚协议(packet data convergence protocol，PDCP)头，无线链路控制(Radio Link Control，RLC)头以及MAC头。
若第一报文格式为图9所示的IEEE 802.3帧格式，第五报文的格式如图7所示，其中，第五报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第二报文中的相应的字段相同；图7中的AN协议头又称为空口协议头，示例性的，具体可以包括，PDCP头，RLC头以及MAC头。
需要说明的是，无线接入网络设备向用户设备发送报文的方式为空口传输的方式，不受以太网最小帧长的要求限制，因此第二报文在剥除了N3隧道协议头之后，长度小于64字节，即第五报文的长度小于64字节也可以进行传输。且因为在之前的步骤中，已经删除了第一报文中载荷部分的填充冗余数据，也就是说第五报文的载荷部分不包括填充冗余数据，因此在空口传输时，可以节省空口资源。
在一种可能的实现方式中，当用户设备接收到第五报文后，用户设备应用层可以直接获取该第五报文的载荷数据部分进行使用。
或者，在一种可能的实现方式中，当用户设备是网络的中间节点，需要继续向下一跳节点转发以太帧的时候，则用户设备在该第五报文的载荷部分补充填充冗余数据，生成第六报文，使得第六报文的数据长度大于或等于64字节。可选的，在一种可能的实现方式中，如果用户面网元在根据N3隧道协议对删除了填充冗余数据的第一报文进行封装，得到第二报文之前，用户面网元还删除了第一报文中的前导码字段、SFD字段以及FCS字段，则用户设备还要补充其它字段生成第六报文，如FCS字段，前导码字段和SFD字段，具体此处不做限定。其中，第六报文的格式可以与第一报文的格式相同，也就是说，若第一报文为 图8所示的以太网Ethernet II帧格式，则第六报文也为以太网Ethernet II类型的以太帧，若第一报文格式为图9所示的IEEE 802.3帧格式，则第六报文也为IEEE 802.3类型的以太帧。优选的，在补充完填充冗余数据之后，该第六报文的数据长度和第一报文的数据长度相同。其中，第一报文或第六报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第六报文与第一报文相同。
具体的，用户设备可以将第六报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，用户设备可以根据第一指示信息在第五报文的载荷部分补充填充冗余数据，生成第六报文，使得该第六报文的数据长度大于或等于64字节。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户设备根据填充冗余数据的长度信息，将填充冗余数据填充至第五报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户设备根据填充冗余数据的位置信息，从第五报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户设备根据有效载荷数据的长度信息，将填充冗余数据填充至第五报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户设备根据有效载荷数据的位置信息，从第五报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，用户设备根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第五报文填充填充冗余数据。
在步骤210中，用户设备接收第七报文，该第七报文为上行以太报文。
第七报文为以太报文，当上行数据传输时，用户设备会获取上行的一个或者多个上行以太报文，其中，上行以太报文即第七报文。当用户设备有上一跳节点时，用户设备接收上一跳节点发送的上行以太报文。当用户设备没有上一跳节点时，用户设备生成上行以太报文。
具体的，在一种可能的实现方式中，该上行以太报文为以太网Ethernet II帧格式。具体的，如图8所示，该上行以太报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，类型字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
具体的，在一种可能的实现方式中，该上行以太报文为以太网IEEE802.3帧格式。具体的，如图9所示，该上行以太报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，净荷长度字段，LLC字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
在步骤211中，用户设备删除第七报文中的填充冗余数据。
用户设备在获取到第七报文之后，用户设备删除第七报文中的填充冗余数据。
具体的，当第七报文为以太网Ethernet II帧格式时，用户设备根据第一指示信息删除第七报文中的填充冗余数据。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户设备根据填充冗余数据的长度信息，将第七报文中载荷部分的填充冗余数据删除。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户设备根据填充冗余数据的位置信息，从第七报文的载荷部分找到填充冗余数据的起始位置和结束位置，将起始位置开始到结束位置的数据删除。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户设备根据有效载荷数据的长度信息，将上行以太报文的载荷部分中除了有效载荷数据之外的数据删除，即删除填充冗余数据。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户设备根据有效载荷数据的位置信息，从第七报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将有效载荷数据起始位置到结束位置之外的数据删除，即删除填充冗余数据。
具体的，当第七报文为以太网IEEE802.3帧格式时，用户设备元可以根据第一指示信息确定填充冗余数据在第七报文中的位置，还可以根据长度(Length)字段确定填充冗余数据在第七报文中的位置，根据填充冗余数据在第七报文中的位置，删除第七报文中的填充冗余数据。具体的，根据Length字段将第七报文的载荷部分中除了Length字段对应的有效载荷数据之外的数据删除，即删除第七报文的填充冗余数据。
在步骤212中，用户设备生成第八报文，并向无线网络设备发送第八报文。
用户设备在删除了第七报文的填充冗余数据之后，生成第八报文，该第八报文中的载荷数据为第七报文中删除了填充冗余数据之后的有效载荷数据。
具体的，用户设备删除了第七报文的填充冗余数据之后，根据空口协议对删除了填充冗余数据的第七报文进行封装，得到第八报文。
示例性的，若第七报文格式为图8所示的以太网Ethernet II帧格式，且第七报文包括填充字段，则第八报文的格式为图12所示，其中，第八报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与接收到的第七报文中的相应的字段相同；图12中的AN协议头又称为空口协议头，示例性的，具体可以包括，PDCP头、RLC头以及MAC头。
若第七报文格式为图9所示的IEEE802.3帧格式时，第八报文的格式为图7所示，其中，第八报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与接收到的第七报文中的相应的字段相同；图7中的AN协议头又称为空口协议头，示例性的，具体可以包括，PDCP头、RLC头以及MAC头。
用户设备在生成了第八报文之后，向无线接入网络设备发送第八报文。
可选的，用户设备除了删除第七报文中的填充冗余数据外，还删除第七报文中的前导码字段、SFD字段以及FCS字段。即第七报文中的前导码字段、SFD字段以及FCS字段不在用户设备、无线接入网设备以及用户面网元之间传输。
需要说明的是，用户设备向无线接入网络设备发送报文的方式为空口传输的方式，不受以太网最小帧长的要求限制，因此上行以太报文的数据长度小于64字节也可以进行传 输。且因为在之前的步骤中，已经删除了第七报文中载荷部分的填充冗余数据，也就是说第八报文的载荷部分不包括填充冗余数据，因此在空口传输时，可以节省空口资源。
在步骤213中，无线接入网络设备向用户面网元发送第九报文。
无线接入网络设备在接收到用户设备发送第八报文之后，无线接入网络设备将第八报文中的空口协议头剥除，并添加N3隧道协议头，生成第九报文，并向用户面网元发送第九报文。
示例性的，若第七报文格式为图8所示的以太网Ethernet II帧格式，第九报文的格式如图10所示，其中，第九报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与第八报文中的相应的字段相同；而N3隧道协议头字段包括图10中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图10中的FSC字段与第一报文不同，图10中的FCS字段是无线接入网设备根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图10中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段。
若第七报文格式为图9所示的IEEE 802.3帧格式时，第九报文的格式为图11所示，其中，第九报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第八报文中的相应的字段相同；而N3隧道协议头字段包括图11中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图11中的FSC字段与第一报文不同，图11中的FCS字段是无线接入网设备根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图11中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、长度字段以及有效载荷字段。
需要说明的是，在工业小包传输的应用场景下，用户设备删除了第七报文的填充冗余数据之后，第八报文的数据长度可能会小于以太网最小帧长，例如小于64字节。但是在增加了图10或图11中所示的N3隧道协议的协议头之后，第九报文的数据长度可能会大于或等于64字节，因此符合协议规定的以太网报文需满足以太网最小帧长的要求。其中，第七报文的数据长度是图8或图9中所示的报文格式中不包括前导码字段、SFD字段和FCS字段的剩余部分的长度之和，第九报文的数据长度是图10或图11中所示的报文格式中不包括N3 MAC头字段和FCS字段的剩余部分的长度之和。
具体的，无线接入网络设备根据N3隧道协议对第八报文进行封装，得到第九报文。具体的，在一种可能的实现方式中，这里的N3隧道协议可以是GTP-U协议，可以理解的是，在实际应用过程中，还可以是其他N3隧道协议，具体此处不做限定。例如，在工业场景下，示例性的，N3隧道协议可能采用更简化的协议栈，示例性的，若N3隧道协议不采用图10或图11中所示的UDP、IP以及GTP-U协议层，而采用其它的协议层，如，仅采用GTP-U层，即第九报文不包括图10或图11中所示的IP头字段以及UDP头字段，或第二报文不包括图10或图11中所示的IP头字段、UDP头字段以及GTP-U头字段，第九报文的数据长度可能会小于64字节，此时，有两种方式：
方式一：无线接入网设备根据N3隧道协议对第八报文进行封装得到第十报文，若第十 报文的数据长度小于以太网最小帧长，则在第十报文的N3隧道协议头中增加隧道协议填充冗余数据生成第九报文，第九报文的数据长度大于或者等于以太网最小帧长。
方式二：若无线接入网设备确定其根据N3隧道协议对第八报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则用户面网元根据N3隧道协议对第八报文进行封装得封装报文，并在该封装报文的N3隧道协议头中增加隧道协议填充冗余数据生成第九报文，第九报文的数据长度大于或者等于以太网最小帧长。
可选的，无线接入网设备在执行上述方式一或方式二的操作之前，从会话管理网元接收第二指示信息，该第二指示信息用于指示无线接入网设备在对将在N3隧道发送的报文进行以太帧长度检查，当报文的以太帧长度小于64字节时，增加隧道协议填充冗余数据。具体的，可以在会话管理网元向无线接入网设备发送控制面消息时携带该第二指示信息。
也就是说，上述方式一中无线接入网设备，先生成第十报文，再根据第十生成报文生成第九报文，方式二中可以不包括生成第十报文的过程，直接根据第八报文生成第九报文。
需要说明的是，N3隧道协议是指用户面网元与接入网节点之间的隧道协议，本发明中N3隧道协议可以被其他可能用于用户面网元与接入网节点之间的传输数据的隧道协议替代。
在步骤214中，用户面网元增加第九报文的填充冗余数据。
用户面网元在接收到第九报文之后，用户面网元剥除该N3隧道协议头，并增加填充冗余数据，生成第十一报文，使得第十一报文的数据长度大于或等于64字节，可选地，如果用户设备除了删除了第七报文中的填充冗余数据外，还删除了第七报文中的前导码字段、SFD字段以及FCS字段，则用户面网元还补充其它字段生成第十一报文，如FCS字段，前导码字段和SFD字段，具体此处不做限定。其中第十一报文的格式与第七报文相同，也就是说，若第七报文为图8所示的以太网Ethernet II帧格式，则第十一报文也为以太网Ethernet II类型的以太帧，若第七报文格式为图9所示的IEEE 802.3帧格式，则第十一报文也为IEEE 802.3类型的以太帧。优选的，在补充完填充冗余数据之后，该第十一报文的数据长度和第七报文的数据长度相同。其中，第七报文或第十一报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第十一报文与第七报文相同。
具体的，用户设备可以将第十一报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，用户面网元可以根据第一指示信息在该第九报文的载荷部分补充填充冗余数据，生成第十一报文，使得该第十一报文的数据长度大于或等于64字节。具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户面网元根据填充冗余数据的长度信息，将填充冗余数据填充至第九报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户面网元根据填充冗余数据的位置信息，从第九报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户面网元根据有效载 荷数据的长度信息，将填充冗余数据填充至第九报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户面网元根据有效载荷数据的位置信息，从第九报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，用户面网元根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第九报文进行填充填充冗余数据。
在步骤215中，用户面网元发送第十一报文。
用户面网元将第十一报文发送给下一跳节点。
本实施例中，步骤206至步骤209为发送下行报文的应用场景，步骤210至步骤215为发送上行报文的应用场景。在实际应用过程中，步骤206至步骤209可以单独实施，步骤210至步骤215也可以单独实施，还可以合并实施，具体此处不做限定。
本申请实施例中，用户面设备通过将接收到的下行报文中的填充冗余数据删除使得在空口传输给用户设备的下行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例中，用户设备通过将接收到的上行报文中的填充冗余数据删除，使得在空口传输给无线接入网设备的上行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
请参阅图3，为本申请实施例另一个流程示意图。
在步骤301中，用户设备建立PDU会话。
在步骤302中，应用功能网元向策略控制网元发送AF请求消息。
在步骤303中，策略控制网元向会话管理网元发送策略更新消息。
在步骤304中，会话管理网元向用户面网元发送N4会话修改请求。
本实施例中，步骤301至步骤304与前述图2所示实施例中步骤201至步骤204中所执行的方法类似，具体此处不再赘述。
在步骤305中，会话管理网元向无线接入网络设备发送N2接口会话管理消息。
会话管理网元获取策略更新消息中的第一指示信息和SDF模板，根据策略更新消息中的PCC规则，生成QoS Flow对应的QoS配置文件(QoS Profile)，QoS Profile规则中包括包括第一指示信息。SMF通过N2接口会话管理信息将包括了QoS Profile以及对应的Qos Flow标识发送给无线接入网设备。可选的，第一指示信息也可以不包括在QoS Profile中，也就是说，会话管理网元通过N2接口会话管理消息向无线接入网设备发送第一指示信息以及对应的QoS Flow标识，指示无线接入网设备该第一指示信息是针对该QoS Flow标识所标识的QoS Flow。
需要说明的是，这里的N2接口会话管理消息是SMF通过AMF发送给无线接入网络设备的。
步骤304和步骤305的执行顺序不做限定。可以是，SMF在步骤303之后，发起PDU会话修改流程，在PDU会话修改流程中，先执行步骤305，再执行步骤304；也可以先执行步骤304，再执行步骤305；也可以同时执行步骤304和步骤305，具体此处不做限定。
需要说明的是，步骤304和步骤305中包括的第一指示信息可以不同，比如，步骤304第一指示信息用于指示删除填充冗余数据，步骤305中第一指示信息用于指示增加填充冗余数据；或者，步骤304第一指示信息用于指示增加填充冗余数据，步骤305中第一指示信息用于指示删除填充冗余数据。
在步骤306中，无线接入网络设备向用户设备发送无线资源控制(Radio Resource Control，RRC)重配置信令。
无线接入网络设备获取N2接口会话管理消息中的第一指示信息和QoS Flow标识，并将第一指示信息和QoS Flow标识携带在RRC重配置信令中，向用户设备发送该RRC重配置信令。
在步骤307中，用户面网元接收第一报文。
在步骤308中，用户面网元删除第一报文中的填充冗余数据。
在步骤309中，用户面网元生成第二报文，并向无线接入网络设备发送第二报文。
在步骤310中，无线接入网络设备向用户设备发送第五报文。
在步骤311中，用户设备接收第七报文，所述第七报文为上行以太报文。
在步骤312中，用户设备删除第七报文中的填充冗余数据。
在步骤313中，用户设备生成第八报文，并向无线网络设备发送第八报文。
在步骤314中，无线接入网络设备向用户面网元发送第九报文。
在步骤315中，用户面网元增加第九报文的填充冗余数据。
在步骤316中，用户面网元发送第十一报文。
本实施例中，步骤307至步骤316与前述图2所示实施例中步骤206至步骤215中所执行的方法类似，具体此处不再赘述。
本实施例中，步骤307至步骤310为发送下行报文的应用场景，步骤311至步骤316为发送上行报文的应用场景。在实际应用过程中，步骤307至步骤310可以单独实施，步骤311至步骤316也可以单独实施，还可以合并实施，具体此处不做限定。
本申请实施例中，用户面设备通过将接收到的下行报文中的填充冗余数据删除使得在空口传输给用户设备的下行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例中，用户设备通过将接收到的上行报文中的填充冗余数据删除，使得在空口传输给无线接入网设备的上行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
请参阅图4，为本申请实施例提供的数据传输方法另一流程示意图。
在步骤401中，用户设备建立PDU会话。
在步骤402中，应用功能网元向策略控制网元发送AF请求消息。
在步骤403中，策略控制网元向会话管理网元发送策略更新消息。
本实施例中，步骤401至步骤403与前述图3所示实施例中步骤301至步骤303中所执行的方法类似，具体此处不再赘述。
在步骤404中，会话管理网元向无线接入网络设备发送N2接口会话管理消息。
会话管理网元获取策略更新消息中的第一指示信息和SDF模板，根据策略更新消息中 的PCC规则，生成QoS Flow对应的QoS配置文件(QoS Profile)，QoS Profile规则中包括包括第一指示信息。SMF通过N2接口会话管理信息将包括了QoS Profile以及对应的Qos Flow标识发送给无线接入网设备。可选的，第一指示信息也可以不包括在QoS Profile中，也就是说，会话管理网元通过N2接口会话管理消息向无线接入网设备发送第一指示信息以及对应的QoS Flow标识，指示无线接入网设备该第一指示信息是针对该QoS Flow标识所标识的QoS Flow。
需要说明的是，这里的N2接口会话管理消息是SMF通过AMF发送给无线接入网络设备的。
在步骤405中，会话管理网元向用户设备发送N1接口会话管理消息。
会话管理网元获取策略更新消息中的第一指示信息和SDF模板，根据策略更新消息中的PCC规则，生成QoS规则(QoS Rule)，QoS规则中包括QoS Flow标识，还包括第一指示信息和QoS Flow标识对应的包过滤集合。SMF通过N1接口会话管理信息将QoS规则发送给用户设备UE。可选的，第一指示信息也可以不包括在QoS Rule中，也就是说，会话管理网元通过N1接口会话管理消息向用户设备发送第一指示信息以及对应的QoS Flow标识，指示用户设备该第一指示信息是针对该QoS Flow标识所标识的QoS Flow。
需要说明的是，这里的N1接口会话管理消息是SMF通过AMF发送给无线接入网络设备的，再通过无线接入网设备发送给用户设备的。N1接口会话管理消息具体携带PDU会话修改命令，也就是说，N1接口会话管理消息中包括PDU会话修改命令；PDU会话修改命令中包括QoS Rule，QoS Rule中包括QoS Flow标识和第一指示信息，或者，PDU会话修改命令中包括的QoS Flow标识以及第一指示信息，可选的，还包括QoS Rule。
步骤404和步骤405的执行顺序不做限定。可以是，SMF在步骤403之后，发起PDU会话修改流程，在PDU会话修改流程中，先执行步骤405，再执行步骤404；也可以先执行步骤404，再执行步骤405；也可以同时执行步骤404和步骤405，具体此处不做限定。
需要说明的是，步骤404和步骤405中包括的第一指示信息可以不同，比如，步骤404第一指示信息用于指示删除填充冗余数据，步骤405中第一指示信息用于指示增加填充冗余数据；或者，步骤404第一指示信息用于指示增加填充冗余数据，步骤405中第一指示信息用于指示删除填充冗余数据。
需要说明的是，本实施例中，也可以通过无线接入网络设备RAN向用户设备发送第一指示信息和QoS Flow标识，即和上述图3所示实施例中步骤306中所执行的方法类似，具体此处不再赘述。当通过RAN向用户设备发送第一指示信息和SDF模板对应的QoS Flow标识时，则不执行步骤405。
在步骤406中，用户面网元接收第一报文。
在步骤407中，用户面网元向无线接入网络设备发送第十二报文。
用户面网元在接收到第一报文之后，根据N3隧道协议对第一报文进行封装，得到第十二报文。具体的，在一种可能的实现方式中，这里的N3隧道协议可以是GTP-U协议，可以理解的是，在实际应用过程中，还可以是其他隧道协议，具体此处不做限定。
示例性的，若第一报文格式为图8所示的以太网Ethernet II帧格式，且第一报文包括填充字段，则第十二报文的格式为图10所示，其中，第十二报文的目的MAC地址字段、 源MAC地址字段、类型字段以及有效载荷字段均与第一报文中的相应的字段相同；而N3隧道协议头字段包括图10中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图10中的FSC字段与第一报文不同，图10中的FCS字段是用户面网元根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图10中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段。
若第一报文格式为图9所示的IEEE 802.3帧格式时，第十二报文的格式为图11所示，其中，第十二报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第一报文中的相应的字段相同；而N3隧道协议头字段包括图11中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图11中的FSC字段与第一报文不同，图11中的FCS字段是用户面网元根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图11中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、长度字段以及有效载荷字段。
可选的，用户面网元在根据N3隧道协议对第一报文进行封装得到第十二报文之前，用户面网元还删除第一报文中的前导码字段、SFD字段以及FCS字段。即第一报文中的前导码字段、SFD字段以及FCS字段不在用户面网元、无线接入网设备以及用户设备之间传输。
需要说明的是，N3隧道协议是指用户面网元与接入网节点之间的隧道协议，本发明中N3隧道协议可以被其他可能用于用户面网元与接入网节点之间的传输数据的隧道协议替代。
在步骤408中，无线接入网络设备删除填充冗余数据。
无线接入网络设备在接收到第十二报文之后，无线接入网络设备将第十二报文中的N3隧道协议头剥除，且删除第十二报文中的填充冗余数据。
具体的，无线接入网络设备在接收到第十二报文之后，根据在步骤404中接收到的第一指示信息删除填充冗余数据。
具体的，当第一报文为以太网Ethernet II帧格式时，无线接入网络设备根据第一指示信息删除第十二报文中的填充冗余数据。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则无线接入网络设备根据填充冗余数据的长度信息，将第十二报文中载荷部分的填充冗余数据删除。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，无线接入网络设备根据填充冗余数据的位置信息，从第十二报文的载荷部分找到填充冗余数据的起始位置和结束位置，将起始位置开始到结束位置的数据删除。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，无线接入网络设备根据有效载荷数据的长度信息，将第十二报文的载荷部分中除了有效载荷数据之外的数据删除，即删除填充冗余数据。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，无线接入网络设备根据有效载荷数据的位置信息，从第十二报文的载荷部分找出有效载荷数据的起始位置和结束 位置，并将有效载荷数据起始位置到结束位置之外的数据删除，即删除填充冗余数据。
具体的，当第一报文为以太网IEEE802.3帧格式时，无线接入网络设备可以根据第一指示信息确定填充冗余数据的在第十二报文中的位置，还可以根据如图9所示中的长度(Length)字段确定填充冗余数据在第十二报文中的位置，进而根据填充冗余数据在第十二报文中的位置，删除第十二报文中的填充冗余数据。具体的，根据Length字段将第十二报文的载荷部分中除了Length字段对应的有效载荷数据之外的数据删除，即删除填充冗余数据。
需要说明的是，在实际应用过程中，第一指示信息可以只包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个，当第一指示信息包含了上述信息中的一个或者多个时，则无线接入网络设备可以根据该第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息还可以包含要删除填充冗余数据的指示，用于指示无线接入网络设备根据第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息只包含要删除填充冗余数据的指示，则无线接入网络设备根据该第一指示信息，删除填充冗余数据。
在步骤409中，无线接入网络设备向用户设备发送第二报文。
无线接入网络设备在删除了第十二报文的填充冗余数据之后就，添加空口协议头，生成第二报文。并将第二报文发送给用户设备。
示例性的，若第十二报文格式为图8所示的以太网Ethernet II帧格式，第二报文的格式如图12所示，其中，第二报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与第十二报文中的相应的字段相同；图12中的AN协议头又称为空口协议头，示例性的，具体可以包括，PDCP头，RLC头以及MAC头。
若第十二报文格式为图9所示的IEEE 802.3帧格式，第二报文的格式如图7所示，其中，第二报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第十二报文中的相应的字段相同；图7中的AN协议头又称为空口协议头，示例性的，具体可以包括，PDCP头，RLC头以及MAC头。
需要说明的是，无线接入网络设备向用户设备发送报文的方式为空口传输的方式，不受以太网最小帧长的要求限制，因此第十二报文在剥除了N3隧道协议头之后，长度小于64字节，即第二报文的长度小于64字节也可以进行传输。且因为已经删除了第十二报文中载荷部分的填充冗余数据，也就是说第二报文的载荷部分不包括填充冗余数据，因此在空口传输时，可以节省空口资源。
在一种可能的实现方式中，当用户设备接收到第二报文后，用户设备应用层可以直接获取该第二报文的载荷数据部分进行使用。
或者，在一种可能的实现方式中，当用户设备是网络的中间节点，需要继续向下一跳节点转发以太帧的时候，则用户设备在该第二报文的载荷部分补充填充冗余数据，生成第十三报文，使得第十三报文的数据长度大于或等于64字节。可选的，在一种可能的实现方 式中，如果用户面网元在根据N3隧道协议对删除了填充冗余数据的第一报文进行封装，得到第十二报文之前，用户面网元还删除了第一报文中的前导码字段、SFD字段以及FCS字段，则用户设备还要补充其它字段生成第十三报文，如FCS字段，前导码字段和SFD字段，具体此处不做限定。其中，第十三报文的格式可以与第一报文的格式相同，也就是说，若第一报文为图8所示的以太网Ethernet II帧格式，则第十三报文也为以太网Ethernet II类型的以太帧，若第一报文格式为图9所示的IEEE 802.3帧格式，则第十三报文也为IEEE802.3类型的以太帧。优选的，在补充完填充冗余数据之后，该第十三报文的数据长度和第一报文的数据长度相同。其中，第一报文或第十三报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第十三报文与第一报文相同。
具体的，用户设备可以将第十三报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，用户设备可以根据第一指示信息在第十二报文的载荷部分补充填充冗余数据，生成第十三报文，使得该第十三报文的数据长度大于或等于64字节。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户设备根据填充冗余数据的长度信息，将填充冗余数据填充至第十二报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户设备根据填充冗余数据的位置信息，从第十二报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户设备根据有效载荷数据的长度信息，将填充冗余数据填充至第十二报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户设备根据有效载荷数据的位置信息，从第十二报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，用户设备根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第十二报文填充填充冗余数据。
在步骤410中，用户设备接收第七报文，该第七报文为上行以太报文。
在步骤411中，用户设备删除第七报文中的填充冗余数据。
在步骤412中，用户设备生成第八报文，并向无线网络设备发送第八报文。
步骤410至步骤412与前述图2所示实施例中步骤210至步骤212中所执行的方法类似，具体此处不再赘述。
在步骤413中，无线接入网络设备增加第八报文的填充冗余数据。
无线接入网络设备在接收到用户设备发送的第八报文之后，无线接入网络设备将第八报文中的空口协议头剥除，并在第八报文中增加填充冗余数据，并添加N3隧道协议头，生成第九报文，使得第九报文的数据长度大于或等于64字节。示例性的，若第七报文格式为 图8所示的以太网Ethernet II帧格式，第九报文的格式如图10所示，其中，第九报文的目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段均与第八报文中的相应的字段相同；而N3隧道协议头字段包括图10中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图10中的FSC字段与第七报文不同，图10中的FCS字段是无线接入网设备根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图10中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、类型字段以及有效载荷字段。
若第七报文格式为图9所示的IEEE 802.3帧格式时，第九报文的格式为图11所示，其中，第九报文的目的MAC地址字段、源MAC地址字段、Length字段、LLC字段以及有效载荷字段均与第八报文中的相应的字段相同；而N3隧道协议头字段包括图11中的N3 MAC头字段、IP头字段、UDP头字段以及GTP-U头字段。其中N3 MAC头字段是指报文在接入网节点和用户面网元之间的层二传输网络中传输所使用的MAC层的协议头字段。图11中的FSC字段与第七报文不同，图11中的FCS字段是无线接入网设备根据N3 MAC帧的有效长度计算的，其中N3 MAC帧的有效长度包括图11中的N3 MAC头字段、IP头字段、UDP头字段、GTP-U头字段、目的MAC地址字段、源MAC地址字段、长度字段以及有效载荷字段。
具体的，无线接入网络设备根据N3隧道协议对第八报文进行封装，得到第九报文。具体的，在一种可能的实现方式中，这里的N3隧道协议可以是GTP-U协议，可以理解的是，在实际应用过程中，还可以是其他N3隧道协议，具体此处不做限定。
需要说明的是，N3隧道协议是指用户面网元与接入网节点之间的隧道协议，本发明中N3隧道协议可以被其他可能用于用户面网元与接入网节点之间的传输数据的隧道协议替代。
其中第九报文的格式与第七报文相同，也就是说，若第七报文为图8所示的以太网Ethernet II帧格式，则第九报文也为以太网Ethernet II类型的以太帧，若第七报文格式为图9所示的IEEE 802.3帧格式，则第九报文也为IEEE 802.3类型的以太帧。其中，第七报文或第九报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。
具体的，无线接入网络设备可以将第九报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，无线接入网络可以根据第一指示信息在该第八报文的载荷部分补充填充冗余数据，生成第九报文，使得该第九报文的数据长度大于或等于64字节。具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则无线接入网络根据填充冗余数据的长度信息，将填充冗余数据填充至第八报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，无线接入网络根据填充冗余数据的位置信息，从第八报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，无线接入网络根据有效 载荷数据的长度信息，将填充冗余数据填充至第八报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，无线接入网络根据有效载荷数据的位置信息，从第八报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，无线接入网络根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第八报文填充填充冗余数据。
在步骤414中，无线接入网络设备向用户面网元发送第九报文。
无线接入网络设备在生成第九报文之后，向用户面网元发送第九报文。
用户面网元在接收到第九报文之后，可以将该第九报文中的N3隧道协议头剥除，生成第十四报文，并发送给下一跳节点。
可选的，如果用户设备除了删除了第七报文中的填充冗余数据外，还删除了第七报文中的前导码字段、SFD字段以及FCS字段，则用户面网元还补充其它字段生成第十四报文。
需要说明的是，其中第十四报文的格式与第七报文相同，也就是说，若第七报文为图8所示的以太网Ethernet II帧格式，则第十四报文也为以太网Ethernet II类型的以太帧，若第七报文格式为图9所示的IEEE 802.3帧格式，则第十四报文也为IEEE 802.3类型的以太帧。其中，第七报文或第十四报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第十四报文与第七报文相同。
本实施例中，步骤406至步骤409为发送下行报文的应用场景，步骤410至步骤414为发送上行报文的应用场景。在实际应用过程中，步骤406至步骤409可以单独实施，步骤410至步骤414也可以单独实施，还可以合并实施，具体此处不做限定。
本申请实施例中，用户面设备通过将接收到的下行以太报文中的填充冗余数据删除使得在空口传输给用户设备的下行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例中，用户设备通过将接收到的上行以太报文中的填充冗余数据删除，使得在空口传输给无线接入网设备的上行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
请参阅图5，为本申请实施例提供的数据传输方法另一流程示意图。
在步骤501中，用户设备建立PDU会话。
用户设备UE建立PDU会话，该PDU会话用于通过控制面传输(蜂窝物联网Cellular Internet of Thinns，CIoT)小包，即通过(Non-Access-Stratum，NAS)消息来传输CIoT小包。
需要说明的是，本实施例可以应用于5G系统和工业网络互通的场景，还可以应用于其它网络场景，具体此处不做限定。对于5G系统和工业网络互通的场景，该应用服务器可以是工业网络中的产线控制器或者其他工业节点。
在步骤502中，应用功能网元向策略控制网元发送AF请求消息。
本实施例中，步骤502与前述图2所示实施例中步骤202中所执行的方法类似，具体 此处不再赘述。
在步骤503中，策略控制网元向会话管理网元发送策略更新消息。
策略控制网元在接收到会话管理网元发送的AF请求消息之后，策略控制网元获取AF请求消息中的第一指示信息和业务数据流SDF模板，根据该第二指示信息生成第一指示信息，并将该第一指示信息和SDF模板携带在策略更新消息中，发送给会话管理网元。其中，SDF模板包括策略控制网元在步骤502中收到的应用标识或者业务过滤信息，或者在步骤502中收到的DN对应的一个或多个应用的应用标识或者业务过滤信息。其中，第一指示信息用于删除或者增加该SDF模板描述的业务的报文的填充冗余数据。
具体的，在一种可能的实现方式中，该策略更新消息中包括PCC规则，该PCC规则进一步包括了第一指示信息和SDF模板。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示第一填充冗余数据填充冗余数据的长度信息。具体的，该第一填充冗余数据填充冗余数据的长度信息可以是报文载荷(payload)字段中的填充冗余数据(padding)的长度。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示第一填充冗余数据填充冗余数据的位置信息。具体的，该第一填充冗余数据填充冗余数据的位置信息可以是报文的载荷字段中的填充冗余数据的起始位置和结束位置。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示报文的有效载荷数据的长度信息。具体的，该报文的有效载荷数据的长度信息可以是报文载荷字段中的有效载荷数据的长度。
具体的，在一种可能的实现方式中，该第一指示信息还可以指示报文的有效载荷数据的位置信息。具体的，该报文的有效载荷数据的位置信息可以是报文的载荷字段中有效载荷数据的起始位置和结束位置。
需要说明的是，在实际应用过程中，第一指示信息可以包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个，当第一指示信息包含了上述信息中的一个或者多个时，则接收到该第一指示信息的设备可以根据该第一指示信息对填充冗余数据进行增加或者删除。或者，在一种可能的实现方式中，该第一指示信息还可以包含要增加或者删除填充冗余数据的指示，用于指示接收到该第一指示信息的设备在接收到业务报文时根据第一指示信息对填充冗余数据进行增加或者删除。或者，在一种可能的实现方式中，该第一指示信息只包含要增加或者删除填充冗余数据的指示，则接受到该第一指示信息的设备在接收到业务报文时根据该第一指示信息，增加或者删除填充冗余数据。
当会话管理网元接收到策略更新消息之后，会话管理网元根据策略更新消息执行会话管理进行处理。
具体的，会话管理网元将从策略更新消息中获取的PCC规则与PDU会话标识绑定。其中，PCC规则中包括第一指示信息和SDF模板，将PCC规则与PDU会话标识绑定可以理解为将PCC规则应用到该PDU会话中，即PCC规则中的SDF模板对应的一个或多个业务流都绑定到该PDU会话中，且第一指示信息中包括的填充冗余数据长度信息相同。
在步骤504中，会话管理网元向用户设备发送N1接口会话管理消息。
会话管理网元获取策略更新消息中的第一指示信息和SDF模板，SMF通过N1接口会话管理信息将SDF对应的PDU会话标识以及第一指示信息发送给用户设备，具体的，N1接口会话管理消息携带PDU会话修改命令，也就是说，N1接口会话管理消息中包括PDU会话修改命令，PDU会话修改命令中包括PDU会话标识以及第一指示信息。需要说明的是，这里的N1接口会话管理消息是SMF通过AMF发送给无线接入网络设备的，再通过无线接入网设备发送给用户设备的。
需要说明的是，本实施例中，也可以通过无线接入网络设备RAN向用户设备发送PDU会话标识和第一指示信息，即和上述图3所示实施例中步骤306中所执行的方法类似，具体此处不再赘述。
在步骤505中，用户面网元接收第一报文。
第一报文为以太报文，当下行数据传输时，用户面网元会接收到下行的一个或者多个第一报文，该一个或者多个第一报文对应一个PDU会话标识。
具体的，在一种可能的实现方式中，该第一报文为以太网Ethernet II帧格式。具体的，如图8所示，该第一报文中包含了前导码字段，起始帧分隔符字段(Start Frame Delimiter，SFD)字段，目的MAC地址字段，源MAC地址字段，类型字段，数据载荷字段，帧校验序列(Frame Check Sequence，FCS)字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
具体的，在一种可能的实现方式中，该第一报文为以太网IEEE 802.3帧格式。具体的，如图9所示，该第一报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，长度字段，逻辑链路控制(Logic Link Control，LLC)字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
在步骤506中，用户面网元向会话管理网元发送第一报文。
用户面网元UPF在接收到第一报文之后，将该第一报文转发给会话管理网元，即向会话管理网元发送该第一报文。
在步骤507中，会话管理网元删除填充冗余数据。
会话管理网元在接收到第一报文之后，会话管理网元删除第一报文中的填充冗余数据。
具体的，当第一报文为以太网Ethernet II帧格式时，会话管理网元SMF根据第一指示信息删除第一报文中的填充冗余数据。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则会话管理网元根据填充冗余数据的长度信息，将第一报文中载荷部分的填充冗余数据删除。示例性的，会话管理网元SMF根据图8或图9中的帧格式，可以确定填充冗余数据的结束位置，再根据第一指示信息中包含的填充冗余数据的长度，可以确定填充冗余数据的起始位置，进而可以根据该起始位置和结束位置，删除填充冗余数据。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，会话管理网元SMF根据填充冗余数据的位置信息，从第一报文的载荷部分找到填充冗余数据的起始位置和结束位置，将起始位置开始到结束位置的数据删除。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，会话管理网元根据有效 载荷数据的长度信息，将第一报文的载荷部分中除了有效载荷数据之外的数据删除，即删除填充冗余数据。示例性的，会话管理网元SMF根据图8或图9中的帧格式，可以确定填充冗余数据的结束位置，再根据第一指示信息中包含的填充冗余数据的长度，可以确定填充冗余数据的起始位置，进而可以根据该起始位置和结束位置，删除填充冗余数据。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，会话管理网元根据有效载荷数据的位置信息，从第一报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将有效载荷数据起始位置到结束位置之外的数据删除，即删除填充冗余数据。
具体的，当第一报文为以太网IEEE802.3帧格式时，会话管理网元可以根据第一指示信息确定填充冗余数据的在第一报文中的位置，还可以根据如图9所示的长度(Length)字段确定填充冗余数据在第一报文中的位置，进而根据填充冗余数据在第一报文中的位置，删除第一报文中的填充冗余数据。具体的，根据Length字段将第一报文的载荷部分中除了Length字段对应的有效载荷数据之外的数据删除，即删除填充冗余数据。
需要说明的是，在实际应用过程中，第一指示信息可以只包含填充冗余数据的长度信息、填充冗余数据的位置信息、有效载荷数据的长度信息或者有效载荷数据的位置信息中的一个或者多个，当第一指示信息包含了上述信息中的一个或者多个时，则用户面网元可以根据该第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息还可以包含要删除填充冗余数据的指示，用于指示会话管理网元根据第一指示信息对填充冗余数据进行删除。或者，在一种可能的实现方式中，该第一指示信息只包含要删除填充冗余数据的指示，则会话管理网元根据该第一指示信息，删除填充冗余数据。
可选的，会话管理网元处理删除填充冗余数据外，还删除第一报文中的前导码字段、SFD字段以及FCS字段。即第一报文中的前导码字段、SFD字段以及FCS字段不在用户会话管理网元以及用户设备之间传输。
在步骤508中，会话管理网元向接入和移动管理网元发送N1与N2的组合消息。
会话管理网元在删除了第一报文的填充冗余数据之后，会话管理网元生成第二报文，并通过NAS消息向移动管理网元AMF发送第二报文，该第二报文中的载荷数据为第一报文中删除了填充冗余数据之后的有效载荷数据。
具体的，在一种可能的实现方式中，会话管理网元通过N1与N2的组合消息(Namf_Communication_N1N2MessageTransfer service operation)向AMF发送第二报文和PDU会话标识。
在步骤509中，移动管理网元向无线接入网络设备发送下行NAS传输消息。
移动管理网元在接收到第二报文和PDU会话标识之后，移动管理网元向无线接入网络设备发送下行NAS传输消息。
具体的，移动管理网元生成一个下行NAS传输消息，并在该下行NAS传输消息中携带第二报文和PDU会话标识，向无线接入网络设备发送该下行NAS传输消息。
在步骤510中，无线接入网络设备向用户设备发送RRC消息。
无线接入网络设备在接收到下行NAS传输消息之后，通过RRC消息将该下行NAS消息发送给UE。
具体的，在一种可能的实现方式中，RAN通过RRC DL消息将该下行NAS消息发送给UE。
在一种可能的实现方式中，当用户设备接收到第二报文后，用户设备应用层可以直接获取该第二报文的载荷数据部分进行使用。
或者，在一种可能的实现方式中，当用户设备是网络的中间节点，需要继续向下一跳节点转发以太帧的时候，则用户设备在该第二报文的载荷部分补充填充冗余数据，生成第六报文，使得第六报文的数据长度大于或等于64字节。可选的，在一种可能的实现方式中，如果会话管理网元还删除了第一报文中的前导码字段、SFD字段以及FCS字段，则用户设备还要补充其它字段生成第六报文，如FCS字段，前导码字段和SFD字段，具体此处不做限定。其中，第六报文的格式与第一报文的格式相同，也就是说，若第一报文为图8所示的以太网Ethernet II帧格式，则第六报文也为以太网Ethernet II类型的以太帧，若第一报文格式为图9所示的IEEE 802.3帧格式，则第六报文也为IEEE 802.3类型的以太帧。优选的，在补充完填充冗余数据之后，该第六报文的数据长度和第一报文的数据长度相同。其中，第一报文或第六报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第六报文与第一报文相同。
具体的，用户设备可以将第六报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，用户设备可以根据第一指示信息在第二报文的载荷部分补充填充冗余数据，生成第六报文，使得该第六报文的数据长度大于或等于64字节。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户设备根据填充冗余数据的长度信息，将填充冗余数据填充至第二报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户设备根据填充冗余数据的位置信息，从第五报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户设备根据有效载荷数据的长度信息，将填充冗余数据填充至第二报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户设备根据有效载荷数据的位置信息，从第五报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，用户设备根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第二报文填充填充冗余数据。
在步骤511中，用户设备接收第七报文，该第七报文为上行以太报文。
第七报文为以太报文，当上行数据传输时，用户设备会获取上行的一个或者多个上行以太报文，其中，上行以太报文即第七报文。当用户设备有上一跳节点时，用户设备接收上一跳节点发送的上行以太报文。当用户设备没有上一跳节点时，用户设备生成上行以太报文。
具体的，在一种可能的实现方式中，该上行以太报文为以太网Ethernet II帧格式。具体的，如图8所示，该上行以太报文中包含了前导码字段，SFD字段，目的MAC地址字 段，源MAC地址字段，类型字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
具体的，在一种可能的实现方式中，该上行以太报文为以太网IEEE802.3帧格式。具体的，如图9所示，该上行以太报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，净荷长度字段，LLC字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
在步骤512中，用户设备删除填充冗余数据。
用户设备在获取到第七报文之后，用户设备删除第七报文中的填充冗余数据。
具体的，当第七报文为以太网Ethernet II帧格式时，用户设备根据第一指示信息删除第七报文中的填充冗余数据。
具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则用户设备根据填充冗余数据的长度信息，将第七报文中载荷部分的填充冗余数据删除。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，用户设备根据填充冗余数据的位置信息，从第七报文的载荷部分找到填充冗余数据的起始位置和结束位置，将起始位置开始到结束位置的数据删除。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，用户设备根据有效载荷数据的长度信息，将上行以太报文的载荷部分中除了有效载荷数据之外的数据删除，即删除填充冗余数据。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，用户设备根据有效载荷数据的位置信息，从第七报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将有效载荷数据起始位置到结束位置之外的数据删除，即删除填充冗余数据。
具体的，当第七报文为以太网IEEE802.3帧格式时，用户设备元可以根据第一指示信息确定填充冗余数据在第七报文中的位置，还可以根据长度(Length)字段确定填充冗余数据在第七报文中的位置，根据填充冗余数据在第七报文中的位置，删除第七报文中的填充冗余数据。具体的，根据Length字段将第七报文的载荷部分中除了Length字段对应的有效载荷数据之外的数据删除，即删除第七报文的填充冗余数据。
可选的，用户设备除了删除第七报文中的填充冗余数据外，还删除第七报文中的前导码字段、SFD字段以及FCS字段。即第七报文中的前导码字段、SFD字段以及FCS字段不在用户设备以及会话管理网元之间传输。
在步骤513中，用户设备向无线接入网络设备发送RRC消息。
用户设备在删除了第七报文的填充冗余数据之后，生成第八报文，该第八报文中的载荷数据为第七报文中删除了填充冗余数据之后的有效载荷数据，并将该第八报文通过RRC消息发送给无线接入网络设备RAN。
具体的，用户设备将该第八报文以及对应的PDU会话标识封装在上行NAS消息中，并将该上行NAS消息携带在RRC消息中发送给RAN。
在步骤514中，无线接入网络设备向接入和移动管理网元AMF发送上行NAS消息。
无线接入网络设备RAN在接收到用户设备发送的上行NAS消息之后，无线接入网络设备将该上行NAS消息转发给接入和移动管理网元AMF。
在步骤515中，接入和移动管理网元AMF向会话管理网元发送N1与N2的组合消息。
接入和移动管理网元AMF在接收到RAN发送的上行NAS消息之后，将该NAS消息携带在N1与N2的组合消息(Namf_Communication_N1N2MessageTransfer service operation)中，向会话管理网元发送。
在步骤516中，会话管理网元增加填充冗余数据。
会话管理网元在接收到NAS消息中携带的第八报文之后，会话管理网元增加填充冗余数据，生成第九报文，使得第九报文的数据长度大于或等于64字节，可选的，如果用户设备除了删除了第七报文中的填充冗余数据外，还删除了第七报文中的前导码字段、SFD字段以及FCS字段，则会话管理网元还补充其它字段生成第九报文，如FCS字段，前导码字段和SFD字段，具体此处不做限定。其中第九报文的格式与第七报文相同，也就是说，若第七报文为图8所示的以太网Ethernet II帧格式，则第第九报文也为以太网Ethernet II类型的以太帧，若第七报文格式为图9所示的IEEE 802.3帧格式，则第九报文也为IEEE802.3类型的以太帧。优选的，在补充完填充冗余数据之后，该第九报文的数据长度和第七报文的数据长度相同。其中，第七报文或第九报文的数据长度为图8或图9中除去前导码字段、SFD字段以及帧校验序列字段以外的其它字段长度之和。可选的，第九报文与第七报文相同。
具体的，会话管理网元可以将第九报文中的填充冗余数据的各个位数填为0。可以理解的是，还可以通过其他方式进行填充，只要填充之后的报文的数据长度大于或等于64字节即可，具体此处不做限定。
具体的，在一种可能的实现方式中，会话管理网元可以根据第一指示信息在该第八报文的载荷部分补充填充冗余数据，生成第九报文，使得该第九报文的数据长度大于或等于64字节。具体的，当第一指示信息中包含了填充冗余数据的长度信息时，则会话管理网元根据填充冗余数据的长度信息，将填充冗余数据填充至第八报文中的载荷部分。
或者，当第一指示信息中包含了填充冗余数据的位置信息时，会话管理网元根据填充冗余数据的位置信息，从第八报文的载荷部分找到准备填充的填充冗余数据的起始位置和结束位置，将填充冗余数据填充到对应的位置。
或者，当第一指示信息中包含了有效载荷数据的长度信息时，会话管理网元根据有效载荷数据的长度信息，将填充冗余数据填充至第八报文的载荷部分中。
或者，当第一指示信息中包含了有效载荷数据的位置信息时，会话管理网元根据有效载荷数据的位置信息，从第八报文的载荷部分找出有效载荷数据的起始位置和结束位置，并将填充冗余数据填充至效载荷数据结束位置之后FCS字段之前的位置。
在一种可选的方式中，当第一指示信息只包含要增加填充冗余数据的指示时，会话管理网元根据第一指示信息确定要增加填充冗余数据，并根据协议规定的以太网最小帧长，对第八报文进行填充填充冗余数据
在步骤517中，会话管理网元发送第九报文。
会话管理网元向下一跳节点发送该第九报文。
本实施例中，步骤505至步骤510为发送下行报文的应用场景，步骤511至步骤517为发送上行报文的应用场景。在实际应用过程中，步骤505至步骤510可以单独实施，步 骤511至步骤517也可以单独实施，还可以合并实施，具体此处不做限定。
本申请实施例中，用户面设备通过将接收到的下行报文中的填充冗余数据删除使得在空口传输给用户设备的下行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例中，用户设备通过将接收到的上行报文中的填充冗余数据删除，使得在空口传输给无线接入网设备的上行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
请参阅图6，为本申请实施例提供的数据传输方法另一流程示意图。
在步骤601中，用户设备建立PDU会话。
在步骤602中，应用功能网元向策略控制网元发送AF请求消息。
在步骤603中，策略控制网元向会话管理网元发送策略更新消息。
在步骤604中，会话管理网元向用户设备发送PDU会话修改命令。
本实施例中，步骤601至步骤604与前述图5实施例中步骤501至504所执行的方法类似，具体此处不再赘述。
在步骤605中，网络能力开放功能网元接收第一报文。
第一报文为以太报文，当下行数据传输时，NEF会接收到下行的一个或者多个第一报文，该一个或者多个第一报文对应一个PDU会话标识。
具体的，在一种可能的实现方式中，该第一报文为以太网Ethernet II帧格式。具体的，如图8所示，该第一报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，类型字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
具体的，在一种可能的实现方式中，该第一报文为以太网IEEE 802.3帧格式。具体的，如图9所示，该第一报文中包含了前导码字段，SFD字段，目的MAC地址字段，源MAC地址字段，长度字段，LLC字段，数据载荷字段，FCS字段。其中，数据载荷字段包括有效载荷字段，还包括填充字段。
在步骤606中，NEF向会话管理网元发送第一报文。
NEF在接收到第一报文之后，将该第一报文转发给会话管理网元，即向会话管理网元发送该第一报文。
具体的，在一种可能的实现方式中，NEF通过Nsmf_NIDD_Delivery请求消息将第一报文转发给SMF。
在步骤607中，会话管理网元删除填充冗余数据。
在步骤608中，会话管理网元向接入和移动管理网元AMF发送N1与N2的组合消息。
在步骤609中，移动管理网元AMF向无线接入网络设备发送下行NAS传输消息。
在步骤610中，无线接入网络设备向用户设备发送RRC消息。
在步骤611中，用户设备接收第七报文，该第七报文为上行以太报文。
在步骤612中，用户设备删除填充冗余数据。
在步骤613中，用户设备向无线接入网络设备发送RRC消息。
在步骤614中，无线接入网络设备向接入和移动管理网元发送上行NAS消息。
在步骤615中，接入和移动管理网元向会话管理网元发送N1与N2的组合消息。
在步骤616中，会话管理网元增加填充冗余数据。
本实施例中，步骤607至步骤616与前述图5实施例中步骤507至516所执行的方法类似，具体此处不再赘述。
在步骤617中，会话管理网元发送第九报文。
会话管理网元在增加了填充冗余数据得到第九报文之后，将该第九报文通过Nnef_SMContext_Delivery请求消息向NEF发送。
具体的，NEF在接收到该第九报文之后，将该第九报文发送给下一跳节点。
本实施例中，步骤605至步骤610为发送下行报文的应用场景，步骤611至步骤617为发送上行报文的应用场景。在实际应用过程中，步骤605至步骤610可以单独实施，步骤611至步骤617也可以单独实施，还可以合并实施，具体此处不做限定。
本申请实施例中，用户面设备通过将接收到的下行报文中的填充冗余数据删除使得在空口传输给用户设备的下行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
本申请实施例中，用户设备通过将接收到的上行报文中的填充冗余数据删除，使得在空口传输给无线接入网设备的上行报文不包括填充冗余数据，即不需要传输填充冗余数据，节省了空口资源，提高了空口容量。
上面对本申请实施例中的数据传输方法进行了说明，下面对本申请实施例中提供的设备进行说明。
请参阅图13，为本申请实施例提供的设备的一个结构示意图。
一种设备，包括：
接收单元1301，用于接收第一报文，第一报文中的载荷数据包括填充冗余数据；
删除单元1302，用于删除填充冗余数据；
生成单元1303，用于生成第二报文，第二报文中的载荷数据为第一报文中删除填充冗余数据后的有效载荷数据；
发送单元1304，用于向第二设备发送第二报文。
本实施例中设备各单元所执行的方法与前述图2至图6中各个网络设备或者用户设备所执行的方法类似，具体此处不再赘述。
请参阅图13，为本申请实施例提供的设备的另一结构示意图。
一种设备，包括：
接收单元1301，用于接收第一报文，第一报文中的载荷数据包括填充冗余数据；
删除单元1302，用于删除填充冗余数据；
生成单元1303，用于生成第二报文，第二报文中的载荷数据为第一报文中删除填充冗余数据后的有效载荷数据；
发送单元1304，用于向第二设备发送第二报文。
可选地，接收单元1301还用于接收第一指示信息；
删除单元1302具体用于根据第一指示信息删除填充冗余数据。
可选地，第一指示信息用于指示设备删除填充冗余数据，或，第一指示信息包括填充 冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一下行报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
可选地，删除单元1302具体用于根据第一报文的长度字段删除填充冗余数据。
可选地，设备为UPF，第二设备为RAN，第一报文为下行以太报文。
可选地，生成单元1303具体用于根据N3隧道协议对第三报文进行封装得到第四报文，其中，第三报文为第一报文删除填充冗余数据后的报文；若第四报文的数据长度小于以太网最小帧长，则在第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长；或者，
若设备确定第一设备根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则生成单元1303具体用于根据N3隧道协议对第三报文进行封装得封装报文，并在封装报文的N3隧道协议头中增加隧道协议填充冗余数据得到第二报文，第二报文的数据长度大于或者等于以太网最小帧长，其中，第三报文为第一报文删除填充冗余数据后的报文。
可选地，设备为RAN，第二设备为UE，第一报文为下行报文。
可选地，设备为UE，第二设备为RAN，第一报文为上行以太报文。
可选地，设备为SMF，第二设备为UE，第一报文为下行以太报文。
可选地，设备为UE，第二设备为SMF，第一报文为上行以太报文。
本实施例中设备各单元所执行的方法与前述图2至图6中各个网络设备或者用户设备所执行的方法类似，具体此处不再赘述。
请参阅图14，为本申请实施例提供的设备的一个结构示意图。
一种设备，包括：
发送单元1401，用于向第四设备发送第一指示信息，其中，第一指示信息用于删除第一报文的填充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
本实施例中设备各单元所执行的方法与前述图2至图6中各个网络设备所执行的方法类似，具体此处不再赘述。
请参阅图15，为本申请实施例提供的设备的另一结构示意图。
一种设备，包括：
发送单元1501，用于向第四设备发送第一指示信息，其中，第一指示信息用于删除第一报文的填充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，第一指示信息包括填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第一指示信息包括第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息。
可选地，当第一指示信息用于删除第一报文的填充冗余数据时，
设备为PCF，第四设备为SMF，第一报文为以太报文；或者，
设备为SMF，第四设备为UPF，第一报文为以太报文；或者，
设备为SMF，第四设备为UE，第一报文为以太报文；或者，
设备为SMF，第四设备为RAN；或者，
设备为RAN，第四设备为UE。
可选地，当第一指示信息用于在第一报文增加填充冗余数据时，
设备为SMF，第四设备为UPF，第一报文为以太报文；或者，
设备为SMF，第四设备为UE，第一报文为以太报文；或者，
设备为SMF，第四设备为RAN。
可选地，设备为策略控制网元PCF，第四设备为会话管理网元SMF，第五设备为应用功能网元AF，设备还包括：
接收单元1502，用于接收第五设备的第二指示信息，第二指示信息用于指示填充冗余数据的长度信息，或，填充冗余数据的位置信息，或，第二指示信息用于指示第一报文的有效载荷数据的长度信息，或，第一报文的有效载荷数据的位置信息；
确定单元1503，用于根据第二指示信息确定第一指示信息。
本实施例中设备各单元所执行的方法与前述图2至图6中各个网络设备所执行的方法类似，具体此处不再赘述。
请参阅图16，为本申请实施例提供的设备一个结构示意图。
处理器1601、存储器1602、总线1605、接口1604，处理器1601与存储器1602、接口1604相连，总线1605分别连接处理器1601、存储器1602以及接口1604，接口1604用于接收或者发送数据，处理器1601是单核或多核中央处理单元，或者为特定集成电路，或者为被配置成实施本发明实施例的一个或多个集成电路。存储器1602可以为随机存取存储器(random access memory，RAM)，也可以为非易失性存储器(non-volatile memory)，例如至少一个硬盘存储器。存储器1602用于存储计算机执行指令。具体的，计算机执行指令中可以包括程序1603。
本实施例中，该处理器1601调用程序1603时，可以使图16中的设备执行前述图2至图6所示实施例中各个网络设备所执行的操作，具体此处不再赘述。
请参阅图17，为本申请实施例提供的设备一个结构示意图。
处理器1701、存储器1702、总线1705、接口1704，处理器1701与存储器1702、接口1704相连，总线1705分别连接处理器1701、存储器1702以及接口1704，接口1704用于接收或者发送数据，处理器1701是单核或多核中央处理单元，或者为特定集成电路，或者为被配置成实施本发明实施例的一个或多个集成电路。存储器1702可以为随机存取存储器(random access memory，RAM)，也可以为非易失性存储器(non-volatile memory)，例如至少一个硬盘存储器。存储器1702用于存储计算机执行指令。具体的，计算机执行指令中可以包括程序1703。
本实施例中，该处理器1701调用程序1703时，可以使图17中的设备执行前述图2至图6所示实施例中用户设备所执行的操作，具体此处不再赘述。
应理解，本申请以上实施例中的网络设备或者用户设备中提及的处理器，或者本申请上述实施例提供的处理器，可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application-specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、 分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请中以上实施例中的网络设备或者用户设备中的处理器的数量可以是一个，也可以是多个，可以根据实际应用场景调整，此处仅仅是示例性说明，并不作限定。本申请实施例中的存储器的数量可以是一个，也可以是多个，可以根据实际应用场景调整，此处仅仅是示例性说明，并不作限定。
还需要说明的是，当网络设备或者用户设备包括处理器(或处理单元)与存储器时，本申请中的处理器可以是与存储器集成在一起的，也可以是处理器与存储器通过接口连接，可以根据实际应用场景调整，并不作限定。
本申请实施例还提供了一种计算机程序或包括计算机程序的一种计算机程序产品，该计算机程序在某一计算机上执行时，将会使所述计算机实现上述任一方法实施例中与网络设备或者用户设备相关的方法流程。
本申请实施例还提供了一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述任一方法实施例中与网络设备或者用户设备相关的方法流程。
在上述图2-图6中各个实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。
所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
本申请各实施例中提供的消息/帧/信息、模块或单元等的名称仅为示例，可以使用其他名称，只要消息/帧/信息、模块或单元等的作用相同即可。
在本申请实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本发明。在本申请实施例中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的 “和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。
取决于语境，如在此所使用的词语“如果”或“若”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。类似地，取决于语境，短语“如果确定”或“如果检测(陈述的条件或事件)”可以被解释成为“当确定时”或“响应于确定”或“当检测(陈述的条件或事件)时”或“响应于检测(陈述的条件或事件)”。
以上所述，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (29)

  1. 一种数据传输方法，其特征在于，包括：
    第一设备接收第一报文，所述第一报文中的载荷数据包括填充冗余数据；
    所述第一设备删除所述填充冗余数据；
    所述第一设备生成第二报文，所述第二报文中的载荷数据为所述第一报文中删除所述填充冗余数据后的有效载荷数据；
    所述第一设备向第二设备发送所述第二报文。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一设备接收第一指示信息；
    所述第一设备删除所述填充冗余数据包括：
    所述第一设备根据所述第一指示信息删除所述填充冗余数据。
  3. 根据权利要求2所述的方法，其特征在于，所述第一指示信息用于指示所述第一网络设备删除所述填充冗余数据，或，所述第一指示信息包括所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第一指示信息包括所述第一下行报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一设备删除所述填充冗余数据包括：
    所述第一设备根据所述第一报文的长度字段删除所述填充冗余数据。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备为用户面网元UPF，所述第二设备为无线接入网设备RAN，所述第一报文为下行以太报文。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一设备生成第二报文包括：
    所述第一设备根据N3隧道协议对第三报文进行封装得到第四报文，其中，所述第三报文为第一报文删除所述填充冗余数据后的报文；若所述第四报文的数据长度小于以太网最小帧长，则在所述第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到所述第二报文，所述第二报文的数据长度大于或者等于所述以太网最小帧长；或者，
    若所述第一设备确定所述第一设备根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则所述第一设备根据N3隧道协议对所述第三报文进行封装得封装报文，并在所述封装报文的N3隧道协议头中增加隧道协议填充冗余数据得到所述第二报文，所述第二报文的数据长度大于或者等于所述以太网最小帧长，其中，所述第三报文为第一报文删除所述填充冗余数据后的报文。
  7. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备为无线接入网设备RAN，所述第二设备为用户设备UE，所述第一报文为下行报文。
  8. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备为用户设备UE，所述第二设备为无线接入网设备RAN，所述第一报文为上行以太报文。
  9. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备为会话管理网元SMF，所述第二设备为用户设备UE，所述第一报文为下行以太报文。
  10. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一设备为用户设 备UE，所述第二设备为会话管理网元SMF，所述第一报文为上行以太报文。
  11. 一种数据传输方法，其特征在于，包括：
    第三设备向第四设备发送第一指示信息，其中，所述第一指示信息用于删除第一报文的填充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，所述第一指示信息包括所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第一指示信息包括所述第一报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息。
  12. 根据权利要求11所述的方法，其特征在于，
    当所述第一指示信息用于删除所述第一报文的填充冗余数据时，
    所述第三设备为策略控制网元PCF，所述第四设备为会话管理网元SMF，所述第一报文为以太报文；或者，
    所述第三设备为会话管理网元SMF，所述第四设备为用户面网元UPF，所述第一报文为以太报文；或者，
    所述第三设备为会话管理网元SMF，所述第四设备为用户设备UE，所述第一报文为以太报文；或者，
    所述第三设备为会话管理网元SMF，所述第四设备为无线接入网设备RAN；或者，
    所述第三设备为无线接入网设备RAN，所述第四设备为用户设备UE。
  13. 根据权利要求11所述的方法，其特征在于，
    当所述第一指示信息用于在所述第一报文增加填充冗余数据时，
    所述第三设备为会话管理网元SMF，所述第四设备为用户面网元UPF，所述第一报文为以太报文；或者，
    所述第三设备为会话管理网元SMF，所述第四设备为用户设备UE，所述第一报文为以太报文；或者，
    所述第三设备为会话管理网元SMF，所述第四设备为无线接入网设备RAN；或者，
    所述第三设备为无线接入网设备RAN，所述第四设备为用户设备UE。
  14. 根据权利要求11所述的方法，其特征在于，所述第三设备为策略控制网元PCF，所述第四设备为会话管理网元SMF，所述第五设备为应用功能网元AF；所述第三设备向第四设备发送第一指示信息之前，所述方法还包括：
    所述第三设备接收第五设备的第二指示信息，所述第二指示信息用于指示所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第二指示信息用于指示所述第一报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息；
    所述第三设备根据所述第二指示信息确定所述第一指示信息。
  15. 一种设备，其特征在于，包括：
    接收单元，用于接收第一报文，所述第一报文中的载荷数据包括填充冗余数据；
    删除单元，用于删除所述填充冗余数据；
    生成单元，用于生成第二报文，所述第二报文中的载荷数据为所述第一报文中删除所述填充冗余数据后的有效载荷数据；
    发送单元，用于向第二设备发送所述第二报文。
  16. 根据权利要求15所述的设备，其特征在于，所述接收单元还用于接收第一指示信息；
    所述删除单元具体用于根据所述第一指示信息删除所述填充冗余数据。
  17. 根据权利要求16所述的设备，其特征在于，所述第一指示信息用于指示所述设备删除所述填充冗余数据，或，所述第一指示信息包括所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第一指示信息包括所述第一下行报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息。
  18. 根据权利要求15至17中任一项所述的设备，其特征在于，所述删除单元具体用于根据所述第一报文的长度字段删除所述填充冗余数据。
  19. 根据权利要求15至18中任一项所述的设备，其特征在于，所述设备为用户面网元UPF，所述第二设备为无线接入网设备RAN，所述第一报文为下行以太报文。
  20. 根据权利要求15至18中任一项所述的设备，其特征在于，所述生成单元具体用于根据N3隧道协议对第三报文进行封装得到第四报文，其中，所述第三报文为第一报文删除所述填充冗余数据后的报文；若所述第四报文的数据长度小于以太网最小帧长，则在所述第四报文的N3隧道协议头中增加隧道协议填充冗余数据得到所述第二报文，所述第二报文的数据长度大于或者等于所述以太网最小帧长；或者，
    若所述设备确定所述第一设备根据N3隧道协议对第三报文进行封装得到的封装报文的数据长度小于以太网最小帧长，则所述生成单元具体用于根据N3隧道协议对所述第三报文进行封装得封装报文，并在所述封装报文的N3隧道协议头中增加隧道协议填充冗余数据得到所述第二报文，所述第二报文的数据长度大于或者等于所述以太网最小帧长，其中，所述第三报文为第一报文删除所述填充冗余数据后的报文。
  21. 根据权利要求15至18中任一项所述的设备，其特征在于，所述设备为无线接入网设备RAN，所述第二设备为用户设备UE，所述第一报文为下行报文。
  22. 根据权利要求15至18中任一项所述的设备，其特征在于，所述设备为用户设备UE，所述第二设备为无线接入网设备RAN，所述第一报文为上行以太报文。
  23. 根据权利要求15至18中任一项所述的设备，其特征在于，所述设备为会话管理网元SMF，所述第二设备为用户设备UE，所述第一报文为下行以太报文。
  24. 根据权利要求15至18中任一项所述的设备，其特征在于，所述设备为用户设备UE，所述第二设备为会话管理网元SMF，所述第一报文为上行以太报文。
  25. 一种设备，其特征在于，包括：
    发送单元，用于向第四设备发送第一指示信息，其中，所述第一指示信息用于删除第一报文的填充冗余数据，或，第一指示信息用于在第一报文增加填充冗余数据，所述第一指示信息包括所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第一指示信息包括所述第一报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息。
  26. 根据权利要求25所述的设备，其特征在于，
    当所述第一指示信息用于删除所述第一报文的填充冗余数据时，
    所述设备为策略控制网元PCF，所述第四设备为会话管理网元SMF，所述第一报文为以 太报文；或者，
    所述设备为会话管理网元SMF，所述第四设备为用户面网元UPF，所述第一报文为以太报文；或者，
    所述设备为会话管理网元SMF，所述第四设备为用户设备UE，所述第一报文为以太报文；或者，
    所述设备为会话管理网元SMF，所述第四设备为无线接入网设备RAN；或者，
    所述设备为无线接入网设备RAN，所述第四设备为用户设备UE。
  27. 根据权利要求25所述的设备，其特征在于，
    当所述第一指示信息用于在所述第一报文增加填充冗余数据时，
    所述设备为会话管理网元SMF，所述第四设备为用户面网元UPF，所述第一报文为以太报文；或者，
    所述设备为会话管理网元SMF，所述第四设备为用户设备UE，所述第一报文为以太报文；或者，
    所述设备为会话管理网元SMF，所述第四设备为无线接入网设备RAN。
  28. 根据权利要求25所述的设备，其特征在于，所述设备为策略控制网元PCF，所述第四设备为会话管理网元SMF，第五设备为应用功能网元AF，所述设备还包括：
    接收单元，用于接收第五设备的第二指示信息，所述第二指示信息用于指示所述填充冗余数据的长度信息，或，所述填充冗余数据的位置信息，或，所述第二指示信息用于指示所述第一报文的有效载荷数据的长度信息，或，所述第一报文的有效载荷数据的位置信息；
    确定单元，用于根据所述第二指示信息确定所述第一指示信息。
  29. 一种计算机存储介质，其特征在于，所述计算机存储介质中存储有指令，所述指令在计算机上执行时，使得所述计算机执行如权利要求1至14中任一项所述的方法。
PCT/CN2020/113070 2020-09-02 2020-09-02 一种数据传输方法及其设备 WO2022047675A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2020/113070 WO2022047675A1 (zh) 2020-09-02 2020-09-02 一种数据传输方法及其设备
EP20951922.2A EP4191909A4 (en) 2020-09-02 2020-09-02 DATA TRANSMISSION METHOD AND ASSOCIATED DEVICE
CN202080101252.7A CN115699629A (zh) 2020-09-02 2020-09-02 一种数据传输方法及其设备
US18/177,458 US20230209399A1 (en) 2020-09-02 2023-03-02 Data transmission method and device therefor

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/113070 WO2022047675A1 (zh) 2020-09-02 2020-09-02 一种数据传输方法及其设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/177,458 Continuation US20230209399A1 (en) 2020-09-02 2023-03-02 Data transmission method and device therefor

Publications (1)

Publication Number Publication Date
WO2022047675A1 true WO2022047675A1 (zh) 2022-03-10

Family

ID=80492377

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/113070 WO2022047675A1 (zh) 2020-09-02 2020-09-02 一种数据传输方法及其设备

Country Status (4)

Country Link
US (1) US20230209399A1 (zh)
EP (1) EP4191909A4 (zh)
CN (1) CN115699629A (zh)
WO (1) WO2022047675A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009212686A (ja) * 2008-03-03 2009-09-17 Mitsubishi Electric Corp データ送信装置、データ受信装置及びデータ通信システム
CN108242969A (zh) * 2016-12-23 2018-07-03 华为技术有限公司 一种传输速率的调整方法及网络设备
CN110381071A (zh) * 2019-07-24 2019-10-25 新华三技术有限公司合肥分公司 一种报文传输方法、装置及发送方设备
CN110943917A (zh) * 2019-11-26 2020-03-31 中国电子科技集团公司第五十四研究所 一种减少多路由网络中冗余报文的方法
CN111541521A (zh) * 2020-05-07 2020-08-14 上海道生物联技术有限公司 一种数据包长度识别方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH09181876A (ja) * 1995-12-25 1997-07-11 Ricoh Co Ltd ファクシミリ用アダプタ装置
TWI247510B (en) * 2003-08-18 2006-01-11 Asustek Comp Inc Method to avoid potential deadlocks in a SDU discard function
JP2007135035A (ja) * 2005-11-11 2007-05-31 Nippon Telegr & Teleph Corp <Ntt> 通信装置及びパケット処理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009212686A (ja) * 2008-03-03 2009-09-17 Mitsubishi Electric Corp データ送信装置、データ受信装置及びデータ通信システム
CN108242969A (zh) * 2016-12-23 2018-07-03 华为技术有限公司 一种传输速率的调整方法及网络设备
CN110381071A (zh) * 2019-07-24 2019-10-25 新华三技术有限公司合肥分公司 一种报文传输方法、装置及发送方设备
CN110943917A (zh) * 2019-11-26 2020-03-31 中国电子科技集团公司第五十四研究所 一种减少多路由网络中冗余报文的方法
CN111541521A (zh) * 2020-05-07 2020-08-14 上海道生物联技术有限公司 一种数据包长度识别方法及系统

Also Published As

Publication number Publication date
EP4191909A1 (en) 2023-06-07
EP4191909A4 (en) 2023-08-09
CN115699629A (zh) 2023-02-03
US20230209399A1 (en) 2023-06-29

Similar Documents

Publication Publication Date Title
US11425600B2 (en) Wireless backhaul data transmission method and apparatus
US11510131B2 (en) Configuration method, data transmission method, and apparatus
WO2020199896A1 (zh) 一种业务流路由控制方法、装置及系统
JP7303833B2 (ja) 情報伝送方法及び装置
JP7135100B2 (ja) パケット伝送方法、装置、およびシステム
US11968565B2 (en) User plane information reporting method and apparatus
WO2020103807A1 (zh) 一种通信方法及装置
WO2021208561A1 (zh) 通信方法和装置
EP3735092B1 (en) Transmission methods, transmission apparatus, computer readable storage medium and system
EP4138443A1 (en) Communication method and apparatus
WO2019196788A1 (zh) 通信方法和通信装置
WO2020169039A1 (zh) 一种策略管理的方法及装置
WO2021026939A1 (zh) 以太帧头的压缩、解压方法和装置
WO2021135650A1 (zh) 通信方法及装置
WO2017067007A1 (zh) 服务质量的控制方法、设备及系统
WO2019154160A1 (zh) 一种通信方法及装置
WO2021134723A1 (zh) 通信方法、设备及系统
WO2022047675A1 (zh) 一种数据传输方法及其设备
WO2021008402A1 (zh) 支持端口关联的方法、网关选择的方法及通信设备
EP3869755A1 (en) Control plane network function, user plane network function, and packet processing method using same
US20240121201A1 (en) Communication method and apparatus
WO2022237505A1 (zh) 一种通信方法、设备及系统
WO2023197105A1 (zh) 配置信息的方法、装置和通信系统
WO2023011111A1 (zh) 路由方法和通信装置
WO2024055871A1 (zh) 一种通信系统中传输数据的方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20951922

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020951922

Country of ref document: EP

Effective date: 20230303

NENP Non-entry into the national phase

Ref country code: DE