# US 2021/0084526 A1 · Data Transmission Method, Data Transmitting End, Data Receiving End, Data Transmission System And Computer Readable Storage Medium

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0084526 A1
- Document ID: US20210084526A1
- Status: Published application
- Kind: A1
- Application number: 16/620,378
- Filed: 2018-06-05
- Published: 2021-03-18
- Earliest claimed: 2017-06-08
- Assignees: Vivo Mobile Communication Co., Ltd.
- Applicants: Vivo Mobile Communication Co., Ltd.
- Inventors: Yumin WU
- Web page: https://patentgrep.com/patent/US20210084526A1

## CPC

- H04W 28/02: Traffic management, e.g. flow control or congestion control
- H04W 28/0273: {adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP] (wireless network protocols or protocol adaptations to wireless operation, e.g. wireless application protocol H04W80/00)}
- H04W 28/0263: {involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]}
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 28/06: Optimizing {the usage of the radio link}, e.g. header compression, information sizing {, discarding information (system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365)}
- H04W 76/11: Allocation or use of connection identifiers
- H04W 76/12: Setup of transport tunnels
- H04W 80/02: Data link layer protocols
- H04W 80/08: Upper layer protocols {(network arrangements or communication protocols for networked applications H04L67/00)}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure provides a data transmission method, related devices and system. The method includes: an upper layer transmits a data packet to a corresponding Service Data Adaptation Protocol (SDAP) entity, according to at least one of a network slice identifier, an SDAP identifier, a flow identifier or a session identifier; the SDAP entity adds the flow identifier to the data packet, and transmits the data packet with the flow identifier to a Packet Data Convergence Protocol (PDCP) entity corresponding to a Data Radio Bearer (DRB), according to a corresponding relationship between the SDAP entity and the DRB.

## Claims

### Claim 1

A data transmission method, applied to a data transmitting end, comprising:
transmitting, by an upper layer, a data packet to a corresponding Service Data Adaptation Protocol (SDAP) entity, according to at least one of a network slice identifier, an SDAP identifier, a flow identifier or a session identifier;
adding, by the SDAP entity, the flow identifier to the data packet; and,
transmitting the data packet with the flow identifier to a Packet Data Convergence Protocol (PDCP) entity corresponding to a Data Radio Bearer (DRB), according to a corresponding relationship between the SDAP entity and the DRB.

### Claim 2 (depends on 1)

The method according to claim 1, wherein, before transmitting, by the upper layer, the data packet to the corresponding SDAP entity, according to at least one of the network slice identifier, the flow identifier or the session identifier, the method further comprises:
establishing the SDAP entity in advance, according to configuration information which is configured by a network or pre-defined; wherein the configuration information comprises at least one of the network slice identifier, a DRB identifier, the flow identifier, the session identifier, or association relationship indication information; and,
indicating corresponding relationship information of the SDAP entity to the upper layer through the SDAP entity; wherein the corresponding relationship information comprises at least one of the network slice identifier, the DRB identifier, the flow identifier, the session identifier or the SDAP identifier.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the association relationship indication information comprises any one of:
indicating that one SDAP entity corresponds to one flow;
indicating that one SDAP entity corresponds to one Protocol Data Unit (PDU) session;
indicating that one SDAP entity corresponds to one PDCP entity;
indicating that one SDAP entity corresponds to one Medium Access Control (MAC) entity; and,
indicating that one SDAP entity corresponds to one terminal.

### Claim 4 (depends on 3)

The method according to claim 3, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further comprises MAC ID.

### Claim 5 (depends on 3)

The method according to claim 3, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one PDU session, indicates that one SDAP entity corresponds to one PDCP entity, indicates that one SDAP entity corresponds to one MAC entity, or indicates that one SDAP entity corresponds to one terminal, the corresponding relationship information further comprises the association relationship indication information.

### Claim 6 (depends on 5)

The method according to claim 5, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one PDU session, or indicates that one SDAP entity corresponds to one PDCP entity, the method further comprises:
providing, by the upper layer, auxiliary information of the data packet, wherein the auxiliary information comprises the flow identifier.

### Claim 7 (depends on 5)

The method according to claim 5, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, or indicates that one SDAP entity corresponds to one terminal, the method further comprises:
providing, by the upper layer, auxiliary information of the data packet, wherein the auxiliary information comprises at least one of the flow identifier, the network slice identifier, or the session identifier.

### Claim 8

A data transmission method, applied to a data receiving end, comprising:
receiving, by a Packet Data Convergence Protocol (PDCP) entity, a data packet from a data transmitting end, and transmitting the data packet to a corresponding Service Data Adaptation Protocol (SDAP) entity according to a flow identifier carried by the data packet; and,
forwarding, by the SDAP entity, the data packet to an application protocol layer, or forwarding the data packet to a corresponding network slice, a flow and a Protocol Data Unit (PDU) session.

### Claim 9 (depends on 8)

The method according to claim 8, wherein forwarding by the SDAP entity the data packet to the corresponding network slice, flow and PDU session, comprises:
forwarding, by the SDAP entity, the data packet to the corresponding network slice, flow and PDU session, according to at least one of a network slice identifier, an SDAP identifier, the flow identifier, or a session identifier.

### Claim 10 (depends on 8)

The method according to claim 8, further comprising:
establishing the SDAP entity in advance, according to configuration information which is configured by a network or protocol-agreed; wherein the configuration information comprises at least one of a network slice identifier, a Data Radio Bearer (DRB) identifier, the flow identifier, a session identifier, or association relationship indication information; and,
indicating corresponding relationship information of the SDAP entity to an upper layer through the SDAP entity; wherein the corresponding relationship information comprises at least one of the network slice identifier, the DRB identifier, the flow identifier, the session identifier or an SDAP identifier.

### Claim 11 (depends on 10)

The method according to claim 10, wherein the association relationship indication information comprises any one of:
indicating that one SDAP entity corresponds to one flow;
indicating that one SDAP entity corresponds to one PDU session;
indicating that one SDAP entity corresponds to one PDCP entity;
indicating that one SDAP entity corresponds to one Medium Access Control (MAC) entity;
indicating that one SDAP entity corresponds to one terminal.

### Claim 12 (depends on 11)

The method according to claim 11, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one MAC entity, the configuration information further comprises an MAC ID.

### Claim 13 (depends on 11)

The method according to claim 11, wherein when the association relationship indication information indicates that one SDAP entity corresponds to one PDU session, indicates that one SDAP entity corresponds to one PDCP entity, indicates that one SDAP entity corresponds to one MAC entity, or indicates that one SDAP entity corresponds to one terminal, the corresponding relationship information further comprises the association relationship indication information.

### Claim 14

(canceled)

### Claim 15

(canceled)

### Claim 16

(canceled)

### Claim 17

(canceled)

### Claim 18

(canceled)

### Claim 19

(canceled)

### Claim 20

(canceled)

### Claim 21

(canceled)

### Claim 22

(canceled)

### Claim 23

(canceled)

### Claim 24

(canceled)

### Claim 25

(Cancelled)

### Claim 26

(canceled)

### Claim 27 (depends on 1)

A data transmitting end, comprising: a processor, a memory, a network interface and a user interface, wherein the processor, the memory, the network interface and the user interface are coupled through a bus system, the processor is configured to read a program from the memory to perform steps of the data transmitting method according to any of claim 1.

### Claim 28 (depends on 8)

A data receiving end, comprising: a processor, a memory a network interface and a user interface, wherein the processor, the memory, the network interface and the user interface are coupled through a bus system, the processor is configured to read a program from the memory to perform steps of the data transmitting method according to any of claim 8.

### Claim 29

(canceled)

### Claim 30 (depends on 1)

A computer readable storage medium, which stores a data transmission program, wherein when the data transmission program is executed by a processor, the processor is caused to perform steps of the data transmission method according to claim 1.

### Claim 31 (depends on 8)

A computer readable storage medium, which stores a data transmission program, wherein when the data transmission program is executed by a processor, the processor is caused to perform steps of the data transmission method according to claim 8.
