A data transmission method, a sending device and a storage medium

By providing a data transmission method in the sending device, the transmission behavior and path configuration problems when the replication transmission state is deactivated are solved, and the switching from the replication transmission mode to the separate transmission mode and the flexible configuration of the data path are realized, which improves the transmission Reliability and adaptability.

CN115103340BActive Publication Date: 2024-12-06GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210900109.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-04-09
Publication Date
2024-12-06
Estimated Expiration
2040-04-09

AI Technical Summary

Technical Problem

In the case where the replicated transmission state is deactivated, the transmission behavior of the sending device is not clear, especially the problem of how to determine the separation auxiliary path and configure the uplink data separation threshold is not solved.

Method used

Provides a data transmission method, in the case where the copy transmission state is deactivated, the sending device transmits data based on the separate transmission mode, or submits the data to the main path or the separate auxiliary path, and determines the data transmission mode by configuring a first threshold, Ensure that the sending device can switch to the appropriate transmission path and mode when certain conditions are met.

Benefits of technology

It clarifies the transmission behavior of the sending device when the replication transmission state is deactivated. It can fall back from the replication transmission mode to the separate transmission mode, or submit data to the main path or separate auxiliary path, which solves the configuration of the separate auxiliary path and data transmission mode. The problem was not clarified, improving the flexibility and reliability of transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115103340B_ABST
    Figure CN115103340B_ABST
Patent Text Reader

Abstract

The present application discloses a data transmission method, comprising: when the copy transmission state is deactivated, if a first condition is met, a sending device transmits data based on a separate transmission mode, or the sending device delivers the data to a primary path or a separate auxiliary path. The present application also discloses another data transmission method, a sending device and a storage medium.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the PCT international patent application PCT / CN2020 / 084063 with an application date of April 9, 2020, which entered the Chinese national phase with Chinese patent application number 202080074780.8 and the invention name being “A data transmission method, sending device and storage medium”. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a data transmission method, a sending device and a storage medium. Background Art

[0003] In the related art, when the copy transmission state is deactivated, the transmission behavior of the sending device has not been clarified. Summary of the invention

[0004] The embodiments of the present application provide a data transmission method, a sending device, and a storage medium, which clarify the transmission behavior of the sending device when the copy transmission state is deactivated.

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, comprising: when the copy transmission state is deactivated, if a first condition is met, the sending device transmits data based on a separate transmission mode, or the sending device delivers the data to a main path (leg) or a separate auxiliary path.

[0006] In a second aspect, an embodiment of the present application provides a data transmission method, including: when a third condition is met, a sending device determines that a path corresponding to a radio link control (Radio Link Control, RLC) entity of a non-main path is a separated auxiliary path, and the separated auxiliary path is used for separated transmission.

[0007] In a third aspect, an embodiment of the present application provides a data transmission method, including: when a fourth condition is met, a sending device configures a copy transmission state.

[0008] In a fourth aspect, an embodiment of the present application provides a data transmission method, comprising: when a second condition is met, a sending device configures a first threshold, and the first threshold is used to determine a data transmission mode of the sending device.

[0009] In the fifth aspect, an embodiment of the present application provides a sending device, which includes: a sending unit, configured to transmit data based on a separate transmission mode if a first condition is met when the copy transmission state is deactivated, or to deliver the data to a main path or a separate auxiliary path.

[0010] In a sixth aspect, an embodiment of the present application provides a sending device, comprising: a second processing unit, configured to, when a third condition is met, determine that the path corresponding to the RLC entity of the non-main path is a separated auxiliary path, and the separated auxiliary path is used for separated transmission.

[0011] In a seventh aspect, an embodiment of the present application provides a sending device, comprising: a third processing unit, configured to configure a copy transmission state when a fourth condition is met.

[0012] In an eighth aspect, an embodiment of the present application provides a sending device, comprising: a fourth processing unit, configured to configure a first threshold when a second condition is met, wherein the first threshold is used to determine a data transmission mode of the sending device.

[0013] In a ninth aspect, an embodiment of the present application provides a sending device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when used to run the computer program, executes the steps of the data transmission method executed by the above-mentioned terminal device.

[0014] In the tenth aspect, an embodiment of the present application provides a chip, including: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned sending device.

[0015] In the eleventh aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned sending device.

[0016] In a twelfth aspect, an embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method performed by the above-mentioned sending device.

[0017] In a thirteenth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method performed by the above-mentioned sending device.

[0018] The data transmission method, sending device and storage medium provided in the embodiment of the present application include: when the copy transmission state is deactivated, if the first condition is met, the sending device transmits data based on the separation transmission mode, or the sending device delivers the data to the main path or the separation auxiliary path. It is thus clarified that when the copy transmission state is deactivated, the transmission behavior of the sending device can be: falling back from the copy transmission mode to the separation transmission mode, or delivering data to the main path or the separation auxiliary path. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 This is a schematic diagram of the replication transmission of the data radio bearer of this application;

[0020] Figure 2 This is a schematic diagram of the structure of the communication system according to the embodiment of the present application;

[0021] Figure 3 A schematic diagram of an optional processing flow of the data transmission method according to an embodiment of the present application;

[0022] Figure 4 This is another optional processing flow diagram of the data transmission method according to an embodiment of the present application;

[0023] Figure 5 A schematic diagram of another optional processing flow of the data transmission method according to an embodiment of the present application;

[0024] Figure 6 This is another optional processing flow diagram of the data transmission method according to the embodiment of the present application;

[0025] Figure 7 This is a schematic diagram of an optional structure of a sending device according to an embodiment of the present application;

[0026] Figure 8 This is another optional structural diagram of the sending device according to the embodiment of the present application;

[0027] Fig. 9 This is another optional structural diagram of the sending device in the embodiment of the present application;

[0028] Fig.10 This is a schematic diagram of another optional composition structure of the sending device in the embodiment of the present application;

[0029] Fig.11 This is a schematic diagram of the hardware composition structure of the sending device according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

[0031] Before describing the embodiments of the present application in detail, a brief description is given as follows.

[0032] New Radio (NR) Industrial interest of Things (IIoT) requires support for the transmission of services such as industrial automation (Factory automation), transport automation (Transport Industry), and smart power (Electrical Power Distribution) in NR systems. Based on the transmission requirements of service latency and reliability, IIoT introduces the concept of time sensitive network (TSN) network or TSC. In order to achieve high reliability and low latency transmission of services, the research direction of data duplication and multi-connectivity is introduced, and the Duplication architecture combining dual connectivity (DC) and carrier aggregation (CA) is determined to further improve the reliability of services.

[0033] The duplication bearer can be configured with up to 4 transmission paths or RLC entities; the bearer may include: Data Radio Bearer (DRB) or Signaling Radio Bearer (SRB). The duplication mechanism can be applied to CA scenarios or DC and CA scenarios. It can be described as: Specify PDCP duplication with up to 4RLC entities configured by RRC inarchitectural combinations including CA only and NR-DC in combination with CA.

[0034] Data replication is performed at the Packet Data Convergence Protocol (PDCP) layer, and the same PDCP protocol data unit (PDU) is mapped to different RLC entities. Data replication transmission is also called PDCP replication transmission. The Media Access Control (MAC) needs to transmit the replicated data of different RLC entities to different carriers. At this time, the corresponding number of RLC entities can be at least one: for example, the number of RLC entities is 1, 2, 3 or 4.

[0035] For CA scenarios, solutions that support data duplication use the data duplication function of PDCP to transmit the duplicated PDCP PDU to two RLC entities (i.e., two different logical channels) respectively, and ultimately ensure that the duplicated PDCP PDU can be transmitted on different physical layer aggregated carriers, thereby achieving frequency diversity gain and improving data transmission reliability; Figure 1 DRB ID1 and DRB ID3 are shown.

[0036] For the DC scenario, the solution supporting data duplication uses the data duplication function of PDCP to transmit the duplicated PDCP PDU to two RLC entities respectively, and the two RLC entities correspond to different MAC entities respectively; Figure 1 DRB ID 2 is shown.

[0037] In Release 16 (Rel-16), a duplication bearer can be configured with up to 4 RLC entities. Rel-15 supports split (spit) transmission. In Rel-15, when two RLC entities are configured, if duplication is deactivated, the PDCP entity uses both the primary leg and the secondary leg to transmit the PDCP PDU when the split transmission conditions are met; otherwise, the primary leg is used to transmit the PDCP PDU. The conditions for split transmission are determined based on the relationship between the size of the PDCP / RLC entity data waiting to be transmitted and the threshold of the two configured RLC entities.

[0038] In Rel-16, RAN2 agrees to configure the secondary leg for split transmission. The current split bearer protocol is described as follows:

[0039] When submitting a PDCP PDU to lower layer, the transmitting PDCPentity shall:

[0040] -if the transmitting PDCP entity is associated with one RLC entity:

[0041] 1)-submit the PDCP PDU to the associated RLC entity;

[0042] -else,if the transmitting PDCP entity is associated with at least twoRLC entities:

[0043] 2)-if the PDCP duplication is activated:

[0044] -if the PDCP PDU is a PDCP Data PDU:

[0045] -duplicate the PDCP Data PDU and submit the PDCP Data PDU to theassociated RLC entities activated for PDCP duplication;-else:

[0046] -submit the PDCP Control PDU to the primary RLC entity;

[0047] 3)-else:

[0048] -if the split secondary RLC entity is configured;and

[0049] -if the total amount of PDCP data volume and RLC data volume pendingfor initial transmission(as specified in TS 38.322[5])in the primary RLCentity and the split secondary RLC entity is equal to or larger than ul-DataSplitThreshold:

[0050] -submit the PDCP PDU to either the primary RLC entity or the splitsecondary RLC entity;

[0051] -else:

[0052] -submit the PDCP PDU to the primary RLC entity.

[0053] The description of the Split secondary RLC entity is as follows:

[0054] Split secondary RLC entity: in dual connectivity, the RLC entity otherthan the primary RLC entity which is responsible for split bearer operation.

[0055] For PDCP configuration, the information element (IE) PDCP-Config is used to set configurable PDCP parameters for SRB and DRB.

[0056]

[0057]

[0058]

[0059] In Rel-16, a duplication radio bearer can be configured with up to 4 RLC entities. However, when the duplication transmission state is deactivated, it is not clear how the sending device performs data transmission and how to determine the separation auxiliary path. When the duplication transmission state is not configured, it is not clear how to determine the current duplication transmission state. It is also not clear how to configure the uplink data separation threshold (ul-Data Split Threshold).

[0060] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, advanced long term evolution (LTE-A) system, new radio (NR) system, NR system evolution system, LTE on unlicensed band (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed band (NR-based access to unlicensed spectrum, NR-U) system, universal mobile telecommunication system (UMTS), global interoperability for microwave access (worldwide interoperability for microwave access, WiMAX) communication system, wireless local area networks (WLAN), wireless fidelity (WiFi), next generation communication system or other communication systems, etc.

[0061] The system architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0062] The network equipment involved in the embodiments of the present application may be an ordinary base station (such as NodeB or eNB or gNB), a new radio controller (new radio controller, NR controller), a centralized unit, a new wireless base station, a radio frequency remote module, a micro base station, a relay, a distributed unit, a transmission reception point (TRP), a transmission point (TP) or any other device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment. For the convenience of description, in all embodiments of the present application, the above-mentioned devices that provide wireless communication functions for terminal devices are collectively referred to as network devices.

[0063] In the embodiment of the present application, the terminal device may be any terminal, for example, the terminal device may be a user device for machine type communication. That is to say, the terminal device may also be referred to as a user equipment UE, a mobile station (MS), a mobile terminal, a terminal, etc. The terminal device may communicate with one or more core networks via a radio access network (RAN). For example, the terminal device may be a mobile phone (or a "cellular" phone), a computer with a mobile terminal, etc. For example, the terminal device may also be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device, which exchanges language and / or data with a radio access network. This is not specifically limited in the embodiment of the present application.

[0064] Optionally, the network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; can also be deployed on aircraft, balloons and artificial satellites in the air. The embodiments of the present application do not limit the application scenarios of the network device and the terminal device.

[0065] Optionally, the network device and the terminal device, and the terminal device and the terminal device may communicate through a licensed spectrum, or may communicate through an unlicensed spectrum, or may communicate through both a licensed spectrum and an unlicensed spectrum. The network device and the terminal device, and the terminal device and the terminal device may communicate through a spectrum below 7 gigahertz (GHz), or may communicate through a spectrum above 7 GHz, or may communicate using a spectrum below 7 GHz and a spectrum above 7 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used between the network device and the terminal device.

[0066] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (D2D) communication, machine to machine (M2M) communication, machine type communication (MTC), and vehicle to vehicle (V2V) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0067] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 2 As shown. The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area, and may communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network-side device in a 5G network, or a network device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

[0068] The communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110. As used herein, "terminal device" includes but is not limited to connection via a wired line, such as via a Public Switched Telephone Networks (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or via a wireless interface, such as, for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or a device of another terminal device configured to receive / send communication signals; and / or an Internet of Things (IoT) device. A terminal device configured to communicate via a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; Personal Communications System (PCS) terminals that may combine cellular radiotelephones with data processing, fax, and data communications capabilities; PDAs that may include radiotelephones, pagers, Internet / Intranet access, Web browsers, notepads, calendars, and / or Global Positioning System (GPS) receivers; and conventional laptop and / or palmtop receivers or other electronic devices that include radiotelephone transceivers. A terminal device may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device. The access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

[0069] Optionally, terminal devices 120 may perform device-to-device (D2D) communication with each other.

[0070] Optionally, the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.

[0071] Figure 2 One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0072] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.

[0073] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 2 Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.

[0074] An optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 3 As shown, the following steps are included:

[0075] Step S201: When the copy transmission state is deactivated, if a first condition is met, the sending device transmits data based on the separate transmission mode, or the sending device delivers the data to the primary path or the separate auxiliary path.

[0076] In some embodiments, the path may also be replaced by a term such as RLC entity.

[0077] In some embodiments, the data may be a PDCP PDU.

[0078] In some embodiments, the sending device transmits data based on the separate transmission mode, and the sending device may fall back from the copy transmission mode to the separate transmission mode.

[0079] In some embodiments, delivering the data to the primary path or the separated secondary path may be delivering the data to an RLC entity corresponding to the primary path or an RLC entity corresponding to the separated secondary path.

[0080] In some embodiments, the first condition may include at least one of the following: the sum of the amount of PDCP data on the main path and the separated auxiliary path, and the amount of RLC data waiting for initial transmission is greater than or equal to a first threshold; a separated auxiliary path is configured; the PDCP entity is associated with two RLC entities, and the two RLC entities correspond to different cell groups; the separated auxiliary path is not configured, the PDCP entity is associated with two PLC entities, and the two RLC entities correspond to different cell groups; the separated auxiliary path is configured, and duplicate transmission of more than two RLC entities is configured; the separated auxiliary path is configured, and IE configuration or appearance of more than two RLC entities; more than two RLC entities are not configured; IE configuration or appearance of more than two RLC entities is not configured; less than or equal to two RLC entities are configured; the separated auxiliary path is not configured, but IE configuration or appearance of more than one RLC entity is configured; the first threshold is configured; the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups.

[0081] Through the embodiments of the present application, it is clarified that when the copy transmission state is deactivated, the transmission behavior of the sending device can be: falling back from the copy transmission mode to the separation transmission mode; or delivering data to the main path or the separation auxiliary path.

[0082] With respect to the transmission behavior of the sending device when the copy transmission state is deactivated, the corresponding protocol can be modified as follows:

[0083] When submitting a PDCP PDU to lower layer, the transmitting PDCPentity shall:

[0084] -if the transmitting PDCP entity is associated with one RLC entity:

[0085] 1)-submit the PDCP PDU to the associated RLC entity;

[0086] -else,if the transmitting PDCP entity is associated with at least twoRLC entities:

[0087] 2)-if the PDCP duplication is activated:

[0088] -if the PDCP PDU is a PDCP Data PDU:

[0089] -duplicate the PDCP Data PDU and submit the PDCP Data PDU to theassociated RLC entities activated for PDCP duplication;

[0090] -else:

[0091] -submit the PDCP Control PDU to the primary RLC entity;

[0092] 3)-else:

[0093] -if the total amount of PDCP data volume and RLC data volume pendingfor initial transmission(as specified in TS 38.322[5])in the primary RLCentity and the split secondary RLC entity is equal to or larger than ul-DataSplitThreshold;and:

[0094] -if the split secondary RLC entity is configured;or

[0095] -if the transmitting PDCP entity is associated with two RLC entitiesand the two associated RLC entities belong to the different Cell Groups:

[0096] -submit the PDCP PDU to either the primary RLC entity or the splitsecondary RLC entity;

[0097] -else:

[0098] -submit the PDCP PDU to the primary RLC entity.

[0099] In some embodiments, the first threshold is configured when the second condition is met. The second condition may include at least one of the following: the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups; the configured bearer is a split bearer; IE configuration or occurrence of more than two RLC entities; duplicate transmission of more than two RLC entities is configured; a split auxiliary path is configured; the configuration condition of the first threshold includes split bearer SplitBearer2; at least two RLC entities of the RLC entities associated with the PDCP entity correspond to different cell groups; the radio bearer is associated with more than two RLC entities, and the RLC entities correspond to different cell groups; the radio bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes split bearer, and the description of the split bearer includes that the radio bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes split bearer, and the description of the split bearer includes that the radio bearer is associated with more than one or two RLC entities, and the RLC entities correspond to different cell groups. Wherein, the radio bearer can be a DRB and / or an SRB.

[0100] In some embodiments, the first threshold may be ul-Data Split Threshold.

[0101] It should be noted that in the embodiment of the present application, the first threshold can be configured when the second condition is met; the data transmission state has no effect on the configuration of the first threshold. It can be understood that whether it is data replication transmission or data separation transmission, as long as the second condition is met, the first threshold is configured.

[0102] In this way, the configuration conditions of ul-Data Split Threshold are clarified through the embodiments of the present application.

[0103] With respect to the configuration conditions of ul-Data Split Threshold in the embodiment of the present application, the existing description of ul-DataSplit Threshold may be modified as follows:

[0104] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting split DRB-with UL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field can be present, if more ThanTwo RLC is configured.

[0105] Alternatively, the description for ul-Data Split Threshold is modified to:

[0106] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting split DRB-with UL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field is optional present, if more ThanTwo RLC is configured.

[0107] Alternatively, the description for ul-Data Split Threshold is modified to:

[0108] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field is optional present, if more than one RLC entities are configured.

[0109] Alternatively, the description for Split Bearer is modified to:

[0110] The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with more than one associated RLC mapped to different cell groups, or in case of radio bearer with more than two associated RLC mapped to different cell groups.

[0111] Alternatively, the description of Split Bearer is modified as follows: The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with at least two associated RLC mapped to different cell groups.

[0112] In some embodiments, the data transmission method may further include:

[0113] Step S202: When the third condition is met, the sending device determines that the path corresponding to the RLC entity of the non-primary path is a separated auxiliary path, or determines that the RLC entity of the non-primary path is a separated auxiliary RLC entity.

[0114] In some embodiments, the third condition includes at least one of the following: more than two RLC entities are not configured; IE for more than two RLC entities is not configured or does not appear; duplicate transmission for more than two RLC entities is not configured; duplicate transmission for two RLC entities is configured; the first threshold is configured; the wireless bearer is a separate bearer; separate bearer IE appears or is configured; DC-based PDCP duplication; separate bearers associating two RLC entities.

[0115] Furthermore, the radio bearer may be a data radio bearer.

[0116] In some embodiments, the two RLC entities correspond to different cell groups; or, at least two RLC entities correspond to different cell groups.

[0117] For the scenario where the duplicate transmission state is deactivated and the sending device determines that the path corresponding to the RLC entity of the non-primary path is a separated auxiliary path, the field configuration of the PrimaryPath IE can be modified as follows:

[0118] primaryPath

[0119] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is not configured, the RLC entity other than primary path is split secondary RLC entity.

[0120] Or,

[0121] primaryPath

[0122] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is absent, the RLC entity other than primary path is split secondary RLC entity.

[0123] Or,

[0124] primaryPath

[0125] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323[5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is not configured, the RLC entity other than primary path is split secondary RLC entity for split bearers.

[0126] Or,

[0127] primaryPath

[0128] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323[5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is absent, the RLC entity other than primary path is split secondary RLC entity for split bearers.

[0129] Alternatively, modify the definition of the split secondary RLC entity in 38.323 protocol as follows:

[0130] Split secondary RLC entity: in dual connectivity, the RLC entity other than the primary RLC entity which is responsible for split bearer operation. The RLC entity other than primary path is split secondary RLC entity for split bearers associated with two RLC entities.

[0131] In some embodiments, the data transmission method may further include:

[0132] When the fourth condition is met, the copy transmission state is configured or the copy transmission state occurs.

[0133] In some embodiments, the fourth condition includes at least one of the following: IE configuration or occurrence of more than two RLC entities; configuration of duplicate transmission of more than two RLCs; configured wireless bearers associated with at least two RLC entities; configured wireless bearers associated with at least one RLC entity.

[0134] The aforementioned embodiments are described for data replication transmission being in a deactivated state. In a specific implementation, when the replication transmission state does not appear or is not configured, the replication transmission state being deactivated may occur in at least one of the following scenarios: the initial PDCP replication transmission state of the RLC entity associated with the data radio bearer is deactivated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the RLC entity associated with the data radio bearer is deactivated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the associated RLC entity is deactivated; when the replication transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or When the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated.

[0135] or,

[0136] The aforementioned embodiments are described for data replication transmission being in a deactivated state. In a specific implementation, when the replication transmission state does not appear or is not configured, the replication transmission state being activated may occur in at least one of the following scenarios: the initial PDCP replication transmission state of the RLC entity associated with the signaling radio bearer is activated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the RLC entity associated with the signaling radio bearer is activated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the associated RLC entity is activated; when the replication transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or When the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the RLC entity associated with the signaling radio bearer is activated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is activated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the signaling radio bearer is activated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is activated.

[0137] For the scenario where the replication transport state is deactivated, the domain configuration of the duplicationState IE can be modified as follows:

[0138] duplicationState

[0139] 该字段指示相关RLC实体的初始上行链路PDCP重复状态。如果设置为真,则为相关RLC实体激活初始PDCP重复状态。该指示的索引由除主路径在MCG和SCG顺序中指示的主RLC实体之外的所有RLC实体的逻辑信道ID按升序确定,如TS38.321[3]的6.1.3.Y节所述。如果除主RLC实体之外的相关RLC实体数量为两个,则UE忽略该字段中最大索引处的值。如果该字段不存在,则相关RLC实体的初始PDCP重复状态对于DRB被停用。相关RLC实体的初始PDCP重复状态对于SRB始终被激活。

[0140] Alternatively, further,

[0141] duplicationState

[0142] 该字段指示相关RLC实体的初始上行链路PDCP复制状态。如果设置为真,则为相关RLC实体激活初始PDCP复制状态。该指示的索引由除主路径指示的主RLC实体之外的所有RLC实体的逻辑信道ID按MCG和SCG的顺序升序确定,如TS38.321[3]的6.1.3.Y节所述。如果除主RLC实体之外的相关RLC实体数量为两个,则UE忽略该字段最大索引中的值。如果该字段不存在,则对于DRB,相关RLC实体的初始PDCP复制状态被停用。如果该字段不存在,则对于SRB,相关RLC实体的初始PDCP复制状态被激活。对于SRB,相关RLC实体的初始PDCP复制状态始终被激活。

[0143] Another optional processing flow of the data transmission method provided by the embodiments of this application is as follows Figure 4 shown, and includes the following steps:

[0144] Step S301, when the third condition is met, the sending device determines that the path corresponding to the RLC entity of the non-primary path is a separated auxiliary path, or determines that the RLC entity of the non-primary path is a separated auxiliary RLC entity; the separated auxiliary path is used for separated transmission.

[0145] In some embodiments, the third condition includes at least one of the following: more than two RLC entities are not configured; IE for more than two RLC entities is not configured or does not appear; duplicate transmission for more than two RLC entities is not configured; duplicate transmission for two RLC entities is configured; the first threshold is configured; the wireless bearer is a separate bearer; separate bearer IE appears or is configured; DC-based PDCP duplication; separate bearers associating two RLC entities.

[0146] Furthermore, the radio bearer may be a data radio bearer.

[0147] In some embodiments, the two RLC entities correspond to different cell groups; or, at least two RLC entities correspond to different cell groups.

[0148] For the scenario where the duplicate transmission state is deactivated and the sending device determines that the path corresponding to the RLC entity of the non-primary path is a separated auxiliary path, the field configuration of the PrimaryPath IE can be modified as follows:

[0149] primaryPath

[0150] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is not configured, the RLC entity other than primary path is split secondary RLC entity.

[0151] Or,

[0152] primaryPath

[0153] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323[5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is absent, the RLC entity other than primary path is split secondary RLC entity.

[0154] Or

[0155] primaryPath

[0156] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is not configured, the RLC entity other than primary path is split secondary RLC entity for split bearers.

[0157] Or

[0158] primaryPath

[0159] Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323[5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW indicates logicalChannel for CA based PDCP duplication, i.e., if both logical channels terminate in the same cell group. If moreThanTwoRLC is absent, the RLC entity other than primary path is split secondary RLC entity for split bearers.

[0160] Alternatively, modify the definition of the split secondary RLC entity in TS 38.323 as follows:

[0161] Split secondary RLC entity: in dual connectivity, the RLC entity other than the primary RLC entity which is responsible for split bearer operation. The RLC entity other than primary path is split secondary RLC entity for split bearers associated with two RLC entities.

[0162] Another optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 5 As shown, the following steps are included:

[0163] Step S401: When the fourth condition is met, the sending device configures the replication transmission status.

[0164] In some embodiments, the fourth condition includes at least one of the following: IE configuration or occurrence of more than two RLC entities; configuration of duplicate transmission of more than two RLCs; configured wireless bearers associated with at least two RLC entities; configured wireless bearers associated with at least one RLC entity.

[0165] The aforementioned embodiments are described for data replication transmission being in a deactivated state. In a specific implementation, when the replication transmission state does not appear or is not configured, the replication transmission state being deactivated may occur in at least one of the following scenarios: the initial PDCP replication transmission state of the RLC entity associated with the data radio bearer is deactivated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the RLC entity associated with the data radio bearer is deactivated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the associated RLC entity is deactivated; when the replication transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or When the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated.

[0166] or,

[0167] The aforementioned embodiments are described for data replication transmission being in a deactivated state. In a specific implementation, when the replication transmission state does not appear or is not configured, the replication transmission state being activated may occur in at least one of the following scenarios: the initial PDCP replication transmission state of the RLC entity associated with the signaling radio bearer is activated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the RLC entity associated with the signaling radio bearer is activated; when the replication transmission state does not appear or is not configured, the initial PDCP replication transmission state of the associated RLC entity is activated; when the replication transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or When the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the RLC entity associated with the signaling radio bearer is activated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is activated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the signaling radio bearer is activated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is activated.

[0168] For the scenario where the replication transport state is deactivated, the domain configuration of the duplicationState IE can be modified as follows:

[0169] duplicationState

[0170] 该字段指示相关RLC实体的初始上行链路PDCP重复状态。如果设置为真,则为相关RLC实体激活初始PDCP重复状态。该指示的索引按照除主路径(primaryPath)指示的主RLC实体之外的所有RLC实体的逻辑信道ID的升序确定,顺序为MCG和SCG,如TS38.321[3]的6.1.3.Y节所述。如果除主RLC实体之外的相关RLC实体数量为两个,则UE忽略该字段中最大索引处的值。如果该字段不存在,则对于DRB,相关RLC实体的初始PDCP重复状态被停用。对于SRB,相关RLC实体的初始PDCP重复状态始终被激活。

[0171] Alternatively, further,

[0172] duplicationState

[0173] 该字段指示相关RLC实体的初始上行链路PDCP复制状态。如果设置为真,则为相关RLC实体激活初始PDCP复制状态。该指示的索引由除主路径在TS38.321[3]的6.1.3.Y条款中指示的主RLC实体之外的所有RLC实体的逻辑信道ID按MCG和SCG的顺序升序确定。如果除主RLC实体之外的相关RLC实体数量为两个,则UE忽略该字段最大索引中的值。如果该字段不存在,则相关RLC实体的初始PDCP复制状态对于DRB被停用。如果该字段不存在,则相关RLC实体的初始PDCP复制状态对于SRB被激活。相关RLC实体的初始PDCP复制状态对于SRB始终被激活。

[0174] Another optional processing flow of the data transmission method provided by the embodiments of this application is as follows Figure 6 shown, and includes the following steps:

[0175] Step S501: When the second condition is met, the sending device configures a first threshold value, where the first threshold value is used to determine a data transmission mode of the sending device.

[0176] In some embodiments, the second condition may include at least one of the following: the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups; the configured bearer is a split bearer; IE configuration or occurrence of more than two RLC entities; duplicate transmission of more than two RLC entities is configured; a split auxiliary path is configured; the configuration condition of the first threshold includes split bearer SplitBearer2; at least two RLC entities among the RLC entities associated with the PDCP entity correspond to different cell groups; the radio bearer is associated with more than two RLC entities, and the RLC entities correspond to different cell groups; the radio bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes split bearer, and the description of the split bearer includes that the radio bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes split bearer, and the description of the split bearer includes that the radio bearer is associated with more than one or two RLC entities, and the RLC entities correspond to different cell groups. Wherein, the radio bearer can be a DRB and / or an SRB.

[0177] In some embodiments, the data transmission mode includes: a copy transmission mode and / or a separate transmission mode.

[0178] In some embodiments, the first threshold may be ul-Data Split Threshold.

[0179] It should be noted that in the embodiment of the present application, the first threshold can be configured when the second condition is met; the data transmission state has no effect on the configuration of the first threshold. It can be understood that whether it is data replication transmission or data separation transmission, as long as the second condition is met, the first threshold is configured.

[0180] In this way, the configuration conditions of ul-Data Split Threshold are clarified through the embodiments of the present application.

[0181] With respect to the configuration conditions of ul-Data Split Threshold in the embodiment of the present application, the existing description of ul-DataSplit Threshold may be modified as follows:

[0182] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting split DRB - with UL - Both - MCG - SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field can be present, if more Than Two RLC is configured.

[0183] Alternatively, the description for ul - Data Split Threshold is modified to:

[0184] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting split DRB - with UL - Both - MCG - SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field is optionally present, if more Than Two RLC is configured.

[0185] Alternatively, the description of ul-Data Split Threshold is modified to:

[0186] Parameter specified in TS 38.323[5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. This field is optional present, if more than one RLC entities are configured.

[0187] Alternatively, the description of Split Bearer is modified to: The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with more than one associated RLC mapped to different cell groups, or in case of radio bearer with more than two associated RLC mapped to different cell groups.

[0188] Alternatively, the description of Split Bearer is modified as follows: The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with at least two associated RLC mapped to different cell groups.

[0189] It should be noted that the main path or the separated auxiliary path described in each embodiment of the present application can be an RLC entity. For example, submitting data to the main path can be understood as submitting data to the RLC entity corresponding to the main path; submitting data to the separated auxiliary path can be understood as submitting data to the RLC entity corresponding to the separated auxiliary path. Alternatively, submitting data to the main path can be understood as submitting data to the main RLC entity; submitting data to the separated auxiliary path can be understood as submitting data to the separated auxiliary RLC entity.

[0190] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0191] To implement the above data transmission method, an embodiment of the present application provides a sending device, an optional structural diagram of the sending device 600 is as follows: Figure 7 As shown, including:

[0192] The sending unit 601 is configured to transmit data based on the separate transmission mode, or deliver the data to the primary path or the separate auxiliary path if the first condition is met when the copy transmission state is deactivated.

[0193] In some embodiments, the first condition includes at least one of the following: the sum of the PDCP data volume on the main path and the separated auxiliary path, and the RLC data volume waiting for initial transmission is greater than or equal to a first threshold; a separated auxiliary path is configured; the PDCP entity is associated with two RLC entities, and the two RLC entities correspond to different cell groups; the separated auxiliary path is not configured, the PDCP entity is associated with two PLC entities, and the two RLC entities correspond to different cell groups; the separated auxiliary path is configured, and duplicate transmission of more than two RLC entities is configured; the separated auxiliary path is configured, and IE configuration or appearance of more than two RLC entities; more than two RLC entities are not configured; IE configuration or appearance of more than two RLC entities is not configured; less than or equal to two RLC entities are configured; the separated auxiliary path is not configured, but IE configuration or appearance of more than one RLC entity is configured; the first threshold is configured; the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups.

[0194] In some embodiments, the first threshold is configured if a second condition is satisfied.

[0195] In some embodiments, the second condition includes at least one of the following: the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups; the configured bearer is a separated bearer; IE configuration or occurrence is greater than two RLC entities; duplicate transmission of greater than two RLC entities is configured; a separated auxiliary path is configured; the configuration condition of the first threshold includes a separated bearer SplitBearer2; at least two of the RLC entities associated with the PDCP entity correspond to different cell groups; the wireless bearer is associated with greater than two RLC entities, and the RLC entities correspond to different cell groups; the wireless bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes a separated bearer, and the description of the separated bearer includes that the wireless bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes a separated bearer, and the description of the separated bearer includes that the wireless bearer is associated with greater than one or two RLC entities, and the RLC entities correspond to different cell groups.

[0196] In some embodiments, the first threshold comprises an uplink data separation threshold.

[0197] In some embodiments, the sending device 600 further includes:

[0198] The first processing unit 602 is configured to determine that a path corresponding to the RLC entity of the non-primary path is a separated auxiliary path when a third condition is met.

[0199] In some embodiments, the third condition includes at least one of the following: no more than two RLC entities are configured; IEs of more than two RLC entities are not configured or do not appear; duplicate transmissions of more than two RLC entities are not configured; duplicate transmissions of two RLC entities are configured; the first threshold is configured; the radio bearer is a separate bearer; separate bearer IE appears or is configured; DC-based PDCP duplication; separate bearers of two RLC entities are associated. The radio bearer may be a data radio bearer.

[0200] In some embodiments, the two RLC entities correspond to different cell groups; or, at least two RLC entities correspond to different cell groups.

[0201] In some embodiments, if a fourth condition is met, the copy transport state is configured or the copy transport state occurs.

[0202] In some embodiments, the fourth condition includes at least one of the following: IE configuration or occurrence of more than two RLC entities; configuration of duplicate transmission of more than two RLCs; configured wireless bearers associated with at least two RLC entities; configured wireless bearers associated with at least one RLC entity.

[0203] In some embodiments, when the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated.

[0204] To implement the above data transmission method, an embodiment of the present application provides a sending device, and another optional structural diagram of the sending device 800 is as follows: Figure 8 As shown, including:

[0205] The second processing unit 801 is configured to, when a third condition is met, determine, by the sending device, that a path corresponding to an RLC entity of a non-primary path is a separated auxiliary path, where the separated auxiliary path is used for separated transmission.

[0206] In some embodiments, the third condition includes at least one of the following: no more than two RLC entities are configured; information unit IE of more than two RLC entities is not configured or does not appear; duplicate transmission of more than two RLC entities is not configured; duplicate transmission of two RLC entities is configured; the first threshold is configured; the radio bearer is a separate bearer; separate bearer IE appears or is configured; DC-based PDCP duplication; separate bearers of two RLC entities are associated. The radio bearer may be a data radio bearer.

[0207] In some embodiments, the two RLC entities correspond to different cell groups; or, at least two of the RLC entities correspond to different cell groups.

[0208] To implement the above data transmission method, the present application embodiment provides a sending device, and another optional structural diagram of the sending device 900 is as follows: Fig. 9 As shown, including:

[0209] The third processing unit 901 is configured to configure the copy transmission state when the fourth condition is met.

[0210] In some embodiments, the fourth condition includes at least one of the following: IE configuration or occurrence of more than two RLC entities; configuration of duplicate transmission of more than two RLCs; configured wireless bearers associated with at least two RLC entities; configured wireless bearers associated with at least one RLC entity.

[0211] In some embodiments, when the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the IE of more than two RLC entities appears or is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when the duplicate transmission state does not appear or is not configured, and the duplicate transmission of more than two RLC entities is configured, the initial PDCP duplicate transmission state of the associated RLC entity is deactivated.

[0212] To implement the above data transmission method, an embodiment of the present application provides a sending device, and another optional structural diagram of the sending device 1000 is as follows: Fig.10 As shown, including:

[0213] The fourth processing unit 1001 is configured to configure a first threshold when the second condition is met, where the first threshold is used to determine the data transmission mode of the sending device.

[0214] In some embodiments, the second condition includes at least one of the following: the PDCP entity is associated with at least two RLC entities, and the at least two RLC entities correspond to different cell groups; the configured bearer is a separate bearer; information units greater than two RLC entities are configured or appear; duplicate transmissions greater than two RLC entities are configured; a separate auxiliary path is configured; the configuration condition of the first threshold includes SplitBearer2; at least two of the RLC entities associated with the PDCP entity correspond to different cell groups; the wireless bearer is associated with greater than two RLC entities, and the RLC entities correspond to different cell groups; the wireless bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes a separate bearer, and the description of the separate bearer includes that the wireless bearer is associated with at least two RLC entities, and the RLC entities correspond to different cell groups; the configuration condition of the first threshold includes a separate bearer, and the description of the separate bearer includes that the wireless bearer is associated with greater than one or two RLC entities, and the RLC entities correspond to different cell groups.

[0215] In some embodiments, the first threshold comprises an uplink data separation threshold.

[0216] In some embodiments, the data transmission mode includes: a copy transmission mode and / or a separate transmission mode.

[0217] An embodiment of the present application also provides a sending device, including a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is used to execute the steps of the data transmission method executed by the above-mentioned sending device when running the computer program.

[0218] An embodiment of the present application also provides a chip, including: a processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned sending device.

[0219] An embodiment of the present application further provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned sending device.

[0220] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned sending device.

[0221] An embodiment of the present application also provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned sending device.

[0222] It should be noted that the sending device described in each embodiment of the present application can be a terminal device in a communication system or a base station in a communication system.

[0223] Fig.11 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The various components in the sending device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 8 Various buses are labeled as bus system 705 .

[0224] It can be understood that the memory 702 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), ferromagnetic random access memory, flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory 702 described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.

[0225] The memory 702 in the embodiment of the present application is used to store various types of data to support the operation of the sending device 700. Examples of such data include: any computer program for operating on the sending device 700, such as the application 7022. The program for implementing the method of the embodiment of the present application may be included in the application 7022.

[0226] The method disclosed in the above embodiment of the present application can be applied to the processor 701, or implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 701 or the instruction in the form of software. The above processor 701 may be a general processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 701 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

[0227] In an exemplary embodiment, the sending device 700 can be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), FPGA, general processor, controller, MCU, MPU, or other electronic components to execute the aforementioned method.

[0228] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0229] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0230] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0231] It should be understood that the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0232] The above is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A data transmission method, the method comprising: In the case where the copy transmission state is deactivated, if the first condition is met, the sending device transmits data based on the separate transmission mode; The method further comprises: In the absence of a duplicate transmission state, the initial PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; When the fourth condition is met, the duplicate transmission state is configured or the duplicate transmission state occurs; wherein the fourth condition includes: configuring duplicate transmission of more than two RLCs; The first condition includes: A split secondary path is not configured, the PDCP entity is associated with two RLC entities, and the two RLC entities correspond to different cell groups; The separate transmission mode does not distinguish between a main path and a separate auxiliary path.

2. The method according to claim 1, wherein: The first condition also includes: A sum of a Packet Data Convergence Protocol (PDCP) data volume on the primary path and the separate secondary path, and a Radio Link Control (RLC) data volume waiting for initial transmission is greater than or equal to a first threshold.

3. The method according to claim 2, wherein: The first threshold is configured when a second condition is satisfied.

4. The method according to claim 3, wherein: The second condition includes: At least two RLC entities among the RLC entities associated with the PDCP entity correspond to different cell groups.

5. The method according to any one of claims 2 to 4, wherein: The first threshold includes an uplink data separation threshold.

6. A sending device, comprising: A sending unit is configured to transmit data based on a separate transmission mode if a first condition is met when the duplicate transmission state is deactivated; wherein, when the duplicate transmission state does not appear, the initial packet data convergence protocol PDCP duplicate transmission state of the RLC entity associated with the data radio bearer is deactivated; when a fourth condition is met, the duplicate transmission state is configured or the duplicate transmission state appears; wherein, the fourth condition includes: configuring duplicate transmissions greater than two RLCs; the first condition includes: no separate auxiliary path is configured, the PDCP entity is associated with two RLC entities, and the two RLC entities correspond to different cell groups; and the separate transmission mode does not distinguish between a main path and a separate auxiliary path.

7. The transmitting device according to claim 6, wherein: The first condition includes at least one of the following: A sum of a Packet Data Convergence Protocol (PDCP) data volume on the primary path and the separate secondary path, and a Radio Link Control (RLC) data volume waiting for initial transmission is greater than or equal to a first threshold.

8. The transmitting device according to claim 7, wherein: The first threshold is configured when a second condition is satisfied.

9. The transmitting device according to claim 8, wherein: The second condition includes: At least two RLC entities among the RLC entities associated with the PDCP entity correspond to different cell groups.

10. The transmitting device according to any one of claims 7 to 9, wherein: The first threshold includes an uplink data separation threshold.

11. A transmitting device comprising a processor and a memory for storing a computer program that can be run on the processor, wherein: When the processor is used to run the computer program, the processor executes the steps of the data transmission method according to any one of claims 1 to 5.

12. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the data transmission method according to any one of claims 1 to 5 is implemented.

13. A chip, comprising: A processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method as described in any one of claims 1 to 5.

Citation Information

Patent Citations

  • Methods and devices for packet data convergence protocol (PDCP) data transmission in wireless communication systems

    US20190215719A1

  • Method and device for indicating radio bearer

    WO2019036861A1