CN112004241A

CN112004241A - Data transmission method, terminal, network equipment and storage medium

Info

Publication number: CN112004241A
Application number: CN202010879748.9A
Authority: CN
Inventors: 吴玉清
Original assignee: Realme Mobile Telecommunications Shenzhen Co Ltd
Current assignee: Realme Mobile Telecommunications Shenzhen Co Ltd
Priority date: 2020-08-27
Filing date: 2020-08-27
Publication date: 2020-11-27
Anticipated expiration: 2040-08-27
Also published as: CN112004241B

Abstract

The embodiment of the application discloses a data transmission method, a terminal, network equipment and a storage medium, and the method comprises the steps of acquiring transmission state data of a first data resource bearing DRB in a current session; the first DRB bears the mapped IP data packet in the first application data flow IP flow; the mapped IP data packet carries first content of a service type field; if at least one of the transmission state data does not meet the preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of the service type field of the data packet to be mapped into second content from preset first content, and thus obtaining a redefined data packet; the second content corresponds to a second IP flow; carrying the redefined data packet in a second IP flow; mapping the second IP flow onto a second DRB according to the second content, and sending the second DRB; the second DRB is a DRB in the current session.

Description

Data transmission method, terminal, network equipment and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data transmission method, a terminal, a network device, and a storage medium.

Background

With the gradual completion of independent networking (SA) deployment in a 5th Generation mobile communication technology (5G) system, a 5G SA network can implement network slicing, and respond to different network requirements through different network slices. After selecting a network slice, the terminal establishes a corresponding Protocol Data Unit (PDU) session, the network issues a Quality of Service (Qos) rule set for the PDU session, the terminal maps an application Data stream (IP flow) into a Qos Data stream according to the Qos rule, and then maps the Qos Data stream to a DRB according to a mapping relationship between a Data Radio Bearer (DRB) configured for the PDU session and the Qos Data stream, thereby completing Data transmission on the DRB. Due to the limitation of the mapping mode, data transmission is not flexible enough, and the data transmission effect is influenced.

Disclosure of Invention

The embodiment of the application provides a data transmission method, a terminal, network equipment and a storage medium, and improves the data transmission effect.

The technical scheme of the application is realized as follows:

the embodiment of the application provides a data transmission method, which is applied to a terminal and comprises the following steps:

acquiring transmission state data of a first data resource bearing DRB in a current session; the first DRB bears a mapped IP data packet in a first application data flow IP flow; the mapped IP data packet carries first content of a service type field; if at least one of the transmission state data does not meet a preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of the service type field of the data packet to be mapped into second content from preset first content, and thus obtaining a redefined data packet; the second content corresponds to a second IP flow; carrying the redefined data packet in the second IP flow; mapping the second IP flow onto the second DRB according to the second content, and sending the second DRB; the second DRB is a DRB in the current session.

The embodiment of the application provides a data transmission method, which is applied to network equipment and comprises the following steps:

receiving a second Data Resource Bearer (DRB) in the current session; the second DRB carries redefined data packets in a second application data flow IP flow; when at least one piece of transmission state data of the first DRB does not meet a preset condition, redefining the content of the service type field of the data packet to be mapped of the first IP flow into a data packet obtained by redefining the first content into the second content; the second content corresponds to a second IP flow; the first DRB bears the mapped data packet in the first IP flow; the first DRB is a DRB in the current session.

The embodiment of the application provides a terminal, the terminal includes:

an obtaining module, configured to obtain transmission state data of a DRB carried by a first data resource in a current session; the first DRB bears a mapped IP data packet in a first application data flow IP flow; the mapped IP data packet carries first content of a service type field;

the obtaining module is further configured to obtain a data packet to be mapped in the first IP flow if at least one of the transmission state data does not satisfy a preset condition;

a redefining module, configured to redefine the content of the service type field of the packet to be mapped from a preset first content to a second content, so as to obtain a redefined packet; the second content corresponds to a second IP flow; carrying the redefined data packet in the second IP flow;

a mapping module, configured to map the second IP flow to the second DRB according to the second content, and send the second DRB; the second DRB is a DRB in the current session.

An embodiment of the present application provides a network device, where the network device includes:

a receiving module, configured to receive a second data resource bearer DRB in a current session; the second DRB carries redefined data packets in a second application data flow IP flow; when at least one piece of transmission state data of the first DRB does not meet a preset condition, redefining the content of the service type field of the data packet to be mapped of the first IP flow into a data packet obtained by redefining the first content into the second content; the second content corresponds to a second IP flow; the first DRB bears the mapped data packet in the first IP flow; the first DRB is a DRB in the current session.

The embodiment of the application provides a terminal, the terminal includes:

a first processor and a first memory for storing a computer program operable on the first processor; wherein the first processor is configured to execute the steps of the terminal-side data transmission method when the computer program is executed.

a second processor and a second memory for storing a computer program operable on the second processor; and the second processor is used for executing the steps of the network equipment side data transmission method when the computer program is run.

The present embodiments provide a storage medium storing one or more computer programs, which are executable by one or more processors to implement the steps of the above-described data transmission method.

According to the data transmission method, the terminal, the network device and the storage medium provided by the embodiment of the application, the terminal obtains the transmission state data of the DRB carried by the first data resource in the current session; the first DRB bears the mapped IP data packet in the first application data flow IP flow; the mapped IP data packet carries first content of a service type field; if at least one of the transmission state data does not meet the preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of the service type field of the data packet to be mapped into second content from preset first content, and thus obtaining a redefined data packet; the second content corresponds to a second IP flow; carrying the redefined data packet in a second IP flow; mapping the second IP flow onto a second DRB according to the second content, and sending the second DRB; the second DRB is a DRB in the current session; that is to say, the terminal can redefine the content of the service type field of the data packet that needs to be mapped on the first DRB under the condition that the transmission state of the first DRB is not good, so that the data packet can be mapped on the second DRB for transmission, thereby increasing the flexibility of data transmission and improving the data transmission effect.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 2 is a first schematic flow chart of a data transmission method according to an embodiment of the present application;

fig. 3 is a schematic diagram of a data transmission process according to an embodiment of the present application;

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

fig. 5 is a schematic flow chart of a data transmission method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a Qos rule set according to an embodiment of the present application;

fig. 7 is an information diagram of a filtering field in a Qos rule according to an embodiment of the present application;

fig. 8 is a schematic diagram of RRC connection reconfiguration information according to an embodiment of the present application;

fig. 9 is a schematic flowchart of a data transmission method according to an embodiment of the present application;

fig. 10 is a schematic interaction diagram of a terminal and a network device according to an embodiment of the present application;

fig. 11 is a first schematic structural component diagram of a terminal according to an embodiment of the present disclosure;

fig. 12 is a first schematic structural component diagram of a network device according to an embodiment of the present application;

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

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

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

An embodiment of the present application provides a schematic structural diagram of a communication system, as shown in fig. 1, the communication system may include: a terminal 101 and a network device 102.

The terminal 101 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication capability, as well as various forms of user equipment, Mobile Stations (MSs), terminals (terminal devices), and so forth. For convenience of description, the above-mentioned devices are collectively referred to as a terminal. The network device 102 and the terminal 101 communicate with each other through some air interface technology, for example, a Uu interface.

The network device 102 may be an evolved NodeB (eNB), an Access Point (AP), or a relay station in a Long Term Evolution (LTE) system, or may be a base station (e.g., a gNB or a Transmission Point (TRP)) in a 5G system, and in a 5G NR-U system, a device having a base station function is referred to as a gnnodeb or a gNB. The description of "base station" may change as communication technology evolves. The Network device 102 may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, a Mobile switching center, a relay Station, an Access Point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a Network device in a future communication System, and may also be a Base Station in an NTN System (such as a gNB or a Transmission Point (TRP), a Global System for Mobile communication (GSM) System, or a Base Station in a Code Division Multiple Access (CDMA) System (Base Transceiver Station, BTS), or a Base Station in a Wideband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) System (NodeB, NB), and the like, which is not limited in this application.

In addition, in this embodiment of the present application, the network device 102 provides a service for a cell, and the terminal 101 communicates with the network device 102 through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device 102 (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell (small cell), where the small cell may include: urban cell (etro cell), Micro cell (Micro cell), Pico cell (Pico cell), Femto cell (Femto cell), these small cells have the characteristics that coverage is little, transmission power is low, are applicable to and provide high-speed data transmission service. In addition, the cell may also be a super cell (supercell).

In the 5G communication era, due to the diversification of terminals accessing the network, the network needs to meet diversified service requirements, such as time-delay, reliability, security, etc., therefore, a network slicing technology can be adopted to divide a plurality of logical networks on an independent physical network, so that different network requirements can adopt different network slices to provide differential services through the network slices. With the completion of the deployment of the 5G SA network, the differential service with different slices and different charging can be provided for the user; for example, a low-delay game slice, a high-bandwidth data transmission slice, a high-access low-data-requirement internet-of-things mass access, a vehicle network slice with an extremely high real-time requirement, and the like.

In this embodiment, the terminal may select a network slice according to a UE Route Selection Policy (URSP) rule of a User Equipment (User Equipment, UE), where different network slices correspond to different PDU sessions, and map an IP flow to a Qos flow according to Qos rules issued by a network, and then map a Qos Data flow to a Radio bearer (Data Radio bearer, DRB) according to a mapping relationship between the DRB and the Qos Data flow, thereby completing Data transmission on the DRB.

The mapping relationship between the DRB and the Qos data stream may be configured by a network, or may be the same mapping relationship determined according to the mapping relationship between the downlink DRB and the Qos data stream, which is not limited in this embodiment.

In the embodiment of the present application, the mapping process from IP flow to Qos flow, and then the mapping from Qos flow to DRB are performed according to a fixed mapping relationship, that is, the transmission effect of DRB depends on the stability and reliability of the network itself; a fixed network time-frequency resource is different in different time periods and different areas; therefore, if mapping is performed according to a fixed mapping relationship, the uplink transmission effect of the mobile phone will be affected when the corresponding DRB transmission performance cannot be guaranteed.

An embodiment of the present application provides a data transmission method, as shown in fig. 2, applied to a terminal, where the method includes:

s101, acquiring transmission state data of a first data resource bearing DRB in a current session; the first DRB bears the mapped IP data packet in the first application data flow IP flow; the mapped IP data packet carries first content of a service type field;

in the embodiment of the application, at least one PDU session may be established between the terminal and the network device, and the current session is one PDU session in the at least one PDU session.

In the embodiment of the application, after the current session is established, the terminal can perform data transmission on at least one DRB configured for the current session; therefore, the terminal may acquire transmission status data of a first DRB of the at least one DRB, the transmission status data of the first DRB being used to characterize a transmission effect of the first DRB.

In some embodiments of the present application, the transmission status data may include at least one of: packet loss rate, retransmission rate, round trip delay, number of handshake failures, transmission rate, etc. Wherein, different transmission state data are used for representing different transmission effects; for example, the packet loss rate is used to represent the reliability of transmission, and the lower the packet loss rate is, the higher the reliability is, the higher the packet loss rate is, the lower the reliability is; the transmission rate is used to characterize the throughput of the transmission, and may also characterize the round trip delay, where a lower transmission rate indicates a higher round trip delay or a lower throughput, and a higher transmission rate indicates a lower round trip delay or a higher throughput.

In this embodiment, the terminal may obtain the transmission data state in real time, or may obtain the transmission data state according to a specific time interval, which is not limited in this embodiment.

It should be noted that, the terminal issues an IP data packet to the TCP/IP layer through the application program to form at least one IP flow; mapping the data packet in the at least one IP flow to at least one QoS flow, and then mapping the at least one QoS flow to at least one DRB by the terminal; in this way, the data packet sent by the application program may be carried on the DRB for transmission, or may be carried on a plurality of DRBs for transmission, which is not limited in this embodiment.

In the embodiment of the present application, the mapped data packet in the first IP flow is carried on the first DRB. The transmission effect of the first DRB may affect the transmission effect of the mapped packet in the first IP flow.

Referring to fig. 3, fig. 3 shows a data transmission diagram. As shown in fig. 3, the application program issues data packets to form 5 IP flows, which are mapped onto 3 Qos flows, and then the 3 Qos flows are mapped onto 2 DRBs for transmission.

In the embodiment of the application, the filtering field of the IP data packet sent by the application program comprises a service type field; different contents of the service type fields indicate different service types of the data packets, and different transmission effects corresponding to different service types are different; that is, the contents of different service type fields indicate different transmission effects.

In the embodiment of the present application, the type of service field may be a TOS field; the TOS field is an 8-bit field that includes a 3-bit priority subfield, a 4-bit TOS subfield, and 1-bit unused bits.

Fig. 4 shows a format schematic diagram of a data packet, and as shown in fig. 4, the packet header may include information such as version, header length, service type, identifier, source IP address, and destination IP address. Wherein the service type is the TOS field of 8 bits.

In the embodiment of the application, the content of the TOS field is the content of the TOS subfield; here, only one bit of the 4 bits is 1; wherein, each bit is set to 1, so as to obtain 4 service types; respectively as follows: minimum delay, maximum throughput, maximum reliability, and minimum cost; each bit of 4 bits is 0 in total, which indicates a general service.

In the embodiment of the present application, different applications may correspond to different service types. For example, an application program for transmitting interactive data may correspond to a service type with minimum delay, and the TOS subfield of the TOS field of a data packet sent by the application may be set to the content corresponding to the minimum delay.

In the embodiment of the present application, different services of the same application program may also correspond to different service types. Here, one application may relate to a plurality of services; for example, a UDP query by a DNS application may correspond to a minimum latency, while a regional transfer may correspond to a maximum throughput.

Table 1 shows the corresponding TOS field contents of the application. As shown in table 1, the TOS field content includes 4 types, where the service type corresponding to "1000" is the minimum delay, the service type corresponding to "0100" is the maximum throughput, the service type corresponding to "0010" is the highest reliability, and the service type corresponding to "0001" is the minimum cost; the Telnet and the Rlogic are mainly used for transmitting a small amount of interactive data, and the minimum transmission delay is required; simple Network Management Protocol (SNMP) requires the highest reliability; a Bootstrap Protocol (BOOTP Protocol, BOOTP) is a general service; among them, user Network News (NNTP) is the only application requiring the minimum cost.

TABLE 1

In the embodiment of the application, the service type field of the data packet sent by the application program is configured according to the content of the TOS field defined in the table 1; the terminal can bear the data packet on the corresponding DRB for transmission according to the content of the TOS field, so that the transmission effect corresponding to the content of the TOS field is realized.

In this embodiment, the TOS field content of the data packet in the first IP flow is the first content, so that the terminal can carry the data of the first IP flow on the first DRB for transmission.

S102, if at least one of the transmission state data does not meet a preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of the service type field of the data packet to be mapped into second content from preset first content, and thus obtaining a redefined data packet; the second content corresponds to a second IP flow; carrying the redefined data packet in a second IP flow;

in this embodiment of the application, after the terminal acquires the transmission state data of the first DRB, the terminal may acquire the data packet to be mapped in the first IP flow under the condition that at least one of the transmission state data does not satisfy the preset condition, redefine the content of the service type field of the data packet to be mapped, modify the content of the service type field of the data packet to be mapped into the second content, and obtain the redefined data packet.

In this embodiment, the second content corresponds to the second IP flow, and therefore, the redefined data packet is carried in the second IP flow for mapping.

In this embodiment of the present application, at least one of the transmission status data of the first DRB that does not satisfy the preset condition represents that the transmission effect of the first DRB is not good.

In this embodiment of the present application, the transmission status data of the first DRB does not satisfy the preset condition, and may be that the transmission status data of the first DRB is not within a preset range; or the transmission status data of the first DRB is not within a preset range and the duration time exceeds a preset time; the setting can be performed as needed, and the embodiment of the present application is not limited.

It should be noted that each transmission status data has a corresponding preset range; for example, the preset range corresponding to the time delay may be less than 460 ms; the predetermined range of the packet loss rate may be less than 0.2%.

In the embodiment of the application, different transmission state data can correspond to different preset conditions; for example, the time delay does not satisfy the preset condition, and the time delay is greater than or equal to 460ms and the duration time exceeds 1 s; the packet loss rate does not satisfy the preset condition, and the packet loss rate is greater than or equal to 0.2%.

In this embodiment of the present application, the number of at least one of the transmission status data may be one, two, three, or the like, which does not exceed the number of the transmission status data, and this is not limited in this embodiment of the present application.

In the embodiment of the present application, at least one of the transmission status data may be any at least one, and may also be at least one designated data.

Illustratively, the transmission state data includes a packet loss rate and a transmission delay, and at least one of the terminals of the transmission state data may be the packet loss rate or the transmission delay, and may also be the packet loss rate and the transmission delay.

S103, mapping the second IP flow to a second DRB according to the second content, and sending the second DRB; the second DRB is a DRB in the current session.

In the embodiment of the application, the terminal maps the second IP flow to the second DRB of the current session for transmission according to the second content; that is, the redefined data packet will be mapped onto the second DRB.

It should be noted that, the content of the service type field of the data packet of the first IP flow is a first content, and according to the first content, the terminal maps the first IP flow to a first Qos flow, and then maps the first Qos flow to a first DRB for transmission; and the content of the service type field of the data packet in the second IP flow is the second content, so the terminal maps the second IP flow to the second Qos flow according to the second content, and then may map the second Qos flow to the second DRB for transmission.

It can be understood that, the terminal obtains the transmission state data of the first DRB in the current session, redefines the content of the service type field of the data packet to be mapped in the first IP flow when at least one of the transmission state data does not meet the preset condition, redefines the content of the service type field from the first content to the second content, thereby obtaining the redefined data packet; the redefined data packet is carried in the second IP flow, so that the redefined data packet will be transmitted on the second DRB after the terminal maps the second IP flow onto the second DRB, thereby improving the data transmission effect.

In some embodiments of the present application, redefining the content of the service type field of the data packet to be mapped from the preset first content to the second content in S102, as shown in fig. 5, may include:

s201, acquiring a first corresponding relation; the first corresponding relation comprises a corresponding relation between the content of the service type field and at least one DRB;

in the embodiment of the present application, in the current session, multiple Qos flows may be mapped on one DRB, that is, the contents of multiple TOS fields may correspond to one DRB. In order to enable the redefined data packet carrying the second content to be carried on the second DRB, the terminal needs to determine which content of the service type field does not correspond to the first DRB.

In an embodiment of the present application, the first correspondence includes a correspondence between the content of the service type field and at least one DRB. According to the first corresponding relationship, the terminal can determine on which DRB the data packets containing the contents of the different service type fields can be carried for transmission respectively.

In this embodiment of the present application, at least one DRB in the first corresponding relationship is all DRBs corresponding to the contents of different service type fields; the at least one DRB includes a first DRB and a second DRB.

S202, determining third content according to the first corresponding relation; the third content is the content corresponding to the third DRB; the third DRB is a DRB of the at least one DRB except the first DRB;

in this embodiment of the application, after obtaining the first corresponding relationship, the terminal may determine a third DRB from the at least one DRB; the third DRB is a DRB other than the first DRB among the at least one DRB. As such, the second DRB may be one of the third DRBs.

In this embodiment, the terminal may determine, according to the first corresponding relationship, a field content corresponding to the third DRB as the third content.

S203, determining second content from the third content;

s204, redefining the first content into the second content.

In this embodiment, the third content is a content corresponding to the third DRB, and the third content includes at least one content, so that after determining the third content, the terminal may determine one content from the third content as the second content, and redefine the first content as the second content. In this way, redefined data packets carrying the second content may be carried on a second DRB different from the first DRB.

In this embodiment of the application, the terminal may take any one of the third contents as the second content; the content in the third content may also be sorted according to a preset priority, and the content with the highest priority is used as the second content, which is not limited in the embodiment of the present application.

Illustratively, in the current session, "0001" and "0100" correspond to DRB1, "0010" corresponds to DRB2, and "0001" corresponds to DRB 3; referring to table 1, the content of the default TOS field of the data packet for data transmission sent by the FTP is "0100", and a first IP flow is formed corresponding to the service type with the maximum throughput, and is mapped on the DRB1 for transmission. When the transmission state data of the DRB1 does not satisfy the preset condition, the terminal determines that the third DRB is DRB2 and DRB3, and the contents corresponding to the DRB2 and DRB3 are "0010" and "0001", respectively, as the third content; the terminal may determine any one of "0010" and "0001" as the second content; alternatively, if "0010" is higher in priority than "0001" in the third content, the terminal determines "0010" as the second content.

It should be noted that, if the terminal redefines the TOS field of the packet to be mapped for FTP data transmission from "0100" to "0010", resulting in a redefined packet, the redefined packet forms a second IP flow, the second IP flow is mapped for transmission on the DRB2, and the DRB2 is a second DRB.

It can be understood that the terminal may determine the second content corresponding to the second DRB according to the corresponding relationship between the content of the service type field and the DRB, so that the terminal redefines the content of the service type field of the packet to be mapped from the first content to the second content when the transmission status data of the first DRB does not satisfy the preset condition, and after obtaining the redefined packet, may ensure that the redefined packet is mapped to the second DRB different from the first DRB for transmission.

In some embodiments of the present application, the at least one of the transmission status data not satisfying the preset condition may include one of the transmission status data not satisfying the preset condition, or a plurality of the transmission status data not satisfying the preset condition.

In some embodiments of the present application, if one of the transmission status data does not satisfy the preset condition, the second content is a content of a service field corresponding to the transmission status data in the third content.

In the embodiment of the present application, different transmission state data are used to represent different transmission effects, and different contents of the service type field correspond to different transmission effects, so that there may be a corresponding relationship between the transmission state data and the contents of the service type field.

Illustratively, referring to table 1, the transmission delay corresponds to the contents "1000" of the TOS field; the service type of '0010' is the minimum delay; the packet loss rate corresponds to the content '0010' of the TOS field; the service type of "0010" is the highest reliability.

In this embodiment of the application, if one of the transmission status data does not satisfy the preset condition, the terminal may further determine whether the third content includes the content of the service type field corresponding to the transmission status data, and if so, take the content as the second content.

Illustratively, in the current session, "0001" and "0100" correspond to DRB1, "0010" corresponds to DRB2, and "0001" corresponds to DRB 3; referring to table 1, the default TOS field content of the data packet for data transmission sent by the FTP is the first content "0100", and the service type corresponding to the maximum throughput is carried in the first IP flow and is mapped on the DRB1 for transmission. The first transmission state data is the packet loss rate in the transmission state data, and when the packet loss rate of the DRB1 is greater than 0.2%, the terminal determines that the third DRB is DRB2 and DRB3, and the contents corresponding to the DRB2 and DRB3 are "0010" and "0001", respectively, and are the third content; the highest reliability is represented by the content '0010' of the TOS field corresponding to the packet loss rate; accordingly, the terminal may determine "0010" as the second content; and redefining the content of the TOS field of the data packet to be mapped in the first IP flow from '0100' to '0010', obtaining a redefined data packet, and transmitting the second IP flow carried in the redefined data packet on the DRB2 in a mapping manner, thereby improving the reliability of FTP data transmission.

It can be understood that, when the first transmission status data does not satisfy the preset condition, the terminal needs to take the content corresponding to the first transmission status data as the second content to purposefully improve the transmission effect of the first service type.

In some embodiments of the present application, if a plurality of transmission status data do not satisfy the preset condition, the terminal may determine, from the third content, contents of a plurality of service type fields corresponding to the plurality of transmission status data, that is, a fourth content; and determining the second content from the fourth content.

In this embodiment of the application, the terminal determines that the implementation of the second content from the contents of the multiple service type fields may be the same as the implementation of S203, and details are not described here again.

In some embodiments of the present application, if at least one of the transmission status data does not satisfy the preset condition in S102, obtaining the implementation after the data packet to be mapped in the first IP flow may further include:

s401, copying a data packet to be mapped to obtain a copied data packet;

s402, redefining the content of the service type field of the copied data packet from the first content to the second content to obtain a redefined data packet.

In this embodiment of the application, if at least one of the transmission status data of the first DRB does not satisfy the preset condition, the terminal may copy the data packet to be mapped in the first IP flow to obtain a copied data packet, and redefine the content of the service type field of the copied data packet to the second content to obtain a redefined data packet, so that the redefined data packet is transmitted on the second DRB, and the content of the service type field of the original data packet to be mapped is still the default first content and is still carried on the first DRB for transmission; that is to say, under the condition that the transmission effect of the first DRB is not good, after one copy of the data packet originally carried on the first DRB is made, two copies of the data packet to be mapped are obtained, wherein one copy is carried on the first DRB for transmission, and the other copy is carried on the second DRB for transmission, so that the data transmission effect is improved, and the reliability of data transmission is ensured.

In some embodiments of the present application, the first correspondence is determined based on a set of Qos rules and a correspondence of Qos flow and DRB; the Qos rule set is used for characterizing the correspondence between the content of the service type field and the Qos flow.

In this embodiment of the present application, the Qos rule set includes at least one Qos rule, where one Qos rule corresponds to one Qos Flow, and different Qos flows have different identities QFI (QFI).

In the embodiment of the present application, each Qos rule includes filtering field information, where the filtering field information includes filtering field identification and content of the filtering field. Wherein, the filtering field identifies the type of the filtering field, i.e. which filtering fields are in the Qos rule; the content of the filtering field indicates the content of the filtering field in the Qos rule.

Fig. 6 is a schematic diagram of Qos rule set composition information. As shown in fig. 6, the addressing unit in the Qos rule set composition information is octet, i.e. 8 bits. As can be seen, the Qos rule set list includes the length of the Qos rule set composition information and n Qos rules, where the n Qos rules are Qos rule 1 and Qos rule 2 … … Qos rule n in sequence.

The information of the filtering field of each Qos rule is shown in fig. 7, where the filtering field information of one Qos rule includes N filtering fields, and each filtering field includes a filtering direction, a field identifier, a field content length, and a field content; wherein different field identifications characterize different filter field types.

In some embodiments of the present application, the field identification may be represented by 8 bits; for example, "01110000" indicates the TOS field, "10000001" indicates the destination MAC address, etc.

It should be noted that the content of the service type field corresponding to different Qos rules is different; the terminal may determine Qos rules including the service type field according to the filtered field identifier, and further determine a corresponding relationship between the content of the service type field and the Qos rules, thereby determining a corresponding relationship between the content of the service type field and the Qos flow.

In the embodiment of the application, the terminal can determine the corresponding relationship between the content of the service type field and the Qos flow according to the Qos rule set, and determine the corresponding relationship between the content of the service type field and the DRB according to the corresponding relationship between the Qos flow and the DRB, so as to obtain the first corresponding relationship.

In the embodiment of the present application, the Qos rule set and the corresponding relationship between Qos flow and DRB may be preset in a standard, or may be issued by a network device when a current session is established or modified, or may be self-defined by a terminal; the embodiments of the present application are not limited thereto.

In some embodiments of the present application, the correspondence between the Qos flow and the DRB may be issued by the network device through Radio Resource Control (RRC) connection reconfiguration information.

Exemplarily, fig. 8 shows a schematic diagram of RRC connection reconfiguration information, as shown in fig. 8, in a PDU session with a PDU session identifier (PDU-session) of 5, 3 Qos flows are mapped to a DRB with an identifier (DRB-identity) of 1, where the 3 Qos flows are identified as QFI 11, QFI 12, and QFI 13, respectively.

It can be understood that the terminal may determine the corresponding relationship between the content of the service type field and the DRB according to the Qos rule set and the corresponding relationship between Qos flow and DRB, obtain a first corresponding relationship, and then determine a second content corresponding to a second DRB according to the first corresponding relationship; in this way, the terminal can redefine the content of the service field of the data packet to be mapped in the first IP flow from the first content to the second content, and after obtaining the redefined data packet, the redefined data packet can be carried to a second DRB different from the first DRB for transmission, so as to improve the data transmission effect.

In some embodiments of the present application, mapping the second IP flow onto the second DRB according to the second content in S103 includes:

s501, according to the second content, determining a target Qos rule from at least one Qos rule in the Qos rule set;

in this embodiment, the terminal may determine Qos rules including a service type field from the Qos rule set, and then determine, from the Qos rules, a target Qos rule in which the content of the service type field is the second content.

S502, mapping the second IP flow to a target Qos flow corresponding to the target Qos rule;

in the embodiment of the application, the terminal confirms the target Qos rule, which is equivalent to determining the target QFI, and the Qos flow marked with the target QFI is the target Qos flow. In this way, the terminal can map the IP flow to the corresponding target Qos flow.

S503, mapping the target Qos flow to a second DRB according to the corresponding relation between the Qos flow and the DRB.

In this embodiment of the present application, after the terminal maps the IP flow to the corresponding target Qos flow, the target Qos flow may be mapped to the corresponding DRB according to the mapping relationship between the Qos flow and the DRB, where the corresponding DRB is the second DRB.

An embodiment of the present application provides a data transmission method, as shown in fig. 9, applied to a network device, where the method includes:

s601, receiving a second data resource bearing DRB in the current session; the second DRB carries redefined data packets in a second application data flow IP flow; redefining the data packet into a data packet obtained by redefining the content of the service type field of the data packet to be mapped of the first IP flow into second content from first content under the condition that at least one of the transmission state data of the first DRB does not meet a preset condition; the second content corresponds to a second IP flow; the first DRB bears the mapped data packet in the first IP flow; the first DRB is a DRB in the current session.

In some embodiments of the present application, the transmission status data comprises at least one of: packet loss rate, retransmission rate, transmission delay, number of handshake failures, and transmission rate.

In some embodiments of the present application, the second content is determined from the third content; the third content is the content corresponding to the third DRB; the third DRB is the DRB except the first DRB in the at least one DRB determined according to the first corresponding relation; the first correspondence includes a correspondence between the content of the service type field and at least one DRB.

In some embodiments of the present application, at least one of the transmission status data does not satisfy a preset condition, including one of:

one of the transmission status data does not satisfy a preset condition;

a plurality of the transmission status data do not satisfy a preset condition.

In some embodiments of the present application, when one of the transmission status data does not satisfy a preset condition, the second content is a content of a service field corresponding to the transmission status data in a third content.

In some embodiments of the present application, when a plurality of the transmission status data do not satisfy a preset condition, the second content is one of fourth contents; the fourth content is a plurality of contents determined from the contents of the service field corresponding to the transmission status data in the third content.

In some embodiments of the present application, in the case that the redefined data packet is that the transmission status data does not satisfy the preset condition, the redefined data packet is obtained by redefining the content of the service type field of the duplicated data packet from the first content to the second content; the copy data packet is obtained by copying the data packet to be mapped.

In some embodiments of the present application, the first correspondence is determined based on a set of Qos rules and a correspondence of Qos flow and DRB; the Qos rule set is used for representing the corresponding relation between the content of the TOS field and the QoS data flow Qos flow.

In some embodiments of the present application, when a current session is established or modified, the network device issues the correspondence between Qos flow and DRB to the terminal.

In some embodiments of the present application, the second DRB is obtained by mapping the target Qos flow according to a correspondence between the Qos flow and the DRB; the target Qos flow corresponds to the target Qos rule; the target Qos rule is determined from at least one Qos rule of the set of Qos rules according to the second content.

It should be noted that, the description of the second DRB received by the network device is detailed in the data transmission method at the terminal side, and is not described herein again.

It is to be appreciated that the data packets received by the network device on the second DRB include redefined data packets. That is, the data packet originally received by the network device on the first DRB is redefined by the content of the service type field, so that the network device can receive the data packet on the second DRB, thereby improving the data transmission effect.

Based on the foregoing embodiments, the present application provides an interaction diagram of a terminal and a network device, as shown in fig. 10, the method includes:

s701, the terminal acquires transmission state data of a first data resource bearing DRB in the current session; the first DRB bears the mapped IP data packet in the first application data flow IP flow; the mapped IP data packet carries first content of a service type field;

s702, if at least one of the transmission state data does not meet a preset condition, the terminal acquires a data packet to be mapped in the first IP flow;

s703, redefining the content of the service type field of the data packet to be mapped into second content from preset first content by the terminal, thereby obtaining a redefined data packet; carrying the redefined data packet in a second IP flow;

s704, the terminal maps the second IP flow to the second DRB according to the second content;

s705, the terminal sends the second DRB.

In the embodiment of the application, a terminal acquires transmission state data of a first DRB in a current session, redefines the content of a service type field of a data packet to be mapped in a first IP flow when at least one of the transmission state data does not meet a preset condition, redefines the content of the service type field from first content to second content, and accordingly obtains a redefined data packet; the redefined data packet is carried in the second IP flow, so that after the terminal maps the second IP flow onto the second DRB, the redefined data packet will be transmitted on the second DRB, and the network device will receive the redefined data packet on the second DRB, that is, the data received by the network device on the second DRB includes the data that should be received on the first DRB; therefore, the flexibility of data transmission is improved, and the data transmission effect is improved.

An embodiment of the present application provides a terminal, as shown in fig. 11, where the terminal 18 includes:

an obtaining module 181, configured to obtain transmission state data of a first data resource bearer DRB in a current session; the first DRB bears a mapped IP data packet in a first application data flow IP flow; the mapped IP data packet carries first content of a service type field;

the obtaining module 181 is further configured to obtain a data packet to be mapped in the first IP flow if at least one of the transmission state data does not satisfy a preset condition;

a redefining module 182, configured to redefine the content of the service type field of the packet to be mapped from a preset first content to a second content, so as to obtain a redefined packet; the second content corresponds to a second IP flow; carrying the redefined data packet in the second IP flow;

a mapping module 183, configured to map the second IP flow onto the second DRB according to the second content, and send the second DRB; the second DRB is a DRB in the current session.

In some embodiments, the transmission status data comprises at least one of:

packet loss rate, retransmission rate, transmission delay, number of handshake failures, and transmission rate.

In some embodiments, the redefining module 182 is further configured to obtain the first corresponding relationship; the first correspondence comprises a correspondence between the content of the service type field and at least one DRB; determining third content according to the first corresponding relation; the third content is a content corresponding to a third DRB; the third DRB is a DRB of the at least one DRB except the first DRB; determining the second content from the third content; redefining the first content as the second content.

In some embodiments, at least one of the transmission status data does not satisfy a preset condition, including one of:

one of the transmission status data does not satisfy a preset condition;

a plurality of the transmission status data do not satisfy a preset condition.

In some embodiments, when one of the transmission status data does not satisfy a preset condition, the second content is a content of a service field corresponding to the transmission status data in a third content.

In some embodiments, when a plurality of the transmission status data do not satisfy a preset condition, the second content is one of fourth contents; the fourth content is a plurality of contents determined from the contents of the service field corresponding to the transmission status data in the third content.

In some embodiments, the redefining module 182 is further configured to duplicate the data packet to be mapped to obtain a duplicate data packet; redefining the content of the service type field of the duplicate packet from the first content to a second content, thereby obtaining the redefined packet.

In some embodiments, the first correspondence is determined based on a set of Qos rules and a correspondence of Qos flow and DRB; and the Qos rule set is used for representing the corresponding relation between the content of the service type field and the QoS flow.

In some embodiments, the Qos rule and the corresponding relationship between Qos flow and DRB are issued by the network device when the current session is established or modified.

In some embodiments, the mapping module 183 is further configured to determine a target Qos rule from at least one Qos rule in the Qos rule set according to the second content; mapping the second IP flow to a target Qos flow corresponding to the target Qos rule; and mapping the target Qos flow to the second DRB according to the corresponding relation between the Qos flow and the DRB.

An embodiment of the present application provides a network device, as shown in fig. 12, where the network device 19 includes:

a receiving module 191, configured to receive a second data resource bearer DRB in the current session; the second DRB carries redefined data packets in a second application data flow IP flow; when at least one piece of transmission state data of the first DRB does not meet a preset condition, redefining the content of the service type field of the data packet to be mapped of the first IP flow into a data packet obtained by redefining the first content into the second content; the second content corresponds to a second IP flow; the first DRB bears the mapped data packet in the first IP flow; the first DRB is a DRB in the current session.

In some embodiments, the transmission status data comprises at least one of:

In some embodiments, the second content is determined from a third content; the third content is a content corresponding to a third DRB; the third DRB is a DRB except the first DRB in at least one DRB determined according to the first corresponding relation; the first correspondence includes a correspondence between the content of the service type field and the at least one DRB.

one of the transmission status data does not satisfy a preset condition;

a plurality of the transmission status data do not satisfy a preset condition.

In some embodiments, the redefined data packet is obtained by redefining the content of the service type field of the duplicated data packet from the first content to the second content in case that the transmission state data does not meet the preset condition; the copy data packet is obtained by copying the data packet to be mapped.

In some embodiments, the network device further includes a sending module, configured to send the Qos flow and the DRB to the terminal when the current session is established or modified.

In some embodiments, the second DRB is obtained by mapping a target Qos flow according to the correspondence between the Qos flow and the DRB; the target Qos flow corresponds to a target Qos rule; the target Qos rule is determined from at least one Qos rule of the set of Qos rules according to the second content.

Fig. 13 is a schematic structural composition diagram of a terminal according to an embodiment of the present application, and as shown in fig. 13, the terminal 20 includes a first memory 2001, a first processor 2002, and a computer program stored in the first memory 2001 and operable on the first processor 2002; wherein the first processor is configured to execute the transmission method of the channel at the terminal side as in the foregoing embodiments when running the computer program.

It will be appreciated that the terminal 20 also includes a bus system 2003; the various components in the terminal 20 are coupled together by a bus system 2003. It is understood that a bus system 2003 is used to enable the connection communication between these components. The bus system 2003 includes a power bus, a control bus, and a status signal bus in addition to the data bus.

Fig. 14 is a schematic structural composition diagram of a network device according to an embodiment of the present application, and as shown in fig. 14, the network device 21 includes a second memory 2101, a second processor 2102, and a computer program stored in the second memory 2101 and operable on the second processor 2102; the second processor is configured to execute the transmission method of the channel on the network device side in the foregoing embodiments when the computer program is executed.

It will be appreciated that the network device 21 also includes a bus system 2103; the various components in network device 21 are coupled together by a bus system 2103. It is understood that the bus system 2103 is used to enable connected communication between these components. The bus system 2103 comprises, in addition to a data bus, a power bus, a control bus and a status signal bus.

It will be appreciated that the memory in this embodiment can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic Random Access Memory (FRAM), a Flash Memory (Flash Memory), a magnetic surface Memory, an optical Disc, or a Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced Synchronous DRAM), Direct Memory Access (DRAM), and Direct Memory Access (DRDRU). The memories described in the embodiments of the present application are intended to comprise, without being limited to, these and any other suitable types of memory.

The method disclosed in the embodiments of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor described above may be a general purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium having a memory and a processor reading the information in the memory and combining the hardware to perform the steps of the method.

The embodiment of the present application further provides a storage medium, on which a computer program is stored, and when the storage medium is located in a terminal, the computer program is executed by a first processor to implement the steps in the terminal-side data transmission method according to the embodiment of the present application.

The embodiment of the present application further provides a storage medium, on which a computer program is stored, where when the storage medium is located in a network device, the computer program is executed by a second processor to implement the steps in the network device side data transmission method according to the embodiment of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described device embodiments are merely illustrative, for example, the division of the modules is only one logical functional division, and there may be other division ways in actual implementation, such as: multiple modules or components may be combined, or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the coupling, direct coupling or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection between the devices or modules may be electrical, mechanical or other.

Claims

1. A data transmission method is applied to a terminal and comprises the following steps:

acquiring transmission state data of a first data resource bearing DRB in a current session; the first DRB bears a mapped IP data packet in a first application data flow IP flow; the mapped IP data packet carries first content of a service type field;

if at least one of the transmission state data does not meet a preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of the service type field of the data packet to be mapped into second content from preset first content, and thus obtaining a redefined data packet; the second content corresponds to a second IP flow; carrying the redefined data packet in the second IP flow;

mapping the second IP flow onto the second DRB according to the second content, and sending the second DRB; the second DRB is a DRB in the current session.

2. The method of claim 1, wherein the transmission status data comprises at least one of:

3. The method according to any one of claims 1-2, wherein redefining the content of the service type field of the data packet to be mapped from a preset first content to a second content comprises:

acquiring a first corresponding relation; the first correspondence comprises a correspondence between the content of the service type field and at least one DRB;

determining third content according to the first corresponding relation; the third content is a content corresponding to a third DRB; the third DRB is a DRB of the at least one DRB except the first DRB;

determining the second content from the third content;

redefining the first content as the second content.

4. The method according to any of claims 1-3, wherein at least one of the transmission status data does not satisfy a preset condition, comprising one of:

one of the transmission status data does not satisfy a preset condition;

a plurality of the transmission status data do not satisfy a preset condition.

5. The method according to claim 4, wherein when one of the transmission status data does not satisfy a preset condition, the second content is a content of a service field corresponding to the transmission status data in a third content.

6. The method according to claim 4, wherein when a plurality of the transmission status data do not satisfy a preset condition, the second content is one of fourth contents; the fourth content is a plurality of contents determined from the contents of the service field corresponding to the transmission status data in the third content.

7. The method according to any one of claims 1 to 6, wherein after acquiring the data packet to be mapped in the first IP flow if at least one of the transmission status data does not satisfy a preset condition, the method further comprises:

copying the data packet to be mapped to obtain a copied data packet;

redefining the content of the service type field of the duplicate packet from the first content to a second content, thereby obtaining the redefined packet.

8. The method of claim 3, wherein the first correspondence is determined based on a set of quality of service (Qos) rules and a correspondence of quality of service (Qos) flows and DRBs; and the Qos rule set is used for representing the corresponding relation between the content of the service type field and the Qos flow.

9. The method of claim 8, wherein the Qos rule and the corresponding relationship between Qos flow and DRB are issued by a network device when a current session is established or modified.

10. The method of claim 8 or 9, wherein mapping the second IP flow onto the second DRB according to the second content comprises:

according to the second content, determining a target Qos rule from at least one Qos rule in the Qos rule set;

mapping the second IP flow to a target Qos flow corresponding to the target Qos rule;

and mapping the target Qos flow to the second DRB according to the corresponding relation between the Qos flow and the DRB.

11. A data transmission method is applied to network equipment and comprises the following steps:

12. The method of claim 11, wherein the transmission status data comprises at least one of:

13. A method according to any of claims 11-12, wherein the second content is determined from a third content; the third content is a content corresponding to a third DRB; the third DRB is a DRB except the first DRB in at least one DRB determined according to the first corresponding relation; the first correspondence includes a correspondence between the content of the service type field and the at least one DRB.

14. The method according to any of claims 11-13, wherein at least one of the transmission status data does not satisfy a preset condition, comprising one of:

one of the transmission status data does not satisfy a preset condition;

a plurality of the transmission status data do not satisfy a preset condition.

15. The method according to claim 14, wherein when one of the transmission status data does not satisfy a preset condition, the second content is a content of a service field corresponding to the transmission status data in a third content.

16. The method according to claim 14, wherein when a plurality of the transmission status data do not satisfy a preset condition, the second content is one of fourth contents; the fourth content is a plurality of contents determined from the contents of the service field corresponding to the transmission status data in the third content.

17. The method according to any of claims 11-16, wherein the redefined data packet is obtained by redefining the content of the service type field of the duplicated data packet from the first content to the second content in case the transmission status data does not satisfy a preset condition; the copy data packet is obtained by copying the data packet to be mapped.

18. The method of claim 13, wherein the first correspondence is determined based on a set of Qos rules and a correspondence of Qos flow and DRB; and the Qos rule set is used for representing the corresponding relation between the content of the service type field and the QoS flow.

19. The method of claim 18, further comprising:

and when the current session is established or modified, transmitting the corresponding relation between the Qos flow and the DRB to the terminal.

20. The method according to claim 16 or 19, wherein said second DRB is obtained by mapping a target Qos flow according to the correspondence between said Qos flow and DRB; the target Qos flow corresponds to a target Qos rule; the target Qos rule is determined from at least one Qos rule of the set of Qos rules according to the second content.

21. A terminal, comprising:

22. A network device, comprising:

23. A terminal, characterized in that the terminal comprises: a first processor and a first memory for storing a computer program operable on the first processor;

wherein the first processor is adapted to perform the steps of the method of any one of claims 1 to 10 when running the computer program.

24. A network device, characterized in that the network device comprises: a second processor and a second memory for storing a computer program operable on the second processor;

wherein the second processor is adapted to perform the steps of the method of any of claims 11 to 20 when running the computer program.

25. A storage medium having one or more computer programs stored thereon that are executable by one or more processors to perform the steps of the method of any one of claims 1 to 10 or any one of claims 11 to 20.