CN117082565A

CN117082565A - Data transmission method, information transmission method, terminal and network side equipment

Info

Publication number: CN117082565A
Application number: CN202210501989.9A
Authority: CN
Inventors: 张艳霞; 杨晓东
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-05-09
Filing date: 2022-05-09
Publication date: 2023-11-17
Also published as: WO2023217012A1

Abstract

The application discloses a data transmission method, an information sending method, a terminal and network side equipment, which belong to the technical field of communication, and the data transmission method of the embodiment of the application comprises the following steps: the method comprises the steps that a terminal receives target configuration information sent by network side equipment, wherein the target configuration information is used for configuring a data packet format; and the terminal transmits service data based on the target configuration information.

Description

Data transmission method, information transmission method, terminal and network side equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a data transmission method, an information sending method, a terminal and network side equipment.

Background

When the terminal encapsulates the data packet, the data packet is encapsulated according to an encapsulation rule, and each protocol layer is associated with an encapsulation packet header of the protocol layer when the data packet is encapsulated. The encapsulation rule in the related art needs to have the characteristic of being compatible with encapsulating variable-size data packets, and the variable-size data packet formats may be different, so that the data packet heads of different data packet formats are different, a large amount of data packet head overhead is generated when the data packet is encapsulated according to the predefined encapsulation rule, and the resource utilization rate is low.

Disclosure of Invention

The embodiment of the application provides a data transmission method, an information transmission method, a terminal and network side equipment, which can solve the problem of low resource utilization rate.

In a first aspect, a data transmission method is provided, including:

the method comprises the steps that a terminal receives target configuration information sent by network side equipment, wherein the target configuration information is used for configuring a data packet format;

and the terminal transmits service data based on the target configuration information.

In a second aspect, there is provided an information transmission method including:

and the network side equipment sends target configuration information to the terminal, wherein the target configuration information is used for configuring the data packet format.

In a third aspect, there is provided an information transmission method, including:

the method comprises the steps that core network equipment sends first indication information to access network equipment, wherein the first indication information is used for assisting the access network equipment to configure a data packet format.

In a fourth aspect, there is provided a data transmission apparatus, a terminal including the data transmission apparatus, the data transmission apparatus including:

the receiving module is used for receiving target configuration information sent by the network side equipment, wherein the target configuration information is used for configuring a data packet format;

and the transmission module is used for transmitting service data based on the target configuration information.

In a fifth aspect, there is provided an information transmission apparatus, a network-side device including the information transmission apparatus, the information transmission apparatus including:

the sending module is used for sending target configuration information to the terminal, wherein the target configuration information is used for configuring the data packet format.

In a sixth aspect, there is provided an information transmission apparatus, a core network device including the information transmission apparatus, the information transmission apparatus including:

the sending module is used for sending first indication information to the access network equipment, wherein the first indication information is used for assisting the access network equipment to configure a data packet format.

In a seventh aspect, there is provided a terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the first aspect.

An eighth aspect provides a terminal, including a processor and a communication interface, where the communication interface is configured to receive target configuration information sent by a network side device, where the target configuration information is used to configure a data packet format; the processor is configured to transmit traffic data based on the target configuration information.

In a ninth aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the second aspect.

In a tenth aspect, a network side device is provided, including a processor and a communication interface, where the communication interface is configured to send target configuration information to a terminal, where the target configuration information is used to configure a data packet format.

In an eleventh aspect, there is provided a core network device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method according to the third aspect.

In a twelfth aspect, there is provided a data transmission system comprising: a terminal and a network side device, the terminal being operable to perform the steps of the data transmission method according to the first aspect, the network side device being operable to perform the steps of the information transmission method according to the second or third aspect.

In a thirteenth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect, or performs the steps of the method according to the second aspect, or performs the steps of the method according to the third aspect.

In a fourteenth aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being for running a program or instructions to implement the method according to the first aspect, or to implement the method according to the second aspect, or to implement the method according to the third aspect.

In a fourteenth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to perform the steps of the method as described in the first aspect or to perform the steps of the method as described in the second aspect, the steps of the method as described in the third aspect.

In the embodiment of the application, a terminal receives target configuration information sent by network side equipment, wherein the target configuration information is used for configuring a data packet format; and the terminal transmits service data based on the target configuration information. Therefore, the terminal can configure the data packet format for service data transmission based on the target configuration information sent by the network side equipment, so that the terminal can use a relatively fixed data packet format when transmitting service data, thereby reducing the data packet header overhead and improving the resource utilization rate.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

fig. 2 is a diagram of an NR UP protocol architecture provided by an embodiment of the present application;

fig. 3 is a schematic diagram of an SDAP packet format according to an embodiment of the present application;

FIG. 4 is a schematic diagram of another SDAP packet format provided by an embodiment of the present application;

fig. 5 is a schematic diagram of a PDCP packet format according to an embodiment of the present application;

FIG. 6 is a diagram illustrating another PDCP packet format provided by an embodiment of the present application;

fig. 7 is a schematic diagram of an RLC packet format according to an embodiment of the present application;

fig. 8 is a schematic diagram of another RLC packet format provided by an embodiment of the present application;

fig. 9 is a schematic diagram of a MAC packet format according to an embodiment of the present application;

fig. 10 is a schematic diagram of another MAC packet format according to an embodiment of the present application;

FIG. 11 is a schematic diagram of another MAC packet format provided by an embodiment of the present application;

fig. 12 is a schematic diagram of another MAC packet format according to an embodiment of the present application;

fig. 13 is a schematic diagram of another MAC packet format according to an embodiment of the present application;

fig. 14 is a schematic diagram of another MAC packet format according to an embodiment of the present application;

Fig. 15 is a flowchart of a data transmission method according to an embodiment of the present application;

fig. 16 is a schematic diagram of a configuration of a data packet format according to an embodiment of the present application;

fig. 17 is a flowchart of an information sending method provided in an embodiment of the present application;

fig. 18 is a flowchart of another information transmission method according to an embodiment of the present application;

fig. 19 is a block diagram of a data transmission device according to an embodiment of the present application;

fig. 20 is a block diagram of an information transmitting apparatus according to an embodiment of the present application;

fig. 21 is a block diagram of another information transmitting apparatus provided in an embodiment of the present application;

fig. 22 is a block diagram of a communication device according to an embodiment of the present application;

fig. 23 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 24 is a schematic structural diagram of a network side device according to an embodiment of the present application;

fig. 25 is a schematic structural diagram of a core network device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example, and NR terminology is used in much of the description below, but these techniques are also applicable to N Applications other than R-system applications, e.g. generation 6 (6 ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only a base station in the NR system is described as an example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

In order to facilitate a better understanding of the embodiments of the present invention, the following technical points are first described.

Regarding NR User Plane (UP) protocol stacks:

the NR UP protocol architecture diagram is shown in fig. 2, and is composed of a service data adaptation protocol (Service Data Adaptation Protocol, SDAP), a packet data convergence protocol (Packet Data Convergence Protocol, PDCP), a radio link control (Radio Link Control, RLC), a medium access control (Medium Access Control, MAC), and a Physical Layer (PHY).

For SDAP:

the SDAP is mainly responsible for mapping management of quality of service (Quality of Service, qoS) flows (flows) and data radio bearers (Data Radio Bearer, DRB);

wherein, the SDAP header (header) corresponding to the Uplink (UL) and Downlink (DL) packets is configurable. If so, the corresponding SDAP header occupies one byte. The SDAP layer packet format may be as shown in FIGS. 3 and 4, and is mainly used to carry QoS flow identifiers (QoS Flow Identifier, QFI). Data is a Data area.

For PDCP:

the PDCP is mainly responsible for header compression and/or decompression, encryption and/or decryption, integrity protection and/or integrity verification, data replication and/or duplicate detection, reordering, PDCP retransmission and other processes;

PDCP packets (i.e., PDCP data PDUs) carry PDCP headers that mainly carry PDCP Sequence Numbers (SNs), for service data, PDCP SNs of 12 or 18 bits may be used, occupying 2 or 3 bytes, respectively, depending on network side configuration. The PDCP layer packet format is shown in fig. 5 and 6. Fig. 5 is a PDCP layer packet format using a PDCP SN of 12 bits. Fig. 6 is a PDCP layer packet format using a PDCP SN of 18 bits. Optionally, the Optional token, the cont token.

For RLC:

RLC is mainly responsible for data segmentation and/or reassembly, automatic repeat request (ARQ, automatic Repeat request) and/or repetition detection and/or re-segmentation (applicable to acknowledged mode), etc.

RLC has three transmission modes, transparent Mode (TM), unacknowledged Mode (Unacknowledged Mode, UM) and acknowledged Mode (Acknowledged Mode, AM), with different transmission modes having different packet formats. The TM does not need to carry RLC header, and is usually used for signaling carried by system messages, paging messages, and SRB0, and is not used for transmitting service data. The AM carries an RLC header, which must carry an RLC SN, which may be a 12-bit or 18-bit RLC SN. UM carries one byte of RLC header when the carried data packet is a complete data packet (i.e. the data packet is not segmented), the RLC header does not need to carry RLC SN, otherwise the RLC header needs to carry RLC SN, and the carried RLC SN can be 6 bits or 12 bits of RLC SN. Because AM and UM support packet segmentation and/or reassembly, the packet format is relatively complex, and RLC header needs to carry segmentation information, such as SI field and SO field, in order for the receiving end to reassemble the packet. A partial RLC layer packet format is shown in fig. 7 and 8. Fig. 7 is a UDM PDU packet format carrying 12 bits RLC SN and SO fields. Fig. 8 is an AMD PDU packet format carrying 18-bit RLC SN and SO fields.

For MAC:

the MAC layer is mainly responsible for data multiplexing and/or demultiplexing, hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ), resource scheduling, etc.

The MAC layer can transmit data packets transparently, i.e. does not carry MAC headers, but is mainly applicable to paging messages and system message transmission. Other cases need to carry a MAC header. Since the MAC layer has data multiplexing and/or demultiplexing functions, there is a corresponding MAC subheader for each MAC subPDU for carrying a logical channel identification (Logical Channel Identity, LCID) for identifying the data source. In addition, an L field is carried to indicate the length of the MAC sdu. Fig. 9 to 11 show the MAC layer packet format of the 8-bit L-field carried by the MAC subheader. Fig. 12 to 14 show the MAC layer packet format of the 16-bit L-field carried by the MAC subheader.

The data transmission method, the information transmission method, the terminal and the network side device provided by the embodiment of the application are described in detail below through some embodiments and application scenes thereof with reference to the accompanying drawings.

Referring to fig. 15, fig. 15 is a flowchart of a data transmission method according to an embodiment of the present application, and as shown in fig. 15, the data transmission method includes the following steps:

Step 101, a terminal receives target configuration information sent by network side equipment, wherein the target configuration information is used for configuring a data packet format;

and 102, the terminal transmits service data based on the target configuration information.

Wherein, the target configuration information may be packet format configuration information.

In addition, the terminal can send first negotiation information to the network side device, wherein the first negotiation information is used for negotiating a data packet format, so that the network side device can send target configuration information to the terminal based on the first negotiation information sent by the terminal; or the terminal may receive the target configuration information actively sent by the network side device, where the network side device may actively send the target configuration information to the terminal based on at least one of a load condition of the network side device, a link condition between the network side device and the terminal, and first indication information, where the first indication information may be used to assist the network side device in configuring the target configuration information.

It should be noted that, the target configuration information may be used to configure a packet format of the target service, and for example, the target configuration information may carry service identification information of the target service, where the service identification information may be at least one of session identification information, bearer identification information, and logical channel identification information; alternatively, the target configuration information may be used to configure a data packet format of all services, for example, the target configuration information may not carry service identification information, so that the data packet format configured by the target configuration information may be suitable for data transmission of any service of the terminal.

In addition, the target configuration information may be used to configure a packet format of each protocol layer of the NR protocol stack, and in an embodiment, the target configuration information may be used to configure a packet format of at least one protocol layer of the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer. For example, the target configuration information may be used to configure packet formats of the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer.

It should be noted that, in the related art, the packet format design of each protocol layer of the NR protocol stack is compatible with the feature of encapsulating variable-size packets. However, in some scenarios (e.g., limited uplink coverage), this feature of encapsulating variable-size packets that is too flexible may generate a significant amount of overhead, e.g., the RLC layer may carry split domains, the MAC layer needs to carry packet length domains, etc., which is detrimental to improving resource utilization. According to the embodiment of the application, the data packet format is configured through the target configuration information sent by the network side equipment, the service data is encapsulated by adopting the configured data packet format, the same data packet format can be used for data transmission of a certain or all services, and further the header overhead required by the data transmission can be reduced.

Optionally, the target configuration information is used for configuring a data packet format of the target service;

the terminal transmits service data based on the target configuration information, and the method comprises the following steps:

and the terminal transmits service data of the target service based on the target configuration information.

The target configuration information may carry service identification information of the target service; or, the target configuration information may be associated with service identification information of the target service, for example, the terminal receives a first message sent by the network side device, where the first message carries the target configuration information and the service identification information of the target service.

In this embodiment, the target configuration information is used to configure a packet format of the target service; and the terminal transmits service data of the target service based on the target configuration information. Therefore, the terminal can configure the data packet format for transmitting the target service based on the target configuration information sent by the network side equipment, 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 and improving the resource utilization rate.

Optionally, the target configuration information is configured based on at least one of:

the terminal transmits first negotiation information, wherein the first negotiation information is used for negotiating a data packet format;

the load condition of the network side equipment;

a link status between the network side device and the terminal;

the first indication information is used for configuring 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 packet format negotiation information, where the first negotiation information may be used to indicate a packet format of a transmission target service expected by the terminal, and the network side device sends target configuration information to the terminal based on the first negotiation information, where the target configuration information configures the packet format of the target service to a packet format of the transmission target service expected by the terminal.

In addition, the network side device may configure the target configuration information based on the load condition of the network side device. For example, if the network side device desires to adjust the coding rate of the target traffic of the terminal to 30 bytes of the data packet size sampled per unit time based on the load condition, the network side device may transmit target configuration information to the terminal, which may be used to indicate that the data packet (e.g., PDCP service data unit (Service Data Unit, SDU)) size is fixed to 30 bytes.

In addition, the network side device may configure the target configuration information based on a link condition between the network side device and the terminal. For example, the network side device may send, to the terminal, target configuration information that adjusts the size of a payload (e.g., PDCP SDU) carried by the data packet from 50 bytes to 30 bytes based on the link state with the terminal.

In addition, 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, where the first indication information may be used to assist the access network device in determining the target configuration information. The first indication information may also be referred to as core network indication information, and the first indication information may be used to indicate at least one of a coding rate of a service and the target configuration information.

In one embodiment, the first indication information may be used to indicate a coding rate of the target service, for example, the first indication information indicates that the coding rate of the target service is adjusted to be 30 bytes of a data packet size sampled per unit time, and the network side device may send target configuration information to the terminal, where the target configuration information may be used to indicate that the data packet (such as PDCP SDU) size is fixed to 30 bytes.

In this embodiment, the target configuration information is configured according to the first negotiation information, so that the target configuration information can be determined by negotiating a data packet format between the terminal and the network side device; the target configuration information is configured according to the load condition of the network side equipment, so that the network side equipment can determine the data packet format of the terminal for service data transmission based on the load condition of the network side equipment; configuring target configuration information through the link condition between the network side equipment and the terminal, so that an adaptive data packet format for transmitting service data can be determined based on the link condition; the target configuration information is configured through the core network indication information, so that the data packet format of the terminal for transmitting service data can be determined according to the indication of the core network indication information.

Optionally, 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 equipment, wherein the first negotiation information is used for negotiating a data packet format.

The first negotiation information may be used to negotiate a packet format of at least one of an SDAP packet, a PDCP packet, an RLC packet, and a MAC packet. For example, 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.

It should be noted that, the first negotiation information may be first request information, or may be first desired information, or may be first suggestion information, or the like, and the naming of the information for negotiating the data packet format is not limited in this embodiment. The first request information may be used to characterize a packet format requested by the terminal, the first desired information may be used to characterize a packet format desired by the terminal, and the first advice information may be used to characterize a packet format suggested by the terminal.

In addition, the first negotiation information may be used to negotiate a packet format of the target service, and for example, the first negotiation information may carry service identification information of the target service, where the service identification information may be at least one of session identification information, bearer identification information, and logical channel identification information; or, the first negotiation information may not carry service identification information, so that the packet format negotiated by the first negotiation information may be suitable for data transmission of any service of the terminal.

In this embodiment, the terminal and the network side device negotiate the data packet format, so that a fixed data packet format is used for each data transmission, and a large amount of header overhead caused by excessively flexible data packet format is avoided.

Optionally, the first negotiation information is used for negotiating a data packet format of the target service.

The first negotiation information may carry service identification information of the target service; or, the first negotiation information may be associated with service identification information of the target service, for example, the terminal sends a second message to the network side device, where the second message carries the first negotiation information and the service identification information of the target service.

In this embodiment, the terminal and the network side device negotiate the data packet format of the target service, so that a fixed data packet format is used for each data transmission of the target service, and a large amount of header overhead caused by excessively flexible data packet formats is avoided.

Optionally, the target service is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

Wherein the session identification information may include a protocol data unit (Protocol Data Unit, PDU) session control (session) ID; the Bearer identification information may include a Radio Bearer (RB) ID; the logical channel identification information may include LCID.

Optionally, the target configuration information includes at least one of:

The first configuration information is used for configuring the data packet format of the SDAP data packet of the service data adaptation protocol;

the second configuration information is used for configuring the data packet format of the packet data convergence protocol PDCP data packet;

third configuration information for configuring a packet format of the radio link control RLC packet;

and fourth configuration information for configuring a packet format of the medium access control MAC packet.

It should be noted that, in the case that the target configuration information does not include the configuration information of the packet format of a certain protocol layer, the terminal may configure the protocol layer using the preset configuration information. For example, if the target configuration information does not include the configuration information for configuring the packet format of the PDCP packet, i.e., the second configuration information, the terminal may configure the PDCP protocol layer using the preset PDCP packet format configuration information. For example, the pre-set PDCP packet format configuration information can include encapsulating PDCP layer packets with a sequence number (e.g., a 6bit PDCP SN) of a pre-set length. For example, if the target configuration information does not include the configuration information for configuring the packet format of the RLC layer packet, i.e., the third configuration information, the terminal may configure the RLC protocol layer using the preset RLC packet format configuration information. For example, the preset RLC packet format configuration information may include configuring the RLC entity using a transparent mode.

In this embodiment, the packet format of the SDAP packet is configured by the first configuration information, the packet format of the PDCP packet is configured by the second configuration information, the packet format of the RLC packet is configured by the third configuration information, and the packet format of the MAC packet is configured by the fourth configuration information, so that the packet format of each layer of packet of the NR UP protocol stack can be configured.

Optionally, the first configuration information includes at least one of:

the second indication information is used for indicating enabling or disabling the SDAP packaging packet header;

the third indication information is used for indicating the size of the SDAP data packet;

the second configuration information includes at least one of:

fourth indication information, the fourth indication information is used for indicating the PDCP data packet size;

PDCP sequence number configuration information;

the third configuration information includes:

fifth indication information for indicating an RLC layer transmission mode;

the fourth configuration information includes at least one of:

a sixth indication information, where the sixth indication information is used to indicate that the MAC multiplexing function is enabled or disabled;

seventh indication information for indicating a MAC packet size.

The PDCP sequence number length configured by the PDCP sequence number configuration information may be less than 8 bits, and for example, the PDCP sequence number length configured by the PDCP sequence number configuration information may be 6 bits.

In addition, the second configuration information may further include: eighth indication information, which may be used to indicate whether to enable or disable the PDCP encapsulation header. The eighth indication information may have an association relationship with PDCP sequence number configuration information, and in case that 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.

In one embodiment, the packet format of the PDCP packet may be configured as: the PDCP SDU is indicated to be fixed to 30 bytes through the fourth indication information, the PDCP header carries 6-bit PDCP SN through the PDCP sequence number configuration information, and the PDCP header occupies one byte.

Optionally, the terminal sends first negotiation information to the network side device, including:

and the terminal sends first negotiation information to the network side equipment 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.

For example, if the coding rate of the target service of the terminal is adjusted from the first coding rate to the second coding rate, the size of the data packet sampled in the unit time of the first coding rate is 30 bytes, and the size of the data packet sampled in the unit time of the second coding rate is 50 bytes, the terminal may send first negotiation information to the network side device, where the first negotiation information may be used to indicate that the size of the data packet (such as PDCP SDU) is fixed to be 50 bytes.

In this embodiment, the terminal sends the first negotiation information to the network side device based on the coding rate of the service, so that the terminal can negotiate a data packet format with the network side device according to the coding rate of the service itself, so that the negotiated data packet format is adapted to the coding rate of the service.

Optionally, the first negotiation information is used for negotiating a packet format of at least one of the following packets:

SDAP data packet;

PDCP data packet;

RLC data packets;

and (5) MAC data packets.

In this embodiment, the packet format of at least one packet among the SDAP packet, the PDCP packet, the RLC packet, and the MAC packet is negotiated by the first negotiation information, so that the packet format of each layer packet of the NR UP protocol stack can be negotiated.

Optionally, in case the first negotiation information is used for negotiating a packet format of an SDAP packet, the first negotiation information includes at least one of:

SDAP subheader negotiation information;

SDAP data packet size negotiation information.

The SDAP subheader negotiation information may be negotiation information of the SDAP subheader. The SDAP packet size negotiation information may be negotiation information of SDAP packet size.

In this embodiment, the SDAP sub-header configuration can be negotiated through the SDAP sub-header negotiation information, and the SDAP packet size can be negotiated through the SDAP packet size negotiation information.

Optionally, the SDAP subheader negotiation information is configured to indicate any one of the following:

the terminal expects or does not expects to configure an SDAP subheader; the terminal suggests or does not suggest to configure an SDAP subheader; the terminal supports or does not support configuration of SDAP subheads;

the SDAP data packet size negotiation information is used for indicating any one of the following:

the SDAP data packet size expected by the terminal; the SDAP data packet size supported by the terminal; the SDAP data packet size suggested by the terminal.

Optionally, in case the first negotiation information is used for negotiating a packet format of a PDCP packet, the first negotiation information includes at least one of:

PDCP sequence number negotiation information;

PDCP packet size negotiation information.

The PDCP sequence number negotiation information may be PDCP sequence number negotiation information. The PDCP packet size negotiation information can be negotiation information of a PDCP packet size.

In this embodiment, the PDCP sequence number length can be negotiated by PDCP sequence number negotiation information, and the PDCP packet size can be negotiated by PDCP packet size negotiation information.

Optionally, the PDCP sequence number negotiation information is configured to indicate any one of the following:

the PDCP sequence number length which is expected to be configured by the terminal; the terminal suggests the configured PDCP sequence number length; the terminal supports the configured PDCP sequence number length;

the PDCP packet size negotiation information is configured to negotiate at least one of:

concatenation PDCP packet size with packet concatenation enabled;

PDCP packet size with packet concatenation disabled.

It should be noted that, in the case where the packet concatenation function is disabled, i.e., in the case where no PDCP concatenation operation is performed, the PDCP packet size negotiation information can be used to negotiate a single PDCP packet (e.g., PDCP SDU) size. In the case of enabling the packet concatenation function, that is, in the case of PDCP concatenation operation, the PDCP packet size negotiation information may include single PDCP packet size information and concatenation number information.

Optionally, in case the first negotiation information is used for negotiating a packet format of an RLC packet, the first negotiation information includes at least one of:

RLC subheader negotiation information;

RLC sequence number negotiation information;

RLC packet size negotiation information;

RLC segmentation function negotiation information.

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 negotiation information of the RLC segmentation function.

In this embodiment, RLC subheader configuration can be negotiated through RLC subheader negotiation information, RLC sequence numbers can be negotiated through RLC sequence number negotiation information, RLC data packet sizes can be negotiated through RLC data packet size negotiation information, and enabling or disabling RLC segmentation functions can be negotiated through RLC segmentation function negotiation information.

Optionally, the RLC subheader negotiation information is configured to indicate any one of the following:

the terminal expects or does not expect to configure the RLC subheader; the terminal recommends or does not recommends configuration of an RLC subheader;

the RLC sequence number negotiation information is configured to indicate any one of:

the terminal expects configured RLC serial numbers; the terminal suggests configured RLC sequence numbers;

the RLC packet size negotiation information is configured to indicate any one of:

The size of the RLC data packet expected by the terminal; the size of the RLC data packet supported by the terminal; the size of the RLC data packet suggested by the terminal;

the RLC segmentation function negotiation information is configured to indicate any one of:

the terminal expects or does not expect to enable the segmentation function; the terminal suggests enabling or suggesting disabling of the segmentation function.

Optionally, in case the first negotiation information is used for negotiating a packet format of a MAC packet, the first negotiation information includes at least one of:

the MAC multiplexing function negotiates information;

MAC packet size negotiation information.

The MAC packet may be a MAC sdu from a specific logical channel or may be a MAC pdu. The MAC multiplexing function negotiation information may be negotiation information of MAC multiplexing. The MAC packet size negotiation information may be negotiation information of a MAC packet size.

In this embodiment, the multiplexing function can be negotiated to be enabled or disabled by the MAC multiplexing function negotiation information, and the MAC packet size can be negotiated by the MAC packet size negotiation information.

Optionally, the MAC multiplexing function negotiation information is used to indicate any one of the following:

the terminal expects or does not expect to enable multiplexing functions; the terminal suggests or does not suggest to enable the multiplexing function;

The MAC packet size negotiation information is configured to indicate any one of the following:

the size of the MAC data packet expected by the terminal; the MAC data packet size supported by the terminal; the terminal suggests a MAC packet size.

Optionally, the SDAP packet size includes at least one of: SDAP service data unit SDU data packet size; SDAP protocol data unit PDU data packet size;

the PDCP packet size includes at least one of: PDCP SDU packet size; PDCP PDU packet size;

the RLC packet size includes at least one of: RLC SDU packet size; RLC PDU packet size;

the MAC packet size includes at least one of: MAC SDU packet size; MAC PDU packet size.

Optionally, the terminal transmits service data based on the target configuration information, including:

the terminal encapsulates service data based on the target configuration information;

and the terminal transmits the packaged service data.

In this embodiment, the terminal encapsulates service data based on the target configuration information; and the terminal transmits the packaged service data. Therefore, the terminal can package the service data according to the data packet format configured by the target configuration information, so that the terminal uses a relatively fixed data packet format when packaging the data packet, thereby reducing the data packet header overhead and improving the resource utilization rate.

The following describes a data transmission method according to an embodiment of the present application by a specific embodiment:

(1): the terminal (e.g., user Equipment (UE)) sends first negotiation information to the network side device, where the first negotiation information may be a packet format negotiation message, where the packet format negotiation message is used to negotiate a packet format of transmission target service data.

Wherein, the data packet format negotiation message may include at least one of the following:

SDAP data packet format negotiation information;

PDCP data packet format negotiation information;

RLC packet format negotiation information;

MAC packet format negotiation information.

Wherein, the SDAP packet format negotiation information may include one or more of the following information:

negotiation information of SDAP subheader;

negotiation information of the SDAP packet size.

Further, 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 instruct the UE to suggest to configure or not to configure the SDAP subheader; or indicate that the UE supports configuration or does not support configuration of the SDAP subheader.

Further, the SDAP data packet may be an SDAP SDU or an SDAP PDU. The SDAP data packet size information is used for indicating the expected SDAP data packet size of the UE, or is used for indicating the SDAP data packet size supported by the UE, or is used for indicating the suggested SDAP data packet size of the UE.

Wherein, the PDCP data packet format negotiation information can include one or more of the following:

negotiation information of PDCP sequence numbers;

negotiation information of PDCP packet size.

Further, the negotiation information of the PDCP sequence number may be used to indicate PDCP SNs that the UE desires to configure. Illustratively, the negotiation information of the PDCP sequence number may be length information of an SN sequence number, such as sn=6bit (which may be understood as a short sequence number). As a specific example, the length information of the SN sequence number can be said to be sn=0bit. In this case, the negotiation information of the PDCP sequence number is equivalent to informing the network side that the UE does not desire to configure the PDCP header, that is, the PDCP layer does not need to carry the PDCP encapsulation header when encapsulating the data packet.

Further, the PDCP data packet may be a PDCP SDU or a PDCP PDU. The negotiation information of the PDCP data packet size is used for negotiating the size of a single PDCP data packet and/or the PDCP data packet after concatenation. Wherein, the RLC data packet format negotiation information may include one or more of the following:

negotiation information of the RLC subheader;

negotiation information of the RLC sequence number;

negotiation information of the RLC packet size;

negotiation information of RLC segmentation function.

Further, 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 indicate that the UE suggests to carry or not carry the RLC subheader.

Further, the negotiation information of the RLC sequence number may be used to indicate the RLC SN that the UE desires to configure. Illustratively, the negotiation information of the RLC sequence number may be length information of an SN sequence number, such as sn=6bit (which may be understood as a short sequence number). As a specific example, the length information of the SN sequence number can be said to be sn=0bit. In this case, the negotiation information of the RLC sequence number is equivalent to informing the network side that the UE does not desire to configure the RLC header, i.e. the RLC layer does not need to carry the RLC encapsulation header when encapsulating the data packet.

Further, the RLC data packet may be an RLC SDU or an RLC PDU. The negotiation information of the RLC data packet size may be used to indicate the RLC data packet size expected by the UE, or to indicate the RLC data packet size supported by the UE, or to indicate the RLC data packet size suggested by the UE.

Further, the negotiation information of the RLC segmentation function is used to indicate that the UE desires or does not desire to enable the segmentation function, or that the UE suggests or does not suggest to enable the segmentation function. Illustratively, when the segmentation function is not enabled, the transmission resources provided by the network side device are sufficient to transmit the complete RLC SDU.

Wherein, the MAC packet format negotiation information may include one or more of the following information:

negotiation information of the MAC multiplexing;

negotiation information of the MAC packet size.

Further, the negotiation information of the MAC multiplexing is used to indicate that the UE desires to perform or not perform the multiplexing function, or indicate that the UE suggests to perform or not perform multiplexing.

In one embodiment, the packet format negotiation information may further include service identification information. The data packet format negotiation message is used for negotiating the data packet format of the target service identified by the service identification information. The service identification information is used for identifying the target service of the UE.

Wherein the service identification information may include one or more of:

session identification information;

carrying identification information;

logical channel identification information.

For example, the session identification information may include a PDU session ID; the bearer identification information may include an RB ID; the logical channel identification information may include LCID.

In an embodiment, the 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 traffic.

It should be noted that, in the case that the packet format negotiation information does not include service identification information, the packet format negotiated by the packet format negotiation information may be defaulted and may be suitable for data transmission of any service of the UE.

(2): the network side device sends target configuration information to the UE, where the target configuration information may be packet format configuration information, where the packet format configuration information is used to configure a packet format for transmitting target service data.

Wherein the network side device (e.g., base station) determines the packet format configuration information based on one or more of the following:

the data packet format negotiation information of the UE;

the load condition of the network side equipment;

link conditions of the UE;

the first indication information may be indication information of the core network.

Taking the case of determining the data packet format configuration information based on the data packet format negotiation information of the UE as an example, the network side device receives the data packet format negotiation information sent by the UE, where the data packet format negotiation information is used to indicate a data packet format of a transmission target service expected by the UE, and the network side device provides the data packet format configuration information, where the data packet format of the target service is configured as a data packet format of the transmission target service expected by the UE.

Taking the example of determining the data packet format configuration information based on the load condition of the network side device, 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 condition, the size of the data packet sampled in the unit time of the third coding rate is 50 bytes, the size of the data packet sampled in the unit time of the fourth coding rate is 30 bytes, and then the network side device may send the data packet format configuration information to the UE, where the data packet format configuration information may be used to indicate that the size of the data packet (such as PDCP SDU) is fixed to 30 bytes.

Taking the example of determining the data packet format configuration information based on the link status of the UE, the network side device may send the data packet format configuration information to the UE based on the link status with the UE, where the data packet format configuration information adjusts the size of the payload (such as PDCP SDU) carried by the data packet from 50 bytes to 30 bytes.

Taking the case of determining the data packet format configuration information based on the first indication information as an example, the network side device may be a base station, and the core network sends the first indication information to the base station, where the first indication information is used to assist the base station in determining the data packet format configuration information, and the data packet format configuration information is used to determine a data packet format of the target service.

In one embodiment, the packet format configuration information includes one or more of the following:

SDAP data packet format configuration information;

PDCP packet format configuration information;

RLC packet format configuration information;

MAC packet format configuration information.

Further, the SDAP packet format configuration information may include one or more of: enabling or disabling the use of the indication information of the SDAP encapsulation header; SDAP packet size indication information.

Further, the PDCP packet format configuration information can include one or more of the following: PDCP packet size indication information, PDCP sequence number configuration information.

Further, the RLC packet format configuration information may include the following information: the RLC layer transmits mode information.

Further, the MAC packet format configuration information may include one or more of the following: indication information to enable or disable the MAC multiplexing function, indication information of the MAC packet size. The MAC packet size may be a packet size of a MAC subSDU of a specific logical channel.

In addition, 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 configuration information of the data packet format of the RLC layer, and the MAC data packet format configuration information is the configuration information of the data packet format of the MAC layer.

In one embodiment, the packet format configuration information may further include service identification information, where the service identification information may include one or more of the following:

session identification information;

carrying identification information;

logical channel identification information.

It should be noted that, in the case that the packet format configuration information does not include service identification information, it may be defaulted that the packet format configuration information may be applicable to data transmission of any service of the UE.

In addition, when the UE receives the packet format configuration information, the AS of the UE may notify a higher layer (for example, an application layer) of the packet format configuration information and related information of a target service associated with the packet format configuration information, so AS to assist the higher layer in adjusting the coding rate of the target service.

(3): and the UE receives the data packet format configuration information sent by the network side equipment and transmits the data packet of the target service based on the data packet format configuration information.

In one embodiment, as shown in fig. 16, the packet format of the packet format configuration information configured to perform data transmission is as follows:

for the SDAP layer, negotiating no SDAP header through the UE and the network side equipment, and fixing the SDAP SDU size to 30 bytes;

for the PDCP layer, negotiating PDCP SDU fixing to 30 bytes through the UE and the network side equipment, wherein the PDCP header occupies one byte and carries 6-bit PDCP SN;

for the RLC layer, negotiating no RLC header through the UE and the network side equipment, and not starting an RLC segmentation function;

for the MAC layer, the MAC SDU is negotiated to be fixed into 31 bytes through the UE and the network side equipment, the multiplexing function is started by the MAC header, the MAC header occupies one byte, the LCID domain is carried, and the total number of the MAC subPDU is 32 bytes.

It should be noted that, in the related art, the NR protocol stack flexibly supports data packets with various sizes, and the packet format design of each protocol layer is compatible with the feature of encapsulating data packets with variable sizes. However, in some scenarios (e.g., limited uplink coverage), this feature of encapsulating variable-size packets that is too flexible may generate a significant amount of overhead, e.g., the RLC layer may carry split domains, the MAC layer needs to carry packet length domains, etc., which is detrimental to improving resource utilization. The embodiment of the application negotiates the data packet format through the UE and the network side equipment so as to realize that the same data packet format is used for the data transmission of the target service, thereby reducing the head expenditure required by the data transmission.

Referring to fig. 17, fig. 17 is a flowchart of an information sending method according to an embodiment of the present application, and as shown in fig. 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 a data packet format.

Optionally, the target configuration information is used for configuring a data packet format of the target service.

Optionally, before the network side device sends the target configuration information to the terminal, the method further includes:

The network side device configures the target configuration information based on at least one of:

the load condition of the network side equipment;

a link status between the network side device and the terminal;

Optionally, the target configuration information is configured based on the first indication information, the network side device is an access network device, and before the network side device sends the target configuration information to the terminal, the method further includes:

and the access network equipment receives the first indication information sent by the core network equipment.

Optionally, the first indication information is used for indicating any one of the following:

the coding rate of the service;

the target configuration information.

the network side equipment receives first negotiation information sent by the terminal, wherein the first negotiation information is used for negotiating a data packet format.

Optionally, the target service is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

Optionally, the target configuration information includes at least one of:

It should be noted that, as an implementation manner of the network side device corresponding to the embodiment shown in fig. 15, a specific implementation manner of the embodiment may refer to a related description of the embodiment shown in fig. 15, and in order to avoid repetitive description, this embodiment is not repeated. Therefore, the terminal can configure the data packet format for service data transmission based on the target configuration information sent by the network side equipment, so that the terminal can use a relatively fixed data packet format when transmitting service data, thereby reducing the data packet header overhead and improving the resource utilization rate.

Referring to fig. 18, fig. 18 is a flowchart of an information sending method according to an embodiment of the present application, and as shown in fig. 18, the information sending method includes the following steps:

step 301, 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 to configure a data packet format.

the coding rate of the service;

and the target configuration information is used for configuring the data packet format.

It should be noted that, as an implementation manner of the core network device corresponding to the embodiment shown in fig. 17, a specific implementation manner of the embodiment may refer to a description related to the embodiment shown in fig. 17, and in order to avoid repetitive description, this embodiment is not repeated.

In the embodiment of the application, core network equipment sends first indication information to access network equipment, wherein the first indication information is used for assisting the access network equipment to configure a data packet format. Therefore, the access network equipment can configure a data packet format for the terminal to transmit service data based on the first indication information, so that the terminal can use a relatively fixed data packet format when transmitting the service data, thereby reducing the cost of a data packet header and improving the resource utilization rate.

According to the data transmission method provided by the embodiment of the application, the execution main body can be a data transmission device. In the embodiment of the present application, a data transmission device performs a data transmission method as an example, which describes a data transmission device provided in the embodiment of the present application.

Referring to fig. 19, fig. 19 is a block diagram of a data transmission device according to an embodiment of the present application, where a terminal includes the data transmission device, and as shown in fig. 19, a data transmission device 400 includes:

a receiving module 401, configured to receive target configuration information sent by a network side device, where the target configuration information is used to configure a data packet format;

a transmission module 402, configured to transmit service data based on the target configuration information.

the transmission module 402 is specifically configured to:

the load condition of the network side equipment;

a link status between the network side device and the terminal;

Optionally, the apparatus further comprises:

the sending module is used for sending first negotiation information to the network side equipment, wherein the first negotiation information is used for negotiating a data packet format.

Optionally, the target service is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

Optionally, the target configuration information includes at least one of:

Optionally, the first configuration information includes at least one of:

the second configuration information includes at least one of:

PDCP sequence number configuration information;

the third configuration information includes:

fifth indication information for indicating an RLC layer transmission mode;

the fourth configuration information includes at least one of:

seventh indication information for indicating a MAC packet size.

Optionally, the sending module is specifically configured to:

SDAP data packet;

PDCP data packet;

RLC data packets;

and (5) MAC data packets.

SDAP subheader negotiation information;

SDAP data packet size negotiation information.

PDCP sequence number negotiation information;

PDCP packet size negotiation information.

concatenation PDCP packet size with packet concatenation enabled;

PDCP packet size with packet concatenation disabled.

RLC subheader negotiation information;

RLC sequence number negotiation information;

RLC packet size negotiation information;

RLC segmentation function negotiation information.

The MAC multiplexing function negotiates information;

MAC packet size negotiation information.

Optionally, the transmission module 402 is specifically configured to:

packaging business data based on the target configuration information;

and transmitting the packaged service data.

The data transmission device in the embodiment of the application can configure the data packet format for carrying out service data transmission based on the target configuration information sent by the network side equipment, so that the terminal can use a relatively fixed data packet format when carrying out service data transmission, thereby reducing the data packet header cost and improving the resource utilization rate.

The data transmission device in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The data transmission device provided by the embodiment of the present application can implement each process implemented by the method embodiment of fig. 15, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

Referring to fig. 20, fig. 20 is a block diagram of an information sending apparatus provided in an embodiment of the present application, where a network side device includes the information sending apparatus, and as shown in fig. 20, an information sending apparatus 500 includes:

a sending module 501, configured to send target configuration information to a terminal, where the target configuration information is used to configure a packet format.

Optionally, the apparatus further comprises:

a configuration module for configuring the target configuration information based on at least one of:

the load condition of the network side equipment;

a link status between the network side device and the terminal;

Optionally, the target configuration information is configured based on the first indication information, the network side device is an access network device, and the apparatus further includes:

and the first receiving module is used for receiving the first indication information sent by the core network equipment.

the coding rate of the service;

the target configuration information.

Optionally, the apparatus further comprises:

the second receiving module is used for receiving first negotiation information sent by the terminal, and the first negotiation information is used for negotiating a data packet format.

Optionally, the target service is identified by at least one of:

Session identification information;

carrying identification information;

logical channel identification information.

Optionally, the target configuration information includes at least one of:

According to the information sending device provided by the embodiment of the application, the target configuration information is sent to the terminal, so that the terminal can use a relatively fixed data packet format when transmitting service data, the data packet header overhead can be reduced, and the resource utilization rate is improved.

The information sending device in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The information sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment of fig. 17, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

Referring to fig. 21, fig. 21 is a block diagram of an information sending apparatus provided in an embodiment of the present application, where a core network device includes the information sending apparatus, and as shown in fig. 21, an information sending apparatus 600 includes:

a sending module 601, configured to send first indication information to an access network device, where the first indication information is used to assist the access network device in configuring a data packet format.

the coding rate of the service;

The information sending device in the embodiment of the application sends the first indication information to the access network equipment, wherein the first indication information is used for assisting the access network equipment to configure the data packet format. Therefore, the access network equipment can configure a data packet format for the terminal to transmit service data based on the first indication information, so that the terminal can use a relatively fixed data packet format when transmitting the service data, thereby reducing the cost of a data packet header and improving the resource utilization rate.

The information sending device provided by the embodiment of the present application can implement each process implemented by the method embodiment of fig. 18, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

Optionally, as shown in fig. 22, the embodiment of the present application further provides a communication device 700, including a processor 701 and a memory 702, where the memory 702 stores a program or instructions that can be executed on the processor 701, for example, when the communication device 700 is a terminal, the program or instructions implement the steps of the above-mentioned data transmission method embodiment when executed by the processor 701, and achieve the same technical effects. When the communication device 700 is a network side device, the program or the instruction, when executed by the processor 701, implements the steps of the above-described embodiment of the information sending method, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides a terminal, which comprises a processor and a communication interface, wherein the communication interface is used for receiving target configuration information sent by the network side equipment, and the target configuration information is used for configuring a data packet format; the processor is used for transmitting service data based on the target configuration information. The terminal embodiment corresponds to the data transmission method embodiment, and each implementation process and implementation manner of the data transmission method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 23 is a schematic hardware structure of a terminal for implementing an embodiment of the present application.

The terminal 800 includes, but is not limited to: at least part of the components of the radio frequency unit 801, the network module 802, the audio output unit 803, the input unit 804, the sensor 805, the display unit 806, the user input unit 807, the interface unit 808, the memory 809, and the processor 810, etc.

Those skilled in the art will appreciate that the terminal 800 may further include a power source (e.g., a battery) for powering the various components, and that the power source may be logically coupled to the processor 810 by a power management system for performing functions such as managing charging, discharging, and power consumption by the power management system. The terminal structure shown in fig. 23 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 804 may include a graphics processing unit (Graphics Processing Unit, GPU) 8041 and a microphone 8042, with the graphics processor 8041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 806 may include a display panel 8061, and the display panel 8061 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 at least one of a touch panel 8071 and other input devices 8072. Touch panel 8071, also referred to as a 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, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 801 may transmit the downlink data to the processor 810 for processing; in addition, the radio frequency unit 801 may send uplink data to the network side device. In general, the radio frequency unit 801 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 809 may be used to store software programs or instructions and various data. The memory 809 may mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 809 may include volatile memory or nonvolatile memory, or the memory 809 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 809 in embodiments of the application includes, but is not limited to, these and any other suitable types of memory.

The processor 810 may include one or more processing units; optionally, the processor 810 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, etc., and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 810.

The radio frequency unit 801 is configured to receive target configuration information sent by a network side device, where the target configuration information is used to configure a data packet format;

a processor 810 for transmitting traffic data based on the target configuration information.

and a processor 810, configured to transmit service data of the target service based on the target configuration information.

the load condition of the network side equipment;

a link status between the network side device and the terminal;

Optionally, the radio frequency unit 801 is further configured to send first negotiation information to the network side device, where the first negotiation information is used to negotiate a data packet format.

Optionally, the target service is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

Optionally, the target configuration information includes at least one of:

Optionally, the first configuration information includes at least one of:

The second configuration information includes at least one of:

PDCP sequence number configuration information;

the third configuration information includes:

fifth indication information for indicating an RLC layer transmission mode;

the fourth configuration information includes at least one of:

seventh indication information for indicating a MAC packet size.

Optionally, the radio frequency unit 801 is further configured to:

and sending first negotiation information to the network equipment based on the coding rate of the service.

SDAP data packet;

PDCP data packet;

RLC data packets;

and (5) MAC data packets.

SDAP subheader negotiation information;

SDAP data packet size negotiation information.

PDCP sequence number negotiation information;

PDCP packet size negotiation information.

concatenation PDCP packet size with packet concatenation enabled;

PDCP packet size with packet concatenation disabled.

RLC subheader negotiation information;

RLC sequence number negotiation information;

RLC packet size negotiation information;

RLC segmentation function negotiation information.

the MAC multiplexing function negotiates information;

MAC packet size negotiation information.

Optionally, the processor 810 is further configured to:

packaging business data based on the target configuration information;

and transmitting the packaged service data.

The embodiment of the application also provides network side equipment, which comprises a processor and a communication interface, wherein the communication interface is used for: and sending target configuration information to the terminal, wherein the target configuration information is used for configuring the data packet format. The network side device embodiment corresponds to the information sending method embodiment, and each implementation process and implementation manner of the information sending method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 24, 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. The antenna 901 is connected to a radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information via the antenna 901, and transmits the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes information to be transmitted, and transmits the processed information to the radio frequency device 902, and the radio frequency device 902 processes the received information and transmits the processed information through the antenna 901.

The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 903, where the baseband apparatus 903 includes a baseband processor.

The baseband apparatus 903 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 24, where one chip, for example, a baseband processor, is connected to the memory 905 through a bus interface, so as to call a program in the memory 905 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 906, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 900 of the embodiment of the present application further includes: instructions or programs stored in the memory 905 and executable on the processor 904, the processor 904 calls the instructions or programs in the memory 905 to perform the method performed by the modules shown in fig. 20, and achieve the same technical effects, so that repetition is avoided and therefore a description thereof is omitted.

Specifically, the embodiment of the application also provides core network equipment. As shown in fig. 25, 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 (common public radio interface, CPRI).

Specifically, the core network device 1000 of the embodiment of the present application further includes: the instructions or programs stored in the memory 1003 and executable on the processor y01, and the processor 1001 invokes the instructions or programs in the memory 1003 to execute the method executed by each module shown in fig. 21, and achieve the same technical effects, so repetition is avoided and will not be described herein.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above data transmission method or the information transmission method embodiment, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a program or instructions, the processes of the data transmission method or the information transmission method embodiment can be realized, the same technical effects can be achieved, and the repetition is avoided, and the description is omitted here.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The embodiments of the present application further provide a computer program/program product stored in a storage medium, where the computer program/program product is executed by at least one processor to implement each process of the data transmission method or the information transmission method, and achieve the same technical effects, and are not repeated herein.

The embodiment of the application also provides a data transmission system, which comprises: the terminal can be used for executing the steps of the data transmission method, and the network side device can be used for executing the steps of the information transmission method.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. A data transmission method, comprising:

2. The method of claim 1, wherein the target configuration information is used to configure a packet format of a target service;

3. The method of claim 1, wherein the target configuration information is configured based on at least one of:

the load condition of the network side equipment;

a link status between the network side device and the terminal;

4. The method according to claim 1, wherein before the terminal receives the target configuration information sent by the network side device, the method further comprises:

5. The method of claim 4, wherein the first negotiation information is used to negotiate a packet format for a target service.

6. The method according to claim 2 or 5, wherein the target traffic is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

7. The method according to any one of claims 1 to 5, wherein the target configuration information comprises at least one of:

8. The method of claim 7, wherein the first configuration information comprises at least one of:

the second configuration information includes at least one of:

PDCP sequence number configuration information;

the third configuration information includes:

fifth indication information for indicating an RLC layer transmission mode;

the fourth configuration information includes at least one of:

seventh indication information for indicating a MAC packet size.

9. The method according to claim 4, wherein the terminal sends the first negotiation information to the network side device, comprising:

10. The method according to claim 4 or 9, wherein the first negotiation information is used to negotiate a packet format of at least one of the following packets:

SDAP data packet;

PDCP data packet;

RLC data packets;

and (5) MAC data packets.

11. The method of claim 10, wherein in the case that the first negotiation information is used to negotiate a packet format of an SDAP packet, the first negotiation information comprises at least one of:

SDAP subheader negotiation information;

SDAP data packet size negotiation information.

12. The method of claim 11, wherein the SDAP sub-header negotiation information is used to indicate any one of:

13. The method of claim 10, wherein in case the first negotiation information is used to negotiate a packet format of PDCP packets, the first negotiation information comprises at least one of:

PDCP sequence number negotiation information;

PDCP packet size negotiation information.

14. The method of claim 13, wherein the PDCP sequence number negotiation information is used to indicate any one of:

concatenation PDCP packet size with packet concatenation enabled;

PDCP packet size with packet concatenation disabled.

15. The method of claim 10, wherein the first negotiation information comprises at least one of:

RLC subheader negotiation information;

RLC sequence number negotiation information;

RLC packet size negotiation information;

RLC segmentation function negotiation information.

16. The method of claim 15 wherein the RLC subheader negotiation information is used to indicate any one of:

17. The method according to claim 10, wherein in case the first negotiation information is used for negotiating a packet format of a MAC packet, the first negotiation information comprises at least one of:

the MAC multiplexing function negotiates information;

MAC packet size negotiation information.

18. The method of claim 17, wherein the MAC multiplexing function negotiation information is used to indicate any one of:

19. The method of claim 8 or 11 or 13 or 15 or 17, wherein the SDAP packet size comprises at least one of: SDAP service data unit SDU data packet size; SDAP protocol data unit PDU data packet size;

20. The method according to any one of claims 1 to 5, wherein the terminal transmits traffic data based on the target configuration information, comprising:

and the terminal transmits the packaged service data.

21. An information transmission method, comprising:

22. The method of claim 21, wherein the target configuration information is used to configure a packet format of the target service.

23. The method according to claim 21, wherein before the network side device sends the target configuration information to the terminal, the method further comprises:

the load condition of the network side equipment;

a link status between the network side device and the terminal;

24. The method according to claim 23, wherein the target configuration information is configured based on the first indication information, the network side device is an access network device, and before the network side device sends the target configuration information to the terminal, the method further comprises:

25. The method of claim 23, wherein the first indication information is used to indicate any one of:

the coding rate of the service;

the target configuration information.

26. The method according to claim 21, wherein before the network side device sends the target configuration information to the terminal, the method further comprises:

27. The method of claim 26, wherein the first negotiation information is used to negotiate a packet format for the target service.

28. The method according to claim 22 or 27, wherein the target traffic is identified by at least one of:

session identification information;

carrying identification information;

logical channel identification information.

29. The method according to any one of claims 21 to 27, wherein the target configuration information comprises at least one of:

30. An information transmission method, comprising:

31. The method of claim 30, wherein the first indication information is used to indicate any one of:

The coding rate of the service;

32. A data transmission apparatus, a terminal including the data transmission apparatus, comprising:

33. An information transmission apparatus, a network-side device including the information transmission apparatus, comprising:

34. An information transmission apparatus, a core network device including the information transmission apparatus, characterized by comprising:

35. A terminal comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, performs the steps of the data transmission method of any one of claims 1 to 20.

36. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the information transmission method of any one of claims 21 to 29.

37. A core network device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the information transmission method of any one of claims 30 to 31.

38. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions, which when executed by a processor, implements the steps of the data transmission method according to any one of claims 1 to 20, or the steps of the information transmission method according to any one of claims 21 to 29, or the steps of the information transmission method according to any one of claims 30 to 31.