CN118055452A

CN118055452A - Data transmission method, device, terminal equipment and network side equipment

Info

Publication number: CN118055452A
Application number: CN202211399962.XA
Authority: CN
Inventors: 刘佳敏
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-11-09
Filing date: 2022-11-09
Publication date: 2024-05-17
Also published as: WO2024099143A1

Abstract

The application discloses a data transmission method, a device, a terminal device and network side equipment, which belong to the technical field of communication, and the data transmission method of the embodiment of the application comprises the following steps: the method comprises the steps that terminal equipment obtains synchronous transmission configuration information, wherein the synchronous transmission configuration information is used for synchronous transmission of data in at least two transmission paths; and the terminal equipment acquires the public transmission resource and synchronously transmits data based on the synchronous transmission configuration information and the public transmission resource.

Description

Data transmission method, device, terminal equipment and network side equipment

Technical Field

The present application belongs to the technical field of communications, and in particular, relates to a data transmission method, a data transmission device, a terminal device, and a network side device.

Background

A Relay (Relay) technology in a wireless communication system is to add one or more Relay nodes between a base station and a terminal, and is responsible for forwarding a wireless signal one or more times, i.e. the wireless signal can reach the terminal only through multiple hops.

The wireless relay technology not only can be used for expanding cell coverage and compensating cell coverage blind points, but also can improve cell capacity through space resource multiplexing. For indoor coverage, the Relay technology can also play a role in overcoming the penetration loss and improving the indoor coverage quality.

Taking a simpler two-hop relay as an example, the wireless relay divides a base station-terminal link into two links of a base station-relay station and a relay station-terminal, so that a link with poor quality is replaced by two links with good quality, and higher link capacity and better coverage are obtained.

The related art only supports single-path communication of a single-side relay or a direct link, and is in discussion of multi-path communication, so that a scheme of multi-path synchronous transmission does not exist.

Disclosure of Invention

The embodiment of the application provides a data transmission method, a data transmission device, terminal equipment and network side equipment, which can realize multi-path synchronous transmission in a UE relay scene.

In a first aspect, a data transmission method is provided, including:

the method comprises the steps that terminal equipment obtains synchronous transmission configuration information, wherein the synchronous transmission configuration information is used for synchronous transmission of data in at least two transmission paths;

And the terminal equipment acquires the public transmission resource and synchronously transmits data based on the synchronous transmission configuration information and the public transmission resource.

In a second aspect, there is provided another data transmission method, comprising:

The method comprises the steps that network side equipment receives terminal capability information and/or return information of terminal equipment, wherein the terminal equipment comprises remote equipment and relay equipment, and the return information is used for indicating a return mode between the remote equipment and the relay equipment;

The network side equipment determines terminal equipment participating in synchronous transmission according to the terminal capability information and the feedback information of the terminal equipment;

the network side equipment configures synchronous transmission configuration information aiming at terminal equipment participating in synchronous transmission, and the synchronous transmission configuration information is used for synchronous transmission of data.

In a third aspect, a data transmission apparatus is provided, applied to a terminal device, including:

The configuration information acquisition module is used for acquiring synchronous transmission configuration information, and the synchronous transmission configuration information is used for carrying out synchronous transmission of data in at least two transmission paths;

And the synchronous transmission module is used for acquiring the public transmission resources and synchronously transmitting data based on the synchronous transmission configuration information and the public transmission resources.

In a fourth aspect, another data transmission apparatus is provided, which is applied to a network side device, and includes:

The terminal equipment comprises remote equipment and relay equipment, wherein the return information is used for indicating a return mode between the remote equipment and the relay equipment;

The equipment determining module is used for determining terminal equipment participating in synchronous transmission according to the terminal capability information and the feedback information of the terminal equipment;

The information configuration module is used for configuring synchronous transmission configuration information aiming at terminal equipment participating in synchronous transmission, and the synchronous transmission configuration information is used for carrying out synchronous transmission of data.

In a fifth aspect, there is provided a terminal device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the data transmission method according to the first aspect.

In a sixth aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the data transmission method according to the second aspect.

In a seventh aspect, there is provided a data transmission system comprising: a terminal device and a network side device, the terminal device being operable to perform the steps of the data transmission method as described in the first aspect, and the network side device being operable to perform the steps of the data transmission method as described in the second aspect.

In an eighth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect or performs the steps of the method according to the second aspect.

In a ninth aspect, there is provided a chip comprising a processor and a communication interface, the communication interface and the processor being coupled, the processor being configured to execute a program or instructions to implement the data transmission method according to the first aspect or to implement the data transmission method according to the second aspect.

In a tenth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executable by at least one processor to implement the steps of the data transmission method according to the first or second aspect.

In the embodiment of the application, the terminal equipment can synchronously transmit data through multiple paths based on the acquired public transmission configuration information and public transmission resources, so that the reliability and time delay of data transmission are improved, the resource consumption is not additionally improved, and the system efficiency is ensured on the basis of improving the transmission effect.

Drawings

Fig. 1 is a block diagram of a wireless communication system to which embodiments of the present application are applicable;

FIG. 2 is a schematic diagram of a UE-to-Network relay in an embodiment of the present application;

Fig. 3 is a schematic view of a multipath scenario based on a SL relay architecture according to an embodiment of the present application;

FIG. 4 is a flow chart of a data transmission method in an embodiment of the application;

fig. 5 is a schematic diagram of multipath transmission between a terminal device and a network side device in an embodiment of the present application;

FIG. 6 is a flow chart of another data transmission method in an embodiment of the application;

Fig. 7 is a block diagram of a data transmission apparatus in an embodiment of the present application;

fig. 8 is a block diagram of another data transmission apparatus in an embodiment of the present application;

Fig. 9 is a block diagram of a communication device in an embodiment of the application;

fig. 10 is a block diagram of a terminal device in an embodiment of the present application;

Fig. 11 is a block diagram of a network device according to an embodiment of the present application;

fig. 12 is a block diagram of another network device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below 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 are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New Radio (NR) system for exemplary purposes and NR terminology is used in much of the following description, but these techniques may also be applied to applications other than NR system applications, such as6 th Generation (6G) communication systems.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal device 11 and a network device 12. The terminal device 11 may be a Mobile phone, a tablet Computer (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side device called a notebook, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a palm Computer, a netbook, an ultra-Mobile Personal Computer (UMPC), a Mobile internet appliance (Mobile INTERNET DEVICE, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (home device with a wireless communication function, such as a refrigerator, a television, a washing machine, a furniture, etc.), a game machine, a Personal Computer (Personal Computer, a PC), a teller machine, a self-service machine, etc., and the wearable device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. It should be noted that the specific type of the terminal device 11 is not limited in the embodiment of the present application. The network-side device 12 may include an access network device or a core network device, where the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function, or a radio access network element. Access network device 12 may include a base station, a WLAN access Point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access Point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic service set (Basic SERVICE SET, BSS), an Extended service set (Extended SERVICE SET, ESS), a home node B, a home evolved node B, a transmission and reception Point (TRANSMITTING RECEIVING Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only a base station in an NR system is described as an example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility MANAGEMENT ENTITY, MME), access Mobility management functions (ACCESS AND Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and Charging Rules Function (PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified DATA MANAGEMENT, UDM), unified data warehousing (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The Relay supported in LTE at present is UE-to-Network Relay, namely one end of the Relay is connected with UE, and the other end is connected with a Network side. The UE connected to the Relay is called Remote UE (Remote UE).

Referring to fig. 2, a schematic diagram of a scenario of a UE-to-Network relay is shown. In the typical UE-to-Network scenario shown in fig. 2, the Remote UE needs to transmit data with the Network side, but due to poor coverage, a Relay UE is found as a Relay, where a Uu interface is between the Relay UE and the base station, and a side link (side link) interface is between the Relay UE and the Remote UE, for example, a PC5 interface. In general, a Relay UE is open and can serve any Remote UE.

The embodiment of the application provides a data transmission method and a multipath synchronous transmission scheme based on a relay technology. Taking SL relay as an example, referring to fig. 3, a multi-path scene diagram based on the SL relay architecture is shown. As shown in fig. 3, interaction of a Control Plane (CP) and/or interaction of a User Plane (UP) may be performed between the Remote UE and the network side device through a direct link or an indirect link through the Relay UE. For the SL relay architecture, multipath refers to the Remote UE establishing a non-direct path (INDIRECT PATH) and a direct path (DIRECT PATH) at the same time, or two or more INDIRECT PATH. The non-direct path refers to a wireless link where a Remote UE (or Primary UE) performs data transmission with a base station through a Uu air interface of a Relay UE (or Secondary UE). The direct connection path is a wireless link where Remote UE (or Primary UE) performs data transmission with the base station through its Uu air interface.

In multipath transmission, if the connection between each transmission node and the originating terminal equipment is sufficiently ideal, for example, an ideal backhaul link (ideal backhaul) is adopted between the originating terminal equipment and each transmission node, that is, the transmission bandwidth is sufficiently large and the transmission delay approaches zero, data of the originating terminal equipment can be simultaneously and synchronously transmitted at a plurality of transmission nodes involved in a plurality of paths, and the same transmission resource is used. The receiving end performs combined receiving, improves the receiving reliability, reduces the time delay and does not cause the rising of resource consumption.

The data transmission method provided by the embodiment of the application is described in detail below through some embodiments and application scenarios thereof with reference to the accompanying drawings.

In a first aspect, an embodiment of the present application provides a data transmission method. Referring to fig. 4, a flowchart of a data transmission method provided by an embodiment of the present application is shown. The method is applied to the terminal equipment, as shown in fig. 4, and specifically the method may include:

step 401, the terminal device acquires synchronous transmission configuration information, where the synchronous transmission configuration information is used for synchronous transmission of data in at least two transmission paths.

Step 402, the terminal device acquires a common transmission resource, and synchronously transmits data based on the synchronous transmission configuration information and the common transmission resource.

It should be noted that, in the embodiment of the present application, the terminal device may be a Remote device, that is, remote UE (or Primary UE), as an originating end or a receiving end of data; the terminal device may also be a Relay device, i.e. a Relay UE (or Secondary UE), for forwarding data. The remote device and the relay device may each be the terminal device 11 in fig. 1.

In the embodiment of the application, the terminal equipment acquires the synchronous transmission configuration information and the public transmission resource, and then synchronously transmits data in at least two transmission paths based on the synchronous transmission configuration information and the public transmission resource. The common transmission resource is each terminal device participating in synchronous transmission in the at least two transmission paths, and the common transmission resource comprises transmission resources commonly adopted by Remote UE and Relay UE. The common transmission resource may include physical layer resources, that is, physical resource forms to which the transmission data can be attached, such as optical fibers, antenna ports, and the like; time domain resources such as frames, subframes, slots, time resources represented by orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols may also be included; frequency domain resources, such as those represented by subcarriers, may also be included. And each terminal equipment participating in synchronous transmission synchronously transmits data on the public transmission resource according to the synchronous transmission configuration information.

It can be appreciated that in a multipath scenario through the UE relay, the terminal devices (including the remote device and the relay device) participating in the synchronous transmission have the same synchronous transmission configuration information.

Optionally, the synchronous transmission configuration information includes at least one of:

a1, public scheduling identification;

A2, synchronously transmitting time domain period information;

A3, synchronizing transmission parameters;

a4, synchronously transmitting the supported data types;

a5, synchronizing the transmission direction of the transmission.

For the A1 item, the common scheduling identifier may be a Group-RNTI, and each terminal device participating in synchronous transmission, including remote UE and relay UE, is allocated with the same common scheduling identifier.

For the A2 item, the synchronous transmission time domain period information may include a unicast discontinuous reception configuration (unicast DRX parameters), and/or a multicast discontinuous reception configuration (group DRX parameters), and the like.

For the A3 item, the synchronous transmission parameter is a synchronous transmission or common scheduling related parameter, such as a physical layer parameter.

For item A4, the data types supported by the synchronous transmissions are used to define the number of types of synchronous transmissions, which may include a particular data radio bearer (Data Radio Bearer, DRB), or a particular quality of service (Quality of Service, qoS) data, etc.

For the A5 item, the transmission direction of the synchronous transmission may be an uplink transmission, a downlink transmission, or one transmission direction in the UE-to-UE scenario. Optionally, in the synchronous transmission configuration information, one set of synchronous transmission parameters corresponds to one transmission direction, or one set of synchronous transmission parameters corresponds to at least two transmission directions.

The synchronous transmission configuration information is related to terminal capability information and/or backhaul information of the terminal device. The synchronous transmission configuration information can be configured by network side equipment or target terminal equipment. Optionally, before the terminal device obtains the synchronous transmission configuration information, the method further includes:

And the terminal equipment sends the terminal capability information and/or the feedback information to the network side equipment or the target terminal equipment.

The backhaul information is used for indicating a backhaul mode between the remote device and the relay device. The terminal capability information is used for reflecting whether the terminal equipment supports synchronous transmission. The target terminal device may be a remote device or a relay device participating in the synchronous transmission.

In the embodiment of the application, the terminal equipment sends the terminal capability information and/or the feedback information to the network side equipment or the target terminal equipment, and the network side equipment or the target terminal equipment selects proper terminal equipment to participate in synchronous transmission according to the terminal capability information and/or the feedback information of each terminal equipment and configures synchronous transmission configuration information for the selected terminal equipment.

The specific configuration process of the synchronous transmission configuration information will be described below by taking a network side device as an example. Referring to fig. 5, a schematic diagram of multipath transmission between a terminal device and a network side device is shown. As shown in fig. 5, in the scenario of UE-to-Network relay, communication between a remote UE and a base station (gNB) may be performed through multiple paths, for example, including a direct connection path and/or a non-direct connection path through the UE relay, and the non-direct connection path may have multiple interfaces, where an interface between the remote UE and the relay UE is an ideal backhaul, and the relay UE may forward uplink data of the remote UE to the base station through uplink multicast transmission (UL MBS, uplink Multicast Broadcast Service) or synchronous transmission (synchronous transmission).

In a UE-to-Network relay multipath scenario, in order to support multipath configuration, each terminal device involved in synchronous transmission, including remote UE and relay UE(s), needs to be in rrc_connected state, so each terminal device and Network side device may interact through radio resource control (Radio Resource Control, RRC) dedicated signaling.

When the network side device configures the synchronous transmission configuration information, it needs to acquire capability information of the remote UE and the relay UE, that is, whether the remote UE and each related relay UE can support synchronous transmission or Uplink Group-Radio Network Temporary Identifier (UL Group-RNTI) function. The terminal capability information may be reported in association with a terminal capability (UE capability) procedure, or may be reported in a separate reporting procedure, for example, in a terminal auxiliary information (UE assistance information), a terminal relay information (UE relay information), or other uplink signaling procedure.

Meanwhile, the UE needs to report the backhaul situation between the remote UE and the relay UE, because only the ideal backhaul can meet the requirement of synchronous transmission. Optionally, the terminal device is a remote device in a synchronous transmission group, and the backhaul information includes backhaul information between the remote device and each relay device in the synchronous transmission group; or the terminal equipment is a relay equipment in the synchronous transmission group, and the feedback information comprises the feedback information between the relay equipment and the remote equipment in the synchronous transmission group.

In the embodiment of the application, the remote UE can report the backhaul conditions of the remote UE and each relay UE in a unified way, and each relay UE can report the backhaul conditions between the remote UE and the remote UE, such as whether the ideal backhaul is or is associated or can be transmitted synchronously.

Optionally, the backhaul information includes at least one of:

A device identifier of the opposite device;

And the opposite terminal equipment corresponds to the cell identification of the service cell.

When the terminal equipment reports the feedback information, the terminal equipment needs to carry the equipment identifier of the opposite terminal equipment and/or the cell identifier of the service cell corresponding to the opposite terminal equipment. For example, the remote UE needs to report the relay UE ID, which may be a temporary mobile subscription identifier (SAE (System Architecture Evolution) -Temporary Mobile Subscription Identifier, S-TMSI), a cell-level radio network temporary identifier (Cell Radio Network Temporary Identifier, C-RNTI), an inactive radio network temporary identifier (Inactive Radio Network Temporary Identifier, I-RNTI), etc. in the evolved system architecture; a cell identity (SERVING CELL ID) of a serving cell corresponding to the relay UE may also be included. The relay UE needs to report the remote UE ID and/or the cell identifier of the serving cell corresponding to the remote UE. When the terminal device reports the feedback information, UE assistance information, UE relay information or other uplink signaling procedures can be used for reporting.

It should be noted that, the terminal capability information and the feedback information may be reported independently, or may be reported jointly. Optionally, if the feedback information of the terminal device indicates an ideal feedback, defaulting to the terminal device to support a synchronous transmission function; or if the terminal capability information of the terminal equipment indicates that the terminal equipment supports the synchronous transmission function and the terminal capability information carries the equipment identifier of the associated terminal equipment, defaulting to the ideal backhaul between the terminal equipment and the associated terminal equipment.

In the embodiment of the present application, a typical joint reporting manner is that when the backhaul is indicated as an ideal backhaul in the backhaul information reported by the terminal device, the terminal device defaults to support synchronous transmission capability. Or when the terminal capability information reported by the terminal equipment indicates that the terminal equipment supports synchronous transmission capability, and the terminal capability information carries associated UE, for example, the terminal capability information reported by remote UE carries a relay UE ID, or the terminal capability information reported by the relay UE carries a remote UE ID, the default related UE has an ideal backhaul.

Optionally, the terminal device sends terminal capability information and/or backhaul information to a network side device or a target terminal device, including: the terminal equipment sends terminal capability information and/or feedback information to the network side equipment or the target terminal equipment under the condition of supporting a synchronous transmission function or receiving a first notification or a first request sent by the network side equipment or the target terminal equipment; the first notification is used for indicating that the network side equipment or the target terminal equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or backhaul information of the terminal device.

The terminal device may report the terminal capability information and/or return information in different manners. As an example, the terminal device may directly send the terminal capability information and/or the backhaul information to the network side device or the target terminal device in case of supporting the synchronous transmission function. For example, if the terminal device supports the synchronous transmission function, the terminal capability information may be carried in UE capability, and if the network side device does not support synchronous transmission, the terminal capability information may be directly ignored.

Or the terminal device may send the terminal capability information and/or the backhaul information to the network side device or the target terminal device when receiving the first notification for indicating that the network side device or the target terminal device supports the synchronous transmission function. For example, when the network side device supports the synchronous transmission function, the terminal device may be notified with a system information block (System Information Block, SIB) or RRC dedicated signaling, and the terminal device may not allow reporting of terminal capability information and/or backhaul information until the terminal device obtains the notification.

As another example, the terminal device may also send the terminal capability information and/or the backhaul information to the network side device or the target terminal device after receiving the first request sent by the network side device or the target terminal device. For example, when the network side device supports the synchronous transmission function and is about to configure synchronous transmission configuration information for the terminal device as required, the network side device requests terminal capability information and/or feedback information from the terminal device, and the terminal device receives the request and reports the terminal capability information and/or the feedback information.

After knowing the terminal capability and the backhaul condition of each terminal device, the network side device can only perform configuration and synchronous scheduling operations on the terminal devices which have synchronous transmission capability and backhaul meet the requirements.

Optionally, the method comprises: if the terminal capability information or the feedback information of the terminal equipment is updated, the terminal equipment sends the updated terminal capability information or the updated feedback information to the network side equipment or the target terminal equipment.

When the condition of the remote UE or the relay UE changes, for example, the processing capability is limited, or the backhaul no longer satisfies the ideal backhaul, the UE may actively report and update information to the network side device or the target terminal device, so that the network side device or the target terminal device can remove the UE from the synchronous transmission range, or end synchronous transmission.

In addition, in the UE-to-Network relay multipath scenario, when the Network side device decides to exit from synchronous transmission according to an algorithm or other input factors, configuration update may be performed on the UE that has acquired the configuration information of synchronous transmission, and the configuration information of the previous synchronous transmission is released, so as to end the related operation of synchronous transmission.

Optionally, the synchronization transmission configuration information is cooperatively configured by each terminal device in the synchronization transmission group.

When the number of terminal devices participating in the synchronous transmission is large, each terminal device may be divided into different synchronous transmission groups. The synchronous transmission group comprises a remote device and at least one relay device, or the synchronous transmission group comprises at least two relay devices. For example, the remote UE and the relay UE1 form a group 1to perform synchronous transmission, the remote UE and the relay UE2 form a group 2 to perform synchronous transmission, and the remote UE and the relay UE1 and the relay UE3 form a group 3 to perform synchronous transmission.

In the UE-to-UE scenario, the synchronous transmission configuration information may be configured by the network side device and the target terminal device, and when the link between the terminal devices is ideal backhaul, how to interact and configure the terminal devices, or may be cooperatively configured by the terminal devices participating in synchronous transmission. Illustratively, the remote UE and the relay UE synchronously transmit the same data content to the opposite terminal device with a agreed identity, for example, the remote UE and the relay UE1 use the same source Layer2 identity (source Layer2 ID) and the same PC5 interface resource, and synchronously transmit the same data to the opposite terminal remote UE. The source layer 2ID is required to be agreed or configured in advance, which is equivalent to that of the remote UE and the relay UE1, and the receiving-end remote UE needs to know that the source layer 2ID can send data to itself, and that the subsequent data should be processed together with the data sent by each UE separately.

After the configuration of the common schedule or the synchronous transmission has been completed, the terminal devices participating in the synchronous transmission need to acquire the common transmission resources and complete the data transmission.

Optionally, step 402 of the terminal device obtaining a common transmission resource and synchronously transmitting data based on the synchronous transmission configuration information and the common transmission resource includes:

step S11, the terminal equipment monitors the public scheduling identifier to acquire public transmission resources, and each terminal equipment in the synchronous transmission group has the same public scheduling identifier;

And step S12, the terminal equipment sends uplink data to the network side equipment by utilizing the public transmission resource.

Taking UE-to-Network as an example, UEs participating in synchronous transmission need to monitor the common scheduling identifier Group-RNTI to acquire common transmission resources. When a Group-RNTI schedules a new transmission and resource, each UE configured with the Group-RNTI needs to synchronously transmit the same data with the same parameters at the scheduled resource location. In order to achieve the above objective, a fast interaction is required between UEs, in general, data is buffered in remote UEs, because the remote UEs are the initial source of data, after the arrival of the scheduling, the remote UEs need to quickly organize the data packets according to the size of the scheduled resources, for example, form media access control layer protocol data units (Medium Access Control Protocol Data Unit, MAC PDUs), and send the data packets to other UEs participating in the transmission through an ideal backhaul, and all UEs transmit the data packets processed by the physical layer, for example, interleaving, encoding, etc., on the scheduled resources; or the remote UE directly performs corresponding physical layer processing, such as interleaving and encoding, on the MAC PDU, and then transmits the MAC PDU to each participating UE for co-synchronization transmission.

Optionally, each terminal device in the synchronization transmission group uses the same hybrid automatic repeat request process identifier, or each terminal device in the synchronization transmission group synchronizes the hybrid automatic repeat request process. In the uplink transmission, each terminal device uses the same hybrid automatic repeat request (Hybrid Automatic Repeat re-Quest, HARQ) process number, or a synchronous HARQ process.

Optionally, the method further comprises: the terminal equipment retransmits the uplink data by utilizing the public transmission resource under the condition of receiving a retransmission request until the hybrid automatic retransmission request process is finished; wherein the retransmission request carries the common scheduling identifier.

In uplink transmission, the network side equipment does not need to perform HARQ feedback, and when the network side equipment uses the Group-RNTI to schedule retransmission of the same process, all the terminal equipment performs data retransmission on the same resource again according to the same method until the network side equipment successfully receives the uplink data or ends the process.

Optionally, the method further comprises: and the terminal equipment receives downlink data sent by the network side equipment by utilizing the public transmission resource, and the terminal equipment is any terminal equipment in a synchronous transmission group.

If the network side equipment synchronously sends the downlink data to the plurality of terminal equipment, the plurality of terminal equipment receives the data at the same resource position after acquiring the public transmission resource corresponding to the Group-RNTI.

Optionally, the condition that the downlink data is successfully received includes: and each terminal device in the synchronous transmission group successfully receives the downlink data in a merging way, or if any terminal device in the synchronous transmission group successfully receives the downlink data.

And each terminal device in the synchronous transmission group performs merging and receiving processing on the downlink data sent by the network side device, deletes the repeated data and determines whether the reception is successful or not. And if the downlink data is successfully received by each terminal device in the synchronous transmission group, or if at least one terminal device in the synchronous transmission group is successful in receiving the downlink data, determining that the downlink data is successful in receiving.

Optionally, at least one terminal device in the synchronous transmission group sends transmission feedback at a first feedback position, or at least two terminal devices in the synchronous transmission group send transmission feedback at respective corresponding second feedback positions, where the transmission feedback is used to indicate that the downlink data is received successfully, or the transmission feedback is used to indicate that the downlink data is received failed; each terminal device in the synchronous transmission group corresponds to the same first feedback position, and each terminal device corresponds to a second feedback position; the first feedback position and the second feedback position are configured by network side equipment, or are cooperatively agreed by each terminal equipment in the synchronous transmission group, or are specified by a protocol.

All terminal devices in the synchronous transmission group may send a common transmission feedback, such as a negative acknowledgement/positive acknowledgement (HARQ NACK/ACK), at the first feedback position for the reception process of the downlink data, for indicating successful or failed reception of the downlink data. Of course, one or more transmission feedback may also be sent by one or more terminal devices in the synchronous transmission group at their own corresponding feedback positions, i.e. the second feedback position in the present application.

Step S21, the terminal equipment acquires public transmission resources according to a preset resource selection mode;

And S22, the terminal equipment utilizes the public transmission resource to synchronously transmit data to a receiving end with other terminal equipment in a synchronous transmission group, wherein the terminal equipment is any terminal equipment in the synchronous transmission group.

The resource selection pattern includes any one of the following:

B1, scheduling public transmission resources by network equipment;

b2, selecting public transmission resources from a configuration resource pool by any terminal equipment in the synchronous transmission group according to a preset rule.

In the UE-to-UE scenario, if a group of UEs simultaneously and synchronously transmit data to a receiving UE, that is, if a terminal device and other terminal devices in the synchronous transmission group synchronously transmit data to a receiving end, each terminal device in the synchronous transmission group firstly acquires a common transmission resource according to a preset resource selection mode.

If the resource selection mode is B1, the public transmission resource adopted by the synchronous transmission group comes from the scheduling of the network side equipment. If the resource selection mode is B2, one terminal device in the synchronous transmission group can autonomously select resources in the configured resource pool according to a preset rule, and after the public transmission resource is obtained, the UE is notified to all UEs, and the receiving end is notified through the sidelink control information (Sidelink Control Information, SCI). In another possible implementation, the SCI may also be transmitted jointly by all the transmitting ends, i.e. all the terminal devices in the synchronization transmission group, and then the synchronization data transmission is performed. The receiving end combines the data from different transmission nodes and forms feedback, and all the sending ends retransmit again when needed until the receiving is successful or the process is finished.

If the joint reception between UEs is performed, one UE sends data to a group of UEs at the same time, and the method is similar to the side link multicast (PC 5 groupcast) sending, except that after the receiving end receives the data, the receiving end can combine and decode to improve the success probability and reduce the transmission delay, delete the repeated received data, and keep a complete data to reach the remote UE.

Optionally, the terminal capability information includes capability information for indicating whether the terminal device supports multiple transmissions at the same time, and before the terminal device obtains the common transmission resource in step 402, the method further includes:

step S31, the terminal equipment receives a scheduling notice sent by the network side equipment, wherein the scheduling notice is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing manner according to a public scheduling identifier and a terminal scheduling identifier;

Step 402, the terminal device obtains a common transmission resource, and synchronously transmits data based on the synchronous transmission configuration information and the common transmission resource, including:

And step S32, the terminal equipment performs data transmission simultaneously or in a time-sharing manner by utilizing the public transmission resources corresponding to the public scheduling identification and the terminal transmission resources corresponding to the terminal scheduling identification according to the scheduling notification.

In the scenario of UE-to-Network relay multipath, a common scheduling identity, such as a Group-RNTI, is typically configured for connected UEs or UE relays, which then also have their own terminal scheduling identity C-RNTI. When the UE does not have the multi-transmission capability at the same time, the scheduling of the Group-RNTI and the C-RNTI needs time division multiplexing; when the UE has multiple transmission capability at the same time, the Group-RNTI and the C-RNTI may be monitored or scheduled simultaneously.

The scheduling of Group-RNTI and C-RNTI is determined by the network-side device. Specifically, a terminal device participating in synchronous transmission, including remote UE and relay UE, needs to report capability information for indicating whether the terminal device supports multiple transmissions at the same time to a network side device. The network side equipment generates a scheduling notice according to the capability information reported by the terminal equipment so as to instruct the terminal equipment to transmit data simultaneously or in a time-sharing manner according to the public scheduling identifier and the terminal scheduling identifier. If the terminal equipment supports simultaneous multi-transmission, the network side equipment generates a scheduling notification for indicating the terminal equipment to simultaneously transmit data according to the public scheduling identifier and the terminal scheduling identifier. If the terminal equipment does not support simultaneous multi-transmission, the network side equipment generates a scheduling notification for indicating the terminal equipment to perform data transmission in a time-sharing mode according to the public scheduling identification and the terminal scheduling identification. And the terminal equipment performs data transmission simultaneously or in a time-sharing manner by utilizing the public transmission resources corresponding to the public scheduling identifier and the terminal transmission resources corresponding to the terminal scheduling identifier according to the received scheduling notification.

Optionally, the terminal device monitors the public scheduling identifier to obtain a public transmission resource, including:

The terminal equipment monitors the public scheduling identification and/or the terminal scheduling identification to acquire transmission resources.

In the scenario of UE-to-Network relay multipath, the terminal device may acquire the common transmission resource by monitoring the common scheduling identifier, and acquire the terminal transmission resource by monitoring the terminal scheduling identifier.

In an optional embodiment of the present application, the terminal device monitors a common scheduling identifier and/or a terminal scheduling identifier to obtain a transmission resource, and includes: the terminal equipment monitors the public scheduling identifier and the terminal scheduling identifier based on unicast discontinuous receiving configuration so as to acquire public transmission resources corresponding to the public scheduling identifier and terminal transmission resources corresponding to the terminal scheduling identifier.

The monitoring of the common scheduling identity, for example, the Group-RNTI, by the terminal device may multiplex the monitoring procedure of the terminal scheduling identity C-RNTI in the unicast discontinuous reception configuration (unicast DRX parameters). When multiplexing existing unicast DRX parameters, the influence and operation of Group-RNTI on DRX parameters, the C-RNTI is completely multiplexed, and the UE needs to monitor both the C-RNTI and the Group-RNTI at ACTIVE TIME.

Optionally, the common scheduling identifier and the terminal scheduling identifier correspond to the same set of discontinuous receiving configuration, the common scheduling identifier and the terminal scheduling identifier correspond to the same timer, and the timer comprises at least one of an inactivity timer, a hybrid automatic repeat request round trip delay timer and a hybrid automatic repeat request timer.

When the existing unicast DRX parameters is multiplexed, the public scheduling identifier and the terminal scheduling identifier correspond to the same set of discontinuous receiving configuration, and the public scheduling identifier and the terminal scheduling identifier correspond to the same timer. Specifically, the Group-RNTI scheduled new transmission also restarts the inactivity timer (DRX INACTIVITY TIMER), the Group-RNTI scheduled resource end location also starts the hybrid automatic repeat request round trip delay timer (HARQ RTT TIMER), and starts the corresponding hybrid automatic repeat timer (HARQ retransmission timer) after HARQ RTT TIMER times out.

In another optional embodiment of the present application, the terminal device monitors a common scheduling identifier and/or a terminal scheduling identifier to obtain a transmission resource, including: the terminal equipment monitors the public scheduling identifier in the multicast discontinuous receiving effective time to acquire public transmission resources corresponding to the public scheduling identifier; and the terminal equipment monitors the terminal scheduling identifier in the unicast discontinuous receiving effective time so as to acquire terminal transmission resources corresponding to the terminal scheduling identifier.

The listening of the terminal device to a common scheduling identity, e.g. Group-RNTI, may also configure and maintain a separate multicast discontinuous reception configuration (Group DRX parameters). If separate Group DRX parameters is configured and maintained for common schedule identity, then both sets of DRX parameters are each running, the UE listens to the Group-RNTI during the multicast discontinuous reception active time (Group DRX ACTIVE TIME) and the UE listens to the C-RNTI during the unicast discontinuous reception active time (unified DRX ACTIVE TIME).

Optionally, the common scheduling identifier and the terminal scheduling identifier respectively correspond to independent discontinuous receiving configuration and to independent timers, and the timers comprise at least one of an on duration timer, an inactivity timer, a hybrid automatic repeat request round trip delay timer and a hybrid automatic repeat request timer.

If the terminal device configures and maintains separate Group DRX parameters for the common scheduling identifier, the common scheduling identifier Group-RNTI and the terminal scheduling identifier C-RNTI respectively correspond to separate timers, such as an on duration timer (onDuration timer), an inactivity timer (INACTIVITY TIMER), a hybrid automatic repeat request round trip delay timer (HARQ RTT TIMER), a hybrid automatic repeat request timer (HARQ retransmission timer), and the like.

In summary, the application provides a data transmission method, in a UE relay scenario, a terminal device can synchronously transmit data through multiple paths based on acquired public transmission configuration information and public transmission resources, so that reliability and time delay of data transmission are improved, no additional improvement is caused to resource consumption, and system efficiency is ensured on the basis of improving transmission effect.

In a second aspect, an embodiment of the present application provides another data transmission method. Referring to fig. 6, a flowchart of another data transmission method according to an embodiment of the present application is shown. The method is applied to network side equipment, as shown in fig. 6, and specifically the method can include:

in step 601, the network side device receives terminal capability information and/or backhaul information of a terminal device, where the terminal device includes a remote device and a relay device, and the backhaul information is used to indicate a backhaul manner between the remote device and the relay device.

Step 602, the network side device determines a terminal device participating in synchronous transmission according to the terminal capability information and/or the backhaul information of the terminal device.

Step 603, the network side device configures synchronous transmission configuration information for a terminal device participating in synchronous transmission, where the synchronous transmission configuration information is used for synchronous transmission of data.

It should be noted that, in the embodiment of the present application, the terminal device may be a Remote device, that is, remote UE (or Primary UE), as an originating end or a receiving end of data; the terminal device may also be a Relay device, i.e. a Relay UE (or Secondary UE), for forwarding data. The remote device and the relay device may each be the terminal device 11 in fig. 1. The Network side device may be an access Network device in fig. 1, such as a base station or an artificial intelligence processing node newly defined at the access Network side, or a core Network device in fig. 1, such as a Network DATA ANALYTICS Function (NWDAF), a location management Function (Location Management Function, LMF), or a processing node newly defined at the core Network side, or a combination of the above multiple nodes.

In the embodiment of the application, the network side equipment can configure synchronous transmission configuration information for each terminal equipment participating in synchronous transmission, including the remote equipment and the relay equipment. When the network side equipment configures the synchronous transmission configuration information, the capability information of the remote UE and the relay UE, namely whether the remote UE and each related relay UE can support synchronous transmission or the function of the UL Group-RNTI, needs to be known at first. The terminal capability information may be reported in association with the UE capability procedure, or may be reported by a separate reporting procedure, for example UE assistance information, UE relay information, or other uplink signaling procedure.

It should be noted that, the terminal capability information and the feedback information may be reported independently, or may be reported jointly. A typical joint reporting manner is that when the backhaul is indicated as ideal backhaul in the backhaul information reported by the terminal device, the terminal device defaults to support synchronous transmission capability. Or when the terminal capability information reported by the terminal equipment indicates that the terminal equipment supports synchronous transmission capability, and the terminal capability information carries associated UE, for example, the terminal capability information reported by remote UE carries a relay UE ID, or the terminal capability information reported by the relay UE carries a remote UE ID, the default related UE has an ideal backhaul.

After knowing the terminal capability and the backhaul condition of each terminal device, the network side device can only perform configuration and synchronous scheduling operations on the terminal devices which have synchronous transmission capability and backhaul meet the requirements. Therefore, the network side equipment determines the terminal equipment participating in the synchronous transmission according to the terminal capability information and/or the feedback information reported by the terminal equipment, and configures synchronous transmission configuration information for the terminal equipment participating in the synchronous transmission. It will be appreciated that the terminal devices involved in the synchronous transmission support synchronous transmission, and that the backhaul between the other terminal devices is an ideal backhaul.

Optionally, before the network side device receives the terminal capability information and/or the backhaul information of the terminal device, the method further includes: the network side equipment sends a first notification or a first request to the terminal equipment.

In the embodiment of the application, the network side equipment can instruct the terminal equipment to report the terminal capability information and/or the return information through the first notification or the first request. The first notification is used for indicating that the network side equipment supports a synchronous transmission function. For example, when the network side device supports the synchronous transmission function, the terminal device may be notified with SIB or dedicated signaling, and the terminal device is allowed to report the terminal capability information and/or backhaul information after obtaining the notification. The first request is used for requesting terminal capability information and/or backhaul information of the terminal device. For example, when the network side device supports the synchronous transmission function and is about to configure synchronous transmission configuration information for the terminal device as required, the network side device requests terminal capability information and/or feedback information from the terminal device, and the terminal device receives the request and reports the terminal capability information and/or the feedback information.

a1, public scheduling identification;

A2, synchronously transmitting time domain period information;

A3, synchronizing transmission parameters;

a4, synchronously transmitting the supported data types;

a5, synchronizing the transmission direction of the transmission.

For the A2 item, the synchronous transmission time domain period information may include a unicast discontinuous reception configuration (unicast DRX pattern), a multicast discontinuous reception configuration (group DRX pattern), and the like.

For the A4 item, the data type supported by the synchronous transmission is used to define the number type of synchronous transmissions, and the data type may include a specific DRB, or a specific QoS, etc.

In an optional embodiment of the present application, the synchronization transmission configuration information includes a common scheduling identifier, and the method further includes: the network side equipment schedules public transmission resources according to the public scheduling identification; and the network side equipment transmits downlink data to each terminal equipment in the synchronous transmission group by utilizing the public transmission resource.

In the UE-to-Network relay multipath scenario, the Network side device may schedule a common transmission resource through a common scheduling identifier, and send downlink data to each terminal device participating in synchronous transmission by using the common transmission resource.

Optionally, the method further comprises: the network side equipment receives transmission feedback sent by the terminal equipment in the synchronous transmission group at a first feedback position or a second feedback position, wherein the transmission feedback is used for indicating that the downlink data is successfully received or the transmission feedback is used for indicating that the downlink data is failed to be received; each terminal device in the synchronous transmission group corresponds to the same first feedback position, and each terminal device corresponds to a second feedback position; the first feedback position and the second feedback position are configured by network side equipment, or are cooperatively agreed by each terminal equipment in the synchronous transmission group, or are specified by a protocol.

All terminal devices in the synchronous transmission group can send a common transmission feedback, such as HARQ NACK/ACK, at the first feedback position for the downlink data receiving process, so as to indicate that the downlink data is received successfully or failed. Of course, one or more transmission feedback may also be sent by one or more terminal devices in the synchronous transmission group at their own corresponding feedback positions, i.e. the second feedback position in the present application. The network side device can determine whether the downlink data is successfully transmitted according to the transmission feedback received at the first feedback position or the second feedback position.

Optionally, the terminal capability information includes capability information for indicating whether the terminal device supports multiple transmissions at the same time, and the method further includes: the network side equipment determines a public scheduling identifier and/or a terminal scheduling identifier corresponding to the terminal equipment according to the terminal capability information; the network side equipment sends a scheduling notice to the terminal equipment, wherein the scheduling notice is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing mode according to a public scheduling identifier and a terminal scheduling identifier.

In summary, the embodiment of the application provides a data transmission method, network side equipment can determine terminal equipment participating in synchronous transmission according to terminal capability information and/or return information reported by the terminal equipment, and configure synchronous transmission configuration information for the terminal equipment participating in synchronous transmission, so that the terminal equipment can synchronously transmit data through multiple paths based on the acquired public transmission configuration information and public transmission resources, the reliability and time delay of data transmission are improved, no additional improvement is caused to resource consumption, and the system efficiency is ensured on the basis of improving transmission effects.

According to the data transmission method provided by the embodiment of the application, the execution main body can be a data transmission device. In the embodiment of the present application, a data transmission device executes a data transmission method as an example, which describes the data transmission device provided in the embodiment of the present application.

In a third aspect, an embodiment of the present application provides a data transmission apparatus. Referring to fig. 7, a block diagram of a data transmission apparatus according to an embodiment of the present application is shown, where the apparatus may be applied to a terminal device. As shown in fig. 7, the apparatus may specifically include:

A configuration information obtaining module 701, configured to obtain synchronous transmission configuration information, where the synchronous transmission configuration information is used for synchronous transmission of data in at least two transmission paths;

And the synchronous transmission module 702 is configured to acquire a common transmission resource and synchronously transmit data based on the synchronous transmission configuration information and the common transmission resource.

A public scheduling identifier;

synchronously transmitting time domain period information;

Synchronizing transmission parameters;

Synchronizing the supported data types;

The transmission direction of the synchronous transmission.

Optionally, in the synchronous transmission configuration information, one set of synchronous transmission parameters corresponds to one transmission direction, or one set of synchronous transmission parameters corresponds to at least two transmission directions.

Optionally, the synchronous transmission configuration information is configured by a network side device or a target terminal device, or is cooperatively configured by each terminal device in a synchronous transmission group; the target terminal equipment comprises remote equipment or relay equipment; the synchronous transmission group comprises a remote device and at least one relay device, or the synchronous transmission group comprises at least two relay devices.

Optionally, the apparatus further comprises:

The first information sending module is used for sending terminal capability information and/or return information to the network side equipment or the target terminal equipment; the backhaul information is used for indicating a backhaul mode between the remote device and the relay device.

Optionally, the terminal device is a remote device in a synchronous transmission group, and the backhaul information includes backhaul information between the remote device and each relay device in the synchronous transmission group; or alternatively

The terminal equipment is a relay equipment in a synchronous transmission group, and the feedback information comprises the feedback information between the relay equipment and a remote equipment in the synchronous transmission group.

Optionally, the backhaul information includes at least one of:

A device identifier of the opposite device;

Optionally, the first information sending module includes:

The information sending sub-module is used for sending terminal capacity information and/or return information to the network side equipment or the target terminal equipment under the condition that the terminal equipment supports a synchronous transmission function or receives a first notification or a first request sent by the network side equipment or the target terminal equipment; the first notification is used for indicating that the network side equipment or the target terminal equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or backhaul information of the terminal device.

Optionally, if the feedback information of the terminal device indicates an ideal feedback, defaulting to the terminal device to support a synchronous transmission function; or if the terminal capability information of the terminal equipment indicates that the terminal equipment supports the synchronous transmission function and the terminal capability information carries the equipment identifier of the associated terminal equipment, defaulting to the ideal backhaul between the terminal equipment and the associated terminal equipment.

Optionally, the apparatus further comprises:

And the second information sending module is used for sending updated terminal capability information or backhaul information to the network side equipment or the target terminal equipment if the terminal capability information or backhaul information of the terminal equipment is updated.

Optionally, the terminal capability information includes capability information for indicating whether the terminal device supports multiple transmissions at the same time, and the apparatus further includes:

The scheduling notification receiving module is used for receiving scheduling notification sent by the network side equipment, and the scheduling notification is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing manner according to the public scheduling identification and the terminal scheduling identification;

The synchronous transmission module comprises:

And the first synchronous transmission sub-module is used for carrying out data transmission simultaneously or in a time-sharing manner by utilizing the public transmission resources corresponding to the public scheduling identification and the terminal transmission resources corresponding to the terminal scheduling identification according to the scheduling notification.

Optionally, the apparatus further comprises:

And the downlink data receiving module is used for receiving downlink data sent by the network side equipment by utilizing the public transmission resource, and the terminal equipment is any terminal equipment in the synchronous transmission group.

Optionally, the synchronous transmission module includes:

the first resource acquisition sub-module is used for the terminal equipment to acquire public transmission resources according to a preset resource selection mode;

the second synchronous transmission sub-module is used for synchronously transmitting data to the receiving end by utilizing the public transmission resource and other terminal equipment in the synchronous transmission group, wherein the terminal equipment is any terminal equipment in the synchronous transmission group;

The resource selection pattern includes any one of the following:

The public transmission resource is scheduled by the network side equipment;

And the public transmission resource is selected from the configuration resource pool by any terminal equipment in the synchronous transmission group according to a preset rule.

Optionally, the synchronous transmission module includes:

a second resource obtaining sub-module, configured to monitor a common scheduling identifier to obtain a common transmission resource, where each terminal device in the synchronous transmission group has the same common scheduling identifier;

And the uplink data transmission sub-module is used for transmitting uplink data to the network side equipment by utilizing the public transmission resource.

Optionally, each terminal device in the synchronization transmission group uses the same hybrid automatic repeat request process identifier, or each terminal device in the synchronization transmission group synchronizes the hybrid automatic repeat request process.

Optionally, the apparatus further comprises:

The data retransmission module is used for retransmitting the uplink data by utilizing the public transmission resource under the condition of receiving a retransmission request until the hybrid automatic retransmission request process is ended; wherein the retransmission request carries the common scheduling identifier.

Optionally, the second resource obtaining sub-module includes:

and the monitoring unit is used for monitoring the public scheduling identifier and/or the terminal scheduling identifier to acquire the transmission resource.

Optionally, the listening unit includes:

and the first monitoring subunit is used for monitoring the public scheduling identifier and the terminal scheduling identifier based on unicast discontinuous receiving configuration so as to acquire the public transmission resource corresponding to the public scheduling identifier and the terminal transmission resource corresponding to the terminal scheduling identifier.

Optionally, the listening unit includes:

A second monitoring subunit, configured to monitor the common scheduling identifier in a multicast discontinuous reception effective time, so as to obtain a common transmission resource corresponding to the common scheduling identifier;

and the third monitoring subunit is used for monitoring the terminal scheduling identifier in the unicast discontinuous reception effective time so as to acquire the terminal transmission resource corresponding to the terminal scheduling identifier.

The data transmission device in the embodiment of the application can be an electronic device, for example, an electronic device with an operating system, or can be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal device. By way of example, the terminal devices may include, but are not limited to, the types of terminal devices 11 listed above.

The data transmission device provided by the embodiment of the application can realize each process realized by the method embodiment of the first aspect and achieve the same technical effect, and in order to avoid repetition, the description is omitted here.

In a fourth aspect, an embodiment of the present application provides another data transmission apparatus. Referring to fig. 8, a block diagram of a data transmission apparatus according to an embodiment of the present application is shown, where the apparatus may be applied to a network side device. As shown in fig. 8, the apparatus may specifically include:

An information receiving module 801, configured to receive terminal capability information and/or backhaul information of a terminal device, where the terminal device includes a remote device and a relay device, and the backhaul information is used to indicate a backhaul manner between the remote device and the relay device;

a device determining module 802, configured to determine, according to the terminal capability information and the backhaul information of the terminal device, a terminal device participating in synchronous transmission;

an information configuration module 803 is configured to configure synchronous transmission configuration information for a terminal device participating in synchronous transmission, where the synchronous transmission configuration information is used for performing synchronous transmission of data.

A public scheduling identifier;

synchronously transmitting time domain period information;

Synchronizing transmission parameters;

Synchronizing the supported data types;

The transmission direction of the synchronous transmission.

Optionally, the backhaul information includes at least one of:

A device identifier of the opposite device;

Optionally, the apparatus further comprises:

the first sending module is used for sending a first notification or a first request to the terminal equipment; the first notification is used for indicating that the network side equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or backhaul information of the terminal device.

Optionally, the synchronous transmission configuration information includes a common scheduling identifier, and the apparatus further includes:

the resource scheduling module is used for scheduling the public transmission resources according to the public scheduling identification;

and the second sending module is used for sending downlink data to each terminal device in the synchronous transmission group by utilizing the public transmission resource.

Optionally, the apparatus further comprises:

A transmission feedback receiving module, configured to receive, at a first feedback position or a second feedback position, a transmission feedback sent by a terminal device in the synchronous transmission group, where the transmission feedback is used to indicate that the downlink data is received successfully, or the transmission feedback is used to indicate that the downlink data is received failed; each terminal device in the synchronous transmission group corresponds to the same first feedback position, and each terminal device corresponds to a second feedback position; the first feedback position and the second feedback position are configured by network side equipment, or are cooperatively agreed by each terminal equipment in the synchronous transmission group, or are specified by a protocol.

The identification determining module is used for determining a public scheduling identification and/or a terminal scheduling identification corresponding to the terminal equipment according to the terminal capability information;

And the scheduling notification sending module is used for sending scheduling notification to the terminal equipment, wherein the scheduling notification is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing manner according to the public scheduling identifier and the terminal scheduling identifier.

Optionally, as shown in fig. 9, the embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, where the memory 902 stores a program or instructions that can be executed on the processor 901, for example, when the communication device 900 is a terminal device, the program or instructions implement, when executed by the processor 901, the steps of the embodiment of the data transmission method described in the first aspect, and achieve the same technical effects. When the communication device 900 is a network side device, the program or the instruction, when executed by the processor 901, implements the steps of the embodiment of the data transmission method described in the second aspect, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

As shown in fig. 10, a schematic hardware structure of a terminal device for implementing an embodiment of the present application is shown.

The terminal device 1000 includes, but is not limited to: at least some of the components of the radio frequency unit 1001, the network module 1002, the audio output unit 1003, the input unit 1004, the sensor 1005, the display unit 1006, the user input unit 1007, the interface unit 1008, the memory 1009, and the processor 1010, etc.

Those skilled in the art will appreciate that terminal device 1000 can also include a power source (e.g., a battery) for powering the various components, which can be logically coupled to processor 1010 via a power management system to perform functions such as managing charge, discharge, and power consumption via the power management system. The terminal device structure shown in fig. 10 does not constitute a limitation of the terminal device, and the terminal device may include more or less components than those shown in the drawings, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 1004 may include a graphics processing unit (Graphics Processing Unit, GPU) 10041 and a microphone 10042, where the graphics processor 10041 processes image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 can include two portions, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 1001 may transmit the downlink data to the processor 1010 for processing; in addition, the radio frequency unit 1001 may send uplink data to the network side device. In general, the radio frequency unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 1009 may include volatile memory or nonvolatile memory, or the memory 1009 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), static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate Synchronous dynamic random access memory (Double DATA RATE SDRAM, DDRSDRAM), enhanced Synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCH LINK DRAM, SLDRAM), and Direct random access memory (DRRAM). Memory 1009 in embodiments of the application includes, but is not limited to, these and any other suitable types of memory.

The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1010.

The radio frequency unit 1001 is configured to obtain synchronous transmission configuration information, where the synchronous transmission configuration information is used for synchronous transmission of data in at least two transmission paths; and acquiring a public transmission resource, and synchronously transmitting data based on the synchronous transmission configuration information and the public transmission resource.

A public scheduling identifier;

synchronously transmitting time domain period information;

Synchronizing transmission parameters;

Synchronizing the supported data types;

The transmission direction of the synchronous transmission.

Optionally, the radio frequency unit 1001 is further configured to:

transmitting terminal capability information and/or return information to network side equipment or target terminal equipment; the backhaul information is used for indicating a backhaul mode between the remote device and the relay device.

Optionally, the backhaul information includes at least one of:

A device identifier of the opposite device;

Optionally, the radio frequency unit 1001 is specifically configured to:

Under the condition of supporting a synchronous transmission function or receiving a first notification or a first request sent by network side equipment or target terminal equipment, sending terminal capability information and/or return information to the network side equipment or the target terminal equipment; the first notification is used for indicating that the network side equipment or the target terminal equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or backhaul information of the terminal device.

Optionally, the radio frequency unit 1001 is further configured to:

and if the terminal capability information or the feedback information of the terminal equipment is updated, the updated terminal capability information or the updated feedback information is sent to the network side equipment or the target terminal equipment.

Optionally, the terminal capability information includes capability information for indicating whether the terminal device supports multiple transmissions at the same time, and the radio frequency unit 1001 is further configured to:

The terminal equipment receives a scheduling notification sent by the network side equipment, wherein the scheduling notification is used for indicating the terminal equipment to transmit data simultaneously or in a time-sharing manner according to a public scheduling identifier and a terminal scheduling identifier;

and according to the scheduling notification, carrying out data transmission simultaneously or in a time-sharing manner by utilizing the public transmission resources corresponding to the public scheduling identifier and the terminal transmission resources corresponding to the terminal scheduling identifier.

Optionally, the radio frequency unit 1001 is further configured to:

And receiving downlink data sent by the network side equipment by utilizing the public transmission resource, wherein the terminal equipment is any terminal equipment in a synchronous transmission group.

Optionally, the radio frequency unit 1001 is specifically configured to:

The terminal equipment acquires public transmission resources according to a preset resource selection mode;

Transmitting data to a receiving end synchronously by utilizing the public transmission resource and other terminal equipment in a synchronous transmission group, wherein the terminal equipment is any terminal equipment in the synchronous transmission group;

The resource selection pattern includes any one of the following:

The public transmission resource is scheduled by the network side equipment;

Optionally, the radio frequency unit 1001 is specifically configured to:

Monitoring a public scheduling identifier to acquire public transmission resources, wherein each terminal device in the synchronous transmission group has the same public scheduling identifier;

and sending uplink data to the network equipment by utilizing the public transmission resource.

Optionally, the radio frequency unit 1001 is further configured to:

under the condition of receiving a retransmission request, retransmitting the uplink data by utilizing the public transmission resource until the hybrid automatic retransmission request process is ended; wherein the retransmission request carries the common scheduling identifier.

Optionally, the radio frequency unit 1001 is specifically configured to:

and monitoring the public scheduling identification and/or the terminal scheduling identification to acquire the transmission resource.

Optionally, the radio frequency unit 1001 is specifically configured to:

Monitoring the public scheduling identifier and the terminal scheduling identifier based on unicast discontinuous receiving configuration so as to acquire public transmission resources corresponding to the public scheduling identifier and terminal transmission resources corresponding to the terminal scheduling identifier.

Optionally, the radio frequency unit 1001 is specifically configured to:

monitoring the public scheduling identifier in the multicast discontinuous reception effective time to acquire a public transmission resource corresponding to the public scheduling identifier;

and monitoring the terminal scheduling identifier in the unicast discontinuous reception effective time to acquire terminal transmission resources corresponding to the terminal scheduling identifier.

The embodiment of the present application further provides a network side device, as shown in fig. 11, where the network side device 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114 and a memory 115. The antenna 111 is connected to a radio frequency device 112. In the uplink direction, the radio frequency device 112 receives information via the antenna 111, and transmits the received information to the baseband device 113 for processing. In the downlink direction, the baseband device 113 processes information to be transmitted, and transmits the processed information to the radio frequency device 112, and the radio frequency device 112 processes the received information and transmits the processed information through the antenna 111.

The method performed by the network side device in the above embodiment may be implemented in the baseband apparatus 113, where the baseband apparatus 113 includes a baseband processor.

The baseband apparatus 113 may, for example, include at least one baseband board, where a plurality of chips are disposed, as shown in fig. 11, where one chip, for example, a baseband processor, is connected to the memory 115 through a bus interface, so as to call a program in the memory 115 to perform the network device operation shown in the above method embodiment.

The network-side device may also include a network interface 116, such as a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 1100 of the embodiment of the present invention further includes: instructions or programs stored in the memory 115 and capable of running on the processor 114, the processor 114 invokes the instructions or programs in the memory 115 to perform the method performed by the modules shown in fig. 6, and achieve the same technical effects, and are not repeated here.

The embodiment of the application also provides network side equipment. As shown in fig. 12, the network side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 1200 of the embodiment of the present invention further includes: instructions or programs stored in the memory 1203 and capable of being executed by the processor 1201, the processor 1201 calls the instructions or programs in the memory 1203 to execute the method executed by each module shown in fig. 4, and achieve the same technical effects, so that repetition is avoided and thus a detailed description is omitted.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the above-mentioned data transmission method embodiment, and can achieve the same technical effects, and in order to avoid repetition, the description is omitted here.

Wherein the processor is a processor in the terminal device described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, which comprises a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used for running programs or instructions to realize the processes of the data transmission method embodiment, and the same technical effects can be achieved, so that repetition is avoided, and the description is omitted here.

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.

The embodiments of the present application further provide a computer program/program product stored in a storage medium, where the computer program/program product is executed by at least one processor to implement the respective processes of the above-mentioned embodiments of the data transmission method, and achieve the same technical effects, and are not repeated herein.

The embodiment of the application also provides a data transmission system, which comprises: a terminal device and a network side device, wherein the terminal is configured to perform the steps of the data transmission method according to the second aspect, and the network side device is configured to perform the steps of the data transmission method according to the first aspect.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present application is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. A method of data transmission, the method comprising:

2. The method of claim 1, wherein the synchronous transmission configuration information comprises at least one of:

A public scheduling identifier;

synchronously transmitting time domain period information;

Synchronizing transmission parameters;

Synchronizing the supported data types;

The transmission direction of the synchronous transmission.

3. The method according to claim 2, wherein in the synchronous transmission configuration information, one set of synchronous transmission parameters corresponds to one transmission direction or one set of synchronous transmission parameters corresponds to at least two transmission directions.

4. The method according to claim 1, wherein the synchronous transmission configuration information is configured by a network side device or a target terminal device, or is cooperatively configured by each terminal device in a synchronous transmission group; the target terminal equipment comprises remote equipment or relay equipment; the synchronous transmission group comprises a remote device and at least one relay device, or the synchronous transmission group comprises at least two relay devices.

5. The method of claim 4, wherein before the terminal device obtains the synchronous transmission configuration information, the method further comprises:

The terminal equipment sends terminal capability information and/or feedback information to the network side equipment or the target terminal equipment; the backhaul information is used for indicating a backhaul manner between the remote device and the relay device.

6. The method of claim 5, wherein the terminal device is a remote device in a synchronous transmission group, and the backhaul information includes backhaul information between the remote device and each relay device in the synchronous transmission group; or alternatively

7. The method of claim 6, wherein the backhaul information comprises at least one of:

A device identifier of the opposite device;

8. The method according to claim 5, wherein the terminal device sends terminal capability information and/or backhaul information to the network side device or the target terminal device, including:

The terminal equipment sends terminal capability information and/or feedback information to the network side equipment or the target terminal equipment under the condition of supporting a synchronous transmission function or receiving a first notification or a first request sent by the network side equipment or the target terminal equipment; the first notification is used for indicating that the network side equipment or the target terminal equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or feedback information of the terminal equipment.

9. The method according to claim 5, wherein if the backhaul information of the terminal device indicates an ideal backhaul, the terminal device defaults to support a synchronous transmission function; or if the terminal capability information of the terminal equipment indicates that the terminal equipment supports the synchronous transmission function and the terminal capability information carries the equipment identifier of the associated terminal equipment, defaulting to the ideal backhaul between the terminal equipment and the associated terminal equipment.

10. The method of claim 5, wherein the method further comprises:

If the terminal capability information or the backhaul information of the terminal device is updated, the terminal device sends the updated terminal capability information or backhaul information to the network side device or the target terminal device.

11. The method of claim 5, wherein the terminal capability information includes capability information for indicating whether the terminal device supports simultaneous multi-transmission, and wherein the method further comprises, prior to the terminal device acquiring the common transmission resource:

The terminal equipment receives a scheduling notification sent by the network side equipment, wherein the scheduling notification is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing manner according to a public scheduling identifier and a terminal scheduling identifier;

The terminal equipment acquires a public transmission resource, and synchronously transmits data based on the synchronous transmission configuration information and the public transmission resource, and the method comprises the following steps:

And the terminal equipment performs data transmission simultaneously or in a time-sharing manner by utilizing the public transmission resources corresponding to the public scheduling identifier and the terminal transmission resources corresponding to the terminal scheduling identifier according to the scheduling notification.

12. The method according to claim 4, wherein the method further comprises:

And the terminal equipment receives downlink data sent by the network side equipment by utilizing the public transmission resource, wherein the terminal equipment is any terminal equipment in a synchronous transmission group.

13. The method of claim 12, wherein the condition for successful reception of the downlink data comprises: and each terminal device in the synchronous transmission group successfully receives the downlink data in a merging way, or if any terminal device in the synchronous transmission group successfully receives the downlink data.

14. The method according to claim 12, wherein at least one terminal device in the synchronous transmission group sends transmission feedback at a first feedback position or at least two terminal devices in the synchronous transmission group send transmission feedback at respective corresponding second feedback positions, the transmission feedback being used to indicate that the downlink data reception was successful or the transmission feedback being used to indicate that the downlink data reception was failed; each terminal device in the synchronous transmission group corresponds to the same first feedback position, and each terminal device corresponds to a second feedback position; the first feedback position and the second feedback position are configured by the network side equipment, or are cooperatively agreed by each terminal equipment in the synchronous transmission group, or are specified by a protocol.

15. The method of claim 4, wherein the terminal device obtains a common transmission resource and synchronously transmits data based on the synchronous transmission configuration information and the common transmission resource, comprising:

The terminal equipment utilizes the public transmission resource to synchronously transmit data to a receiving end with other terminal equipment in a synchronous transmission group, wherein the terminal equipment is any terminal equipment in the synchronous transmission group;

The resource selection pattern includes any one of the following:

scheduling common transmission resources by the network device;

16. The method of claim 4, wherein the terminal device obtains a common transmission resource and synchronously transmits data based on the synchronous transmission configuration information and the common transmission resource, comprising:

The terminal equipment monitors the public scheduling identifier to acquire public transmission resources, and each terminal equipment in the synchronous transmission group has the same public scheduling identifier;

and the terminal equipment transmits uplink data to the network side equipment by utilizing the public transmission resource.

17. The method of claim 16, wherein each terminal device in the synchronized transmission group uses the same hybrid automatic repeat request process identification or the synchronized hybrid automatic repeat request process of each terminal device in the synchronized transmission group.

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

the terminal equipment retransmits the uplink data by utilizing the public transmission resource under the condition of receiving a retransmission request until the hybrid automatic retransmission request process is finished; wherein the retransmission request carries the common scheduling identifier.

19. The method of claim 16, wherein the terminal device listening to the common scheduling identity to obtain a common transmission resource comprises:

20. The method according to claim 19, wherein the terminal device listens to the common scheduling identity and/or the terminal scheduling identity to obtain the transmission resource, comprising:

The terminal equipment monitors the public scheduling identifier and the terminal scheduling identifier based on unicast discontinuous receiving configuration so as to acquire public transmission resources corresponding to the public scheduling identifier and terminal transmission resources corresponding to the terminal scheduling identifier.

21. The method of claim 20, wherein the common schedule identity and the terminal schedule identity correspond to a same set of discontinuous reception configurations, wherein the common schedule identity and the terminal schedule identity correspond to a same timer, and wherein the timer comprises at least one of an inactivity timer, a hybrid automatic repeat request round trip delay timer, and a hybrid automatic repeat request timer.

22. The method according to claim 19, wherein the terminal device listens to the common scheduling identity and/or the terminal scheduling identity to obtain the transmission resource, comprising:

The terminal equipment monitors the public scheduling identifier in the multicast discontinuous receiving effective time to acquire public transmission resources corresponding to the public scheduling identifier;

And the terminal equipment monitors the terminal scheduling identifier in the unicast discontinuous receiving effective time so as to acquire terminal transmission resources corresponding to the terminal scheduling identifier.

23. The method of claim 22, wherein the common schedule identity and the terminal schedule identity each correspond to an independent discontinuous reception configuration and to an independent timer, the timer comprising at least one of an on duration timer, an inactivity timer, a hybrid automatic repeat request round trip delay timer, and a hybrid automatic repeat request timer.

24. A method of data transmission, the method comprising:

25. The method of claim 24, wherein the synchronous transmission configuration information comprises at least one of:

A public scheduling identifier;

synchronously transmitting time domain period information;

Synchronizing transmission parameters;

Synchronizing the supported data types;

The transmission direction of the synchronous transmission.

26. The method of claim 25, wherein in the synchronous transmission configuration information, one set of synchronous transmission parameters corresponds to one transmission direction or one set of synchronous transmission parameters corresponds to at least two transmission directions.

27. The method of claim 24, wherein the backhaul information comprises at least one of:

A device identifier of the opposite device;

28. The method according to claim 24, wherein before the network side device receives the terminal capability information and/or backhaul information of the terminal device, the method further comprises:

The network side equipment sends a first notification or a first request to the terminal equipment; the first notification is used for indicating that the network side equipment supports a synchronous transmission function; the first request is used for requesting terminal capability information and/or backhaul information of the terminal device.

29. The method of claim 25, wherein the synchronized transmission configuration information includes a common scheduling identification, the method further comprising:

the network side equipment schedules public transmission resources according to the public scheduling identification;

and the network side equipment transmits downlink data to each terminal equipment in the synchronous transmission group by utilizing the public transmission resource.

30. The method of claim 29, further comprising:

The network side equipment receives transmission feedback sent by the terminal equipment in the synchronous transmission group at a first feedback position or a second feedback position, wherein the transmission feedback is used for indicating that the downlink data is successfully received or the transmission feedback is used for indicating that the downlink data is failed to be received; each terminal device in the synchronous transmission group corresponds to the same first feedback position, and each terminal device corresponds to a second feedback position; the first feedback position and the second feedback position are configured by network side equipment, or are cooperatively agreed by each terminal equipment in the synchronous transmission group, or are specified by a protocol.

31. The method of claim 24, wherein the terminal capability information includes capability information for indicating whether the terminal device supports simultaneous multi-transmission, the method further comprising:

The network side equipment determines a public scheduling identifier and/or a terminal scheduling identifier corresponding to the terminal equipment according to the terminal capability information;

the network side equipment sends a scheduling notice to the terminal equipment, wherein the scheduling notice is used for indicating the terminal equipment to perform data transmission simultaneously or in a time-sharing mode according to a public scheduling identifier and a terminal scheduling identifier.

32. A data transmission apparatus, characterized in that it is applied to a terminal device, said apparatus comprising:

33. A data transmission apparatus, applied to a network-side device, comprising:

34. A terminal device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, performs the steps of the data transmission method of any one of claims 1 to 23.

35. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the data transmission method of any one of claims 24 to 31.

36. A readable storage medium, characterized in that the readable storage medium stores thereon a program or instructions, which when executed by a processor, implements the data transmission method according to any one of claims 1 to 23, or the steps of the data transmission method according to any one of claims 24 to 31.