WO2022021220A1 - 一种数据传输方法及装置 - Google Patents

一种数据传输方法及装置 Download PDF

Info

Publication number
WO2022021220A1
WO2022021220A1 PCT/CN2020/105849 CN2020105849W WO2022021220A1 WO 2022021220 A1 WO2022021220 A1 WO 2022021220A1 CN 2020105849 W CN2020105849 W CN 2020105849W WO 2022021220 A1 WO2022021220 A1 WO 2022021220A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
resource
packet
configuration information
present application
Prior art date
Application number
PCT/CN2020/105849
Other languages
English (en)
French (fr)
Inventor
刘航
杨常青
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN202080004797.6A priority Critical patent/CN112640564A/zh
Priority to PCT/CN2020/105849 priority patent/WO2022021220A1/zh
Publication of WO2022021220A1 publication Critical patent/WO2022021220A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a data transmission method and apparatus.
  • the connected devices involved in the smart cockpit mainly include a cockpit domain controller (CDC) (or called a car machine) and in-car devices, wherein the in-car devices may include in-car devices (such as car speakers, car Audio and video equipment such as microphones and car screens, etc.) and non-vehicle devices (for example, mobile phones, wearable devices, etc.).
  • CDC cockpit domain controller
  • in-car devices such as car speakers, car Audio and video equipment such as microphones and car screens, etc.
  • non-vehicle devices for example, mobile phones, wearable devices, etc.
  • the CDC and in-vehicle devices can communicate wirelessly or by wire.
  • Active noise reduction services may involve a microphone array.
  • the microphone array is generally composed of several array elements, and the microphone array aggregates the data of multiple array elements into a data packet.
  • the on-board microphone array can send the aggregated data packets to the CDC for processing.
  • the present application provides a data transmission method and device, which are used to reduce the system overhead in the data transmission process.
  • the present application provides a data transmission method, the method comprising: a first device receiving at least one resource configuration information sent by a second device, where the at least one resource configuration information is used to configure a first resource and a second resource; The first device sends first data to the second device through the first resource, and sends second data to the second device through the second resource, the first data and the second device
  • the data does not contain media access control (media access control, MAC) layer header information.
  • media access control media access control
  • the first device can send the data to be sent to the second device through the first resource and the second resource configured by the second device, and none of the sent data contains packet header information. That is to say, during data encapsulation, no packet header is added to the MAC protocol data unit (protocol data unit, PDU) formed by the encapsulation, which can reduce the system overhead in the data transmission process.
  • PDU protocol data unit
  • the first resource and the second resource are semi-persistent scheduling (semi-persistent scheduling, SPS) resources.
  • the SPS resource is used for the terminal to periodically transmit data, that is, the terminal indicates time-frequency resources for multiple data transmissions through an indication message.
  • semi-static time-frequency resources are periodic in the time domain and the same in the frequency domain.
  • the time-frequency resource size ie, the resource amount of the frequency resource usually used for each data transmission is fixed.
  • the terminal sends data in the time-frequency resources configured this time.
  • the first device may send the first data and the second data to the second device through the first resource and the second resource.
  • the first data and the second data may include the following situations:
  • the first type the first data and the second data are different segments of the first data packet. That is to say, when the amount of data to be sent by the terminal is large, the terminal can segment the data (or data packets), and then send the segmented data to the network through the configured first and second resources equipment.
  • the data size of the first data packet is greater than a first threshold; or the first resource or the second resource cannot carry the first data packet.
  • the second type the first data and the second data are the same.
  • the second data is obtained by copying the first data at the MAC layer.
  • the first data and the second data respectively correspond to different hybrid automatic repeat request (HARQ) processes.
  • HARQ hybrid automatic repeat request
  • the first device may send the first data to the second device through the first resource on the first HARQ process, send the second data to the second device through the second resource on the second HARQ process, and the first data
  • the data is exactly the same as the second data, which can improve the reliability of data transmission.
  • the third type the first data and the second data are different redundant versions of the third data.
  • the first device can send data of different redundancy versions to the second device, and the second device then combines the received data, which can improve the reliability of data transmission.
  • the present application provides a data transmission method, the method includes: a second device sends at least one resource configuration information to a first device, the at least one resource configuration information is used to configure the first resource and the second resource; The second device receives the first data sent by the first device through the first resource, and receives the second data sent by the first device through the second resource, the first data and the second data Neither contains the media access control MAC layer header information.
  • the first device in the above solution may be a microphone device, and the second device may be a cockpit domain controller (cockpit domain controller, CDC).
  • cockpit domain controller cockpit domain controller
  • the second device may allocate the first resource and the second resource to the first device, and then receive the first data and the second data sent by the first device through the first resource and the second resource, and the first data And the second data does not contain packet header information, that is, during data encapsulation, no additional packet header information is added, which can reduce system overhead during data transmission.
  • the first resource and the second resource are semi-persistently scheduled SPS resources.
  • the method further includes: the second device recombines the second data and the first data to generate a first data packet; wherein the first data and all The second data is a different segment of the first data packet.
  • the second device can reassemble the data packet fragments, thus receiving complete data Bag.
  • the first way based on the time domain sequence and/or frequency domain sequence of the second resource and the first resource, or the semi-persistent scheduling SPS identifiers corresponding to the second resource and the first resource respectively sequence, recombining the second data with the first data.
  • the position of the first resource in the time domain is located before the position of the second resource in the time domain, and the first data corresponds to a high-order byte or high-order bit, and the The second data corresponds to a low-order byte or a low-order bit.
  • the second manner recombining the second data and the first data based on the pattern formed by the second resource and the first resource.
  • the third way receiving the first data and the second data within a time window, and reorganizing the first data and the second data in time sequence; the time window is based on the first data The time domain location of the resource and the second resource is determined.
  • the first data and the second data are the same, and the method further includes: delivering the second data or successfully decoded data in the first data to an upper layer, where The upper layer is the upper layer of the MAC layer.
  • the second device when the data sent by the first device to the second device are two identical data, the second device can deliver the successfully decoded data of the two identical data to the upper layer.
  • the first data and the second data are different redundant versions of the third data
  • the method further includes: according to the difference between the first data and the second data Redundant version, combined and decoded to obtain third data.
  • the present application provides a data transmission device, and the beneficial effects can be referred to the description of the first aspect and will not be repeated here.
  • the data transmission device has the function of implementing the behavior in the method example of the first aspect above.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the data transmission apparatus includes: a receiving module, configured to receive at least one resource configuration information sent by the second device, where the at least one resource configuration information is used to configure the first resource and the second resource; send a module configured to send first data to the second device through the first resource, and send second data to the second device through the second resource, the first data and the second data Neither contains the media access control MAC layer header information.
  • a receiving module configured to receive at least one resource configuration information sent by the second device, where the at least one resource configuration information is used to configure the first resource and the second resource
  • send a module configured to send first data to the second device through the first resource, and send second data to the second device through the second resource, the first data and the second data Neither contains the media access control MAC layer header information.
  • the present application provides a data transmission device, and the beneficial effects can be referred to the description of the second aspect and will not be repeated here.
  • the data transmission device has the function of implementing the behavior in the method example of the second aspect above.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • the data transmission apparatus includes: a sending module, configured to send at least one resource configuration information to the first device, where the at least one resource configuration information is used to configure the first resource and the second resource; a receiving module , used to receive the first data sent by the first device through the first resource, and receive the second data sent by the first device through the second resource, the first data and the second data are both Does not contain the media access control MAC layer header information.
  • a sending module configured to send at least one resource configuration information to the first device, where the at least one resource configuration information is used to configure the first resource and the second resource
  • a receiving module used to receive the first data sent by the first device through the first resource, and receive the second data sent by the first device through the second resource, the first data and the second data are both Does not contain the media access control MAC layer header information.
  • a data transmission apparatus is provided, and the data transmission apparatus may be the first device in the above method embodiment, or a chip provided in the first device.
  • the data transmission apparatus includes a transceiver and at least one processor, and the transceiver is configured to perform the method described in the first aspect or any one of the first aspects.
  • a data transmission apparatus in a sixth aspect, is provided, and the data transmission apparatus may be the second device in the above method embodiment, or a chip provided in the second device.
  • the data transmission device includes a transceiver and at least one processor, the transceiver is configured to perform the method described in the second aspect or any one of the second aspects, and the data transmission device performs the operations of receiving and sending messages;
  • the at least one processor invokes an instruction to execute the message processing operation performed by the data transmission device in the second aspect or the method described in any one of the second aspect.
  • a computer program product comprising: computer program code, which when executed, causes the method performed by the first device in the above aspects to be performed.
  • a computer program product comprising: computer program code, which, when executed, causes the method performed by the second device in the above aspects to be performed.
  • the present application provides a chip system, the chip system includes at least one processor and a transceiver, and the processor executes any one of the first aspect and the second aspect by running instructions.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method performed by the first device in the above aspects is implemented.
  • the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, the method performed by the second device in the above aspects is implemented.
  • FIG. 1 is a schematic structural diagram of a data segmented encapsulation PDU in the prior art
  • FIG. 2 is a schematic diagram of a communication scenario provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a data transmission method provided by an embodiment of the present application.
  • 4A provides a schematic diagram of the distribution of SPS resources according to an embodiment of the present application.
  • 4B provides a schematic diagram of a high-order byte and a low-order byte according to an embodiment of the present application
  • 4C is a schematic diagram of time-frequency distribution of an SPS resource provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of another data transmission method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a protocol stack architecture provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of another data transmission method provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a logical structure of a data transmission apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a first device according to an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a logical structure of a data transmission apparatus according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a second device according to an embodiment of the present application.
  • FIG 1 is a schematic diagram of the structure of a data segment encapsulation protocol data unit (PDU) in the prior art.
  • Figure 1 takes the radio link control (RLC) sublayer as an example, such as , for each upper layer data, the RLC layer is called RLC layer service data unit (service data unit, SDU).
  • RLC radio link control
  • SDU service data unit
  • the SDU may need to be segmented at the RLC layer. For example, if a single SDU is divided into two segments, each segment will be encapsulated by adding header information to generate multiple RLC PDUs.
  • the data (data) part in the PDU structure corresponds to the segments of different SDUs.
  • additional header information is added for different segments of the SDU.
  • segmentation indicator Segmentation Indicator
  • SI is used to indicate whether to segment the SDU, for example, 1 indicates segmentation, 0 indicates no segmentation
  • Segmentation offset Segmentation offset
  • SO is used to indicate when there is segmentation Time-sharing, at the position where the original RLC SDU is split
  • SN is used to indicate the sequence number, which will greatly increase the system overhead and make the payload contained in a single PDU relatively small.
  • an embodiment of the present application provides a data transmission method that does not add header information, and then sends data without adding header information to the receiving end, which can reduce system overhead and ensure that the payload contained in the PDU is relatively large .
  • the cockpit domain controller is referred to as the car machine.
  • CDC can communicate with other in-vehicle devices or non-vehicle devices to achieve functions including but not limited to traditional radio, music video playback, navigation broadcast, mobile phone navigation screen projection, etc.
  • CDC can also have cellular communication functions, such as third-party communication.
  • 3rd-generation, 3G fourth generation mobile communication technology (the 4th generation mobile communication technology, 4G), fifth generation mobile communication technology (the 5th generation mobile communication technology, 5G), sixth generation mobile communication technology (5G) Communication technology (the 6th generation mobile communication technology, 6G), etc., as well as the telematics function, realize the information communication between people and vehicles, vehicles and the outside world, and enhance user experience, services, and safety-related functions.
  • the master node and the slave node refer to two types of nodes that are logically functionally distinguished. Among them, the master node manages the slave nodes, has resource allocation capability or resource scheduling capability, and is responsible for allocating time-frequency resources to the slave nodes; the slave node obeys the assignment of the master node and uses the time-frequency resources allocated by the master node for communication.
  • the master node and the slave node may be different.
  • the CDC schedules the vehicle audio device
  • the CDC is the master node and the vehicle audio device is the slave node
  • the mobile phone schedules the smart wearable device, at this time, the mobile phone is the master node and the smart wearable device is the slave node.
  • the properties of nodes may change in different scenarios for the same device. For example, when the mobile phone communicates with the headset, the mobile phone is the master node and the headset is the slave node; but when the mobile phone is connected to the CDC and the mobile phone obeys the CDC scheduling, the role attribute of the mobile phone is changed to the slave node.
  • the communication domain includes a master node and at least one slave node, the at least one slave node establishes a communication connection with the master node, the master node allocates or schedules time-frequency resources for the at least one slave node, and each slave node uses the scheduled or allocated resources.
  • the time-frequency resource communicates with the master node.
  • Off-vehicle device means a device that is placed in a vehicle (eg, in a smart cockpit) and is capable of communicating or connecting with other devices in the vehicle, but is not part of the vehicle.
  • a non-vehicle device may be a terminal (terminal), a mobile station (mobile station, MS), a mobile terminal (mobile terminal), a wearable device and other devices, or devices such as chips and chip systems in these devices.
  • the non-vehicle device in this embodiment of the present application may be a mobile phone (or called a "cellular" phone), a computer with a mobile terminal, a smart vehicle, and an intelligent device related to the Internet of Vehicles (such as a vehicle-mounted device in the field of unmanned driving). ), wearable devices, etc., non-vehicle devices may also be portable, pocket-sized, hand-held, computer built-in or vehicle-mounted mobile devices.
  • the off-board equipment can also be a communication chip with a communication module.
  • the off-board device may be configured to support wireless communication, eg, the off-board device may include, or be connected to, a wireless communication module.
  • On-board equipment also known as on-board unit (OBU) refers to equipment that is integrated or installed in or on a vehicle (e.g. in a smart cockpit) and is part of the vehicle.
  • the vehicle-mounted terminal may refer to a device that is factory-installed on the vehicle by the vehicle manufacturer before the vehicle leaves the factory. For example: car microphone, car audio, car screen, etc.
  • Microphone also known as “microphone”, “microphone” or “microphone” can be used to convert sound signals into electrical signals.
  • the user's voice can be collected by the microphone, and then the user's voice can be converted into an electrical signal, which can then be sent to the CDC or other in-vehicle devices via wired and/or wireless means.
  • at least one microphone may be arranged in the vehicle.
  • two or more microphones may be installed in the vehicle, and in addition to collecting sound signals, functions such as noise reduction and directional recording may also be implemented.
  • Speakers also known as “speakers”, “horns”, etc., are used to convert audio electrical signals into sound signals for playback. Users can listen to music or answer hands-free calls through the speaker. The speaker can also cooperate with the microphone to achieve noise reduction.
  • a screen, or "display screen” can be used to display images, videos, etc.
  • the screen may include a display panel.
  • the display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode, or an active-matrix organic light-emitting diode (active-matrix organic light).
  • one or more screens may be provided in the vehicle.
  • the screen may also be a touch screen, which can be used to obtain a user's touch operation.
  • the above-mentioned in-vehicle device may be configured to support wireless communication, for example, the above-mentioned in-vehicle device may include a wireless communication module (or referred to as a wireless transceiver, etc.), or be connected to a wireless communication module.
  • a wireless communication module or referred to as a wireless transceiver, etc.
  • a terminal device may be referred to as a terminal for short, also referred to as user equipment (user equipment, UE), which is a device with a wireless transceiver function.
  • Terminal equipment can be deployed on land, including indoor or outdoor, handheld or vehicle; can also be deployed on water (such as ships, etc.); can also be deployed in the air (such as aircraft, drones, balloons and satellites, etc.).
  • the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal device in industrial control, a wireless terminal device in unmanned driving, and a wireless terminal device in telemedicine.
  • Terminal devices can also be stationary or mobile. This embodiment of the present application does not limit this.
  • the apparatus for implementing the function of the terminal may be a terminal device; it may also be an apparatus capable of supporting the terminal device to implement the function, such as a chip system, and the apparatus may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for realizing the functions of the terminal device as the terminal device as an example.
  • the terminal device in this application may be an in-vehicle device and/or a non-vehicle device. It can be understood that, in an implementation manner, the terminal device may be a CDC or other domain controller.
  • a network device may be an access network device, and an access network device may also be called a radio access network (RAN) device, which is a device that provides wireless communication functions for terminal devices.
  • Access network equipment includes, but is not limited to, the next generation base station (generation nodeB, gNB), evolved node B (evolved node B, eNB), baseband unit (baseband unit, BBU) in 5G, transmitting and receiving points (transmitting and receiving), for example, but not limited to: point, TRP), transmitting point (transmitting point, TP), the base station in the future mobile communication system or the access point in the WiFi system, etc.
  • the access network device may also be a wireless controller, centralized unit (centralized unit, CU), and/or distributed unit (distributed unit, DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or a network
  • the device may be a relay station, a vehicle-mounted device, and a network device in a future evolved PLMN network, and the like.
  • a terminal device can communicate with multiple access network devices of different technologies. For example, a terminal device can communicate with an access network device that supports long term evolution (LTE), and can also communicate with an access network device that supports 5G. It can also communicate with LTE-enabled access network devices and 5G-enabled access network devices at the same time.
  • LTE long term evolution
  • 5G 5th Generationан ⁇
  • the apparatus for implementing the function of the network device may be a network device; it may also be an apparatus capable of supporting the network device to implement the function, such as a chip system, and the apparatus may be installed in the network device.
  • the technical solutions provided by the embodiments of the present application are described by taking the device for realizing the function of the network device being a network device as an example.
  • the network device in this application may be a CDC.
  • LTE long term evolution
  • WiMAX Worldwide interoperability for microwave access
  • the embodiments of the present application can be applied to different data transmission scenarios, such as the vehicle-mounted active noise reduction service in the smart cockpit scenario.
  • In-vehicle active noise reduction is to neutralize engine noise, road noise, wind noise and other noises through the in-vehicle speakers to emit reversed-phase acoustic signals, so as to achieve a global or regional static field in the car, and achieve the purpose of eliminating or reducing in-vehicle noise.
  • multiple on-board microphones need to collect in-vehicle noise signals, transmit them to the processor unit to generate anti-phase noise signals, and then transmit the anti-phase noise signals to multiple on-board speakers for playback respectively, so as to achieve the effect of active noise reduction at the cockpit receiving end .
  • the noise collection, processing, transmission, generation of the anti-phase noise signal, transmission of the anti-phase noise signal to the car speakers and playing at the cockpit receiving end The delay needs to be smaller than the delay of the real noise transmitted to the cockpit receiving end for playback, and the transmission of the noise signal and the inverted noise signal needs to meet high reliability.
  • the communication scenario mainly includes the communication between the CDC and in-vehicle devices (eg, in-vehicle devices such as microphones, speakers, screens, etc.) or non-vehicle devices (eg, user's mobile phone, wearable device).
  • in-vehicle devices eg, in-vehicle devices such as microphones, speakers, screens, etc.
  • non-vehicle devices eg, user's mobile phone, wearable device.
  • the CDC and the in-vehicle device can be installed inside the vehicle, and the non-vehicle device can be installed in the vehicle, or can enter or leave the vehicle as the user moves.
  • a flowchart of a data transmission method provided by an embodiment of the present application, referring to FIG. 3 , the method may include the following steps:
  • S301 The second device sends at least one resource configuration information to the first device.
  • the first device receives at least one resource configuration information sent by the second device.
  • At least one resource configuration information can be used to configure the first resource and the second resource.
  • the first device and the second device may transmit data through the first resource and the second resource.
  • the first resource and the second resource are semi-persistent scheduling (semi-persistent scheduling, SPS) resources.
  • the first resource and the second resource may be included in one resource configuration information or multiple resource configuration information.
  • the first resource and/or the second resource includes at least one time-frequency resource unit (unit).
  • resource blocks RBs
  • resource elements REs
  • the resource configuration information may be radio resource control signaling (radio resource control, RRC); or it may be downlink control indicator (DCI); wherein the RRC signaling includes system information (System information), such as , the master system information block (master information block, MIB) or system information block (system information block, SIB).
  • RRC radio resource control
  • DCI downlink control indicator
  • System information system information
  • MIB master system information block
  • SIB system information block
  • the first resource may be used to transmit the first data between the first device and the second device, specifically, the first device may send the first data to the second device through the first resource, or the second device may The first data is sent to the first device through the first resource.
  • the second device when the second device is the master node device and the first device is the slave node device, the second device can configure the first resource for the first device, and the first device can use the first resource configured by the second device and the first resource.
  • the two devices communicate.
  • the first device is a terminal device
  • the second device is a network device
  • the first device is a microphone
  • the second device is a CDC as an example for description.
  • the microphones include two types of microphones. Due to the different types of microphones, the amount of data generated is also different. Therefore, for data with different amounts of data, data transmission methods may also be different. The following describes the data transmission between the two different types of microphones and the CDC.
  • the first form a single microphone.
  • the size of the data volume is relatively small. That is to say, the size of the data amount of a single microphone is smaller than a set threshold (hereinafter referred to as "the first threshold"), or a single resource can carry the size of the data amount of a single microphone.
  • the first threshold a set threshold
  • the second form Array type microphones.
  • the so-called array type microphone is an array composed of multiple microphones. Therefore, the data generated by the array type microphone can be regarded as one data, and the data can include the sound signals collected by the multiple microphones.
  • a microphone array includes multiple array elements, and the array data is formed by the aggregation of multiple array element data. Therefore, the amount of data is relatively large. That is, when the size of the data volume is greater than the first threshold, or a single resource cannot carry the size of the data volume, in this embodiment of the present application, the second device may be configured with at least one resource configuration information, that is, the second device may be configured with at least one resource, such as the first resource. The first resource and the second resource send the data collected by the microphone array to the CDC through the first resource and the second resource.
  • the first device may report first information to the second device (CDC), where the first information includes device type information, service type information, and data in the array. At least one item of information such as the number of array elements, the sampling rate of each array element, the sampling period, and quantization bits.
  • the device type information may include a microphone, a speaker, an array form, a single microphone form, and the like. After receiving the first information sent by the microphone, the CDC may determine the size of the resource to be configured according to the first information.
  • the parameter information included in the above-mentioned first information is introduced as follows:
  • the number of array elements in the array may be the number of array elements in the working state or working mode in the array. It is understandable that the number of working array elements in the array can be dynamically adjusted according to business requirements.
  • Sampling rate also known as sampling frequency or sampling speed, defines the number of samples per second extracted from continuous signals to form discrete signals, which is expressed in Hertz (Hz).
  • sampling period is the reciprocal of the sampling frequency, which can also be called the sampling time, which is the time interval between sampling.
  • Quantization refers to the process of approximating a continuous value of a signal (or a large number of possible discrete values) into a finite number of (or less) discrete values.
  • quantization is mainly used in the conversion from continuous signals to digital signals. Continuous signals become discrete signals after sampling, and discrete signals become digital signals after quantization. The number of binary digits of the sample value determines the quantization bit of the sample value, also known as quantization precision or quantization bit width.
  • Service type information which can be used to indicate the type of service.
  • service type information can be an identifier.
  • an application identifier (AID) 1 can be used to identify an active noise reduction service; AID2 can be used to identify streaming media Rearview mirror business.
  • reporting the sampling rate or sampling period is helpful for CDC to understand the period of accurate arrival of sampled data in a microphone device (for example, a microphone array device); reporting the number of array elements and quantization bits is helpful for CDC to understand the single-shot data of the microphone device.
  • the size of the sampled data; reporting the service type information helps the CDC to understand the service type on the microphone device, so as to configure appropriate resources for it.
  • the microphone array device reports to the CDC that its current data transmission uses K (K is a positive integer) array elements to collect data, it is assumed that the signal collected by a single array element is quantized using Xbit, then the CDC at this time It can be determined that the total data volume of the single data sampling of the microphone array is K*Xbit, so as to determine to allocate an appropriate resource to the microphone device, and send at least one resource configuration information to it.
  • K is a positive integer
  • the sampling rate, sampling period, and quantization bits of the array elements in the microphone array are generally the same.
  • the microphone in order to save signaling overhead, can report the same sampling rate, sampling period, and quantization bits when reporting the first information, instead of reporting the sampling rate, sampling period, and quantization bit of each array element. bits.
  • the second device When the first device needs to send data to the second device, the second device needs to schedule resources for the first device.
  • the second device may receive information sent by the first device about the service to which the data to be sent belongs, such as type information.
  • the second device allocates resources from the first resource pool to the first device only when it is determined that the data to be sent by the first device is data of the first service. For example, assuming that the service type information sent by the first device to the second device is AID1 to indicate that it is an active noise reduction service, the second device allocates resources from the first resource pool to the first device.
  • the first resource pool includes several time-frequency resource units.
  • the second device may configure different resource pools for different services.
  • the active noise reduction service corresponds to the first resource pool
  • the streaming media service corresponds to the second resource pool
  • the first resource pool and the second resource pool may be the same or different, which is not limited in this application.
  • step S301 is an optional step. That is to say, if the CDC sends downlink data to the speaker, the CDC may not send resource configuration information to the speaker.
  • the first device sends the first data to the second device through the first resource, and sends the second data to the second device through the second resource.
  • the second device receives the first data sent by the first device through the first resource, and receives the second data sent by the first device through the second resource.
  • neither the first data nor the second data includes media access control (media access control, MAC) layer header information.
  • media access control media access control, MAC
  • the MAC layer directly "transmits" the data to be sent (for example, the first data packet) to the physical layer.
  • transparent transmission is also called transparent transmission, that is, when at least one service data unit SDU is processed by a certain protocol layer, the protocol data unit PDU generated by the protocol layer includes the at least one SDU, However, the corresponding packet header information is not added, and the SDU is not segmented.
  • the generated PDU is equal to the SDU, that is, it is approximated that the protocol layer "does not” process the SDU, which is similar to transparent, so it is called transparent transmission.
  • the transparent transmission includes encrypting the data, for example, an equal-length encryption technology may be used, so that the length of the encrypted data is the same as the length of the data before the encryption.
  • the MAC layer "transparently transmits" the data to be sent by the first device to the physical layer means that the MAC encapsulates the data in a MAC PDU, and the MAC PDU does not contain header information.
  • the data is not segmented.
  • the data may be packets.
  • the data may be MAC SDUs.
  • the second device may configure multiple resources for the first device, such as the first resource and the second resource, and then the first device The data to be sent can be divided, and the data to be divided can be sent to the second device through the configured multi-channel resources.
  • the data to be sent by the first device is a first data packet
  • the data link layer of the first device may segment the first data packet, for example, into two pieces of data, which are recorded as are the first data and the second data.
  • the first device may send the segmented data to the second device through the multiplexed resources respectively.
  • the first device can send the first data to the second device through the first resource, and can send the second data to the second device through the second resource. That is to say, if the amount of data is relatively large, the data can be segmented at the data link layer first, and then the segmented data can be encapsulated. Multiple PDUs generated by encapsulation do not contain packet header information.
  • the data link layer includes a MAC layer, and multiple MAC PDUs that encapsulate and generate the segmented data can be performed at the MAC layer, and none of the MAC PDUs includes packet header information.
  • the data to be sent by the first device is a first data packet
  • the second device allocates the first resource and the second resource to the first device.
  • the MAC layer of the first device "transparently transmits" the first data packet to the physical layer, and the physical layer can divide the first data packet into multiple coded blocks (Coded Blocks), for example, into two encoding blocks, denoted as first data and second data respectively.
  • the first data is carried on the first resource
  • the second data is carried on the second resource.
  • the first coding block and the second coding block may adopt different coding parameters; for example, coding rate, coding manner, and the like.
  • the second device may also configure a third resource for the first device, where the third resource includes the first resource and the second resource.
  • the first resource and the second resource are determined by the physical layer of the first device itself.
  • the physical layer of the first device may determine the first resource and the second resource according to the size of the split first data and the second data (for example, including the size of the first resource and the second resource, or the The relative position of the second resource in the third resource).
  • the physical layer usually performs channel encoding and decoding, which is beneficial to improve the reliability of data transmission.
  • S303 The second device reassembles the second data and the first data to generate a first data packet.
  • the first data and the second data are different segments of the first data packet. Therefore, after the first device sends the different segments of the first data packet to the second device through the first resource and the second resource, the second device may receive the different segments of the first data packet, and perform processing on the different segments. Reassembly is performed to obtain a complete first data packet.
  • an implementation manner of the reorganization is concatenation. Therefore, as a possible implementation manner, the first data and the second data may be concatenated. It can be understood that, considering that the first data and the second data do not carry packet header information, the key to the reorganization is to determine the relative sequence of the first data and the second data, and directly splicing to generate the first data packet.
  • the second device Since the first data and the second data sent by the first device do not contain the MAC layer header information, when the second device performs reassembly, it needs to know which data on the resources can be reassembled to generate the first data packet, and needs to know these The sequence of the data can successfully reassemble the received data into the first data packet.
  • the second device may splicing the second data and the first data based on the time domain sequence of the first resource and the second resource.
  • the second device may configure the first device with semi-persistent scheduling resources that have a certain priority in the time domain.
  • the second device configures a first resource and a second resource for the first device, where the first resource and the second resource are both semi-persistently scheduled resources.
  • the first resource and the second resource are resources that appear periodically, because the upper-layer service (ie, the first data packet) may appear periodically.
  • the first resource and the second resource have a certain sequence in the time domain, and the position of the first resource in the time domain is located in the time domain of the second resource. position before. That is, the position where at least one symbol (or subframe, frame) exists in the first resource precedes all symbols (or subframe, frame) in the second resource.
  • the first data generated by the first data packet segment corresponds to the high-order byte (Most Significant Byte) or the high-order bit (Most Significant Bit) of the first data packet, that is, the first data is the first data packet of the first data packet. segment; the second data is the low-order byte (Least Significant Byte) or the low-order bit (Least Significant Bit) of the first data packet, that is, the second data is the second segment of the first data packet.
  • FIG. 4B a schematic diagram of a high-order byte and a low-order byte is provided in an embodiment of the present application.
  • the protocol may stipulate that the first segment is sent on the resource located at the front in the time domain, and the second segment is sent on the resource located at the back in the time domain. Alternatively, the protocol can also stipulate that the second segment is sent on the resource in the earlier time domain. As long as the two ends of the sending and receiving end have the same understanding, the first data packet can also be reassembled according to this rule, which is not limited in this application.
  • the CDC can obtain the first data on the first resource, obtain the second segment on the second resource, and use the relative relationship between the first resource and the second resource in the time domain to determine that the first data is the first data
  • the first segment of the data packet, and the second data is the second segment of the first data packet, so that the first data packet is obtained by splicing.
  • the second device may perform splicing according to the sequence of the first resource and the second resource in the time domain.
  • the first resource is located before the second resource, then during splicing, the first data corresponding to the first resource may be before the second data corresponding to the second resource.
  • the receiving end may be a time window at the receiving end, and the receiving end only reorganizes the data on the first resource and the data on the second resource within the time window.
  • the second device may splicing the second data and the first data based on the frequency domain sequence of the second resource and the first resource.
  • the second device may configure the first device with semi-persistent scheduling resources that have a certain priority in the frequency domain.
  • the second device configures a first resource and a second resource for the first device, wherein the first resource and the second resource are both semi-persistently scheduled resources.
  • the first resource and the second resource are resources that appear periodically, because the upper layer service (that is, the first data packet) may appear periodically.
  • the first resource and the second resource have a certain sequence in the frequency domain, and the position of the first resource in the frequency domain is located in the frequency domain of the second resource. position before.
  • the first resource corresponds to 5900-5905 Hz
  • the second resource corresponds to 5905-5910 Hz. That is, there is at least one RE in the first resource, or the position of the subcarrier is before the positions of all REs or subcarriers in the second resource.
  • the first data generated by the first data packet segment corresponds to the high-order byte (Most Significant Byte) or the high-order bit (Most Significant Bit) of the first data packet, that is, the first data is the first data packet of the first data packet.
  • the second data is the low-order byte (Least Significant Byte) or the low-order bit (Least Significant Bit) of the first data packet, that is, the second data is the second segment of the first data packet.
  • the protocol can stipulate that the first segment is sent on the resource located at the front of the frequency domain, and the second segment is sent on the resource located at the back of the frequency domain;
  • the first data packet can also be reassembled according to this rule, which is not limited in this application.
  • the CDC can obtain the first data on the first resource, obtain the second segment on the second resource, and use the relative relationship between the first resource and the second resource in the frequency domain to determine that the first data is the first data
  • the first segment of the data packet, and the second data is the second segment of the first data packet, so that the first data packet is obtained by splicing.
  • the second device may perform splicing according to the sequence of the first resource and the second resource in the frequency domain.
  • the first resource is located before the second resource, then during splicing, the first data corresponding to the first resource may be before the second data corresponding to the second resource.
  • the second type the second device is the SPS resource configured by the first device, and there may be an SPS identifier (for example, SPS ID) corresponding to the SPS resource, that is, the first resource corresponds to SPS ID1, and the second resource corresponds to SPS ID2.
  • SPS ID an SPS identifier
  • the first data generated by the first data packet segment corresponds to the high-order byte (Most Significant Byte) or the high-order bit (Most Significant Bit) of the first data packet, that is, the first data is the first part of the first data packet. segment; the second data is the low-order byte (Least Significant Byte) or the low-order bit (Least Significant Bit) of the first data packet, that is, the second data is the second segment of the first data packet.
  • the protocol stipulates that data is sent in the order of SPS IDs (assuming that the order of SPS IDs is: SPS ID1 first, SPS ID2 last), that is, at the sender, the first segment is sent on the first resource, and the first segment is sent on the first resource.
  • the second segment is sent on the second resource, then at the receiving end, the CDC can obtain the first data on the first resource, obtain the second segment on the second resource, and use the corresponding data of the first resource and the second resource.
  • the relative sequence relationship of the SPS ID determines that the first data is the first segment of the first data packet, and the second data is the second segment of the first data packet, so that the first data packet is obtained by splicing.
  • the second device can perform splicing according to the sequence of the SPS IDs corresponding to the first resource and the second resource.
  • the protocol can also stipulate that the second segment is sent on the resource with the SPS ID first.
  • the first data packet can also be reassembled according to this rule, which is not limited in this application.
  • For the reorganization process refer to the above process, which will not be repeated here.
  • the third type the second device may recombine the second data and the first data based on the pattern formed by the first resource and the second resource.
  • resource configurations will present different resource shapes corresponding to the time domain and the frequency two-dimensional domain, which are also called resource patterns.
  • the physical layer can segment the first data packet into multiple coded blocks (Coded Blocks), for example, into two coded blocks, which are respectively recorded as the first data and the second data.
  • the first data that the first data packet segment generates corresponds to the high-order byte (Most Significant Byte) or the high-order bit (Most Significant Bit) of the first data packet, that is, the first data is the first segment of the first data packet;
  • the second data is the low-order byte (Least Significant Byte) or the low-order bit (Least Significant Bit) of the first data packet, that is, the second data is the second segment of the first data packet.
  • the first device may divide the third resource into the first resource and the second resource.
  • the first resource is used to carry the first data
  • the second resource is used to carry the second data.
  • the first resource and/or the second resource includes at least one time-frequency resource unit (unit), for example, may include RB or RE.
  • unit may include RB or RE.
  • the first resource and the second resource include a total of 4 time-frequency resource units, for example, denoted as X1, X2, X3 respectively , X4.
  • the order in which the data of the sender is placed on the time-frequency resources included in the pattern may be agreed in the protocol.
  • the first data is carried on X1 and X3, and the second data is carried on X2 and X4.
  • the first data can be obtained from the resources corresponding to X1 and X3, and the second data can be obtained from the resources corresponding to X2 and X4, and the first data can be determined as the first data packet.
  • the first segment of the first data packet, and the second data is the second segment of the first data packet, so that the first data packet is obtained by splicing.
  • the sending end device can send segmented data without packet header information to the receiving end device through multiple resources, so that the receiving end device can splicing the received segmented data to obtain a complete data packet , and then deliver the complete packet to the upper layer.
  • the problem of large system overhead caused by adding packet header information in the process of data encapsulation can be solved.
  • the first device may add header information when encapsulating the segmented data, that is, the encapsulated MAC PDU includes header information.
  • a sequence number may be added to the packet header information, and the sequence number is used to identify the sequence of data, that is, the packet header information only includes the sequence number.
  • the second device may reorganize the first data and the second data according to the sorting numbers contained in the first data and the second data respectively. Exemplarily, assuming that the sequence number in the packet header information of the first data is 0, and the sequence number in the packet header information of the second data is 1, the second device can splicing the data with sequence numbers of 0 and 1. .
  • the sequence number added to the packet header information can be up to 3 bits, that is, the packet header information of the data is relatively small, which can appropriately reduce the system overhead.
  • a data transmission method provided by an embodiment of the present application, referring to FIG. 5, the method may include the following steps:
  • S501 The second device sends at least one resource configuration information to the first device.
  • the first device receives at least one resource configuration information sent by the second device.
  • At least one resource configuration information can be used to configure the first resource and the second resource. It should be understood that this step S501 is the same as step S301 , and for details, reference may be made to the description in the embodiment of FIG. 3 , which will not be repeated here.
  • the resource configuration information may include second information, where the second information is used to indicate that the second resource is an SPS resource for repeated transmission.
  • the first device sends the first data to the second device through the first resource, and sends the second data to the second device through the second resource.
  • neither the first data nor the second data includes media access control MAC layer packet header information.
  • the first data and the second data here are the same, and the second data is obtained by copying the first data at the MAC layer, and the first data and the second data respectively correspond to different hybrid automatic retransmission requests (hybrid automatic retransmission requests). repeat request, HARQ) process. That is to say, the first device can copy the same first data to be sent, send the first data through the first SPS resource, and send the copied second data through the second SPS resource, so that the first device can Two copies of the same data are sent to the second device, and the two copies of data are sent on different HARQ processes.
  • hybrid automatic retransmission requests hybrid automatic retransmission requests
  • HARQ repeat request
  • the network device may configure the terminal device (eg, a microphone) to perform repeated data transmission through signaling.
  • the terminal device eg, a microphone
  • the MAC layer is configured or activated through RRC signaling to perform repeated data transmission; or the MAC layer is configured or activated through DCI to perform repeated data transmission.
  • the network device here refers to the second device, and the terminal device refers to the first device.
  • S503 The second device delivers the successfully decoded data in the second data or the first data to the upper layer.
  • the upper layer is the upper layer of the MAC layer.
  • the upper layer of the MAC layer may be any one of the link control layer and the network layer.
  • the protocol stack may include a physical layer, a data link layer, and a network layer.
  • the data link layer may include: a link control layer and a MAC layer (or called a medium access layer).
  • the network layer is located above the data link layer and is responsible for routing selection, thereby determining the path between two nodes.
  • the network layer may also perform flow control.
  • the link control layer defines different transmission modes to meet the transmission requirements of different services. For example, it can be divided into Acknowledged Mode and Unacknowledged Mode according to whether the receiving end needs to confirm the sent data.
  • the link control layer can also perform functions such as duplicate packet detection, sorting, data packet segmentation, and reassembly.
  • the MAC layer implements functions such as resource management, scheduling, access control, and data encapsulation with different priorities.
  • a transmission medium is used to provide a physical connection for the data link layer, so as to realize the transparent transmission of the bit stream.
  • the physical layer performs channel coding or decoding to ensure the reliability of data transmission.
  • the link control layer may contain adaptation layer functions, that is, may be used to provide transport between different networks and/or transport protocols Adaptation function. For example, receive a data packet from the bottom layer (the protocol layer below the link control layer), distinguish the protocol type of the upper network layer (the protocol layer above the link control layer, that is, the network layer) to which the data packet belongs, and convert the The data packet is submitted (or passed) to the corresponding upper-layer protocol for processing.
  • the adaptation function is a logical function layer, and in implementation, it may also be included in the network layer, which is not limited in this application.
  • the second device can receive the two copies of the same data, and the second device can submit the first data or the successfully decoded data in the second data to The upper layer of the MAC layer. For example, if the first data is successfully decoded first, the second device can submit the first data to the upper layer of the MAC layer; or the second data is successfully decoded before the first data, then the second device can submit the second data to the upper layer of the MAC layer.
  • the data that is not successfully decoded may be discarded.
  • the first data is successfully decoded data
  • the second data is not successfully decoded
  • the second device may discard the second data.
  • the protocol layer of the transmitting end may add a cyclic redundancy check (cyclic redundancy check, CRC) check code to the transmission data, which is used for the protocol layer corresponding to the receiving end to verify the data.
  • CRC cyclic redundancy check
  • the algorithm and parameters used in the CRC check operation may be pre-agreed by the master node and the slave node or defined in the agreement.
  • the CRC check code can be added at the end of the transmitted data.
  • the sender device can send data without header information, and the receiver device can receive two copies of the same data in two different HARQ processes, which not only reduces system overhead, but also improves data transmission. reliability.
  • a data transmission method provided by an embodiment of the present application, referring to FIG. 7, the method may include the following steps:
  • S701 The second device sends at least one resource configuration information to the first device.
  • the first device receives at least one resource configuration information sent by the second device.
  • At least one resource configuration information can be used to configure the first resource and the second resource. It should be understood that this step S701 is the same as step S301 , and for details, reference may be made to the description in the embodiment of FIG. 3 , which will not be repeated here.
  • the first device sends the first data to the second device through the first resource, and sends the second data to the second device through the second resource.
  • neither the first data nor the second data includes the media access control MAC layer packet header information.
  • the first data and the second data are different redundant versions of the third data.
  • the third data may be data packets.
  • the first data and the second data are different redundancy versions of the third data
  • the first device may send data of different redundancy versions to the second device.
  • data with a redundancy version of 0 may be sent through the first SPS resource
  • data with a redundancy version of 1 may be sent through the second SPS resource, so that the receiver can receive data with different redundancy versions.
  • sending data of different redundancy versions at the transmitting end can enable the receiving end to perform soft combining, thereby obtaining better results.
  • different redundancy versions correspond to different coded bit sets respectively, but contain the same information, and the receiving end will combine the data of different redundancy versions.
  • S703 Combine and decode to obtain third data according to different redundancy versions of the first data and the second data.
  • the second device After receiving the data of different redundancy versions sent by the first device, the second device can combine and decode the first data and the second data according to the different redundancy versions of the first data and the second data, and then obtain a third data.
  • the different redundant versions of the first data and the second data may be combined according to the sequence or pattern of the SPS IDs.
  • the sequence or pattern of the SPS IDs please refer to the description about the sequence and pattern of the SPS IDs in the embodiment of FIG. 3 , which will not be repeated here.
  • the sending end device can send data without header information, and the receiving end device can combine data of two different redundancy versions, which can reduce system overhead and improve the reliability of data transmission.
  • the first user equipment may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division methods may be used in actual implementation.
  • the embodiments of the present application provide a data transmission apparatus.
  • the data transmission device can be applied to the first device, as shown in FIG. 8 , the data transmission device 800 includes a receiving module 801 , sending module 802 .
  • the apparatus 800 is configured to implement the function of the first device in the above method.
  • the apparatus may be a microphone device, or may be a device in a microphone device, such as a chip system.
  • the receiving module 801 is configured to receive at least one resource configuration information sent by the second device, where the at least one resource configuration information is used to configure the first resource and the second resource; the sending module 802 is configured to pass the first resource Send the first data to the second device, and send the second data to the second device through the second resource, the first data and the second data do not contain a media access control MAC layer header information.
  • the first resource and the second resource are semi-persistently scheduled SPS resources.
  • the first data and the second data are different segments of the first data packet.
  • the data size of the first data packet is greater than a first threshold; or the first resource or the second resource cannot carry the first data packet.
  • the first data and the second data are the same.
  • the second data is obtained by copying the first data at the MAC layer.
  • the first data and the second data respectively correspond to different HARQ processes of HARQ.
  • the first data and the second data are different redundant versions of the third data.
  • the receiving module 801 may be a communication interface, a receiver, a transceiver circuit, and the like.
  • the sending module 802 may be a communication interface, a transmitter, a transceiver circuit, and the like.
  • the communication interface is a general term, which may include one or more interfaces.
  • the data transmission apparatus 800 involved in the embodiment of the present application may be as shown in FIG. 9 .
  • a data transmission apparatus 900 provided by an embodiment of the present application is shown.
  • the data transmission apparatus may be the first device.
  • the data transmission apparatus 900 may include a receiver 901 , a transmitter 902 , a processor 903 , and a memory 904 .
  • the memory 904 stores instructions or programs, and the processor 903 is configured to execute the instructions or programs stored in the memory 904 .
  • the receiver 901 is configured to perform the operations performed by the receiving module 801 in the above embodiments.
  • the transmitter 902 is configured to perform the operations performed by the sending module 802 in the above embodiments.
  • the data transmission apparatus 900 or the first device 900 may correspond to the first device in the embodiments shown in FIG. 3 , FIG. 5 , and FIG. 7 , and the data transmission apparatus 900 or the first device 900
  • the operations and/or functions of the respective modules in FIG. 3 , FIG. 5 , and FIG. 7 respectively implement the corresponding processes in the embodiments shown in FIG. 3 , FIG. 5 , and are not repeated here for brevity.
  • an embodiment of the present application further provides a schematic diagram of a logical structure of a data transmission apparatus.
  • the data transmission apparatus 1000 includes a sending module 1001 and a receiving module 1002 .
  • the apparatus 1000 is configured to implement the function of the second device in the above method.
  • the device may be a CDC device, or may be a device in a CDC device, such as a system-on-a-chip.
  • the sending module 1001 is configured to send at least one resource configuration information to the first device, where the at least one resource configuration information is used to configure the first resource and the second resource;
  • a receiving module 1002 configured to receive first data sent by the first device through a first resource, and receive second data sent by the first device through the second resource, the first data and the first data Both data do not contain the media access control MAC layer packet header information.
  • the first resource and the second resource are semi-persistently scheduled SPS resources.
  • the apparatus further includes: a processing module 1003; the processing module 1003 is configured to recombine the second data and the first data to generate a first data packet; wherein, The first data and the second data are different segments of the first data packet.
  • the processing module 1003 is specifically configured to recombine the second data and the first data as follows: based on the time domain of the second resource and the first resource The second data and the first data are recombined according to the sequence and/or the sequence of the frequency domain, or the semi-persistent scheduling SPS identification sequence respectively corresponding to the second resource and the first resource.
  • the position of the first resource in the time domain is located before the position of the second resource in the time domain, and the first data corresponds to a high-order byte or high-order bit, and the The second data corresponds to a low-order byte or a low-order bit.
  • the processing module 1003 is specifically configured to reorganize the second data and the first data in the following manner, including: based on the second resource and the first resource composition pattern, recombining the second data with the first data.
  • the processing module 1003 is specifically configured to recombine the second data and the first data as follows: receiving the first data and the second data within a time window data, and reorganize the first data and the second data in time sequence; the time window is determined based on the time domain positions of the first resource and the second resource.
  • the first data and the second data are the same, and the processing unit is further configured to: deliver the second data or the successfully decoded data in the first data to an upper layer , the upper layer is the upper layer of the MAC layer.
  • the first data and the second data are different redundant versions of the third data
  • the processing module 1003 is further configured to: according to the first data and the second data The different redundant versions of the data are combined and decoded to obtain the third data.
  • the sending module 1001 may be a communication interface, a receiver, a transceiver circuit, and the like.
  • the receiving module 1002 may be a communication interface, a transmitter, a transceiver circuit, and the like.
  • the communication interface is a general term, which may include one or more interfaces.
  • the data transmission apparatus 1000 involved in this embodiment of the present application may be as shown in FIG. 11 .
  • a data transmission apparatus 1100 is provided in an embodiment of the present application.
  • the data transmission apparatus may be a second device, and the data transmission apparatus 1100 may include a transmitter 1101 , a receiver 1102 , a processor 1103 , and a memory 1104 .
  • the memory 1104 stores instructions or programs, and the processor 1103 is configured to execute the instructions or programs stored in the memory 1104 .
  • the transmitter 1101 is configured to perform the operations performed by the sending module 1001 in the above embodiments.
  • the receiver 1102 is configured to perform the operations performed by the receiving module 1002 in the above embodiments.
  • the data transmission apparatus 1000 or the data transmission apparatus 1100 may correspond to the second device in the embodiments shown in FIG. 3 , FIG. 5 , and FIG. 7 , and the data transmission apparatus 1000 or the data transmission apparatus 1100
  • the operations and/or functions of the respective modules in FIG. 3 , FIG. 5 , and FIG. 7 respectively implement the corresponding processes in the embodiments shown in FIG. 3 , FIG. 5 , and are not repeated here for brevity.
  • processors mentioned in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits ( application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the memory mentioned in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SCRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components
  • the memory storage module
  • memory described herein is intended to include, but not be limited to, these and any other suitable types of memory.
  • the embodiments of the present application further provide a computer-readable storage medium on which a computer program is stored.
  • the program is executed by a processor, the computer is made to execute the above method embodiments and method implementations.
  • the present application further provides a computer program product, which, when invoked and executed by a computer, can enable a computer to implement any one of the foregoing method embodiments and any possible implementation manners of the method embodiments. in the operation performed by the first device or the second device.
  • the present application further provides a chip or a chip system, where the chip may include a processor.
  • the chip may also include a memory (or a storage module) and/or a transceiver (or a communication module), or the chip may be coupled with a memory (or a storage module) and/or a transceiver (or a communication module), wherein the transceiver (or or communication module) can be used to support the chip to perform wired and/or wireless communication, the memory (or storage module) can be used to store a program, and the processor can call the program to implement any one of the above method embodiments and method embodiments.
  • the chip system may include the above chips, or may include the above chips and other discrete devices, such as memories (or storage modules) and/or transceivers (or communication modules).
  • the present application further provides a communication system, which can be used to implement the above-mentioned method embodiments and any possible implementation manners of the above-mentioned method embodiments, executed by a first device and a second device. operation.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the apparatus embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种数据传输方法及装置，应用于通信领域，例如智能座舱域，也可以应用于自动驾驶领域、智能驾驶等领域。该方法包括：第一设备接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；所述第一设备通过所述第一资源向所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。通过本申请的方法，能够降低在数据传输过程中的***开销。该方法可以应用于车联网，如车辆外联V2X、车间通信长期演进技术LTE-V、车辆-车辆V2V等。

Description

一种数据传输方法及装置 技术领域
本申请涉及通信技术领域，尤其涉及一种数据传输方法及装置。
背景技术
车辆在人们的日常生活中发挥着越来越重要的作用。随着智能座舱技术的不断发展，车辆不仅是运输工具，更是人们生活的空间之一。人们期望智能座舱能为人们提供更加丰富的娱乐、音频、视频和办公体验。
目前，智能座舱中涉及到的连接设备主要有座舱域控制器(cockpit domain controller，CDC)(或称为车机)和车内设备，其中，车内设备可包括车载设备(例如车载扬声器、车载麦克等音视频设备以及车载屏幕等)和非车载设备(例如，手机，可穿戴设备等)。CDC与车内设备可通过无线或者有线的方式进行通信。
在座舱环境下存在丰富的业务类型，比如主动降噪业务。主动降噪业务可能涉及麦克风阵列，麦克风阵列一般由若干阵元组成，麦克风阵列将多个阵元的数据汇聚成一个数据包。车载麦克风阵列可以将汇聚得到的数据包发送给CDC进行处理。
一般的，在该过程中，如果数据的数据量比较大时，可能需要对数据进行切分，然后对切分后的数据添加额外的包头信息，例如分段偏移(Segmentation offset)，从而使得接收端能够进行数据重组。然而，添加额外的包头信息会极大地增加***开销。
发明内容
本申请提供一种数据传输方法及装置，用于降低数据传输过程中的***开销。
第一方面，本申请提供一种数据传输方法，该方法包括：第一设备接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；所述第一设备通过所述第一资源向所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制(media access control，MAC)层包头信息。
通过上述技术方案，第一设备可以通过第二设备配置的第一资源和第二资源将待发送的数据发送给第二设备，并且发送的数据均不含有包头信息。也就是说，在进行数据封装时，封装形成的MAC协议数据单元(protocol data unit，PDU)中不添加包头，这样能够降低数据传输过程中的***开销。
在一种可能的实现方式中，所述第一资源和第二资源为半静态调度(semi-persistent scheduling，SPS)资源。
在本申请中，由于主动降噪业务的周期一般为固定的周期，而SPS资源用于终端周期性地数据传输，即通过一个指示信息，为终端指示用于多次数据传输的时频资源。一般的，半静态时频资源在时间域上是周期性的，在频域上是相同的。并且，通常用于每次数据传输的时频资源大小(即时频资源的资源量)是固定不变的。在每次数据传输时，终端均在本次配置的时频资源中发送数据。
本申请中，第一设备可通过第一资源和第二资源向第二设备发送第一数据和第二数据， 作为一些可能的实施方式，第一数据和第二数据可包括如下几种情况：
第一种：所述第一数据和所述第二数据为第一数据包的不同分段。也就是说，当终端要发送的数据的数据量较大时，终端可以将数据(或者数据包)进行分段，然后将分段后的数据通过配置的第一资源和第二资源发送给网络设备。
其中，所述第一数据包的数据量大小大于第一阈值；或者所述第一资源或所述第二资源不能承载所述第一数据包。
第二种：所述第一数据和所述第二数据相同。
在一种可能的实现方式中，所述第二数据由第一数据在MAC层复制得到。
在一种可能的实现方式中，所述第一数据和所述第二数据分别对应不同的混合自动重传请求(hybrid automatic repeat request，HARQ)进程。
示例性的，第一设备可以在第一HARQ进程上通过第一资源向第二设备发送第一数据，在第二HARQ进程上通过第二资源向第二设备发送第二数据，并且第一数据和第二数据为完全相同的数据，这样可以提高数据传输的可靠性。
第三种：所述第一数据和所述第二数据为第三数据的不同冗余版本。通过该方案，第一设备可以将不同冗余版本的数据发送给第二设备，第二设备再将接收到的数据进行合并，这样能够提高数据传输的可靠性。
第二方面，本申请提供一种数据传输方法，该方法包括：第二设备向第一设备发送至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；所述第二设备通过第一资源接收所述第一设备发送的第一数据，并通过所述第二资源接收所述第一设备发送的第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
需要说明的是，上述方案中的第一设备可以为麦克风设备，第二设备可以为驾驶舱域控制器(cockpit domain controller，CDC)。
在上述技术方案中，第二设备可以为第一设备分配第一资源和第二资源，然后接收第一设备通过第一资源和第二资源发送的第一数据和第二数据，并且第一数据和第二数据不包含包头信息，也就是说，在进行数据封装时，不添加额外的包头信息，这样能够降低数据传输过程中的***开销。
在一种可能的实现方式中，所述第一资源和第二资源为半静态调度SPS资源。
在一种可能的实现方式中，所述方法还包括：所述第二设备将所述第二数据与所述第一数据进行重组，生成第一数据包；其中，所述第一数据和所述第二数据为所述第一数据包的不同分段。
基于上述技术方案，当第一设备将数据包的分片分别通过第一资源和第二资源发送给第二设备之后，第二设备可以将数据包的分段进行重组，这样接收到完整的数据包。
在本申请中，第二设备将第一数据和第二数据进行重组时，可采用如下几种方式：
第一种方式：基于所述第二资源与所述第一资源的时域先后顺序和/或频域先后顺序，或所述第二资源与所述第一资源分别对应的半静态调度SPS标识顺序，将所述第二数据与所述第一数据进行重组。
在一种可能的实现方式中，所述第一资源在时域上的位置位于所述第二资源在时域上的位置之前，且所述第一数据对应高位字节或高位比特，所述第二数据对应低位字节或低位比特。
第二种方式：基于所述第二资源以及所述第一资源组成的图样，将所述第二数据与所述第一数据进行重组。
第三种方式：在时间窗内接收所述第一数据和所述第二数据，并按照时间顺序对所述第一数据和所述第二数据进行重组；所述时间窗基于所述第一资源和所述第二资源的时域位置确定。
在一种可能的实现方式中，所述第一数据和所述第二数据相同，所述方法还包括：将所述第二数据或所述第一数据中成功解码的数据递交到上层，所述上层为MAC层的上层。
基于上述技术方案，当第一设备向第二设备发送的数据为两个相同的数据时，第二设备可将这两个相同的数据中成功解码的数据递交到上层。
在一种可能的实现方式中，所述第一数据和所述第二数据为第三数据的不同冗余版本，所述方法还包括：根据所述第一数据和所述第二数据的不同冗余版本，合并解码得到第三数据。
第三方面，本申请提供一种数据传输装置，有益效果可以参见第一方面的描述此处不再赘述。所述数据传输装置具有实现上述第一方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述数据传输装置包括：接收模块，用于接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；发送模块，用于通过所述第一资源向所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。这些模块可以执行上述第一方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第四方面，本申请一种数据传输装置，有益效果可以参见第二方面的描述此处不再赘述。所述数据传输装置具有实现上述第二方面的方法实例中行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。在一个可能的设计中，所述数据传输装置包括：发送模块，用于向第一设备发送至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；接收模块，用于通过第一资源接收所述第一设备发送的第一数据，并通过所述第二资源接收所述第一设备发送的第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。这些模块可以执行上述第二方面方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
第五方面，提供了一种数据传输装置，该数据传输装置可以为上述方法实施例中的第一设备，或者为设置在第一设备中的芯片。该数据传输装置包括收发器和至少一个处理器，所述收发器用于执行上述第一方面或第一方面任一项所述的方法。
第六方面，提供了一种数据传输装置，该数据传输装置可以为上述方法实施例中的第二设备，或者为设置在第二设备中的芯片。该数据传输装置包括收发器和至少一个处理器，所述收发器用于执行上述第二方面或第二方面任一项所述的方法中，所述数据传输装置进行消息接收和发送的操作；所述至少一个处理器调用指令，执行上述第二方面或第二方面任一项所述的方法中，所述数据传输装置进行的消息处理操作。
第七方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码并运行时，使得上述各方面中由第一设备执行的方法被执行。
第八方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码被运行时，使得上述各方面中由第二设备执行的方法被执行。
第九方面，本申请提供了一种芯片***，该芯片***包括至少一个处理器，和收发器，所述处理器通过运行指令，以执行上述第一方面以及第二方面任一项所述的方法。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
第十方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第一设备执行的方法。
第十一方面，本申请提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，当该计算机程序被运行时，实现上述各方面中由第二设备执行的方法。
应当理解的是，本申请实施例的第三方面至第十一方面技术方案及对应的可行实施方式所取得的有益效果可以参见上述对第一方面、第二方面及其对应的可能的实现方式的技术效果，此处不再赘述。
附图说明
图1为现有技术中的一种数据分段封装PDU结构示意图；
图2为本申请实施例提供的一种通信场景的示意图；
图3为本申请实施例提供的一种数据传输方法流程图；
图4A为本申请实施例提供一种SPS资源的分布示意图；
图4B为本申请实施例提供一种高位字节与低位字节的示意图；
图4C为本申请实施例提供的一种SPS资源的时频分布示意图；
图5为本申请实施例提供的另一种数据传输方法流程图；
图6为本申请实施例提供的一种协议栈架构示意图；
图7为本申请实施例提供的又一种数据传输方法流程图；
图8为本申请实施例提供的一种数据传输装置的逻辑结构示意图；
图9为本申请实施例提供的一种第一设备的结构示意图；
图10为本申请实施例提供的一种数据传输装置的逻辑结构示意图；
图11为本申请实施例提供的一种第二设备的结构示意图。
具体实施方式
下面将结合本申请以下实施例中的附图，对本申请实施例中的技术方案进行详尽描述。
如图1所示为现有技术中的一种数据分段封装协议数据单元(protocol data unit，PDU)结构示意图，图1以无线链路控制子层(radio link control，RLC)为例，比如，对于每一个上层数据，RLC层称为RLC层服务数据单元(service data unit，SDU)。在RLC层可能需要对SDU进行分段，例如单个SDU被分为两个分段，则每个分段将会被添加包头信息封装生成多个RLC PDU。
图1中，PDU结构中的数据(data)部分即对应不同SDU的分段。然而，在数据传输过程中，为SDU的不同分段添加额外的包头信息。例如，切分指示(Segmentation Indicator)，SI用于指示是否对SDU进行切分，例如1标识切分，0表示不切分；分段偏移量(Segmentation offset)，SO用于指示当有切分时，在原始RLC SDU的切分的位置； SN用于指示顺序号，这会极大的增加***开销，使得单个PDU中包含的有效负载比较小。
有鉴于此，本申请实施例提供一种数据传输方法，不添加包头信息，然后将没有添加包头信息的数据发送给接收端，这样能够降低***开销，并且能够保证PDU中包含的有效负载比较大。
以下，首先对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1)驾驶舱域控制器
驾驶舱域控制器(cockpit domain controller，CDC)简称车机。目前CDC可以与其它车载设备或非车载设备通信，实现包括但不限于传统的收音机、音乐视频播放、导航播报、手机导航投屏等功能，此外，CDC还可以带有蜂窝通信功能，例如第三代移动通信技术(3rd-generation，3G)、***移动通信技术(the 4th generation mobile communication technology，4G)、第五代移动通信技术(the 5th generation mobile communication technology，5G)、第六代移动通信技术(the 6th generation mobile communication technology，6G)、等，以及车载信息服务(telematics)功能，实现人与车，车与外界的信息通讯，增强了用户体验及服务、安全相关的功能。
2)主节点、从节点
主节点和从节点是指在逻辑功能上区分的两类节点。其中，主节点管理从节点，具有资源分配能力或资源调度能力，负责为从节点分配时频资源；从节点听从主节点的分配，使用主节点分配的时频资源进行通信。
需要说明的是，在不同的场景下，主节点和从节点可能不同。示例性的，比如CDC调度车载音频设备，此时CDC为主节点，车载音频设备为从节点；手机调度智能可穿戴设备，此时手机为主节点，智能穿戴设备为从节点。并且，同一设备在不同的场景下，节点的属性可能会发生改变。例如，当手机与耳机进行通信时，手机为主节点，耳机为从节点；但是当手机与CDC连接，手机听从CDC调度的时候，此时手机的角色属性变更为从节点。
3)通信域
通信域包括一个主节点和至少一个从节点，所述至少一个从节点与主节点建立通信连接，主节点为所述至少一个从节点分配或调度时频资源，每一个从节点使用调度或分配的时频资源与主节点进行通信。
4)非车载设备
“非车载设备”，是指放置在车内(例如，智能座舱内)、能够与车内的其他设备进行通信或连接、但不属于车的一部分的设备。
例如：非车载设备，可以是终端(terminal)、移动台(mobile station，MS)、移动终端(mobile terminal)、可穿戴设备等设备，或这些设备中的芯片、芯片***等装置。示例性的，本申请实施例中的非车载设备可以是移动电话(或称为“蜂窝”电话)、具有移动终端的计算机、智能车辆、车联网相关智能设备(如无人驾驶领域的车载设备)、可穿戴设备等，非车载设备还可以是便携式、袖珍式、手持式、计算机内置的或者车载上的移动装置。非车载设备也可以是具有通信模块的通信芯片。非车载设备可被配置为支持无线通信，例如，非车载设备可包括无线通信模块，或连接至无线通信模块。
5)车载设备
“车载设备”，也称为车载单元(on-board unit，OBU)，是指集成或安装在车内或车 上(例如智能座舱内)、属于该车的一部分的设备。一般的，车载终端可以指由车辆制造商在该车辆出厂前装(factory-installed)在车辆上的设备。例如：车载麦克、车载音响、车载屏幕等。
(1)、麦克，也可称为“麦克风”、“话筒”或“传声器”，可用于将声音信号转换为电信号。当拨打电话或发送语音信息时，可由麦克采集用户的声音，然后将用户的声音转换为电信号，后续可通过有线和/或无线方式向CDC或其他车内设备发送该电信号。在一种可能的示例中，车内可以设置至少一个麦克。在另一些实施例中，车内可以设置两个或更多的麦克，除了采集声音信号，还可以实现降噪、定向录音等功能。
(2)、音箱，也可称为“扬声器”、“喇叭”等，用于将音频电信号转换为声音信号通过进行播放。用户可以通过音箱收听音乐或接听免提通话等。音箱也可与麦克配合实现降噪。
(3)、屏幕，或称“显示屏”，可以用于显示图像、视频等。屏幕可以包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)、有机发光二极管(organic light-emitting diode，OLED)、有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)、柔性发光二极管(flex light-emitting diode，FLED)、迷你发光二极管(miniLED)、微型发光二极管(microLED)、微型OLED、量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，车内可以设置一个或多个屏幕。此外，屏幕还可以是触控屏，可供获取用户的触控操作。
应理解，上述车载设备可被配置为支持无线通信，例如，上述车载设备可包括无线通信模块(或称无线收发器等)，或连接至无线通信模块。
6)终端设备
终端设备可以简称为终端，也称为用户设备(user equipment，UE)，是一种具有无线收发功能的设备。终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、无人机、气球和卫星上等)。所述终端设备可以是手机、平板电脑、带无线收发功能的电脑、虚拟现实终端设备、增强现实终端设备、工业控制中的无线终端设备、无人驾驶中的无线终端设备、远程医疗中的无线终端设备、智能电网中的无线终端设备、运输安全中的无线终端设备、智慧城市中的无线终端设备、智慧家庭中的无线终端设备。终端设备也可以是固定的或者移动的。本申请实施例对此并不限定。
本申请实施例中，用于实现终端的功能的装置可以是终端设备；也可以是能够支持终端设备实现该功能的装置，例如芯片***，该装置可以被安装在终端设备中。本申请实施例中，芯片***可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端设备的功能的装置是终端设备为例，描述本申请实施例提供的技术方案。示例性的，本申请中的终端设备可以是车载设备和/或非车载设备。可以理解的，在一种实施方式中，终端设备可以是CDC或其他域控制器。
7)网络设备
网络设备可以是接入网设备，接入网设备也可以称为无线接入网(radio access network，RAN)设备，是一种为终端设备提供无线通信功能的设备。接入网设备例如包括但不限于：5G中的下一代基站(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点 (transmitting point，TP)、未来移动通信***中的基站或WiFi***中的接入点等。接入网设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)，和/或分布单元(distributed unit，DU)，或者网络设备可以为中继站、车载设备以及未来演进的PLMN网络中的网络设备等。
终端设备可以与不同技术的多个接入网设备进行通信，例如，终端设备可以与支持长期演进(long term evolution，LTE)的接入网设备通信，也可以与支持5G的接入网设备通信，还可以同时与支持LTE的接入网设备以及支持5G的接入网设备进行通信。本申请实施例并不限定。
本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片***，该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备为例，描述本申请实施例提供的技术方案。示例性的，本申请中的网络设备可以是CDC。
需要说明的是，本申请可以应用于智能座舱环境下，也可以应用于各种通信***，例如：长期演进(long term evolution，LTE)***，短距通信***(例如，蓝牙，WIFI等)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信***，5G***以及未来的移动通信***等。
具体的，本申请实施例可以应用于不同的数据传输场景，比如智能座舱场景中的车载主动降噪业务。车载主动降噪是通过车内扬声器发射反相声学信号来中和发动机噪声、路噪、风噪等噪声，实现车内全局或区域静场，达到消除或降低车内噪声的目的。具体的，多个车载麦克风需要采集车内噪声信号，传输至处理器单元生成反相噪声信号，然后传输反相噪声信号至多个车载扬声器分别播放出来，从而在座舱接收端实现主动降噪的效果。为了确保反相噪声和真实噪声相互抵消，并且确保降噪***能够稳定工作，噪声的采集、处理、传输、反相噪声信号的产生、反相噪声信号传输到车载扬声器并在座舱接收端播放的时延需要小于真实噪声传输至座舱接收端播放的时延，并且噪声信号和反相噪声信号的传输需满足高可靠性。
如图2所示，为本申请实施例提供的一种通信场景的示意图。在图1中，该通信场景主要包括CDC与车载设备(例如，麦克、音箱、屏幕等车载设备)或非车载设备(例如用户的手机、可穿戴设备)之间的通信。
其中，CDC与车载设备可设置于车辆内部，非车载设备可设置于车辆内部，或者可随着用户的移动进入或离开车辆内部。
如图3所示，为本申请实施例提供的一种数据传输方法流程图，参阅图3所示，该方法可包括如下步骤：
S301：第二设备向第一设备发送至少一个资源配置信息。相应的，第一设备接收第二设备发送的至少一个资源配置信息。
其中，至少一个资源配置信息可以用于配置第一资源和第二资源。第一设备和第二设备可通过第一资源和第二资源传输数据。所述第一资源和第二资源为半静态调度(semi-persistent scheduling，SPS)资源。
可以理解的，第一资源和第二资源可以包含在一个资源配置信息或多个资源配置信息中。其中，第一资源和/或第二资源中至少包括一个时频资源单元(unit)。例如，可以包括资源块(resource block，RB)，或者资源元素(resource element，RE)。
示例性的，其中资源配置信息可以是无线资源控制信令(radio resource control，RRC)；或者可以是下行控制指示(downlink control indicator，DCI)；其中RRC信令包括***消息(System information)，例如，主***信息块(master information block，MIB)或者***信息块(system information block，SIB)。
示例性的，第一资源可用于第一设备与第二设备之间传输第一数据，具体包括，第一设备可通过该第一资源向第二设备发送第一数据，或者，第二设备可通过该第一资源向第一设备发送第一数据。
举例来说，当第二设备是主节点设备，第一设备是从节点设备时，第二设备可以为第一设备配置第一资源，第一设备可使用第二设备配置的第一资源与第二设备进行通信。
以下以第一设备为终端设备，第二设备为网络设备，并且第一设备为麦克风，第二设备为CDC为例进行介绍。
在本申请实施例中，麦克风包括两种形态的麦克风，由于麦克风形态的不同，产生的数据量的大小也不同，因此，对于不同数据量的数据，数据传输的方式可能也是不同的。以下分别对两种不同形态的麦克风与CDC之间的数据传输进行介绍。
第一种形态：单个麦克风。
对于单个麦克风而言，数据量的大小相对较小。也就是说，单个麦克风的数据量的大小小于设定阈值(以下记为“第一阈值”)，或者单个资源能够承载单个麦克风的数据量大小。
第二种形态：阵列类型的麦克风。
所谓阵列类型的麦克风，就是多个麦克风组成的阵列，因此，对于阵列类型的麦克风产生的数据可以认为是一个数据，该数据可包括多个麦克风采集的声音信号。一般的，麦克风阵列中包含多个阵元，阵列数据是多个阵元数据汇聚形成的，因此，数据量相对较大。即数据量的大小大于第一阈值，或者单个资源不能承载该数据量的大小时，本申请实施例中第二设备可以配置至少一个资源配置信息，即第二设备可以配置至少一个资源，比如第一资源和第二资源，通过第一资源和第二资源将麦克风阵列采集到的数据发送给CDC。
作为一种可能的实现方式，在步骤S301实施之前，第一设备(麦克风)可以向第二设备(CDC)上报第一信息，所述第一信息包括设备类型信息、业务类型信息、阵列中的阵元个数、每个阵元的采样率、采样周期、量化比特等信息中的至少一项。可选的，设备类型信息可包括麦克风、扬声器、阵列形态、单麦克风形态等。CDC在接收到麦克风发送的第一信息之后，可根据第一信息确定所要配置的资源的大小。
以下对上述第一信息中包括的参数信息进行介绍：
(1)、阵列中的阵元个数可以是阵列中处在工作状态或者工作模式的阵元个数。可以理解的是，阵列中工作的阵元个数可以根据业务的需求动态调整。
(2)、采样率，又称为采样频率或采样速度，定义了每秒从连续信号中提取并组成离散信号的采样个数，它用赫兹(Hz)来表示。
(3)、采样周期，为采样频率的倒数，也可称为采样时间，它是采样之间的时间间隔。
(4)、量化，是指将信号的连续取值(或者大量可能的离散取值)近似为有限多个(或较少的)离散值的过程。一般来说，量化主要应用于从连续信号到数字信号的转换中。连续信号经过采样成为离散信号，离散信号经过量化即成为数字信号。采样值的二进制位数决定了采样值的量化比特，也称为量化精度或量化位宽。
(5)、业务类型信息，可用于指示业务的类型，比如，业务类型信息可以是标识，例如，可以用应用标识(application identifier，AID)1来标识主动降噪业务；用AID2来标识流媒体后视镜业务。
可以理解的是，上报采样率或者采样周期有利于CDC了解麦克风设备(例如，麦克风阵列设备)中采样数据准确到达的周期；上报阵元个数和量化比特，有利于CDC了解麦克风设备单次数据采样数据量的大小；上报业务类型信息有利于CDC了解麦克风设备上的业务类型，从而有利于为其配置合适的资源。
例如，如果麦克风阵列设备向CDC上报其本次数据传输利用其中K(K为正整数)个阵元采集数据，假定对于单个阵元采集的信号，采用Xbit对该信号进行量化，则此时CDC可以确定该麦克风阵列单次数据采样的总数据量为K*Xbit，从而确定为该麦克风设备分配合适的资源，并向其发送至少一个资源配置信息。
通常，麦克风阵列中的阵元的采样率、采样周期、量化比特一般是相同的。在一种可能的实现中，为了节省信令开销，麦克风可在上报第一信息时，上报相同的采样率、采样周期、量化比特，而不必上报每个阵元的采样率、采样周期、量化比特。
当第一设备需要向第二设备发送数据时，第二设备需要为第一设备调度资源。可选的，第二设备可接收第一设备发送的所需要发送的数据所属业务的信息，如类型信息。当第二设备确定第一设备需要发送的数据是第一业务的数据时，才为第一设备从第一资源池分配资源。例如，假设第一设备向第二设备发送的业务类型信息为AID1，用于指示其为主动降噪业务，则第二设备为第一设备从第一资源池中分配资源。其中第一资源池中包含若干时频资源单元。
进一步的，第二设备可针对不同的业务配置不同的资源池。例如，主动降噪业务对应第一资源池，流媒体业务对应第二资源池等等。其中，第一资源池和第二资源池可以相同，也可以不同，本申请对此不作限定。
需要说明的是，上述仅是以CDC与麦克风为例，当第一设备为CDC，第二设备为扬声器时，第一设备向第二设备发送数据即为下行数据，在该过程中，步骤S301为可选的步骤。也就是说，如果是CDC向扬声器发送下行数据时，CDC可以不向扬声器发送资源配置信息。
S302：第一设备通过第一资源向第二设备发送第一数据，并通过第二资源向第二设备发送第二数据。
相应的，第二设备通过第一资源接收第一设备发送的第一数据，并通过第二资源接收第一设备发送的第二数据。
其中，所述第一数据和所述第二数据均不包含媒体接入控制(media access control，MAC)层包头信息。
(1)、当第一设备要发送的数据(例如，第一数据包)的数据量比较小时(例如，所述第一数据包的数据量大小小于等于第一阈值；或者所述第一资源或所述第二资源能够承载所述第一数据包)，MAC层将所述要发送的数据(例如第一数据包)直接“透传”给物理层。
本申请实施例中，透传也称为透明传输(Transparent transmission)，即至少一个服务数据单元SDU在经过某个协议层处理时，该协议层生成的协议数据单元PDU包含所述至少一个SDU，但是并不添加相应的包头信息，也不对SDU进行切分。
可选地，生成的PDU等于SDU，即近似于该协议层”没有“对该SDU进行处理，类似于透明的，所以称为透明传输。
可选的，透传包括对数据进行加密，例如可以采用等长加密技术，使得加密后的数据长度与加密前的数据长度相同。
MAC层将第一设备要发送的数据“透传”给物理层是指MAC将该数据封装在MAC PDU中，该MAC PDU不包含包头信息。在封装过程中，不对数据进行切分。可选地，数据可以是数据包。可选地，数据可以是MAC SDU。
(2)、当第一设备要发送的数据(例如，第一数据包)的数据量较大(例如，所述第一数据包的数据量大小大于第一阈值；或者所述第一资源或所述第二资源不能承载所述第一数据包)时，在本申请一些实施例中，第二设备可以为第一设备配置多路资源，比如第一资源和第二资源，然后第一设备可对要发送的数据进行切分，并通过配置的多路资源将要切分后的数据发送给第二设备。
在一种可能的实现方式中，比如第一设备要发送的数据为第一数据包，第一设备的数据链路层可以对第一数据包进行切分，比如切分为两个数据，记为第一数据和第二数据。
当第二设备为第一设备分配第一资源和第二资源之后，第一设备可分别通过多路资源将切分后的数据发送给第二设备。以两路资源为例，第一设备可通过第一资源将第一数据发送给第二设备，并且可通过第二资源将第二数据发送给第二设备。也就是说，如果数据量比较大，可首先在数据链路层对数据进行切分，然后再对切分后的数据进行封装，封装生成的多个PDU不包含包头信息。
可选的，数据链路层包含MAC层，对切分数据进行封装并生成的多个MAC PDU，可以在MAC层进行,且所述MAC PDU均不包含包头信息。
在另外一种可能的实现方式中，比如第一设备要发送的数据为第一数据包，第二设备为第一设备分配第一资源和第二资源。第一设备的MAC层将所述第一数据包“透传”给物理层，物理层可以对第一数据包进行切分，切分为多个编码块(Coded Block)，比如切分为两个编码块，分别记为第一数据和第二数据。其中，第一数据承载在第一资源上，第二数据承载在第二资源上。
可选的，所述第一编码块和第二编码块可以采用不同的编码参数；例如，编码率，编码方式等。
在另一些实施例中，第二设备也可以为第一设备配置第三资源，其中所述第三资源包括第一资源和第二资源。具体的，第一资源和第二资源是第一设备的物理层自己确定的。例如，第一设备物理层可以根据切分的第一数据和第二数据的大小，确定第一资源和第二资源(例如，包括第一资源和第二资源的大小，或者第一资源和第二资源在第三资源中的相对位置)。
可以理解的，一般的，物理层通常对进行信道编解码，有利于提高数据传输的可靠性。
S303：第二设备将第二数据与第一数据进行重组，生成第一数据包。
在步骤S302中，所述第一数据和所述第二数据为第一数据包的不同分段。因此，当第一设备将第一数据包的不同分段通过第一资源和第二资源发送给第二设备之后，第二设备可接收第一数据包的不同分段，并对不同分段进行重组(reassembly)，得到完整的第一数据包。
可以理解的，对于带有包头的数据，进行重组可能需要移除相应的包头。
可选的，重组的一种实现方式为拼接(concatenation)，因此，作为一种可能的实现方式，可以对第一数据和第二数据进行拼接。可以理解的，考虑到第一数据和第二数据都不携带包头信息，则重组的关键是确定第一数据和第二数据的相对先后关系，直接进行拼接生成第一数据包。
由于第一设备发送的第一数据和第二数据不包含MAC层包头信息，那么第二设备在进行重组的时候，就需要知道哪些资源上的数据可以重组生成第一数据包，并且需要知道这些数据的顺序，才能成功的将接收到的数据重组成第一数据包。
在本申请实施例中，第二设备对接收到的数据进行重组的方式可参阅如下几种可能的实施方式：
第一种：
(1)第二设备可基于第一资源与第二资源的时域先后顺序，将第二数据与第一数据进行拼接。
可以理解的，第二设备可以为第一设备配置在时域有一定先后关系的半静态调度资源。
如图4A所示，假设第二设备为第一设备配置了第一资源和第二资源，其中，第一资源和第二资源都是半静态调度资源。一般的，第一资源和第二资源为周期性出现的资源，因为上层业务(即第一数据包)可能是周期性出现的。从图4A中可以看到，在每个周期内，第一资源和第二资源在时间域上是有一定先后顺序的，第一资源在时域上的位置位于所述第二资源在时间域上的位置之前。即，第一资源中存在至少一个符号(或者子帧、帧)的位置在第二资源中所有符号(或者子帧、帧)之前。
在发送端，第一数据包分段生成的第一数据对应第一数据包的高位字节(Most Significant Byte)或高位比特(Most Significant Bit)，即第一数据为第一数据包的第一分段；第二数据为第一数据包的低位字节(Least Significant Byte)或低位比特(Least Significant Bit)，即，第二数据为第一数据包的第二分段。示意性的，可参阅图4B所示，为本申请实施例提供一种高位字节与低位字节的示意图。
可以理解的是，协议可以约定，在时域位置靠前的资源上发送第一分段，在时域位置靠后的资源上发送第二分段。或者协议也可以约定在时域靠前的资源上发送第二分段，只要收发两端理解一致，按照此规则也可以重组得到第一数据包，本申请对此不作限定。
在接收端，CDC可以在第一资源上得到第一数据，在第二资源上得到第二分段，并利用第一资源与第二资源在时域上的相对关系确定第一数据为第一数据包的第一分段，第二数据为第一数据包的第二分段，从而拼接得到所述第一数据包。
也就是说，第二设备可根据第一资源和第二资源在时域上的前后顺序进行拼接。比如，在时域上，第一资源位于第二资源之前，那么在拼接的时候，第一资源对应的第一数据可在第二资源对应的第二数据之前。
可选的，在接收端可以存在一个时间窗，接收端只对该时间窗内的第一资源和第二资源上的数据进行重组。
(2)第二设备可基于第二资源与第一资源的频域先后顺序，将第二数据与第一数据进行拼接。
可以理解的，第二设备可以为第一设备配置在频域有一定先后关系的半静态调度资源。继续参阅图4A所示，第二设备为第一设备配置了第一资源和第二资源，其中，第一资源和第二资源都是半静态调度资源。一般的，第一资源和第二资源为周期性出现的资源，因 为上层业务(即第一数据包)可能是周期性出现的。从图4A中可以看到，在每个周期内，第一资源和第二资源在频域上是有一定先后顺序的，第一资源在频域上的位置位于所述第二资源在频域上的位置之前。其中，第一资源对应5900-5905Hz，第二资源对应5905-5910Hz。即，第一资源中存在至少一个RE，或者子载波的位置在第二资源中所有RE或者子载波的位置之前。
在发送端，第一数据包分段生成的第一数据对应第一数据包的高位字节(Most Significant Byte)或高位比特(Most Significant Bit)，即第一数据为第一数据包的第一分段；第二数据为第一数据包的低位字节(Least Significant Byte)或低位比特(Least Significant Bit)，即，第二数据为第一数据包的第二分段。
可以理解的是，协议可以约定，在频域位置靠前的资源上发送第一分段，在频域位置靠后的资源上发送第二分段；或者，协议也可以约定在频率靠前的资源上发送第二分段，只要收发两端理解一致，按照此规则也可以重组得到第一数据包，本申请对此不作限定。
在接收端，CDC可以在第一资源上得到第一数据，在第二资源上得到第二分段，并利用第一资源与第二资源在频域上的相对关系确定第一数据为第一数据包的第一分段，第二数据为第一数据包的第二分段，从而拼接得到所述第一数据包。
也就是说，第二设备可根据第一资源和第二资源在频域上的前后顺序进行拼接。比如，在频域上，第一资源位于第二资源之前，那么在拼接的时候，第一资源对应的第一数据可在第二资源对应的第二数据之前。
第二种：第二设备为第一设备配置的SPS资源，可以存在SPS资源对应的SPS标识(例如，SPS ID)，即第一资源对应SPS ID1，第二资源对应SPS ID2。
发送端，第一数据包分段生成的第一数据对应第一数据包的高位字节(Most Significant Byte)或高位比特(Most Significant Bit)，即第一数据为第一数据包的第一分段；第二数据为第一数据包的低位字节(Least Significant Byte)或低位比特(Least Significant Bit)，即，第二数据为第一数据包的第二分段。
如果协议约定按照SPS ID的先后顺序来进行数据发送(假定SPS ID的先后顺序为：SPS ID1在先，SPS ID2在后)，即在发送端，在第一资源上发送第一分段，在第二资源上发第二分段，则在接收端，CDC可以在第一资源上得到第一数据，在第二资源上得到第二分段，并利用第一资源与第二资源分别对应的SPS ID的相对先后关系，确定第一数据为第一数据包的第一分段，第二数据为第一数据包的第二分段，从而拼接得到所述第一数据包。
也就是说，第二设备可根据第一资源和第二资源对应的SPS ID的前后顺序进行拼接。
可以理解的是，协议也可以约定在SPS ID靠前的资源上发送第二分段，只要收发两端理解一致，按照此规则也可以重组得到第一数据包，本申请对此不作限定，具体的重组过程可参阅上述过程，在此不再赘述。
第三种：第二设备可基于所述第一资源以及第二资源所述组成的图样，将所述第二数据与所述第一数据进行重组。
一般的，不同的资源配置对应于时域、频率两维域会呈现不同的资源形状，也称为资源图样。
发送端，物理层可以对第一数据包进行切分，切分为多个编码块(Coded Block)，比如切分为两个编码块，分别记为第一数据和第二数据。第一数据包分段生成的第一数据对应第一数据包的高位字节(Most Significant Byte)或高位比特(Most Significant Bit)，即 第一数据为第一数据包的第一分段；第二数据为第一数据包的低位字节(Least Significant Byte)或低位比特(Least Significant Bit)，即，第二数据为第一数据包的第二分段。
假设第二设备为第一设备配置第三资源，第一设备可将第三资源划分为第一资源和第二资源。其中，第一资源用于承载第一数据，第二资源用于承载第二数据。
其中，第一资源和/或第二资源中至少包括一个时频资源单元(unit)，例如可以包括RB或者RE。
假设第一资源和第二资源的时频分布如图4C所示，在每个周期内，第一资源和第二资源一共包含4个时频资源单元，例如，分别记为X1、X2，X3，X4。
对于某个固定的资源图样/形状，发送端数据在图样包含的时频资源上的依次摆放顺序可以是协议约定好的。例如，将第一数据承载在X1，X3上，将第二数据承载在X2，X4上。那么在接收端，按照协议约定的顺序，可以首先从X1，X3对应的资源上得到第一数据，再从X2，X4对应的资源上得到第二数据，并确定第一数据为第一数据包的第一分段，第二数据为第一数据包的第二分段，从而拼接得到所述第一数据包。
通过本申请实施例的方案，发送端设备可以通过多路资源向接收端设备发送不包含包头信息的分段数据，这样接收端设备可以对接收到的分段数据进行拼接，得到完整的数据包，然后将完整的数据包递交到上层。通过该方法，可以解决数据封装过程中添加包头信息带来的***开销较大的问题。
在另一些实施例中，第一设备在对切分后的数据进行封装时，可以添加包头信息，也就是说，封装后的MAC PDU包含包头信息。本申请实施例中，可在包头信息中添加排序号，该排序号用于标识数据的先后顺序，也就是说，包头信息只包含排序号。
第二设备可在接收到第一数据和第二数据之后，根据第一数据和第二数据中分别包含的排序号对第一数据和第二数据进行重组。示例性的，假设第一数据的包头信息中的排序号为0，第二数据的包头信息中的排序号为1，则第二设备可将顺序号为0和顺序号为1的数据进行拼接。
可选的，包头信息中添加的排序号最大可以为3bit，也就是说数据的包头信息比较小，这样可以适当降低***开销。
如图5所示，为本申请实施例提供的一种数据传输方法，参阅图5所示，该方法可包括如下步骤：
S501：第二设备向第一设备发送至少一个资源配置信息。相应的，第一设备接收第二设备发送的至少一个资源配置信息。
其中，至少一个资源配置信息可以用于配置第一资源和第二资源。应理解，该步骤S501与步骤S301相同，具体可参阅上述图3实施例中的描述，此处不再重复赘述。
可选的，所述资源配置信息中可以包含第二信息，所述第二信息用于指示第二资源为进行重复传输的SPS资源。
S502：第一设备通过第一资源向第二设备发送第一数据，并通过第二资源向第二设备发送第二数据。
其中，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
这里的第一数据和第二数据相同，并且第二数据是由第一数据在MAC层复制得到的，所述第一数据和所述第二数据分别对应不同的混合自动重传请求(hybrid automatic repeat request，HARQ)进程。也就是说，第一设备可将待发送的第一数据复制一份相同的数据， 并通过第一SPS资源发送第一数据，通过第二SPS资源发送复制的第二数据，这样第一设备可以向第二设备发送两份相同的数据，并且这两份数据分别在不同的HARQ进程上发送。
需要说明的是，网络设备(CDC)可以通过信令配置终端设备(比如，麦克风)进行数据重复传输。示例性的，比如通过RRC信令配置或激活MAC层进行数据重复传输；或通过DCI配置或激活MAC层进行数据重复传输。
可以理解的是，此处网络设备指的是第二设备，终端设备指的是第一设备。
S503：第二设备将第二数据或第一数据中成功解码的数据递交到上层。
其中，所述上层为MAC层的上层。例如，MAC层的上层可以为链路控制层、网络层中的任意一个协议层。
如图6所示，为本申请实施例提供的一种协议栈的架构示意图，图6中，协议栈可包括物理层、数据链路层以及网络层。
其中，数据链路层可包括：链路控制层和MAC层(或称媒体接入层)。
一般的，网络层位于数据链路层之上，负责进行路由选择，从而确定两节点之间的路径。可选的，网络层还可以进行流量控制。
一般的，链路控制层定义不同的传输模式，满足不同业务的传输需求。例如，可以根据是否需要接收端对发送的数据进行确认，分为Acknowledged mode和Unacknowledged Mode。
可选的，链路控制层还可以进行重复包检测、排序、数据包分段、重组等功能。
一般的，MAC层实现资源管理、调度、接入控制、不同优先级的数据封装等功能。
一般的，利用传输介质为数据链路层提供物理连接，实现比特流的透明传输。一般的，物理层进行信道编码或解码，保障数据传输的可靠性。
可以理解的是，由于网络层可能存在不同的网络和/或传输协议，因此，链路控制层可能包含适配层功能，即，可用于提供与不同的网络和/或传输协议之间的传输适配功能。比如，接收来自底层(链路控制层之下的协议层)的数据包，区分该数据包所属的上层网络层(链路控制层之上的协议层，即网络层)协议类型，并将该数据包递交(或称传递)给对应的上层协议处理。需要说明的是，适配功能是一个逻辑功能层，在实现上，其也可以包含在网络层中，本申请对此不作限制。
当第一设备将两份相同的数据发送给第二设备之后，第二设备可接收到两份相同的数据，此时第二设备可将第一数据或第二数据中成功解码的数据递交到MAC层的上层。比如，第一数据为先成功解码的数据，则第二设备可将第一数据递交到MAC层的上层；或者第二数据先于第一数据成功解码，则第二设备可将第二数据递交到MAC层的上层。
在另一些实施例，对于没有成功解码的数据可以丢弃，比如第一数据为成功解码的数据，第二数据没有成功解码，则第二设备可将第二数据丢弃。
可选的，发送端协议层可以对传输数据添加循环冗余校验(cyclic redundancy check，CRC)校验码，用于接收端对应的协议层对数据进行校验。其中，CRC校验运算使用的算法、参数可以是主节点与从节点双方预先约定的或协议中定义的。CRC校验码可添加在传输数据的尾部。
通过该方案，发送端设备可以发送不包含有包头信息的数据，并且接收端设备可以在两个不同的HARQ进程上接收到两份相同的数据，这样不但可以降低***开销，而且能够提高数据传输的可靠性。
如图7所示，为本申请实施例提供的一种数据传输方法，参阅图7所示，该方法可包括如下步骤：
S701：第二设备向第一设备发送至少一个资源配置信息。相应的，第一设备接收第二设备发送的至少一个资源配置信息。
其中，至少一个资源配置信息可以用于配置第一资源和第二资源。应理解，该步骤S701与步骤S301相同，具体可参阅上述图3实施例中的描述，此处不再重复赘述。
S702：第一设备通过第一资源向第二设备发送第一数据，并通过第二资源向第二设备发送第二数据。
其中，第一数据和第二数据均不包含媒体接入控制MAC层包头信息。并且，所述第一数据和所述第二数据为第三数据的不同冗余版本。可选的，所述第三数据可以为数据包。
本申请实施例中，第一数据和第二数据为第三数据的不同冗余版本，第一设备可以向第二设备发送不同冗余版本的数据。示例性的，可通过第一SPS资源发送冗余版本为0的数据，通过第二SPS资源发送冗余版本为1的数据，这样接收端可接收到不同冗余版本的数据。
一般的，在发送端发送不同冗余版本的数据，可以使得接收端进行软合并，从而获得较好的效果。其中，不同的冗余版本分别对应不同的编码比特集合，但是包含相同的信息，接收端会把不同冗余版本的数据进行合并。
S703：根据所述第一数据和所述第二数据的不同冗余版本，合并解码得到第三数据。
当第二设备接收到第一设备发送的不同冗余版本的数据之后，可根据第一数据和第二数据的不同冗余版本，对第一数据和第二数据进行合并解码，然后得到第三数据。
在一种可能的实现方式中，可以根据SPS ID的先后顺序或者图样，对第一数据和第二数据的不同冗余版本进行合并。具体可参阅图3实施例中有关SPS ID的先后顺序以及图样的描述，此处不再重复赘述。
通过该方案，发送端设备可以发送不包含有包头信息的数据，并且接收端设备可以对两个不同冗余版本的数据进行合并，这样可以降低***开销，并且能够提高数据传输的可靠性。
下面结合附图介绍本申请实施例中用来实现上述方法的装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。
本申请实施例可以根据上述方法示例对第一用户设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
基于与上述方法实施例相同构思，本申请实施例提供了一种数据传输装置。
在采用集成的单元的情况下，如图8所示为一种数据传输装置的逻辑结构示意图，该数据传输装置可应用于第一设备，参阅图8所示，数据传输装置800包括接收模块801、发送模块802。作为一种示例，装置800用于实现上述方法中第一设备的功能。例如，该装置可以是麦克风设备，也可以是麦克风设备中的装置，例如芯片***。
其中，接收模块801，用于接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；发送模块802，用于通过所述第一资源向 所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
在一种可能的实施方式中，所述第一资源和第二资源为半静态调度SPS资源。
在一种可能的实施方式中，所述第一数据和所述第二数据为第一数据包的不同分段。
在一种可能的实施方式中，所述第一数据包的数据量大小大于第一阈值；或者所述第一资源或所述第二资源不能承载所述第一数据包。
在一种可能的实施方式中，所述第一数据和所述第二数据相同。
在一种可能的实施方式中，所述第二数据由第一数据在MAC层复制得到。
在一种可能的实施方式中，所述第一数据和所述第二数据分别对应不同的混合自动重传请求HARQ进程。
在一种可能的实施方式中，所述第一数据和所述第二数据为第三数据的不同冗余版本。
当采用硬件形式实现时，本申请实施例中，接收模块801可以是通信接口、接收器、收发电路等。发送模块802可以是通信接口、发射器、收发电路等。其中，通信接口是统称，可以包括一个或多个接口。
当接收模块801是接收器，发送模块802是发射器时，本申请实施例所涉及的数据传输装置800可以如图9所示。参阅图9所示，为本申请实施例提供的一种数据传输装置900。示例性的，该数据传输装置可以为第一设备。该数据传输装置900可包括接收器901、发射器902、处理器903、存储器904。其中，存储器904中存储指令或程序，处理器903用于执行存储器904中存储的指令或程序。接收器901用于执行上述实施例中接收模块801执行的操作。发射器902用于执行上述实施例中发送模块802执行的操作。
应理解，根据本申请实施例的数据传输装置900或第一设备900可对应于图3、图5、图7所示的实施例中的第一设备，并且数据传输装置900或第一设备900中的各个模块的操作和/或功能分别为了实现图3、图5、图7所示的实施例中的相应流程，为了简洁，在此不再赘述。
如图10所示，本申请实施例还提供了一种数据传输装置的逻辑结构示意图，参阅图10所示，数据传输装置1000包括发送模块1001、接收模块1002。作为一种示例，装置1000用于实现上述方法中第二设备的功能。例如，该装置可以是CDC设备，也可以是CDC设备中的装置，例如芯片***。
其中，发送模块1001，用于向第一设备发送至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；
接收模块1002，用于通过第一资源接收所述第一设备发送的第一数据，并通过所述第二资源接收所述第一设备发送的第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
在一种可能的实施方式中，所述第一资源和第二资源为半静态调度SPS资源。
在一种可能的实施方式中，所述装置还包括：处理模块1003；所述处理模块1003，用于将所述第二数据与所述第一数据进行重组，生成第一数据包；其中，所述第一数据和所述第二数据为所述第一数据包的不同分段。
在一种可能的实施方式中，所述处理模块1003具体用于按如下方式将所述第二数据与所述第一数据进行重组：基于所述第二资源与所述第一资源的时域先后顺序和/或频域先后顺序，或所述第二资源与所述第一资源分别对应的半静态调度SPS标识顺序，将所述第 二数据与所述第一数据进行重组。
在一种可能的实施方式中，所述第一资源在时域上的位置位于所述第二资源在时域上的位置之前，且所述第一数据对应高位字节或高位比特，所述第二数据对应低位字节或低位比特。
在一种可能的实施方式中，所述处理模块1003具体用于按如下方式将所述第二数据与所述第一数据进行重组，包括：基于所述第二资源以及所述第一资源组成的图样，将所述第二数据与所述第一数据进行重组。
在一种可能的实施方式中，所述处理模块1003具体用于按如下方式将所述第二数据与所述第一数据进行重组：在时间窗内接收所述第一数据和所述第二数据，并按照时间顺序对所述第一数据和所述第二数据进行重组；所述时间窗基于所述第一资源和所述第二资源的时域位置确定。
在一种可能的实施方式中，所述第一数据和所述第二数据相同，所述处理单元还用于：将所述第二数据或所述第一数据中成功解码的数据递交到上层，所述上层为MAC层的上层。
在一种可能的实施方式中，所述第一数据和所述第二数据为第三数据的不同冗余版本，所述处理模块1003还用于：根据所述第一数据和所述第二数据的不同冗余版本，合并解码得到第三数据。
当采用硬件形式实现时，本申请实施例中，发送模块1001可以是通信接口、接收器、收发电路等。接收模块1002可以是通信接口、发射器、收发电路等。其中，通信接口是统称，可以包括一个或多个接口。
当发送模块1001是发射器，接收模块1002是接收器时，本申请实施例所涉及的数据传输装置1000可以如图11所示。参阅图11所示，为本申请实施例提供的一种数据传输装置1100。示例性的，该数据传输装置可以为第二设备，该数据传输装置1100可包括发射器1101、接收器1102、处理器1103、存储器1104。其中，存储器1104中存储指令或程序，处理器1103用于执行存储器1104中存储的指令或程序。发射器1101用于执行上述实施例中发送模块1001执行的操作。接收器1102用于执行上述实施例中接收模块1002执行的操作。
应理解，根据本申请实施例的数据传输装置1000或数据传输装置1100可对应于图3、图5、图7所示的实施例中的第二设备，并且数据传输装置1000或数据传输装置1100中的各个模块的操作和/或功能分别为了实现图3、图5、图7所示的实施例中的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM， EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)集成在处理器中。
应注意，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
基于与上述方法实施例相同构思，本申请实施例中还提供一种计算机可读存储介质，其上存储有计算机程序，该程序被处理器执行时，使该计算机执行上述方法实施例、方法实施例的任意一种可能的实现方式中由第一设备或第二设备执行的操作。
基于与上述方法实施例相同构思，本申请还提供一种计算机程序产品，该计算机程序产品在被计算机调用执行时，可以使得计算机实现上述方法实施例、方法实施例的任意一种可能的实现方式中由第一设备或第二设备执行的操作。
基于与上述方法实施例相同构思，本申请还提供一种芯片或芯片***，该芯片可包括处理器。该芯片还可包括存储器(或存储模块)和/或收发器(或通信模块)，或者，该芯片与存储器(或存储模块)和/或收发器(或通信模块)耦合，其中，收发器(或通信模块)可用于支持该芯片进行有线和/或无线通信，存储器(或存储模块)可用于存储程序，该处理器调用该程序可用于实现上述方法实施例、方法实施例的任意一种可能的实现方式中由第一设备或第二设备执行的操作。该芯片***可包括以上芯片，也可以包含上述芯片和其他分立器件，如存储器(或存储模块)和/或收发器(或通信模块)。
基于与上述方法实施例相同构思，本申请还提供一种通信***，该通信***可用于实现上述方法实施例、方法实施例的任意一种可能的实现方式中由第一设备和第二设备执行的操作。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另一点，所显 示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (37)

  1. 一种数据传输方法，其特征在于，包括：
    接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；
    通过所述第一资源向所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
  2. 如权利要求1所述的方法，其特征在于，所述第一资源和第二资源为半静态调度SPS资源。
  3. 如权利要求1所述的方法，其特征在于，所述第一数据和所述第二数据为第一数据包的不同分段。
  4. 如权利要求3所述的方法，其特征在于，所述第一数据包的数据量大小大于第一阈值；或者所述第一资源或所述第二资源不能承载所述第一数据包。
  5. 如权利要求1所述的方法，其特征在于，所述第一数据和所述第二数据相同。
  6. 如权利要求5所述的方法，其特征在于，所述第二数据由第一数据在MAC层复制得到。
  7. 如权利要求5所述的方法，其特征在于，所述第一数据和所述第二数据分别对应不同的混合自动重传请求HARQ进程。
  8. 如权利要求1所述的方法，其特征在于，所述第一数据和所述第二数据为第三数据的不同冗余版本。
  9. 一种数据传输方法，其特征在于，包括：
    向第一设备发送至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；
    通过第一资源接收所述第一设备发送的第一数据，并通过所述第二资源接收所述第一设备发送的第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
  10. 如权利要求9所述的方法，其特征在于，所述第一资源和第二资源为半静态调度SPS资源。
  11. 如权利要求9所述的方法，其特征在于，所述方法还包括：
    将所述第二数据与所述第一数据进行重组，生成第一数据包；其中，所述第一数据和所述第二数据为所述第一数据包的不同分段。
  12. 如权利要求11所述的方法，其特征在于，将所述第二数据与所述第一数据进行重组，包括：
    基于所述第二资源与所述第一资源的时域先后顺序和/或频域先后顺序，或所述第二资源与所述第一资源分别对应的半静态调度SPS标识顺序，将所述第二数据与所述第一数据进行重组。
  13. 如权利要求12所述的方法，其特征在于，所述第一资源在时域上的位置位于所述第二资源在时域上的位置之前，且所述第一数据对应高位字节或高位比特，所述第二数据对应低位字节或低位比特。
  14. 如权利要求11所述的方法，其特征在于，将所述第二数据与所述第一数据进行重 组，包括：
    基于所述第二资源以及所述第一资源组成的图样，将所述第二数据与所述第一数据进行重组。
  15. 如权利要求11所述的方法，其特征在于，将所述第二数据与所述第一数据进行重组，包括：
    在时间窗内接收所述第一数据和所述第二数据，并按照时间顺序对所述第一数据和所述第二数据进行重组；所述时间窗基于所述第一资源和所述第二资源的时域位置确定。
  16. 如权利要求9所述的方法，其特征在于，所述第一数据和所述第二数据相同，所述方法还包括：
    将所述第二数据或所述第一数据中成功解码的数据递交到上层，所述上层为MAC层的上层。
  17. 如权利要求9所述的方法，其特征在于，所述第一数据和所述第二数据为第三数据的不同冗余版本，所述方法还包括：
    根据所述第一数据和所述第二数据的不同冗余版本，合并解码得到第三数据。
  18. 一种数据传输装置，其特征在于，包括：
    接收模块，用于接收第二设备发送的至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；
    发送模块，用于通过所述第一资源向所述第二设备发送第一数据，并通过所述第二资源向所述第二设备发送第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
  19. 如权利要求18所述的装置，其特征在于，所述第一资源和第二资源为半静态调度SPS资源。
  20. 如权利要求18所述的装置，其特征在于，所述第一数据和所述第二数据为第一数据包的不同分段。
  21. 如权利要求20所述的装置，其特征在于，所述第一数据包的数据量大小大于第一阈值；或者所述第一资源或所述第二资源不能承载所述第一数据包。
  22. 如权利要求18所述的装置，其特征在于，所述第一数据和所述第二数据相同。
  23. 如权利要求22所述的装置，其特征在于，所述第二数据由第一数据在MAC层复制得到。
  24. 如权利要求22所述的装置，其特征在于，所述第一数据和所述第二数据分别对应不同的混合自动重传请求HARQ进程。
  25. 如权利要求18所述的装置，其特征在于，所述第一数据和所述第二数据为第三数据的不同冗余版本。
  26. 一种数据传输装置，其特征在于，包括：
    发送模块，用于向第一设备发送至少一个资源配置信息，所述至少一个资源配置信息用于配置第一资源和第二资源；
    接收模块，用于通过第一资源接收所述第一设备发送的第一数据，并通过所述第二资源接收所述第一设备发送的第二数据，所述第一数据和所述第二数据均不包含媒体接入控制MAC层包头信息。
  27. 如权利要求26所述的装置，其特征在于，所述第一资源和第二资源为半静态调 度SPS资源。
  28. 如权利要求26所述的装置，其特征在于，所述装置还包括：处理模块；
    所述处理模块，用于将所述第二数据与所述第一数据进行重组，生成第一数据包；其中，所述第一数据和所述第二数据为所述第一数据包的不同分段。
  29. 如权利要求28所述的装置，其特征在于，所述处理模块具体用于按如下方式将所述第二数据与所述第一数据进行重组：
    基于所述第二资源与所述第一资源的时域先后顺序和/或频域先后顺序，或所述第二资源与所述第一资源分别对应的半静态调度标识顺序，将所述第二数据与所述第一数据进行重组。
  30. 如权利要求29所述的装置，其特征在于，所述第一资源在时域上的位置位于所述第二资源在时域上的位置之前，且所述第一数据对应高位字节或高位比特，所述第二数据对应低位字节或低位比特。
  31. 如权利要求28所述的装置，其特征在于，所述处理模块具体用于按如下方式将所述第二数据与所述第一数据进行重组：
    基于所述第二资源以及所述第一资源组成的图样，将所述第二数据与所述第一数据进行重组。
  32. 如权利要求28所述的装置，其特征在于，所述处理模块具体用于按如下方式将所述第二数据与所述第一数据进行重组：
    在时间窗内接收所述第一数据和所述第二数据，并按照时间顺序对所述第一数据和所述第二数据进行重组；所述时间窗基于所述第一资源和所述第二资源的时域位置确定。
  33. 如权利要求26所述的装置，其特征在于，所述第一数据和所述第二数据相同，所述处理模块还用于：将所述第二数据或所述第一数据中成功解码的数据递交到上层，所述上层为MAC层的上层。
  34. 如权利要求26所述的装置，其特征在于，所述第一数据和所述第二数据为第三数据的不同冗余版本，所述处理模块还用于：根据所述第一数据和所述第二数据的不同冗余版本，合并解码得到第三数据。
  35. 一种数据传输装置，其特征在于，包括：处理器和存储器；所述存储器用于存储一个或多个程序，所述一个或多个程序包括计算机执行指令，当该装置运行时，所述处理器执行所述存储器存储的所述一个或多个程序以使该装置执行如权利要求1-8中任一项所述的方法。
  36. 一种数据传输装置，其特征在于，包括：处理器和存储器；所述存储器用于存储一个或多个程序，所述一个或多个程序包括计算机执行指令，当该装置运行时，所述处理器执行所述存储器存储的所述一个或多个程序以使该装置执行如权利要求9-17中任一项所述的方法。
  37. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机程序，当所述计算机程序被运行时，实现如权利要求1-8中任一项所述的方法或实现如权利要求9-17中任一项所述的方法。
PCT/CN2020/105849 2020-07-30 2020-07-30 一种数据传输方法及装置 WO2022021220A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202080004797.6A CN112640564A (zh) 2020-07-30 2020-07-30 一种数据传输方法及装置
PCT/CN2020/105849 WO2022021220A1 (zh) 2020-07-30 2020-07-30 一种数据传输方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/105849 WO2022021220A1 (zh) 2020-07-30 2020-07-30 一种数据传输方法及装置

Publications (1)

Publication Number Publication Date
WO2022021220A1 true WO2022021220A1 (zh) 2022-02-03

Family

ID=75291159

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/105849 WO2022021220A1 (zh) 2020-07-30 2020-07-30 一种数据传输方法及装置

Country Status (2)

Country Link
CN (1) CN112640564A (zh)
WO (1) WO2022021220A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114913624A (zh) * 2022-03-23 2022-08-16 中国第一汽车股份有限公司 域控制器间数据共享方法、车机***及车辆
CN116186613A (zh) * 2023-05-04 2023-05-30 利维智能（深圳）有限公司 工业互联网数据的智能采集处理方法及***

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014161139A1 (zh) * 2013-04-01 2014-10-09 华为技术有限公司 数据传输方法、用户设备、基站和无线网络控制器
WO2017166141A1 (zh) * 2016-03-30 2017-10-05 广东欧珀移动通信有限公司 数据传输的方法、终端及基站
CN110035507A (zh) * 2018-01-12 2019-07-19 中国信息通信研究院 一种移动通讯上行信息传输方法和***
CN110536445A (zh) * 2019-04-30 2019-12-03 中兴通讯股份有限公司 Ue信息的报告方法、车辆网资源配置方法及装置
US20200128376A1 (en) * 2017-08-03 2020-04-23 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for indicating multi-service data multiplex transmission, terminal and base station

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8165152B2 (en) * 2008-02-01 2012-04-24 Interdigital Patent Holdings, Inc. Method and apparatus for prioritizing logical channels
CN108023665A (zh) * 2016-11-03 2018-05-11 中兴通讯股份有限公司 一种数据传输方法及装置、电子设备
CN108337214B (zh) * 2017-01-20 2020-01-10 华为技术有限公司 一种数据处理方法，终端和网络设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014161139A1 (zh) * 2013-04-01 2014-10-09 华为技术有限公司 数据传输方法、用户设备、基站和无线网络控制器
WO2017166141A1 (zh) * 2016-03-30 2017-10-05 广东欧珀移动通信有限公司 数据传输的方法、终端及基站
US20200128376A1 (en) * 2017-08-03 2020-04-23 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for indicating multi-service data multiplex transmission, terminal and base station
CN110035507A (zh) * 2018-01-12 2019-07-19 中国信息通信研究院 一种移动通讯上行信息传输方法和***
CN110536445A (zh) * 2019-04-30 2019-12-03 中兴通讯股份有限公司 Ue信息的报告方法、车辆网资源配置方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114913624A (zh) * 2022-03-23 2022-08-16 中国第一汽车股份有限公司 域控制器间数据共享方法、车机***及车辆
CN114913624B (zh) * 2022-03-23 2023-10-27 中国第一汽车股份有限公司 域控制器间数据共享方法、车机***及车辆
CN116186613A (zh) * 2023-05-04 2023-05-30 利维智能（深圳）有限公司 工业互联网数据的智能采集处理方法及***

Also Published As

Publication number Publication date
CN112640564A (zh) 2021-04-09

Similar Documents

Publication Publication Date Title
US20230327802A1 (en) Data transmission method and data transmission device
WO2022021220A1 (zh) 一种数据传输方法及装置
CN113228717B (zh) 一种通信方法及装置
CN113630738A (zh) 一种侧行链路通信方法及装置
WO2019238066A1 (zh) 用于无线通信***的电子设备、方法和存储介质
WO2022029664A1 (en) Indicating source and destination devices
WO2019029739A1 (zh) 一种多载频传输方法、设备及***
WO2021000937A1 (zh) 多时间单元传输方法及相关装置
US20230064935A1 (en) Data transmission method, apparatus, and system
US20230224105A1 (en) Communication Method and Apparatus
US20230139029A1 (en) Communications method and apparatus
WO2021227076A1 (zh) 一种通信方法、装置及***
WO2021062849A1 (zh) 缓冲状态报告上报方法及通信装置
WO2022198463A1 (zh) 一种通信方法与装置
WO2023165235A1 (zh) 半静态调度方法、用户设备、基站及通信***
WO2023165247A1 (zh) 半静态调度方法、用户设备、基站及通信***
WO2023185956A1 (zh) 基于侧行链路的通信方法、装置、存储介质和芯片***
WO2022193225A1 (zh) 一种突发监测的方法和装置
WO2023000710A1 (zh) 处理广播信息的方法和装置
WO2021163929A1 (zh) 业务传输的方法和通信装置
JP2023523366A (ja) データ通信方法および関連装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20947541

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20947541

Country of ref document: EP

Kind code of ref document: A1