Data transmitting method and device, data receiving method and device, communication system, and communication device

Abstract

The present disclosure relates to the technical field of communications, and relates to a data transmitting method and device, a communication system, and a communication device. The method comprises: a transmitting entity of a first protocol layer of a first device receiving a first data packet transmitted by a second protocol layer of the first device, wherein the second protocol layer is the layer above the first protocol layer; setting a sequence number (SN) field in a packet header of the first protocol layer to be a value of a first state variable; when a first condition is satisfied, segmenting a second data packet to obtain a plurality of data packet segments, wherein the second data packet is obtained by performing first processing on the first data packet, or the second data packet is the first data packet; and transmitting each data packet segment among the plurality of data packet segments to a third protocol layer, or when the first condition is not satisfied, transmitting the second data packet to the third protocol layer. The processes of transmitting and receiving data by the protocol layers are simplified, the functions of the PDCP and RLC layers are merged, and the processing complexity of a protocol stack is simplified, thereby effectively supporting the transmission of high-rate data.

Description

A data transmission and reception method and apparatus, a communication system, and communication equipment. Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a data transmission and reception method and apparatus, a communication system, and a communication device. Background Technology

[0002] In the new radio / air interface (NR), each radio bearer (RB) has a corresponding PDCP (Packet Data Convergence Protocol) entity. A PDCP entity consists of a transmitting PDCP entity and a receiving PDCP entity.

[0003] Summary of the Invention

[0004] This disclosure provides a data transmission and reception method and device, a communication system, and a communication device that can be used in the field of communication technology to combine the functions of the PDCP layer and the RLC layer in the first protocol layer, thereby simplifying the steps that originally required two layers to execute, thus simplifying the processing complexity of the protocol stack and effectively supporting the transmission of high-speed data.

[0005] According to a first aspect of the present disclosure, a data transmission method is proposed, executed by a transmission entity of a first protocol layer of a first device, comprising: receiving a first data packet transmitted by a second protocol layer of the first device, wherein the second protocol layer is an upper layer of the first protocol layer; setting the sequence number (SN) field in the header of the first protocol layer to the value of a first state variable, wherein the transmission entity does not perform wrapback when the SN field reaches its upper limit, the first state variable being used to represent a count value of the data packets transmitted by the first protocol layer, the count value being associated with the first data packet; segmenting a second data packet to obtain multiple data packet segments if a first condition is met, wherein the space provided by a third protocol layer of the first device cannot completely contain the second data packet, the third protocol layer being a lower layer of the first protocol layer, the second data packet being obtained by performing a first processing on the first data packet, or the second data packet being the first data packet; and transmitting each data packet segment in the multiple data packet segments to the third protocol layer, or transmitting the second data packet to the third protocol layer if the first condition is not met.

[0006] According to a second aspect of the present disclosure, a data receiving method is proposed, executed by a receiving entity of a first protocol layer of a second device, comprising: receiving multiple data packet segments or a second data packet sent by a third protocol layer of the second device, wherein the third protocol layer is a lower layer of the first protocol layer; determining a count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling multiple data packet segments, or the third data packet is a second data packet; sending a first data packet to the second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, and the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is a third data packet, wherein the first data packet does not include the header information of the first protocol layer.

[0007] According to a third aspect of the present disclosure, a transmitting entity of a first protocol layer is proposed, including a transceiver module for receiving a first data packet sent by a second protocol layer of a first device, wherein the second protocol layer is an upper layer of the first protocol layer; the processing module is further configured to: set the sequence number (SN) field in the packet header of the first protocol layer to the value of a first state variable, wherein the transmitting entity does not perform wrapback when the SN field reaches its upper limit, and the first state variable is used to represent a count value of the data packet sent by the first protocol layer, the count value being associated with the first data packet; the processing module is further configured to: segment a second data packet to obtain multiple data packet segments if a first condition is met, wherein the space provided by a third protocol layer of the first device cannot completely contain the second data packet, the third protocol layer is a lower layer of the first protocol layer, and the second data packet is obtained by performing a first processing on the first data packet, or the second data packet is the first data packet; the transceiver module is further configured to: send each data packet segment in the multiple data packet segments to the third protocol layer, or send the second data packet to the third protocol layer if the first condition is not met.

[0008] According to a fourth aspect of the present disclosure, a receiving entity of a first protocol layer is provided, including a transceiver module for receiving multiple data packet segments or a second data packet sent by a third protocol layer of a second device, wherein the third protocol layer is a lower layer of the first protocol layer; the processing module is further configured to: determine a count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling multiple data packet segments, or the third data packet is a second data packet; the transceiver module is further configured to: send a first data packet to the second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, and the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is a third data packet, wherein the first data packet does not include the header information of the first protocol layer.

[0009] According to a fifth aspect of the present disclosure, a communication system is provided, including a first device and a second device, wherein the first device is configured to implement the data transmission method of the first aspect, and the second device is configured to implement the data reception method of the second aspect.

[0010] According to a sixth aspect of the present disclosure, a communication device is provided, comprising: a transceiver; a memory; and a processor connected to the transceiver and the memory respectively, configured to control the transmission and reception of wireless signals of the transceiver by executing computer-executable instructions on the memory, and capable of implementing the communication method described in any one of the first and second aspects of the present disclosure.

[0011] According to a seventh aspect of the present disclosure, a storage medium is provided, wherein the computer storage medium stores computer-executable instructions, which, when executed by a processor, can implement the communication method described in any one of the first and second aspects of the present disclosure.

[0012] According to the data transmission and reception method proposed in this disclosure, the functions of the PDCP layer and the RLC layer are merged through the first protocol layer, which simplifies the data processing steps that originally required two layers to execute, reduces the processing complexity of the protocol stack, and thus effectively supports the transmission of high-speed data. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0014] Figure 1 is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0015] Figure 2 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure;

[0016] Figure 3A is a schematic flowchart of a data transmission method for a first protocol layer transmission entity of a first device according to an embodiment of the present disclosure.

[0017] Figure 3B is a schematic flowchart of a data transmission method for a first protocol layer transmission entity of a first device according to an embodiment of the present disclosure.

[0018] Figure 4A is a schematic flowchart of a data receiving method for a receiving entity of a first protocol layer of a second device according to an embodiment of the present disclosure.

[0019] Figure 4B is a schematic flowchart of a data receiving method for a receiving entity of a first protocol layer of a second device according to an embodiment of the present disclosure.

[0020] Figure 5 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure;

[0021] Figure 6A is a schematic diagram of the composition of the COUNT value provided in an embodiment of this disclosure;

[0022] Figure 6B is a schematic diagram of the PDU format provided in an embodiment of this disclosure;

[0023] Figure 6C is a schematic diagram of the PDU format provided in the embodiments of this disclosure;

[0024] Figure 6D is a schematic diagram of the user plane data stream processing flow provided in an embodiment of this disclosure;

[0025] Figure 6E is a schematic diagram of PDU being sent to multiple logical channels according to an embodiment of this disclosure;

[0026] Figure 6F is a functional diagram of the simplified protocol layer provided in an embodiment of this disclosure;

[0027] Figure 7A is a schematic diagram of the structure of a first device provided according to an embodiment of the present disclosure;

[0028] Figure 7B is a schematic diagram of the structure of a second device provided according to an embodiment of the present disclosure;

[0029] Figure 8A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure;

[0030] Figure 8B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0031] This disclosure provides a data transmission and reception method and apparatus, a communication system, and a communication device.

[0032] In a first aspect, embodiments of this disclosure provide a data transmission method, which is executed by a transmission entity of a first protocol layer, comprising: receiving a first data packet transmitted by a second protocol layer of a first device, wherein the second protocol layer is an upper layer of the first protocol layer; setting the sequence number (SN) field in the header of the first protocol layer to the value of a first state variable, wherein the transmission entity does not perform wrapback when the SN field reaches its upper limit, and the first state variable is used to represent a count value of the data packets transmitted by the first protocol layer, the count value being associated with the first data packet; segmenting a second data packet to obtain multiple data packet segments under a first condition, wherein the first condition is that the space provided by a third protocol layer of the first device cannot completely contain the second data packet, the third protocol layer is a lower layer of the first protocol layer, and the second data packet is obtained by performing a first processing on the first data packet, or the second data packet is the first data packet; and transmitting each data packet segment in the multiple data packet segments to the third protocol layer, or transmitting the second data packet to the third protocol layer if the first condition is not met.

[0033] In the above embodiments, the functions of the PDCP layer and the RLC layer are merged through the first protocol layer, which simplifies the data processing steps that originally required two layers to execute, and further improves the efficiency of data transmission.

[0034] In conjunction with some embodiments of the first aspect, in some embodiments, the first process includes at least one of the following: compressing the header of the first data packet; using a count value as input to a security algorithm, performing integrity protection and encryption processing on the header-compressed first data packet to obtain a second data packet.

[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: under a second condition, incrementing a first state variable by 1, wherein the second condition is that multiple data packet segments include the last byte of a second data packet, or the second data packet is not segmented.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining the length of the SN field in the packet header based on protocol conventions.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first device is a terminal, and the method further includes: receiving first information sent by an access network device, the first information being used to configure the length of the SN field; and determining the length of the SN field based on the first information.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the length of the count value is the sum of the lengths of the first number of bits located in the SN field.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the packet header includes: a first field, which indicates the position of a first data packet segment among a plurality of data packet segments in a second data packet; and a second field, which indicates whether the first data packet segment among a plurality of data packet segments is the last segment of the second data packet.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the packet header includes: a third field, the third field being used to indicate the segmentation information of the first data packet segment among multiple data packet segments and whether the packet header contains the first field, the first field being used to indicate the position of the first data packet segment in the second data packet.

[0041] In conjunction with some embodiments of the first aspect, in some embodiments, the value of the first field is the initial position of the multiple data packet segments in the second data packet, or the value of the first field is the index value of the multiple data packet segments.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: segmenting multiple data packets or copying second data packets to obtain multiple copied data packet segments or multiple copied second data packets; wherein, sending multiple data packet segments to the third protocol layer includes: sending multiple copied data packet segments or multiple copied second data packets to the third protocol layer.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: resetting the first state variable to its initial value when the sending entity of the first protocol layer is reconstructed; and sending data packets that have not yet been sent to the third protocol layer in segments to the third protocol layer.

[0044] In the above embodiments, by simplifying the process of sending data at the protocol layer, the functions of the PDCP and RLC layers are combined, simplifying the processing complexity of the protocol stack, thereby effectively supporting the transmission of high-speed data.

[0045] Secondly, embodiments of this disclosure provide a data receiving method, executed by a receiving entity of a first protocol layer of a second device, comprising: receiving multiple data packet segments or a second data packet sent by a third protocol layer of the second device, wherein the third protocol layer is a lower layer of the first protocol layer; determining a count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling multiple data packet segments, or the third data packet is a second data packet; sending a first data packet to the second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, and the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is a third data packet, and the first data packet does not include the header information of the first protocol layer.

[0046] In the above embodiments, the receiving entity processes the data packets received from the sending entity in segments to recover the first data packet. Similarly, the functions of the PDCP layer and the RLC layer are combined in the first protocol layer, thereby simplifying the processing steps of the protocol layer.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the second processing includes at least one of the following: using a count value as input to a security algorithm, performing decryption and / or integrity verification processing on the second data packet, and determining whether to discard the second data packet; if the second data packet is not discarded, performing header decompression processing on the second data packet.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, determining whether to discard the second data packet includes: in the event of an integrity verification failure, determining to discard the second data packet and sending a verification failure notification to the Radio Resource Control (RRC) layer; and in the event that a data packet with a count value has already been received by the receiving entity, determining to discard the second data packet.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: determining the length of the SN field in the packet header based on protocol conventions.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the second device is a terminal, and the method further includes: receiving first information sent by the access network device, the first information being used to configure the length of the SN field; and determining the length of the SN field based on the first information.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: for each of a plurality of data packet segments, storing data packet segments with the same SN field in the packet header into a receive buffer; and, when all data packet segments with the same SN field have been received, reassembling all data packet segments with the same SN field into a third data packet.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: for each of a plurality of data packet segments, determining a timer associated with the SN field in the packet header, the timer being initially set to not start.

[0053] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes at least one of the following: stopping a first timer associated with the same SN field when all data packet segments with the same SN field are received; starting the first timer when data packet segments with the same SN field are received when the first timer is not running; and discarding all data packet segments with the same SN field when the first timer times out.

[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the second device is a terminal, and the method further includes: receiving second information sent by an access network device, the second information being used to configure a timer.

[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: discarding all data packet segments when the receiving entity of the first protocol layer performs reconstruction.

[0056] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: stopping all running timers when the receiving entity of the first protocol layer is reconstructing.

[0057] In conjunction with some embodiments of the second aspect, in some embodiments, the length of the count value is the sum of a first number of bits and the length of the SN field.

[0058] In the above embodiments, the receiving entity reassembles the data packets received from the sending entity based on the segmentation. By combining the functions of PDCP and RLC in the protocol layer, the data processing steps are simplified, thereby further improving the efficiency of data transmission.

[0059] Thirdly, this disclosure provides a sending entity of a first protocol layer, including a transceiver module for receiving a first data packet sent by a second protocol layer of a first device, wherein the second protocol layer is an upper layer of the first protocol layer; the processing module is further configured to: set the sequence number (SN) field in the packet header of the first protocol layer to the value of a first state variable, wherein when the SN field reaches its upper limit, the sending entity does not perform a wrapback, and the first state variable is used to represent the count value of the data packet sent by the first protocol layer, the count value being associated with the first data packet; the processing module is further configured to: segment a second data packet to obtain multiple data packet segments when a first condition is met, wherein the space provided by a third protocol layer of the first device cannot completely contain the second data packet, the third protocol layer is a lower layer of the first protocol layer, and the second data packet is obtained by performing a first processing on the first data packet, or the second data packet is the first data packet; the transceiver module is further configured to: send each data packet segment in the multiple data packet segments to the third protocol layer, or send the second data packet to the third protocol layer when the first condition is not met.

[0060] Fourthly, this disclosure provides a receiving entity for a first protocol layer, including a transceiver module for receiving multiple data packet segments or a second data packet sent by a third protocol layer of a second device, wherein the third protocol layer is a lower layer of the first protocol layer; the processing module is further configured to: determine the count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling multiple data packet segments, or the third data packet is a second data packet; the transceiver module is further configured to: send a first data packet to the second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, and the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is a third data packet, and the first data packet does not include the header information of the first protocol layer.

[0061] Fifthly, embodiments of this disclosure provide a communication system, including: a first device and a second device, wherein the first device is configured to implement the method described in any embodiment of the first aspect of this disclosure; and the second device is configured to implement the method described in any embodiment of the second aspect of this disclosure.

[0062] In a sixth aspect, embodiments of this disclosure provide a communication device, including: one or more processors; wherein the one or more processors are configured to invoke instructions to cause the communication device to perform the method described in any one of the embodiments of the first or second aspect of this disclosure.

[0063] In a seventh aspect, embodiments of this disclosure provide a computer storage medium storing computer-executable instructions, which, when executed by a processor, can implement the method described in any one of the embodiments of the first or second aspect of this disclosure.

[0064] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in the optional implementations of the first and second aspects.

[0065] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in the optional implementations of the first and second aspects.

[0066] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to optional implementations of the first and second aspects above.

[0067] It is understood that the aforementioned first device, second device, communication system, communication equipment, storage medium, program product, computer program, chip, or chip system are all used to perform the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0068] This disclosure provides a communication method and device, a communication system, a communication device, and a storage medium. In some embodiments, the terms "communication method" and "data transmission," "data reception," and "information processing method" can be used interchangeably; the terms "network device" and "information processing apparatus" and "communication apparatus" can be used interchangeably; and the terms "information processing system" and "communication system" can be used interchangeably.

[0069] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0070] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0071] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0072] In this disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the aforementioned," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular or a plural expression.

[0073] In the embodiments disclosed herein, "multiple" refers to two or more.

[0074] In some embodiments, the terms “at least one of”, “at least one of”, “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0075] The descriptions in this disclosure, such as "at least one of A, B, C..." or "A and / or B and / or C...", include the case where any one of A, B, C... exists alone, as well as the case where any combination of any of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and A and B combination.

[0076] In some embodiments, the notation "in one case A, in another case B" or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: A is executed regardless of B, i.e., A is executed in some embodiments; B is executed regardless of A, i.e., B is executed in some embodiments; A and B are selectively executed, i.e., A and B are selected for execution in some embodiments; A and B are both executed, i.e., A and B are executed in some embodiments. The same applies when there are more branches such as A, B, and C.

[0077] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0078] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0079] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0080] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.

[0081] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0082] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as “device”, “equipment”, “circuit”, “network element”, “node”, “function”, “unit”, “section”, “system”, “network”, “chip”, “chip system”, “entity”, and “subject” can be used interchangeably.

[0083] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0084] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0085] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0086] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0087] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0088] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0089] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0090] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0091] PDU (Protocol Data Unit): A PDU is the basic unit for data exchange between entities at the same protocol layer in a computer network. The form of a PDU differs at different network layers; for example, a PDU at the physical layer is a bit stream, a PDU at the data link layer is a frame, a PDU at the network layer is a packet, and a PDU at the transport layer is a segment or datagram. A PDU contains control information, address information, or data and is an information unit transmitted between network peers.

[0092] SDU (Service Data Unit): An information unit transmitted from a higher-layer protocol to a lower-layer protocol. At each layer, unprocessed data is called a Service Data Unit (SDU), while data processed by the layer and formatted into a specific format is called a Protocol Data Unit (PDU). The PDU formed at one layer becomes the SDU of the next layer. For example, an application layer PDU becomes a transport layer SDU after being transmitted to the transport layer. The transport layer SDU, along with its header information, forms the transport layer PDU, which is then transmitted to the network layer to become the network layer SDU.

[0093] The relationship between SDU and PDU can be summarized as follows: SDU is raw data, while PDU is a specific formatted data unit formed by adding protocol control information to SDU, used for transmission in the network. During transmission, SDU is encapsulated and control information is added to form PDU for transmission; upon arrival at the receiving end, the receiving end decapsulates the PDU back into SDU according to the protocol control information. This conversion can be performed in a one-to-many, many-to-one, or one-to-one manner, depending on the requirements for data segmentation, combination, splicing, or division.

[0094] Each layer's data packet is called a Protocol Data Unit (PDU), which contains a header and trailer (if any) specific to that layer. The portion of the packet excluding the header and trailer is called a Service Data Unit (SDU), where "service" refers to providing services to the upper layers.

[0095] In the new radio / new air interface, when data transmission is currently using the PDCP layer and RLC layer, the PDCP entity's state variable RX_DELIV indicates the COUNT value of the first PDCP SDU that has not yet been delivered to the upper layer but is waiting to be delivered. PDCP SDUs with a COUNT value less than RX_DELIV are discarded. The PDCP entity maintains a reordering timer (t-Reordering) to detect the loss of PDCP Data SDUs. The PDCP entity's state variable RX-REORD indicates the COUNT value (i.e., COUNT+1) after the COUNT value of the PDCP Data SDU that triggered t-Reordering. When the t-Reordering timer expires, RX_DELIV is updated to the first undelivered COUNT value greater than or equal to RX_REORD. The PDCP layer's SN is 12 bits or 18 bits long. The PDCP SN wraps around after growing to the maximum number of digits that the field can hold. For example, with a 12-bit PDCP SN, when the PDCP SN grows to 2... 12 When -1 = 4095, the PDCP SN of the next PDCP PDU will return to 0. The COUNT consists of the HFN and the PDCP SN. The PDCP entity's reception operation is based on the COUNT of the received PDCP Data PDU. Therefore, when a PDCP Data PDU is received, the value of the COUNT of the received PDU needs to be determined first according to the PDCP SN and the status variable RX_DELIV.

[0096] Radio Link Control (RLC) entities can be configured in three modes: Transparent Mode (TM), Unacknowledged Mode (UM), or Acknowledged Mode (AM). Correspondingly, an RLC entity is classified as a TM RLC entity, a UM RLC entity, or an AM RLC entity. An AM RLC entity consists of a transmitting side and a receiving side. For an RLC entity configured on the network side, the UE side is configured with an RLC peer entity, and vice versa. An RLC entity receives RLC SDUs from higher layers and transmits RLC SDUs to higher layers. An RLC entity sends RLC PDUs to or receives RLC PDUs from its peer entity via lower layers. When the space provided by the MAC layer is insufficient to transmit a complete RLC SDU, the RLC SDU is segmented and transmitted, and these segments are called RLC SDU segments. The RLC header information includes a Segmentation Offset (SO) field, which indicates the position (in bytes) of the RLC SDU segment within the original RLC SDU. Specifically, the SO field indicates the position of the first byte of the RLC SDU segment in the Data field within the original RLC SDU. The first byte of the original RLC SDU corresponds to an SO field value of 0, meaning the numbering starts from zero. RLC PDUs are classified into RLC data PDUs and RLC control PDUs. RLC data PDUs are used to transmit higher-layer PDUs (i.e., RLC SDUs). RLC data PDUs in UM mode are called UMD PDUs, and RLC data PDUs in AM mode are called AMD PDUs. RLC control PDUs are used for ARQ; the RLC status report mentioned above is an RLC control PDU. The RLC UM SN is 6 bits or 12 bits long. Similar to the PDCP SN, the RLC SN wraps around after growing to the maximum number of digits that the field can hold. Currently, the PDCP and RLC layers of NR have overlapping functions. For example, both the PDCP and RLC layers transmit the SN. The PDCP layer needs to determine the COUNT value of the received PDU based on the PDCP SN and the state variable RX_DELIV, and maintain the corresponding state variable RX_DELIV. Both the PDCP and RLC receiving sides have operations to discard PDUs. These overlapping functions and complex processing have a certain negative impact on the transmission of high-speed data.

[0097] Therefore, this disclosure proposes a data transmission and reception method and device, a communication system and a communication device, which simplifies the process of transmitting and receiving data at the protocol layer, combines the functions of the PDCP and RLC layers, simplifies the processing complexity of the protocol stack, and thus effectively supports the transmission of high-speed data.

[0098] The method proposed in this disclosure is applicable to various communication systems, including but not limited to 4G, 5G, 5G-advance and subsequent communication technologies (such as 6G).

[0099] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a first device 101 and a second device 102.

[0100] In some embodiments, the first device 101 may be a device that receives the first data packet.

[0101] In some embodiments, the first device 101 may be a device that performs a first processing on the first data packet.

[0102] In some embodiments, the first device 101 may be a device that sends a second data packet.

[0103] In some embodiments, the first device 101 may be a device for determining a first state variable.

[0104] In some embodiments, the first device 101 may be a device for compressing the package head.

[0105] In some embodiments, the first device 101 may be a device for integrity protection.

[0106] In some embodiments, the first device 101 may be a device for performing encryption processing.

[0107] In some embodiments, the first device 101 may be a device for segmenting data packets.

[0108] In some embodiments, the first device 101 may be a terminal.

[0109] In some embodiments, the first device 101 may be an access network device.

[0110] In some embodiments, the name of the first device 101 is not limited, and it may be, for example, a "data processing device", a "data packet segmentation device", a "packet header compression / integrity protection / encryption device", etc.

[0111] In some embodiments, the second device 102 may be a device for receiving data packet segments.

[0112] In some embodiments, the second device 102 may be a device for performing a recombination operation.

[0113] In some embodiments, the second device 102 may be a device for decryption and / or integrity verification.

[0114] In some embodiments, the second device 102 may be a device for performing a second process.

[0115] In some embodiments, the second device 102 may be a terminal.

[0116] In some embodiments, the second device 102 may be an access network device.

[0117] In some embodiments, the name of the second device 102 is not limited, and may be, for example, "device for receiving data packet segments", "device for reassembling data packets", "device for decryption and / or integrity verification", etc.

[0118] In some embodiments, the terminal may include at least one of, but is not limited to, a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home.

[0119] The network device in this application embodiment is an entity on the network side used to transmit or receive signals. For example, the network device can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of this application do not limit the specific technology or device form used in the network device. The network device provided in this application embodiment can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure, the protocol layer of the network device, such as a base station, can be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0120] The terminal device in this application embodiment is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0121] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0122] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. ​​The number and form of each main body are arbitrary. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0123] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other user plane path establishment methods, and next-generation systems extended from them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0124] Figure 2 is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure. As shown in Figure 2, this embodiment of the disclosure relates to a communication method that can be executed by a communication system, such as the communication system 100 shown in Figure 1. The communication system includes a first device and a second device. The interactive method includes a data transmission method executed by a transmitting entity of the first protocol layer of the first device and a data reception method executed by a receiving entity of the first protocol layer of the second device.

[0125] In the embodiments disclosed herein, the first protocol layer integrates the functions of the PDCP layer and the RLC layer, and is called LCC (Lean Convergence Control); the second protocol layer is the upper layer of the first protocol layer, such as the SDAP layer; and the third protocol layer is the lower layer of the first protocol layer, such as the MAC layer. The second protocol layer can also be the RRC layer, for example, when the receiver fails to perform integrity verification, the LLC layer can send a verification failure notification to the RRC layer.

[0126] The communication method includes the following steps:

[0127] Step 2101: The sending entity of the first protocol layer of the first device receives the first data packet sent by the second protocol layer of the first device.

[0128] In some embodiments, the second protocol layer is the upper layer of the first protocol layer.

[0129] In some embodiments, when establishing the sending entity of the first protocol layer, the first state variable is initialized, and the initialized value is zero.

[0130] For example, the first protocol layer receives the Service Data Unit (SDU) sent by the second protocol layer, where the second protocol layer is the upper layer of the first protocol layer.

[0131] Step 2102: The sending entity of the first protocol layer of the first device performs first processing on the first data packet to obtain the second data packet.

[0132] In some embodiments, the first process includes at least one of the following: compressing the header of the first data packet; and performing integrity protection and encryption processing on the header-compressed first data packet using a count value as input to a security algorithm.

[0133] In some embodiments, packet header compression of the first data packet may involve reducing the number of bits in the header data; integrity protection may involve adding a preset number of bits; and encryption may involve transforming the content of the data in the data packet while keeping the length unchanged.

[0134] In some embodiments, header compression, integrity protection, and encryption are optional and can be combined arbitrarily in different embodiments.

[0135] For example, the SDU is compressed in the header; the COUNT value is used as input to the security algorithm for integrity protection and ciphering.

[0136] It is understandable that step 2102, which involves the first processing, is an optional step. The sending entity of the first protocol layer may not perform the first processing on the first data packet, but may directly determine whether the first data packet meets the first condition. If the first condition is met, the first data packet is segmented. If the first condition is not met, the first data packet is directly sent as a data packet to the third protocol layer.

[0137] Step 2103: The sending entity of the first protocol layer of the first device sets the sequence number SN field in the packet header of the first protocol layer to the value of the first state variable.

[0138] In some embodiments, when the SN field reaches its upper limit, the sending entity does not perform a wrapback. The first state variable is used to represent the count value of the data packets sent by the first protocol layer, and the count value is associated with the first data packet.

[0139] In some embodiments, the sending entity not performing a wrapback may mean that when the SN field reaches its upper limit, the entity does not perform the zeroing operation of the SN field. In other words, the sending entity of the first protocol layer no longer performs data transmission, and other entities perform data transmission instead.

[0140] In some embodiments, the length of the count value is the sum of a first number of bits and the length of the SN field.

[0141] In some embodiments, the value of the first number of bits is zero; optionally, the first number of bits precedes the SN field.

[0142] For example, Figure 6A shows a schematic diagram of the SN field and several 0s forming the COUNT, that is, SN is the LSB, and the actual value of COUNT is the same as SN.

[0143] In some embodiments, the length of the SN field can be based on protocol conventions.

[0144] In some embodiments, the first device is a terminal, and the length of the SN field can be determined based on first information sent by the access network device. The first information is used to configure the length of the SN field.

[0145] For example, the length of the SN field in the packet header is configured by the access network device by sending the first information. Specifically, the first information is transmitted in RRC signaling. In particular, the granularity of the first information configuration is a simplified protocol layer entity.

[0146] For example, the length of the SN field can be configured jointly for downlink and uplink data, or it can be configured separately for downlink and uplink data. In other words, the access network device can configure the length of the SN field for both the terminal's uplink and downlink data, or it can configure them separately.

[0147] Step 2104: The sending entity of the first protocol layer of the first device segments the second data packet.

[0148] In some embodiments, if a first condition is met, the second data packet is segmented to obtain multiple data packet segments. The first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet.

[0149] In some embodiments, the segmentation operation is optional, i.e., segmentation is performed only if the lower layer of the first protocol layer cannot completely contain the PDU after header compression and / or integrity protection and / or encryption.

[0150] In some embodiments, the packet header includes: a first field indicating the position of a first packet segment in a second packet among a plurality of packet segments; and a second field indicating whether the first packet segment is the last segment of the second packet among a plurality of packet segments.

[0151] In some embodiments, the first data packet segment is one of a plurality of data packet segments, that is, the first field is used to indicate the position of a certain data packet segment in the second data packet.

[0152] For example, the packet header may contain a first field indicating the location of the PDU after packet header compression and / or integrity protection and / or encryption. The first field can be indicated in two ways:

[0153] Method 1: The first field indicates the position in bytes. That is, the first byte in the PDU's Data field corresponds to the position of the data after header compression and / or integrity protection and / or encryption. The first field value corresponding to the first byte of the data after header compression and / or integrity protection and / or encryption is 0, meaning the numbering starts from 0. In this method, the first field is the Segmentation Offset (SO) field.

[0154] Method 2: The first field indicates the index, which is the PDU number after the data has been segmented following header compression and / or integrity protection and / or encryption. This numbering starts from 0, meaning the first field value for the first segment is 0, the first field value for the second segment is 1, and so on. In this method, the first field is the index field.

[0155] For example, the packet header always contains the following two fields: a first field; and a second field indicating whether the PDU is the last segment of the corresponding SDU. The second field will be referred to as LS (Last Segment) below. See Figure 6B for a schematic diagram of the PDU format.

[0156] In some embodiments, the packet header includes a third field, which is used to indicate the segmentation information of the first data packet segment in a plurality of data packet segments and whether the packet header contains the first field, and the first field is used to indicate the position of the first data packet segment in the second data packet.

[0157] For example, the packet header always contains a third field that indicates segmentation information and at least indicates whether the packet header contains the first field. See Figure 6C for a schematic diagram of the PDU format.

[0158] Optionally, the header can always include the first and second fields, or it can always include the third field.

[0159] In some embodiments, the value of the first field is the initial position of the multiple data packet segments in the second data packet, or the value of the first field is the index value of the multiple data packet segments.

[0160] In some embodiments, the first protocol layer increments the first state variable by 1 under the second condition, where the second condition is that the multiple data packet segments include the last byte of the second data packet, or the second data packet is not segmented.

[0161] In other words, the second condition could be that the underlying space of the first device can contain the complete data packet, in which case the value of the state variable is incremented by one.

[0162] It is understood that step 2104 is an optional step. The sending entity of the first protocol layer can segment the second data packet, or it can not segment the second data packet and directly send the second data packet as a data packet to the third protocol layer. Alternatively, if the sending entity of the first protocol layer does not perform the first processing on the first data packet and does not segment the first data packet, the first data packet can be directly sent as a data packet to the third protocol layer.

[0163] Step 2105: The sending entity of the first protocol layer of the first device segments the multiple data packets or copies the second data packet.

[0164] In some embodiments, multiple data packets are segmented or second data packets are copied to obtain multiple copied data packet segments or multiple copied second data packets.

[0165] In some embodiments, the first protocol layer can perform a replication function, which combines the PDCP and RLC layers to map PDUs to logical channels.

[0166] For example, a single PDU from the simplified protocol layer can be sent multiple times to lower protocol layers. In particular, when the lower protocol layer is the MAC layer, a single PDU from the simplified protocol layer can be sent to multiple logical channels.

[0167] For example, the main application scenario for sending a PDU to multiple logical channels is packet duplication. In this embodiment, the PDU can be sent to two logical channels, namely a primary logical channel and a secondary logical channel. The PDU can also be sent to more than two logical channels, and this disclosure does not limit this.

[0168] Step 2106: The sending entity of the first protocol layer of the first device sends multiple data packets in segments to the third protocol layer, or sends the second data packet to the third protocol layer.

[0169] In some embodiments, the sending entity of the first protocol layer of the first device sends multiple data packets to the third protocol layer in segments, or sends a second data packet to the third protocol layer if the first condition is not met.

[0170] In some embodiments, the third protocol layer is the lower layer of the first protocol layer.

[0171] In some embodiments, the first protocol layer of the first device segments or copies multiple data packets or second data packets to obtain multiple copied data packet segments or multiple copied second data packets, and then sends the multiple copied data packet segments or multiple copied second data packets to the third protocol layer.

[0172] In some embodiments, multiple replicated data packets are sent in segments either sequentially or in a combined manner.

[0173] In some embodiments, the sending entity of the first protocol layer of the first device sends multiple data packet segments to the third protocol layer until the last data packet segment of the multiple data packet segments is sent to the bottom layer of the first device. The bottom layer is used to send each data packet segment to the receiving entity of the first protocol layer of the second device. The multiple data packet segments or the second data packet are then sent to the third protocol layer of the second device.

[0174] In some embodiments, the first protocol layer of the first device segments multiple data packets or sends the second data packet to the lowest layer of the first device, and transmits it to the lowest layer of the second device through the air interface.

[0175] In some embodiments, when the first device reconstructs the first protocol layer's transmission entity, it resets the first state variable to its initial value. Data packets that have not yet been sent to the third protocol layer are then segmented and sent to the third protocol layer.

[0176] In some embodiments, after the first device performs a handover, it needs to be rebuilt. In other words, after the first device performs a handover, it may no longer continue to execute according to the above logic, but instead send all data packets in segments to the lower layer for processing.

[0177] Step 2107: The receiving entity of the first protocol layer of the second device receives multiple data packet segments or the second data packet sent by the third protocol layer of the second device.

[0178] In some embodiments, the third protocol layer is the lower layer of the first protocol layer.

[0179] In some embodiments, multiple data packet segments are received by the bottom layer of the second device from the bottom layer of the first device.

[0180] In some embodiments, the receiving entity of the first protocol layer of the second device also needs to receive a second data packet sent by the third protocol layer. The second data packet is a data packet that has not been segmented on the first device side.

[0181] In some embodiments, for each of a plurality of packet segments, a timer associated with the SN field in the packet header is determined, and the timer is initially set to not start.

[0182] For example, a timer t-Reassembly associated with the SN is maintained for each received PDU segment, and the initial state of the timer is not started.

[0183] In some embodiments, if all packet segments with the same SN field are received, the first timer associated with the same SN field is stopped.

[0184] In some embodiments, if the first timer is not running, the first timer is started when a data packet segment with the same SN field is received.

[0185] In some embodiments, if the first timer times out, all packet segments with the same SN field are discarded.

[0186] In some embodiments, when the second device is a terminal, the second device receives second information sent by the access network device, and the second information is used to configure a timer.

[0187] For example, when a PDU with SN x is received, the following operations are performed: If all PDU segments with SN x have been received, the timer t-Reassembly associated with SN x is stopped; otherwise, if the timer t-Reassembly associated with SN x is not running, the timer t-Reassembly associated with SN x is started. When the timer t-Reassembly associated with SN x times out, all PDU segments with SN x are discarded.

[0188] Step 2108: The receiving entity of the first protocol layer of the second device reassembles multiple data packets into a third data packet.

[0189] In some embodiments, the reassembly operation of multiple data packet segments includes: for each of the multiple data packet segments, storing data packet segments with the same SN field in the packet header into a receive buffer; and, if all data packet segments with the same SN field have been received, reassembling all data packet segments with the same SN field into a third data packet.

[0190] In some embodiments, data packet segments with the same SN field in the packet header are stored in the receive buffer, that is, all data packet segments with the SN field having a preset value are stored in the receive buffer. In other words, all data packet segments with the same SN field will be stored in the receive buffer for data packet segment reassembly.

[0191] For example, the preset value can be x. The reassembly operation means storing the PDU with SN x in the header of each received packet into the receive buffer. When all PDU segments with SN x are received, the PDU segments are reassembled into a complete PDU.

[0192] It is understood that step 2108 is an optional step. If the receiving entity at the first protocol layer of the second device receives multiple data packet segments sent by the third protocol layer of the second device, the reassembly operation in step 2108 is performed. If the receiving entity at the first protocol layer of the second device receives a second data packet sent by the third protocol layer of the second device, the reassembly operation in step 2108 is not performed.

[0193] Step 2109: The receiving entity of the first protocol layer of the second device determines the count value of the data packets received by the first protocol layer.

[0194] In some embodiments, the receiving entity of the first protocol layer of the second device determines the count value of the received data packets of the first protocol layer based on the sequence number (SN) field in the header of the third data packet. When the SN field reaches the upper limit, the receiving entity does not perform a wrapback. The third data packet is obtained by reassembling multiple data packets into segments, or the third data packet is the second data packet.

[0195] It can be understood that if the receiving entity of the first protocol layer of the second device receives multiple data packet segments sent by the third protocol layer of the second device, then performing the reassembly operation in step 2108 will result in the third data packet being obtained by reassembling the multiple data packet segments. If the receiving entity of the first protocol layer of the second device receives the second data packet sent by the third protocol layer of the second device, then not performing the reassembly operation in step 2108 will result in the third data packet being the second data packet.

[0196] It should be noted that the header of the third data packet can be understood as the header of the first protocol layer. The data packet segments or the second data packet received by the first protocol layer both contain the header of the first protocol layer. The third data packet is the result of reassembling data packet segments, and it also contains the header of the first protocol layer. In other words, the third data packet still contains at least the SN from the original header.

[0197] In some embodiments, when the sending entity reaches the upper limit of the SN field during the sending process, the sending entity does not perform a wrapback. That is, when the corresponding receiving entity reaches the upper limit of the SN field, the receiving entity does not perform a wrapback. In other words, when the sending entity stops using the current entity to send data because the SN field has reached the upper limit, the corresponding receiving entity will not receive the data.

[0198] In some embodiments, the length of the count value is the sum of a first number of bits and the length of the SN field.

[0199] In some embodiments, the value of the first number of bits is zero; optionally, the first number of bits precedes the SN field.

[0200] In some embodiments, the length of the SN field is determined based on protocol conventions.

[0201] In some embodiments, the second device is a terminal, and the length of the SN field is determined based on first information sent by the access network device, the first information being used to configure the length of the SN field.

[0202] For example, the length of the SN field in the packet header is configured by the access network device by sending the first information. Specifically, the first information is transmitted in RRC signaling. In particular, the granularity of the first information configuration is a simplified protocol layer entity.

[0203] For example, the length of the SN field can be configured jointly for downlink and uplink data, or it can be configured separately for downlink and uplink data. In other words, the access network device can configure the length of the SN field jointly for uplink and downlink data, or it can configure it separately.

[0204] Step 2110: The receiving entity of the first protocol layer of the second device performs second processing on the third data packet.

[0205] In some embodiments, the second processing of the third data packet includes at least one of the following: using a count value as input to a security algorithm, performing decryption and / or integrity verification processing on the second data packet, and determining whether to discard the second data packet; if the second data packet is not discarded, performing header decompression processing on the second data packet.

[0206] In some embodiments, integrity verification may be used to prevent hacking attacks.

[0207] In some embodiments, the second data packet is decrypted and / or its integrity is verified. If the integrity verification fails, the corresponding second data packet is discarded and it is confirmed that the data packet was not received.

[0208] In some embodiments, determining whether to discard the second data packet includes: in the event of an integrity verification failure, determining to discard the second data packet and sending a verification failure notification to the Radio Resource Control (RRC) layer; and in the event that a data packet with a count value has already been received by the receiving entity, determining to discard the second data packet.

[0209] In some embodiments, if integrity verification fails, it is determined to discard the second data packet and send a verification failure notification to the RRC layer. The second protocol layer can be the RRC layer, which is the upper layer of LCC.

[0210] In some embodiments, the upper layer of the LCC layer can be either the RRC layer or the SDAP layer. When the LCC layer carries data, the upper layer is the SDAP layer; when the LCC layer carries signaling, the upper layer is the RRC layer. However, for an LCC entity whose upper layer is the SDAP layer, if an integrity verification failure occurs, a notification is also sent to the RRC layer. Therefore, regardless of whether the LCC layer carries data or signaling, when an integrity verification fails, the LCC layer sends a verification failure notification to the RRC layer.

[0211] For example, the COUNT value is used as input to the security algorithm for deciphering and integrity verification. If integrity verification fails, the receiving entity discards the data PDU and assumes that the data PDU has not been received, and notifies the higher layer of integrity verification failure. If the data PDU with the COUNT value has been received before, the data PDU is discarded. If the data PDU has not been discarded by the above steps, the SDU is passed to the higher protocol layer after packet header decompression.

[0212] It is understood that step 2110 is an optional step. The receiving entity of the first protocol layer of the second device may not perform the second processing on the third data packet.

[0213] Step 2111: The receiving entity of the first protocol layer of the second device sends the first data packet to the second protocol layer.

[0214] In some embodiments, the second protocol layer is the layer above the first protocol layer, the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is the third data packet, and the first data packet does not include the header information of the first protocol layer. For example, the header information includes information such as SN. In other words, the first data packet submitted by the first protocol layer to the upper layer is an SDU, and the SDU does not carry the header of this protocol layer (the first protocol layer).

[0215] It is understandable that if the receiving entity of the first protocol layer of the second device performs second processing on the third data packet, then step 2110 is executed, and the first data packet is obtained by performing second processing on the third data packet. If the receiving entity of the first protocol layer of the second device does not perform second processing on the third data packet, then step 2110 is not executed, and the first data packet is the third data packet. Regardless of whether the third data packet has undergone second processing, the data packets sent by the receiving entity of the first protocol layer of the second device to the upper layer do not carry the header of the first protocol layer.

[0216] In some embodiments, the receiving entity of the first protocol layer of the second device sends a third data packet that has not undergone the second processing to the second protocol layer.

[0217] In some embodiments, the receiving entity of the first protocol layer of the second device decrypts the second data packet, verifies its integrity, and then decompresses the resulting first data packet before sending it to the higher protocol layer.

[0218] In the above embodiment, when the receiving entity of the first protocol layer of the second device reconstructs the data packet, it discards all data packet segments.

[0219] In the above embodiment, when the receiving entity of the first protocol layer of the second device is rebuilt, all running timers are stopped.

[0220] In some embodiments, after the second device performs a handover, a rebuild is required. In other words, after the second device performs a handover, it may no longer continue to execute according to the above logic, but instead discard all data packets in segments and stop all running timers.

[0221] The communication method involved in the embodiments of this disclosure may include at least one of steps 2101 to 2111. For example, step 2101 may be tried as a standalone embodiment, step 2107 may be implemented as a standalone embodiment, and so on, but is not limited thereto. Steps 2101+2102+2103+2106, 2101+2103+2105+2106, 2101+2103+2104+2105+2106, 2101+2102+2103+2104+2106, 2101+2102+2103+2104+2105+2106, 2107+2109+2111, 2107+2109+2110+2111, 2107+2108+2109+2111, and 2107+2108+2109+2110+2111 can be implemented as independent embodiments, but are not limited thereto.

[0222] In some embodiments, steps 2102, 2104, and 2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0223] In some embodiments, steps 2108 and 2110 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0224] In this implementation or embodiment, unless there is contradiction, each step can be independent, arbitrarily combined or exchanged in order, optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other implementations or other embodiments.

[0225] Figure 3A is a schematic flowchart of a communication method for a first protocol layer transmitting entity of a first device according to an embodiment of the present disclosure. This disclosure relates to a data transmission method, which includes:

[0226] Step 3101: Receive the first data packet sent by the second protocol layer of the first device.

[0227] The optional implementation of step 3101 can be found in the optional implementation of step 2101 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0228] Step 3102: Perform first processing on the first data packet to obtain the second data packet.

[0229] The optional implementation of step 3102 can be found in the optional implementation of step 2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0230] Step 3103: Set the sequence number SN field in the packet header of the first protocol layer to the value of the first state variable.

[0231] The optional implementation of step 3103 can be found in the optional implementation of step 2103 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0232] Step 3104: Segment the second data packet.

[0233] The optional implementation of step 3104 can be found in the optional implementation of step 2104 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0234] Step 3105: Segment multiple data packets or copy the second data packet.

[0235] The optional implementation of step 3105 can be found in the optional implementation of step 2105 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0236] Step 3106: Send multiple data packets in segments to the third protocol layer, or send the second data packet to the third protocol layer.

[0237] The optional implementation of step 3106 can be found in the optional implementation of step 2106 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0238] The communication method involved in the embodiments of this disclosure may include at least one of steps 3101 to 3106. For example, step 3101 may be implemented as a standalone embodiment, or it may be implemented as a standalone embodiment. And so on, but not limited thereto. Steps 3101+3102+3103+3106, 3101+3103+3105+3106, 3101+3103+3104+3105+3106, 3101+3102+3103+3104+3106, and 3101+3102+3103+3104+3105+3106 may be implemented as standalone embodiments, but are not limited thereto.

[0239] In some embodiments, steps 3102, 3104, and 3105 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0240] Figure 3B is a schematic flowchart of a communication method for a first protocol layer transmitting entity of a first device according to an embodiment of the present disclosure. This disclosure relates to a data transmission method, which includes:

[0241] Step 3201: Receive the first data packet sent by the second protocol layer of the first device.

[0242] The second protocol layer is the layer above the first protocol layer.

[0243] The optional implementation of step 3201 can be found in step 2101 of Figure 2, the optional implementation of step 3101 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0244] Step 3202: Set the sequence number (SN) field in the packet header of the first protocol layer to the value of the first state variable, wherein the sending entity does not perform a wrapback when the SN field reaches its upper limit.

[0245] The first state variable is used to represent the count value of the data packets sent by the first protocol layer, and the count value is associated with the first data packet.

[0246] The optional implementation of step 3202 can be found in step 2103 of Figure 2, the optional implementation of step 3103 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0247] Step 3203: If the first condition is met, the second data packet is segmented to obtain multiple data packet segments.

[0248] The first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet. The third protocol layer is the lower layer of the first protocol layer. The second data packet is obtained by performing the first processing on the first data packet, or the second data packet is the first data packet.

[0249] The optional implementations of step 3203 can be found in steps 2102 and 2104 of Figure 2, the optional implementations of steps 3102 and 3104 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0250] Step 3204: Send each data packet segment from the multiple data packet segments to the third protocol layer, or if the first condition is not met, send the second data packet to the third protocol layer.

[0251] The optional implementations of step 3204 can be found in steps 2105 and 2106 of Figure 2, the optional implementations of steps 3105 and 3106 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0252] In the embodiments of this disclosure, step 3201 can be combined with step 3102 in FIG3A, step 3202 can be combined with step 3102 in FIG3A, step 3203 can be combined with step 3103 or 3105 in FIG3A, and step 3204 can be combined with step 3104 in FIG3A.

[0253] Figure 4A is a schematic flowchart of a communication method for a receiving entity of a first protocol layer in a second device according to an embodiment of the present disclosure. This disclosure relates to a data receiving method, which includes:

[0254] Step 4101: Receive multiple data packet segments or a second data packet sent by the third protocol layer of the second device.

[0255] The optional implementation of step 4101 can be found in the optional implementation of step 2107 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0256] Step 4102: Reassemble multiple data packets into segments to obtain the third data packet.

[0257] The optional implementation of step 4102 can be found in the optional implementation of step 2108 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0258] Step 4103: Determine the count value of the data packets received by the first protocol layer.

[0259] The optional implementation of step 4103 can be found in the optional implementation of step 2109 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0260] Step 4104: Perform a second processing on the third data packet.

[0261] The optional implementation of step 4104 can be found in the optional implementation of step 2110 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0262] Step 4105: Send the first data packet to the second protocol layer.

[0263] The optional implementation of step 4105 can be found in the optional implementation of step 2111 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.

[0264] The communication method involved in the embodiments of this disclosure may include at least one of steps 4101 to 4105. For example, step 4101 may be implemented as a standalone embodiment, and steps 4101+4103+4105, 4101+4103+4104+4105, 4101+4102+4103+4105, and 4101+4102+4103+4104+4105 may also be implemented as standalone embodiments.

[0265] In some embodiments, steps 4102 and 4104 are optional and can be omitted or replaced in different embodiments.

[0266] Figure 4B is a schematic flowchart of a communication method for a receiving entity of a first protocol layer in a second device according to an embodiment of the present disclosure. This disclosure relates to a data receiving method, which includes:

[0267] Step 4201: Receive multiple data packet segments or a second data packet sent by the third protocol layer of the second device.

[0268] The third protocol layer is the layer below the first protocol layer.

[0269] The optional implementation of step 4201 can be found in step 2107 of Figure 2, the optional implementation of step 4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0270] Step 4202: Determine the count value of the received data packets of the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit.

[0271] The third data packet is obtained by reassembling multiple data packets into segments, or the third data packet is the second data packet.

[0272] The optional implementations of step 4202 can be found in steps 2108 and 2109 of Figure 2, steps 4102 and 4103 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0273] Step 4203: Send the first data packet to the second protocol layer, which is the upper layer of the first protocol layer.

[0274] The first data packet is obtained by performing a second processing on the third data packet, or the first data packet is the third data packet, and the first data packet does not include the header information of the first protocol layer.

[0275] The optional implementations of step 4203 can be found in steps 2110 and 2111 in Figure 2, steps 4104 and 4105 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0276] In the embodiments of this disclosure, step 4201 can be combined with step 4102 in FIG4A, step 4202 can be combined with step 4101 or 4104 in FIG4A, and step 4203 can be combined with step 4103 in FIG4A.

[0277] Figure 5 is an interactive schematic diagram of the communication method provided according to an embodiment of the present disclosure. This disclosure relates to a communication method, which includes:

[0278] Step 5101: The sending entity of the first protocol layer of the first device receives the first data packet sent by the second protocol layer of the first device.

[0279] The second protocol layer is the layer above the first protocol layer.

[0280] The optional implementation of step 5101 can be found in the optional implementation of step 2101 in Figure 2, step 3101 in Figure 3A, step 3201 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0281] Step 5102: Set the sequence number (SN) field in the header of the first protocol layer to the value of the first state variable. When the SN field reaches its upper limit, the sending entity does not perform a wrapback. The first state variable is used to represent the count value of the data packets sent by the first protocol layer, and the count value is associated with the first data packet.

[0282] The optional implementation of step 5102 can be found in the optional implementation of step 2103 in Figure 2, step 3103 in Figure 3A, step 3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0283] Step 5103: If the first condition is met, the sending entity of the first protocol layer of the first device segments the second data packet to obtain multiple data packet segments; and sends each data packet segment in the multiple data packet segments to the third protocol layer, or if the first condition is not met, sends the second data packet to the third protocol layer.

[0284] The first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet. The third protocol layer is the lower layer of the first protocol layer, and the second data packet is obtained by performing the first processing on the first data packet, or the second data packet is the first data packet.

[0285] The optional implementations of step 5103 can be found in steps 2102, 2104, 2105, and 2106 in Figure 2, steps 3102, 3104, 3105, and 3106 in Figure 3A, steps 3203 and 3204 in Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0286] Step 5104: The receiving entity of the first protocol layer of the second device receives multiple data packet segments or the second data packet sent by the third protocol layer of the second device.

[0287] The third protocol layer is the layer below the first protocol layer.

[0288] The optional implementation of step 5104 can be found in the optional implementation of step 2107 in Figure 2, step 4101 in Figure 4A, step 4201 in Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0289] Step 5105: Determine the count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit; send the first data packet to the second protocol layer, the second protocol layer being the upper layer of the first protocol layer, the first data packet being obtained by performing the second processing on the third data packet, or the first data packet being the third data packet.

[0290] The third data packet is obtained by reassembling multiple data packets into segments, or the third data packet is the second data packet, and the first data packet does not include the header information of the first protocol layer.

[0291] The optional implementations of step 5105 can be found in steps 2108, 2109, 2110, and 2111 in Figure 2; steps 4102, 4103, 4104, and 4105 in Figure 4A; steps 4202 and 4203 in Figure 4B; and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0292] The communication method involved in the embodiments of this disclosure may include at least one of steps 5101-5105. For example, step 5101 may be implemented as a standalone embodiment, step 5104 may be implemented as a standalone embodiment, and steps 5101+5102+5103, 5104+5105, and 5101+5102+5103+5104+5105 may be implemented as standalone embodiments.

[0293] In summary, the communication method provided in this disclosure simplifies the processing complexity of the protocol stack by reducing the variables that need to be maintained at the protocol layer and merging the functions of the PDCP layer and RLC layer, thereby further and more effectively supporting the high-speed data transmission requirements.

[0294] The following is a specific scheme of a communication method provided in this disclosure, including the following method steps:

[0295] 1. The transmitting entity of the first device sets COUNT as the first state variable and associates the COUNT value with the SDU received from the higher layer of the protocol stack. The initial value of the first state variable is 0.

[0296] Optionally, the SDU header can be compressed.

[0297] Optionally, the COUNT value can be used as input to a security algorithm for integrity protection and encryption.

[0298] Set the SN field in the protocol layer header to the COUNT value, where the SN will not wrap around;

[0299] Data that has undergone header compression and / or integrity protection and / or encryption is segmented into PDUs of the protocol layer according to the space provided by the lower protocol layer. The segmentation operation is optional, that is, segmentation is only performed if the lower protocol layer cannot completely contain the PDU.

[0300] If the protocol layer PDU contains the last byte of data that has undergone header compression and / or integrity protection and / or encryption, then increment the first state variable by 1;

[0301] The protocol layer sends the PDU to the lower protocol layer.

[0302] SDU is equivalent to data that has undergone header compression and / or integrity protection and / or encryption.

[0303] 2. Optionally, the first device is a terminal.

[0304] 3. Optionally, the first device is an access network device.

[0305] 4. The length of the SN field in the packet header is determined by the protocol. In particular, the length of both the COUNT and SN fields is 32.

[0306] 5. The length of the SN field in the packet header is configured by the access network device by sending the first information. In particular, the first information is transmitted in the RRC signaling.

[0307] Specifically, the granularity of the first information configuration is the entity of the simplified protocol layer. The length of the SN field can be configured jointly for downlink and uplink data, or separately for downlink and uplink data.

[0308] Example 1, as shown in Figure 6A, the SN field and several 0s form COUNT, that is, SN is LSB, and the actual value of COUNT is the same as SN.

[0309] 6. The packet header may contain a first field, which indicates the location of the PDU after packet header compression and / or integrity protection and / or encryption. The first field can be indicated in two ways:

[0310] Method 1: The first field indicates the position in bytes, that is, the first byte in the Data field of the PDU corresponds to the position of the data after packet header compression and / or integrity protection and / or encryption.

[0311] After the data has undergone header compression and / or integrity protection and / or encryption, the first field value corresponding to the first byte is 0, meaning the numbering starts from 0. Hereinafter, the first field in Method 1 will be referred to as the Segmentation Offset (SO) field.

[0312] Method 2: The first field indicates the index, which is the PDU number after the data has been segmented following header compression and / or integrity protection and / or encryption. This numbering starts from 0; that is, the first field value for the first segment is 0, the first field value for the second segment is 1, and so on. Hereinafter, the first field in Method 2 will be referred to as the index field.

[0313] 7. The packet header always contains the following two fields:

[0314] First field;

[0315] The second field indicates whether the PDU is the last segment of the corresponding SDU. The second field will be indicated as LS (Last Segment) below.

[0316] Example 2, as shown in Figure 6B, illustrates the PDU format corresponding to 1, 6, and 7, with each field as follows:

[0317] D / C: Indicates whether the PDU is a data PDU or a control PDU. For example, a value of 0 indicates a control PDU, and a value of 1 indicates a data PDU.

[0318] LS: The second field as described in section 7. For example, a value of 0 indicates that the PDU is not the last segment of its corresponding SDU, while a value of 1 indicates that the PDU is the last segment of its corresponding SDU. The receiving side can use the LS field to determine whether all segments corresponding to the PDU have been received.

[0319] SN: The SN field (Sequence Number) as described in 1. In this embodiment, the SN field is 22 bits long.

[0320] SO: The SO field as described in 6. In this embodiment, the SO field as described in 7 is always present in the packet header, thus the length of the packet header is fixed, which facilitates processing by the receiving side.

[0321] Data, MAC-I: Data after header compression and / or integrity protection and / or encryption, where MAC-I (Message Authentication Code for Integrity) is the integrity protection verification information. Typically, MAC-I is transmitted after the data (as shown in Figure 6B), meaning that Figure 6B shows either the last segment or an unsegmented case.

[0322] 8. The header always contains a third field that indicates segmentation information and at least indicates whether the header contains the first field.

[0323] Example 3: As shown in Figure 6C, this is the PDU format corresponding to 1, 6, and 8. The D / C, Data, and MAC-I fields are the same as in Example 2 and will not be described again. The remaining fields are as follows:

[0324] R: Reserved field. This field is usually set to 0, and the receiving end will ignore this field.

[0325] SN: The SN field as described in 1. In this embodiment, the SN field is 32 bits long.

[0326] SI: As described in section 8, the third field is Segmentation Information (SI). This field indicates whether the PDU contains a complete SDU (i.e., data after header compression and / or integrity protection and / or encryption), or the first, middle, or last segment of the SDU. For example, "00" indicates that the PDU contains a complete SDU, "01" indicates that it contains the first segment of the SDU, "10" indicates that it contains the last segment of the SDU, and "11" indicates that it is neither the first nor the last segment.

[0327] SO: The SO field as described in 6. In this embodiment, the presence of the SO field in the packet header is indicated by the SI field. For example, if the SI field is "10" or "11" (i.e., the PDU does not have a complete SDU, or does not contain the first segment of the SDU), the packet header contains the SO field; otherwise, the packet header does not contain the SO field.

[0328] Example 4: Figure 6D shows the user plane data stream processing flow. In this example, the name of the simplified protocol layer mentioned in 1 is LCC (Lean Convergence Control). In this example, it is assumed that the upper layer of the LCC layer is the SDAP layer and the lower layer is the MAC layer. SDAP SDU 1 and SDU 2 correspond to LCC PDU 1 and PDU 2, respectively. In this example, LCC PDU refers to the unsegmented PDU, while LCC PDU Segment refers to the segmented PDU. PDU and PDU Segment include packet headers. The reason for using LCC PDU and LCC PDU Segment instead of LCC SDU and LCC SDU Segment in Figure 6D is that SDUs undergo packet header compression and / or integrity protection and / or encryption. SDAP SDU 3 is segmented into LCC PDU Segment 1 and Segment 2 at the LCC layer. LCC PDU 1, LCC PDU 2 and LCC PDU Segment 1 are multiplexed at the MAC layer to become MAC PDU 1.

[0329] 9. A single PDU from the simplified protocol layer can be sent to multiple lower protocol layers. In particular, when the lower protocol layer is the MAC layer, a single PDU from the simplified protocol layer can be sent to multiple logical channels.

[0330] Example 5, Figure 6E shows a schematic diagram of PDU being sent to multiple logical channels. The main applicable scenario is packet duplication. In this example, the PDU can be sent to two logical channels: a primary logical channel and a secondary logical channel. The PDU can also be sent to more than two logical channels; this example does not impose any restrictions. The simplified protocol layer sends the PDU to the lower protocol layer according to the following process:

[0331] If the sending entity is associated with a logical channel or packet replication is not activated, the PDU will be sent to the corresponding logical channel.

[0332] Otherwise: If the PDU is a data PDU; copy the PDU and send it to the corresponding logical channel that has already activated packet copying;

[0333] Otherwise: Send the PDU (i.e., the control PDU) to the main logic channel;

[0334] 10. When the simplified protocol layer's sending entity is rebuilt, it resets the first state variable to 0 and sends the PDUs that have not yet been sent to the lower protocol layer to the lower protocol layer.

[0335] Optionally, the optional implementation of steps 1-10 on the sending side can be found in the optional implementation of steps 2101-2106 in Figure 2.

[0336] Receiving side:

[0337] 11. The receiving entity of the second device performs a reassembly operation on the received PDU;

[0338] The following steps are performed on the reassembled and fully received data PDU: the COUNT value is confirmed based on the SN field in the packet header, wherein the SN field and several zeros constitute the COUNT, and the SN will not wrap around; optionally, the COUNT value is used as input to a security algorithm for deciphering and integrity verification.

[0339] When the integrity verification fails, the receiving entity discards the data PDU and considers that the data PDU has not been received, and notifies the higher layer of the integrity verification failure.

[0340] If a data PDU with this COUNT value has already been received, then discard the data PDU.

[0341] If the data PDU is not discarded in the above steps, the SDU is passed to the higher-level protocol layer after header decompression (optional operation).

[0342] 12. The reassembly operation involves storing the PDU with SN x in the header of each received packet into the received data. When all PDU segments with SN x have been received, the PDU segments are reassembled into a complete PDU.

[0343] 13. Maintain a timer associated with the SN for each received PDU. The initial state of the timer is not started. When a PDU with SN x is received, perform the following operation:

[0344] If all PDU segments with SN x are received: stop the timer t-Reassembly associated with SN x;

[0345] Otherwise, if the timer t-Reassembly associated with SN x is not running, start the timer t-Reassembly associated with SN x.

[0346] When the timer t-Reassembly associated with SN x times out, all PDU segments with SN x are discarded.

[0347] 14. The timer t-Reassembly is configured by the access network device by sending second information. Specifically, the second information is transmitted in RRC signaling. Specifically, the granularity of the second information configuration is the entity of the simplified protocol layer. Specifically, the timer t-Reassembly is configured for receiving downlink data transmissions.

[0348] 15. In the method described in 11, the receiving entity of the simplified protocol layer discards all PDU segments during reconstruction.

[0349] 16. In the methods described in 11 and 13, the receiving entity of the simplified protocol layer stops all running timers t-Reassembly during reconstruction.

[0350] Example 6: Figure 6F shows a functional diagram of the Reduced Protocol Layer (PPL). This diagram is for illustrative purposes only and does not limit the specific implementation. Depending on the specific configuration, some functions in this diagram may be omitted. A terminal can have multiple PPL entities. Each PPL entity can be associated with a radio bearer.

[0351] Optionally, the optional implementation of steps 11-16 on the receiving side can be found in the optional implementation of steps 2108-2111 in Figure 2.

[0352] In the embodiments disclosed herein, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations in other embodiments.

[0353] This disclosure also provides an apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0354] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0355] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0356] Figure 7A is a schematic diagram of the structure of a first protocol layer transmitting entity provided according to an embodiment of the present disclosure. As shown in Figure 7A, the first protocol layer transmitting entity 7100 includes a transceiver module 7101 and a processing module 7102.

[0357] In some embodiments, the transceiver module is used to receive a first data packet sent by a second protocol layer of the first device, wherein the second protocol layer is an upper layer of the first protocol layer.

[0358] In some embodiments, the transceiver module is further configured to send each data packet segment in the plurality of data packet segments to the third protocol layer, or, if the first condition is not met, send the second data packet to the third protocol layer.

[0359] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending or receiving performed by the terminal 7100 in any of the above methods (e.g., steps 2101, 2106, 3101, 3106, 3201, 3204, but not limited thereto), which will not be elaborated here.

[0360] In some embodiments, the processing module is configured to set the sequence number (SN) field in the header of the first protocol layer to the value of a first state variable, wherein the sending entity does not perform a wrapback when the SN field reaches its upper limit, and the first state variable is used to represent the count value of the data packets sent by the first protocol layer, and the count value is associated with the first data packet.

[0361] In some embodiments, the processing module is further configured to segment the second data packet to obtain multiple data packet segments when a first condition is met. The first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet. The third protocol layer is the lower layer of the first protocol layer. The second data packet is obtained by performing the first processing on the first data packet, or the second data packet is the first data packet.

[0362] Optionally, the processing module is used to execute at least one of the other communication steps (e.g., steps 2102, 2103, 2104, 2105, 3102, 3103, 3104, 3105, 3202, 3203, but not limited thereto) executed by the sending entity 7100 of the first protocol layer in any of the above methods, which will not be described in detail here.

[0363] Figure 7B is a schematic diagram of the structure of a receiving entity of the first protocol layer according to an embodiment of the present disclosure. As shown in Figure 7B, the receiving entity 7200 of the first protocol layer may include a transceiver module 7201 and a processing module 7202.

[0364] In some embodiments, the transceiver module is used to receive multiple data packet segments or a second data packet sent by a third protocol layer, where the third protocol layer is the lower layer of the first protocol layer.

[0365] In some embodiments, the transceiver module is further configured to send a first data packet to a second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, the first data packet is obtained by performing a second processing on a third data packet, or the first data packet is a third data packet, and the first data packet does not include the header information of the first protocol layer.

[0366] Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the receiving entity 7200 of the first protocol layer in any of the above methods (e.g., steps 2107, 2111, 4101, 4105, 4201, 4203, but not limited thereto), which will not be elaborated here.

[0367] In some embodiments, the processing module is used to determine the count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform a wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling multiple data packets into segments, or the third data packet is the second data packet.

[0368] Optionally, the processing module is used to execute at least one of the other communication steps (e.g., steps 2108, 2109, 2110, 4102, 4103, 4104, 4202, but not limited thereto) executed by the receiving entity 7200 of the first protocol layer in any of the above methods, which will not be described in detail here.

[0369] Figure 8A is a schematic diagram of the structure of a communication device 8100 provided according to an embodiment of this disclosure. The communication device 8100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 8100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0370] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 8100 can be used to execute any of the above methods. Optionally, one or more processors 8101 can be used to invoke instructions to cause the communication device 8100 to execute any of the above methods.

[0371] In some embodiments, the communication device 8100 further includes one or more transceivers 8102. When the communication device 8100 includes one or more transceivers 8102, the transceiver 8102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 2101, 2106, 3101, 3106, 3201, 3204, 2107, 2111, 4101, 4105, 4201, 4203, but not limited thereto), and the processor 8101 performs at least one of other steps (e.g., steps 2102, 2103, 2104, 2105, 3102, 3103, 3104, 3105, 3202, 3203, 2108, 2109, 2110, 4102, 4103, 4104, 4202, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0372] In some embodiments, the communication device 8100 further includes one or more memories 8103 for storing data. Optionally, all or part of the memories 8103 may be located outside the communication device 8100. In an optional embodiment, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuits 8104 are connected to the memories 8102, and the interface circuits 8104 can be used to receive data from the memories 8102 or other devices, and can be used to send data to the memories 8102 or other devices. For example, the interface circuits 8104 can read data stored in the memories 8102 and send the data to the processor 8101.

[0373] In some embodiments, the processor 8101 may store a computer program 8105, which runs on the processor 8101 and enables the communication device 8000 to perform the methods described in the above method embodiments. The computer program 8105 may be embedded in the processor 8101, in which case the processor 8101 may be implemented in hardware.

[0374] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in this disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG8A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0375] Figure 8B is a schematic diagram of the structure of chip 8200 according to an embodiment of this disclosure. For cases where the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of chip 8200 shown in Figure 8B, but it is not limited thereto.

[0376] Chip 8200 includes one or more processors 8201. Chip 8200 is used to perform any of the methods described above.

[0377] In some embodiments, chip 8200 further includes one or more interface circuits 8202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 8200 further includes one or more memories 8203 for storing data. Optionally, all or part of the memories 8203 may be located outside of chip 8200. Optionally, interface circuit 8202 is connected to memory 8203, and interface circuit 8202 can be used to receive data from memory 8203 or other devices, and interface circuit 8202 can be used to send data to memory 8203 or other devices. For example, interface circuit 8202 can read data stored in memory 8203 and send the data to processor 8201.

[0378] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps 2101, 2106, 3101, 3106, 3201, 3204, 2107, 2111, 4101, 4105, 4201, 4203, but not limited thereto). The interface circuit 8202 performing the communication steps such as sending and / or receiving in the above method refers, for example, to the interface circuit 8202 performing data interaction between the processor 8201, the chip 8200, the memory 8203, or the transceiver device. In some embodiments, the processor 8201 performs at least one of other steps (e.g., steps 2102, 2103, 2104, 2105, 3102, 3103, 3104, 3105, 3202, 3203, 2108, 2109, 2110, 4102, 4103, 4104, 4202, but not limited thereto).

[0379] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0380] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 8100, cause the communication device 8100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0381] This disclosure also provides a program product that, when executed by the communication device 8100, causes the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0382] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A data transmission method, characterized in that, The method is performed by a transmitting entity of the first protocol layer of the first device, and the method includes: Receives a first data packet sent by the second protocol layer of the first device, wherein the second protocol layer is the upper layer of the first protocol layer; The sequence number (SN) field in the header of the first protocol layer is set to the value of the first state variable, wherein the sending entity does not perform a wrapback when the SN field reaches its upper limit. The first state variable is used to represent the count value of the data packet sent by the first protocol layer, and the count value is associated with the first data packet. Under the condition that the first condition is met, the second data packet is segmented to obtain multiple data packet segments. The first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet. The third protocol layer is the lower layer of the first protocol layer. The second data packet is obtained by performing the first processing on the first data packet, or the second data packet is the first data packet. Each of the multiple data packet segments is sent to the third protocol layer, or, if the first condition is not met, the second data packet is sent to the third protocol layer.

2. The method according to claim 1, characterized in that, The first process includes at least one of the following: The header of the first data packet is compressed; The count value is used as input to the security algorithm to perform integrity protection and encryption on the first data packet compressed by the header.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Under the second condition, the first state variable is incremented by 1. The second condition is that the multiple data packet segments include the last byte of the second data packet, or the second data packet is not segmented.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Based on the protocol agreement, the length of the SN field in the packet header is determined.

5. The method according to any one of claims 1 to 3, characterized in that, The first device is a terminal, and the method further includes: Receive first information sent by the access network device, the first information being used to configure the length of the SN field; Based on the first information, the length of the SN field is determined.

6. The method according to any one of claims 1 to 5, characterized in that, The length of the count value is the sum of a first number of bits and the length of the SN field.

7. The method according to any one of claims 1 to 6, characterized in that, The package head includes: The first field is used to indicate the position of the first data packet segment in the second data packet among the plurality of data packet segments; The second field is used to indicate whether the first data packet segment among the plurality of data packet segments is the last segment of the second data packet.

8. The method according to any one of claims 1 to 6, characterized in that, The package head includes: The third field is used to indicate the segmentation information of the first data packet segment among the plurality of data packet segments and whether the packet header contains the first field. The first field is used to indicate the position of the first data packet segment in the second data packet.

9. The method according to claim 7, characterized in that, The value of the first field is the initial position of the plurality of data packet segments in the second data packet, or the value of the first field is the index value of the plurality of data packet segments.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: The multiple data packets are segmented or the second data packet is copied to obtain multiple copied data packet segments or multiple copied second data packets; Specifically, sending the multiple data packets in segments to the third protocol layer includes: sending the multiple copied data packets in segments or sending the multiple copied second data packets to the third protocol layer.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: When the sending entity of the first protocol layer is reconstructed, the first state variable is reset to its initial value; Data packets that have not yet been sent to the third protocol layer are sent to the third protocol layer in segments.

12. A data receiving method, characterized in that, The method is performed by a receiving entity at the first protocol layer of the second device, and the method includes: Receive multiple data packet segments or second data packets sent by the third protocol layer of the second device, wherein the third protocol layer is the lower layer of the first protocol layer; The count value of the data packets received by the first protocol layer is determined based on the sequence number (SN) field in the header of the third data packet. When the SN field reaches the upper limit, the receiving entity does not perform a wrapback. The third data packet is obtained by reassembling the segments of the multiple data packets, or the third data packet is the second data packet. A first data packet is sent to a second protocol layer, the second protocol layer being the upper layer of the first protocol layer. The first data packet is obtained by performing a second processing on the third data packet, or the first data packet is the third data packet. The first data packet does not include the header information of the first protocol layer.

13. The method according to claim 12, characterized in that, The second process includes at least one of the following: The count value is used as input to a security algorithm to decrypt and / or verify the integrity of the second data packet, and to determine whether to discard the second data packet. If the second data packet is not dropped, the header of the second data packet is decompressed.

14. The method according to claim 13, characterized in that, Determining whether to discard the second data packet includes: In the event that the integrity verification fails, the second data packet is discarded, and a verification failure notification is sent to the Radio Resource Control (RRC) layer. If it is determined that a data packet with the count value has already been received by the receiving entity, the second data packet is discarded.

15. The method according to any one of claims 12 to 14, characterized in that, The method further includes: Based on the protocol agreement, the length of the SN field in the packet header is determined.

16. The method according to any one of claims 12 to 14, characterized in that, The second device is a terminal, and the method further includes: Receive first information sent by the access network device, the first information being used to configure the length of the SN field; Based on the first information, the length of the SN field is determined.

17. The method according to any one of claims 12 to 16, characterized in that, The method further includes: For each of the plurality of data packet segments, the data packet segments with the same SN field in the packet header are stored in the receive buffer; If all data packet segments with the same SN field are received, all data packet segments with the same SN field are reassembled into the third data packet.

18. The method according to any one of claims 12 to 17, characterized in that, The method further includes: For each of the plurality of data packet segments, a timer is determined that is associated with the SN field in the packet header, the timer being initially set to not start.

19. The method according to claim 18, characterized in that, The method further includes at least one of the following: If all data packet segments with the same SN field are received, stop the first timer, which is associated with the same SN field. If the first timer is not running, the first timer is started when a data packet segment with the same SN field is received; If the first timer times out, all data packet segments with the same SN field are discarded.

20. The method according to claim 18 or 19, characterized in that, The second device is a terminal, and the method further includes: The system receives second information sent by the access network device, the second information being used to configure the timer.

21. The method according to claims 12 to 20, characterized in that, The method further includes: When the receiving entity of the first protocol layer reconstructs the data, all data packet segments are discarded.

22. The method according to claims 12 to 21, characterized in that, The method further includes: When the receiving entity of the first protocol layer is reconstructing, all running timers are stopped.

23. The method according to claims 12 to 22, characterized in that, The length of the count value is the sum of a first number of bits and the length of the SN field.

24. A transmitting entity of a first protocol layer, characterized in that, include: The transceiver module is used to receive a first data packet sent by the second protocol layer of the first device, wherein the second protocol layer is the upper layer of the first protocol layer; The processing module is further configured to: set the sequence number (SN) field in the packet header of the first protocol layer to the value of a first state variable, wherein when the SN field reaches the upper limit, the sending entity does not perform a wrapback, and the first state variable is used to represent the count value of the data packet sent by the first protocol layer, and the count value is associated with the first data packet; The processing module is further configured to: segment the second data packet to obtain multiple data packet segments when a first condition is met, wherein the first condition is that the space provided by the third protocol layer of the first device cannot completely contain the second data packet, the third protocol layer is the lower layer of the first protocol layer, and the second data packet is obtained by performing the first processing on the first data packet, or the second data packet is the first data packet; The transceiver module is further configured to: send each data packet segment from the plurality of data packet segments to the third protocol layer, or, if the first condition is not met, send the second data packet to the third protocol layer.

25. A receiving entity for a first protocol layer, characterized in that, include: The transceiver module is used to receive multiple data packet segments or a second data packet sent by the third protocol layer of the second device, wherein the third protocol layer is the lower layer of the first protocol layer; The processing module is further configured to: determine the count value of the data packets received by the first protocol layer based on the sequence number (SN) field in the header of the third data packet, wherein the receiving entity does not perform wrapback when the SN field reaches the upper limit, and the third data packet is obtained by reassembling the multiple data packets into segments, or the third data packet is the second data packet; The transceiver module is further configured to: send a first data packet to a second protocol layer, wherein the second protocol layer is an upper layer of the first protocol layer, the first data packet is obtained by performing a second processing on the third data packet, or the first data packet is the third data packet, and the first data packet does not include the header information of the first protocol layer.

26. A communication device, wherein, include: transceiver; Memory; The processor is connected to the transceiver and the memory respectively, and is configured to control the wireless signal transmission and reception of the transceiver by executing computer-executable instructions on the memory, and is capable of implementing the method of any one of claims 1-23.

27. A computer storage medium, wherein, The computer storage medium stores computer-executable instructions; when executed by a processor, the computer-executable instructions can implement the method of any one of claims 1-23.

Images