CN112586016B

CN112586016B - Data replication transmission control method, terminal equipment and network equipment

Info

Publication number: CN112586016B
Application number: CN201980054847.9A
Authority: CN
Inventors: 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-01-28
Filing date: 2019-01-28
Publication date: 2023-06-09
Anticipated expiration: 2039-01-28
Also published as: WO2020154867A1; CN112586016A

Abstract

The invention discloses a data replication transmission control method, a terminal device, a network device, a chip, a computer readable storage medium, a computer program product and a computer program, wherein the method comprises the following steps: receiving control information; wherein the control information is used for indicating the terminal equipment to control the control of data copy transmission of the RLC entity for at least one radio link; based on the control information, determining that at least part of the RLC entities in at least one RLC entity indicated by the control information perform data transmission.

Description

Data replication transmission control method, terminal equipment and network equipment

Technical Field

The present invention relates to the field of information processing technologies, and in particular, to a data replication and transmission control method, a terminal device, a network device, a computer storage medium, a chip, a computer readable storage medium, a computer program product, and a computer program.

Background

In 5G, the method is divided into 3 large application scenarios according to service requirements, such as eMBB (enhanced mobile broadband), emtc (mass machine type communication), and ullc (ultra-reliable low-latency communication). In Release15 URLLC, high reliability low latency traffic is considered and handled. In Rel-16, the study object is expanded and the concept of Time Sensitive Networks (TSNs) is introduced. For data replication transmission and multiple connections, it has been described that existing Dual Connectivity (DC) and Carrier Aggregation (CA) replication (multiplexing) can be optimized.

A higher demand is placed on the data copy transmission characteristics than in conventional networks, mainly in the case where the number of RLC entities for the same bearer needs to be supported greater than two. Therefore, how to instruct by which RLC entity to transmit duplicate data is a problem to be solved in the case where more than two RLC entities are configured.

Disclosure of Invention

To solve the above technical problems, embodiments of the present invention provide a data replication transmission control method, a terminal device, a network device, a computer storage medium, a chip, a computer readable storage medium, a computer program product, and a computer program.

In a first aspect, a data replication transmission control method is provided, applied to a terminal device, and the method includes:

receiving control information; wherein the control information is used for indicating the terminal equipment to control the control of data copy transmission of the RLC entity for at least one radio link;

based on the control information, determining that at least part of the RLC entities in at least one RLC entity indicated by the control information perform data transmission.

In a second aspect, a data replication transmission control method is provided, applied to a network device, and the method includes:

Transmitting control information to the terminal equipment; wherein the control information is used to indicate control of data copy transmission for at least one RLC entity.

In a third aspect, there is provided a terminal device comprising:

a first communication unit that receives control information; wherein the control information is used for indicating the terminal equipment to control the control of data copy transmission of the RLC entity for at least one radio link;

and the first processing unit is used for determining that at least part of the RLC entities in the at least one RLC entity indicated by the control information carry out data transmission based on the control information.

In a fourth aspect, there is provided a network device comprising:

a second communication unit which transmits control information to the terminal device; wherein the control information is used to indicate control of data copy transmission for at least one RLC entity.

In a fifth aspect, a terminal device is provided comprising a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory and executing the method in the first aspect or various implementation manners thereof.

In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is for storing a computer program and the processor is for calling and running the computer program stored in the memory for performing the method of the second aspect or implementations thereof described above.

A seventh aspect provides a chip for implementing the method of any one of the first aspect, the second aspect or each implementation thereof.

Specifically, the chip includes: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method as in any one of the above first aspect, second aspect or implementations thereof.

In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, where the computer program causes a computer to perform the method of any one of the first aspect, the second aspect, or implementations thereof.

In a ninth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of any one of the above first aspect, second aspect or implementations thereof.

In a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of any one of the above-described first aspect, second aspect or implementations thereof.

By adopting the scheme, at least partial RLC entities in all RLC entities are determined to carry out data transmission according to the content in the received control information. Therefore, under the condition that a plurality of RLC entities are configured, the terminal equipment can determine that part of the RLC entities carry out data transmission according to the control information of the network in combination with the terminal equipment, coordination among the network RLC entities is reduced, and the terminal equipment is applicable to the condition that the number of the RLC entities for data duplication transmission is smaller than that of the configured RLC entities.

Drawings

Fig. 1-1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application;

FIGS. 1-2 are schematic diagrams of a duplicate transmission;

FIGS. 1-3 are control bit diagrams;

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

FIG. 3 is a schematic diagram of a replication and transmission architecture according to an embodiment of the present application;

fig. 4 is a schematic diagram of a control bit control all RLC duplicate transmission architecture according to an embodiment of the present application;

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

fig. 6 is a flowchart of a control method for data replication and transmission according to an embodiment of the present application;

fig. 7 is a schematic diagram of a composition structure of a terminal device according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a network device composition structure provided in an embodiment of the present application;

fig. 9 is a schematic diagram of a communication device according to an embodiment of the present invention;

FIG. 10 is a schematic block diagram of a chip provided in an embodiment of the present application;

fig. 11 is a schematic diagram of a communication system architecture according to an embodiment of the present application.

Detailed Description

For a more complete understanding of the nature and the technical content of the embodiments of the present invention, reference should be made to the following detailed description of embodiments of the invention, taken in conjunction with the accompanying drawings, which are meant to be illustrative only and not limiting of the embodiments of the invention.

The following description of the technical solutions in the embodiments of the present application will be made with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, or 5G systems, and the like.

By way of example, the communication system 100 to which embodiments of the present application apply may be as shown in fig. 1-1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio 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 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.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (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 means of the other terminal device arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device may refer to an access terminal, user Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved PLMN, etc.

Alternatively, direct terminal (D2D) communication may be performed between the terminal devices 120.

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

Fig. 1-1 exemplarily illustrates one network device and two terminal devices, alternatively, the communication system 100 may include a plurality of network devices and each network device may include other numbers of terminal devices within a coverage area, which is not limited in the embodiments of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1-1 as an example, the communication device may include the network device 110 and the terminal device 120 with communication functions, where the network device 110 and the terminal device 120 may be specific devices described above, which are not described herein again; the communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

The duplication transmission architecture in the embodiment of the present application may be as shown in fig. 1-2, where data duplication is performed in the PDCP layer, and the same PDCP pdu is mapped to different RLC entities respectively. The MAC needs to transmit duplicate data of different RLC entities (RLC entities) to different carriers, where the corresponding RLC entity number is defined as 2 in the current standard of Rel15, IIoT will further study the case of more than 2, i.e. 3 and 4.

Specifically, two copy data transmission modes are supported at NR R15, and one of the two modes is selected for one bearer, and only copy data transmission of at most two copies is supported. The specific two copy transmission modes are as follows:

CA publication: CA-based replication data transmission. The protocol architecture of the CA multiplexing transmission scheme is shown in the following figures DRB ID 1 or DRB ID 3. The protocol architecture of CA (carrier aggregation) adopted by the data transmission scheme is replicated. The PDCP entity is associated with two different RLC entities below, the two associated different RLC entities being associated to the same MAC entity. For uplink and downlink, the PDCP PDU is duplicated into two identical PDCP PDU, the two PDCP PDU passes through different RLC entities and the same MAC entity, then reaches the corresponding MAC entity of the base station (uplink) through an air interface, and finally is converged to the PDCP. The PDCP layer detects that two PDCP layers are identical duplicate versions, e.g., if it is determined that the two PDCP PDUs have identical SNs, then one of them is discarded and the other is delivered to the higher layer (note that duplicate PDCP PDUs do not necessarily arrive at the PDCP layer at the same time).

DC implementation: DC-based replication data transmission. The protocol architecture of the DC implementation transmission scheme is shown in the following figure DRB ID 2. The copy data transmission mode adopts a split bearer protocol architecture. Two different RLC entities are associated below the PDCP entity, the two associated different RLC entities being associated to different MAC entities, one MAC entity corresponding to the MCG and one MAC entity corresponding to the SCG. For uplink and downlink, PDCP copies PDCP PDUs into two identical copies, the two PDCP passes RLC entities and MAC entities of different CG, and reaches the corresponding MAC entity and RLC entity of the base station through an air interface, and finally the PDCP is converged to PDCP, and PDCP layer detects that the two PDCP PDUs are identical copy versions, for example, if the two PDCP PDUs have identical SN, one PDCP layer is discarded, and the other PDCP layer is submitted to a higher layer (note that the copy PDCP PDUs do not necessarily reach the PDCP layer at the same time).

For data duplication transmission, the uplink PDCP data duplication function can be configured based on DRBs, that is, with DRB granularity, to configure duplication data transmission, and control activation or deactivation of duplication data transmission. In the prior art, corresponding information is added in a PDCP-config IE in an RRC reconfiguration message to configure a bearer-based data duplication mode, and only a duplication data transmission mode of at most 2 leg is supported.

The data copy transport function of a certain data radio bearer is dynamically activated (activated) or deactivated (deactivated) by the MAC CE. The MACCE includes an 8-bit Bitmap, the bits in the Bitmap correspond to different DRBs, and the activation or deactivation of the data copy data of the corresponding DRBs is indicated by the difference of the values in the bits, as shown in fig. 1-3.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

Embodiment 1,

The embodiment of the invention provides a data replication transmission control method, which is applied to terminal equipment, as shown in fig. 2, and comprises the following steps:

Step 201: receiving control information; wherein the control information is used to instruct the terminal device to control the data copy transmission for at least one radio link control (RLC, radio Link Control) entity;

step 202: based on the control information, determining that at least part of the RLC entities in at least one RLC entity indicated by the control information perform data transmission.

Here, the terminal device may be a device configured with a plurality of RLC entities for data copy transmission, wherein a plurality may be understood as more than 2. At least a part of the at least one RLC entity may be a target number of RLC entities among all RLC entities configured for data copy transmission by the terminal device, and the target number is less than the number of all RLC entities. For example, the terminal device is configured with 5 RLC entities, where the 5 RLC entities respectively belong to different network devices; based on the control information, it may be determined to employ 2 RLC entities of the 5 RLC entities for data transmission.

The control information may be at least one control information sent by one or more network devices. The control bits in the control information sent by one network device may be specific to the network device, may also be specific to a plurality of network devices, or may also be specific to one bearer or a plurality of bearers, may also be specific to one or more RLC entities under one network device, and may, of course, be specific to a plurality of RLC entities of a plurality of network devices.

The following describes the scheme provided in this embodiment in detail in several scenarios:

scene 1,

In the scene, control bits in the control information only control data copy transmission aiming at the RLC entity of single network equipment; alternatively, the control bits in the control information also control the data copy transmission for RLC entities of more than one network device.

The Control bits may explicitly include an identity of the bearer in a medium access Control (MAC, media Access Control) Control Element (CE) or implicitly indicate the bearer to which the bit is associated by predefining a mapping relationship of the bearer identity to the bit.

The control bits in the control information of the sub-scenario 11 are only for the RLC entity of a single network device to control the data copy transmission, specifically:

the target network device or RLC entity corresponding to the control information may be determined according to the network device sending the control information. Further, according to the identifier of the network device sending the control information, the network device or RLC entity associated with the implicit indication bit can be indicated according to the mapping relationship between the preset network device identifier and the bit. Further, it is determined that only control bits for a single network device or RLC of a single network device are included in the MAC CE, i.e., control information.

Or determining the target network equipment or the RLC entity corresponding to the control information according to the radio resource control (RRC, radio Resource Control) configuration information. The RRC configuration information indicates a mapping relationship between the target network device or RLC entity and the control bits. Namely, acquiring the network equipment or the RLC entity associated with the indication bit implicitly according to the mapping relation between the predefined network equipment identification and the bit according to the RRC configuration information, and further determining at least one network equipment or at least one RLC entity corresponding to the control bit which can be contained in the MAC CE.

Or determining the target network equipment or the RLC entity corresponding to the control information according to the first information contained in the control information. The first information includes an identification of the target network device. The mac ce may explicitly include an identifier of the network device, and determine, based on the identifier of the network device, a target network device or RLC entity corresponding to the control bit in the control information.

When the target network device contains an RLC entity, determining whether to use the RLC entity contained in the target network device for data copy transmission based on a control bit in the control information. That is, when the target network device is configured with only one RLC entity, one bit is used to control whether the terminal device uses the current RLC entity for data transmission.

When the target network equipment comprises at least two RLC entities, determining to adopt the at least two RLC entities contained in the target network equipment to carry out data transmission or determining to adopt the target RLC entities contained in the target network equipment to carry out data copying transmission based on one control bit contained in the control information. That is, when the target network device is configured with at least two RLC entities, one bit controls the plurality of RLC entities to perform duplicate transmission, or one target RLC entity of the at least two RLC entities of the target network device performs data duplicate transmission.

One bit is used to control whether the UE performs data transmission by two RLC entities or only one RLC entity is used for data transmission; the one RLC entity is which one of the two RLC entities can be configured additionally, e.g. by another bit, or by RRC.

When the target network equipment comprises at least two RLC entities, determining that the at least two RLC entities contained in the target network equipment perform data copying transmission based on at least two control bits contained in the control information; wherein different control bits correspond to different RLC entities. Namely, whether the two RLC entities are subjected to data transmission or not is controlled by using two bits respectively, wherein the control bits of different bits can determine the RLC entities corresponding to the control bits through a preset relationship, and the control bits of different control bits are used for controlling different RLC entities.

For example, referring to fig. 3, a primary network device and two

auxiliary contacts

1, 2 are configured, and two bearers are configured at the same time, for the first bearer, there is one RLC entity on the primary network device, there are two RLC entities on the auxiliary network device 1, and the corresponding primary network device issues one control bit for RLC1, and the auxiliary network device issues one control bit for RLC2, 3 (or issues two control bits for two RLC entities respectively);

for the second bearer, there is an RLC entity 4 on the auxiliary network device 1, and there is an RLC entity on the auxiliary network device 2, corresponding to the auxiliary network device 1 issuing a control bit for RLC4, and the auxiliary network device 2 issuing a control bit for RLC5.

In this sub-scenario, the terminal device needs to ensure that the terminal device only performs data transmission in the target number of RLC entities, for example, only performs transmission on one or two RLC entities, and may perform the following processing:

the network devices need to coordinate with each other (including but not limited to signaling interactions of the X2 and Xn interfaces between different network devices), which is not described in this embodiment.

The terminal equipment determines the use of the RLC entity according to the latest received signaling, and coordinates the processing according to the received signaling, and the specific explanation is as follows:

the determining, based on the control information, that at least part of RLC entities perform data copy transmission in at least one RLC entity indicated by the control information, includes:

based on the latest received control information, determining that the RLC entity indicated by the latest received control information performs data copy transmission. For example, control information from network device 1 has been received before, wherein control bits indicate two RLC entities using network device 1, and control information from network device 2 has been received after, wherein control bits indicate two RLC entities using network device 2; and comprehensively considering that the terminal equipment can also configure a preset quantity threshold value, selecting that the target quantity of the RLC entities is smaller than the preset quantity threshold value, namely the target quantity can be two, and the terminal equipment performs data transmission according to the indication of the control bits in the latter control information.

Or, based on the control information, determining a target number of RLC entities to perform data copy transmission; wherein the target number of RLC entities may be from the same network device or from different network devices;

Or based on the control information, determining the RLC entity of the unique network equipment to perform data copying transmission.

For example, the control information from the network device 1 has been received before, where the control bit indicates that two RLC entities of the network device 1 are used, and then the control information from the network device 2 is received, where the control bit indicates that one RLC entity of the network device 2 is used, and the target number is considered comprehensively, and then the terminal device can only perform data transmission on at most two RLC entities, and then the terminal device can: selecting one RLC entity of the network device 1 and one RLC entity of the network device 2 to transmit; or only on the RLC entity of the network device 2.

Alternatively, the terminal device may perform data copy transmission based on the RLC entity configured by the network. I.e. the network may perform data transmission in this case by configuring at least one default RLC entity, e.g. RLC1 for the first bearer and RLC4 for the second bearer.

For example, the control information has been received at a previous time, wherein the control bit indicates that transmission is only performed on one RLC entity of the network device 1, after which the control bit from the network device 1 is received, indicating that either RLC entity of the network device 1 cannot be used, the network may perform data transmission in this case by configuring at least one default RLC entity, e.g. RLC1 for the first bearer, RLC4 for the second bearer.

Or the network may control the bit (bit) of a certain RLC entity, e.g. RLC1 for the first bearer and RLC4 for the second bearer, fixing its value to allow data duplication.

Or the network may not configure the bit of a certain RLC entity, e.g. RLC1 for the first bearer and RLC4 for the second bearer, defaulting to allow data duplication.

Sub-scene 12,

The control information comprises at least one control bit; the at least one control bit is configured to indicate a data copy transmission status of at least two RLC entities; wherein the at least two RLC entities belong to the same or different network devices. That is, unlike the sub-scenario 11, the sub-scenario is determined by comprehensively considering RLC entity configuration on at least one network device, and the control bits in the network device control information are issued.

The manner in which the terminal device determines the data copy transmission state based on the control bits in the control information may include:

and determining the data replication transmission state corresponding to the at least two control bits based on the at least two control bits contained in the control information and the corresponding relation between the preset control bits and the transmission state.

Or alternatively, the process may be performed,

and determining the data replication transmission state corresponding to the at least two control bits based on the at least two control bits contained in the control information and the corresponding relation between the control bits and the transmission state of the network configuration.

That is, the correspondence between the control bits and the transmission state may be preconfigured for the terminal device itself, or may be issued by the network side through signaling, specifically, the issuing may be issued through RRC signaling, or may be issued through MAC CE or Downlink Control Information (DCI), which is not limited herein.

The at least one network device may be network RRC configured or refer to all network devices; for example: for each of the primary and secondary network devices, two RLC entities, i.e. four RLC entities, are configured,

RLC entities

1, 2 are on network device 1, RLC entities 3, 4 are on

network device

2, and 1, 2 or 3 bits can be configured to control the following different state transitions.

Regarding which network device the control information is issued by, the control information of at least one RLC entity managed by itself may be sent for each network device, or the information of RLC entities of all network devices corresponding to the terminal device may be sent for each network device.

Still further, as shown in fig. 4, since

RLC entities

1 and 2 are on the same network device, the effect of transmitting only RLC entity 1 or RLC entity 2 is the same, and both RLC entities can transmit control information equally with the network device; the fourth state is equivalent to being sent only on RLC entity 1 for table 1 below.

Similarly, for the fifth state, it is only sent on RLC entity 3, which is equivalent to RLC entity 4 only.

In addition, if the effect is different only on RLC entity 1 or only on RLC entity 2, more entries need to be added, and more bits can be used for the representation.

For table 1 of the correspondence between control bits and transmission states, two bits may be used to represent the transition between different states, and for table 2 of the correspondence between control bits and transmission states, we may use three bits to represent different states, for example, the diagram may be seen in fig. 5, where it can be seen that the corresponding different states are represented by 3 control bits.

In this example, a case is shown where it is guaranteed that the terminal device transmits only on one or two RLC entities if necessary.

Status of	RLC1	RLC2	RLC3	RLC4
					1	Hair brush	Hair brush
2		Hair brush	Hair brush
					3			Hair brush	Hair brush
4		Hair brush

TABLE 1

Status of	RLC1	RLC2	RLC3	RLC4
						1	Hair brush	Hair brush
2		Hair brush	Hair brush
						3			Hair brush	Hair brush
4		Hair brush
					5				Hair brush

TABLE 2

As shown in fig. 4, a primary network device and a secondary node are configured, and a bearer is configured, there are 2 RLC entities on the primary network device, there are 2 RLC entities on the secondary network device 1, the corresponding primary network device issues 2 control bits for RLC1, 2, 3, 4, and the secondary network device issues 2 control bits for RLC1, 2, 3, 4 (or issues three control bits for all 3 RLC entities).

It should be understood that in this sub-scenario, the terminal device performs processing according to the latest received control information, that is, the control information 1 sent by the network device 1 is received at the previous moment, and at this time, the data transmission of the RLC entity of the terminal device may be determined for RLC1, 2, 3, and 4 according to the control bits in the control information 1; after receiving the control information 2 from the network device 2, the network device updates the data transmission control based on the newly received control information 2.

It should be noted that tables 1, 2, and 5 may be further extended to the case of 3 network devices/6 RLC entities, and will not be described again. The control bits issued by the network device can point to a specific state through RRC configuration, for example, the values of different control bits of the network device are related to or independent of each other for selecting the state, i.e. the states may not overlap with each other; the values of all control bits in the control information of the network device may or may not cover all possible states.

The sub-scene 11 and the sub-scene 12 in the present scene 1 may be combined, and specifically described as follows:

a part of RLC entities may be implemented by means of sub-scenario 11; another part of the RLC entity may be implemented by means of the sub-scenario 12.

For example, two RLC entities, namely four RLC entities in total, are configured on each of the primary and secondary network devices, RLC1, 2 on network device 1, RLC3,4 on network device 2

For RLC1 of network device 1 and RLC3 of network device 2, the manner of sub-scenario 11 is used, i.e. using separate control bits; a control bit 1 of the control information is transmitted by the network device 1 to control whether the RLC entity 1 is used for data transmission; control bit 2 in the control information sent by network equipment 2 controls whether RLC entity 3 is used for data transmission; while the

network devices

1 and 2 transmit control bits 3 (or control bits 3, 4) of the control information, controlling the state of the RLC2, 4.

The terminal equipment in the two combined sub-scenes can be also configured with a preset quantity threshold value, and the target quantity of the selected RLC entities is smaller than the preset quantity threshold value, namely, the target quantity of the RLC entities is adopted for transmission. For example, as shown in Table 1-1, the combination of different control bits indicates different RLC entity usage.

Control bit 1	Control bit 2	Control bit 3	RLC1	RLC2	RLC3	RLC4
								1	0	0	Hair brush	Hair brush
0	0	1		Hair brush		Hair brush
							0	1	0			Hair brush	Hair brush
0	0	0		Hair brush

TABLE 1-1

Similar to sub-scenario 11, in this case, to ensure transmission over a target number of RLC entities, such as one or two RLC entities, mutual coordination between network devices is required and the following criteria need to be defined:

for example, the control bit from the network device 1 has been received before, indicating to use both RLC entities of the network device 1, and the control bit from the network device 2 has been received after, indicating to use both RLC entities of the network device 2, working according to the latter indication, considering that the UE can only transmit data at maximum on both RLC entities.

For example, control bits from network device 1 have been received before, indicating to use two RLC entities of network device 1, and control bits from network device 2 have been received after, indicating to use one RLC entity of network device 2, one RLC entity of network device 1 and one RLC entity of network device 2 are selected to transmit, considering that the UE can transmit data only on at most two RLC entities, or transmit only on an RLC entity of network device 2.

For example, the control bit has been received before indicating that transmission is only performed on one RLC entity of the network device 1, and the control bit from the network device 1 is received after indicating that any RLC entity of the network device 1 cannot be used, then:

The network may perform data transmission in this case by configuring at least one default RLC entity, e.g. RLC1 for the first bearer, RLC4 for the second bearer;

or the network can control the bit of a certain RLC entity, for example, for RLC1 of the first bearer and for RLC4 of the second bearer, fix the value as allowing for data duplication;

or the network may not configure the bit of a certain RLC entity, for example, RLC1 for the first bearer and RLC4 for the second bearer, defaulting to allow data duplication.

Scenario 2, data replication is controlled by network signaling and terminal device autonomous selection.

The present scene is similar to scene 1 and is also divided into the following cases, for example

The network device only controls the data copying aiming at the RLC entity of the single network device;

the network device also controls the copying of data for RLC entities of more than one network device.

Similarly, the control bits in the control information sent by the network device may be determined as in scenario 1 for which bearer and which RLC entity, which is not described in detail herein.

The difference between the present scenario and scenario 1 is that no coordination process of the network device is required in the present scenario, and the terminal device is required to perform subsequent processes based on the control bits after receiving the control information, where the selection of the control information in scenario 1 may be determined according to the time sequence relationship of receiving the control information, and the present scenario focuses on selecting RLC entities according to the channel condition.

That is, the terminal device selects RLC entities under the network device, and finally determines through which RLC entity data transmission should be performed. The selection here needs to take into account the following two factors:

channel conditions: such as RSRP, RSRQ, SINR, RSSI;

absolute threshold: for example, the channel condition value associated with the network device 1 or the RLC entity is greater than or equal to a certain threshold a, and/or the channel condition value associated with the network device 1 or the RLC entity is less than or equal to a certain threshold B;

relative threshold: for example, the channel condition value of the network device 1 or the RLC entity one is greater than or equal to the channel condition value of the network device 2 or the RLC entity two by a certain threshold a, and/or the channel condition value of the network device 1 or the RLC entity one is less than or equal to the channel condition value of the network device 2 or the RLC entity two by a certain threshold B;

here, the channel conditions related to the network device or the RLC entity may be comprehensively considered in combination with the channel conditions related to the frequency point/cell related to the network device or the RLC entity.

The process of scenario 2 will be described with reference to fig. 5, in which the terminal device receives control information sent by network signaling, such as MAC CE, and then the terminal device autonomously selects RLC entity for transmission according to control bits in the control information. The network equipment can configure the network equipment and the RLC entity which can be selected by the terminal equipment for the terminal equipment through RRC; alternatively, the criteria for the network device and RLC entity set that the terminal device can autonomously select are predefined by the protocol.

Sub-scene 21,

when at least two pieces of control information are RLC entities aiming at different network equipment, the terminal equipment selects a target number of RLC entities from the RLC entities indicated by the at least two pieces of control information according to a first criterion to carry out data copying and transmission; wherein the target number of RLC entities belong to the same or different network devices.

The first criterion is that a target number of RLC entities are selected based on channel quality information; at least one of the following:

channel quality information of different cells, channel quality information of different RLC entities, channel quality information of different bandwidth parts BWP. In addition, the first criterion may further include an absolute threshold and a relative threshold.

The control bits of the control information issued by the network are similar to those of sub-scenario 11, except that in this sub-scenario, further, if it is required to ensure that the terminal device can also transmit at a target number of RLC entities, for example, the target number is two, the terminal device determines to transmit at one or two RLC entity RLC entities.

No coordination between the network devices is required. The terminal equipment autonomously determines the use of the RLC entity according to the received signaling.

For example, receiving control information from the network device 1, wherein the control bits indicate two RLC entities using the network device 1, and receiving control bits from the network device 2, indicating two RLC entities using the network device 2, the selection may be made according to the first criterion described above, considering that the target number is two, i.e. that data transmission can only be performed on at most two RLC entities.

May be transmitted on one RLC entity of the network device 1 and/or the network device 2;

it is also possible to transmit on both RLC entities of the network device 1 or the network device 2, respectively.

For another example, receiving control information from the network device 1, wherein a control bit indicates one RLC entity using the network device 1, and receiving control information from the network device 2, wherein a control bit indicates two RLC entities using the network device 2, the terminal device can only perform data transmission on at most two RLC entities considering that the target number is two, and the terminal device can perform processing according to the first criterion.

it may also be transmitted on two RLC entities of the network device 2.

When the terminal device receives the network indication that the data copy transmission is not performed, one of the following steps is executed:

performing data transmission based on a preset target number of default RLC entities;

based on a preconfigured target RLC entity, carrying out data transmission;

the terminal equipment selects a target number of RLC entities to transmit data.

For example, if an indication of the network is received and transmission cannot be made on any network device, then

The network may perform data transmission in this case by configuring a target number of default RLC entities.

Or the UE autonomously selects to transmit on one RLC entity of the network device 1 and/or the network device 2; the transmission is performed on two RLC entities of the network device 1 or the network device 2.

Sub-scene 22,

The control bits issued by the network are similar to those of sub-scenario 12, except that in this example, the control information contains at least one control bit; the at least one control bit is used to indicate a set of states. I.e. the control bits issued by the network are no longer directed to a specific state but to a set of states comprising at least one state, the terminal device further selecting the specific state among the set of states by autonomous selection.

Furthermore, the terminal device may further configure a preset number threshold, and select that the target number of RLC entities is smaller than the preset number threshold, that is, the target number of RLC entities, for example, one or two RLC entities transmit.

For example: for two RLC entities on the primary network device and the secondary network device respectively, namely four RLC entities in total, RLC1, 2 is on network device 1, RLC3,4 is on

network device

2, and 1, 2 or 3 bits can be configured to control the following different state transitions: since the first and second RLC entities are on the same network device, transmitting only on the first RLC entity or transmitting only on the second RLC entity has the same effect, the fourth state is equivalent to transmitting only on the first RLC entity. Similarly, for the fifth state, it is only sent on the third RLC entity, which is equivalent to the fourth RLC entity.

Status of	RLC1	RLC2	RLC3	RLC4
					A1	Hair brush	Hair brush
A2		Hair brush	Hair brush
					A3			Hair brush	Hair brush
B4		Hair brush
					B5				Hair brush

TABLE 3 Table 3

In table 3 above, the network may issue a control bit, marking state set a and state set B, respectively, identifying activation and deactivation of replication, respectively; in the state set A, the terminal equipment further selects A1/2/3; in state set B, the UE further selects state B4/5.

Status of	RLC1	RLC2	RLC3	RLC4
					A1	Hair brush	Hair brush
B1		Hair brush	Hair brush
					C1			Hair brush	Hair brush
D1		Hair brush
					D2				Hair brush

TABLE 4 Table 4

In Table 4 above, the network may issue 2 control bits, respectively marking state sets A, B, C, D, among which state set A, further selection is made for D1/2. The method specifically comprises the following steps: determining a corresponding state set based on at least two control bits contained in the control information; and selecting a data copying transmission state based on the state set. And the terminal equipment selects the data copying transmission state from the state set according to a second criterion. The second criterion is selecting a data copy transmission state from a set of states based on channel quality information.

The channel quality information includes at least one of:

channel quality information of different cells, channel quality information of different RLC entities, channel quality information of different bandwidth parts BWP.

That is, based on the channel quality conditions corresponding to the respective RLC entities included in the state set, it is determined in which data copy transmission state the quality of the target number of RLC entities satisfies the requirement, and the data copy transmission state may be selected.

The selection of the values of different control bits of the network to the states is related or independent, namely, the states can be overlapped or not overlapped, namely, the state sets corresponding to the values of the different control bits can be overlapped, partially overlapped or not overlapped; the values of all control bits of the network may or may not cover all possible state sets; the control bit values of the network may all comprise more than one state set, or only partially comprise more than one state set, or all comprise only one state set.

It should also be noted that sub-scene 21 and sub-scene 22 in scene 2 may also be processed in combination, such as

A part of RLC entities may be implemented by means of sub-scenario 21; another part of the RLC entity may be implemented by means of the sub-scenario 22.

For example, two RLC entities, namely four RLC entities in total, are configured on each of the primary network device 1 and the secondary network device 2, with the RLC1, 2 on the network device 1 and the RLC3,4 on the network device 2;

for RLC1 of network device 1 and RLC3 of network device 2, a separate control bit is used in a manner that uses scenario 21;

the network device 1 transmits a control bit 1 to control whether the RLC1 is used for data transmission;

the network device 2 transmits a control bit 2 to control whether the RLC3 is used for data transmission;

while

network devices

1 and 2 transmit control bits 3 (or control bits 3, 4) controlling the state of RLC2, 4.

For example, as shown in tables 5 and 6 below, combinations of different control bits represent different RLC entity usage scenarios.

In this example, it is further necessary to ensure that the terminal device transmits in a target number of RLC entities, such as in the case of transmitting on only one or two RLC entities.

TABLE 5

TABLE 6

Similar to sub-scenario 21, in this case, in order to ensure that the terminal device transmits in the target number of RLC entities, no mutual coordination between the network devices is required, and the terminal device autonomously determines the use of the RLC entities from the received signaling.

For example, receiving control information from the network device 1, indicating two RLC entities using the network device 1 according to control bits in the control information, and receiving control information from the network device 2, indicating two RLC entities using the network device 2 according to control bits in the control information, the UE selecting according to the above factors, considering that the UE can transmit data only at the two RLC entities at most:

transmitting on one RLC entity of the network device 1 and/or the network device 2;

alternatively, the transmission is performed on two RLC entities of the network device 1 or the network device 2.

For example, receiving a control bit from network device 1 indicating one RLC entity using network device 1 and receiving a control bit from network device 2 indicating two RLC entities using network device 2, the UE selects as possible based on the above factors considering that the UE can only transmit data at most two RLC entities:

The network may perform data transmission in this case by configuring at least one default RLC entity.

Or the network may not configure the bit of a certain RLC entity, for example, for RLC1 of the first bearer, for RLC4 of the second bearer, defaulting to allow for data duplication;

or the UE autonomously selects to transmit on one RLC entity of the network device 1 and/or the network device 2; alternatively, the transmission is performed on two RLC entities of the network device 1 or the network device 2.

By adopting the scheme, at least partial RLC entities in all RLC entities can be determined to transmit data according to the content in the received control information. Therefore, the terminal equipment can determine partial RLC entities to carry out data transmission according to the control information of the network in combination with the terminal equipment under the condition of configuring a plurality of RLC entities, so that coordination among the network RLC entities can be reduced, and the terminal equipment is applicable to the condition that the number of the RLC entities for data duplication transmission is smaller than that of the configured RLC entities.

Embodiment II,

The embodiment of the invention provides a data replication transmission control method, which is applied to network equipment, as shown in fig. 6, and comprises the following steps:

step 601: transmitting control information to the terminal equipment; wherein the control information is used to indicate control of data copy transmission for at least one RLC entity.

scene 1,

and indicating the target network equipment or the RLC entity corresponding to the control information through the control information sent by the network equipment. Further, according to the identifier of the network device sending the control information, the network device or RLC entity associated with the implicit indication bit can be indicated according to the mapping relationship between the preset network device identifier and the bit. Further, it is determined that only control bits for a single network device or RLC of a single network device are included in the MAC CE, i.e., control information.

Or, the target network device or the RLC entity corresponding to the control information is indicated by the RRC configuration information. The RRC configuration information indicates a mapping relationship between the target network device or RLC entity and the control bits. Namely, acquiring the network equipment or the RLC entity associated with the indication bit implicitly according to the mapping relation between the predefined network equipment identification and the bit according to the RRC configuration information, and further determining at least one network equipment or at least one RLC entity corresponding to the control bit which can be contained in the MAC CE.

Or, indicating the target network device or RLC entity corresponding to the control information through the first information included in the control information. The first information includes an identification of the target network device. The mac ce may explicitly include an identifier of the network device, and determine, based on the identifier of the network device, a target network device or RLC entity corresponding to the control bit in the control information.

For example, referring to fig. 3, a primary network device and two

auxiliary contacts

the network devices need to coordinate with each other (including but not limited to signaling interaction of X2 and Xn interfaces between different network devices), for example, the network devices may know in advance the target number of RLC entities to be configured by the terminal device, then perform signaling interaction with at least one other network device through the X2 or Xn interface, finally determine the target number of RLC entities, and send the target number of RLC entities to the terminal device through control bits in the control information.

The terminal device determines the use of the RLC entity according to the latest received signaling, and performs coordination according to the received signaling, which may be referred to in the first embodiment, and will not be described herein.

Sub-scene 12,

The control information comprises at least one control bit; the at least one control bit is configured to indicate a data copy transmission status of at least two RLC entities; wherein the at least two RLC entities are directed to different network devices. That is, unlike the sub-scenario 11, the sub-scenario is determined by comprehensively considering RLC entity configuration on at least one network device, and the control bits in the network device control information are issued.

The manner in which the terminal device determines the data copy transmission status based on the control bits in the control information may be the same as that of the first embodiment, and will not be described again.

The sub-scene 11 and the sub-scene 12 in the present scene 1 may be used in combination, and specifically described as follows:

For example, two RLC entities, namely four RLC entities in total, are configured on each of the primary and secondary network devices, RLC1, 2 on network device 1 and RLC3,4 on network device 2.

network devices

The scene is different from scene 1 in that coordination processing of network equipment is not needed in the scene, and terminal equipment is needed to carry out subsequent processing based on control bits after receiving control information, wherein the control information comprises at least one control bit; the at least one control bit is used to indicate a set of states.

Third embodiment,

An embodiment of the present invention provides a terminal device, as shown in fig. 7, including:

a first communication unit 71 that receives control information; wherein the control information is used to instruct the terminal device to control the data copy transmission for at least one radio link control (RLC, radio Link Control) entity;

the first processing unit 72 determines, based on the control information, that at least part of RLC entities among the at least one RLC entity indicated by the control information perform data transmission.

Here, at least a part of the at least one RLC entity may be a target number of RLC entities among all RLC entities configured for data copy transmission by the first processing unit 72, and the target number is smaller than the number of all RLC entities. For example, the terminal device is configured with 5 RLC entities, where the 5 RLC entities respectively belong to different network devices; based on the control information, it may be determined to employ 2 RLC entities of the 5 RLC entities for data transmission.

scene 1,

The first processing unit 72 may determine, according to the network device that transmits the control information, a target network device or RLC entity corresponding to the control information. Further, according to the identifier of the network device sending the control information, the network device or RLC entity associated with the implicit indication bit can be indicated according to the mapping relationship between the preset network device identifier and the bit. Further, it is determined that only control bits for a single network device or RLC of a single network device are included in the MAC CE, i.e., control information.

Alternatively, the first processing unit 72 determines the target network device or RLC entity corresponding to the control information according to radio resource control (RRC, radio Resource Control) configuration information. The RRC configuration information indicates a mapping relationship between the target network device or RLC entity and the control bits. Namely, acquiring the network equipment or the RLC entity associated with the indication bit implicitly according to the mapping relation between the predefined network equipment identification and the bit according to the RRC configuration information, and further determining at least one network equipment or at least one RLC entity corresponding to the control bit which can be contained in the MAC CE.

Alternatively, the first processing unit 72 determines, according to the first information included in the control information, a target network device or RLC entity corresponding to the control information. The first information includes an identification of the target network device. The control information, that is, the MAC CE, explicitly includes the identifier of the network device, and the target network device or RLC entity corresponding to the control bit in the control information may be determined based on the identifier of the network device.

The first processing unit 72 determines whether to use an RLC entity included in the target network device for data copy transmission based on a single control bit in the control information when the target network device includes an RLC entity. That is, when the target network device is configured with only one RLC entity, one bit is used to control whether the terminal device uses the current RLC entity for data transmission.

The first processing unit 72 determines to perform data transmission using at least two RLC entities included in the target network device or determines to perform data copy transmission using a target RLC entity included in the target network device, based on a one-bit control bit included in the control information when the target network device includes at least two RLC entities. That is, when the target network device is configured with at least two RLC entities, one bit controls the plurality of RLC entities to perform duplicate transmission, or one target RLC entity of the at least two RLC entities of the target network device performs data duplicate transmission.

The first processing unit 72 determines, when the target network device includes at least two RLC entities, that the at least two RLC entities included in the target network device perform data copy transmission based on at least two control bits included in the control information; wherein different control bits correspond to different RLC entities. Namely, whether the two RLC entities are subjected to data transmission or not is controlled by using two bits respectively, wherein the control bits of different bits can determine the RLC entities corresponding to the control bits through a preset relationship, and the control bits of different control bits are used for controlling different RLC entities.

the first processing unit 72 determines, based on the latest received control information, that data copy transmission is performed at the RLC entity indicated by the latest received control information. For example, control information from network device 1 has been received before, wherein control bits indicate two RLC entities using network device 1, and control information from network device 2 has been received after, wherein control bits indicate two RLC entities using network device 2; and comprehensively considering that the terminal equipment can also configure a preset quantity threshold value, selecting that the target quantity of the RLC entities is smaller than the preset quantity threshold value, namely the target quantity can be two, and the terminal equipment performs data transmission according to the indication of the control bits in the latter control information.

Sub-scene 12,

The first processing unit 72 determines the data copy transmission state corresponding to at least two control bits based on at least two control bits included in the control information and a preset correspondence between the control bits and the transmission state.

Or alternatively, the process may be performed,

RLC entities

1, 2 are on network device 1, RLC entities 3, 4 are on

network device

network devices

The terminal equipment in the two combined sub-scenes can be also configured with a preset quantity threshold value, and the target quantity of the selected RLC entities is smaller than the preset quantity threshold value, namely, the target quantity of the RLC entities is adopted for transmission. Similar to sub-scenario 11, in this case, to ensure transmission over a target number of RLC entities, such as one or two RLC entities, mutual coordination between network devices is required and the following criteria need to be defined:

channel conditions: such as RSRP, RSRQ, SINR, RSSI;

The first processing unit 72 of the sub-scenario 21 selects a target number of RLC entities from the RLC entities indicated by the at least two control information according to a first criterion for data duplication transmission when the at least two control information are RLC entities for different network devices; wherein the target number of RLC entities belong to the same or different network devices.

The first processing unit 72, when receiving the network indication that no data copy transmission is performed, performs one of:

based on a preconfigured target RLC entity, carrying out data transmission;

Sub-scene 22,

Still further, the first processing unit 72 may configure a preset number threshold, and select that the target number of RLC entities is smaller than the preset number threshold, that is, the target number of RLC entities, such as one or two RLC entities, transmit.

The first processing unit 72 determines a corresponding set of states based on at least two control bits contained in the control information; and selecting a data copying transmission state based on the state set. And the terminal equipment selects the data copying transmission state from the state set according to a second criterion. The second criterion is selecting a data copy transmission state from a set of states based on channel quality information.

The channel quality information includes at least one of:

while

network devices

It should be understood that the processing functions of the units in this embodiment are the same as those of the flow process in the method described in the embodiment, and will not be described in detail.

Fourth embodiment,

An embodiment of the present invention provides a network device, as shown in fig. 8, including:

a second communication unit 81 that transmits control information to the terminal device; wherein the control information is used to indicate control of data copy transmission for at least one RLC entity.

scene 1,

The second communication unit 81 indicates, through the control information sent by the network device, a target network device or RLC entity corresponding to the control information. Further, according to the identifier of the network device sending the control information, the network device or RLC entity associated with the implicit indication bit can be indicated according to the mapping relationship between the preset network device identifier and the bit. Further, it is determined that only control bits for a single network device or RLC of a single network device are included in the MAC CE, i.e., control information.

Or, indicating the target network device or RLC entity corresponding to the control information through the first information included in the control information. The first information includes an identification of the target network device. The control information, that is, the MAC CE, explicitly includes the identifier of the network device, and the target network device or RLC entity corresponding to the control bit in the control information may be determined based on the identifier of the network device.

When the target network device contains one RLC entity, the second communication unit 81 determines whether to use one RLC entity contained in the target network device for data copy transmission based on one control bit in the control information. That is, when the target network device is configured with only one RLC entity, one bit is used to control whether the terminal device uses the current RLC entity for data transmission.

When the target network device includes at least two RLC entities, the second communication unit 81 determines to perform data transmission using at least two RLC entities included in the target network device, or determines to perform data copy transmission using the target RLC entities included in the target network device, based on a one-bit control bit included in the control information. That is, when the target network device is configured with at least two RLC entities, one bit controls the plurality of RLC entities to perform duplicate transmission, or one target RLC entity of the at least two RLC entities of the target network device performs data duplicate transmission.

When the target network device includes at least two RLC entities, the second communication unit 81 determines, based on at least two control bits included in the control information, that the at least two RLC entities included in the target network device perform data copy transmission; wherein different control bits correspond to different RLC entities. Namely, whether the two RLC entities are subjected to data transmission or not is controlled by using two bits respectively, wherein the control bits of different bits can determine the RLC entities corresponding to the control bits through a preset relationship, and the control bits of different control bits are used for controlling different RLC entities.

Sub-scene 12,

network devices

Fig. 9 is a schematic block diagram of a communication device 900 provided in the embodiment of the present application, where the communication device may be a terminal device or a network device as described in the foregoing embodiment. The communication device 900 shown in fig. 9 comprises a processor 910, from which the processor 910 may call and run a computer program to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 9, the communication device 900 may also include a memory 920. Wherein the processor 910 may invoke and run a computer program from the memory 920 to implement the methods in the embodiments of the present application.

Wherein the memory 920 may be a separate device from the processor 910 or may be integrated in the processor 910.

Optionally, as shown in fig. 9, the communication device 900 may further include a transceiver 930, and the processor 910 may control the transceiver 930 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

Wherein transceiver 930 may include a transmitter and a receiver. Transceiver 930 may further include antennas, the number of which may be one or more.

Optionally, the communication device 900 may be specifically a network device in the embodiment of the present application, and the communication device 900 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 900 may be specifically a terminal device or a network device in the embodiments of the present application, and the communication device 900 may implement corresponding flows implemented by a mobile terminal/terminal device in each method in the embodiments of the present application, which are not described herein for brevity.

Fig. 10 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 1000 shown in fig. 10 includes a processor 1010, and the processor 1010 may call and run a computer program from a memory to implement the method in the embodiments of the present application.

Optionally, as shown in fig. 10, the chip 1000 may further include a memory 1020. Wherein the processor 1010 may call and run a computer program from the memory 1020 to implement the methods in embodiments of the present application.

The memory 1020 may be a separate device from the processor 1010 or may be integrated into the processor 1010.

Optionally, the chip 1000 may also include an input interface 1030. The processor 1010 may control the input interface 1030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

Optionally, the chip 1000 may further include an output interface 1040. Wherein the processor 1010 may control the output interface 1040 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

Fig. 11 is a schematic block diagram of a communication system 1100 provided by an embodiment of the present application. As shown in fig. 11, the communication system 1100 includes a terminal device 1110 and a network device 1120.

The terminal device 1110 may be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1120 may be used to implement the corresponding functions implemented by the network device in the above method, which are not described herein for brevity.

It should be appreciated that the processor of an embodiment of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.

It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a terminal device in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

Embodiments of the present application also provide a computer program product comprising computer program instructions.

Optionally, the computer program product may be applied to a network device in the embodiments of the present application, and the computer program instructions cause the computer to execute corresponding flows implemented by the network device in the methods in the embodiments of the present application, which are not described herein for brevity.

Optionally, the computer program product may be applied to a mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause a computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, which are not described herein for brevity.

The embodiment of the application also provides a computer program.

Optionally, the computer program may be applied to a network device in the embodiments of the present application, and when the computer program runs on a computer, the computer is caused to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer program may be applied to a mobile terminal/terminal device in the embodiments of the present application, where the computer program when run on a computer causes the computer to execute corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiments of the present application, and for brevity, will not be described herein.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data copy transmission control method applied to a terminal device, the method comprising:

determining, based on the control information, that at least part of RLC entities among at least one RLC entity indicated by the control information perform data transmission when the control information is for performing data copy transmission for an RLC entity of a single network device;

under the condition that the control information is at least two pieces of control information aiming at RLC entities of different network equipment, selecting a target number of RLC entities from at least one RLC entity indicated by the control information according to a first criterion for data copying and transmission;

Wherein the first criterion is to select a target number of RLC entities based on channel quality information; the channel quality information includes at least one of: channel quality information of different cells, channel quality information of different RLC entities, channel quality information of different bandwidth parts BWP.

2. The method of claim 1, wherein after the receiving control information, the method further comprises:

and determining target network equipment or RLC entity corresponding to the control information according to the network equipment for sending the control information.

3. The method of claim 1, wherein after the receiving control information, the method further comprises:

and determining target network equipment or RLC entity corresponding to the control information according to the Radio Resource Control (RRC) configuration information.

4. The method of claim 1, wherein after the receiving control information, the method further comprises:

and determining target network equipment or RLC entity corresponding to the control information according to the first information contained in the control information.

5. The method of claim 4, wherein the first information comprises an identification of the target network device.

6. A method according to claim 3, wherein the method further comprises:

and acquiring a mapping relation between the indication target network equipment or the RLC entity and the control bit through the RRC configuration information.

7. The method of any of claims 2-6, wherein the method further comprises:

when the target network device contains one RLC entity, determining whether to use the RLC entity contained in the target network device for data copy transmission based on a single control bit in the control information.

8. The method of any of claims 2-6, wherein the method further comprises:

when the target network equipment contains at least two RLC entities, determining that the target network equipment contains at least two RLC entities for data transmission or determining that the target network equipment contains target RLC entities for data copy transmission based on one control bit contained in the control information.

9. The method of any of claims 2-6, wherein the method further comprises:

when the target network equipment comprises at least two RLC entities, determining that the at least two RLC entities contained in the target network equipment perform data copying transmission based on at least two control bits contained in the control information; wherein different control bits correspond to different RLC entities.

10. The method according to any of claims 2-6, wherein the determining, based on the control information, that at least part of the RLC entities among the at least one RLC entity indicated by the control information perform data copy transmission comprises:

based on the latest received control information, determining that the RLC entity indicated by the latest received control information performs data copy transmission.

11. The method according to any of claims 2-6, wherein the determining, based on the control information, that at least part of the RLC entities among the at least one RLC entity indicated by the control information perform data copy transmission comprises:

and determining a target number of RLC entities to perform data copy transmission based on the control information.

12. The method according to any of claims 2-6, wherein the determining, based on the control information, that at least part of the RLC entities among the at least one RLC entity indicated by the control information perform data copy transmission comprises:

based on the control information, determining the RLC entity of the target network equipment to perform data copying transmission.

13. The method of any of claims 1-6, wherein the method further comprises:

and carrying out data copying transmission based on the RLC entity of the network configuration.

14. The method according to any of claims 1-6, wherein the control information comprises at least one control bit; the at least one control bit is configured to indicate a data copy transmission status of at least two RLC entities; wherein the at least two RLC entities belong to the same or different network devices.

15. The method of claim 14, wherein the method further comprises:

16. The method of claim 14, wherein the method further comprises:

17. The method of any of claims 1-6, wherein the method further comprises:

when the network is received to indicate that the data copy transmission is not performed, one of the following is performed:

Based on a preconfigured target RLC entity, carrying out data transmission;

18. The method of claim 17, wherein the control information comprises at least one control bit; the at least one control bit is used to indicate a set of states.

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

determining a corresponding state set based on at least two control bits contained in the control information;

and selecting a data copying transmission state based on the state set.

20. The method of claim 19, wherein the selecting a data copy transmission state comprises:

and selecting the data copy transmission state from the state set according to a second criterion.

21. The method of claim 20, wherein the second criterion is selecting a data copy transmission state from a set of states based on channel quality information.

22. The method of claim 21, wherein the channel quality information comprises at least one of:

23. The method of claim 22, wherein the method further comprises:

based on a preconfigured target RLC entity, carrying out data transmission;

24. A data copy transmission control method applied to a network device, the method comprising:

transmitting control information to the terminal equipment; wherein the control information is used to indicate control of data duplicate transmission for at least one RLC entity;

in the case that the control information is data duplication transmission for an RLC entity of a single network device, the control information is used for indicating the terminal device to determine, based on the control information, that at least part of RLC entities in at least one RLC entity indicated by the control information perform data transmission;

in the case that the control information is at least two control information aiming at RLC entities of different network devices, the control information is used for indicating the terminal device to select a target number of RLC entities for data duplication transmission from at least one RLC entity indicated by the control information according to a first criterion;

25. The method of claim 24, wherein the method further comprises:

and indicating the target network equipment or the RLC entity corresponding to the control information through the RRC configuration information.

26. The method of claim 24, wherein the sending control information to a terminal device comprises:

and indicating the target network equipment or the RLC entity corresponding to the control information through the first information contained in the control information.

27. The method of claim 26, wherein the first information comprises an identification of the target network device.

28. The method of claim 25, wherein the method further comprises:

and indicating the mapping relation between the target network equipment or the RLC entity and the control bit through the RRC configuration information.

29. The method according to any of claims 24-28, wherein the sending control information to a terminal device comprises:

When the network device contains one RLC entity, indicating whether to use the one RLC entity contained in the network device for data copy transmission based on one control bit in the control information.

30. The method according to any of claims 24-28, wherein the sending control information to a terminal device comprises:

and when the network equipment comprises at least two RLC entities, based on one control bit contained in the control information, indicating the at least two RLC entities contained in the network equipment to perform data transmission or indicating a target RLC entity contained in the network equipment to perform data copying transmission.

31. The method of any of claims 24-28, wherein the method further comprises:

when the network equipment comprises at least two RLC entities, indicating the at least two RLC entities contained in the network equipment to perform data copying transmission based on at least two control bits contained in the control information; wherein different control bits correspond to different RLC entities.

32. The method of any of claims 24-28, wherein the method further comprises:

negotiating with at least one other network device to determine control information for the terminal device.

33. The method according to any of claims 24-28, wherein the control information comprises at least two control bits; the at least two control bits are used for indicating the data copy transmission state of the at least two RLC entities; wherein the at least two RLC entities are directed to different network devices.

34. The method according to any of claims 24-28, wherein the control information comprises at least two control bits; the at least two control bits are used to indicate a set of states.

35. A terminal device, comprising:

a first processing unit, configured to determine, based on the control information, that at least part of RLC entities among at least one RLC entity indicated by the control information perform data transmission when the control information is for performing data copy transmission with respect to RLC entities of a single network device;

a first processing unit, configured to select a target number of RLC entities from at least one RLC entity indicated by the control information according to a first criterion for performing data duplication transmission when the control information is at least two control information for RLC entities of different network devices; wherein the first criterion is to select a target number of RLC entities based on channel quality information; the channel quality information includes at least one of: channel quality information of different cells, channel quality information of different RLC entities, channel quality information of different bandwidth parts BWP.

36. The terminal device of claim 35, wherein the first processing unit determines, according to a network device that transmits control information, a target network device or RLC entity to which the control information corresponds.

37. The terminal device of claim 35, wherein the first processing unit determines a target network device or RLC entity corresponding to the control information according to radio resource control, RRC, configuration information.

38. The terminal device of claim 35, wherein the first processing unit determines, according to first information included in the control information, a target network device or RLC entity to which the control information corresponds.

39. The terminal device of claim 38, wherein the first information includes an identification of the target network device.

40. The terminal device of claim 37, wherein the first processing unit obtains, via the RRC configuration information, a mapping relationship between an indication target network device or RLC entity and control bits.

41. The terminal device of any of claims 36-40, wherein the first processing unit, when the target network device comprises an RLC entity, determines whether to use an RLC entity comprised by the target network device for data copy transmission based on a control bit in the control information.

42. The terminal device according to any of claims 36-40, wherein the first processing unit determines, when a target network device contains at least two RLC entities, to perform data transmission by the at least two RLC entities contained in the target network device or determines to perform data copy transmission by using the target RLC entity contained in the target network device, based on a one-bit control bit contained in the control information.

43. The terminal device according to any of claims 36-40, wherein the first processing unit determines, when a target network device contains at least two RLC entities, that the target network device contains at least two RLC entities for data copy transmission based on at least two control bits contained in the control information; wherein different control bits correspond to different RLC entities.

44. The terminal device of any of claims 36-40, wherein the first processing unit determines, based on the latest received control information, that a data copy transmission is performed at the RLC entity indicated by the latest received control information.

45. The terminal device of any of claims 36-40, wherein the first processing unit determines a target number of RLC entities for data copy transmission based on control information.

46. The terminal device of any of claims 36-40, wherein the first processing unit determines, based on control information, that the RLC entity of the target network device is performing data copy transmission.

47. The terminal device of any of claims 36-40, wherein the first processing unit performs data copy transmission based on a network configured RLC entity.

48. The terminal device according to any of claims 36-40, wherein the control information comprises at least one control bit; the at least one control bit is configured to indicate a data copy transmission status of at least two RLC entities; wherein the at least two RLC entities belong to the same or different network devices.

49. The terminal device of claim 48, wherein the first processing unit determines a data copy transmission state corresponding to at least two control bits based on the at least two control bits included in the control information and a preset correspondence between the control bits and the transmission state.

50. The terminal device of claim 48, wherein the first processing unit determines a data copy transmission state corresponding to at least two control bits based on the at least two control bits included in the control information and a correspondence between the control bits and the transmission state of the network configuration.

51. The terminal device of any of claims 35-40, wherein the first processing unit, when receiving the network indication that no data copy transmission is performed, performs one of:

based on a preconfigured target RLC entity, carrying out data transmission;

and selecting the target number of RLC entities for data transmission.

52. The terminal device of claim 51, wherein the control information includes at least one control bit; the at least one control bit is used to indicate a set of states.

53. The terminal device of claim 52, wherein said first processing unit,

and selecting a data copying transmission state based on the state set.

54. The terminal device of claim 53, wherein said first processing unit selects a data copy transmission state from said set of states according to a second criterion.

55. The terminal device of claim 54, wherein the second criterion is selecting a data copy transmission state from a set of states based on channel quality information.

56. The terminal device of claim 55, wherein the channel quality information includes at least one of:

57. The terminal device of claim 56, wherein said first processing unit, when receiving the network indication that no data copy transmission is made, performs one of:

based on a preconfigured target RLC entity, carrying out data transmission;

58. A network device, comprising:

a second communication unit which transmits control information to the terminal device; wherein the control information is used to indicate control of data duplicate transmission for at least one RLC entity;

59. The network device of claim 58, wherein the second communication unit indicates, through RRC configuration information, a target network device or RLC entity to which the control information corresponds.

60. The network device of claim 58, wherein the second communication unit indicates, through first information included in the control information, a target network device or RLC entity to which the control information corresponds.

61. The network device of claim 60, wherein the first information comprises an identification of the target network device.

62. The network device of claim 59, wherein the second communication unit indicates a mapping relationship between a target network device or RLC entity and control bits through the RRC configuration information.

63. The network device of any of claims 58-62, wherein the second communication unit, when the network device comprises an RLC entity, indicates whether to use the RLC entity comprised by the network device for data copy transmission based on a one-bit control bit in the control information.

64. The network device according to any of claims 58-62, wherein the second communication unit instructs, when the network device contains at least two RLC entities, the at least two RLC entities contained in the network device to perform data transmission or instructs to perform data copy transmission with a target RLC entity contained in the network device based on a one-bit control bit contained in the control information.

65. The network device according to any of claims 58-62, wherein the second communication unit, when the network device contains at least two RLC entities, instructs the at least two RLC entities contained in the network device to perform data copy transmission based on at least two control bits contained in the control information; wherein different control bits correspond to different RLC entities.

66. The network device of any of claims 58-62, wherein the second communication unit negotiates with at least one other network device to determine control information for the terminal device.

67. The network device of any one of claims 58-62, wherein the control information comprises at least two control bits; the at least two control bits are used for indicating the data copy transmission state of the at least two RLC entities; wherein the at least two RLC entities are directed to different network devices.

68. The network device of any one of claims 58-62, wherein the control information comprises at least two control bits; the at least two control bits are used to indicate a set of states.

69. A terminal device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

wherein the memory is adapted to store a computer program, said processor being adapted to invoke and run the computer program stored in said memory, performing the steps of the method according to any of claims 1-23.

70. A network device, comprising: a processor and a memory for storing a computer program capable of running on the processor,

Wherein the memory is adapted to store a computer program, said processor being adapted to invoke and run the computer program stored in said memory, performing the steps of the method according to any of claims 24-34.

71. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 1-23.

72. A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any of claims 24-34.

73. A computer readable storage medium for storing a computer program which causes a computer to perform the steps of the method of any one of claims 1-34.