WO2023217012A1 - 数据传输方法、信息发送方法、终端及网络侧设备 - Google Patents

数据传输方法、信息发送方法、终端及网络侧设备 Download PDF

Info

Publication number
WO2023217012A1
WO2023217012A1 PCT/CN2023/092429 CN2023092429W WO2023217012A1 WO 2023217012 A1 WO2023217012 A1 WO 2023217012A1 CN 2023092429 W CN2023092429 W CN 2023092429W WO 2023217012 A1 WO2023217012 A1 WO 2023217012A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
data packet
terminal
configuration information
negotiation
Prior art date
Application number
PCT/CN2023/092429
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 维沃移动通信有限公司
Publication of WO2023217012A1 publication Critical patent/WO2023217012A1/zh

Links

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
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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
    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • H04L1/0007—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length
    • 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/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a data transmission method, an information sending method, a terminal and a network side device.
  • the terminal When the terminal encapsulates the data packet, it encapsulates the data packet according to the encapsulation rules, and each protocol layer associates the encapsulation header of the protocol layer when encapsulating the data packet.
  • the encapsulation rules in related technologies need to be compatible with the characteristics of encapsulating variable-sized data packets, and the formats of variable-sized data packets may be different. Different data packet formats have different data packet headers, resulting in the data packets being encapsulated according to the predefined encapsulation rules. Encapsulation will generate a large amount of data packet header overhead, resulting in low resource utilization.
  • Embodiments of the present application provide a data transmission method, an information sending method, a terminal and a network side device, which can solve the problem of low resource utilization.
  • the first aspect provides a data transmission method, including:
  • the terminal receives target configuration information sent by the network side device, and the target configuration information is used to configure the data packet format;
  • the terminal transmits service data based on the target configuration information.
  • the second aspect provides a method of sending information, including:
  • the network side device sends target configuration information to the terminal, and the target configuration information is used to configure the data packet format.
  • the third aspect provides a method of sending information, including:
  • the core network device sends first indication information to the access network device, where the first indication information is used to assist the access network device in configuring the data packet format.
  • a data transmission device applied to a terminal, and the data transmission device includes:
  • a receiving module configured to receive target configuration information sent by the network side device, where the target configuration information is used to configure the data packet format
  • a transmission module configured to transmit service data based on the target configuration information.
  • an information sending device which is applied to network side equipment.
  • the information sending device includes:
  • a sending module configured to send target configuration information to the terminal, where the target configuration information is used to configure the data packet format.
  • an information sending device applied to core network equipment, and the information sending device includes:
  • a sending module configured to send first indication information to the access network device, where the first indication information is used to assist the access network device in configuring the data packet format.
  • a terminal in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions When the program or instructions are executed by the processor, the following implementations are implemented: The steps of the method described in one aspect.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to receive target configuration information sent by a network side device, and the target configuration information is used to configure a data packet format; the processing The server is configured to transmit service data based on the target configuration information.
  • a network side device in a ninth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • a network side device including a processor and a communication interface, wherein the communication interface is used to send target configuration information to a terminal, and the target configuration information is used to configure a data packet format.
  • a core network device in an eleventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are used by the processor. When executed, the steps of the method as described in the third aspect are implemented.
  • a data transmission system including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the data transmission method as described in the first aspect.
  • the network side device can be used to perform the steps of the data transmission method as described in the first aspect. The steps of the information sending method described in the second aspect or the third aspect.
  • a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented. The steps of the method as described in the second aspect, or the steps of implementing the method as described in the third aspect.
  • a chip in a fourteenth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the method described in the first aspect. method, or implement the method as described in the second aspect, or implement the method as described in the third aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect
  • the terminal receives target configuration information sent by the network side device, and the target configuration information is used to configure the data packet format; the terminal transmits service data based on the target configuration information.
  • the terminal can configure the data packet format for business data transmission based on the target configuration information sent by the network side device, so that the terminal can use a relatively fixed data packet format when transmitting business data, thereby reducing data packet header overhead and improving resources. Utilization.
  • Figure 1 is a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • Figure 2 is a diagram of an NR UP protocol architecture provided by an embodiment of this application.
  • FIG. 3 is a schematic diagram of an SDAP data packet format provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of another SDAP data packet format provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a PDCP data packet format provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of another PDCP data packet format provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an RLC data packet format provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of another RLC data packet format provided by an embodiment of the present application.
  • Figure 9 is a schematic diagram of a MAC data packet format provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of another MAC data packet format provided by an embodiment of the present application.
  • FIG 11 is a schematic diagram of another MAC data packet format provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of another MAC data packet format provided by the embodiment of the present application.
  • Figure 13 is a schematic diagram of another MAC data packet format provided by the embodiment of the present application.
  • Figure 14 is a schematic diagram of another MAC data packet format provided by the embodiment of the present application.
  • Figure 15 is a flow chart of a data transmission method provided by an embodiment of the present application.
  • Figure 16 is a schematic configuration diagram of a data packet format provided by an embodiment of the present application.
  • Figure 17 is a flow chart of an information sending method provided by an embodiment of the present application.
  • Figure 18 is a flow chart of another information sending method provided by an embodiment of the present application.
  • Figure 19 is a structural diagram of a data transmission device provided by an embodiment of the present application.
  • Figure 20 is a structural diagram of an information sending device provided by an embodiment of the present application.
  • Figure 21 is a structural diagram of another information sending device provided by an embodiment of the present application.
  • Figure 22 is a structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 23 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 24 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • Figure 25 is a schematic structural diagram of a core network device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first,”
  • the objects distinguished by “second” are usually of the same type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/” generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the wireless communication system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer.
  • Tablet Personal Computer Tablet Personal Computer
  • laptop computer laptop computer
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • UMPC ultra-mobile personal computer
  • UMPC mobile Internet device
  • MID mobile Internet Device
  • AR augmented reality
  • VR virtual reality
  • robots wearable devices
  • WUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • smart home home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.
  • game consoles personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices.
  • Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc.
  • the network side device 12 may include an access network device or a core network device, where the access network device may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a wireless access network unit.
  • Access network equipment may include a base station, a Wireless Local Area Network (WLAN) Access Point (AP) or a Wireless Fidelity (Wireless Fidelity, WiFi) node, etc.
  • the base station may be called a Node B (Node B).
  • NB Evolved Node B
  • eNB Evolved Node B
  • BTS Base Transceiver Station
  • BSS Base Transceiver Station
  • BSS Basic Service Set
  • BSS Extension Service set
  • HNB home Node B
  • HNB home evolved Node B
  • TRP Transmitting Receiving Point
  • the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only the base station in the NR system is used as an example for introduction, and the specific name of the base station is not limited. type.
  • Core network equipment may include but is not limited to at least one of the following: Core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User plane function (User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data management (Unified Data Management, UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Storage function (Network Repository) Function (NRF), Network Exposure Function (NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • PCF Policy and Charging Rules Function
  • EASDF Edge Application
  • the NR UP protocol architecture diagram is shown in Figure 2, which consists of Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Link Control (RLC) , Media Access Control (Medium Access Control, MAC) and Physical Layer (Physical Layer, PHY).
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • Media Access Control Medium Access Control
  • MAC Medium Access Control
  • Physical Layer Physical Layer
  • SDAP is mainly responsible for the mapping management of Quality of Service (QoS) flow and Data Radio Bearer (DRB);
  • QoS Quality of Service
  • DRB Data Radio Bearer
  • the SDAP header (header) corresponding to the uplink (UL) and downlink (Downlink, DL) data packets is configurable. If configured, the corresponding SDAP header occupies one byte.
  • the SDAP layer data packet format can be shown in Figure 3 and Figure 4, which is mainly used to carry QoS flow identifier (QoS Flow Identifier, QFI).
  • QFI QoS Flow Identifier
  • PDCP is mainly responsible for header compression and/or decompression, encryption and/or decryption, integrity protection and/or integrity verification, data copy and/or duplication detection, reordering, PDCP retransmission and other processing;
  • PDCP data packets (i.e. PDCP data PDU) carry PDCP headers (headers).
  • PDCP headers mainly carry PDCP sequence numbers (Sequence Number, SN).
  • SN PDCP sequence numbers
  • 12-bit or 18-bit PDCP SN can be used, depending on the network side. configuration, occupying 2 or 3 bytes respectively.
  • the PDCP layer data packet format is shown in Figure 5 and Figure 6.
  • Figure 5 shows the PDCP layer packet format using 12-bit PDCP SN.
  • Figure 6 shows the PDCP layer packet format using 18-bit PDCP SN.
  • Data represents the data area, Optional represents optional, and cont represents content.
  • RLC is mainly responsible for data segmentation and/or reassembly, automatic repeat request (Automatic Repeat request, ARQ) and/or duplicate detection and/or re-segmentation (applicable to confirmation mode) and other functions.
  • RLC has three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM) and Acknowledged Mode (AM). Different transmission modes have different data packet formats. Among them, TM does not need to carry RLC header. It is commonly used for system messages, paging messages and signaling carried by Signaling Radio Bearer 0 (SRB0), and is not used to transmit business data. AM carries RLC header, and RLC header must carry RLC SN. The RLC SN can be a 12-bit or 18-bit RLC SN. UM carries a one-byte RLC header when the data packet it carries is a complete data packet (that is, the data packet is not divided). The RLC header does not need to carry the RLC SN.
  • TM Transparent Mode
  • UM Unacknowledged Mode
  • AM Acknowledged Mode
  • the RLC header needs to carry the RLC SN.
  • the carried RLC The SN can be a 6-bit or 12-bit RLC SN. Since AM and UM support data packet segmentation and/or reassembly functions, the data packet format is relatively complex.
  • the RLC header needs to carry segmentation information, such as SI fields and SO fields, so that the receiving end can reassemble the data packets.
  • Part of the RLC layer data packet format is shown in Figure 7 and Figure 8.
  • Figure 7 shows the UDM PDU data packet format carrying 12-bit RLC SN and SO fields.
  • Figure 8 shows the AMD PDU data packet format carrying 18-bit RLC SN and SO fields.
  • Data represents the data area.
  • the MAC layer is mainly responsible for data multiplexing and/or demultiplexing, Hybrid Automatic Repeat Request (HARQ), resource scheduling and other functions.
  • HARQ Hybrid Automatic Repeat Request
  • the MAC layer can transparently transmit data packets, that is, it does not carry a MAC header, but it is mainly suitable for the transmission of paging messages and system messages. In other cases, the MAC header needs to be carried. Since the MAC layer has data multiplexing and/or demultiplexing functions, each MAC sub (sub) PDU has a corresponding MAC subheader, which is used to carry the logical channel identifier (Logical Channel Identity, LCID). The LCID is used Identify the data source. In addition, it also carries the L field to indicate the length of the MAC subSDU.
  • Figures 9 to 11 show the MAC layer packet format in which the MAC subheader carries the 8-bit L field.
  • Figures 12 to 14 show the MAC layer packet format in which the MAC subheader carries the 16-bit L field.
  • Figure 15 is a flow chart of a data transmission method provided by an embodiment of the present application. As shown in Figure 15, the data transmission method includes the following steps:
  • Step 101 The terminal receives the target configuration information sent by the network side device, and the target configuration information is used to configure the data packet format;
  • Step 102 The terminal transmits service data based on the target configuration information.
  • the target configuration information may be data packet format configuration information.
  • the terminal may send first negotiation information to the network side device, where the first negotiation information is used to negotiate a data packet format, so that the network side device may send target configuration information to the terminal based on the first negotiation information sent by the terminal. ;
  • the terminal can receive the target configuration information actively sent by the network side device, and the network side device can be based on the load status of the network side device, the link status between the network side device and the terminal, and the first indication information.
  • At least One item actively sends target configuration information to the terminal, and the first indication information can be used to assist the network side device in configuring the target configuration information.
  • the target configuration information can be used to configure the data packet format of the target service.
  • the target configuration information can carry the service identification information of the target service.
  • the service identification information can be session identification information, bearer identification information and At least one item in the logical channel identification information; or, the target configuration information can be used to configure the data packet format of all services.
  • the target configuration information may not carry the service identification information, so that the target configuration information configures the data packet format. It can be applied to the data transmission of any business of the terminal.
  • the target configuration information can be used to configure the data packet format of each protocol layer of the NR protocol stack.
  • the target configuration information can be used to configure the SDAP layer, PDCP layer, RLC layer and MAC layer.
  • the packet format of at least one protocol layer For example, the target configuration information may be used to configure the data packet format of the SDAP layer, PDCP layer, RLC layer and MAC layer.
  • each protocol layer of the NR protocol stack in the related art is compatible with the characteristics of encapsulating variable-sized data packets.
  • this overly flexible feature of encapsulating variable-sized data packets will generate a large amount of header overhead.
  • the RLC layer may carry segmentation fields, and the MAC layer needs to carry Packet length fields, etc. are not conducive to improving resource utilization.
  • the embodiment of the present application configures the data packet format through the target configuration information sent by the network side device, and uses the configured data packet format to encapsulate the service data, which can realize the use of the same data packet format for data transmission of one or all services, and thus can Reduce the header overhead required for data transfer.
  • the terminal receives target configuration information sent by the network side device, and the target configuration information is used to configure the data packet format; the terminal transmits service data based on the target configuration information.
  • the terminal can configure the data packet format for business data transmission based on the target configuration information sent by the network side device, so that the terminal can use a relatively fixed data packet format when transmitting business data, thereby reducing data packet header overhead and improving resources. Utilization.
  • the target configuration information is used to configure the data packet format of the target service
  • the terminal transmits service data based on the target configuration information, including:
  • the terminal transmits service data of the target service based on the target configuration information.
  • the target configuration information may carry the service identification information of the target service; or the target configuration information may be associated with the service identification information of the target service.
  • the terminal receives a first message sent by the network side device, and the first message carries the target configuration. information and business identification information of the target business.
  • the target configuration information is used to configure the data packet format of the target service; the terminal transmits the service data of the target service based on the target configuration information.
  • the terminal can configure the data packet format for transmitting the target service based on the target configuration information sent by the network side device, so that the terminal can use a relatively fixed data packet format when transmitting the service data of the target service, thereby reducing the data packet header overhead.
  • Improve resource utilization is used to configure the data packet format of the target service; the terminal transmits the service data of the target service based on the target configuration information.
  • the target configuration information is based on at least one of the following configurations:
  • the first negotiation information sent by the terminal is used to negotiate the data packet format
  • the first indication information is used to configure the target configuration information.
  • the network side device may configure the target configuration information based on the first negotiation information.
  • the first negotiation information may be data packet format negotiation information.
  • the first negotiation information may be used to indicate the data packet format of the transmission target service expected by the terminal.
  • the network side device sends target configuration information to the terminal based on the first negotiation information.
  • the target configuration information configures the data packet format of the target service to the data packet format expected by the terminal to transmit the target service.
  • the network side device can configure target configuration information based on the load status of the network side device. For example, if the network side device expects to adjust the encoding rate of the terminal's target service based on the load condition so that the data packet size sampled per unit time is 30 bytes, then the network side device can send target configuration information to the terminal, and the target configuration information Can be used to indicate that the size of a data packet (e.g., PDCP Service Data Unit (SDU)) is fixed at 30 bytes.
  • SDU PackedCP Service Data Unit
  • the network side device may configure the target configuration information based on the link status between the network side device and the terminal. For example, based on the link status with the terminal, the network side device can send target configuration information to the terminal.
  • the target configuration information adjusts the size of the payload (such as PDCP SDU) carried in the data packet from 50 bytes to 30 bytes. .
  • the network side device may configure the target configuration information based on the first indication information.
  • the network side device may be an access network device, and the access network device may receive first indication information sent by the core network device, and the first indication information may be used to assist the access network device in determining target configuration information.
  • the first indication information may also be called core network indication information, and the first indication information may be used to indicate at least one of the coding rate of the service and the target configuration information.
  • the first indication information may be used to indicate the coding rate of the target service.
  • the first indication information indicates to adjust the coding rate of the target service so that the size of the data packet sampled per unit time is 30 bytes, then
  • the network side device can send target configuration information to the terminal, and the target configuration information can be used to indicate that the size of the data packet (such as PDCP SDU) is fixed at 30 bytes.
  • the target configuration information is configured through the first negotiation information, so that the target configuration information can be determined by negotiating the data packet format between the terminal and the network side device; the target configuration information is configured through the load status of the network side device, so that the network side device
  • the data packet format for service data transmission by the terminal can be determined based on its own load condition; the target configuration information can be configured through the link condition between the network side device and the terminal, so that the adaptive service can be determined based on the link condition.
  • the data packet format for data transmission; configure the target configuration information through the core network indication information, so that the data packet format for the terminal's business data transmission can be determined according to the instructions of the core network indication information.
  • the method before the terminal receives the target configuration information sent by the network side device, the method further includes:
  • the terminal sends first negotiation information to the network side device, where the first negotiation information is used to negotiate a data packet format.
  • the first negotiation information may be used to negotiate the data packet format of at least one of SDAP data packets, PDCP data packets, RLC data packets, and MAC data packets.
  • the first negotiation information may include one or more of SDAP packet format negotiation information, PDCP packet format negotiation information, RLC packet format negotiation information, and MAC packet format negotiation information.
  • the first negotiation information may be the first request information, or may be the first expectation information, or may be the first suggestion information, etc.
  • This embodiment names the information used to negotiate the data packet format. Not limited.
  • the first request information may be used to characterize the data packet format requested by the terminal
  • the first expectation information may be used to characterize the data packet format expected by the terminal
  • the first suggestion information may be used to characterize the data packet format recommended by the terminal.
  • the first negotiation information can be used to negotiate the data packet format of the target service.
  • the first negotiation information can carry the service identification information of the target service.
  • the service identification information can be session identification information, bearer identification information and logical channel identification. At least one item in the information; or, the first negotiation information may not carry service identification information, so that the data packet format negotiated by the first negotiation information may be suitable for data transmission of any service of the terminal.
  • the data packet format is negotiated between the terminal and the network side device, so that a fixed data packet format is used for each data transmission, thereby avoiding a large amount of header overhead caused by using an overly flexible data packet format.
  • the first negotiation information is used to negotiate the data packet format of the target service.
  • the first negotiation information may carry the service identification information of the target service; or the first negotiation information may be associated with the service identification information of the target service.
  • the terminal sends a second message to the network side device, and the second message carries the second message. 1.
  • Negotiation information and service identification information of the target service may carry the service identification information of the target service.
  • the data packet format of the target service is negotiated through the terminal and the network side device, so that a fixed data packet format is used for each data transmission of the target service, avoiding a large number of problems caused by using an overly flexible data packet format. header overhead.
  • the target service is identified by at least one of the following:
  • the session identification information may include a protocol data unit (PDU) session (session) control ID; the bearer identification information may include a radio bearer (Radio Bearer, RB) ID; and the logical channel identification information may include an LCID.
  • PDU protocol data unit
  • RB radio bearer
  • the target configuration information includes at least one of the following:
  • the first configuration information is used to configure the data packet format of the service data adaptation protocol SDAP data packet
  • the second configuration information is used to configure the data packet format of the Packet Data Convergence Protocol PDCP data packet
  • the third configuration information is used to configure the data packet format of the wireless link control RLC data packet
  • the fourth configuration information is used to configure the data packet format of the media access control MAC data packet.
  • the terminal can use the preset configuration information to configure the protocol layer.
  • the target configuration information does not include configuration information for configuring the data packet format of the PDCP data packet, that is, the second configuration information
  • the terminal can use the preset PDCP data packet format configuration information to configure the PDCP protocol layer.
  • the preset PDCP data packet format configuration information may include encapsulating the PDCP layer data packet using a sequence number of a preset length (such as 6-bit PDCP SN).
  • the terminal The RLC protocol layer can be configured using preset RLC packet format configuration information.
  • the preset RLC packet format configuration information may include configuring the RLC entity using transparent transmission mode.
  • the data packet format of the SDAP data packet is configured through the first configuration information
  • the data packet format of the PDCP data packet is configured through the second configuration information
  • the data packet format of the RLC data packet is configured through the third configuration information
  • the data packet format of the RLC data packet is configured through the fourth configuration information.
  • the configuration information configures the packet format of the MAC packet, so that the packet format of each layer of the NR UP protocol stack can be configured.
  • the first configuration information includes at least one of the following:
  • the second indication information is used to indicate enabling or disabling the SDAP encapsulation header
  • the third indication information is used to indicate the SDAP data packet size
  • the second configuration information includes at least one of the following:
  • the fourth indication information is used to indicate the PDCP data packet size
  • the third configuration information includes:
  • the fifth indication information is used to indicate the RLC layer transmission mode
  • the fourth configuration information includes at least one of the following:
  • the sixth indication information is used to indicate enabling or disabling the MAC multiplexing function
  • the seventh indication information is used to indicate the MAC data packet size.
  • the length of the PDCP sequence number configured in the PDCP sequence number configuration information may be less than 8 bits.
  • the length of the PDCP sequence number configured in the PDCP sequence number configuration information may be 6 bits.
  • the second configuration information may further include: eighth indication information, and the eighth indication information may be used to indicate enabling or disabling the PDCP encapsulation header.
  • the eighth indication information may be associated with the PDCP sequence number configuration information. When the PDCP sequence number configuration information indicates that the PDCP SN is carried, the eighth indication information indicates that the PDCP encapsulation header is enabled.
  • the data packet format of the PDCP data packet can be configured as follows: the fourth indication information indicates that the PDCP SDU is fixed to 30 bytes, and the PDCP sequence number configuration information indicates that the PDCP header carries a 6-bit PDCP SN, and the PDCP header occupies one byte.
  • the terminal sends first negotiation information to the network side device, including:
  • the terminal sends first negotiation information to the network side device based on the coding rate of the service.
  • the terminal may send the first negotiation information to the network side device based on the coding rate of the target service.
  • the coding rate of the terminal's target service is adjusted from the first coding rate to the second coding rate.
  • the size of the data packet sampled per unit time at the first coding rate is 30 bytes, and the data sampled per unit time at the second coding rate If the packet size is 50 bytes, the terminal can send the first negotiation information to the network side device.
  • the first negotiation information can be used to indicate that the size of the data packet (such as PDCP SDU) is fixed at 50 bytes.
  • the terminal sends the first negotiation information to the network side device based on the coding rate of the service.
  • the terminal can negotiate the data packet format with the network side device based on the coding rate of its own service, so that the negotiated data
  • the packet format is adapted to the coding rate of the service.
  • the first negotiation information is used to negotiate the data packet format of at least one of the following data packets:
  • the data packet format of at least one of the SDAP data packet, PDCP data packet, RLC data packet and MAC data packet is negotiated through the first negotiation information, so that the data packets at each layer of the NR UP protocol stack can be processed.
  • the packet format is negotiated.
  • the first negotiation information includes at least one of the following:
  • the SDAP subheader negotiation information may be SDAP subheader negotiation information.
  • the SDAP packet size negotiation information may be SDAP packet size negotiation information.
  • the SDAP subheader configuration can be negotiated through the SDAP subheader negotiation information
  • the SDAP packet size can be negotiated through the SDAP packet size negotiation information
  • the SDAP subheader negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to configure the SDAP subheader; the terminal recommends or does not recommend configuring the SDAP subheader; the terminal supports or does not support the configuration of the SDAP subheader;
  • the SDAP packet size negotiation information is used to indicate any of the following:
  • the SDAP data packet size expected by the terminal The SDAP data packet size supported by the terminal; and the SDAP data packet size recommended by the terminal.
  • the first negotiation information includes at least one of the following:
  • the PDCP sequence number negotiation information may be PDCP sequence number negotiation information.
  • the PDCP packet size negotiation information may be PDCP packet size negotiation information.
  • the PDCP sequence number length can be negotiated through the PDCP sequence number negotiation information
  • the PDCP data packet size can be negotiated through the PDCP data packet size negotiation information
  • the PDCP sequence number negotiation information is used to indicate any of the following:
  • the PDCP packet size negotiation information is used to negotiate at least one of the following:
  • the PDCP packet size negotiation information can be used to negotiate the size of a single PDCP packet (such as PDCP SDU).
  • the PDCP data packet size negotiation information may include single PDCP data packet size information and cascade number information.
  • the first negotiation information includes at least one of the following:
  • the RLC subheader negotiation information may be RLC subheader negotiation information.
  • the RLC sequence number negotiation information may be RLC sequence number negotiation information.
  • the RLC packet size negotiation information may be RLC packet size negotiation information.
  • the RLC segmentation function negotiation information may be RLC segmentation function negotiation information.
  • the RLC subheader configuration can be negotiated through the RLC subheader negotiation information
  • the RLC sequence number can be negotiated through the RLC sequence number negotiation information
  • the RLC data packet size can be negotiated through the RLC packet size negotiation information.
  • Enabling or disabling the RLC segmentation function can be negotiated through the RLC segmentation function negotiation information.
  • the RLC subheader negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to configure the RLC subheader; the terminal recommends or does not recommend configuring the RLC subheader;
  • the RLC sequence number negotiation information is used to indicate any of the following:
  • the RLC sequence number that the terminal desires to configure the RLC sequence number that the terminal recommends to configure;
  • the RLC packet size negotiation information is used to indicate any of the following:
  • the RLC data packet size expected by the terminal the RLC data packet size supported by the terminal; the RLC data packet size recommended by the terminal;
  • the RLC segmentation function negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to enable the segmentation function; the terminal recommends enabling or disabling the segmentation function.
  • the first negotiation information includes at least one of the following:
  • the MAC data packet may be a MAC subSDU from a specific logical channel, or may be a MAC subPDU.
  • the MAC multiplexing function negotiation information may be MAC multiplexing negotiation information.
  • the MAC packet size negotiation information may be MAC packet size negotiation information.
  • the MAC multiplexing function negotiation information can be used to negotiate whether to enable the multiplexing function, and the MAC data packet size negotiation information can be used to negotiate the MAC data packet size.
  • the MAC multiplexing function negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to enable the multiplexing function; the terminal recommends or does not recommend enabling the multiplexing function;
  • the MAC packet size negotiation information is used to indicate any of the following:
  • the MAC data packet size expected by the terminal The MAC data packet size supported by the terminal; and the MAC data packet size recommended by the terminal.
  • the SDAP data packet size includes at least one of the following: SDAP service data unit SDU data packet size; SDAP protocol data unit PDU data packet size;
  • PDCP packet size includes at least one of the following: PDCP SDU packet size; PDCP PDU packet size;
  • RLC packet size includes at least one of the following: RLC SDU packet size; RLC PDU packet size;
  • the MAC packet size includes at least one of the following: MAC SDU packet size; MAC PDU packet size.
  • the terminal transmits service data based on the target configuration information, including:
  • the terminal encapsulates service data based on the target configuration information
  • the terminal transmits the encapsulated service data.
  • the terminal encapsulates service data based on the target configuration information; the terminal transmits the encapsulated service data.
  • the terminal can encapsulate service data according to the data packet format configured in the target configuration information, so that the terminal uses a relatively fixed data packet format when encapsulating data packets, thereby reducing data packet header overhead and improving resource utilization.
  • the terminal (such as User Equipment (UE)) sends the first negotiation information to the network side device.
  • the first negotiation information may be a data packet format negotiation message.
  • the data packet format negotiation message is used to negotiate transmission.
  • the data packet format negotiation message may include at least one of the following:
  • the SDAP packet format negotiation information may include one or more of the following information:
  • the negotiation information of the SDAP subheader may be used to indicate that the UE desires to configure or not configure the SDAP subheader; or to indicate that the UE recommends configuring or not to configure the SDAP subheader; or to indicate that the UE supports configuring or does not support configuring the SDAP subheader.
  • the SDAP data packet may be SDAP SDU or SDAP PDU.
  • the SDAP data packet size information is used to indicate the SDAP data packet size expected by the UE, or the SDAP data packet size supported by the UE, or the SDAP data packet size recommended by the UE.
  • the PDCP packet format negotiation information may include one or more of the following information:
  • the PDCP sequence number negotiation information may be used to indicate the PDCP SN that the UE expects to configure.
  • the PDCP sequence number negotiation information is equivalent to informing the network side that the UE does not expect to configure the PDCP header, that is, the PDCP layer does not need to carry the PDCP encapsulation header when encapsulating the data packet.
  • the PDCP data packet may be a PDCP SDU or a PDCP PDU.
  • the PDCP data packet size negotiation information is used to negotiate the size of a single PDCP data packet and/or the concatenated PDCP data packet.
  • the RLC packet format negotiation information may include one or more of the following information:
  • the negotiation information of the RLC subheader may be used to indicate that the UE desires to carry or not carry the RLC subheader, or to indicate that the UE recommends carrying or not to carry the RLC subheader.
  • the negotiation information of the RLC sequence number may be used to indicate the RLC SN that the UE expects to configure.
  • the negotiation information of the RLC sequence number is equivalent to informing the network side that the UE does not expect to configure the RLC header, that is, the RLC layer does not need to carry the RLC encapsulation header when encapsulating the data packet.
  • the RLC data packet may be an RLC SDU or an RLC PDU.
  • the RLC data packet size negotiation information may be used to indicate the RLC data packet size expected by the UE, or the RLC data packet size supported by the UE, or the RLC data packet size recommended by the UE.
  • the negotiation information of the RLC segmentation function is used to indicate that the UE expects or does not expect to enable the segmentation function, or the UE recommends or does not recommend enabling the segmentation function. For example, when the segmentation function is not enabled, the transmission resources provided by the network side device are sufficient to transmit the complete RLC SDU.
  • the MAC packet format negotiation information may include one or more of the following information:
  • the MAC multiplexing negotiation information is used to indicate that the UE desires to perform or not perform the multiplexing function, or or instructs the UE to recommend performing or not performing multiplexing.
  • the data packet format negotiation information may also include service identification information.
  • the data packet format negotiation message is used to negotiate the data packet format of the target service identified by the service identification information.
  • the service identification information is used to identify the target service of the UE.
  • the service identification information may include one or more of the following:
  • the session identification information may include PDU session ID; the bearer identification information may include RB ID; and the logical channel identification information may include LCID.
  • the data packet format negotiation information sent by the UE to the network side device may be sent based on the following information:
  • the coding rate of the target service is the coding rate of the target service.
  • the data packet format negotiation information does not include service identification information, it may be assumed that the data packet format negotiated by the data packet format negotiation information may be applicable to data transmission of any service of the UE.
  • the network side device sends target configuration information to the UE.
  • the target configuration information may be data packet format configuration information.
  • the data packet format configuration information is used to configure the data packet format for transmitting target service data.
  • the network side device determines the data packet format configuration information based on one or more of the following information:
  • the data packet format negotiation information of the UE is not limited to the UE.
  • the link status of the UE is the link status of the UE
  • the first indication information may be indication information of the core network.
  • the network side device receives the data packet format negotiation information sent by the UE, and the data packet format negotiation information is used to indicate the UE's desired
  • the network side device provides data packet format configuration information, and the data packet format of the target service is configured as the data packet format expected by the UE to transmit the target service.
  • the network side device Taking the determination of the data packet format configuration information based on the load status of the network side device as an example, the network side device expects to adjust the coding rate of the target service of the UE from the third coding rate to the fourth coding rate based on the load status.
  • the size of the data packet sampled per unit time of the coding rate is 50 bytes, and the size of the data packet sampled per unit time of the fourth coding rate is 30 bytes.
  • the network side device can send the data packet format configuration information to the UE.
  • the data packet Format configuration information can be used to indicate that the size of data packets (such as PDCP SDU) is fixed at 30 bytes.
  • the network side device can send the data packet format configuration information to the UE based on the link status with the UE.
  • the data packet format configuration information Adjust the size of the payload carried by the data packet (such as PDCP SDU) from 50 bytes to 30 bytes.
  • the network side device may be a base station, and the core network sends the first indication information to the base station, and the first indication information is used to assist the base station.
  • Determine the data packet format configuration information which is used to determine the data packet format of the target service.
  • the data packet format configuration information includes one or more of the following:
  • the SDAP packet format configuration information may include one or more of the following: indication information to enable or disable the use of SDAP encapsulation header; SDAP packet size indication information.
  • the PDCP packet format configuration information may include one or more of the following: PDCP packet size indication information, PDCP sequence number configuration information.
  • the RLC data packet format configuration information may include the following information: RLC layer transmission mode information.
  • the MAC packet format configuration information may include one or more of the following: indication information for enabling or disabling the MAC multiplexing function, and indication information for the MAC packet size.
  • the MAC data packet size may be the data packet size of the MAC subSDU of a specific logical channel.
  • the SDAP data packet format configuration information is the configuration information of the data packet format of the SDAP layer
  • the PDCP data packet format configuration information is the configuration information of the data packet format of the PDCP layer
  • the RLC data packet format configuration information is the data packet format of the RLC layer.
  • Configuration information, MAC packet format configuration information is the configuration information of the MAC layer packet format.
  • the data packet format configuration information may also include service identification information, and the service identification information may include one or more of the following:
  • the data packet format configuration information does not include service identification information, it may be assumed that the data packet format configuration information may be applicable to data transmission of any service of the UE.
  • the AS of the UE may notify the higher layer (for example, application layer) to assist the higher layer in adjusting the coding rate of the target service.
  • the higher layer for example, application layer
  • the UE receives the data packet format configuration information sent by the network side device, and transmits the data packet of the target service based on the data packet format configuration information.
  • the data packet format for data transmission configured by the data packet format configuration information is as follows:
  • the SDAP SDU size is fixed at 30 byte
  • the PDCP SDU is fixed to 30 bytes after negotiation between the UE and the network side device, the PDCP header occupies one byte, and the PDCP header (header) carries a 6-bit PDCP SN;
  • the RLC layer there is no RLC header after negotiation between the UE and the network side device, and the RLC splitting function is not enabled;
  • the MAC SDU is fixed to 31 bytes after negotiation between the UE and the network side device.
  • the MAC enables multiplexing.
  • the MAC header occupies one byte and carries the LCID field.
  • the MAC sub (sub) PDU is 32 bytes in total.
  • the NR protocol stack flexibly supports data packets of various sizes, and the data packet format design of each protocol layer is compatible with the characteristics of encapsulating variable-sized data packets.
  • this overly flexible feature of encapsulating variable-sized data packets will generate a large amount of header overhead.
  • the RLC layer may carry segmentation fields, and the MAC layer needs to carry Packet length fields, etc. are not conducive to improving resource utilization.
  • the UE and the network side device negotiate the data packet format to achieve the use of the same data packet format for data transmission of the target service, thereby reducing the header overhead required for data transmission.
  • Figure 17 is a flow chart of an information sending method provided by an embodiment of the present application. As shown in Figure 17, the information sending method includes the following steps:
  • Step 201 The network side device sends target configuration information to the terminal, where the target configuration information is used to configure the data packet format.
  • the target configuration information is used to configure the data packet format of the target service.
  • the method further includes:
  • the network side device configures the target configuration information based on at least one of the following:
  • the first negotiation information sent by the terminal is used to negotiate the data packet format
  • the first indication information is used to configure the target configuration information.
  • the target configuration information is configured based on the first indication information
  • the network side device is an access network device
  • the method further includes:
  • the access network device receives the first indication information sent by the core network device.
  • the first indication information is used to indicate any of the following:
  • the method further includes:
  • the network side device receives the first negotiation information sent by the terminal, and the first negotiation information is used to negotiate the data packet format.
  • the first negotiation information is used to negotiate the data packet format of the target service.
  • the target service is identified by at least one of the following:
  • the target configuration information includes at least one of the following:
  • the first configuration information is used to configure the data packet format of the service data adaptation protocol SDAP data packet
  • the second configuration information is used to configure the data packet format of the Packet Data Convergence Protocol PDCP data packet
  • the third configuration information is used to configure the data packet format of the wireless link control RLC data packet
  • the fourth configuration information is used to configure the data packet format of the media access control MAC data packet.
  • this embodiment is an implementation of the network side device corresponding to the embodiment shown in Figure 15.
  • the terminal can configure the data packet format for business data transmission based on the target configuration information sent by the network side device, so that the terminal can use a relatively fixed data packet format when transmitting business data, thereby reducing data packet header overhead and improving resources. Utilization.
  • Figure 18 is a flow chart of an information sending method provided by an embodiment of the present application. As shown in Figure 18, the information sending method includes the following steps:
  • Step 301 The core network device sends first instruction information to the access network device, where the first instruction information is used to assist the access network device in configuring the data packet format.
  • the first indication information is used to indicate any of the following:
  • Target configuration information which is used to configure the data packet format.
  • this embodiment is an implementation of the core network equipment corresponding to the embodiment shown in Figure 17.
  • the core network equipment corresponding to the embodiment shown in Figure 17.
  • the core network device sends first instruction information to the access network device, and the first instruction information is used to assist the access network device in configuring the data packet format. Therefore, the access network device can configure the data packet format for service data transmission for the terminal based on the first indication information, so that the terminal can use a relatively fixed data packet format when transmitting service data, thereby reducing data packet header overhead and improving resource utilization. Rate.
  • the execution subject may be a data transmission device.
  • a data transmission device performing a data transmission method is used as an example to illustrate the data transmission device provided by the embodiment of the present application.
  • Figure 19 is a structural diagram of a data transmission device provided by an embodiment of the present application.
  • the data transmission device is applied to a terminal.
  • the data transmission device 400 includes:
  • the receiving module 401 is used to receive target configuration information sent by the network side device, where the target configuration information is used to configure the data packet format;
  • the transmission module 402 is used to transmit service data based on the target configuration information.
  • the target configuration information is used to configure the data packet format of the target service
  • the transmission module 402 is specifically used for:
  • the terminal transmits service data of the target service based on the target configuration information.
  • the target configuration information is based on at least one of the following configurations:
  • the first negotiation information sent by the terminal is used to negotiate the data packet format
  • the first indication information is used to configure the target configuration information.
  • the device also includes:
  • a sending module configured to send first negotiation information to the network side device, where the first negotiation information is used to negotiate a data packet format.
  • the first negotiation information is used to negotiate the data packet format of the target service.
  • the target service is identified by at least one of the following:
  • the target configuration information includes at least one of the following:
  • the first configuration information is used to configure the data packet format of the service data adaptation protocol SDAP data packet
  • the second configuration information is used to configure the data packet format of the Packet Data Convergence Protocol PDCP data packet
  • the third configuration information is used to configure the data packet format of the wireless link control RLC data packet
  • the fourth configuration information is used to configure the data packet format of the media access control MAC data packet.
  • the first configuration information includes at least one of the following:
  • the second indication information is used to indicate enabling or disabling the SDAP encapsulation header
  • the third indication information is used to indicate the SDAP data packet size
  • the second configuration information includes at least one of the following:
  • the fourth indication information is used to indicate the PDCP data packet size
  • the third configuration information includes:
  • the fifth indication information is used to indicate the RLC layer transmission mode
  • the fourth configuration information includes at least one of the following:
  • the sixth indication information is used to indicate enabling or disabling the MAC multiplexing function
  • the seventh indication information is used to indicate the MAC data packet size.
  • the sending module is specifically used to:
  • the terminal sends first negotiation information to the network side device based on the coding rate of the service.
  • the first negotiation information is used to negotiate the data packet format of at least one of the following data packets:
  • the first negotiation information includes at least one of the following:
  • the SDAP subheader negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to configure the SDAP subheader; the terminal recommends or does not recommend configuring the SDAP subheader; the terminal supports or does not support the configuration of the SDAP subheader;
  • the SDAP packet size negotiation information is used to indicate any of the following:
  • the SDAP data packet size expected by the terminal The SDAP data packet size supported by the terminal; and the SDAP data packet size recommended by the terminal.
  • the first negotiation information includes at least one of the following:
  • the PDCP sequence number negotiation information is used to indicate any of the following:
  • the PDCP packet size negotiation information is used to negotiate at least one of the following:
  • the first negotiation information includes at least one of the following:
  • the RLC subheader negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to configure the RLC subheader; the terminal recommends or does not recommend configuring the RLC subheader;
  • the RLC sequence number negotiation information is used to indicate any of the following:
  • the RLC sequence number that the terminal desires to configure the RLC sequence number that the terminal recommends to configure;
  • the RLC packet size negotiation information is used to indicate any of the following:
  • the RLC data packet size expected by the terminal the RLC data packet size supported by the terminal; the RLC data packet size recommended by the terminal;
  • the RLC segmentation function negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to enable the segmentation function; the terminal recommends enabling or disabling the segmentation function.
  • the first negotiation information includes at least one of the following:
  • the MAC multiplexing function negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to enable the multiplexing function; the terminal recommends or does not recommend enabling the multiplexing function;
  • the MAC packet size negotiation information is used to indicate any of the following:
  • the MAC data packet size expected by the terminal The MAC data packet size supported by the terminal; and the MAC data packet size recommended by the terminal.
  • the SDAP data packet size includes at least one of the following: SDAP service data unit SDU data packet size; SDAP protocol data unit PDU data packet size;
  • PDCP packet size includes at least one of the following: PDCP SDU packet size; PDCP PDU packet size;
  • RLC packet size includes at least one of the following: RLC SDU packet size; RLC PDU packet size;
  • the MAC packet size includes at least one of the following: MAC SDU packet size; MAC PDU packet size.
  • the transmission module 402 is specifically used to:
  • the data transmission device in the embodiment of the present application can configure the data packet format for business data transmission based on the target configuration information sent by the network side device, so that the terminal can use a relatively fixed data packet format when transmitting business data, thereby enabling Reduce data packet header overhead and improve resource utilization.
  • the data transmission device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • NAS Network Attached Storage
  • the data transmission device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 15 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 20 is a structural diagram of an information sending device provided by an embodiment of the present application.
  • the information sending device is applied to network side equipment.
  • the information sending device 500 includes:
  • the sending module 501 is used to send target configuration information to the terminal, where the target configuration information is used to configure the data packet format.
  • the target configuration information is used to configure the data packet format of the target service.
  • the device also includes:
  • a configuration module configured to configure the target configuration information based on at least one of the following:
  • the first negotiation information sent by the terminal is used to negotiate the data packet format
  • the first indication information is used to configure the target configuration information.
  • the target configuration information is configured based on the first indication information
  • the network side device is an access network device
  • the device further includes:
  • the first receiving module is configured to receive the first indication information sent by the core network device.
  • the first indication information is used to indicate any of the following:
  • the device also includes:
  • the second receiving module is configured to receive the first negotiation information sent by the terminal, where the first negotiation information is used to negotiate the data packet format.
  • the first negotiation information is used to negotiate the data packet format of the target service.
  • the target service is identified by at least one of the following:
  • the target configuration information includes at least one of the following:
  • the first configuration information is used to configure the data packet format of the service data adaptation protocol SDAP data packet
  • the second configuration information is used to configure the data packet format of the Packet Data Convergence Protocol PDCP data packet
  • the third configuration information is used to configure the data packet format of the wireless link control RLC data packet
  • the fourth configuration information is used to configure the data packet format of the media access control MAC data packet.
  • the information sending device in the embodiment of the present application sends target configuration information to the terminal, so that the terminal can use a relatively fixed data packet format when transmitting business data, thereby reducing data packet header overhead and improving resource utilization.
  • the information sending device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • NAS Network Attached Storage
  • the information sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 17 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 21 is a structural diagram of an information sending device provided by an embodiment of the present application.
  • the information sending device is applied to core network equipment.
  • the information sending device 600 includes:
  • the sending module 601 is configured to send first indication information to the access network device, where the first indication information is used to assist the access network device in configuring the data packet format.
  • the first indication information is used to indicate any of the following:
  • Target configuration information which is used to configure the data packet format.
  • the information sending device in the embodiment of the present application sends first instruction information to the access network device, and the first instruction information is used to assist the access network device in configuring the data packet format. Therefore, the access network device can configure the data packet format for service data transmission for the terminal based on the first indication information, so that the terminal can use a relatively fixed data packet format when transmitting service data, thereby reducing data packet header overhead and improving resource utilization. Rate.
  • the information sending device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip.
  • the electronic device may be a terminal or other devices other than the terminal.
  • terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.
  • NAS Network Attached Storage
  • the information sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 18 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 700, which includes a processor 701 and a memory 702.
  • the memory 702 stores programs or instructions that can be run on the processor 701, such as , when the communication device 700 is a terminal, when the program or instruction is executed by the processor 701, each step of the above data transmission method embodiment is implemented, and the same technical effect can be achieved.
  • the communication device 700 is a network-side device, when the program or instruction is executed by the processor 701, each step of the above information sending method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, the details are not repeated here.
  • Embodiments of the present application also provide a terminal, including a processor and a communication interface.
  • the communication interface is used to receive target configuration information sent by a network side device.
  • the target configuration information is used to configure the data packet format; the processor is used to configure the data packet format based on the target.
  • Configuration information transmits business data.
  • This terminal embodiment corresponds to the above-mentioned data transmission method embodiment.
  • Each implementation process and implementation method of the above-mentioned data transmission method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 23 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, a processor 810, etc. At least some parts.
  • the terminal 800 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 810 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in Figure 23 does not constitute a limitation on the terminal. The terminal can Including more or less components than shown in the figures, or combining certain components, or different arrangement of components, will not be described again here.
  • the input unit 804 may include a graphics processing unit (Graphics Processing Unit, GPU) 8041 and a microphone 8042.
  • the graphics processor 8041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 807 includes a touch panel 8071 and at least one of other input devices 8072 .
  • Touch panel 8071 also known as touch screen.
  • the touch panel 8071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 8072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 801 after receiving downlink data from the network side device, the radio frequency unit 801 can transmit it to the processor 810 for processing; in addition, the radio frequency unit 801 can send uplink data to the network side device.
  • the radio frequency unit 801 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 809 may be used to store software programs or instructions as well as various data.
  • the memory 809 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 809 may include volatile memory or non-volatile memory, or memory 809 may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus
  • the processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 810.
  • the radio frequency unit 801 is used to receive target configuration information sent by the network side device, where the target configuration information is used to configure the data packet format;
  • Processor 810 configured to transmit service data based on the target configuration information.
  • the target configuration information is used to configure the data packet format of the target service
  • Processor 810 configured to transmit service data of the target service based on the target configuration information.
  • the target configuration information is based on at least one of the following configurations:
  • the first negotiation information sent by the terminal is used to negotiate the data packet format
  • the first indication information is used to configure the target configuration information.
  • the radio frequency unit 801 is also configured to send first negotiation information to the network side device, where the first negotiation information is used to negotiate a data packet format.
  • the first negotiation information is used to negotiate the data packet format of the target service.
  • the target service is identified by at least one of the following:
  • the target configuration information includes at least one of the following:
  • the first configuration information is used to configure the data packet format of the service data adaptation protocol SDAP data packet
  • the second configuration information is used to configure the data packet format of the Packet Data Convergence Protocol PDCP data packet
  • the third configuration information is used to configure the data packet format of the wireless link control RLC data packet
  • the fourth configuration information is used to configure the data packet format of the media access control MAC data packet.
  • the first configuration information includes at least one of the following:
  • the second indication information is used to indicate enabling or disabling the SDAP encapsulation header
  • the third indication information is used to indicate the SDAP data packet size
  • the second configuration information includes at least one of the following:
  • the fourth indication information is used to indicate the PDCP data packet size
  • the third configuration information includes:
  • the fifth indication information is used to indicate the RLC layer transmission mode
  • the fourth configuration information includes at least one of the following:
  • the sixth indication information is used to indicate enabling or disabling the MAC multiplexing function
  • the seventh indication information is used to indicate the MAC data packet size.
  • the radio frequency unit 801 is also used for:
  • the first negotiation information is used to negotiate the data packet format of at least one of the following data packets:
  • the first negotiation information includes at least one of the following:
  • the SDAP subheader negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to configure the SDAP subheader; the terminal recommends or does not recommend configuring the SDAP subheader; the terminal supports or does not support the configuration of the SDAP subheader;
  • the SDAP packet size negotiation information is used to indicate any of the following:
  • the SDAP data packet size expected by the terminal The SDAP data packet size supported by the terminal; and the SDAP data packet size recommended by the terminal.
  • the first negotiation information includes at least one of the following:
  • the PDCP sequence number negotiation information is used to indicate any of the following:
  • the PDCP packet size negotiation information is used to negotiate at least one of the following:
  • the first negotiation information includes at least one of the following:
  • the RLC subheader negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to configure the RLC subheader; the terminal recommends or does not recommend configuring the RLC subheader;
  • the RLC sequence number negotiation information is used to indicate any of the following:
  • the RLC sequence number that the terminal desires to configure the RLC sequence number that the terminal recommends to configure;
  • the RLC packet size negotiation information is used to indicate any of the following:
  • the RLC data packet size expected by the terminal the RLC data packet size supported by the terminal; the RLC data packet size recommended by the terminal;
  • the RLC segmentation function negotiation information is used to indicate any of the following:
  • the terminal desires or does not desire to enable the segmentation function; the terminal recommends enabling or disabling the segmentation function.
  • the first negotiation information includes at least one of the following:
  • the MAC multiplexing function negotiation information is used to indicate any of the following:
  • the terminal expects or does not expect to enable the multiplexing function; the terminal recommends or does not recommend enabling the multiplexing function;
  • the MAC packet size negotiation information is used to indicate any of the following:
  • the MAC data packet size expected by the terminal The MAC data packet size supported by the terminal; and the MAC data packet size recommended by the terminal.
  • the SDAP data packet size includes at least one of the following: SDAP service data unit SDU data packet size; SDAP protocol data unit PDU data packet size;
  • PDCP packet size includes at least one of the following: PDCP SDU packet size; PDCP PDU packet size;
  • RLC packet size includes at least one of the following: RLC SDU packet size; RLC PDU packet size;
  • the MAC packet size includes at least one of the following: MAC SDU packet size; MAC PDU packet size.
  • processor 810 is also used to:
  • Embodiments of the present application also provide a network side device, including a processor and a communication interface.
  • the communication interface is used to send target configuration information to a terminal, and the target configuration information is used to configure a data packet format.
  • This network-side device embodiment corresponds to the above-mentioned information sending method embodiment.
  • Each implementation process and implementation manner of the above-mentioned information sending method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • the network side device 900 includes: an antenna 901, a radio frequency device 902, a baseband device 903, a processor 904 and a memory 905.
  • Antenna 901 is connected to radio frequency device 902.
  • the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing.
  • the baseband device 903 processes the information to be sent and sends it to the radio frequency device 902.
  • the radio frequency device 902 processes the received information and then sends it out through the antenna 901.
  • the method performed by the network side device in the above embodiment can be implemented in the baseband device 903, which includes a baseband processor.
  • the baseband device 903 may include, for example, at least one baseband board on which multiple chips are disposed, as shown in FIG. 24 .
  • One of the chips is, for example, a baseband processor, which is connected to the memory 905 through a bus interface to call the memory 905 .
  • the network side device may also include a network interface 906, which is, for example, a common public radio interface (CPRI).
  • a network interface 906 which is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 900 in this embodiment of the present invention also includes: stored in the memory 905 and available on the processor 904, the processor 904 calls the instructions or programs in the memory 905 to execute the method of executing each module shown in Figure 20, and achieves the same technical effect. To avoid repetition, it will not be described again here.
  • the embodiment of the present application also provides a core network device.
  • the core network device 1000 includes: a processor 1001, a network interface 1002, and a memory 1003.
  • the network interface 1002 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the core network device 1000 in this embodiment of the present invention also includes: instructions or programs stored in the memory 1003 and executable on the processor 1001.
  • the processor 1001 calls the instructions or programs in the memory 1003 to execute each of the steps shown in Figure 21.
  • the method of module execution and achieving the same technical effect will not be described in detail here to avoid duplication.
  • Embodiments of the present application also provide a readable storage medium.
  • Programs or instructions are stored on the readable storage medium.
  • the program or instructions are executed by a processor, each process of the above-mentioned data transmission method or information transmission method embodiment is implemented. And can achieve the same technical effect, so to avoid repetition, they will not be described again here.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above data transmission method or information sending. Each process of the method embodiment can achieve the same technical effect, so to avoid repetition, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above data transmission method or information.
  • Each process of the sending method can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • Embodiments of the present application also provide a data transmission system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the data transmission method as described above.
  • the network side device can be used to perform the information as described above. The steps of the sending method.
  • the methods of the above embodiments can It can be implemented with the help of software plus the necessary common hardware platform. Of course, it can also be implemented through hardware, but in many cases the former is a better implementation method.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to related technologies.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种数据传输方法、信息发送方法、终端及网络侧设备，属于通信技术领域，本申请实施例的数据传输方法，包括：终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；所述终端基于所述目标配置信息传输业务数据。

Description

数据传输方法、信息发送方法、终端及网络侧设备
相关申请的交叉引用
本申请主张在2022年05月09日在中国提交的中国专利申请No.202210501989.9的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种数据传输方法、信息发送方法、终端及网络侧设备。
背景技术
终端在对数据包进行封装时，按照封装规则对数据包进行封装，并且每一协议层在对数据包进行封装时会关联该协议层的封装包头。相关技术中的封装规则需要具备兼容封装可变大小的数据包的特性，而可变大小的数据包格式可能不同，不同的数据包格式的数据包头不同，导致按照预定义的封装规则对数据包进行封装会产生大量的数据包头开销，资源利用率较低。
发明内容
本申请实施例提供一种数据传输方法、信息发送方法、终端及网络侧设备，能够解决资源利用率较低的问题。
第一方面，提供了一种数据传输方法，包括：
终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
所述终端基于所述目标配置信息传输业务数据。
第二方面，提供了一种信息发送方法，包括：
网络侧设备向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
第三方面，提供了一种信息发送方法，包括：
核心网设备向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
第四方面，提供了一种数据传输装置，应用于终端，所述数据传输装置包括：
接收模块，用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
传输模块，用于基于所述目标配置信息传输业务数据。
第五方面，提供了一种信息发送装置，应用于网络侧设备，所述信息发送装置包括：
发送模块，用于向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
第六方面，提供了一种信息发送装置，应用于核心网设备，所述信息发送装置包括：
发送模块，用于向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
第七方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第八方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；所述处理器用于基于所述目标配置信息传输业务数据。
第九方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第十方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
第十一方面，提供了一种核心网设备，该核心网设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第十二方面，提供了一种数据传输系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的数据传输方法的步骤，所述网络侧设备可用于执行如第二方面或第三方面所述的信息发送方法的步骤。
第十三方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十四方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法，或实现如第二方面所述的方法，或实现如第三方面所述的方法。
第十四方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或实现如第二方面所述的方法的步骤，实现如第三方面所述的方法的步骤。
在本申请实施例中，终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；所述终端基于所述目标配置信息传输业务数据。这样，终端能够基于网络侧设备发送的目标配置信息，配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的一种NR UP协议架构示图；
图3是本申请实施例提供的一种SDAP数据包格式的示意图；
图4是本申请实施例提供的另一种SDAP数据包格式的示意图；
图5是本申请实施例提供的一种PDCP数据包格式的示意图；
图6是本申请实施例提供的另一种PDCP数据包格式的示意图；
图7是本申请实施例提供的一种RLC数据包格式的示意图；
图8是本申请实施例提供的另一种RLC数据包格式的示意图；
图9是本申请实施例提供的一种MAC数据包格式的示意图；
图10是本申请实施例提供的另一种MAC数据包格式的示意图；
图11是本申请实施例提供的另一种MAC数据包格式的示意图；
图12是本申请实施例提供的另一种MAC数据包格式的示意图；
图13是本申请实施例提供的另一种MAC数据包格式的示意图；
图14是本申请实施例提供的另一种MAC数据包格式的示意图；
图15是本申请实施例提供的一种数据传输方法的流程图；
图16是本申请实施例提供的一种数据包格式的配置示意图；
图17是本申请实施例提供的一种信息发送方法的流程图；
图18是本申请实施例提供的另一种信息发送方法的流程图；
图19是本申请实施例提供的一种数据传输装置的结构图；
图20是本申请实施例提供的一种信息发送装置的结构图；
图21是本申请实施例提供的另一种信息发送装置的结构图；
图22是本申请实施例提供的一种通信设备的结构图；
图23是本申请实施例提供的一种终端的结构示意图；
图24是本申请实施例提供的一种网络侧设备的结构示意图；
图25是本申请实施例提供的一种核心网设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、 “第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等，基站可被称为节点B(Node B，NB)、演进节点B(Evolved Node B，eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项： 核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)，统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
为了便于更好地理解本发明实施例，下面先介绍以下技术点。
关于NR用户面(User plane，UP)协议栈：
NR UP协议架构示图如图2所示，由服务数据适应协议(Service Data Adaptation Protocol，SDAP)、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)、无线链路控制(Radio Link Control，RLC)、媒体接入控制(Medium Access Control，MAC)和物理层(Physical Layer，PHY)组成。
对于SDAP：
SDAP主要负责服务质量(Quality of Service，QoS)流(flow)和数据无线承载(Data Radio Bearer，DRB)的映射管理；
其中，上行(Uplink，UL)和下行(Downlink，DL)数据包对应的SDAP头(header)是可配置的。如果配置，则对应的SDAP header占据一字节。SDAP层数据包格式可以如图3和图4所示，主要用于携带QoS flow标识(QoS Flow Identifier，QFI)。图3和图4中，Data表示数据区域。
对于PDCP：
PDCP主要负责头压缩和/或解压缩，加密和/或解密，完整性保护和/或完整性验证，数据复制和/或重复检测，重排序，PDCP重传等处理；
PDCP数据包(即PDCP data PDU)携带PDCP头(header)，PDCP header主要携带PDCP序列号(Sequence Number，SN)，对于业务数据，可使用12比特或18比特的PDCP SN，具体取决于网络侧配置，分别占据2或3个字节。PDCP层数据包格式如图5和图6所示。图5为使用12比特的PDCP SN的PDCP层数据包格式。图6为使用18比特的PDCP SN的PDCP层数据包格式。图5和图6中，Data表示数据区域，Optional表征可选的，cont表征内容。
对于RLC：
RLC主要负责数据分割和/或重组，自动重传请求(Automatic Repeat request，ARQ)和/或重复检测和/或重分割(适用于确认模式)等功能。
RLC有透明模式(Transparent Mode，TM)、非确认模式(Unacknowledged Mode，UM)及确认模式(Acknowledged Mode，AM)三种传输方式，不同的传输方式具有不同的数据包格式。其中，TM无需携带RLC header，常用于系统消息、寻呼消息以及信令无线承载0(Signalling Radio Bearer 0，SRB0)承载的信令，并不用于传输业务数据。AM携带RLC header，RLC header须携带RLC SN，该RLC SN可为12比特或18比特RLC SN。UM在携带的数据包是完整数据包(即数据包没有被分割)时携带一字节的RLC header，该RLC header无需携带RLC SN，其他情况下RLC header均需携带RLC SN，该携带的RLC SN可为6比特或12比特的RLC SN。由于AM和UM支持数据包分割和/或重组功能，因此数据包格式相对复杂，RLC header需要携带分割信息，例如SI域及SO域，以便于接收端重组数据包。部分RLC层数据包格式如图7和图8所示。图7为携带12比特RLC SN及SO域的UDM PDU数据包格式。图8为携带18比特RLC SN及SO域的AMD PDU数据包格式。图7和图8中，Data表示数据区域。
对于MAC：
MAC层主要负责数据复用和/或解复用，混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)，资源调度等功能。
MAC层可透传数据包，即不携带MAC header，但是主要适用于寻呼消息、系统消息传输。其它情况需携带MAC header。由于MAC层具有数据复用和/或解复用功能，因此对每个MAC子(sub)PDU都有对应的MAC subheader，用于携带逻辑信道标识(Logical Channel Identity，LCID)，该LCID用于标识数据来源。此外，还携带L域，用于指示MAC subSDU的长度。图9至图11为MAC subheader携带8比特L域的MAC层数据包格式。图12至图14为MAC subheader携带16比特L域的MAC层数据包格式。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的数据传输方法、信息发送方法、终端及网络侧设备进行详细地说明。
参见图15，图15是本申请实施例提供的一种数据传输方法的流程图，如图15所示，数据传输方法包括以下步骤：
步骤101、终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
步骤102、所述终端基于所述目标配置信息传输业务数据。
其中，所述目标配置信息可以是数据包格式配置信息。
另外，所述终端可以向所述网络侧设备发送第一协商信息，所述第一协商信息用于协商数据包格式，从而网络侧设备可以基于终端发送的第一协商信息向终端发送目标配置信息；或者，终端可以接收网络侧设备主动发送的目标配置信息，网络侧设备可以基于网络侧设备的负载状况、所述网络侧设备与所述终端之间的链路状况及第一指示信息中的至少 一项主动向终端发送目标配置信息，所述第一指示信息可以用于辅助网络侧设备配置所述目标配置信息。
需要说明的是，所述目标配置信息可以用于配置目标业务的数据包格式，示例地，目标配置信息可以携带目标业务的业务标识信息，该业务标识信息可以是会话标识信息、承载标识信息及逻辑信道标识信息中的至少一项；或者，所述目标配置信息可以用于配置全部业务的数据包格式，示例地，目标配置信息可以不携带业务标识信息，从而目标配置信息配置的数据包格式可以适用于终端的任意业务的数据传输。
另外，所述目标配置信息可以用于配置NR协议栈的各个协议层的数据包格式，一种实施方式中，所述目标配置信息可以用于配置SDAP层、PDCP层、RLC层及MAC层中至少一个协议层的数据包格式。示例地，所述目标配置信息可以用于配置SDAP层、PDCP层、RLC层及MAC层的数据包格式。
需要说明的是，相关技术中NR协议栈的各个协议层的数据包格式设计兼容了封装可变大小的数据包的特性。但是，在某些场景下(例如，上行覆盖受限)，这种过于灵活的封装可变大小的数据包的特性会产生大量的头开销，例如，RLC层可能携带分割域，MAC层需要携带数据包长度域等，不利于提高资源利用率。本申请实施例通过网络侧设备发送的目标配置信息配置数据包格式，采用配置的数据包格式对业务数据进行封装，能够实现对某个或全部业务的数据传输使用相同的数据包格式，进而能够减少数据传输所需的头开销。
在本申请实施例中，终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；所述终端基于所述目标配置信息传输业务数据。这样，终端能够基于网络侧设备发送的目标配置信息，配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
可选地，所述目标配置信息用于配置目标业务的数据包格式；
所述终端基于所述目标配置信息传输业务数据，包括：
所述终端基于所述目标配置信息传输所述目标业务的业务数据。
其中，目标配置信息可以携带目标业务的业务标识信息；或者，目标配置信息可以与目标业务的业务标识信息关联，例如，终端接收网络侧设备发送的第一消息，该第一消息中携带目标配置信息及目标业务的业务标识信息。
该实施方式中，所述目标配置信息用于配置目标业务的数据包格式；所述终端基于所述目标配置信息传输所述目标业务的业务数据。这样，终端能够基于网络侧设备发送的目标配置信息，配置传输目标业务的数据包格式，使得终端在进行目标业务的业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
可选地，所述目标配置信息基于如下至少一项配置：
所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
所述网络侧设备的负载状况；
所述网络侧设备与所述终端之间的链路状况；
第一指示信息，所述第一指示信息用于配置所述目标配置信息。
其中，网络侧设备可以基于第一协商信息配置目标配置信息。该第一协商信息可以为数据包格式协商信息，该第一协商信息可以用于指示终端期望的传输目标业务的数据包格式，网络侧设备基于该第一协商信息向终端发送目标配置信息，该目标配置信息将所述目标业务的数据包格式配置为终端期望的传输目标业务的数据包格式。
另外，网络侧设备可以基于网络侧设备的负载状况配置目标配置信息。示例地，网络侧设备基于负载状况期望将终端的目标业务的编码速率调整为单位时间内采样的数据包大小为30字节，则网络侧设备可向终端发送目标配置信息，所述目标配置信息可用于指示数据包(例如，PDCP服务数据单元(Service Data Unit，SDU))大小固定为30字节。
另外，网络侧设备可以基于网络侧设备与所述终端之间的链路状况配置目标配置信息。示例地，网络侧设备基于与终端之间的链路状态，可向终端发送目标配置信息，该目标配置信息将数据包携带的有效负载(如PDCP SDU)大小从50字节调整为30字节。
另外，网络侧设备可以基于第一指示信息配置目标配置信息。网络侧设备可以为接入网设备，接入网设备可以接收核心网设备发送的第一指示信息，该第一指示信息可以用于辅助所述接入网设备确定目标配置信息。第一指示信息也可以称为核心网指示信息，第一指示信息可以用于指示业务的编码速率及所述目标配置信息中的至少一项。
一种实施方式中，第一指示信息可以用于指示目标业务的编码速率，示例地，第一指示信息指示将目标业务的编码速率调整为单位时间内采样的数据包大小为30字节，则网络侧设备可向终端发送目标配置信息，所述目标配置信息可用于指示数据包(如PDCP SDU)大小固定为30字节。
该实施方式中，通过第一协商信息配置目标配置信息，从而能够通过终端与网络侧设备协商数据包格式确定目标配置信息；通过所述网络侧设备的负载状况配置目标配置信息，从而网络侧设备能够基于自身的负载状况确定终端进行业务数据传输的数据包格式；通过所述网络侧设备与所述终端之间的链路状况配置目标配置信息，从而能够基于链路状况确定适配的进行业务数据传输的数据包格式；通过核心网指示信息配置目标配置信息，从而能够按照核心网指示信息的指示确定终端进行业务数据传输的数据包格式。
可选地，所述终端接收网络侧设备发送的目标配置信息之前，所述方法还包括：
所述终端向所述网络侧设备发送第一协商信息，所述第一协商信息用于协商数据包格式。
其中，所述第一协商信息可以用于协商SDAP数据包、PDCP数据包、RLC数据包、MAC数据包中的至少一项数据包的数据包格式。示例地，第一协商信息可以包括SDAP数据包格式协商信息、PDCP数据包格式协商信息、RLC数据包格式协商信息及MAC数据包格式协商信息中的一项或多项。
需要说明的是，该第一协商信息可以为第一请求信息，或者可以为第一期望信息，或者可以为第一建议信息，等等，本实施例对用于协商数据包格式的信息的命名不进行限定。第一请求信息可以用于表征终端请求的数据包格式，第一期望信息可以用于表征终端期望的数据包格式，第一建议信息可以用于表征终端建议的数据包格式。
另外，第一协商信息可以用于协商目标业务的数据包格式，示例地，第一协商信息可以携带目标业务的业务标识信息，该业务标识信息可以是会话标识信息、承载标识信息及逻辑信道标识信息中的至少一项；或者，所述第一协商信息可以不携带业务标识信息，从而第一协商信息协商的数据包格式可以适用于终端的任意业务的数据传输。
该实施方式中，通过终端和网络侧设备对数据包格式进行协商，使得每次数据传输使用固定的数据包格式，避免使用过于灵活的数据包格式而带来的大量头开销。
可选地，所述第一协商信息用于协商目标业务的数据包格式。
其中，第一协商信息可以携带目标业务的业务标识信息；或者，第一协商信息可以与目标业务的业务标识信息关联，例如，终端向网络侧设备发送第二消息，该第二消息中携带第一协商信息及目标业务的业务标识信息。
该实施方式中，通过终端和网络侧设备对目标业务的数据包格式进行协商，使得对于目标业务的每次数据传输使用固定的数据包格式，避免使用过于灵活的数据包格式而带来的大量头开销。
可选地，所述目标业务通过如下至少一项标识：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
其中，会话标识信息可以包括协议数据单元(Protocol Data Unit，PDU)会话(session)控制ID；承载标识信息可以包括无线承载(Radio Bearer，RB)ID；逻辑信道标识信息可以包括LCID。
可选地，所述目标配置信息包括如下至少一项：
第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
需要说明的是，在目标配置信息未包括某一协议层的数据包格式的配置信息的情况下，终端可以使用预设配置信息配置该协议层。示例性地，若目标配置信息未包括用于配置PDCP数据包的数据包格式的配置信息，即第二配置信息，终端可以使用预设的PDCP数据包格式配置信息配置PDCP协议层。例如，该预设的PDCP数据包格式配置信息可以包括使用预设长度的序列号(如6bit PDCP SN)封装PDCP层数据包。示例性地，若目标配置信息未包括用于配置RLC层数据包的数据包格式的配置信息，即第三配置信息，终端 可以使用预设的RLC数据包格式配置信息配置RLC协议层。例如，该预设的RLC数据包格式配置信息可以包括使用透传模式配置RLC实体。
该实施方式中，通过第一配置信息配置SDAP数据包的数据包格式，通过第二配置信息配置PDCP数据包的数据包格式，通过第三配置信息配置RLC数据包的数据包格式，通过第四配置信息配置MAC数据包的数据包格式，从而能够对NR UP协议栈的各层数据包的数据包格式进行配置。
可选地，所述第一配置信息包括如下至少一项：
第二指示信息，所述第二指示信息用于指示启用或禁用SDAP封装包头；
第三指示信息，所述第三指示信息用于指示SDAP数据包大小；
所述第二配置信息包括如下至少一项：
第四指示信息，所述第四指示信息用于指示PDCP数据包大小；
PDCP序列号配置信息；
所述第三配置信息包括：
第五指示信息，所述第五指示信息用于指示RLC层传输模式；
所述第四配置信息包括如下至少一项：
第六指示信息，所述第六指示信息用于指示启用或禁用MAC复用功能；
第七指示信息，所述第七指示信息用于指示MAC数据包大小。
其中，PDCP序列号配置信息配置的PDCP序列号长度可以小于8比特，示例地，PDCP序列号配置信息配置的PDCP序列号长度可以为6比特。
另外，所述第二配置信息还可以包括：第八指示信息，该第八指示信息可以用于指示启用或禁用PDCP封装包头。第八指示信息可以与PDCP序列号配置信息存在关联关系，在PDCP序列号配置信息指示携带PDCP SN的情况下，第八指示信息指示启用PDCP封装包头。
一种实施方式中，PDCP数据包的数据包格式可以配置为：通过第四指示信息指示PDCP SDU固定为30字节，通过PDCP序列号配置信息指示PDCP header携带6比特PDCP SN，PDCP header占据一字节。
可选地，所述终端向所述网络侧设备发送第一协商信息，包括：
所述终端基于业务的编码速率向所述网络侧设备发送第一协商信息。
其中，终端可以基于目标业务的编码速率向所述网络侧设备发送第一协商信息。
示例性的，终端的目标业务的编码速率从第一编码速率调整为第二编码速率，第一编码速率单位时间内采样的数据包大小为30字节，第二编码速率单位时间内采样的数据包大小为50字节，则终端可向网络侧设备发送第一协商信息，该第一协商信息可用于指示数据包(如PDCP SDU)大小固定为50字节。
该实施方式中，所述终端基于业务的编码速率向所述网络侧设备发送第一协商信息，这样，终端能够根据自身业务的编码速率与网络侧设备协商数据包格式，使得协商的数据 包格式与业务的编码速率适配。
可选地，所述第一协商信息用于协商如下至少一项数据包的数据包格式：
SDAP数据包；
PDCP数据包；
RLC数据包；
MAC数据包。
该实施方式中，通过第一协商信息协商SDAP数据包、PDCP数据包、RLC数据包及MAC数据包中至少一项数据包的数据包格式，从而能够对NR UP协议栈的各层数据包的数据包格式进行协商。
可选地，在所述第一协商信息用于协商SDAP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
SDAP子头协商信息；
SDAP数据包大小协商信息。
其中，SDAP子头协商信息可以是SDAP子头的协商信息。SDAP数据包大小协商信息可以是SDAP数据包大小的协商信息。
该实施方式中，通过SDAP子头协商信息能够对SDAP子头配置进行协商，通过SDAP数据包大小协商信息能够对SDAP数据包大小进行协商。
可选地，所述SDAP子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置SDAP子头；所述终端建议或不建议配置SDAP子头；所述终端支持或不支持配置SDAP子头；
所述SDAP数据包大小协商信息用于指示如下任意一项：
所述终端期望的SDAP数据包大小；所述终端支持的SDAP数据包大小；所述终端建议的SDAP数据包大小。
可选地，在所述第一协商信息用于协商PDCP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
PDCP序列号协商信息；
PDCP数据包大小协商信息。
其中，PDCP序列号协商信息可以是PDCP序列号的协商信息。PDCP数据包大小协商信息可以是PDCP数据包大小的协商信息。
该实施方式中，通过PDCP序列号协商信息能够对PDCP序列号长度进行协商，通过PDCP数据包大小协商信息能够对PDCP数据包大小进行协商。
可选地，所述PDCP序列号协商信息用于指示如下任意一项：
所述终端期望配置的PDCP序列号长度；所述终端建议配置的PDCP序列号长度；所述终端支持配置的PDCP序列号长度；
所述PDCP数据包大小协商信息用于协商如下至少一项：
在启用数据包级联功能的情况下的级联PDCP数据包大小；
在禁用数据包级联功能的情况下的PDCP数据包大小。
需要说明的是，在禁用数据包级联功能的情况下，即无PDCP级联操作的情况下，所述PDCP数据包大小协商信息可以用于协商单个PDCP数据包(例如PDCP SDU)大小。在启用数据包级联功能的情况下，即有PDCP级联操作的情况下，所述PDCP数据包大小协商信息可以包含单个PDCP数据包大小信息和级联个数信息。
可选地，在所述第一协商信息用于协商RLC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
RLC子头协商信息；
RLC序列号协商信息；
RLC数据包大小协商信息；
RLC分段功能协商信息。
其中，RLC子头协商信息可以是RLC子头的协商信息。RLC序列号协商信息可以是RLC序列号的协商信息。RLC数据包大小协商信息可以是RLC数据包大小的协商信息。RLC分段功能协商信息可以是RLC分段功能的协商信息。
该实施方式中，通过RLC子头协商信息能够对RLC子头配置进行协商，通过RLC序列号协商信息能够对RLC序列号进行协商，通过RLC数据包大小协商信息能够对RLC数据包大小进行协商，通过RLC分段功能协商信息能够对启用或禁用RLC分段功能进行协商。
可选地，所述RLC子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置RLC子头；所述终端建议或不建议配置RLC子头；
所述RLC序列号协商信息用于指示如下任意一项：
所述终端期望配置的RLC序列号；所述终端建议配置的RLC序列号；
所述RLC数据包大小协商信息用于指示如下任意一项：
所述终端期望的RLC数据包大小；所述终端支持的RLC数据包大小；所述终端建议的RLC数据包大小；
所述RLC分段功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用分段功能；所述终端建议启用或建议禁用分段功能。
可选地，在所述第一协商信息用于协商MAC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
MAC复用功能协商信息；
MAC数据包大小协商信息。
其中，所述MAC数据包可以是来自特定逻辑信道的MAC subSDU，或者可以是MAC subPDU。MAC复用功能协商信息可以是MAC复用的协商信息。MAC数据包大小协商信息可以是MAC数据包大小的协商信息。
该实施方式中，通过MAC复用功能协商信息能够对启用或不启用复用功能进行协商，通过MAC数据包大小协商信息能够对MAC数据包大小进行协商。
可选地，所述MAC复用功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用复用功能；所述终端建议或不建议启用复用功能；
所述MAC数据包大小协商信息用于指示如下任意一项：
所述终端期望的MAC数据包大小；所述终端支持的MAC数据包大小；所述终端建议的MAC数据包大小。
可选地，SDAP数据包大小包括如下至少一项：SDAP服务数据单元SDU数据包大小；SDAP协议数据单元PDU数据包大小；
PDCP数据包大小包括如下至少一项：PDCP SDU数据包大小；PDCP PDU数据包大小；
RLC数据包大小包括如下至少一项：RLC SDU数据包大小；RLC PDU数据包大小；
MAC数据包大小包括如下至少一项：MAC SDU数据包大小；MAC PDU数据包大小。
可选地，所述终端基于所述目标配置信息传输业务数据，包括：
所述终端基于所述目标配置信息封装业务数据；
所述终端传输封装后的业务数据。
该实施方式中，所述终端基于所述目标配置信息封装业务数据；所述终端传输封装后的业务数据。这样，终端能够按照目标配置信息配置的数据包格式对业务数据进行封装，使得终端在封装数据包时使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
下面通过一个具体的实施例对本申请实施例的数据传输方法进行说明：
(1)：终端(如用户设备(User Equipment，UE))向网络侧设备发送第一协商信息，该第一协商信息可以是数据包格式协商消息，所述数据包格式协商消息用于协商传输目标业务数据的数据包格式。
其中，所述数据包格式协商消息可以包括如下至少一项：
SDAP数据包格式协商信息；
PDCP数据包格式协商信息；
RLC数据包格式协商信息；
MAC数据包格式协商信息。
其中，所述SDAP数据包格式协商信息可以包括以下一项或多项信息：
SDAP子头的协商信息；
SDAP数据包大小的协商信息。
进一步的，所述SDAP子头的协商信息可以用于指示UE期望配置或不配置SDAP子头；或者指示UE建议配置或不配置SDAP子头；或者指示UE支持配置或不支持配置SDAP子头。
进一步的，所述SDAP数据包可以是SDAP SDU，或者是SDAP PDU。所述SDAP数据包大小信息用于指示UE期望的SDAP数据包大小，或者用于指示UE支持的SDAP数据包大小，或者用于指示UE建议的SDAP数据包大小。
其中，所述PDCP数据包格式协商信息可以包括以下一项或多项信息：
PDCP序列号的协商信息；
PDCP数据包大小的协商信息。
进一步的，所述PDCP序列号的协商信息可以用于指示UE期望配置的PDCP SN。示例性的,所述PDCP序列号的协商信息可以是SN序列号的长度信息，如SN＝6bit(可以理解为短序列号)。作为一个特例，上述SN序列号的长度信息可以说SN＝0bit。在该种情况下，所述PDCP序列号的协商信息相当于告知网络侧UE不期望配置PDCP header，即PDCP层在封装数据包时无需携带PDCP封装包头。
进一步的，所述PDCP数据包可以是PDCP SDU，或者是PDCP PDU。所述PDCP数据包大小的协商信息用于协商单个PDCP数据包和/或级联后PDCP数据包的大小。其中，所述RLC数据包格式协商信息可以包括以下一项或多项信息：
RLC子头的协商信息；
RLC序列号的协商信息；
RLC数据包大小的协商信息；
RLC分段功能的协商信息。
进一步的，所述RLC子头的协商信息可以用于指示UE期望携带或不携带RLC子头，或者指示UE建议携带或不携带RLC子头。
进一步的，所述RLC序列号的协商信息可以用于指示UE期望配置的RLC SN。示例性的,所述RLC序列号的协商信息可以是SN序列号的长度信息，如SN＝6bit(可以理解为短序列号)。作为一个特例，上述SN序列号的长度信息可以说SN＝0bit。在该种情况下，所述RLC序列号的协商信息相当于告知网络侧UE不期望配置RLC header，即RLC层在封装数据包时无需携带RLC封装包头。
进一步的，所述RLC数据包可以是RLC SDU，或者是RLC PDU。所述RLC数据包大小的协商信息可以用于指示UE期望的RLC数据包大小，或者用于指示UE支持的RLC数据包大小，或者用于指示UE建议的RLC数据包大小。
进一步的，所述RLC分段功能的协商信息用于指示UE期望或不期望启用分段功能，或者UE建议或不建议启用分段功能。示例性的，当不启用分段功能时，网络侧设备提供的传输资源足够传输完整的RLC SDU。
其中，所述MAC数据包格式协商信息可以包括以下一项或多项信息：
MAC复用的协商信息；
MAC数据包大小的协商信息。
进一步的，所述MAC复用的协商信息用于指示UE期望执行或不执行复用功能，或 者指示UE建议执行或不执行复用。
一种实施方式中，所述数据包格式协商信息还可以包括业务标识信息。所述数据包格式协商消息用于协商业务标识信息所标识的目标业务的数据包格式。其中，所述业务标识信息用于标识所述UE的目标业务。
其中，所述业务标识信息可以包括以下一项或多项：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
示例地，会话标识信息可以包括PDU session ID；承载标识信息可以包括RB ID；逻辑信道标识信息可以包括LCID。
一种实施方式中，所述UE向网络侧设备发送的所述数据包格式协商信息可以是基于以下信息发送：
目标业务的编码速率。
需要说明的是，在所述数据包格式协商信息不包含业务标识信息的情况下，可以默认所述数据包格式协商信息协商的数据包格式可以适用于所述UE的任意业务的数据传输。
(2)：网络侧设备向UE发送目标配置信息，该目标配置信息可以是数据包格式配置信息，所述数据包格式配置信息用于配置传输目标业务数据的数据包格式。
其中，所述网络侧设备(例如基站)基于以下一项或多项信息确定所述数据包格式配置信息：
所述UE的数据包格式协商信息；
所述网络侧设备的负载状况；
所述UE的链路状况；
第一指示信息，该第一指示信息可以是核心网的指示信息。
其中，以基于所述UE的数据包格式协商信息确定所述数据包格式配置信息为例，网络侧设备接收UE发送的数据包格式协商信息，所述数据包格式协商信息用于指示UE期望的传输目标业务的数据包格式，网络侧设备提供数据包格式配置信息，所述目标业务的数据包格式配置为UE期望的传输目标业务的数据包格式。
以基于所述网络侧设备的负载状况确定所述数据包格式配置信息为例，网络侧设备基于负载状况期望将UE的目标业务的编码速率从第三编码速率调整为第四编码速率，第三编码速率单位时间内采样的数据包大小为50字节，第四编码速率单位时间内采样的数据包大小为30字节，则网络侧设备可向UE发送数据包格式配置信息，所述数据包格式配置信息可用于指示数据包(如PDCP SDU)大小固定为30字节。
以基于所述UE的链路状况确定所述数据包格式配置信息为例，网络侧设备基于与UE之间的链路状态，可向UE发送数据包格式配置信息，所述数据包格式配置信息将数据包携带的有效负载(如PDCP SDU)大小从50字节调整为30字节。
以基于第一指示信息确定所述数据包格式配置信息为例，网络侧设备可以为基站，核心网向所述基站发送所述第一指示信息，所述第一指示信息用于辅助所述基站确定数据包格式配置信息，该数据包格式配置信息用于确定目标业务的数据包格式。
一种实施方式中，所述数据包格式配置信息包括以下一种或多种：
SDAP数据包格式配置信息；
PDCP数据包格式配置信息；
RLC数据包格式配置信息；
MAC数据包格式配置信息。
进一步的，所述SDAP数据包格式配置信息可以包括以下一种或多种：启用或禁止使用SDAP封装包头的指示信息；SDAP数据包大小指示信息。
进一步的，所述PDCP数据包格式配置信息可以包括以下一种或多种：PDCP数据包大小指示信息，PDCP序列号配置信息。
进一步的，所述RLC数据包格式配置信息可以包括以下信息：RLC层传输模式信息。
进一步的，所述MAC数据包格式配置信息可以包括以下一种或多种：启用或禁止MAC复用功能的指示信息，MAC数据包大小的指示信息。其中，所述MAC数据包大小可以是特定逻辑信道的MAC subSDU的数据包大小。
另外，SDAP数据包格式配置信息为SDAP层的数据包格式的配置信息，PDCP数据包格式配置信息为PDCP层的数据包格式的配置信息，RLC数据包格式配置信息为RLC层的数据包格式的配置信息，MAC数据包格式配置信息为MAC层的数据包格式的配置信息。
一种实施方式中，所述数据包格式配置信息还可以包括业务标识信息，所述业务标识信息可以包括以下一项或多项：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
需要说明的是，在所述数据包格式配置信息不包含业务标识信息的情况下，可以默认所述数据包格式配置信息可以适用于所述UE的任意业务的数据传输。
另外，UE在接收到所述数据包格式配置信息的情况下，UE的AS可以将所述数据包格式配置信息以及所述数据包格式配置信息关联的目标业务的相关信息通知给高层(例如，应用层)，用以辅助所述高层调整目标业务的编码速率。
(3)：UE接收网络侧设备发送的数据包格式配置信息，基于所述数据包格式配置信息传输目标业务的数据包。
一种实施方式中，如图16所示，所述数据包格式配置信息配置的进行数据传输的数据包格式如下：
对于SDAP层，经UE和网络侧设备协商无SDAP header，SDAP SDU大小固定为30 字节；
对于PDCP层，经UE和网络侧设备协商PDCP SDU固定为30字节，PDCP header占据一字节，PDCP头(header)携带6比特PDCP SN；
对于RLC层，经UE和网络侧设备协商无RLC header，不启用RLC分割功能；
对于MAC层，经UE和网络侧设备协商MAC SDU固定为31字节，MAC启用复用功能，MAC头(header)占据一字节，携带LCID域，MAC子(sub)PDU共32字节。
需要说明的是，相关技术中NR协议栈为灵活地支持各种大小的数据包，各个协议层的数据包格式设计兼容了封装可变大小的数据包的特性。但是，在某些场景下(例如，上行覆盖受限)，这种过于灵活的封装可变大小的数据包的特性会产生大量的头开销，例如，RLC层可能携带分割域，MAC层需要携带数据包长度域等，不利于提高资源利用率。本申请实施例通过UE和网络侧设备协商数据包格式，以实现对目标业务的数据传输使用相同的数据包格式，进而能够减少数据传输所需的头开销。
参见图17，图17是本申请实施例提供的一种信息发送方法的流程图，如图17所示，信息发送方法包括以下步骤：
步骤201、网络侧设备向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
可选地，所述目标配置信息用于配置目标业务的数据包格式。
可选地，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
所述网络侧设备基于如下至少一项配置所述目标配置信息：
所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
所述网络侧设备的负载状况；
所述网络侧设备与所述终端之间的链路状况；
第一指示信息，所述第一指示信息用于配置所述目标配置信息。
可选地，所述目标配置信息基于所述第一指示信息配置，所述网络侧设备为接入网设备，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
所述接入网设备接收核心网设备发送的所述第一指示信息。
可选地，所述第一指示信息用于指示如下任意一项：
业务的编码速率；
所述目标配置信息。
可选地，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
所述网络侧设备接收所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式。
可选地，所述第一协商信息用于协商目标业务的数据包格式。
可选地，所述目标业务通过如下至少一项标识：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
可选地，所述目标配置信息包括如下至少一项：
第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
需要说明的是，本实施例作为与图15所示的实施例中对应的网络侧设备的实施方式，其具体的实施方式可以参见图15所示的实施例的相关说明，为避免重复说明，本实施例不再赘述。这样，终端能够基于网络侧设备发送的目标配置信息，配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
参见图18，图18是本申请实施例提供的一种信息发送方法的流程图，如图18所示，信息发送方法包括以下步骤：
步骤301、核心网设备向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
可选地，所述第一指示信息用于指示如下任意一项：
业务的编码速率；
目标配置信息，所述目标配置信息用于配置数据包格式。
需要说明的是，本实施例作为与图17所示的实施例中对应的核心网设备的实施方式，其具体的实施方式可以参见图17所示的实施例的相关说明，为避免重复说明，本实施例不再赘述。
在本申请实施例中，核心网设备向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。从而接入网设备能够基于第一指示信息为终端配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
本申请实施例提供的数据传输方法，执行主体可以为数据传输装置。本申请实施例中以数据传输装置执行数据传输方法为例，说明本申请实施例提供的数据传输的装置。
请参见图19，图19是本申请实施例提供的一种数据传输装置的结构图，所述数据传输装置应用于终端，如图19所示，数据传输装置400包括：
接收模块401，用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
传输模块402，用于基于所述目标配置信息传输业务数据。
可选地，所述目标配置信息用于配置目标业务的数据包格式；
传输模块402具体用于：
所述终端基于所述目标配置信息传输所述目标业务的业务数据。
可选地，所述目标配置信息基于如下至少一项配置：
所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
所述网络侧设备的负载状况；
所述网络侧设备与所述终端之间的链路状况；
第一指示信息，所述第一指示信息用于配置所述目标配置信息。
可选地，所述装置还包括：
发送模块，用于向所述网络侧设备发送第一协商信息，所述第一协商信息用于协商数据包格式。
可选地，所述第一协商信息用于协商目标业务的数据包格式。
可选地，所述目标业务通过如下至少一项标识：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
可选地，所述目标配置信息包括如下至少一项：
第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
可选地，所述第一配置信息包括如下至少一项：
第二指示信息，所述第二指示信息用于指示启用或禁用SDAP封装包头；
第三指示信息，所述第三指示信息用于指示SDAP数据包大小；
所述第二配置信息包括如下至少一项：
第四指示信息，所述第四指示信息用于指示PDCP数据包大小；
PDCP序列号配置信息；
所述第三配置信息包括：
第五指示信息，所述第五指示信息用于指示RLC层传输模式；
所述第四配置信息包括如下至少一项：
第六指示信息，所述第六指示信息用于指示启用或禁用MAC复用功能；
第七指示信息，所述第七指示信息用于指示MAC数据包大小。
可选地，所述发送模块具体用于：
所述终端基于业务的编码速率向所述网络侧设备发送第一协商信息。
可选地，所述第一协商信息用于协商如下至少一项数据包的数据包格式：
SDAP数据包；
PDCP数据包；
RLC数据包；
MAC数据包。
可选地，在所述第一协商信息用于协商SDAP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
SDAP子头协商信息；
SDAP数据包大小协商信息。
可选地，所述SDAP子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置SDAP子头；所述终端建议或不建议配置SDAP子头；所述终端支持或不支持配置SDAP子头；
所述SDAP数据包大小协商信息用于指示如下任意一项：
所述终端期望的SDAP数据包大小；所述终端支持的SDAP数据包大小；所述终端建议的SDAP数据包大小。
可选地，在所述第一协商信息用于协商PDCP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
PDCP序列号协商信息；
PDCP数据包大小协商信息。
可选地，所述PDCP序列号协商信息用于指示如下任意一项：
所述终端期望配置的PDCP序列号长度；所述终端建议配置的PDCP序列号长度；所述终端支持配置的PDCP序列号长度；
所述PDCP数据包大小协商信息用于协商如下至少一项：
在启用数据包级联功能的情况下的级联PDCP数据包大小；
在禁用数据包级联功能的情况下的PDCP数据包大小。
可选地，在所述第一协商信息用于协商RLC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
RLC子头协商信息；
RLC序列号协商信息；
RLC数据包大小协商信息；
RLC分段功能协商信息。
可选地，所述RLC子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置RLC子头；所述终端建议或不建议配置RLC子头；
所述RLC序列号协商信息用于指示如下任意一项：
所述终端期望配置的RLC序列号；所述终端建议配置的RLC序列号；
所述RLC数据包大小协商信息用于指示如下任意一项：
所述终端期望的RLC数据包大小；所述终端支持的RLC数据包大小；所述终端建议的RLC数据包大小；
所述RLC分段功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用分段功能；所述终端建议启用或建议禁用分段功能。
可选地，在所述第一协商信息用于协商MAC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
MAC复用功能协商信息；
MAC数据包大小协商信息。
可选地，所述MAC复用功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用复用功能；所述终端建议或不建议启用复用功能；
所述MAC数据包大小协商信息用于指示如下任意一项：
所述终端期望的MAC数据包大小；所述终端支持的MAC数据包大小；所述终端建议的MAC数据包大小。
可选地，SDAP数据包大小包括如下至少一项：SDAP服务数据单元SDU数据包大小；SDAP协议数据单元PDU数据包大小；
PDCP数据包大小包括如下至少一项：PDCP SDU数据包大小；PDCP PDU数据包大小；
RLC数据包大小包括如下至少一项：RLC SDU数据包大小；RLC PDU数据包大小；
MAC数据包大小包括如下至少一项：MAC SDU数据包大小；MAC PDU数据包大小。
可选地，传输模块402具体用于：
基于所述目标配置信息封装业务数据；
传输封装后的业务数据。
本申请实施例中的数据传输装置，能够基于网络侧设备发送的目标配置信息，配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
本申请实施例中的数据传输装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的数据传输装置能够实现图15的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图20，图20是本申请实施例提供的一种信息发送装置的结构图，所述信息发送装置应用于网络侧设备，如图20所示，信息发送装置500包括：
发送模块501，用于向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
可选地，所述目标配置信息用于配置目标业务的数据包格式。
可选地，所述装置还包括：
配置模块，用于基于如下至少一项配置所述目标配置信息：
所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
所述网络侧设备的负载状况；
所述网络侧设备与所述终端之间的链路状况；
第一指示信息，所述第一指示信息用于配置所述目标配置信息。
可选地，所述目标配置信息基于所述第一指示信息配置，所述网络侧设备为接入网设备，所述装置还包括：
第一接收模块，用于接收核心网设备发送的所述第一指示信息。
可选地，所述第一指示信息用于指示如下任意一项：
业务的编码速率；
所述目标配置信息。
可选地，所述装置还包括：
第二接收模块，用于接收所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式。
可选地，所述第一协商信息用于协商目标业务的数据包格式。
可选地，所述目标业务通过如下至少一项标识：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
可选地，所述目标配置信息包括如下至少一项：
第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
本申请实施例中的信息发送装置，通过向终端发送目标配置信息，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
本申请实施例中的信息发送装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的信息发送装置能够实现图17的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图21，图21是本申请实施例提供的一种信息发送装置的结构图，所述信息发送装置应用于核心网设备，如图21所示，信息发送装置600包括：
发送模块601，用于向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
可选地，所述第一指示信息用于指示如下任意一项：
业务的编码速率；
目标配置信息，所述目标配置信息用于配置数据包格式。
本申请实施例中的信息发送装置，通过向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。从而接入网设备能够基于第一指示信息为终端配置进行业务数据传输的数据包格式，使得终端在进行业务数据传输时能够使用较为固定的数据包格式，从而能够降低数据包头开销，提高资源利用率。
本申请实施例中的信息发送装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的信息发送装置能够实现图18的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选地，如图22所示，本申请实施例还提供一种通信设备700，包括处理器701和存储器702，存储器702上存储有可在所述处理器701上运行的程序或指令，例如，该通信设备700为终端时，该程序或指令被处理器701执行时实现上述数据传输方法实施例的各个步骤，且能达到相同的技术效果。该通信设备700为网络侧设备时，该程序或指令被处理器701执行时实现上述信息发送方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，通信接口用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；处理器用于基于所述目标配置信息传输业务数据。该终端实施例与上述数据传输方法实施例对应，上述数据传输方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图23为实现本申请实施例的一种终端的硬件结构示意图。
该终端800包括但不限于：射频单元801、网络模块802、音频输出单元803、输入单元804、传感器805、显示单元806、用户输入单元807、接口单元808、存储器809以及处理器810等中的至少部分部件。
本领域技术人员可以理解，终端800还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器810逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图23中示出的终端结构并不构成对终端的限定，终端可以 包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元804可以包括图形处理单元(Graphics Processing Unit，GPU)8041和麦克风8042，图形处理器8041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元806可包括显示面板8061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板8061。用户输入单元807包括触控面板8071以及其他输入设备8072中的至少一种。触控面板8071，也称为触摸屏。触控面板8071可包括触摸检测装置和触摸控制器两个部分。其他输入设备8072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元801接收来自网络侧设备的下行数据后，可以传输给处理器810进行处理；另外，射频单元801可以向网络侧设备发送上行数据。通常，射频单元801包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器809可用于存储软件程序或指令以及各种数据。存储器809可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器809可以包括易失性存储器或非易失性存储器，或者，存储器809可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器809包括但不限于这些和任意其它适合类型的存储器。
处理器810可包括一个或多个处理单元；可选的，处理器810集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器810中。
其中，射频单元801，用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
处理器810，用于基于所述目标配置信息传输业务数据。
可选地，所述目标配置信息用于配置目标业务的数据包格式；
处理器810，用于基于所述目标配置信息传输所述目标业务的业务数据。
可选地，所述目标配置信息基于如下至少一项配置：
所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
所述网络侧设备的负载状况；
所述网络侧设备与所述终端之间的链路状况；
第一指示信息，所述第一指示信息用于配置所述目标配置信息。
可选地，射频单元801，还用于向所述网络侧设备发送第一协商信息，所述第一协商信息用于协商数据包格式。
可选地，所述第一协商信息用于协商目标业务的数据包格式。
可选地，所述目标业务通过如下至少一项标识：
会话标识信息；
承载标识信息；
逻辑信道标识信息。
可选地，所述目标配置信息包括如下至少一项：
第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
可选地，所述第一配置信息包括如下至少一项：
第二指示信息，所述第二指示信息用于指示启用或禁用SDAP封装包头；
第三指示信息，所述第三指示信息用于指示SDAP数据包大小；
所述第二配置信息包括如下至少一项：
第四指示信息，所述第四指示信息用于指示PDCP数据包大小；
PDCP序列号配置信息；
所述第三配置信息包括：
第五指示信息，所述第五指示信息用于指示RLC层传输模式；
所述第四配置信息包括如下至少一项：
第六指示信息，所述第六指示信息用于指示启用或禁用MAC复用功能；
第七指示信息，所述第七指示信息用于指示MAC数据包大小。
可选地，射频单元801还用于：
基于业务的编码速率向所述网络侧设备发送第一协商信息。
可选地，所述第一协商信息用于协商如下至少一项数据包的数据包格式：
SDAP数据包；
PDCP数据包；
RLC数据包；
MAC数据包。
可选地，在所述第一协商信息用于协商SDAP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
SDAP子头协商信息；
SDAP数据包大小协商信息。
可选地，所述SDAP子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置SDAP子头；所述终端建议或不建议配置SDAP子头；所述终端支持或不支持配置SDAP子头；
所述SDAP数据包大小协商信息用于指示如下任意一项：
所述终端期望的SDAP数据包大小；所述终端支持的SDAP数据包大小；所述终端建议的SDAP数据包大小。
可选地，在所述第一协商信息用于协商PDCP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
PDCP序列号协商信息；
PDCP数据包大小协商信息。
可选地，所述PDCP序列号协商信息用于指示如下任意一项：
所述终端期望配置的PDCP序列号长度；所述终端建议配置的PDCP序列号长度；所述终端支持配置的PDCP序列号长度；
所述PDCP数据包大小协商信息用于协商如下至少一项：
在启用数据包级联功能的情况下的级联PDCP数据包大小；
在禁用数据包级联功能的情况下的PDCP数据包大小。
可选地，在所述第一协商信息用于协商RLC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
RLC子头协商信息；
RLC序列号协商信息；
RLC数据包大小协商信息；
RLC分段功能协商信息。
可选地，所述RLC子头协商信息用于指示如下任意一项：
所述终端期望或不期望配置RLC子头；所述终端建议或不建议配置RLC子头；
所述RLC序列号协商信息用于指示如下任意一项：
所述终端期望配置的RLC序列号；所述终端建议配置的RLC序列号；
所述RLC数据包大小协商信息用于指示如下任意一项：
所述终端期望的RLC数据包大小；所述终端支持的RLC数据包大小；所述终端建议的RLC数据包大小；
所述RLC分段功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用分段功能；所述终端建议启用或建议禁用分段功能。
可选地，在所述第一协商信息用于协商MAC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
MAC复用功能协商信息；
MAC数据包大小协商信息。
可选地，所述MAC复用功能协商信息用于指示如下任意一项：
所述终端期望或不期望启用复用功能；所述终端建议或不建议启用复用功能；
所述MAC数据包大小协商信息用于指示如下任意一项：
所述终端期望的MAC数据包大小；所述终端支持的MAC数据包大小；所述终端建议的MAC数据包大小。
可选地，SDAP数据包大小包括如下至少一项：SDAP服务数据单元SDU数据包大小；SDAP协议数据单元PDU数据包大小；
PDCP数据包大小包括如下至少一项：PDCP SDU数据包大小；PDCP PDU数据包大小；
RLC数据包大小包括如下至少一项：RLC SDU数据包大小；RLC PDU数据包大小；
MAC数据包大小包括如下至少一项：MAC SDU数据包大小；MAC PDU数据包大小。
可选地，处理器810还用于：
基于所述目标配置信息封装业务数据；
传输封装后的业务数据。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口用于：向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。该网络侧设备实施例与上述信息发送方法实施例对应，上述信息发送方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图24所示，该网络侧设备900包括：天线901、射频装置902、基带装置903、处理器904和存储器905。天线901与射频装置902连接。在上行方向上，射频装置902通过天线901接收信息，将接收的信息发送给基带装置903进行处理。在下行方向上，基带装置903对要发送的信息进行处理，并发送给射频装置902，射频装置902对收到的信息进行处理后经过天线901发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置903中实现，该基带装置903包括基带处理器。
基带装置903例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图24所示，其中一个芯片例如为基带处理器，通过总线接口与存储器905连接，以调用存储器905中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口906，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备900还包括：存储在存储器905上并可在处理器 904上运行的指令或程序，处理器904调用存储器905中的指令或程序执行图20所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
具体地，本申请实施例还提供了一种核心网设备。如图25所示，该核心网设备1000包括：处理器1001、网络接口1002和存储器1003。其中，网络接口1002例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的核心网设备1000还包括：存储在存储器1003上并可在处理器1001上运行的指令或程序，处理器1001调用存储器1003中的指令或程序执行图21所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述数据传输方法或信息发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述数据传输方法或信息发送方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述数据传输方法或信息发送方法的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种数据传输系统，包括：终端及网络侧设备，所述终端可用于执行如上所述的数据传输方法的步骤，所述网络侧设备可用于执行如上所述的信息发送方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可 借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (38)

  1. 一种数据传输方法，包括：
    终端接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
    所述终端基于所述目标配置信息传输业务数据。
  2. 根据权利要求1所述的方法，其中，所述目标配置信息用于配置目标业务的数据包格式；
    所述终端基于所述目标配置信息传输业务数据，包括：
    所述终端基于所述目标配置信息传输所述目标业务的业务数据。
  3. 根据权利要求1所述的方法，其中，所述目标配置信息基于如下至少一项配置：
    所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
    所述网络侧设备的负载状况；
    所述网络侧设备与所述终端之间的链路状况；
    第一指示信息，所述第一指示信息用于配置所述目标配置信息。
  4. 根据权利要求1所述的方法，其中，所述终端接收网络侧设备发送的目标配置信息之前，所述方法还包括：
    所述终端向所述网络侧设备发送第一协商信息，所述第一协商信息用于协商数据包格式。
  5. 根据权利要求4所述的方法，其中，所述第一协商信息用于协商目标业务的数据包格式。
  6. 根据权利要求2或5所述的方法，其中，所述目标业务通过如下至少一项标识：
    会话标识信息；
    承载标识信息；
    逻辑信道标识信息。
  7. 根据权利要求1至5中任一项所述的方法，其中，所述目标配置信息包括如下至少一项：
    第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
    第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
    第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
    第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
  8. 根据权利要求7所述的方法，其中，所述第一配置信息包括如下至少一项：
    第二指示信息，所述第二指示信息用于指示启用或禁用SDAP封装包头；
    第三指示信息，所述第三指示信息用于指示SDAP数据包大小；
    所述第二配置信息包括如下至少一项：
    第四指示信息，所述第四指示信息用于指示PDCP数据包大小；
    PDCP序列号配置信息；
    所述第三配置信息包括：
    第五指示信息，所述第五指示信息用于指示RLC层传输模式；
    所述第四配置信息包括如下至少一项：
    第六指示信息，所述第六指示信息用于指示启用或禁用MAC复用功能；
    第七指示信息，所述第七指示信息用于指示MAC数据包大小。
  9. 根据权利要求4所述的方法，其中，所述终端向所述网络侧设备发送第一协商信息，包括：
    所述终端基于业务的编码速率向所述网络侧设备发送第一协商信息。
  10. 根据权利要求4或9所述的方法，其中，所述第一协商信息用于协商如下至少一项数据包的数据包格式：
    SDAP数据包；
    PDCP数据包；
    RLC数据包；
    MAC数据包。
  11. 根据权利要求10所述的方法，其中，在所述第一协商信息用于协商SDAP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
    SDAP子头协商信息；
    SDAP数据包大小协商信息。
  12. 根据权利要求11所述的方法，其中，所述SDAP子头协商信息用于指示如下任意一项：
    所述终端期望或不期望配置SDAP子头；所述终端建议或不建议配置SDAP子头；所述终端支持或不支持配置SDAP子头；
    所述SDAP数据包大小协商信息用于指示如下任意一项：
    所述终端期望的SDAP数据包大小；所述终端支持的SDAP数据包大小；所述终端建议的SDAP数据包大小。
  13. 根据权利要求10所述的方法，其中，在所述第一协商信息用于协商PDCP数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
    PDCP序列号协商信息；
    PDCP数据包大小协商信息。
  14. 根据权利要求13所述的方法，其中，所述PDCP序列号协商信息用于指示如下任意一项：
    所述终端期望配置的PDCP序列号长度；所述终端建议配置的PDCP序列号长度；所述终端支持配置的PDCP序列号长度；
    所述PDCP数据包大小协商信息用于协商如下至少一项：
    在启用数据包级联功能的情况下的级联PDCP数据包大小；
    在禁用数据包级联功能的情况下的PDCP数据包大小。
  15. 根据权利要求10所述的方法，其中，在所述第一协商信息用于协商RLC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
    RLC子头协商信息；
    RLC序列号协商信息；
    RLC数据包大小协商信息；
    RLC分段功能协商信息。
  16. 根据权利要求15所述的方法，其中，所述RLC子头协商信息用于指示如下任意一项：
    所述终端期望或不期望配置RLC子头；所述终端建议或不建议配置RLC子头；
    所述RLC序列号协商信息用于指示如下任意一项：
    所述终端期望配置的RLC序列号；所述终端建议配置的RLC序列号；
    所述RLC数据包大小协商信息用于指示如下任意一项：
    所述终端期望的RLC数据包大小；所述终端支持的RLC数据包大小；所述终端建议的RLC数据包大小；
    所述RLC分段功能协商信息用于指示如下任意一项：
    所述终端期望或不期望启用分段功能；所述终端建议启用或建议禁用分段功能。
  17. 根据权利要求10所述的方法，其中，在所述第一协商信息用于协商MAC数据包的数据包格式的情况下，所述第一协商信息包括如下至少一项：
    MAC复用功能协商信息；
    MAC数据包大小协商信息。
  18. 根据权利要求17所述的方法，其中，所述MAC复用功能协商信息用于指示如下任意一项：
    所述终端期望或不期望启用复用功能；所述终端建议或不建议启用复用功能；
    所述MAC数据包大小协商信息用于指示如下任意一项：
    所述终端期望的MAC数据包大小；所述终端支持的MAC数据包大小；所述终端建议的MAC数据包大小。
  19. 根据权利要求8或11或13或15或17所述的方法，其中，SDAP数据包大小包括如下至少一项：SDAP服务数据单元SDU数据包大小；SDAP协议数据单元PDU数据包大小；
    PDCP数据包大小包括如下至少一项：PDCP SDU数据包大小；PDCP PDU数据包大小；
    RLC数据包大小包括如下至少一项：RLC SDU数据包大小；RLC PDU数据包大小；
    MAC数据包大小包括如下至少一项：MAC SDU数据包大小；MAC PDU数据包大小。
  20. 根据权利要求1至5中任一项所述的方法，其中，所述终端基于所述目标配置信息传输业务数据，包括：
    所述终端基于所述目标配置信息封装业务数据；
    所述终端传输封装后的业务数据。
  21. 一种信息发送方法，包括：
    网络侧设备向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
  22. 根据权利要求21所述的方法，其中，所述目标配置信息用于配置目标业务的数据包格式。
  23. 根据权利要求21所述的方法，其中，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
    所述网络侧设备基于如下至少一项配置所述目标配置信息：
    所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式；
    所述网络侧设备的负载状况；
    所述网络侧设备与所述终端之间的链路状况；
    第一指示信息，所述第一指示信息用于配置所述目标配置信息。
  24. 根据权利要求23所述的方法，其中，所述目标配置信息基于所述第一指示信息配置，所述网络侧设备为接入网设备，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
    所述接入网设备接收核心网设备发送的所述第一指示信息。
  25. 根据权利要求23所述的方法，其中，所述第一指示信息用于指示如下任意一项：
    业务的编码速率；
    所述目标配置信息。
  26. 根据权利要求21所述的方法，其中，所述网络侧设备向终端发送目标配置信息之前，所述方法还包括：
    所述网络侧设备接收所述终端发送的第一协商信息，所述第一协商信息用于协商数据包格式。
  27. 根据权利要求26所述的方法，其中，所述第一协商信息用于协商目标业务的数据包格式。
  28. 根据权利要求22或27所述的方法，其中，所述目标业务通过如下至少一项标识：
    会话标识信息；
    承载标识信息；
    逻辑信道标识信息。
  29. 根据权利要求21至27中任一项所述的方法，其中，所述目标配置信息包括如下至少一项：
    第一配置信息，用于配置服务数据适应协议SDAP数据包的数据包格式；
    第二配置信息，用于配置分组数据汇聚协议PDCP数据包的数据包格式；
    第三配置信息，用于配置无线链路控制RLC数据包的数据包格式；
    第四配置信息，用于配置媒体接入控制MAC数据包的数据包格式。
  30. 一种信息发送方法，包括：
    核心网设备向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
  31. 根据权利要求30所述的方法，其中，所述第一指示信息用于指示如下任意一项：
    业务的编码速率；
    目标配置信息，所述目标配置信息用于配置数据包格式。
  32. 一种数据传输装置，终端包括所述数据传输装置，包括：
    接收模块，用于接收网络侧设备发送的目标配置信息，所述目标配置信息用于配置数据包格式；
    传输模块，用于基于所述目标配置信息传输业务数据。
  33. 一种信息发送装置，网络侧设备包括所述信息发送装置，包括：
    发送模块，用于向终端发送目标配置信息，所述目标配置信息用于配置数据包格式。
  34. 一种信息发送装置，核心网设备包括所述信息发送装置，包括：
    发送模块，用于向接入网设备发送第一指示信息，所述第一指示信息用于辅助所述接入网设备配置数据包格式。
  35. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至20任一项所述的数据传输方法的步骤。
  36. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求21至29任一项所述的信息发送方法的步骤。
  37. 一种核心网设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求30至31任一项所述的信息发送方法的步骤。
  38. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至20任一项所述的数据传输方法的步骤，或者实现如权利要求21至29任一项所述的信息发送方法的步骤，或者实现如权利要求30至31任一项所述的信息发送方法的步骤。
PCT/CN2023/092429 2022-05-09 2023-05-06 数据传输方法、信息发送方法、终端及网络侧设备 WO2023217012A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210501989.9 2022-05-09
CN202210501989.9A CN117082565A (zh) 2022-05-09 2022-05-09 数据传输方法、信息发送方法、终端及网络侧设备

Publications (1)

Publication Number Publication Date
WO2023217012A1 true WO2023217012A1 (zh) 2023-11-16

Family

ID=88710267

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/092429 WO2023217012A1 (zh) 2022-05-09 2023-05-06 数据传输方法、信息发送方法、终端及网络侧设备

Country Status (2)

Country Link
CN (1) CN117082565A (zh)
WO (1) WO2023217012A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972282A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 用于以太网数据的通信方法和装置
CN111148153A (zh) * 2018-11-02 2020-05-12 电信科学技术研究院有限公司 数据包发送方法、接收方法和设备
US20210014848A1 (en) * 2019-10-04 2021-01-14 Alexei Davydov Ue configured for joint activation of tci states and spatial relation info on multiple component carriers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110972282A (zh) * 2018-09-28 2020-04-07 华为技术有限公司 用于以太网数据的通信方法和装置
CN111148153A (zh) * 2018-11-02 2020-05-12 电信科学技术研究院有限公司 数据包发送方法、接收方法和设备
US20210014848A1 (en) * 2019-10-04 2021-01-14 Alexei Davydov Ue configured for joint activation of tci states and spatial relation info on multiple component carriers

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "TS38.423 pCR on Configuring Index to RFSP info During Xn Mobility", 3GPP TSG RAN WG3#100, R3-182634, 20 May 2018 (2018-05-20), XP051445137 *

Also Published As

Publication number Publication date
CN117082565A (zh) 2023-11-17

Similar Documents

Publication Publication Date Title
WO2018227555A1 (zh) 用于传输数据的方法、终端设备和网络设备
WO2021057692A1 (zh) 非接入层消息传输的方法、装置和系统
JP2023547257A (ja) Ｐｄｃｐ重複の配置、アクティブ化又は非アクティブ化方法と端末
US20230224785A1 (en) Service data transmission method and apparatus, terminal device, and network device
WO2023217012A1 (zh) 数据传输方法、信息发送方法、终端及网络侧设备
KR20210015101A (ko) 듀얼 커넥티비티를 지원하는 전자 장치 및 그 동작 방법
WO2019127289A1 (zh) 传输数据的方法和终端设备
WO2021062809A1 (zh) 一种时刻信息的通知方法和装置
EP4068842A1 (en) Communication method and apparatus
WO2024012279A1 (zh) 信息传输方法、装置及设备
WO2023030329A1 (zh) 数据传输方法和设备
CN114650508A (zh) 服务更新处理方法及设备
WO2023179728A1 (zh) 通信系统的数据传输方法、终端及网络侧设备
KR20210041766A (ko) 스플릿 베어러를 이용하여 데이터를 수신하는 전자 장치 및 전자 장치의 동작 방법
JP2008148314A (ja) 無線通信システムにおいてリオーダーを処理する方法及び装置
KR20200132617A (ko) 듀얼 커넥티비티를 지원하는 전자 장치 및 그 동작 방법
WO2023217089A1 (zh) 数据传输方法、装置、设备、系统及存储介质
WO2023208048A1 (zh) 小区切换方法、装置、终端及网络侧设备
WO2024078456A1 (zh) 上行控制信息传输方法、装置及终端
WO2023143450A1 (zh) 数据处理规则的配置方法、终端及网络侧设备
WO2023185756A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2024093712A1 (zh) 中继通信链路处理方法、中继通信链路配置方法、中继终端处理方法及相关设备
WO2023208142A1 (zh) 数据的处理方法及通信设备
WO2023217009A1 (zh) 数据传输方法、装置及通信设备
WO2023001173A1 (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: 23802784

Country of ref document: EP

Kind code of ref document: A1