CN112004241B

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

Info

Publication number: CN112004241B
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: 2024-03-08
Anticipated expiration: 2040-08-27
Also published as: CN112004241A

Abstract

The embodiment of the application discloses a data transmission method, a terminal, network equipment and a storage medium, wherein transmission state data of a first data resource bearing DRB in a current session is obtained; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 a service type field of the data packet to be mapped from the preset first content to be second content, and thus obtaining redefined data packets; the second content corresponds to a second IP flow; carrying the redefined data packet in a second IP flow; mapping a second IP flow to a second DRB according to the second content, and sending the second DRB; the second DRB is the DRB in the current session.

Description

Data transmission method, terminal, network equipment and storage medium

Technical Field

The present disclosure 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 the 5th generation mobile communication technology (5th Generation Wireless Systems,5G) system, a 5G SA network can realize network slicing, and different network requirements are met through different network slicing. After selecting a network slice, the terminal establishes a corresponding protocol Data unit (Protocol Data Unit, PDU) session, the network issues a service quality rule set (Quality of Service rules, qos) of the PDU session, the terminal maps an application Data flow (IP flow) into a Qos Data flow according to the Qos rule, and then maps the Qos Data flow to a Data Radio Bearer (DRB) according to the mapping relation between the Data Radio Bearer (DRB) configured by the PDU session and the Qos Data flow, so as to complete Data transmission on the DRB. Due to the limitation of the mapping mode, the data transmission is not flexible enough, and the data transmission effect is affected.

Disclosure of Invention

The embodiment of the application provides a data transmission method, a terminal, network equipment and a storage medium, which improve 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 Bearer (DRB) in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 a service type field of the data packet to be mapped from the preset first content to be second 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 to 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 bears redefined data packets in the second application data flow IP flow; redefining the content of the service type field of the data packet to be mapped of the first IP flow from the first content to be the data packet obtained by the second content under the condition that at least one of the transmission state data of the first DRB does not meet the preset condition; the second content corresponds to a second IP flow; the first DRB bears a mapped data packet in a first IP flow; the first DRB is the DRB in the current session.

The embodiment of the application provides a terminal, which comprises:

the acquisition module is used for acquiring transmission state data of the first data resource bearer DRB in the current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 status data does not meet a preset condition;

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

the mapping module is used for 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 network device, which comprises:

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

The embodiment of the application provides a terminal, which comprises:

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

The embodiment of the application provides a network device, which comprises:

a second processor and a second memory for storing a computer program capable of running 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.

Embodiments of the present application provide a storage medium storing one or more computer programs executable by one or more processors to implement the steps of the data transmission method described above.

The embodiment of the application provides a data transmission method, a terminal, network equipment and a storage medium, wherein the terminal acquires transmission state data of a first Data Resource Bearer (DRB) in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 a service type field of the data packet to be mapped from the preset first content to be second content, and thus obtaining redefined data packets; the second content corresponds to a second IP flow; carrying the redefined data packet in a second IP flow; mapping a second IP flow to a second DRB according to the second content, and sending the second DRB; the second DRB is the DRB in the current session; that is, the terminal may redefine the content of the service type field of the data packet 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, which increases the flexibility of data transmission, and thus improves 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 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 second 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 provided in an embodiment of the present application;

fig. 7 is an information schematic 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 provided in an embodiment of the present application;

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

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

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

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

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

Fig. 14 is a schematic diagram of a second structural component 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 will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only 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, where the communication system may include: a terminal 101 and a network device 102.

The terminal 101 may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of user equipment, mobile Stations (MSs), terminals, etc. 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 via some kind of air interface technology, e.g. Uu interface.

The network device 102 may be an evolved NodeB (eNB) in a long term evolution (Long Term Evolution, LTE) system, an Access Point (AP) or a relay station, or may be a base station (such as a gNB or a transmission point (Transmission Point, TRP)) in a 5G system, and in a 5G NR-U system, a device with a base station function is called a gnob or a gNB. As communication technology evolves, the description of "base station" may change. The network device 102 may also be a wireless controller, a mobile switching center, a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future communication system in a cloud wireless access network (Cloud Radio Access Network, CRAN) scenario, or may also be a base station (such as a gNB or a transmission point (Transmission Point, TRP), a base station (Base Transceiver Station, BTS) in a global system for mobile communications (Global System of Mobile communication, GSM) system or a code division multiple access (Code Division Multiple Access, CDMA) system in an NTN system, or may also be a base station (NodeB, NB) in a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, or the like, which is not limited in this embodiment of the present application.

In addition, in the embodiment of the present application, the network device 102 provides services for a cell, where 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, and 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 cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services. In addition, the cell may also be a super cell (Hypercell).

In the 5G communications era, because of the diversity of terminals accessing a network, the network needs to meet diversified service requirements, such as timeliness, reliability, security, and the like, a network slicing technique may be adopted to slice a plurality of logical networks on an independent physical network, so different network requirements may adopt different network slices, and differential services are provided through the network slices. With the deployment of the 5G SA network being completed, differential services with different slices and different charges can be provided for users; for example, a low-delay game slice, a high-bandwidth data transmission slice, mass access of the Internet of things with high access quantity and low data requirement, a vehicle network slice with extremely high real-time requirement, and the like.

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

The mapping relationship between the DRB and the Qos data flow 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 flow.

In the embodiment of the present application, the mapping process from IP flow to Qos flow and then from Qos flow to DRB are all mapped according to a fixed mapping relationship, that is, the transmission effect of DRB depends on the stability and reliability of the network itself; the 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 is affected under the condition that 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 bearer DRB in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 can 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 by the current session; therefore, the terminal may acquire transmission status data of a first DRB of the at least one DRB, where the transmission status data of the first DRB is 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 characterize the reliability of transmission, and a lower packet loss rate indicates a higher reliability, and a higher packet loss rate indicates a lower reliability; the transmission rate is used to characterize the throughput of the transmission, and may also characterize the round trip delay, with lower transmission rates indicating higher round trip delays or lower throughput, and higher transmission rates indicating lower round trip delays or higher throughput.

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

The terminal sends 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 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 issued by the application may be carried and transmitted on the DRB, or may be carried and transmitted on a plurality of DRBs, which is not limited in this embodiment of the present application.

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 data packet in the first IP flow.

Referring to fig. 3, fig. 3 shows a schematic diagram of data transmission. As shown in fig. 3, the application program issues a data packet to form 5 IP flows, maps the IP flows to 3 Qos flows, and then maps the 3 Qos flows to 2 DRBs for transmission.

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

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

Fig. 4 shows a schematic format of a 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 present application, the content of the TOS field is the content of the TOS subfield; here, only one bit of 4 bits is 1; each bit is respectively set with 1, so that 4 service types can be obtained; the method comprises the following steps of: minimum latency, maximum throughput, maximum reliability, and minimum cost; each 0 in the 4 bits indicates a general service.

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

In the embodiment of the application, different services of the same application program can 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 zone transfer may correspond to a maximum throughput.

Table 1 shows the TOS field contents corresponding to the application program. As shown in table 1, TOS field contents include 4 types, where the service type corresponding to "1000" is the minimum time 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 RLogin interaction applications are mainly used for transmitting a small amount of interaction data, and minimum transmission delay is required; the simple network management protocol (Simple Network Management Protocol, SNMP) requires the highest reliability; the bootstrap protocol (Bootstrap Protocol, BOOTP) is then a generic service; among them, user web news (NNTP) is the only application requiring minimum fee.

TABLE 1

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

In this embodiment of the present application, the TOS field content of the data packet in the first IP flow is the first content, so that the terminal may 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 the preset condition, acquiring a data packet to be mapped in the first IP flow, redefining the content of a service type field of the data packet to be mapped from the preset first content to be second 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 present application, after obtaining transmission status data of the first DRB, the terminal may obtain a to-be-mapped data packet in the first IP flow, redefine the content of a service type field of the to-be-mapped data packet, and modify the content of the service type field of the to-be-mapped data packet to be a second content, to obtain the redefined data packet, where at least one of the transmission status data does not meet a preset condition.

In this embodiment of the present application, the second content corresponds to the second IP flow, and therefore, redefined packets are carried in the second IP flow for mapping.

In the embodiment of the present application, at least one of the transmission status data of the first DRB does not satisfy the preset condition to indicate 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 meet a preset condition, which may be that the transmission status data of the first DRB is not within a preset range; the transmission status data of the first DRB may be not within a preset range, and the duration exceeds a preset time; in this regard, the setting may 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 460ms; the preset range of the packet loss rate may be less than 0.2%.

In the embodiment of the present application, different transmission status data may correspond to different preset conditions; for example, the time delay does not satisfy the preset condition may be that the time delay is greater than or equal to 460ms and the duration exceeds 1s; the packet loss rate does not meet 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, which 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 or may be at least one specified, which is not limited to the embodiment of the present application.

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

S103, mapping the second IP flow onto a second DRB according to the second content, and sending the second DRB; the second DRB is the 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, redefined packets will map 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, 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; 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 a second Qos flow according to the second content, and then can map the second Qos flow to be transmitted on the second DRB.

It can be understood that the terminal obtains 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 a preset condition, redefines the content of the service type field from the first content to the second content, thereby obtaining 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 is transmitted on the second DRB, thereby improving the data transmission effect.

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

s201, acquiring a first corresponding relation; the first correspondence includes a correspondence between 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, multiple TOS field contents may correspond to one DRB. In order to enable the redefined packet carrying the second content to be carried on the second DRB, the terminal needs to determine which of the contents of the service type fields do not correspond to the first DRB.

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

In the embodiment of the present application, at least one DRB in the first correspondence is all DRBs corresponding to the content of the 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 corresponding to a third DRB; the third DRB is a DRB except the first DRB in at least one DRB;

in the embodiment of the present application, after obtaining the first correspondence, the terminal may determine a third DRB from at least one DRB; the third DRB is a DRB other than the first DRB of the at least one DRB. Thus, the second DRB may be one of the third DRBs.

In this embodiment of the present application, the terminal may determine, according to the first correspondence, 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 as the second content.

In the embodiment of the present application, the third content is a content corresponding to the third DRB, and the third content includes at least one content, so 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 can be carried on a second DRB that is different from the first DRB.

In the embodiment of the application, the terminal may use any one of the third contents as the second content; the content in the third content may be ranked according to a preset priority, and the content with the highest priority may be used as the second content.

Illustratively, in the current session, "0001" and "0100" correspond to DRB1, "0010" correspond to DRB2, "0001" corresponds to DRB3; referring to table 1, the default TOS field content of the data packet of the data transmission issued by the ftp is "0100", and the first IP flow is formed corresponding to the service type of the maximum throughput, and is mapped and transmitted on the DRB 1. When the transmission state data of the DRB1 does not meet the preset condition, the terminal determines that the third DRB is DRB2 and DRB3, wherein the contents corresponding to the DRB2 and the DRB3 are 0010 and 0001 respectively and are third contents; 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 data packet to be mapped in the FTP data transmission from "0100" to "0010" to obtain the redefined data packet, the redefined data packet forms a second IP flow, and the second IP flow is mapped and transmitted on DRB2, where DRB2 is a second DRB.

It can be understood that the terminal may determine, according to the correspondence between the content of the service type field and the DRB, the second content corresponding to the second DRB, so that, in the case that the transmission status data of the first DRB does not meet the preset condition, the terminal redefines the content of the service type field of the data packet to be mapped from the first content to the second content, and after obtaining the redefined data packet, it may be ensured that the redefined data packet is mapped onto the second DRB different from the first DRB for transmission.

In some embodiments of the present application, the at least one of the transmission state data not meeting the preset condition may include one of the transmission state data not meeting the preset condition, or a plurality of the transmission state data not meeting 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, since different transmission status data are used to characterize different transmission effects, and the contents of different service type fields correspond to different transmission effects, there may be a correspondence between the transmission status data and the contents of the service type fields.

Illustratively, referring to table 1, the transmission delay corresponds to the content "1000" of the TOS field; the service type of "0010" is 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 present application, if one of the transmission status data does not meet 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, the content is taken as the second content.

Illustratively, in the current session, "0001" and "0100" correspond to DRB1, "0010" correspond to DRB2, "0001" corresponds to DRB3; referring to table 1, the default TOS field content of the data packet of the data transmission issued by the ftp is a first content "0100", and the service type corresponding to the maximum throughput is carried in the first IP flow and mapped to be transmitted on the DRB 1. The first transmission state data is packet loss rate in the transmission state data, 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 contents corresponding to the DRB2 and the DRB3 are 0010 and 0001 respectively and are third contents; the highest reliability is represented by the packet loss rate corresponding to the content '0010' of the TOS field; accordingly, the terminal may determine "0010" as the second content; and redefining the TOS field content of the data packet to be mapped in the first IP flow from 0100 to 0010 to obtain redefined data packet, and transmitting the redefined data packet on the DRB2 by the second IP flow carried in the redefined data packet, thereby improving the reliability of FTP data transmission.

It can be understood that, when the first transmission status data does not meet the preset condition, the terminal needs to use the content corresponding to the first transmission status data as the second content, so as to improve the transmission effect of the first service type in a targeted manner.

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

In this embodiment of the present application, the implementation of determining, by the terminal, the second content from the contents of the multiple service type fields may be the same as the implementation of S203, which is not described herein again.

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

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

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

In this embodiment of the present application, if at least one of the transmission status data of the first DRB does not meet the preset condition, the terminal may copy the data packet to be mapped in the first IP flow to obtain a copied data packet, redefine the content of the service type field of the copied data packet as the second content to obtain a redefined data packet, so that the redefined data packet will be 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 will still be carried on the first DRB for transmission; that is, under the condition that the transmission effect of the first DRB is not good, after the data packet originally carried on the first DRB is duplicated for one part, two parts of data packets to be mapped are obtained, wherein one part is carried on the first DRB for transmission, and the other part is carried on the second DRB for transmission, so that the data transmission effect is improved, and meanwhile, the reliability of data transmission is ensured.

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

In an 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 qoss flows have different identifiers QFI (Qos Flow Identity, QFI).

In the embodiment of the application, each Qos rule includes filtering field information, where the filtering field information includes a filtering field identifier and contents of a filtering field. Wherein, the filtering field identification is used for representing the type of the filtering field, namely, which filtering fields exist in the Qos rule; the content of the filtering field represents the content of the filtering field in the Qos rule.

Fig. 6 shows 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 ottet, i.e., 8 bits. It can be seen that the Qos rule set list includes the length of Qos rule set composition information, and n Qos rules, where n Qos rules are Qos rule 1, 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 filtered field types.

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

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 filter field identifier, and further determine a correspondence between the content of the service type field and the Qos rules, thereby determining a correspondence between the content of the service type field and Qos flow.

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

In the embodiment of the present application, the Qos rule set and the correspondence between Qos flows and DRBs 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 terminal-defined; the embodiments of the present application are not limited in this regard.

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

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

It can be understood that the terminal can 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 the Qos flow and the DRB, so as to obtain a first corresponding relationship, and further determine the second content corresponding to the 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 on 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, determining a target Qos rule from at least one Qos rule in the Qos rule set according to the second content;

in the embodiment of the present application, the terminal may determine a Qos rule including a service type field from the Qos rule set, and then determine, from the Qos rules, that the content of the service type field is a target Qos rule of 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. Thus, 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 mapping the IP flow to the corresponding target Qos flow, the terminal may map the target Qos flow 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 bearer DRB in a current session; the second DRB bears redefined data packets in the second application data flow IP flow; redefining the data packet to be the data packet obtained by redefining the content of the service type field of the data packet to be mapped of the first IP flow from the first content to the second content under the condition that at least one of the transmission state data of the first DRB does not meet the 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 the DRB in the current session.

In some embodiments of the present application, the transmission status data includes 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 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 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 state data does not meet a preset condition;

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

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

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

In some embodiments of the present application, redefining the data packet to be that the transmission status data does not satisfy the preset condition is obtained by redefining the content of the service type field of the duplicate data packet from the first content to the second content; the replication data packet is obtained by replicating the data packet to be mapped.

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

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

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

It should be noted that, the description of the second DRB received by the network device is detailed in the terminal side data transmission method, which is not repeated here.

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

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

s701, a terminal acquires transmission state data of a first data resource bearer DRB in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 a first IP flow;

s703, redefining the content of the service type field of the data packet to be mapped from the preset first content to second content by the terminal, thereby obtaining redefined data packets; 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 a 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 the first content to a second content, and thus a redefined data packet is obtained; 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 originally on the first DRB; therefore, the flexibility of data transmission is increased, and the data transmission effect is improved.

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

an obtaining module 181, configured to obtain transmission status data of a first data resource bearer DRB in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 status data does not meet a preset condition;

redefinition module 182, configured to redefine the content of the service type field of the data packet to be mapped from a preset first content to a second content, thereby obtaining a redefined data 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 includes at least one of:

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

In some embodiments, redefinition module 182 is further configured to obtain a first correspondence; the first correspondence includes a correspondence between content of a service type field and at least one DRB; determining third content according to the first corresponding relation; the third content is corresponding to a third DRB; the third DRB is a DRB except the first DRB in at least one 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 state data does not meet a preset condition;

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

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

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

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

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

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

In some embodiments, the mapping module 183 is further configured to determine, according to the second content, 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.

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 bears redefined data packets in the second application data flow IP flow; redefining the content of the service type field of the data packet to be mapped of the first IP flow from the first content to be the data packet obtained by the second content under the condition that at least one of the transmission state data of the first DRB does not meet the preset condition; the second content corresponds to a second IP flow; the first DRB bears a mapped data packet in a first IP flow; the first DRB is the DRB in the current session.

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

In some embodiments, the second content is determined from a third content; the third content is 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 content of a service type field and the at least one DRB.

one of the transmission state data does not meet a preset condition;

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

In some embodiments, when the redefined packet is that the transmission status data does not meet a preset condition, redefining the content of the service type field of the duplicate packet from the first content to the second content; the copying 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, to a terminal, the corresponding relationship between Qos flow and DRB when the current session is established or modified.

In some embodiments, the second DRB is obtained by mapping the 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 in the set of Qos rules according to the second content.

Fig. 13 is a schematic diagram ii of the structural composition of the terminal according to the embodiment of the present application, 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 executable on the first processor 2002; wherein the first processor is configured to execute the method for transmitting a channel on the terminal side as in the foregoing embodiment when running the computer program.

It will be appreciated that the terminal 20 also includes a bus system 2003; the various components in terminal 20 are coupled together by bus system 2003. It is appreciated that bus system 2003 is employed to facilitate connected communications 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 diagram showing the structural composition of a network device according to an embodiment of the present application, 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 capable of running on the second processor 2102; the second processor is configured to execute the method for transmitting a channel on the network device side in the foregoing embodiment when running the computer program.

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

It will be appreciated that the memory in this embodiment may be either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. Wherein the nonvolatile Memory may be Read Only Memory (ROM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable Read Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic random access Memory (Ferromagnetic Random Access Memory, FRAM), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or Read Only optical disk (Compact Disc Read-Only Memory, CD-ROM); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (Static Random Access Memory, SRAM), synchronous static random access memory (Synchronous Static Random Access Memory, SSRAM), dynamic random access memory (Dynamic Random Access Memory, DRAM), synchronous dynamic random access memory (Synchronous Dynamic Random Access Memory, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate Synchronous Dynamic Random Access Memory, ddr SDRAM), enhanced synchronous dynamic random access memory (Enhanced Synchronous Dynamic Random Access Memory, ESDRAM), synchronous link dynamic random access memory (SyncLink Dynamic Random Access Memory, SLDRAM), direct memory bus random access memory (Direct Rambus Random Access Memory, DRRAM). The memory described in the embodiments of the present application is 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 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 by instructions in the form of software. The processor may be a general purpose processor, 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 embodiments of the present application. The 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 embodied in 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 memory and a processor reading information from the memory and performing the steps of the method in combination with hardware.

The embodiment of the application also 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 the first processor to implement the steps in the terminal-side data transmission method of the embodiment of the application.

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

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the modules is only one logical function division, and there may be other divisions in practice, such as: multiple modules or components may be combined, or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or modules, whether electrically, mechanically, or otherwise.

Claims

1. A data transmission method, applied to a terminal, comprising:

acquiring transmission state data of a first Data Resource Bearer (DRB) in a current session; the first DRB bears mapped IP data packets in the IP flow of the first application data 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 a service type field of the data packet to be mapped from a preset first content to a second content, thereby obtaining a redefined data packet, wherein the redefined data packet is borne on a second DRB different from the first DRB; the second content corresponds to a second IP flow; carrying the redefined data packet in the second IP flow;

mapping the second IP flow to 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 includes a correspondence between content of the service type field and at least one DRB;

Determining third content according to the first corresponding relation; the third content is corresponding to a third DRB; the third DRB is a DRB of the at least one DRB other than 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-2, wherein at least one of the transmission status data does not meet a preset condition, comprising one of:

one of the transmission state data does not meet a preset condition;

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

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

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

7. The method according to any one of claims 1-2, wherein after obtaining the data packet to be mapped in the first IP flow if at least one of the transmission status data does not meet a preset condition, the method further includes:

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

redefining the content of the service type field of the duplicate data packet from the first content to a second content, thereby obtaining the redefined data 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 data flow Qos flows and DRBs; the Qos rule set is used for characterizing a correspondence between content of a service type field and Qos flow.

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

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

Determining 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.

11. A data transmission method, applied to a network device, comprising:

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

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

13. The method of any of claims 11-12, wherein the second content is determined from a third content; the third content is 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 content of a service type field and the at least one DRB.

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

one of the transmission state data does not meet a preset condition;

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

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

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

17. The method according to any one of claims 11 to 12, wherein, in the case where the redefined packet is that the transmission status data does not satisfy a preset condition, redefining the content of the service type field of the duplicate packet from the first content to the second content; the copying 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 flows and DRBs; the Qos rule set is used for characterizing a correspondence between content of a service type field and Qos flow.

19. The method of claim 18, wherein the method further comprises:

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

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

21. A terminal, comprising:

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

22. A network device, comprising:

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

23. A terminal, the terminal comprising: a first processor and a first memory for storing a computer program capable of running on the first processor;

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

24. A network device, the network device comprising: a second processor and a second memory for storing a computer program capable of running 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 the computer program is run.

25. A storage medium storing one or more computer programs executable by one or more processors to implement the steps of the method of any one of claims 1 to 10 or any one of claims 11 to 20.