WO2019024399A1 - 支持数据重复的方法、发射端设备和接收端设备 - Google Patents

支持数据重复的方法、发射端设备和接收端设备 Download PDF

Info

Publication number
WO2019024399A1
WO2019024399A1 PCT/CN2017/117778 CN2017117778W WO2019024399A1 WO 2019024399 A1 WO2019024399 A1 WO 2019024399A1 CN 2017117778 W CN2017117778 W CN 2017117778W WO 2019024399 A1 WO2019024399 A1 WO 2019024399A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
radio bearer
header
end device
indication field
Prior art date
Application number
PCT/CN2017/117778
Other languages
English (en)
French (fr)
Inventor
唐海
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to MX2020001219A priority Critical patent/MX2020001219A/es
Priority to JP2019571489A priority patent/JP7083854B2/ja
Priority to RU2020101950A priority patent/RU2762931C2/ru
Priority to SG11201911811SA priority patent/SG11201911811SA/en
Priority to CA3066605A priority patent/CA3066605A1/en
Priority to US16/625,636 priority patent/US11284296B2/en
Priority to CN202010072503.5A priority patent/CN111212398B/zh
Priority to EP18841323.1A priority patent/EP3627735B1/en
Priority to AU2018310941A priority patent/AU2018310941A1/en
Priority to KR1020197038197A priority patent/KR20200036814A/ko
Priority to BR112019027828-1A priority patent/BR112019027828A2/pt
Priority to CN201880037596.9A priority patent/CN110731061A/zh
Priority to PCT/CN2018/078892 priority patent/WO2019024504A1/zh
Priority to TW107127176A priority patent/TWI785085B/zh
Publication of WO2019024399A1 publication Critical patent/WO2019024399A1/zh
Priority to IL271166A priority patent/IL271166A/en
Priority to ZA2019/08390A priority patent/ZA201908390B/en
Priority to PH12019502858A priority patent/PH12019502858A1/en
Priority to CL2020000032A priority patent/CL2020000032A1/es

Links

Images

Classifications

    • 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/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • 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/02—Arrangements for detecting or preventing errors in the information received by diversity reception
    • H04L1/04—Arrangements for detecting or preventing errors in the information received by diversity reception using frequency diversity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • 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/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application relates to the field of communications, and more particularly to a method for supporting data repetition, a transmitting end device, and a receiving end device.
  • Vehicle networking or Vehicle to Everything (V2X) communication system is a side-link (SideLink, SL) transmission technology based on Device to Device (D2D) communication, with traditional long-term evolution ( In the Long Term Evolution (LTE) system, the communication data is received or transmitted by the base station in different ways.
  • the vehicle networking system adopts the terminal-to-terminal direct communication mode, and thus has higher spectrum efficiency and lower transmission delay.
  • the embodiment of the present application provides a method for supporting data repetition, a transmitting end device, and a receiving end device, which can implement reliable transmission of repeated data in a car network system.
  • an embodiment of the present application provides a method for supporting data repetition, including:
  • the transmitting end device sends a plurality of radio link control protocol data unit RLC PDUs to the receiving end device, where the RLC packet header of the at least one RLC PDU includes an indication field, where the indication field is used to indicate the current RLC
  • the radio bearer corresponding to the PDU sends a plurality of radio link control protocol data unit RLC PDUs to the receiving end device, where the RLC packet header of the at least one RLC PDU includes an indication field, where the indication field is used to indicate the current RLC The radio bearer corresponding to the PDU.
  • the transmitting device may be a terminal device.
  • the receiving end device may be a terminal device or a network device (for example, a base station).
  • the transmitting device when transmitting multiple RLC PDUs, may include the current RLC PDU in the RLC header of at least one of the plurality of RLC PDUs.
  • the indication field of the corresponding radio bearer so that the receiving end device can determine the radio bearer corresponding to each RLC PDU in the plurality of RLC PDUs, thereby enabling reliable transmission of duplicate data.
  • the indication field includes an identifier ID of a radio bearer corresponding to a packet data convergence protocol (PDCP) corresponding to the current RLC PDU.
  • PDCP packet data convergence protocol
  • the indication field includes an identifier ID of the logical channel.
  • the RLC packet header of the at least one RLC PDU is:
  • the RLC packet header of the at least one RLC PDU is:
  • the RLC packet header is used to form a MAC subheader.
  • At least two RLC PDUs of the multiple RLC PDUs correspond to different logical channels, and the at least two RLC PDUs correspond to the same radio bearer.
  • the method is applied to a vehicle networking system.
  • an embodiment of the present application provides a method for supporting data repetition, including:
  • the receiving end device receives a plurality of radio link control protocol data units RLC PDUs sent by the transmitting end device;
  • the receiving end device determines, according to the correspondence between the logical channel and the radio bearer, the radio bearer corresponding to each RLC PDU of the multiple RLC PDUs.
  • the receiving end device may determine each RLC PDU of the multiple RLC PDUs according to the correspondence between the logical channel and the radio bearer. Corresponding radio bearers, in turn, enable reliable transmission of duplicate data.
  • the RLC packet header of the at least one RLC PDU of the multiple RLC PDUs includes an indication domain, where the indication domain includes a radio bearer corresponding to the current RLC PDU.
  • the method further includes:
  • the RLC packet header of the at least one RLC PDU of the multiple RLC PDUs includes an indication domain, where the indication domain includes an identifier ID of the logical channel;
  • the method further includes:
  • the correspondence between the logical channel and the radio bearer is pre-configured.
  • At least two RLC PDUs of the multiple RLC PDUs correspond to different logical channels, and the at least two RLC PDUs correspond to the same radio bearer.
  • the method is applied to a vehicle networking system.
  • the RLC packet header of the at least one RLC PDU is:
  • the RLC packet header of the at least one RLC PDU is:
  • the RLC packet header is used to form a MAC subheader.
  • the embodiment of the present application provides a transmitting end device, which can execute the module or unit of the method in the first aspect or any optional implementation manner of the first aspect.
  • the embodiment of the present application provides a receiving end device, which can execute the module or unit of the method in the second aspect or any optional implementation manner of the second aspect.
  • a transmitter device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a receiving end device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is used to store instructions
  • the processor is used to execute the instructions
  • the communication interface is used to communicate with other network elements under the control of the processor.
  • a computer storage medium storing program code for instructing a computer to perform the method of any of the first aspect or the first aspect of the first aspect. instruction.
  • a computer storage medium storing program code for instructing a computer to perform the method in any one of the possible implementation manners of the second aspect or the second aspect instruction.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 is a schematic diagram of another application scenario of an embodiment of the present application.
  • FIG. 3 is a schematic diagram of data transmission by carrier aggregation in the embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for supporting data repetition according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another method for supporting data repetition according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a transmitting end device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a receiving end device according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of an apparatus for supporting data repetition provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a system chip according to an embodiment of the present application.
  • the technical solutions of the embodiments of the present application may be applied to a vehicle networking system, and the vehicle networking system may be based on various communication systems, for example, an LTE-D2D-based vehicle networking system.
  • Communication data between terminals in a conventional LTE system is differently received or transmitted by a network device (for example, a base station), and the vehicle networking system adopts a terminal-to-terminal direct communication method, thereby having higher spectral efficiency and lower Transmission delay.
  • the communication system based on the Internet of Vehicles system may be a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, and a Wideband Code Division Multiple Access (Wideband Code Division). Multiple Access, WCDMA) System, General Packet Radio Service (GPRS), LTE System, LTE Frequency Division Duplex (FDD) System, LTE Time Division Duplex (TDD), General Purpose Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, New Radio (NR) or future 5G systems.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • Wideband Code Division Multiple Access Wideband Code Division Multiple Access
  • Multiple Access WCDMA) System
  • GPRS General Packet Radio Service
  • LTE System LTE Frequency Division Duplex
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS General Purpose Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the terminal device in the embodiment of the present application may be an in-vehicle terminal device, or may be a terminal device in a future 5G network or a terminal device in a public land mobile communication network (PLMN) in a future evolution.
  • PLMN public land mobile communication network
  • the example is not limited.
  • the present application describes various embodiments in connection with a network device.
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, where the network device may be a Base Transceiver Station (BTS) in GSM or CDMA, or may be a base station (NodeB, NB) in a WCDMA system. And may be an evolved base station (eNB or eNodeB) in the LTE system, or may be a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be
  • the embodiments of the present application are not limited to the relay station, the access point, the in-vehicle device, the wearable device, and the network device in the future 5G network or the network device in the future evolved PLMN network.
  • FIG. 1 and FIG. 2 are schematic diagrams of an application scenario of an embodiment of the present application.
  • FIG. 1 exemplarily shows a network device and two terminal devices.
  • the wireless communication system in the embodiment of the present application may include multiple network devices and may include other numbers in the coverage of each network device.
  • the terminal device is not limited in this embodiment of the present application.
  • the wireless communication system may further include other network entities such as a Mobile Management Entity (MME), a Serving Gateway (S-GW), and a Packet Data Network Gateway (P-GW).
  • MME Mobile Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • embodiments of the present application are not limited thereto.
  • the terminal device 20 and the terminal device 30 can communicate in a D2D communication mode.
  • the terminal device 20 and the terminal device 30 directly communicate via a D2D link, ie, a side link (Sidelink, SL).
  • a side link Sidelink, SL
  • the terminal device 20 and the terminal device 30 directly communicate through the side line.
  • the terminal device 20 and the terminal device 30 communicate by a side line, and the transmission resources thereof are allocated by the network device; in FIG. 2, the terminal device 20 and the terminal device 30 pass the side link. Communication, whose transmission resources are independently selected by the terminal device, does not require the network device to allocate transmission resources.
  • the D2D communication may refer to a vehicle to vehicle (V2V) communication or a vehicle to Everything (V2X) communication.
  • V2X communication X can refer to any device with wireless receiving and transmitting capabilities, such as but not limited to slow moving wireless devices, fast moving in-vehicle devices, or network control nodes with wireless transmit and receive capabilities. It should be understood that the embodiment of the present invention is mainly applied to the scenario of V2X communication, but can also be applied to any other D2D communication scenario, which is not limited in this embodiment.
  • a terminal device having a listening capability such as a Vehicle User Equipment (VUE) or a Pedestrian User Equipment (PUE), and no listening.
  • VUE Vehicle User Equipment
  • PUE Pedestrian User Equipment
  • Capable terminal equipment such as PUE.
  • VUE has higher processing power and is usually powered by the battery in the car, while PUE has lower processing power, and reducing power consumption is also a major factor that PUE needs to consider. Therefore, in the existing car network system, VUE is considered to have Full reception and listening capabilities; while PUE is considered to have partial or no reception and listening capabilities.
  • the resource may be selected by using a similar listening method as the VUE, and the available resources may be selected on the part of the resources that can be intercepted; if the PUE does not have the listening capability, the PUE is in the resource pool. Randomly select transmission resources.
  • transmission mode 3 (mode 3) and transmission mode 4 (mode 4).
  • the transmission resource of the terminal device using the transmission mode 3 is allocated by the base station, and the terminal device performs data transmission on the side line according to the resource allocated by the base station; the base station may allocate the resource for the single transmission to the terminal device, or may be the terminal.
  • the device allocates resources that are semi-statically transmitted. If the terminal device using the transmission mode 4 has the capability of listening, the data is transmitted by means of sensing and reservation. If the listening capability is not available, the transmission resource is randomly selected in the resource pool.
  • the terminal device with the listening capability acquires the available resource set by means of interception in the resource pool, and the terminal device randomly selects one resource from the set for data transmission. Since the service in the car network system has periodic characteristics, the terminal device usually adopts a semi-static transmission mode, that is, after the terminal device selects one transmission resource, the terminal device continuously uses the resource in multiple transmission cycles, thereby reducing the resource weight. The probability of selection and resource conflicts.
  • the terminal device carries the information for reserving the next transmission resource in the control information of the current transmission, so that the other terminal device can determine whether the resource is reserved and used by the terminal device by detecting the control information of the terminal device. Reduce the purpose of resource conflicts.
  • the resource pool of the transmission mode 4 is pre-configured or configured by the base station, so there is no overlap of the resource pools, that is, the transmission mode 3 and the transmission mode 4 respectively correspond to each other.
  • the resource pools are separated or not overlapped, and the terminal device using mode 3 performs data transmission on the time-frequency resources in the resource pool supporting mode 3, and the terminal device in mode 4 supports the time-frequency resources in the resource pool of mode 4. Data transfer is performed.
  • two transmission modes such as the transmission mode 3 and the transmission mode 4 described above are also supported.
  • the terminal device of Release-15 and the terminal device of Release-14 jointly perform data transmission in the communication system, for the terminal device with the listening capability, the resource can be selected through resource sensing, and for the terminal device without the listening capability. It is difficult to avoid interference with data transmission of other terminal devices. Since the terminal device using the transmission mode 3 is connected to the base station, and its transmission resource is allocated by the base station, when the terminal device using the transmission mode 3 and the terminal device using the transmission mode 4 coexist, it is more necessary to protect the transmission mode 3 The transmission reliability of the terminal equipment.
  • the terminal device may send the same PDCP layer data to the network device or other terminal device through two carriers according to a carrier aggregation manner.
  • one PDCP entity is bound to two RLC entities.
  • the terminal device performs duplication of the first PDCP PDU to be sent to obtain a second PDCP PDU.
  • the terminal device delivers the first PDCP PDU to one of the two RLC entities, RLC 1, and delivers the second PDCP PDU to another RLC entity RLC 2 of the two RLC entities.
  • the two RLC entities respectively process the received PDCP PDU, and send the first PDCP PDU and the second PDCP PDU to the network device or other terminal device through two different carriers.
  • the terminal device may perform the reverse process of the data transmission process as shown in FIG. 3 when receiving data transmitted by the network device or other terminal device.
  • the term "article of manufacture” as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or media.
  • the computer readable medium may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape, etc.), such as a compact disc (CD), a digital versatile disc (Digital Versatile Disc, DVD). Etc.), smart cards and flash memory devices (eg, Erasable Programmable Read-Only Memory (EPROM), cards, sticks or key drivers, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, a variety of media capable of storing, containing, and/or carrying instructions and/or data.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • FIG. 4 is a schematic flowchart of a method 200 for supporting data repetition according to an embodiment of the present application.
  • the method 200 may be performed by a transmitting device, which may be a terminal device as shown in FIG. 1 or FIG. 2, and the terminal device may perform data transmission as shown in FIG.
  • the receiving end device in the method 200 may be a network device as shown in FIG. 1 or a terminal device as shown in FIG. 1 or FIG. 2, and the method 200 may be applied to a car network system.
  • the method 200 includes the following.
  • the transmitting end device sends a plurality of RLC PDUs to the receiving end device, where the RLC packet header of the at least one RLC PDU includes an indication field, where the indication field is used to indicate the wireless corresponding to the current RLC PDU. Hosted.
  • the indication domain is required to indicate the radio bearer corresponding to the current RLC PDU.
  • the indication field includes an identifier (Identity, ID) of the radio bearer corresponding to the PDCP corresponding to the current RLC PDU.
  • the indication field includes an identification ID of the logical channel.
  • the RLC header of the at least one RLC PDU is:
  • At least two RLC PDUs of the multiple RLC PDUs correspond to different logical channels, and the at least two RLC PDUs correspond to the same radio bearer.
  • the transmitting device when transmitting multiple RLC PDUs, may include the current RLC PDU in the RLC header of at least one of the plurality of RLC PDUs.
  • the indication field of the corresponding radio bearer so that the receiving end device can determine the radio bearer corresponding to each RLC PDU of the multiple RLC PDUs, thereby enabling reliable transmission of duplicate data.
  • FIG. 5 is a schematic flowchart of a method 300 for supporting data repetition according to an embodiment of the present application.
  • the method 300 may be performed by a receiving end device, which may be a network device as shown in FIG. 1 or a terminal device as shown in FIG. 1 or FIG.
  • the transmitting end device may be a terminal device as shown in FIG. 1 or FIG. 2, and the terminal device may perform data transmission as shown in FIG. 3, and the method 300 may be applied to a car network system.
  • the method 300 includes the following.
  • the receiving end device receives multiple RLC PDUs sent by the transmitting end device.
  • an indication field is included in an RLC message header of at least one of the plurality of RLC PDUs.
  • the indication field includes a radio bearer corresponding to the current RLC PDU.
  • the indication field includes an identification ID of the logical channel.
  • the receiving end device determines, according to the indication field included in the RLC header of the at least one RLC PDU, a correspondence between the logical channel and the radio bearer.
  • the indication field may only contain 1 bit of content.
  • the indication domain may only contain 1 bit of content.
  • the radio bearer corresponding to the current RLC PDU may be indicated.
  • the correspondence between the logical channel and the radio bearer is pre-configured, for example, by a protocol.
  • a logical channel identity (LC ID) allocation table as shown in Table 1 below may allocate 01011-10100 from the reserved index to the RLC for data duplication services, for example, logical Channel 00001 and logical channel 01011 will jointly serve the PDCP entity for bearer 1, and logical channel 00010 and logical channel 01100 will jointly serve the PDCP entity for bearer 2.
  • LC ID logical channel identity
  • the RLC header of the at least one RLC PDU is:
  • the RLC PDU there may be two corresponding manners in the RLC PCU and the RLC packet header, where the RLC PDU is in a corresponding relationship with the RLC packet header, that is, in this relationship, the RLC PDU may not be
  • the RLC header is included, and the RLC header is included in the RLC PDU.
  • the RLC header can form a MAC sub-header; thus, the RLC PDU and the MAC sub-header can be utilized.
  • the RLC header is combined with the MAC header to form the data unit of the MAC layer.
  • the RLC PDU includes an RLC header.
  • the RLC PDU constitutes a data unit of the MAC layer.
  • the data unit of the MAC layer may be a MAC PDU.
  • the receiving end device determines, according to a correspondence between the logical channel and the radio bearer, a radio bearer corresponding to each RLC PDU of the multiple RLC PDUs.
  • the receiving end device may determine each RLC PDU of the multiple RLC PDUs according to the correspondence between the logical channel and the radio bearer. Corresponding radio bearers, in turn, enable reliable transmission of duplicate data.
  • FIG. 6 is a schematic block diagram of a transmitting end device 400 according to an embodiment of the present application. As shown in FIG. 6, the transmitting device 400 includes:
  • the sending unit 410 is configured to send, by the receiving end device, a plurality of radio link control protocol data units, the RLC PDU, where the RLC packet header of the at least one of the plurality of RLC PDUs includes an indication field, where the indication field is used to indicate The radio bearer corresponding to the current RLC PDU.
  • the indication field includes an identifier ID of the radio bearer corresponding to the packet data convergence protocol PDCP corresponding to the current RLC PDU.
  • the indication field includes an identification ID of the logical channel.
  • At least two RLC PDUs of the multiple RLC PDUs correspond to different logical channels, and the at least two RLC PDUs correspond to the same radio bearer.
  • the transmitting device 400 is applied to a car network system.
  • FIG. 7 is a schematic block diagram of a receiving end device 500 according to an embodiment of the present application. As shown in FIG. 7, the receiving device 500 includes:
  • the receiving unit 510 is configured to receive multiple radio link control protocol data units RLC PDUs sent by the transmitting device;
  • the processing unit 520 is configured to determine, according to a correspondence between the logical channel and the radio bearer, a radio bearer corresponding to each RLC PDU of the multiple RLC PDUs.
  • the RLC packet header of the at least one RLC PDU of the multiple RLC PDUs includes an indication domain, where the indication domain includes a radio bearer corresponding to the current RLC PDU.
  • the processing unit 520 Before the processing unit 520 determines the radio bearer corresponding to each RLC PDU in the multiple RLC PDUs according to the correspondence between the logical channel and the radio bearer, the processing unit 520 is further configured to use the RLC report according to the at least one RLC PDU.
  • An indication field included in the header determines a correspondence between the logical channel and the radio bearer.
  • the RLC packet header of the at least one RLC PDU of the multiple RLC PDUs includes an indication domain, where the indication domain includes an identifier ID of the logical channel;
  • the processing unit 520 Before the processing unit 520 determines the radio bearer corresponding to each RLC PDU in the multiple RLC PDUs according to the correspondence between the logical channel and the radio bearer, the processing unit 520 is further configured to use the RLC report according to the at least one RLC PDU.
  • An indication field included in the header determines a correspondence between the logical channel and the radio bearer.
  • the correspondence between the logical channel and the radio bearer is pre-configured.
  • At least two RLC PDUs of the multiple RLC PDUs correspond to different logical channels, and the at least two RLC PDUs correspond to the same radio bearer.
  • the receiving end device 500 is applied to a car network system.
  • FIG. 8 is a schematic block diagram of an apparatus 600 for supporting data repetition according to an embodiment of the present application.
  • the apparatus 600 includes:
  • a memory 610 configured to store a program, where the program includes code
  • the transceiver 620 is configured to communicate with other devices;
  • the processor 630 is configured to execute program code in the memory 610.
  • the processor 630 can also implement various operations performed by the transmitting device in the method 200 in FIG. 4, and details are not described herein for brevity.
  • the device 600 may be a terminal device, for example, an in-vehicle terminal.
  • the processor 630 can implement various operations performed by the receiving device in the method 300 in FIG. 5, and details are not described herein for brevity.
  • the device 600 may be an access network device or a core network device.
  • the transceiver 620 is configured to perform specific signal transceiving under the driving of the processor 630.
  • the processor 630 may be a central processing unit (CPU), and the processor 630 may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 610 can include read only memory and random access memory and provides instructions and data to the processor 630. A portion of the memory 610 may also include a non-volatile random access memory. For example, the memory 610 can also store information of the device type.
  • the transceiver 620 can be used to implement signal transmission and reception functions, such as frequency modulation and demodulation functions or upconversion and down conversion functions.
  • At least one of the steps of the above method may be performed by integrated logic of hardware in the processor 630, or the integrated logic may be driven by instructions in software form to perform the at least one step.
  • device 600 that supports data duplication can be a chip or chipset.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor 630 reads the information in the memory and completes the steps of the above method in combination with the hardware thereof. To avoid repetition, it will not be described in detail here.
  • FIG. 9 is a schematic structural diagram of a system chip 700 according to an embodiment of the present application.
  • the system chip 700 of FIG. 9 includes an input interface 701, an output interface 702, a processor 703, and a memory 704 that can be connected by an internal communication connection line.
  • the processor 703 is configured to execute code in the memory 704.
  • the processor 703 implements the method performed by the transmitting device in the method embodiment. For the sake of brevity, it will not be repeated here.
  • the processor 703 when the code is executed, the processor 703 implements a method performed by the receiving device in the method embodiment. For the sake of brevity, it will not be repeated here.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be wired from a website site, computer, server or data center (for example, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Communication Control (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

本申请实施例提供了一种支持数据重复的方法、发射端设备和接收端设备，能够实现车联网系统中重复数据的可靠传输。该方法包括：发射端设备向接收端设备发送多个无线链路控制协议数据单元RLC PDU，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域用于指示当前的RLC PDU所对应的无线承载。

Description

支持数据重复的方法、发射端设备和接收端设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种支持数据重复的方法、发射端设备和接收端设备。
背景技术
车联网或称车对设备(Vehicle to Everything，V2X)通信系统是基于设备对设备(Device to Device，D2D)通信的一种侧行链路(SideLink，SL)传输技术，与传统的长期演进(Long Term Evolution，LTE)系统中通信数据通过基站接收或者发送的方式不同，车联网系统采用终端到终端直接通信的方式，因此具有更高的频谱效率以及更低的传输时延。
在车联网系统中，对数据传输的可靠性要求较高，如何实现数据的可靠性传输是一项亟待解决的问题。
发明内容
本申请实施例提供了一种支持数据重复的方法、发射端设备和接收端设备，能够实现车联网系统中重复数据的可靠传输。
第一方面，本申请实施例提供了一种支持数据重复的方法，包括：
发射端设备向接收端设备发送多个无线链路控制协议数据单元RLC PDU，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域用于指示当前的RLC PDU所对应的无线承载。
可选地，发射端设备可以是终端设备。
可选地，接收端设备可以是终端设备，也可以是网络设备(例如，基站)。
因此，在本申请实施例的支持数据重复的方法中，发射端设备在发送多个RLC PDU时，可以在多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示当前的RLC PDU所对应的无线承载的指示域，从而，接收端设备可以确定多个RLC PDU中每个RLC PDU对应的无线承载，进而，能够实现重复数据的可靠传输。
可选地，在第一方面的一种实现方式中，该指示域包括当前的RLC PDU所对应的分组数据汇聚协议PDCP对应的无线承载的标识ID。
可选地，在第一方面的一种实现方式中，该指示域包括逻辑信道的标识ID。
可选地，在第一方面的一种实现方式中，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU所对应的RLC报文头。
可选地，在第一方面的一种实现方式中，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU中所包含的RLC报文头。
可选地，在第一方面的一种实现方式中，所述RLC报文头，用于构成MAC子头。
可选地，在第一方面的一种实现方式中，该多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及该至少两个RLC PDU对应相同的无线承载。
可选地，在第一方面的一种实现方式中，该方法应用于车联网系统。
第二方面，本申请实施例提供了一种支持数据重复的方法，包括：
接收端设备接收发射端设备发送的多个无线链路控制协议数据单元RLC PDU；
该接收端设备根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载。
因此，在本申请实施例的支持数据重复的方法中，接收端设备在接收到多个RLC PDU时，可以根据逻辑信道与无线承载之间的对应关系，确定多个RLC PDU中每个RLC PDU对应的无线承载，进而，能够实现重复数据的可靠传输。
可选地，在第一方面的一种实现方式中，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域包括当前的RLC PDU所对应的无线承载；
在该根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载之前，该方法还包括：
根据该至少一个RLC PDU的RLC报文头中包括的指示域，确定该逻辑信道与该无线承载之间的对应关系。
可选地，在第一方面的一种实现方式中，该多个RLC PDU中的至少一 个RLC PDU的RLC报文头中包括指示域，该指示域包括逻辑信道的标识ID；
在该根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载之前，该方法还包括：
根据该至少一个RLC PDU的RLC报文头中包括的指示域，确定该逻辑信道与该无线承载之间的对应关系。
可选地，在第一方面的一种实现方式中，该逻辑信道与该无线承载之间的对应关系是预配置的。
可选地，在第一方面的一种实现方式中，该多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及该至少两个RLC PDU对应相同的无线承载。
可选地，在第一方面的一种实现方式中，该方法应用于车联网系统。
可选地，在第一方面的一种实现方式中，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU所对应的RLC报文头。
可选地，在第一方面的一种实现方式中，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU中所包含的RLC报文头。
可选地，在第一方面的一种实现方式中，所述RLC报文头，用于构成MAC子头。
第三方面，本申请实施例提供了一种发射端设备，可以执行第一方面或第一方面的任一可选的实现方式中的方法的模块或者单元。
第四方面，本申请实施例提供了一种接收端设备，可以执行第二方面或第二方面的任一可选的实现方式中的方法的模块或者单元。
第五方面，提供了一种发射端设备，该发射端设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令，处理器用于执行该指令，通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种接收端设备，该接收端设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令，处理 器用于执行该指令，通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种计算机存储介质，该计算机存储介质中存储有程序代码，该程序代码用于指示计算机执行上述第一方面或第一方面的任一种可能的实现方式中的方法的指令。
第八方面，提供了一种计算机存储介质，该计算机存储介质中存储有程序代码，该程序代码用于指示计算机执行上述第二方面或第二方面的任一种可能的实现方式中的方法的指令。
第九方面，提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1是本申请实施例一个应用场景的示意图。
图2是本申请实施例另一个应用场景的示意图。
图3是本申请实施例通过载波聚合进行数据传输的示意图。
图4是根据本申请实施例的一种支持数据重复的方法的示意性流程图。
图5是根据本申请实施例的另一种支持数据重复的方法的示意性流程图。
图6是根据本申请实施例的一种发射端设备的示意性框图。
图7是根据本申请实施例的一种接收端设备的示意性框图。
图8示出了本申请实施例提供的支持数据重复的设备的示意性框图。
图9是根据本申请实施例的系统芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
应理解，本申请实施例的技术方案可以应用于车联网系统，车联网系统可以基于各种通信系统，例如，基于LTE-D2D的车联网系统。与传统的LTE系统中终端之间的通信数据通过网络设备(例如，基站)接收或者发送的方式不同，车联网系统采用终端到终端直接通信的方式，因此具有更高的频谱 效率以及更低的传输时延。
可选地，车联网系统基于的通信系统可以是全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、LTE系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、新无线(New Radio，NR)或未来的5G系统等。
本申请实施例中的终端设备可以指车载终端设备，也可以是未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例并不限定。
本申请结合网络设备描述了各个实施例。本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
图1和图2是本申请实施例的一个应用场景的示意图。图1示例性地示出了一个网络设备和两个终端设备，可选地，本申请实施例中的无线通信系统可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。此外，该无线通信系统还可以包括移动管理实体(Mobile Management Entity，MME)、服务网关(Serving Gateway，S-GW)、分组数据网络网关(Packet Data Network Gateway，P-GW)等其他网络实体，但本申请实施例不限于此。
具体地，终端设备20和终端设备30可以D2D通信模式进行通信，在进行D2D通信时，终端设备20和终端设备30通过D2D链路即侧行链路(Sidelink上，SL)直接进行通信。例如图1或者图2所示，终端设备20 和终端设备30通过侧行链路直接进行通信。在图1中，终端设备20和终端设备30之间通过侧行链路通信，其传输资源是由网络设备分配的；在图2中，终端设备20和终端设备30之间通过侧行链路通信，其传输资源是由终端设备自主选取的，不需要网络设备分配传输资源。
D2D通信可以指车对车(Vehicle to Vehicle，简称“V2V”)通信或车辆到其他设备(Vehicle to Everything，V2X)通信。在V2X通信中，X可以泛指任何具有无线接收和发送能力的设备，例如但不限于慢速移动的无线装置，快速移动的车载设备，或是具有无线发射接收能力的网络控制节点等。应理解，本发明实施例主要应用于V2X通信的场景，但也可以应用于任意其它D2D通信场景，本申请实施例对此不做任何限定。
在车联网系统中，可以存在两种类型的终端设备，即具有侦听能力的终端设备例如车载终端(Vehicle User Equipment，VUE)或行人手持终端(Pedestrian User Equipment，PUE)，以及不具有侦听能力的终端设备例如PUE。VUE具有更高的处理能力，并且通常通过车内的蓄电池供电，而PUE处理能力较低，降低功耗也是PUE需要考虑的一个主要因素，因此在现有的车联网系统中，VUE被认为具有完全的接收能力和侦听能力；而PUE被认为具有部分或者不具有接收和侦听能力。如果PUE具有部分侦听能力，其资源的选取可以采用和VUE类似的侦听方法，在可侦听的那部分资源上进行可用资源的选取；如果PUE不具有侦听能力，则PUE在资源池中随机选取传输资源。
在3GPP协议的版本Release-14中，定义了两种传输模式，即传输模式3(mode 3)和传输模式4(mode 4)。使用传输模式3的终端设备的传输资源是由基站分配的，终端设备根据基站分配的资源在侧行链路上进行数据的发送；基站可以为终端设备分配单次传输的资源，也可以为终端设备分配半静态传输的资源。使用传输模式4的终端设备如果具备侦听能力，采用侦听(sensing)和预留(reservation)的方式传输数据，如果不具备侦听能力，则在资源池中随机选取传输资源。具侦听能力的终端设备在资源池中通过侦听的方式获取可用的资源集合，终端设备从该集合中随机选取一个资源进行数据传输。由于车联网系统中的业务具有周期性特征，因此终端设备通常采用半静态传输的方式，即终端设备选取一个传输资源后，就会在多个传输周期中持续的使用该资源，从而降低资源重选以及资源冲突的概率。终端设备会在 本次传输的控制信息中携带预留下次传输资源的信息，从而使得其他终端设备可以通过检测该终端设备的控制信息判断这块资源是否被该终端设备预留和使用，达到降低资源冲突的目的。
由于传输模式3的资源是由基站调度的，传输模式4的资源池是预配置或者基站配置的，因此两者不会存在资源池交叠的情况，即传输模式3和传输模式4各自对应的资源池是分离或者不重叠的，使用模式3的终端设备在支持模式3的资源池中的时频资源上进行数据传输，使用模式4的终端设备在支持模式4的资源池中的时频资源上进行数据传输。
对于支持3GPP协议的新版本Release-15的通信协议的终端设备来说，同样支持两种传输模式例如上述的传输模式3和传输模式4。当Release-15的终端设备和Release-14的终端设备在通信系统中共同进行数据传输时，对于有侦听能力的终端设备，可以通过资源侦听选择资源，而对于没有侦听能力的终端设备，就难以避免地会与其他终端设备的数据传输之间产生干扰。由于使用传输模式3的终端设备与基站连接，并且其传输资源是由基站分配的，因此当使用传输模式3的终端设备和使用传输模式4的终端设备共存的时候，更需要保护使用传输模式3的终端设备的传输可靠性。
可选地，如图3所示，在车联网系统中，终端设备可以基于载波聚合的方式，通过两个载波向网络设备或其他终端设备发送相同的PDCP层数据。具体地，如图3所示，一个PDCP实体与两个RLC实体绑定。该终端设备将待发送的第一PDCP PDU进行复制(duplication)，得到第二PDCP PDU。终端设备将该第一PDCP PDU下发到该两个RLC实体中的一个RLC实体RLC 1，将该第二PDCP PDU下发到该两个RLC实体中的另一个RLC实体RLC 2。该两个RLC实体分别对收到的PDCP PDU进行处理，并通过两个不同的载波将该第一PDCP PDU和该第二PDCP PDU发送至网络设备或其他终端设备。
应理解，终端设备在接收网络设备或其他终端设备发送的数据时，可以执行如图3所示的数据发送过程的逆过程。
此外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩 盘(Compact Disc，CD)、数字通用盘(Digital Versatile Disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，能够存储、包含和/或承载指令和/或数据的各种介质。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图4是根据本申请实施例的一种支持数据重复的方法200的示意性流程图。如图4所示，该方法200可以由发射端设备执行，该发射端设备可以是如图1或图2中所示的终端设备，该终端设备可以执行如图3所示的数据传输，该方法200中的接收端设备可以是如图1所示的网络设备，也可以是如图1或图2中所示的终端设备，该方法200可以应用于车联网系统。该方法200包括以下内容。
210，发射端设备向接收端设备发送多个RLC PDU，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域用于指示当前的RLC PDU所对应的无线承载。
应理解，发射端设备通过载波聚合来进行数据复制业务时，发送至少两个RLC PDU。
可选地，该发射端设备通过载波聚合来进行数据复制业务时，需要通过该指示域来指示当前的RLC PDU所对应的无线承载。
可选地，该指示域包括当前的RLC PDU所对应的PDCP对应的无线承载的标识(Identity，ID)。
可选地，该指示域包括逻辑信道的标识ID。
可选地，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU所对应的RLC报文头；
或者，
所述至少一个RLC PDU中所包含的RLC报文头。
可选地，该多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及该至少两个RLC PDU对应相同的无线承载。
因此，在本申请实施例的支持数据重复的方法中，发射端设备在发送多个RLC PDU时，可以在多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示当前的RLC PDU所对应的无线承载的指示域，从而，接收端设备可以确定多个RLC PDU中每个RLC PDU对应的无线承载，进而，能够实现重复数据的可靠传输。
图5是根据本申请实施例的一种支持数据重复的方法300的示意性流程图。如图5所示，该方法300可以由接收端设备执行，该接收端设备可以是如图1所示的网络设备，也可以是如图1或图2中所示的终端设备，该方法300中的发射端设备可以是如图1或图2中所示的终端设备，该终端设备可以执行如图3所示的数据传输，该方法300可以应用于车联网系统。该方法300包括以下内容。
310，接收端设备接收发射端设备发送的多个RLC PDU。
可选地，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域。
可选地，该指示域包括当前的RLC PDU所对应的无线承载。
可选地，该指示域包括逻辑信道的标识ID。
可选地，该接收端设备根据该至少一个RLC PDU的RLC报文头中包括的指示域，确定逻辑信道与无线承载之间的对应关系。
可选地，该指示域可以只包含1bit内容，例如，在协议规定00010只能和00001一起进行数据复制(duplication)业务，或者支持单独的承载，此时，该指示域可以只包含1bit内容就可以指示当前的RLC PDU所对应的无线承载。
可选地，该逻辑信道与该无线承载之间的对应关系是预配置的，例如，通过协议确定。
例如，如下表1所示的逻辑信道标识(logical channel Identity，LC ID)分配表，可以从预留索引(reserved Index)中分配01011-10100给为了数据复制(duplication)服务的RLC，例如，logical channel 00001和logical channel 01011会共同服务用于承载1的PDCP实体，logical channel 00010和logical channel 01100会共同服务用于承载2的PDCP实体。
表1
Figure PCTCN2017117778-appb-000001
还需要说明的是，可选地，所述至少一个RLC PDU的RLC报文头，为：
所述至少一个RLC PDU所对应的RLC报文头；
或者，
所述至少一个RLC PDU中所包含的RLC报文头。
也就是说，RLC PCU与RLC报文头可以存在两种对应方式，其中，一种方式为，RLC PDU与RLC报文头为对应关系，也就是说，这种关系下，RLC PDU中可以不包含RLC报文头，而是在RLC PDU之外包含有RLC报文头，此时，RLC报文头可以构成MAC子头(MAC Sub-header)；这样，可以利用RLC PDU与构成MAC子头的RLC报文头，再结合MAC header(MAC头)公共构成MAC层的数据单元。
另外一种方式，RLC PDU中包含有RLC报文头，这种方式下，RLC PDU构成MAC层的数据单元。MAC层的数据单元可以为MAC PDU。
320，该接收端设备根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载。
因此，在本申请实施例的支持数据重复的方法中，接收端设备在接收到多个RLC PDU时，可以根据逻辑信道与无线承载之间的对应关系，确定多个RLC PDU中每个RLC PDU对应的无线承载，进而，能够实现重复数据的可靠传输。
图6是根据本申请实施例的一种发射端设备400的示意性框图。如图6 所示，该发射端设备400包括：
发送单元410，用于向接收端设备发送多个无线链路控制协议数据单元RLC PDU，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域用于指示当前的RLC PDU所对应的无线承载。
可选地，该指示域包括当前的RLC PDU所对应的分组数据汇聚协议PDCP对应的无线承载的标识ID。
可选地，该指示域包括逻辑信道的标识ID。
可选地，该多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及该至少两个RLC PDU对应相同的无线承载。
可选地，该发射端设备400应用于车联网系统。
应理解，根据本申请实施例的一种发射端设备400中的各个模块的上述和其它操作和/或功能分别为了实现图4中的方法200中的发射端设备的相应流程，为了简洁，在此不再赘述。
图7是根据本申请实施例的一种接收端设备500的示意性框图。如图7所示，该接收端设备500包括：
接收单元510，用于接收发射端设备发送的多个无线链路控制协议数据单元RLC PDU；
处理单元520，用于根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载。
可选地，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域包括当前的RLC PDU所对应的无线承载；
在该处理单元520根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载之前，该处理单元520还用于根据该至少一个RLC PDU的RLC报文头中包括的指示域，确定该逻辑信道与该无线承载之间的对应关系。
可选地，该多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，该指示域包括逻辑信道的标识ID；
在该处理单元520根据逻辑信道与无线承载之间的对应关系，确定该多个RLC PDU中每个RLC PDU对应的无线承载之前，该处理单元520还用于根据该至少一个RLC PDU的RLC报文头中包括的指示域，确定该逻辑信道与该无线承载之间的对应关系。
可选地，该逻辑信道与该无线承载之间的对应关系是预配置的。
可选地，该多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及该至少两个RLC PDU对应相同的无线承载。
可选地，该接收端设备500应用于车联网系统。
应理解，根据本申请实施例的一种接收端设备500中的各个模块的上述和其它操作和/或功能分别为了实现图5中的方法300中的接收端设备设备的相应流程，为了简洁，在此不再赘述。
图8示出了本申请实施例提供的支持数据重复的设备600的示意性框图，该设备600包括：
存储器610，用于存储程序，该程序包括代码；
收发器620，用于和其他设备进行通信；
处理器630，用于执行存储器610中的程序代码。
可选地，当该代码被执行时，该处理器630还可以实现图4中的方法200中发射端设备执行的各个操作，为了简洁，在此不再赘述。此时，该设备600可以为终端设备，例如，车载终端。
可选地，当该代码被执行时，该处理器630可以实现图5中的方法300中接收端设备执行的各个操作，为了简洁，在此不再赘述。此时，该设备600可以为接入网设备，也可以是核心网设备。收发器620用于在处理器630的驱动下执行具体的信号收发。
应理解，在本申请实施例中，该处理器630可以是中央处理单元(Central Processing Unit，CPU)，该处理器630还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器610可以包括只读存储器和随机存取存储器，并向处理器630提供指令和数据。存储器610的一部分还可以包括非易失性随机存取存储器。例如，存储器610还可以存储设备类型的信息。
收发器620可以是用于实现信号发送和接收功能，例如频率调制和解调功能或叫上变频和下变频功能。
在实现过程中，上述方法的至少一个步骤可以通过处理器630中的硬件的集成逻辑电路完成，或该集成逻辑电路可在软件形式的指令驱动下完成该 至少一个步骤。因此，支持数据重复的设备600可以是个芯片或者芯片组。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器630读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
图9是根据本申请实施例的系统芯片700的示意性结构图。图9的系统芯片700包括输入接口701、输出接口702、处理器703以及存储器704之间可以通过内部通信连接线路相连，该处理器703用于执行该存储器704中的代码。
可选地，当该代码被执行时，该处理器703实现方法实施例中由发射端设备执行的方法。为了简洁，在此不再赘述。
可选地，当该代码被执行时，该处理器703实现方法实施例中由接收端设备执行的方法。为了简洁，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应 对本申请实施例的实施过程构成任何限定。
所属领的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (34)

  1. 一种支持数据重复的方法，其特征在于，包括：
    发射端设备向接收端设备发送多个无线链路控制协议数据单元RLC PDU，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域用于指示当前的RLC PDU所对应的无线承载。
  2. 根据权利要求1所述的方法，其特征在于，所述指示域包括当前的RLC PDU所对应的分组数据汇聚协议PDCP对应的无线承载的标识ID。
  3. 根据权利要求1所述的方法，其特征在于，所述指示域包括逻辑信道的标识ID。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU所对应的RLC报文头。
  5. 根据权利要求1至3任一项所述的方法，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU中所包含的RLC报文头。
  6. 根据权利要求4所述的方法，其特征在于，所述RLC报文头，用于构成MAC子头。
  7. 根据权利要求1至3中任一项所述的方法，其特征在于，所述多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及所述至少两个RLC PDU对应相同的无线承载。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法应用于车联网系统。
  9. 一种支持数据重复的方法，其特征在于，包括：
    接收端设备接收发射端设备发送的多个无线链路控制协议数据单元RLC PDU；
    所述接收端设备根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC PDU中每个RLC PDU对应的无线承载。
  10. 根据权利要求9所述的方法，其特征在于，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域包括当前的RLC PDU所对应的无线承载；
    在所述根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC  PDU中每个RLC PDU对应的无线承载之前，所述方法还包括：
    根据所述至少一个RLC PDU的RLC报文头中包括的指示域，确定所述逻辑信道与所述无线承载之间的对应关系。
  11. 根据权利要求9所述的方法，其特征在于，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域包括逻辑信道的标识ID；
    在所述根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC PDU中每个RLC PDU对应的无线承载之前，所述方法还包括：
    根据所述至少一个RLC PDU的RLC报文头中包括的指示域，确定所述逻辑信道与所述无线承载之间的对应关系。
  12. 根据权利要求9所述的方法，其特征在于，所述逻辑信道与所述无线承载之间的对应关系是预配置的。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及所述至少两个RLC PDU对应相同的无线承载。
  14. 根据权利要求9至13中任一项所述的方法，其特征在于，所述方法应用于车联网系统。
  15. 根据权利要求9至12任一项所述的方法，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU所对应的RLC报文头。
  16. 根据权利要求9至12任一项所述的方法，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU中所包含的RLC报文头。
  17. 根据权利要求16所述的方法，其特征在于，所述RLC报文头，用于构成MAC子头。
  18. 一种发射端设备，其特征在于，包括：
    发送单元，用于向接收端设备发送多个无线链路控制协议数据单元RLC PDU，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域用于指示当前的RLC PDU所对应的无线承载。
  19. 根据权利要求18所述的发射端设备，其特征在于，所述指示域包括当前的RLC PDU所对应的分组数据汇聚协议PDCP对应的无线承载的标 识ID。
  20. 根据权利要求18所述的发射端设备，其特征在于，所述指示域包括逻辑信道的标识ID。
  21. 根据权利要求18至20任一项所述的发射端设备，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU所对应的RLC报文头。
  22. 根据权利要求18至20任一项所述的发射端设备，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU中所包含的RLC报文头。
  23. 根据权利要求21所述的发射端设备，其特征在于，所述RLC报文头，用于构成MAC子头。
  24. 根据权利要求18至20中任一项所述的发射端设备，其特征在于，所述多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及所述至少两个RLC PDU对应相同的无线承载。
  25. 根据权利要求18至24中任一项所述的发射端设备，其特征在于，所述发射端设备应用于车联网系统。
  26. 一种接收端设备，其特征在于，包括：
    接收单元，用于接收发射端设备发送的多个无线链路控制协议数据单元RLC PDU；
    处理单元，用于根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC PDU中每个RLC PDU对应的无线承载。
  27. 根据权利要求26所述的接收端设备，其特征在于，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域包括当前的RLC PDU所对应的无线承载；
    在所述处理单元根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC PDU中每个RLC PDU对应的无线承载之前，所述处理单元还用于根据所述至少一个RLC PDU的RLC报文头中包括的指示域，确定所述逻辑信道与所述无线承载之间的对应关系。
  28. 根据权利要求26所述的接收端设备，其特征在于，所述多个RLC PDU中的至少一个RLC PDU的RLC报文头中包括指示域，所述指示域包括逻辑信道的标识ID；
    在所述处理单元根据逻辑信道与无线承载之间的对应关系，确定所述多个RLC PDU中每个RLC PDU对应的无线承载之前，所述处理单元还用于根据所述至少一个RLC PDU的RLC报文头中包括的指示域，确定所述逻辑信道与所述无线承载之间的对应关系。
  29. 根据权利要求26所述的接收端设备，其特征在于，所述逻辑信道与所述无线承载之间的对应关系是预配置的。
  30. 根据权利要求26至29中任一项所述的接收端设备，其特征在于，所述多个RLC PDU中的至少两个RLC PDU对应不同的逻辑信道，以及所述至少两个RLC PDU对应相同的无线承载。
  31. 根据权利要求26至30中任一项所述的接收端设备，其特征在于，所述接收端设备应用于车联网系统。
  32. 根据权利要求26至29任一项所述的接收端设备，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU所对应的RLC报文头。
  33. 根据权利要求26至29任一项所述的接收端设备，其特征在于，所述至少一个RLC PDU的RLC报文头，为：
    所述至少一个RLC PDU中所包含的RLC报文头。
  34. 根据权利要求32所述的接收端设备，其特征在于，所述RLC报文头，用于构成MAC子头。
PCT/CN2017/117778 2017-08-04 2017-12-21 支持数据重复的方法、发射端设备和接收端设备 WO2019024399A1 (zh)

Priority Applications (18)

Application Number Priority Date Filing Date Title
KR1020197038197A KR20200036814A (ko) 2017-08-04 2018-03-13 데이터 복제를 지원하는 방법, 송신단 기기 및 수신단 기기
JP2019571489A JP7083854B2 (ja) 2017-08-04 2018-03-13 データ複製をサポートする方法、送信側デバイスおよび受信側デバイス
AU2018310941A AU2018310941A1 (en) 2017-08-04 2018-03-13 Method of supporting data replication, transmitting terminal device and receiving terminal device
SG11201911811SA SG11201911811SA (en) 2017-08-04 2018-03-13 Method of supporting data replication, transmitting terminal device and receiving terminal device
CA3066605A CA3066605A1 (en) 2017-08-04 2018-03-13 Method of supporting data replication, transmitting terminal device and receiving terminal device
US16/625,636 US11284296B2 (en) 2017-08-04 2018-03-13 Method of supporting data replication, transmitting terminal device and receiving terminal device
CN202010072503.5A CN111212398B (zh) 2017-08-04 2018-03-13 支持数据重复的方法、发射端设备、接收端设备及存储介质
EP18841323.1A EP3627735B1 (en) 2017-08-04 2018-03-13 Method of supporting data replication, transmitting terminal device and receiving terminal device
RU2020101950A RU2762931C2 (ru) 2017-08-04 2018-03-13 Способ поддержки дублирования данных, передающее оконечное устройство и приемное оконечное устройство
MX2020001219A MX2020001219A (es) 2017-08-04 2018-03-13 Metodo para soportar replicacion de datos, dispositivo terminal transmisor y dispositivo terminal receptor.
CN201880037596.9A CN110731061A (zh) 2017-08-04 2018-03-13 支持数据重复的方法、发射端设备和接收端设备
BR112019027828-1A BR112019027828A2 (pt) 2017-08-04 2018-03-13 método para suportar duplicação de dados, dispositivo de transmissão e dispositivo de recebimento
PCT/CN2018/078892 WO2019024504A1 (zh) 2017-08-04 2018-03-13 支持数据重复的方法、发射端设备和接收端设备
TW107127176A TWI785085B (zh) 2017-08-04 2018-08-03 支援資料重複的方法、發射端設備和接收端設備
IL271166A IL271166A (en) 2017-08-04 2019-12-04 A method for supporting data replication, a transmitting terminal device and a receiving terminal device
ZA2019/08390A ZA201908390B (en) 2017-08-04 2019-12-17 Method of supporting data replication, transmitting terminal device and receiving terminal device
PH12019502858A PH12019502858A1 (en) 2017-08-04 2019-12-18 Method for supporting data replication, transmitting terminal device and receiving terminal device
CL2020000032A CL2020000032A1 (es) 2017-08-04 2020-01-06 Método para soportar replicación de datos, dispositivo terminal transmisor y dispositivo terminal receptor.

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PCT/CN2017/096079 WO2019024105A1 (zh) 2017-08-04 2017-08-04 支持数据重复的方法、发射端设备和接收端设备
CNPCT/CN2017/096079 2017-08-04

Publications (1)

Publication Number Publication Date
WO2019024399A1 true WO2019024399A1 (zh) 2019-02-07

Family

ID=65232850

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/CN2017/096079 WO2019024105A1 (zh) 2017-08-04 2017-08-04 支持数据重复的方法、发射端设备和接收端设备
PCT/CN2017/117778 WO2019024399A1 (zh) 2017-08-04 2017-12-21 支持数据重复的方法、发射端设备和接收端设备
PCT/CN2018/078892 WO2019024504A1 (zh) 2017-08-04 2018-03-13 支持数据重复的方法、发射端设备和接收端设备

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096079 WO2019024105A1 (zh) 2017-08-04 2017-08-04 支持数据重复的方法、发射端设备和接收端设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/078892 WO2019024504A1 (zh) 2017-08-04 2018-03-13 支持数据重复的方法、发射端设备和接收端设备

Country Status (17)

Country Link
US (1) US11284296B2 (zh)
EP (1) EP3627735B1 (zh)
JP (1) JP7083854B2 (zh)
KR (1) KR20200036814A (zh)
CN (2) CN110731061A (zh)
AU (1) AU2018310941A1 (zh)
BR (1) BR112019027828A2 (zh)
CA (1) CA3066605A1 (zh)
CL (1) CL2020000032A1 (zh)
IL (1) IL271166A (zh)
MX (1) MX2020001219A (zh)
PH (1) PH12019502858A1 (zh)
RU (1) RU2762931C2 (zh)
SG (1) SG11201911811SA (zh)
TW (1) TWI785085B (zh)
WO (3) WO2019024105A1 (zh)
ZA (1) ZA201908390B (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112583530B (zh) * 2019-09-27 2022-04-15 大唐移动通信设备有限公司 一种数据传输方法、装置及设备
JP2023534056A (ja) * 2020-07-17 2023-08-07 華為技術有限公司 データ伝送方法および装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299711A (zh) * 2007-04-30 2008-11-05 华为技术有限公司 数据单元转换的方法、设备及数据单元传输的系统
CN105684501A (zh) * 2013-10-29 2016-06-15 三星电子株式会社 在移动通信系统中使用多个载波传送/接收数据的方法和装置
US20160295624A1 (en) * 2015-04-02 2016-10-06 Samsung Electronics Co., Ltd Methods and apparatus for resource pool design for vehicular communications
CN106664245A (zh) * 2014-08-19 2017-05-10 高通股份有限公司 使用多连接来对业务进行多播
US20170164187A1 (en) * 2010-03-30 2017-06-08 Hon Hai Precision Industry Co., Ltd. Relay user equipment device and capability discovery method thereof

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6701151B2 (en) * 2001-03-27 2004-03-02 Ericsson Inc. Short access for realizing a signaling radio bearer in geran
KR100889865B1 (ko) 2002-11-07 2009-03-24 엘지전자 주식회사 무선 이동통신 시스템의 통신방법
CN101166193B (zh) * 2006-10-19 2011-07-20 大唐移动通信设备有限公司 一种媒体接入控制协议数据单元的传输方法和系统
ES2740354T3 (es) * 2007-06-25 2020-02-05 Nokia Solutions & Networks Oy Transferencia de mensajes para mensajes de señalización en banda en redes de acceso de radio
US8902927B2 (en) 2007-10-01 2014-12-02 Qualcomm Incorporated Medium access control header format
CN101911630B (zh) 2007-12-24 2013-03-13 上海贝尔股份有限公司 识别多个rlc pdu的源和大小的方法和设备
US8718647B2 (en) 2008-06-20 2014-05-06 Qualcomm Incorporated Method and apparatus for prioritizing status messages in a wireless communication system
JP5479571B2 (ja) * 2009-03-20 2014-04-23 テレフオンアクチーボラゲット エル エム エリクソン（パブル） 高度ｌｔｅにおけるセルフバックホール処理及びリレー処理用の無線ベアラ識別
KR101568310B1 (ko) 2013-02-01 2015-11-12 주식회사 케이티 스몰 셀 환경에서의 사용자 플레인 데이터 전송 방법 및 장치
WO2015006896A1 (zh) * 2013-07-15 2015-01-22 华为技术有限公司 数据处理装置和方法
EP2854444A1 (en) * 2013-09-27 2015-04-01 Panasonic Intellectual Property Corporation of America Efficient uplink scheduling mechanism for dual connectivity
WO2015163624A1 (en) 2014-04-24 2015-10-29 Lg Electronics Inc. Method for releasing a sidelink radio bearer for d2d communication system and device therefor
EP3213490B1 (en) 2014-10-31 2022-09-07 LG Electronics Inc. Method for transmitting mac pdu in a d2d communication system and device therefor
US10505783B2 (en) 2015-06-30 2019-12-10 Lg Electronics Inc. Terminal and V2X communication method thereof in V2X communication system
CN108029148B (zh) 2015-07-23 2022-04-01 苹果公司 移动性中继方法和装置
CN105246106B (zh) * 2015-09-02 2019-02-12 北京星河亮点技术股份有限公司 Lte-a终端测试仪表在载波聚合下mac层数据调度方法
US10841203B2 (en) * 2015-12-11 2020-11-17 Qualcomm Incorporated Coordination of multiple routes for a single IP connection
WO2017164603A1 (en) * 2016-03-25 2017-09-28 Lg Electronics Inc. Method and device for transmitting data unit, and method and device for receiving data unit
WO2018012874A1 (ko) * 2016-07-12 2018-01-18 엘지전자 주식회사 상향링크 신호 전송 방법 및 사용자기기
KR102357594B1 (ko) * 2017-03-23 2022-02-04 삼성전자 주식회사 패킷 중복을 위한 데이터 처리 방법 및 장치
EP3689015A1 (en) * 2017-09-28 2020-08-05 Telefonaktiebolaget LM Ericsson (Publ) Security enhancements for early data transmissions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101299711A (zh) * 2007-04-30 2008-11-05 华为技术有限公司 数据单元转换的方法、设备及数据单元传输的系统
US20170164187A1 (en) * 2010-03-30 2017-06-08 Hon Hai Precision Industry Co., Ltd. Relay user equipment device and capability discovery method thereof
CN105684501A (zh) * 2013-10-29 2016-06-15 三星电子株式会社 在移动通信系统中使用多个载波传送/接收数据的方法和装置
CN106664245A (zh) * 2014-08-19 2017-05-10 高通股份有限公司 使用多连接来对业务进行多播
US20160295624A1 (en) * 2015-04-02 2016-10-06 Samsung Electronics Co., Ltd Methods and apparatus for resource pool design for vehicular communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project, Technical Specification Group Radio Access Network, NR, NR and NG-RAN Overall Description, Stage 2 (Release 15", 3GPP TS 38.300 V0.4.1, 30 June 2017 (2017-06-30), XP055567688 *

Also Published As

Publication number Publication date
AU2018310941A1 (en) 2020-01-16
EP3627735A1 (en) 2020-03-25
TW201911903A (zh) 2019-03-16
CN110731061A (zh) 2020-01-24
US20210092637A1 (en) 2021-03-25
MX2020001219A (es) 2020-03-24
US11284296B2 (en) 2022-03-22
CA3066605A1 (en) 2019-02-07
JP2020529148A (ja) 2020-10-01
SG11201911811SA (en) 2020-01-30
WO2019024504A1 (zh) 2019-02-07
ZA201908390B (en) 2020-10-28
EP3627735A4 (en) 2020-05-27
BR112019027828A2 (pt) 2020-07-07
RU2020101950A (ru) 2021-09-07
IL271166A (en) 2020-01-30
PH12019502858A1 (en) 2020-09-28
CN111212398B (zh) 2022-11-04
CL2020000032A1 (es) 2020-05-29
KR20200036814A (ko) 2020-04-07
EP3627735B1 (en) 2022-05-11
JP7083854B2 (ja) 2022-06-13
CN111212398A (zh) 2020-05-29
RU2020101950A3 (zh) 2021-09-07
RU2762931C2 (ru) 2021-12-24
WO2019024105A1 (zh) 2019-02-07
TWI785085B (zh) 2022-12-01

Similar Documents

Publication Publication Date Title
WO2019192596A1 (zh) 传输数据的方法及其装置和系统
WO2019051803A1 (zh) 资源配置的方法、终端设备和网络设备
WO2019024114A1 (zh) 数据传输的方法、终端设备和网络设备
TWI791033B (zh) 無線通訊的方法、終端設備和網路設備
WO2019100356A1 (zh) 载波选取的方法和设备、终端设备
EP3678437B1 (en) Method for conflict resolution and terminal device
WO2019084931A1 (zh) 确定传输参数的方法、终端设备和网络设备
WO2019183903A1 (zh) 用于传输数据的方法和终端设备
WO2019084929A1 (zh) 资源选取的方法和终端设备
TWI785085B (zh) 支援資料重複的方法、發射端設備和接收端設備
CN112703710B (zh) 数据传输方法、发射端设备和接收端设备
WO2020114326A1 (zh) 资源池配置方法、装置及设备
WO2019033416A1 (zh) 无线通信的方法、终端设备和网络设备
WO2019061982A1 (zh) 用于资源分配的方法、网络设备和通信设备
WO2019028603A1 (zh) 数据传输的方法和终端设备

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: 17919900

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: 17919900

Country of ref document: EP

Kind code of ref document: A1