METHOD AND DEVICE FOR DATA TRANSMISSION

1 . A method for data transmission, comprising;

determining, by a terminal, a correspondence between bearer types and user-plane configurations;

receiving, by the terminal, bearer type indication information indicated by a network side, the bearer type indication information carrying a bearer type identifier;

determining, by the terminal, the user-plane configuration corresponding to a bearer, according to the bearer type identifier carried in the bearer type indication information and the correspondence between the bearer types and the user-plane configurations; and

performing, by the terminal, data transmission according to the determined user-plane configuration,

2 . The method according to claim 1 , wherein the user-plane configurations comprise a user-plane function configuration and/or a user plane parameter configuration; or

the user-plane configurations comprise function division manners for a user-plane function divided between a centralized processing node and a distributed processing node.

3 . The method according to claim 1 , wherein the user-plane configuration corresponding to the bearer type is a configuration for a basic function and/or a basic parameter of a user plane, or the user-plane configuration corresponding to the bearer type is a set of configurations for the basic functions and/or the basic parameters of the user plane.

4 . The method according to claim 1 , wherein the determining, by the terminal, the correspondence between bearer types and the user-plane configurations comprises:

determining, by the terminal, the correspondence between the bearer type of the bearer and the user-plane configuration according to at least one of a service type corresponding to the bearer or a network deployment corresponding to the bearer; or

wherein the determining, by the terminal, the correspondence between bearer types and the user-plane configurations comprises:

determining, by the terminal, the correspondence between the bearer types and the user-plane configurations based on pre-configuration information; or

obtaining, by the terminal, the correspondence between the bearer types and the user-plane configurations in a network notification manner.

5 . (canceled)

6 . The method according to claim 4 , wherein the determining, by the terminal, the correspondence between the bearer types and the user-plane configurations based on the pre-configuration information comprises:

determining, by the terminal, the correspondence between the bearer types corresponding to a terminal capability and the user-plane configurations based on the pre-configuration information, or

wherein the obtaining, by the terminal, the correspondence between the bearer types and the user-plane configurations in the network notification manner comprises;

reporting, by the terminal, a terminal capability; and

obtaining, by the terminal, the correspondence between the bearer types corresponding to the terminal capability and the user-plane configurations in the network notification manner.

7 . (canceled)

8 . The method according to claim 1 , wherein the user-plane configuration corresponding to the bearer type comprises one or more of: header compression, encryption, integrity protection, segmentation, concatenation, Automatic Repeat reQuest (ARQ), Hybrid Automatic Repeat reQuest (HARQ), multiplexing, a Quality of Service (QoS) parameter, a scheduling manner, a modulation manner, an encoding manner, and a multiple access manner.

9 . A method for data transmission, comprising:

determining, by a network side device, a correspondence between bearer types and user-plane configurations;

configuring, by the network side device, the bearer type corresponding to a bearer;

sending, by the network side device, bearer type indication information, wherein a bearer type identity is carried in the bearer type indication information;

determining, by the network side device, the user-plane configuration corresponding to the bearer, according to the bearer type identity and the correspondence between the bearer types and the user-plane configurations; and

performing, by the network side device, data transmission according to the determined user-plane configuration.

10 . The method according to claim 9 , wherein

the user-plane configurations comprise a user-plane function configuration and/or a user plane parameter configuration; or

the user-plane configurations comprise function division manners for a user-plane function divided between a centralized processing node and a distributed processing node,

11 . The method according to claim 9 , wherein the user-plane configuration corresponding to the bearer type is a configuration for a basic function and/or a basic parameter of a user plane, or the user-plane configuration corresponding to the bearer type is a set of configurations for the basic functions and/or the basic parameters of the user plane.

12 . The method according to claim 9 , wherein the determining, by the network side device, the correspondence between bearer types and user-plane configurations comprises:

determining, by the network side device, the correspondence between the bearer types and the user-plane configurations based on pre-configuration information, or

wherein the method further comprises:

notifying, by the network side device, a terminal of the correspondence between the bearer types and the user-plane configurations in a network notification manner.

13 . (canceled)

14 . The method according to claim 12 , wherein the notifying, by the network side device, the terminal of the correspondence between the bearer types and the user-plane configurations in the network notification manner comprises:

obtaining, by the network side device, a terminal capability reported by the terminal; and

notifying, by the network side device, the terminal of the correspondence between the bearer types corresponding to the terminal capability and the user-plane configurations in the network notification manner,

15 . The method according to claim 9 , wherein the user-plane configuration corresponding to the bearer type comprises one or more of: header compression, encryption, integrity protection, segmentation, concatenation, Automatic Repeat reQuest (ARQ), Hybrid Automatic Repeat reQuest (HARQ), multiplexing, a Quality of Service (QoS) parameter, a scheduling manner, a modulation manner, an encoding manner, and a multiple access manner,

16 . A device for data transmission, comprising a processor, a memory acid a transceiver, wherein

the memory is configured to store instructions used by the processor in performing operations;

the processor is configured to determine a correspondence between bearer types and user-plane configurations;

the transceiver is configured to receive bearer type indication information indicated by a network side, wherein a bearer type identifier is carried in the hearer type indication information;

the processor is further configured to determine the user-plane configuration corresponding to a bearer, according to the bearer type identifier carried in the bearer type indication information, and the correspondence between the bearer types and the user-plane configurations; and

the transceiver is further configured to perform data transmission according to the determined user-plane configuration.

17 . The device according to claim 16 , wherein the user-plane configurations comprise a user-plane function configuration and/or a user plane parameter configuration; or

the user-plane configurations comprise function division manners for a user-plane function divided between a centralized processing node and a distributed processing node.

18 . The device according to claim 16 , wherein the user-plane configuration corresponding to the bearer type is a configuration for a basic function and/or a basic parameter of a user plane, or the user-plane configuration corresponding to the bearer type is a set of configurations for the basic functions and/or the basic parameters of the user plane.

wherein the user-plane configuration corresponding to the bearer type comprises one or more of: header compression, encryption, integrity protection, segmentation, concatenation, Automatic Repeat reQuest (ARQ), Hybrid Automatic Repeat reQuest (HARQ), multiplexing, a Quality of Service (QoS) parameter, a scheduling manner, a modulation manner, an encoding manner, and a multiple access manner.

19 . The device according to claim 16 , wherein the first processor is further configured to determine the correspondence between the bearer type of the bearer and the user-plane configuration according to at least one of a service type corresponding to the bearer or a network deployment corresponding to the bearer, or

wherein the processor is further configured to: determine the correspondence between the bearer types and the user-plane configurations based on pre-configuration information, or obtain the correspondence between the bearer types and the user-plane configurations in a network notification manner,

wherein the processor is further configured to determine the correspondence between the bearer types corresponding to a terminal capability and the user-plane configurations based on the pre-configuration information, or the processor is further configured to report a terminal capability, and obtain the correspondence between the bearer types corresponding to the terminal capability and the user-plane configurations in the network notification manner.

20 - 23 . (canceled)

24 . A device for data transmission, configured to implement the method according to claim 9 , comprising: a processor, a memory and a transceiver, wherein

the memory is configured to store instructions used by the processor in performing operations;

the processor is configured to determine the correspondence between the bearer types and the user-plane configurations;

the processor is configured to configure the bearer type corresponding to the bearer;

the transceiver is configured to send the bearer type indication information, wherein a-the bearer type identity is carried in the bearer type indication information;

the processor is configured to determine the user-plane configuration corresponding to the bearer according to the bearer type identity and the correspondence between the bearer types and the user-plane configurations; and

the processor is configured to perform data transmission according to the determined user-plane configuration.

25 . The device according to claim 24 , wherein the user-plane configurations comprise a user-plane function configuration and/or a user plane parameter configuration; or

the user-plane configurations comprise function division manners for a user-plane function divided between a centralized processing node and a distributed processing node.

26 . The device according to claim 24 , wherein the user-plane configuration corresponding to the bearer type is a configuration for a basic function and/or a basic parameter of a user plane, or the user-plane configuration corresponding to the bearer type is a set of configurations for the basic functions and/or the basic parameters of the user plane, and

wherein the user-plane configuration corresponding to the bearer type comprises one or more of: header compression, encryption, integrity protection, segmentation, concatenation, Automatic Repeat reQuest (ARQ), Hybrid Automatic Repeat reQuest (HARQ), multiplexing, a Quality of Service (QoS) parameter, a scheduling manner, a modulation manner, an encoding manner, and a multiple access manner.

27 . The device according to claim 24 , wherein the processor is further configured to determine the correspondence between the bearer types and the user-plane configurations based on pre-configuration information, or is configured to notify a terminal of the correspondence between the bearer types and the user-plane configurations in a network notification manner, and

wherein the processor is further configured to report a terminal capability, and obtain the correspondence between the bearer types corresponding to the terminal capability and the user-plane configurations through the network notification manner.

28 - 32 . (canceled)