WO2018059173A1 - 免授权的传输上行信息的方法、网络设备和终端设备 - Google Patents

免授权的传输上行信息的方法、网络设备和终端设备 Download PDF

Info

Publication number
WO2018059173A1
WO2018059173A1 PCT/CN2017/099485 CN2017099485W WO2018059173A1 WO 2018059173 A1 WO2018059173 A1 WO 2018059173A1 CN 2017099485 W CN2017099485 W CN 2017099485W WO 2018059173 A1 WO2018059173 A1 WO 2018059173A1
Authority
WO
WIPO (PCT)
Prior art keywords
mars
information
redundancy version
terminal device
target
Prior art date
Application number
PCT/CN2017/099485
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 华为技术有限公司
Publication of WO2018059173A1 publication Critical patent/WO2018059173A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04BTRANSMISSION
    • H04B7/00Radio transmission systems, i.e. using radiation field
    • H04B7/02Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/12Frequency diversity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/0001Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0027Scheduling of signalling, e.g. occurrence thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/189Transmission or retransmission of more than one copy of a message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/22Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044Arrangements for allocating sub-channels of the transmission path allocation of payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling
    • H04W72/1263Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

Definitions

  • the present application relates to the field of communications, and more particularly to a method, network device and terminal device for transferring uplink information without authorization.
  • the terminal device before transmitting uplink data, the terminal device first needs to establish a radio resource control connection with the base station, enter a radio resource control connection state, and obtain an authorization instruction of the base station. After that, the uplink data can be sent according to the instruction of the base station. This method of transmitting data upstream is called an authorized transmission. Since the terminal device needs to send data to and from the air interface to determine that there is uplink data, a large amount of signaling interaction is required, and therefore, the delay of the authorized transmission is large.
  • LTE Long Term Evolution
  • the unlicensed transmission is considered to be a method of transmitting uplink data that is superior to the authorized transmission.
  • the basic idea of the unlicensed transmission is that the data is “on the go”, that is, when the terminal determines that there is uplink data to be transmitted, it does not have to go through the process of transmitting the uplink scheduling request and waiting for the authorization command interaction process of the receiving base station, but directly processing the data directly. Then sent to the base station.
  • Ultra-Reliable Low Latency Communication is also an important scenario in 5G.
  • URLLC Ultra-Reliable Low Latency Communication
  • the unlicensed method for transmitting uplink information is to send the same transport block TB multiple times in consecutive uplink subframes without waiting for an Acknowledgement (ACK) or a Negative Acknowledgement (NACK).
  • This technique is called Transmission Time Interval Bundling (TTI Bundling).
  • TTI Bundling Transmission Time Interval Bundling
  • the sub-frame bundling technique only utilizes temporal diversity to reduce latency and has less flexibility.
  • the present application provides a method, a network device, and a terminal device for transmitting an unlicensed transmission uplink information, which can improve the flexibility of uplink transmission.
  • the application provides an unlicensed method for transmitting uplink information, the method comprising: determining, by an end device, a plurality of target multiple access resources MAR carrying at least one redundancy version, each redundancy The version includes at least uplink information that the terminal device needs to send to the network device, and the multiple target MARs can pass frequency diversity. Or signature diversity is distinguished; the terminal device transmits the at least one redundancy version to the network device on the plurality of target MARs.
  • the redundancy version (RV) described in the embodiment of the present application is used to implement Hybrid Automatic Repeat Request (HARQ) of Incremental Redundancy (IR), that is, The redundant bits generated by the transport block (TB) are divided into several groups, each RV defines a transmission starting point, and the first transmission and each retransmission use different RVs respectively to realize the gradual accumulation of redundant bits.
  • HARQ Hybrid Automatic Repeat Request
  • IR Incremental Redundancy
  • the plurality of target MARs can be distinguished by any combination of frequency diversity, signature diversity, and time diversity.
  • the terminal device determines the multiple target MARs that carry the at least one redundancy version, including: determining, by the terminal device, the multiple first MARs corresponding to the at least one redundancy version according to the binding information, where the binding The information is pre-agreed by the terminal device and the network device, and the bundle information includes at least one of the following information: the number of redundant versions used when transmitting the uplink information, and the number and size of the occupied versions of the MAR used when transmitting the uplink information, The location of the plurality of first MARs, the mapping relationship between the redundancy version used when transmitting the uplink information and the plurality of first MARs, the number of redundancy versions carried on each of the first MARs, and the modulation that can be used by each of the first MARs And the coding strategy MCS; the terminal device determines the plurality of target MARs from the plurality of first MARs.
  • the method further includes: the terminal device sends a first control channel to the network device, where the first control channel carries the first indication information, where the first indication information is used to indicate the multiple target MARs,
  • the network device is configured to receive the at least one redundancy version on the plurality of target MARs according to the first indication information.
  • each of the plurality of target MARs carries identification information of the terminal device and a version number of the redundancy version carried
  • each target MAR carries a second control channel
  • second The second indication information is carried on the control channel, and the second indication information is used to indicate the identification information and the version number, so that the network device combines the at least one redundancy version to obtain uplink information.
  • the terminal device sends a third control channel to the network device, where the third control channel carries the third indication information, where the third indication information is used to indicate the multiple determined by the terminal device based on the bundle information.
  • the target MAR is configured to receive, by the network device, the at least one redundancy version on the target MAR in the plurality of first MARs according to the binding information and the third indication information.
  • the uplink data transmitted on the multiple target MARs is the same.
  • the present application provides an unlicensed method for transmitting uplink information, the method comprising: receiving, by a network device, at least one redundancy version sent by a terminal device on a plurality of target multiple access resources MAR, the multiple target MARs
  • the terminal device is determined from the unlicensed resource, and each redundancy version includes at least uplink information that the terminal device needs to send to the network device, and the multiple MARs can be distinguished by frequency diversity or signature diversity; the network device is at least one redundant The remaining versions are merged to get the upstream information.
  • the plurality of target MARs can be distinguished by any combination of frequency diversity, signature diversity, and time diversity.
  • the network device combines the at least one redundancy version to obtain uplink information.
  • the network device combines the at least one redundancy version according to the binding information to obtain uplink information, where the binding information is pre-agreed by the terminal device and the network device, and the binding information includes at least one of the following information: sending the uplink information.
  • the number of redundancy versions used, the redundancy version used when transmitting the uplink information, the number and size of the MARs, the location of the plurality of first MARs, the redundancy version used when transmitting the uplink information, and the plurality of first MARs The mapping relationship, the number of redundancy versions carried on each first MAR, and the modulation and coding strategy MCS that each first MAR can use.
  • the method further includes: the network device receiving the first control channel sent by the terminal device, where the first control channel carries the first indication information, where the first indication information is used to indicate the multiple target MARs; And the network device combines the at least one redundancy version to obtain the uplink information, and the network device combines the at least one redundancy version according to the first indication information to obtain uplink information.
  • each of the plurality of target MARs carries identification information of the terminal device and a version number of the redundancy version carried
  • each target MAR carries a second control channel
  • second The second indicator information is carried on the control channel
  • the second indication information is used to indicate the identifier information and the version number
  • the network device combines the at least one redundancy version to obtain uplink information, including: the network device according to the second Instructing information, combining the at least one redundancy version to obtain uplink information.
  • the method further includes: the network device receiving the third control channel sent by the terminal device, where the third control channel carries the third indication information, where the third indication information is used to indicate that the terminal device determines the binding information. And the plurality of target MARs; and the network device merging the at least one redundancy version to obtain the uplink information, the network device, according to the third indication information, combining the at least one redundancy version to obtain uplink information.
  • the at least one redundancy version has the same version number, and the uplink data transmitted on the multiple target MARs is the same.
  • the present application provides a terminal device for performing the method in the first aspect or any possible implementation manner of the first aspect.
  • the terminal device comprises means for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the application provides a network device for performing the method in any of the possible implementations of the second aspect or the second aspect.
  • the network device comprises means for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • the application provides a terminal device, where the terminal device includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory.
  • the processor performs the method of any of the above-described first aspects or any of the possible implementations of the first aspect.
  • the application provides a network device, the network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program from the memory.
  • the processor performs the method of any of the above-described second aspect or any of the possible implementations of the second aspect when the program is executed.
  • the application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of the first aspect or any of the possible implementations of the first aspect.
  • the present application provides a computer readable medium for storing a computer program, the computer program comprising instructions for performing the method of any of the second aspect or any of the possible implementations of the second aspect.
  • the application provides a terminal device, which includes a transceiver, a processor, and a memory.
  • the processor is configured to control transceiver transceiver signals
  • the memory is used to store a computer program
  • the processor is used to slave the memory
  • the computer program is called and executed such that the terminal device performs the method of the first aspect described above.
  • the application provides a network device, the network device including a transceiver, a processor, and a memory.
  • the processor is for controlling transceiver transceiver signals for storing a computer program for calling and running the computer program from memory such that the network device performs the method of the second aspect.
  • the present application provides a chip system including a processor and a transceiver for implementing the functions involved in the first aspect and any possible implementation thereof, for example, processing Or send the data and/or information involved in the above method.
  • the chip system further comprises a memory for storing the necessary program instructions and data of the terminal device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the present application provides a chip system including a processor and a transceiver for implementing the functions involved in the second aspect and any possible implementation thereof, such as, for example, receiving Or process the data and/or information involved in the above methods.
  • the chip system further comprises a memory for storing the necessary program instructions and data of the terminal device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the application provides a computer program product, comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform the first aspect and any possible implementation thereof The method in the way.
  • the application provides a computer program product, comprising: computer program code, when the computer program code is run on a computer, causing the computer to perform the second aspect and any possible implementation thereof The method in the way.
  • the terminal device uses the uplink of the frequency transmission or the signature diversity (or any combination of time diversity, frequency diversity and signature diversity) to carry the uplink A redundant version of the information.
  • the flexibility of transmitting uplink information can be improved while ensuring low latency.
  • FIG. 1 is a schematic diagram of a computer device (or system) 100 in accordance with an embodiment of the present application.
  • FIG. 2 shows a schematic interaction diagram of a method 200 for granting unauthorized transmission of uplink information in an embodiment of the present application.
  • FIG. 3 shows a manner in which a UE sends a redundancy version in an embodiment of the present application.
  • FIG. 4 shows a schematic diagram of a MAR of an embodiment of the present application.
  • FIG. 5 shows a schematic diagram of a MAR of another embodiment of the present application.
  • FIG. 6 shows a schematic diagram of a MAR of still another embodiment of the present application.
  • FIG. 7 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • FIG. 8 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • FIG. 9 shows another manner in which the UE sends a redundancy version in the embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a MAR of still another embodiment of the present application.
  • FIG. 11 shows a manner in which a UE sends multiple redundancy versions in an embodiment of the present application.
  • Figure 12 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • FIG. 13 illustrates another manner in which a UE transmits multiple redundancy versions according to an embodiment of the present application.
  • Figure 14 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • Figure 15 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • Figure 16 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • Figure 17 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • Figure 18 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • FIG. 19 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • FIG. 20 shows a schematic block diagram of a network device 600 in accordance with an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access Wireless
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • next-generation mobile communication systems for example, 5G
  • M2M Machine to Machine
  • the unlicensed transmission described in the embodiment of the present application is different from the above-mentioned unlicensed spectrum resource transmission, and the process of allocating the unlicensed transmission resource to the user through the user access network and the base station is required.
  • the user has data to send, it is sent directly on the unlicensed resource allocated by the base station. Therefore, the unlicensed spectrum resource transmission described in the embodiment of the present application is different from the traditional unlicensed spectrum resource transmission.
  • the resources used for the unlicensed transmission in the embodiment of the present application need to be pre-allocated by the system.
  • the present application describes various embodiments in connection with a network device.
  • the network device may be a device for communicating with the mobile station, and the network device may be an access point (ACCESS POINT, AP) in a Wireless Local Area Networks (WLAN), GSM or Code Division Multiple Access.
  • Base station in CDMA) (Base Transceiver Station, BTS). It can also be a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or an in-vehicle device, a wearable device, and a future 5G network.
  • PLMN Public Land Mobile Network
  • the network device can perform wireless communication by using the above-mentioned unauthorized transfer.
  • the network device can also perform wireless communication by authorizing the transmission of spectrum resources.
  • a terminal device can also be called a user device (User Equipment, UE), mobile station, access terminal, subscriber unit, subscriber station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user equipment.
  • UE User Equipment
  • the terminal device may be a station (STAION, ST) in a Wireless Local Area Networks (WLAN), and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, or a wireless local loop (Wireless Local) Loop, WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and future communication networks (eg, A mobile station in 5G) or a terminal device in a PLLM network in a future evolution.
  • STAION, ST Wireless Local Area Networks
  • WLAN Wireless Local Area Networks
  • PDAs personal digital assistants
  • the terminal device can perform wireless communication by using the above-mentioned unauthorized transfer.
  • the terminal device can also perform wireless communication by authorizing spectrum resource transmission.
  • the network device and the terminal device described in the embodiments of the present application may be implemented in the manner of the computer device (or system) 100 shown in FIG. 1.
  • FIG. 1 is a schematic diagram of a computer device (or system) 100 provided by an embodiment of the present application.
  • the computer device 100 includes at least one processor 101, a memory 102, a communication bus 103, and at least one communication interface 104.
  • the processor 101 can be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the memory 102 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory can exist independently or be integrated with the processor.
  • the memory 102 is used to store application code for executing the technical solution of the present application, and the processor 101 is configured to execute application code stored in the memory 102.
  • processor 101 may include one or more CPUs.
  • CPU0 and CPU1 shown in FIG. 1 may include one or more CPUs.
  • the computer device 100 may include multiple processors, each of which may be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • computer device 100 may also include output device 105 and input device 106 as an embodiment.
  • Output device 105 is in communication with processor 101 and can display information in a variety of ways.
  • the output device 105 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 106 is in communication with processor 101 and can accept user input in a variety of ways.
  • the input device can be a mouse, a keyboard, a touch screen device, or a sensing device, and the like.
  • the computer device 100 described above may be a general purpose computer device or a special purpose computer device.
  • the computer device 100 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or have FIG. A device of similar structure.
  • PDA personal digital assistant
  • the embodiment of the present application does not limit the type of computer device 100.
  • the method for transmitting the uplink information without authorization in the embodiment of the present application will be described below by using only the example of the UE and the base station as the terminal device and the network device.
  • FIG. 2 is a schematic interaction diagram of a method for exempting transmission of uplink information in an embodiment of the present application. As shown in FIG. 2, the method mainly includes steps 210 to 230.
  • the UE determines multiple target multiple access resources MAR that carry at least one redundancy version, and each redundancy version includes at least uplink information that the terminal device needs to send to the base station, where the multiple target MARs can pass frequency diversity or signature diversity. Make a distinction.
  • MAR multiple access resource
  • MAPR multiple access physical resource
  • MAS multiple access signature
  • the MAS includes at least one of the following: but not limited to: a codebook, a codeword, a sequence, an interleaver pattern, a mapping pattern, and a demodulation reference signal. ), Preamble, Spatial-dimension, and Power dimension.
  • the plurality of target MARs can be distinguished by any combination of frequency diversity, signature diversity, and time diversity.
  • the UE when the UE sends the uplink information, the UE may send a redundancy version or multiple redundancy versions, which is not limited in this embodiment.
  • a redundant version mentioned here refers to only one version number. Multiple redundancy versions refer to multiple version numbers.
  • the redundancy version (RV) described in the embodiment of the present application is used to implement Hybrid Automatic Repeat Request (HARQ) of Incremental Redundancy (IR), that is, The Redundancy Bits generated by the Transport Block (TB) are divided into groups, each RV defines a transmission start point, and the first transmission and each retransmission use different RVs respectively to implement redundant bits. Gradually accumulate, complete incremental redundancy HARQ. More specifically, the detailed description about the redundancy version can also refer to the definition in the prior art, which will not be described in detail herein. In particular, when the redundancy versions transmitted on the respective MARs are identical, this method of incremental redundancy becomes a Chase Combining (CC) method.
  • CC Chase Combining
  • the UE determines multiple target MARs carrying at least one redundancy version, including multiple manners.
  • the UE determines the target MAR according to the binding information, where the binding information is pre-agreed by the terminal device and the network device.
  • the bundle information can be related to the following factors:
  • the UE can use the same bundling information as the initial transmission when retransmitting, or use the bundle information of the initial transmission of the domain. For example, the UE may increase the number of RVs, increase the number of MARs, or place the RVs on a higher diversity MAR, etc., during retransmission.
  • QoS Quality of Service
  • the UE uses different binding information for data packets with different QoS requirements. For example, for packets with higher latency requirements, try to choose frequency diversity or signature diversity instead of time diversity. Alternatively, the base station may attempt to decode in a shorter time by the system's preset rules. For another example, for a data packet with high reliability requirements, more RVs can be transmitted, the number of MARs occupying the RV occupancy can be increased, and the RV can be placed on a higher diversity MAR.
  • the Bundling information in the embodiment of the present application may include at least one of the following information: the number of redundant versions used when transmitting the uplink information, the number of occupied MARs used when transmitting the uplink information, and The size, the location of the MAR, the mapping relationship between the redundancy version used when transmitting the uplink information and the MAR, the number of redundancy versions carried on each MAR, and the modulation and coding scheme that each MAR can use (Modulation and Coding Scheme, MCS).
  • MCS Modulation and Coding Scheme
  • each target MAR of the multiple target MARs carries the identification information of the UE and the version number of the redundancy version carried
  • each target MAR carries a second control channel
  • the second control The second indication information is carried on the channel, and the second indication information is used to indicate the identification information and the version number, so that the base station combines the at least one redundancy version to obtain uplink information.
  • each target MAR may separately carry a control channel (ie, a second control channel), and the control channel carries The indication information of the UE identification information and the RV version number (ie, the second indication information).
  • the base station when receiving the RV, the base station simultaneously receives the identification information of the UE carried on the MAR and the version number of the RV.
  • the base station can learn the version number of each RV and the UE to which the RV belongs based on the identifier information and the version number of the UE, so that the RV of each UE can be combined and decoded.
  • the system definition may refer to a pre-agreed by the base station and the UE. Alternatively, system definitions may also refer to standards.
  • the UE determines the reference bundle information.
  • the UE determines, by the UE, the multiple target MARs that carry the at least one redundancy version, including:
  • the UE determines, according to the bundle information, a plurality of first MARs corresponding to the at least one redundancy version, where the bundle information is pre-agreed by the UE and the network device, and the bundle information includes at least one of the following information: use redundancy when sending the uplink information
  • the UE determines the plurality of target MARs from the plurality of first MARs.
  • the first MAR herein refers to a system-defined MAR that carries RV.
  • the target MAR is the MAR that the UE uses from the plurality of first MARs when actually transmitting the RV.
  • the network side can only know the system pre-defined MAR (ie, the network side only knows the first MAR), and does not know the MAR used when the UE actually sends the RV. Therefore, the UE needs to inform the network The MAR (ie, the target MAR) used by the network device to actually send the RV.
  • the MAR ie, the target MAR
  • the method further includes:
  • the UE sends a third control channel to the network device, where the third control channel carries the third indication information, where the third indication information is used to indicate the multiple target MARs determined by the UE based on the bundle information, so that the network device can And third indication information, receiving the at least one redundancy version on the target MAR in the plurality of first MARs.
  • the UE determines the target MAR based on the bundle information. Different from the above method 1, in this manner, the UE only defines the system as a reference when transmitting the RV. Therefore, the MAR carrying the RV (ie, the target MAR) sent by the UE may not be completely defined by the system. In this way, the UE needs to inform the base station of its own selected MAR that transmits the RV.
  • the UE determines itself.
  • the method further includes:
  • the UE sends a first control channel to the network device, where the first control channel carries the first indication information, where the first indication information is used to indicate the multiple target MARs, so that the network device is in the multiple target MAR according to the first indication information.
  • the at least one redundancy version is received on.
  • the MAR ie, the target MAR used when the UE transmits the RV may be completely determined by the UE itself. Therefore, in this manner, the UE also needs to inform the network side of its own selected RV-bearing MAR.
  • each redundancy version includes at least uplink information that the UE needs to send to the base station.
  • the target MAR of the embodiment of the present application i.e., the MAR for carrying the redundancy version RV
  • the MAR for carrying the redundancy version RV will be described in detail below in conjunction with various embodiments.
  • Figure 3 illustrates one way in which a UE sends a redundancy version. As shown in FIG. 3, the UE transmits one transport block (TB) each time, and the TB has only one redundancy version.
  • TB transport block
  • redundancy version described in various embodiments of the present application means that the version number of the redundancy version sent by the UE to the network side is the same, that is, there is only one version number.
  • multiple redundancy versions refer to multiple versions of the redundancy version sent by the UE to the network side.
  • FIG. 4 shows a schematic diagram of a MAR of an embodiment of the present application.
  • the time-frequency resource block with the fixed length is defined as a resource group by using the same Multiple Access Signature (MAS).
  • Multiple MARs included in each resource group may employ different modulation and coding schemes (MCS).
  • MCS modulation and coding schemes
  • the resource group described in the various embodiments of the present application may be selected by the UE itself, or may be in a semi-static configuration manner.
  • the semi-static configuration described herein refers to pre-configuration based on the network side when the UE first transmits the RV, and stores configuration information on the network side. At regular intervals, the UE transmits the RV using the same MAR resource as when the RV was first transmitted.
  • UE#1 selects resource group #1
  • UE#2 selects resource group #3
  • UE#3 selects resource group 4.
  • a redundancy version including uplink information is placed on all MARs in the selected resource group.
  • the base station combines and decodes the redundancy versions on all MARs on each resource group.
  • the base station can obtain the uplink information sent by the UE.
  • FIG. 5 shows a schematic diagram of a MAR of another embodiment of the present application.
  • a time-frequency resource block with the same multiple access signature and an unfixed length is defined as one resource group.
  • resource group #1 and resource group #2 have different lengths from resource group #3 and resource group #4.
  • UE#1 selects resource group #1, and UE#2 selects resource group #3.
  • UE#3 selects resource group #4. The UE places the RVs of the respective TBs on each of the selected resource groups.
  • the base station combines and decodes the redundancy versions on all the MARs included in each resource group to obtain the uplink information sent by the UE.
  • FIG. 6 shows a schematic diagram of a MAR of still another embodiment of the present application.
  • a time-frequency resource block with a time discontinuity, the same multiple access signature, and an unfixed length is defined as a resource group.
  • placing (or carrying) a redundancy version of multiple MARs may be contiguous in the time domain or may be discontinuous.
  • resource group #1 is not continuous in the time domain.
  • Resource group #3 and resource group #4 are consecutive in the time domain.
  • UE#1 selects resource group #1
  • UE#2 selects resource group 3
  • UE#3 selects resource group 4.
  • Each UE places the RVs generated by the respective TBs on each of the MARs of the selected resource group.
  • the base station combines and decodes the redundancy versions on all the MARs on each resource group to obtain the uplink information sent by the UE.
  • FIG. 7 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • a time-frequency resource block that is discontinuous in time, uses the same multiple access signature, is not fixed in length, and is in different frequency domains is defined as one resource group.
  • resource group #1 selects discontinuous resources in the time domain and is distributed in different frequency domains.
  • UE#1 selects resource group #1, and UE#2 selects resource group #2.
  • UE#3 selects resource group #3. The UE places the RVs generated by the respective TBs on each of the MARs of the selected resource group.
  • the base station combines and decodes the redundancy versions on all the MARs of each resource group to obtain the uplink information sent by the UE to the base station.
  • FIG. 8 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • a time-frequency resource block with a non-contiguous time, different multi-access signatures, and an unfixed length and in different frequency domains is defined as a resource group.
  • resource group #1 selects discontinuous resources in the time domain and is distributed in different frequency domains.
  • UE#1 selects resource group #1.
  • UE#2 selects resource group #2.
  • UE#3 selects resource group #3. The UE places the RVs generated by the respective TBs on each of the MARs of the selected resource group.
  • the base station combines and decodes the redundancy versions of all the MARs on each resource group to obtain the uplink information sent by the UE to the base station.
  • Figure 9 shows another way in which the UE sends a redundancy version.
  • the UE transmits one transport block (TB) each time, and one TB has only one redundancy version.
  • the control word is transmitted on each MAR.
  • FIG. 10 shows a schematic diagram of a MAR of still another embodiment of the present application. As shown in FIG. 10, the UE selects a different number and different locations of the MAR to transmit a redundancy version, and transmits a control word on each MAR.
  • control word carries the UE ID and the end position indication information.
  • the base station demodulates the control word from each MAR.
  • End the end position indication
  • the previously received RVs carried on the same MAR as the UE ID carried in the control word are combined.
  • decoding obtaining the uplink information sent by the UE.
  • the end position indication (End) is “1”, indicating that the end of the uplink transmission is performed as an example.
  • the end position indication (End) information can be set to various forms, for example, the end position indication (End) can also be set to "0". The embodiment of the present application does not limit this.
  • control word carries a UE ID and a Bundling Size.
  • the base station when the base station detects that the number of MARs from the same UE ID is equal to the maximum number of transmissions, it indicates that the current uplink transmission of the UE identified by the UE ID ends.
  • the base station combines and decodes multiple redundancy versions of the same UE ID to obtain uplink information sent by the UE.
  • control word carries a UE ID, a Bundling Size, and an End Position Indicator (End).
  • the base station when the base station detects that the number of MARs from the same UE ID is equal to the maximum number of transmissions or the end position indication (End) of the control word is "1", it indicates that the current uplink transmission of the UE identified by the UE ID ends.
  • the base station combines and decodes all the received RVs on the same MAR that are carried in the control word, and obtains the uplink information sent by the UE.
  • the resource groups described in the foregoing embodiments may be selected by the UE itself. Or it can be specified by the standard or pre-agreed by the UE and the base station.
  • the UE places one or more RVs that need to be transmitted on each MAR in the resource and sends it to the network side.
  • the uplink data transmitted to the network side on each target MAR is the same.
  • FIG. 11 shows a manner in which a UE sends multiple redundancy versions in an embodiment of the present application.
  • the UE transmits one TB at a time, and the TB includes multiple redundancy versions.
  • the TB of UE#1 includes four redundancy versions, which are RV0, RV1, RV2, and RV3, respectively.
  • the respective TBs of UE#2 and UE#3 include 2 redundancy versions, both of which are RV0 and RV1.
  • Figure 12 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • time-frequency resource blocks in different frequency domains are defined as one resource group, such as time discontinuity, different multi-access signatures, and lengths are not fixed.
  • resource group #1 can transmit 4 different versions of RV, which are RV0, RV1, RV2, and RV3, respectively, and are distributed in different time domains and frequency domains.
  • Resource group #2 can transfer 2 versions of RV for RV0 and RV1.
  • Resource group #3 only transmits one redundancy version RV0.
  • UE#1 selects resource group #1
  • UE#2 selects resource group #2
  • UE#3 selects resource group #3.
  • Each UE places the RVs generated by the respective TBs on each MAR of the selected resource group.
  • the eNB combines and decodes the redundancy versions on all the MARs of each resource group to obtain uplink information that the UE sends to the eNB.
  • FIG. 13 illustrates another manner in which a UE transmits multiple redundancy versions according to an embodiment of the present application.
  • the UE transmits one TB at a time and has multiple RVs.
  • the UE selects different numbers and different locations of the MAR for transmission.
  • the RV version carried on each MAR is fixed.
  • the control word is transmitted on each MAR.
  • the control word carries a UE ID, a Bundling Size, and an End Position Indicator (End).
  • the base station detects that the number of MARs from the same UE ID is equal to the maximum number of transmissions, or the end position indication (End) of the control word is "1", it indicates that the current uplink transmission of the UE ends.
  • Figure 14 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • the UE transmits one TB at a time and has multiple RVs.
  • the UE selects different numbers and different locations of the MAR for transmission.
  • the UE places the RV of the version number specified by the MAR on a different MAR and places a control word on all MARs.
  • control word carries an RV ID to indicate a version number of the RV carried on the MAR.
  • the base station obtains the version number of the RV according to the pre-corresponding rules of MAR and RV, and combines them. Specifically, for the RV of the same version number, a method of combining before and after (Chase Combing, CC) is used. For the RV of different version numbers, the method of Incremental Redundancy (IR) merging is adopted.
  • Figure 15 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • the eNB counts the MARs from each UE. When the count exceeds a threshold, all received RVs from each UE are separately translated. code.
  • the eNB starts the merge decoding after receiving two MARs from the same UE.
  • slot #2 the MAR resource selected by UE#1 collides with the MAR resource selected by UE#2.
  • slot #3 the eNB receives the number of MARs from UE#1 reaching the threshold.
  • the eNB combines RV0 and RV2 for decoding. If the decoding is successful, the eNB feeds back an ACK to the UE. If the decoding fails, the eNB performs the second merge decoding when receiving the RV3.
  • the eNB may enable the eNB to initiate a merge decoding mechanism.
  • FIG. 16 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • the eNB performs combined decoding on the redundancy versions of all UEs at regular intervals (or time periods). As shown in FIG. 16, it is assumed that the eNB performs merge decoding once every two slots. In slot 2, the eNB decodes the received RV0 from UE#1, decodes RV0 from UE#2, and combines the two RV0s from UE#3 for decoding. If the decoding is successful, the eNB feeds back an ACK to the UE. If the decoding fails, the eNB performs a second merge decoding in slot #4. In this embodiment, when the partial control word sends a collision, the eNB may enable the eNB to initiate a merge decoding mechanism.
  • FIG. 17 shows still another manner in which the UE sends multiple redundancy versions in the embodiment of the present application.
  • the UE transmits multiple TBs at a time and has multiple RVs.
  • the UE selects different numbers and different locations of the MAR for transmission.
  • the control word is transmitted on each MAR.
  • the control word carries the TB ID in addition to the ID of the UE, the Bundling Size and the End Position indication (End).
  • the TB ID is used to distinguish which TB the RV belongs to.
  • Figure 18 shows a schematic diagram of a MAR of yet another embodiment of the present application.
  • the base station needs to combine and decode the redundancy version with the same UE ID and the same TB ID, so as to obtain the uplink information sent by the UE.
  • the eNB feeds back an ACK to the UE after successful decoding. After receiving the ACK, the UE starts to send the uplink information of the next TB. If the uplink information fails to be sent, the uplink information of the failed transmission may be resent in the following two ways.
  • the eNB feeds back NACK information to the UE.
  • the UE performs retransmission after receiving the NACK information.
  • the eNB does not feed back NACK information to the UE.
  • the UE determines that the transmission fails and performs retransmission.
  • you can select the same resource group or MAR as before.
  • You can also reselect different resource groups or MARs. For example, use a larger number of MARs with higher diversity in retransmission to improve the reliability of transmission.
  • the UE transmits a redundancy version carrying the uplink information by using frequency diversity or signature diversity (or any combination of time diversity, frequency diversity, and signature diversity).
  • frequency diversity or signature diversity or any combination of time diversity, frequency diversity, and signature diversity.
  • the UE sends the at least one redundancy version to the base station on the multiple target MARs, and the base station receiving terminal device sends the at least one redundancy version to the base station on multiple target MARs.
  • the UE determines the MAR (ie, the target MAR) used when transmitting the redundancy version in a different manner.
  • the base station receives the MAR used by the UE to send the redundancy version in different manners, so as to receive the redundancy version sent by the UE on the target MAR.
  • the UE selects the MAR to transmit the redundancy version according to the preset rule.
  • the base station can learn, according to the preset rule, that the UE sends the MAR used by the redundancy version, so as to receive the redundancy version on the corresponding MAR reception.
  • the UE refers to a preset rule (ie, preset bundling information) and informs the base station of the MAR actually selected when the redundancy version is transmitted.
  • the base station can also know which MAR resources the UE sends the redundancy version and receive.
  • the UE autonomously determines the MAR resource used when transmitting the redundancy version, and informs the base station (eg, transmitting indication information, etc.) the MAR used when transmitting the redundancy version.
  • the base station receives the redundancy version on the target MAR according to the indication information sent by the UE.
  • the base station combines the at least one redundancy version to obtain uplink information.
  • the base station receives the redundancy version sent by the UE, and performs combined decoding to obtain uplink information sent by the UE.
  • the base station may perform combined decoding on the received multiple RVs of the UE when the number of the MARs sent by one UE reaches a preset number based on the preset number of the MARs.
  • This embodiment can refer to the foregoing description of FIG. For the sake of brevity, no further details are given here.
  • the base station performs combined decoding on the received redundancy version sent by one UE based on the preset time period.
  • This embodiment can refer to the description made in the foregoing FIG. I will not repeat them here.
  • the method for granting uplink information without authorization in the embodiment of the present application includes a redundancy version of the uplink information.
  • the flexibility of transmitting uplink information can be improved while ensuring low latency.
  • the method for transmitting the uplink information without authorization provided by the embodiment of the present application is described in detail above with reference to FIG. 1 to FIG.
  • the network device and the terminal device in the embodiments of the present application are described below with reference to FIG. 19 and FIG.
  • FIG. 19 shows a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • the terminal device 500 includes:
  • the determining unit 510 is configured to determine, from the unlicensed resources, a plurality of target multiple access resources MAR that carry at least one redundancy version, where each redundancy version includes at least uplink information that the terminal device needs to send to the network device, where the multiple The target MAR can be distinguished by frequency diversity or signature diversity;
  • the sending unit 520 is configured to send the at least one redundancy version to the network device on the multiple target MARs.
  • the plurality of target MARs are capable of passing frequency diversity, signature diversity, and time division Distinguish between any combination of sets.
  • the terminal device 500 provided by the embodiment of the present application may correspond to the terminal device described in the foregoing method 200. Moreover, each module or unit in the terminal device 500 is used to execute a corresponding process performed by the terminal device in the foregoing method 200. For the sake of brevity, it will not be repeated here.
  • the terminal device 500 is presented in the form of a functional unit.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above. Device.
  • ASIC application-specific integrated circuit
  • the terminal device 500 can take the form shown in FIG.
  • the functions implemented by the determining unit 510 and the transmitting unit 520 can be implemented by the processor 101 and the memory 102 of FIG.
  • the memory is used to store a computer program, and the processor executes the corresponding flow executed by the terminal device in the above method embodiment by calling and executing a computer program stored in the memory.
  • the terminal device may include a processor, a transceiver, and a memory.
  • the processor is for controlling transceiver transceiver signals
  • the memory is for storing a computer program
  • the processor is for calling and running the computer program from the memory, such that the terminal device performs corresponding operations and/or steps in the above method embodiments.
  • the present application further provides a chip system (or chip), which includes a processor for implementing the functions involved in the terminal device in the method embodiment of the foregoing aspect, for example, receiving or processing the method involved in the foregoing method. Data and / or information.
  • the chip system further includes a memory that stores program instructions and data necessary for the terminal device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • the chip system can be installed on the terminal device for implementing the functions involved in the terminal device in the foregoing method embodiment.
  • the determining unit 510 can be a processor and the transmitting unit 520 can be a transceiver.
  • the terminal device in the embodiment of the present application transmits a redundancy version carrying the uplink information by using frequency diversity or signature diversity (or any combination of time diversity, frequency diversity, and signature diversity).
  • frequency diversity or signature diversity or any combination of time diversity, frequency diversity, and signature diversity.
  • FIG. 20 shows a schematic block diagram of a network device 600 in accordance with an embodiment of the present application. As shown in FIG. 20, the network device 600 includes:
  • the receiving unit 610 is configured to receive at least one redundancy version that is sent by the terminal device on the multiple target multiple access resources MAR, where the multiple target MARs are determined by the terminal device from the unlicensed resources, and each redundancy version includes at least The terminal device needs uplink information sent to the network device, and the plurality of MARs can be distinguished by frequency diversity or signature diversity;
  • the processing unit 620 is configured to combine the at least one redundancy version to obtain uplink information.
  • the plurality of target MARs can be distinguished by any combination of frequency diversity, signature diversity, and time diversity.
  • the network device 600 provided by the embodiment of the present application may correspond to the network device described in the foregoing method 200. Moreover, each module or unit in the network device 600 is used to perform a corresponding process performed by the network device in the foregoing method 200. For the sake of brevity, it will not be repeated here.
  • network device 600 is presented in the form of functional units.
  • a "unit” herein may refer to an application-specific integrated circuit (ASIC), circuitry, a processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other functions that provide the functionality described above.
  • ASIC application-specific integrated circuit
  • network device 600 can take the form shown in FIG.
  • the functions implemented by the receiving unit 610 and the processing unit 620 can be implemented by the processor 101 and the memory 102 of FIG. Specifically, the memory stores a computer program, and the processor executes the corresponding process executed by the network device in the foregoing method embodiment by calling and executing a computer program stored in the memory.
  • the network device can include a processor, a transceiver, and a memory.
  • the processor is for controlling transceiver transceiver signals
  • the memory is for storing a computer program
  • the processor is for calling and running the computer program from the memory, such that the network device performs the corresponding operations and/or steps in the above method embodiments.
  • the present application further provides a chip system (or chip), which includes a processor for implementing the functions involved in the network device in the method embodiment of the foregoing aspect, for example, receiving or processing the method involved in the foregoing method. Data and / or information.
  • the chip system also includes a memory for storing the necessary program instructions and data for the network device.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • receiving unit 610 can be a transceiver and processing unit 620 can be a processor.
  • the network device in the embodiment of the present application carries the redundancy version of the uplink information transmitted by the receiving terminal device by using frequency diversity or signature diversity (or any combination of time diversity, frequency diversity, and signature diversity).
  • frequency diversity or signature diversity or any combination of time diversity, frequency diversity, and signature diversity.
  • 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.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the 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 of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the function can be stored if it is implemented in the form of a software functional unit and sold or used as a standalone product.
  • a computer readable storage medium Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

本申请公开了一种免授权的传输上行信息的方法、网络设备和终端设备,能够提高上行传输的灵活性。该方法包括:终端设备从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括终端设备需要发送给网络设备的上行信息,该多个目标MAR能够通过频率分集或签名分集进行区分;终端设备在该多个目标MAR上向网络设备发送该至少一个冗余版本。

Description

免授权的传输上行信息的方法、网络设备和终端设备
本申请要求于2016年9月30日提交中国专利局、申请号为201610870865.2、申请名称为“免授权的传输上行信息的方法、网络设备和终端设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域,并且更具体地,涉及一种免授权的传输上行信息的方法、网络设备和终端设备。
背景技术
无线蜂窝网络,例如,长期演进(Long Term Evolution,LTE)系统中,终端设备在发送上行数据之前,首先需要与基站建立无线资源控制连接,进入无线资源控制连接状态,并在获得基站的授权指令后,才能根据基站的指令要求发送上行数据。这种上行发送数据的方法称为授权传输。由于终端设备从确定有上行数据需要发送到从空口将数据发送出去,需要大量的信令交互,因此,授权传输的时延较大。
大规模机器通信是未来第五代通信技术中的一个重要应用场景。在MTC通信场景下,终端设备的数量庞大,业务类型以小数据包业务为主,而且对低时延有一定的要求。这种场景中,免授权传输被认为是一种优于授权传输的传输上行数据方法。免授权传输的基本思想是数据“即来即走”,即终端确定有上行数据要发送时,不必经过发送上行调度请求和等待接收基站的授权指令交互过程,而是直接将数据经过的一定处理后发送给基站。
而低时延高可靠性通信(Ultra-Reliable Low Latency Communication,URLLC)也是5G中的重要场景。对车联网、无人驾驶、工业控制等一些业务来说,系统容量并不是主要的问题,但是对于时延和可靠性却有着很高的要求。因此,免授权传输被认为是更加适用于低时延高可靠性的场景。
现有技术中提供的免授权的传输上行信息的方法,是在连续上行子帧上多次发送同一个传输块TB而无需等待确定应答(Acknowledgement,ACK)或否定应答(Negative Acknowledgement,NACK),这种技术称为子帧捆绑(Transmission Time Interval Bundling,TTI Bundling)。但是子帧捆绑技术仅仅利用了时间上的分集来缩短时延,灵活性较低。
发明内容
本申请提供一种传输免授权的传输上行信息的方法、网络设备和终端设备,能够提高上行传输的灵活性。
第一方面,本申请提供一种免授权的传输上行信息的方法,该方法包括:终端设备从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括该终端设备需要发送给网络设备的上行信息,该多个目标MAR能够通过频率分集 或签名分集进行区分;终端设备在该多个目标MAR上向网络设备发送该至少一个冗余版本。
应理解,本申请实施例中所述的冗余版本(Redundancy Version,RV)用于实现增量冗余(Incremental redundancy,IR)的混合自动重传请求(Hybrid Automatic Repeat Request,HARQ),即,将对传输块(Transport Block,TB)生成的冗余比特分成若干组,每个RV定义一个传输起始点,首次传输和各次重传分别使用不同的RV,以实现冗余比特的逐步积累,完成增量冗余HARQ。更具体地,关于冗余版本的详细说明也可以参考现有技术中的定义,这里不做详述。特别地,当各个MAR上发送的冗余版本一致时,这种增量冗余的方法就变成Chase Combining(蔡司合并,简称为CC)方法。
在一种可能的实现方式中,该多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
在一种可能的实现方式中,终端设备确定承载至少一个冗余版本的多个目标MAR,包括:终端设备根据捆绑信息,确定该至少一个冗余版本对应的多个第一MAR,其中,捆绑信息是终端设备与网络设备预先约定的,捆绑信息中包括以下信息中的至少一个:发送上行信息时使用冗余版本的数量、发送上行信息时使用的冗余版本占用MAR的数量和大小、该多个第一MAR的位置、发送上行信息时使用的冗余版本与该多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS;终端设备从该多个第一MAR中确定该多个目标MAR。
在一种可能的实现方式中,该方法还包括:终端设备向网络设备发送第一控制信道,第一控制信道上承载有第一指示信息,第一指示信息用于指示该多个目标MAR,以便于网络设备根据第一指示信息在该多个目标MAR上接收该至少一个冗余版本。
在一种可能的实现方式中,该多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,第二控制信道上承载有第二指示信息,第二指示信息用于指示该标识信息和该版本号,以便于网络设备对该至少一个冗余版本进行合并,得到上行信息。
在一种可能的实现方式中,终端设备向网络设备发送第三控制信道,第三控制信道上承载有第三指示信息,第三指示信息用于指示终端设备基于该捆绑信息确定的该多个目标MAR,以便于网络设备根据捆绑信息和第三指示信息,在该多个第一MAR中的目标MAR上接收该至少一个冗余版本。
在一种可能的实现方式中,该至少一个冗余版本的版本号相同时,该多个目标MAR上传输的上行数据相同。
第二方面,本申请提供一种免授权的传输上行信息的方法,该方法包括:网络设备接收终端设备在多个目标多接入资源MAR上发送的至少一个冗余版本,该多个目标MAR是终端设备从免授权资源中确定的,每个冗余版本至少包括终端设备需要发送给网络设备的上行信息,该多个MAR能够通过频率分集或签名分集进行区分;网络设备对该至少一个冗余版本进行合并,得到上行信息。
在一种可能的实现方式中,该多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
在一种可能的实现方式中,网络设备对该至少一个冗余版本进行合并,得到上行信息, 包括:网络设备根据捆绑信息,对该至少一个冗余版本进行合并,得到上行信息,其中,捆绑信息是终端设备与网络设备预先约定的,捆绑信息中包括以下信息中的至少一个:发送上行信息时使用冗余版本的数量、发送上行信息时使用的冗余版本占用MAR的数量和大小、该多个第一MAR的位置、发送上行信息时使用的冗余版本与该多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS。
在一种可能的实现方式中,该方法还包括:网络设备接收终端设备发送的第一控制信道,第一控制信道承载有第一指示信息,第一指示信息用于指示该多个目标MAR;以及,网络设备对该至少一个冗余版本进行合并,得到该上行信息,包括:网络设备根据第一指示信息,对该至少一个冗余版本进行合并,得到上行信息。
在一种可能的实现方式中,该多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,第二控制信道上承载有第二指示信息,第二指示信息用于指示该标识信息和该版本号,以及,网络设备对该至少一个冗余版本进行合并,得到上行信息,包括:网络设备根据第二指示信息,对该至少一个冗余版本进行合并,得到上行信息。
在一种可能的实现方式中,该方法还包括:网络设备接收终端设备发送的第三控制信道,第三控制信道承载有第三指示信息,第三指示信息用于指示终端设备基于捆绑信息确定的该多个目标MAR;以及,网络设备对该至少一个冗余版本进行合并,得到上行信息,包括:网络设备根据该第三指示信息,对该至少一个冗余版本进行合并,得到上行信息。
在一种可能的实现方式中,该至少一个冗余版本的版本号相同,该多个目标MAR上传输的上行数据相同。
第三方面,本申请提供一种终端设备,用于执行第一方面或第一方面的任意可能的实现方式中的方法。具体地,该终端设备包括执行第一方面或第一方面的任意可能的实现方式中的方法的单元。
第四方面,本申请提供一种网络设备,用于执行第二方面或第二方面的任意可能的实现方式中的方法。具体地,该网络设备包括执行第二方面或第二方面的任意可能的实现方式中的方法的单元。
第五方面,本申请提供一种终端设备,该终端设备包括处理器和存储器。存储器用于存储计算机程序,处理器用于从存储器中调用并运行计算机程序。当程序被运行时,该处理器执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第六方面,本申请提供一种网络设备,该网络设备包括处理器和存储器。存储器用于存储计算机程序,处理器用于从存储器中调用并运行计算机程序。当程序被运行时,该处理器执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面,本申请提供一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第一方面或第一方面的任意可能的实现方式中的方法的指令。
第八方面,本申请提供一种计算机可读介质,用于存储计算机程序,该计算机程序包括用于执行第二方面或第二方面的任意可能的实现方式中的方法的指令。
第九方面,本申请提供一种终端设备,该终端设备包括收发器、处理器和存储器。该处理器用于控制收发器收发信号,该存储器用于存储计算机程序,该处理器用于从存储器 中调用并运行该计算机程序,使得该终端设备执行上述第一方面中的方法。
第十方面,本申请提供一种网络设备,该网络设备包括收发器、处理器和存储器。该处理器用于控制收发器收发信号,该存储器用于存储计算机程序,该处理器用于从存储器中调用并运行该计算机程序,使得该网络设备执行第二方面中的方法。
第十一方面,本申请提供了一种芯片系统,该芯片系统包括处理器和收发器,用于终端设备实现上述第一方面及其任意可能的实现方式中所涉及的功能,例如,例如处理或发送上述方法中所涉及的数据和/或信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器用于存储终端设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
第十二方面,本申请提供了一种芯片系统,该芯片系统包括处理器和收发器,用于网络设备实现上述第二方面及其任意可能的实现方式中所涉及的功能,例如,例如接收或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中,所述芯片系统还包括存储器,所述存储器用于存储终端设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
第十三方面,本申请提供一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码在计算机上运行时,使得计算机执行上述第一方面及其任意可能的实现方式中的方法。
第十四方面,本申请提供一种计算机程序产品,所述计算机程序产品包括:计算机程序代码,当所述计算机程序代码在计算机上运行时,使得计算机执行上述第二方面及其任意可能的实现方式中的方法。
本申请实施例的免授权的传输上行信息的方法、网络设备和终端设备,终端设备通过使用频率分集或签名分集(或者,时间分集、频率分集和签名分集的任意组合)的MAR传输承载有上行信息的冗余版本。在保证低时延的前提下,能够提高传输上行信息时的灵活性。
附图说明
图1是本申请实施例的计算机设备(或系统)100的示意图。
图2示出了本申请实施例的免授权传输上行信息的方法200的示意性交互图。
图3示出了本申请实施例的UE发送一个冗余版本的一种方式。
图4示出了本申请一实施例的MAR的示意图。
图5示出了本申请另一实施例的MAR的示意图。
图6示出了本申请再一实施例的MAR的示意图。
图7示出了本申请又一实施例的MAR的示意图。
图8示出了本申请又一实施例的MAR的示意图。
图9示出了本申请实施例的UE发送一个冗余版本的另一种方式。
图10示出了本申请又一实施例的MAR的示意图。
图11示出了本申请实施例的UE发送多个冗余版本的一种方式。
图12示出了本申请又一实施例的MAR的示意图。
图13示出了本申请实施例的UE发送多个冗余版本的另一种方式。
图14示出了本申请又一实施例的MAR的示意图。
图15示出了本申请又一实施例的MAR的示意图。
图16示出了本申请又一实施例的MAR的示意图。
图17示出了本申请又一实施例的MAR的示意图。
图18示出了本申请又一实施例的MAR的示意图。
图19示出了根据本申请实施例的终端设备500的示意性框图。
图20示出了根据本申请实施例的网络设备600的示意性框图。
具体实施方式
下面将结合附图,对本申请中的技术方案进行描述。
本申请提供的技术方案,可以应用于无线蜂窝网络的各种通信系统,例如:全球移动通信(Global System of Mobile communication,GSM)系统,码分多址(Code Division Multiple Access,CDMA)系统,宽带码分多址(Wideband Code Division Multiple Access Wireless,WCDMA)系统,通用分组无线业务(General Packet Radio Service,GPRS)系统,长期演进(Long Term Evolution,LTE)系统,通用移动通信系统(Universal Mobile Telecommunications System,UMTS),下一代移动通信系统(例如,5G),和机器与机器(Machine to Machine,M2M)通信系统等。
首先,对本申请实施例涉及到的相关概念作简单介绍。
应理解,传统的授权频谱资源一般需要国家或者地方无线委员会审批才可以使用的频谱资源。不同系统(例如,LTE系统、WiFi系统)或不同运营商的系统不可以共享使用授权频谱资源。
传统的免授权频谱资源传输是指无需系统分配,各个通信设备可以共享使用免许可频谱包括的资源。免许可频段上的资源共享是指对特定频谱的使用只规定发射功率、带外泄露等指标上的限制,以保证共同使用该频段的多个设备之间满足基本的共存要求。
需要说明的是,本申请实施例所描述的免授权传输有别于上述免授权频谱资源传输,需要经过用户接入网络和基站为用户分配免授权传输资源的过程。当用户有数据需要发送时,直接在基站分配的免授权资源上发送。因此,本申请实施例中所述的免授权频谱资源传输与传统的免授权频谱资源传输不同的是,本申请实施例中用于免授权传输的资源需要系统预先分配。
本申请结合网络设备描述了各个实施例。网络设备可以是用于与移动台通信的设备,网络设备可以是无线局域网(Wireless Local Area Networks,WLAN)中的接入点(ACCESS POINT,AP),GSM或码分多址(Code Division Multiple Access,CDMA)中的基站(Base Transceiver Station,BTS)。也可以是WCDMA中的基站(NodeB,NB),还可以是LTE中的演进型基站(Evolutional Node B,eNB或eNodeB),或者中继站或接入点,或者车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)中的网络设备等。
在本申请实施例中,网络设备能够通过上述免授权传输进行无线通信。另外,网络设备也可以通过授权频谱资源传输进行无线通信。
本申请结合终端设备描述了各个实施例。终端设备也可以称为用户设备(User  Equipment,UE)、移动台、接入终端、用户单元、用户站、移动站、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是无线局域网(Wireless Local Area Networks,WLAN)中的站点(STAION,ST),可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及未来通信网络(例如,5G)中的移动台或者未来演进的PLMN网络中的终端设备等。
在本申请实施例中,终端设备能够通过上述免授权传输进行无线通信。另外,终端设备也可以通过授权频谱资源传输进行无线通信。
本申请实施例中所述的网络设备和终端设备可以如图1中所示的计算机设备(或系统)100的方式来实现。
图1是本申请实施例提供的计算机设备(或系统)100的示意图。其中,计算机设备100包括至少一个处理器101、存储器102、通信总线103和至少一个通信接口104。
处理器101可以为中央处理器(CPU)、微处理器、特定应用集成电路(application-specific integrated circuit,ASIC),或一个或多个用于控制本申请技术方案程序执行的集成电路。
存储器102可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory,EEPROM)、只读光盘(Compact Disc Read-Only Memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器可以是独立存在,也可以和处理器集成在一起。
其中,存储器102用于存储执行本申请技术方案的应用程序代码,处理器101用于执行存储器102中存储的应用程序代码。
在具体实现中,作为一种实施例,处理器101可以包括一个或多个CPU。例如图1中所示的CPU0和CPU1。
在具体实现中,作为一种实施例,计算机设备100可以包括多个处理器,每个处理器可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,计算机设备100还可以包括输出设备105和输入设备106。输出设备105和处理器101通信,可以以多种方式来显示信息。例如,输出设备105可以是液晶显示器(Liquid Crystal Display,LCD),发光二级管(Light Emitting Diode,LED)显示设备,阴极射线管(cathode ray tube,CRT)显示设备,或投影仪(projector)等。输入设备106和处理器101通信,可以以多种方式接受用户的输入。例如,输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备100可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中,计算机设备100可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant,PDA)、移动手机、平板电脑、无线终端设备、通信设备、嵌入式设备或有图1中类似结构的设备。本申请实施例不限定计算机设备100的类型。
应理解,在本申请实施例中,编号“第一”、“第二”仅仅为了区分不同的对象。例如,为了区分不同的指示信息,不应对本申请实施例的保护范围构成任何限定。
还应理解,以下各个实施例的方法中所示的步骤或操作仅仅作为示例,也可以执行其他操作或者各种操作的变形。并且,在具体实施时,各个步骤还可以按照与本申请实施例中所述的不同的顺序来执行,并且有可能并非执行本申请实施例所示出的全部操作或步骤。或者,也可能执行本申请各实施例所示出的更多的操作或步骤。
为了便于理解和说明,以下仅以UE和基站分别作为终端设备和网络设备的示例,对本申请实施例的免授权的传输上行信息的方法进行说明。
图2示出了本申请实施例的免授权传输上行信息的方法的示意性交互图。如图2所示,该方法主要包括步骤210至步骤230。
210、UE确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括该终端设备需要发送给基站的上行信息,该多个目标MAR能够通过频率分集或签名分集进行区分。
应理解,一个多接入资源(Multiple Access Resource,MAR)由一个多接入物理资源(Multiple Access Physical Resource,MAPR)和一个多接入签名(MA Signature,MAS)构成。其中,MAPR专指时频资源(Time Frequency Resource)。而MAS至少包括以下一种但不限于:码本(Codebook)、码字(Codeword)、序列(Sequence)、交织图样(Interleaver pattern)、映射图样(mapping pattern)、解调参考信号(Demodulation reference signal)、前导字(Preamble)、空域(Spatial-dimension)和功率域(Power dimension)。
可选地,作为一个实施例,该多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
需要说明的是,UE在发送上行信息时,可以发送一个冗余版本或多个冗余版本,本申请实施例对此不作任何限定。
这里所说的一个冗余版本是指仅有一个版本号。多个冗余版本是指多个版本号。应理解,本申请实施例中所述的冗余版本(Redundancy Version,RV)用于实现增量冗余(Incremental redundancy,IR)的混合自动重传请求(Hybrid Automatic Repeat Request,HARQ),即,将对传输块(Transport Block,TB)生成的冗余比特(Redundancy Bit)分成若干组,每个RV定义一个传输起始点,首次传输和各次重传分别使用不同的RV,以实现冗余比特的逐步积累,完成增量冗余HARQ。更具体地,关于冗余版本的详细说明也可以参考现有技术中的定义,这里不做详述。特别地,当各个MAR上发送的冗余版本一致时,这种增量冗余的方法就变成Chase Combining(蔡司合并,简称为CC)方法。
具体地,在本申请实施例中,UE确定承载至少一个冗余版本的多个目标MAR,包括多种方式。
方式1
UE根据捆绑信息确定目标MAR,其中,捆绑信息是终端设备和网络设备预先约定的。
其中,捆绑信息可以与以下几种因素相关:
是否重传:UE在重传时可以使用与初传相同的捆绑信息,也可以使用域初传不同的捆绑信息。例如,UE可以在重传时增加RV的数量、增加MAR的数量或将RV放置在分集更高的MAR上等。
UE的服务质量(Quality of Service,QoS):UE针对不同QoS要求的数据包,使用不同的捆绑信息。例如,对于时延要求较高的数据包,尽量选择频率分集或签名分集而不是时间分集。或者,基站可以通过系统的预设规则尝试在更短的时间内进行译码。又例如,针对可靠性要求较高的数据包,可以传输更多的RV、增加占用RV占用的MAR数量,将RV放置在分集更高的MAR上等。
具体地,本申请实施例中所述的捆绑(Bundling)信息可以包括以下信息中的至少一个:发送上行信息时使用冗余版本的数量、发送上行信息时使用的冗余版本占用MAR的数量和大小、MAR的位置、发送所述上行信息时使用的冗余版本与MAR的映射关系、每个MAR上承载冗余版本的数量和每个MAR能够使用的调制与编码策略(Modulation and Coding Scheme,MCS)。
可选地,作为一个实施例,该多个目标MAR中的每个目标MAR携带UE的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,第二控制信道上承载有第二指示信息,第二指示信息用于指示该标识信息和版本号,以便于基站对该至少一个冗余版本进行合并,得到上行信息。
在承载有冗余版本的MAR(即,目标MAR)携带有UE的标识信息和RV的版本号时,每个目标MAR可以单独携带控制信道(即,第二控制信道),控制信道上承载有UE标识信息和RV版本号的指示信息(即,第二指示信息)。这样,基站在接收到RV时,同时接收到携带在MAR上的UE的标识信息和RV的版本号。基站基于UE的标识信息和版本号能够获知每个RV的版本号和该RV所属的UE,从而可以对每个UE的RV进行合并译码。
即,在方式1中,UE发送冗余版本时使用哪些MAR完全是根据系统定义确定。这里,系统定义可以指由基站和UE预先约定。或者,系统定义也可以指由标准规定。
方式2
UE参考捆绑信息确定。
可选地,作为一个实施例,UE确定承载至少一个冗余版本的多个目标MAR,包括:
UE根据捆绑信息,确定至少一个冗余版本对应的多个第一MAR,其中,捆绑信息是该UE与网络设备预先约定的,捆绑信息中包括以下信息中的至少一个:发送上行信息时使用冗余版本的数量、发送上行信息时使用的冗余版本占用MAR的数量和大小、该多个第一MAR的位置、发送上行信息时使用的冗余版本与该多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS;
UE从该多个第一MAR中确定该多个目标MAR。
应理解,这里的第一MAR是指系统定义的承载RV的MAR。目标MAR是UE从多个第一MAR中确定的在实际发送RV时使用的MAR。
可以理解的是,在方式2中,网络侧仅能够获知系统预先定义MAR(即,网络侧仅知道第一MAR),而并不知道UE实际发送RV时使用的MAR。因此,UE需要告知网 络设备实际发送RV时使用的MAR(即,目标MAR)。
可选地,作为一个实施例,该方法还包括:
UE向网络设备发送第三控制信道,第三控制信道上承载有第三指示信息,第三指示信息用于指示该UE基于捆绑信息确定的该多个目标MAR,以便于网络设备根据捆绑信息和第三指示信息,在该多个第一MAR中的目标MAR上接收所述至少一个冗余版本。
可见,在方式2中,UE在捆绑信息的基础上确定目标MAR。与上方式1不同的是,在这种方式中,UE仅是将系统定义作为发送RV时的参考。因此,UE发送的承载RV的MAR(即,目标MAR)可能并不是完全按照系统定义。这种方式中,UE需要告知基站自己选定的发送RV的MAR。
方式3
UE自主确定。
可选地,作为一个实施例,该方法还包括:
UE向网络设备发送第一控制信道,第一控制信道上承载有第一指示信息,第一指示信息用于指示该多个目标MAR,以便于网络设备根据第一指示信息在该多个目标MAR上接收该至少一个冗余版本。
可以理解的是,由于在方式3中,UE发送RV时使用的MAR(即,目标MAR)可以完全是由UE自己确定。因此,在这种方式中,UE也需要将自己选定的承载RV的MAR告知网络侧。
UE基于以上多种方式确定了目标MAR后,会在目标MAR上向基站发送一个或多个冗余版本。每个冗余版本都至少包括了UE需要发送给基站的上行信息。
下面结合多个实施例,详细说明本申请实施例的目标MAR(即,用于承载冗余版本RV的MAR)。
图3示出了UE发送一个冗余版本的一种方式。如图3所示,UE每次发送一个传输块(Transport Block,TB),且TB只有一个冗余版本。
应理解,在本申请各个实施例中所述的一个冗余版本是指UE发送给网络侧的冗余版本的版本号相同,即,仅有一个版本号。同样的,多个冗余版本是指UE发送给网络侧的冗余版本有多个版本号。
以下,对目标MAR上仅承载一个冗余版本的情况进行说明。
图4示出了本申请一实施例的MAR的示意图。在本实施例中,将时间连续,采用相同多接入签名(Multiple Access Signature,MAS),长度固定的时频资源块定义为一个资源组。每个资源组中包括的多个MAR可以采用不同的调制与编码策略(modulation and coding scheme,MCS)。其中,每个资源组的划分在传输上行信息前由UE和基站已知。
本申请各个实施例中所述的资源组可以是UE自己选择,或者也可以采用半静态配置的方式。
应理解,这里所述的半静态配置是指UE初次发送RV时基于网络侧的预先配置,并存储网络侧的配置信息。每隔一定周期,UE使用与初次发送RV时相同的MAR资源发送RV。
如图4所示,UE#1选取资源组#1,UE#2选取资源组#3,UE#3选取资源组4。对于每个UE而言,将包括上行信息的冗余版本放置在所选资源组中的所有MAR上。
相对应地,在网络侧,基站将每个资源组上所有MAR上的冗余版本进行合并译码。在译码正确的情况下,基站可以获得UE发送的上行信息。
图5示出了本申请另一实施例的MAR的示意图。如图5所示,在本实施例中,将时间连续,采用相同多接入签名、长度不固定的时频资源块定义为一个资源组。
如图5所示,资源组#1、资源组#2与资源组#3、资源组#4有着不同的长度。UE#1选择资源组#1,UE#2选择资源组#3。UE#3选择资源组#4。UE将各自TB的RV放置在选定资源组中的每个MAR上。
相对应地,在网络侧,基站将每个资源组包括的所有MAR上的冗余版本进行合并译码,得到UE发送的上行信息。
图6示出了本申请再一实施例的MAR的示意图。在本实施例中,将时间不连续、采用相同多接入签名、长度不固定的时频资源块定义为一个资源组。在每个资源中,放置(或者说,承载)冗余版本多个MAR在时域上可以为连续的,或者也可以不连续。
如图6所示,资源组#1在时域上不连续。资源组#3和资源组#4在时域上连续。其中,UE#1选择资源组#1,UE#2选择资源组3,UE#3选择资源组4。每个UE分别将各自的TB产生的RV放置在选定资源组的每个MAR上。
相对应地,基站将每个资源组上所有MAR上的冗余版本进行合并译码,得到UE发送的上行信息。
图7示出了本申请又一实施例的MAR的示意图。在本实施例中,将时间不连续、采用相同多接入签名、长度不固定、在不同频域上的时频资源块定义为一个资源组。
如图7所示,资源组#1在时域上选取了不连续的资源,且分布在不同的频域上。UE#1选取资源组#1,UE#2选取资源组#2。UE#3选取资源组#3。UE分别将各自TB产生的RV放置在选定资源组的每个MAR上。
相对应地,基站将每个资源组的所有MAR上的冗余版本进行合并并译码,从而获取到UE发送给基站的上行信息。
图8示出了本申请又一实施例的MAR的示意图。在本实施例中,将时间不连续、采用不同多接入签名的、长度不固定且在不同频域上的时频资源块定义为一个资源组。
如图8所示,资源组#1在时域上选取了不连续的资源,且分布在不同的频域上。UE#1选取资源组#1。UE#2选取资源组#2。UE#3选取资源组#3。UE分别将各自的TB产生的RV放置在选定资源组的每个MAR上。
相对应地,在网络侧,基站将每个资源组上所有MAR的冗余版本进行合并后译码,得到UE发送给基站的上行信息。
图9示出了UE发送一个冗余版本的另一种方式。在本实施例中,UE每次发送一个传输块(Transport Block,TB),且一个TB仅有一个冗余版本。每个MAR上传送控制字。
图10示出了本申请又一实施例的MAR的示意图。如图10所示,UE选择不同数量、不同位置的MAR发送冗余版本,同时每个MAR上传送控制字。
可选地,作为一个实施例,控制字中携带UE ID和结束(End)位置指示信息。
相对应地,基站解调来自每个MAR的控制字。当检测到控制字的结束位置指示(End)为1时,将之前接收的所有与该控制字中携带的UE ID相同的MAR上承载的RV进行合 并译码,获取到UE发送的上行信息。
应理解,在本申请实施例中,仅将结束位置指示(End)为“1”时表明依次上行传输结束作为示例。显然,结束位置指示(End)信息可以设置为多种形式,例如,结束位置指示(End)也可以设置为“0”。本申请实施例对此不作任何限定。
可选地,作为一个实施例,控制字中携带UE ID和最大传输次数指示(Bundling Size)。
相对应地,当基站检测到来自同一个UE ID的MAR数目等于最大传输次数时,表明该UE ID所标识的UE的本次上行传输结束。
相对应地,基站将同一个UE ID的多个冗余版本进行合并译码,得到UE发送的上行信息。
可选地,作为一个实施例,控制字中携带UE ID、最大传输次数指示(Bundling Size)和结束位置指示(End)。
相对应地,当基站检测到来自同一UE ID的MAR数目等于最大传输次数或控制字的结束位置指示(End)为“1”时,表示该UE ID标识的UE的本次上行传输结束。基站将接收到的所有与该控制字中携带的UE ID相同的MAR上承载的RV进行合并译码,得到该UE发送的上行信息。
需要说明的是,以上各实施例中所述的资源组可以由UE自己选定。或者也可以由标准规定,或由UE和基站预先约定。UE将需要传输的一个或多个RV放置在资源中的每个MAR上发送给网络侧。
可选地,作为一个实施例,当UE发送给网络侧的至少一个冗余版本的版本号相同时,每个目标MAR上传输给网络侧的上行数据相同。
以下对冗余版本为多个的情况进行说明。
图11示出了本申请实施例的UE发送多个冗余版本的一种方式。在本实施例中,UE每次发送一个TB,该TB包括多个冗余版本。如图11所示,UE#1的TB包括4个冗余版本,分别为RV0、RV1、RV2和RV3。UE#2和UE#3各自的TB包括2个冗余版本,均为RV0和RV1。
图12示出了本申请又一实施例的MAR的示意图。在本实施例中,将时间不连续、采用不同多接入签名、长度不固定、在不同频域上的时频资源块定义为一个资源组。
如图12所示,资源组#1可以传送4个不同版本的RV,分别为RV0、RV1、RV2和RV3且分布在不同的时域和频域上。资源组#2可以传送2个版本的RV,为RV0和RV1。资源组#3仅传送一个冗余版本RV0。UE#1选取资源组#1,UE#2选取资源组#2,UE#3选取资源组#3。每个UE将各自TB产生的RV放置在选定资源组的每个MAR上。
相对应地,在网络侧,eNB将每个资源组的所有MAR上的冗余版本进行合并后译码,得到UE发送给eNB的上行信息。
图13示出了本申请实施例的UE发送多个冗余版本的另一种方式。在本实施例中,UE每次发送一个TB,且拥有多个RV。UE选择不同数量、不同位置的MAR进行发送。每个MAR上所携带的RV版本是固定的。每个MAR上传送控制字。其中,控制字中携带UE ID、最大传输次数指示(Bundling Size)和结束位置指示(End)。
相对应地,当基站检测到来自同一UE ID的MAR数目等于最大传输次数,或者控制字的结束位置指示(End)为“1”时,表示该UE的本次上行传输结束。
图14示出了本申请又一实施例的MAR的示意图。在本实施例中,UE每次发送一个TB,且拥有多个RV。UE选择不同数量、不同位置的MAR进行发送。UE在不同的MAR上放置该MAR规定的版本号的RV,并在所有MAR上放置控制字。
可选地,作为一个实施例,控制字中携带RV ID来指示该MAR上承载的RV的版本号。
相对应地,在网络侧,基站根据MAR和RV的预先对应规则来获得RV的版本号,并进行合并,具体地,针对相同版本号的RV,使用前后合并(Chase Combing,CC)的方法。针对不同版本号的RV,采用增量冗余(Incremental Redundancy,IR)合并的方法。
图15示出了本申请又一实施例的MAR的示意图。在本实施例中,eNB在解调每个MAR的控制字后,对来自每个UE的MAR进行计数,当计数超过一个门限时,对所有接收到的来自每个UE的RV分别进行合并译码。
如图15所示,假设eNB收到来自同一UE的2个MAR后开始合并译码。在时隙#2,UE#1选择的MAR资源与UE#2选择的MAR资源发生了碰撞。在时隙#3,eNB接收到来自UE#1的MAR数量达到门限。eNB将来自RV0和RV2合并后进行译码。如果译码成功,eNB向UE反馈ACK。如果译码失败,eNB则在收到RV3时,进行第二次合并译码。本实施例可以在部分控制字发送碰撞时,使eNB启动合并译码机制。
图16示出了本申请又一实施例的MAR的示意图。在本实施例中,eNB每隔一定时间(或者说,时段),对所有UE的冗余版本进行合并译码。如图16所示,假设eNB每隔两个时隙进行一次合并译码。在时隙2,eNB将接收到的来自UE#1的RV0译码,将来自UE#2的RV0译码,将来自UE#3的2个RV0进行合并后译码。如果译码成功,eNB向UE反馈ACK。如果译码失败,eNB在时隙#4进行第二次合并译码。本实施例可以在部分控制字发送碰撞时,使eNB启动合并译码机制。
图17示出了本申请实施例UE发送多个冗余版本的再一种方式。在本实施例中,UE每次发送多个TB,且拥有多个RV。UE选择不同数量、不同位置的MAR进行发送。同时每个MAR上传送控制字。与前述实施例不同的是,控制字中除了携带UE的ID、最大传输次数指示(Bundling Size)和结束位置指示(End),还携带有TB ID。TB ID用来区分该RV属于哪一个TB。
图18示出了本申请又一实施例的MAR的示意图。在本实施例中,相对应地,基站在进行合并译码时,需要合并UE ID相同且TB ID相同的冗余版本并译码,从而得到该UE发送的上行信息。
在上述各个实施例中,eNB在译码成功后向UE反馈ACK。UE接收到ACK后开始发送下一个TB的上行信息。如果上行信息发送失败,可以有以下两种方式对传输失败的上行信息重新进行发送。
(1)eNB向UE反馈NACK信息。
相对应地,UE在接收到NACK信息后进行重传。
(2)eNB不向UE反馈NACK信息。
相对应地,若UE在预设时段内没有接收到eNB反馈的ACK信息,则判断传输失败,并进行重传。重传时可以选择与之前相同的资源组或MAR。也可以重新选择不同的资源组或MAR。例如,在重传时使用数量更多、分集更高的MAR,以提高传输的可靠性。
可见,本申请实施例的免授权的传输上行信息的方法,UE通过频率分集或签名分集(或者,时间分集、频率分集和签名分集的任意组合)传输承载上行信息的冗余版本。与现有技术相比,在保证低时延的前提下,提高了传输上行信息时的灵活性。
220、UE在该多个目标MAR上向基站发送该至少一个冗余版本,基站接收终端设备在多个目标MAR上向基站发送该至少一个冗余版本。
根据前文所述,UE采用不同的方式确定发送冗余版本时使用的MAR(即,目标MAR)。相对应地,基站采用不同的方式接收UE发送冗余版本时使用的MAR,从而在目标MAR上接收到UE发送的冗余版本。
例如,在上述方式1中,UE根据预设规则选择MAR发送冗余版本。相对应地,基站根据预设规则能够获知UE发送冗余版本使用的MAR,从而在对应的MAR接收上接收冗余版本。
又例如,在方式2中,UE参考预设规则(即,预设的捆绑信息),并告知基站发送冗余版本时实际选择的MAR。相对应地,基站也能获知UE在哪些MAR资源上发送了冗余版本,并进行接收。
再例如,在方式3中,UE自主确定发送冗余版本时使用的MAR资源,并告知基站(例如,发送指示信息等)发送冗余版本时使用的MAR。相对应地,基站根据UE发送的指示信息目标MAR上接收冗余版本。
230、基站对该至少一个冗余版本进行合并,得到上行信息。
具体地,基站在接收到UE发送的冗余版本,并进行合并译码,得到UE发送的上行信息。
可选地,基站可以基于预设的MAR的数目,当接收到一个UE发送的MAR的数目达到预设数目时,对接收到的该UE的多个RV进行合并译码。本实施例可参考前文对图15所作的说明。为了简洁,此处不作赘述。
可选地,基站基于预设时段,对接收到的一个UE发送的冗余版本进行合并译码。本实施例可参考前文图16所作的说明。此处不作赘述。
需要说明的是,上述各实施例中资源组中所包括的MAR的数目仅作为示例,不应对本申请实施例的保护范围构成任何限定。
本申请实施例的免授权的传输上行信息的方法,UE通过使用频率分集或签名分集(或者,时间分集、频率分集和签名分集的任意组合)的MAR传输包括上行信息的冗余版本。在保证低时延的前提下,能够提高传输上行信息的灵活性。
上文结合图1至图18,详细说明了本申请实施例提供的免授权的传输上行信息的方法。以下结合图19和图20对本申请实施例的网络设备和终端设备进行说明。
图19示出了根据本申请实施例的终端设备500的示意性框图。如图19所示,终端设备500包括:
确定单元510,用于从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括该终端设备需要发送给网络设备的上行信息,该多个目标MAR能够通过频率分集或签名分集进行区分;
发送单元520,用于在该多个目标MAR上向网络设备发送该至少一个冗余版本。
可选地,作为一个实施例,该多个目标MAR能够通过频率分集、签名分集和时间分 集的任意组合进行区分。
本申请实施例提供的终端设备500,可以对应上述方法200中描述的终端设备。并且,终端设备500中各模块或单元分别用于执行上述方法200中由终端设备所执行的相应流程。为了简洁,此处不再赘述。
应理解,在本实施例中,终端设备500是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit,ASIC)、电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路,和/或其他可以提供上述功能的器件。在一个简单的实施例中,本领域的技术人员可以想到终端设备500可以采用图1所示的形式。确定单元510和发送单元520实现的功能可以通过图1的处理器101和存储器102来实现。具体的,存储器用于存储计算机程序,处理器通过调用并执行存储器中存储的计算机程序来执行上述方法实施例中由终端设备执行的相应流程。
在一种可能的实现方式中,终端设备可以包括处理器、收发器和存储器。处理器用于控制收发器收发信号,存储器用于存储计算机程序,处理器用于从存储器中调用并运行该计算机程序,使得该终端设备执行上述方法实施例中的相应操作和/或步骤。
另外,本申请还提供一种芯片系统(或者,芯片),该芯片系统包括处理器,用于实现上述方面方法实施例中终端设备所涉及的功能,例如,例如接收或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中,芯片系统还包括存储器,存储器存储有终端设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
可以理解的是,该芯片系统可以安装在终端设备上,用于实现上述方法实施例中终端设备涉及的功能。例如,确定单元510可以为处理器,发送单元520可以为收发器。
本申请实施例的终端设备,通过使用频率分集或签名分集(或者,时间分集、频率分集和签名分集的任意组合)传输承载上行信息的冗余版本。在保证低时延的前提下,能够提高传输上行信息时的灵活性。
图20示出了根据本申请实施例的网络设备600的示意性框图。如图20所示,网络设备600包括:
接收单元610,用于接收终端设备在多个目标多接入资源MAR上发送的至少一个冗余版本,该多个目标MAR是终端设备从免授权资源中确定的,每个冗余版本至少包括该终端设备需要发送给该网络设备的上行信息,该多个MAR能够通过频率分集或签名分集进行区分;
处理单元620,用于对该至少一个冗余版本进行合并,得到上行信息。
可选地,作为一个实施例,该多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
本申请实施例提供的网络设备600,可以对应上述方法200中描述的网络设备。并且,网络设备600中各模块或单元分别用于执行上述方法200中由网络设备所执行的相应流程。为了简洁,此处不再赘述。
应理解,在本实施例中,网络设备600是以功能单元的形式来呈现。这里的“单元”可以指特定应用集成电路(application-specific integrated circuit,ASIC)、电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路,和/或其他可以提供上述功能 的器件。在一个简单的实施例中,本领域的技术人员可以想到网络设备600可以采用图1所示的形式。接收单元610和处理单元620实现的功能可以通过图1的处理器101和存储器102来实现。具体的,存储器存储有计算机程序,处理器通过调用并执行存储器中存储的计算机程序来执行上述方法实施例中由网络设备执行的相应流程。
在一种可能的实现方式中,网络设备可以包括处理器、收发器和存储器。处理器用于控制收发器收发信号,存储器用于存储计算机程序,处理器用于从存储器中调用并运行该计算机程序,使得该网络设备执行上述方法实施例中的相应操作和/或步骤。
另外,本申请还提供一种芯片系统(或者,芯片),该芯片系统包括处理器,用于实现上述方面方法实施例中网络设备所涉及的功能,例如,例如接收或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中,芯片系统还包括存储器,存储器用于存储网络设备必要的程序指令和数据。该芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件。
可以理解的是,该芯片系统可以安装在网络设备上,用于实现上述方法实施例中网络设备涉及的功能。例如,接收单元610可以为收发器,处理单元620可以为处理器。
本申请实施例的网络设备,通过接收终端设备使用频率分集或签名分集(或者,时间分集、频率分集和签名分集的任意组合)传输的承载有上行信息的冗余版本。在保证低时延的前提下,能够提高传输上行信息时的灵活性。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储 在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (32)

  1. 一种免授权的传输上行信息的方法,其特征在于,所述方法包括:
    终端设备从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括所述终端设备需要发送给网络设备的上行信息,所述多个目标MAR能够通过频率分集或签名分集进行区分;
    所述终端设备在所述多个目标MAR上向网络设备发送所述至少一个冗余版本。
  2. 根据权利要求1所述的方法,其特征在于,所述多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
  3. 根据权利要求1或2所述的方法,其特征在于,所述终端设备确定承载至少一个冗余版本的多个目标MAR,包括:
    所述终端设备根据捆绑信息,确定所述至少一个冗余版本对应的多个第一MAR,其中,所述捆绑信息是所述终端设备与所述网络设备预先约定的,所述捆绑信息中包括以下信息中的至少一个:发送所述上行信息时使用冗余版本的数量、发送所述上行信息时使用的冗余版本占用MAR的数量和大小、所述多个第一MAR的位置、发送所述上行信息时使用的冗余版本与所述多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS;
    所述终端设备从所述多个第一MAR中确定所述多个目标MAR。
  4. 根据权利要求1或2所述的方法,其特征在于,所述方法还包括:
    所述终端设备向所述网络设备发送第一控制信道,所述第一控制信道上承载有第一指示信息,所述第一指示信息用于指示所述多个目标MAR,以便于所述网络设备根据所述第一指示信息在所述多个目标MAR上接收所述至少一个冗余版本。
  5. 根据权利要求1或2所述的方法,其特征在于,所述多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,所述第二控制信道上承载有第二指示信息,所述第二指示信息用于指示所述标识信息和所述版本号,以便于所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息。
  6. 根据权利要求3所述的方法,其特征在于,所述方法还包括:
    所述终端设备向所述网络设备发送第三控制信道,所述第三控制信道上承载有第三指示信息,所述第三指示信息用于指示所述终端设备基于所述捆绑信息确定的所述多个目标MAR,以便于所述网络设备根据所述捆绑信息和所述第三指示信息,在所述多个第一MAR中的目标MAR上接收所述至少一个冗余版本。
  7. 根据权利要求1至6中任一项所述的方法,其特征在于,所述至少一个冗余版本的版本号相同时,所述多个目标MAR传输的上行数据相同。
  8. 一种免授权的传输上行信息的方法,其特征在于,所述方法包括:
    网络设备接收终端设备在多个目标多接入资源MAR上发送的至少一个冗余版本,所述多个目标MAR是所述终端设备从免授权资源中确定的,每个冗余版本至少包括所述终端设备需要发送给所述网络设备的上行信息,所述多个MAR能够通过频率分集或签名分 集进行区分;
    所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息。
  9. 根据权利要求8所述的方法,其特征在于,所述多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
  10. 根据权利要求8或9所述的方法,其特征在于,所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息,包括:
    所述网络设备根据捆绑信息,对所述至少一个冗余版本进行合并,得到所述上行信息,其中,所述捆绑信息是所述终端设备与所述网络设备预先约定的,所述捆绑信息中包括以下信息中的至少一个:
    发送所述上行信息时使用冗余版本的数量、发送所述上行信息时使用的冗余版本占用MAR的数量和大小、所述多个第一MAR的位置、发送所述上行信息时使用的冗余版本与所述多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS。
  11. 根据权利要求8或9所述的方法,其特征在于,所述方法还包括:
    所述网络设备接收所述终端设备发送的第一控制信道,所述第一控制信道承载有第一指示信息,所述第一指示信息用于指示所述多个目标MAR;
    以及,所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息,包括:
    所述网络设备根据所述第一指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  12. 根据权利要求8或9所述的方法,其特征在于,所述多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,所述第二控制信道上承载有第二指示信息,所述第二指示信息用于指示所述标识信息和所述版本号,
    以及,所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息,包括:
    所述网络设备根据所述第二指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  13. 根据权利要求10所述的方法,其特征在于,所述方法还包括:
    所述网络设备接收所述终端设备发送的第三控制信道,所述第三控制信道承载有第三指示信息,所述第三指示信息用于指示所述终端设备基于所述捆绑信息确定的所述多个目标MAR;
    以及,所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息,包括:
    所述网络设备根据所述第三指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  14. 根据权利要求7至13中任一项所述的方法,其特征在于,所述至少一个冗余版本的版本号相同,所述多个目标MAR传输的上行数据相同。
  15. 一种终端设备,其特征在于,包括:
    确定单元,用于从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括所述终端设备需要发送给网络设备的上行信息,所述多个目标MAR能够通过频率分集或签名分集进行区分;
    发送单元,用于在所述多个目标MAR上向网络设备发送所述至少一个冗余版本。
  16. 根据权利要求15所述的终端设备,其特征在于,所述多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
  17. 根据权利要求15或16所述的终端设备,其特征在于,所述确定单元具体用于:
    根据捆绑信息,确定所述至少一个冗余版本对应的多个第一MAR,其中,所述捆绑信息是所述终端设备与所述网络设备预先约定的,所述捆绑信息中包括以下信息中的至少一个:发送所述上行信息时使用冗余版本的数量、发送所述上行信息时使用的冗余版本占用MAR的数量和大小、所述多个第一MAR的位置、发送所述上行信息时使用的冗余版本与所述多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS;
    从所述多个第一MAR中确定所述多个目标MAR。
  18. 根据权利要求15或16所述的终端设备,其特征在于,所述发送单元还用于向所述网络设备发送第一控制信道,所述第一控制信道上承载有第一指示信息,所述第一指示信息用于指示所述多个目标MAR,以便于所述网络设备根据所述第一指示信息在所述多个目标MAR上接收所述至少一个冗余版本。
  19. 根据权利要求15或16所述的终端设备,其特征在于,所述多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,所述第二控制信道上承载有第二指示信息,所述第二指示信息用于指示所述标识信息和所述版本号,以便于所述网络设备对所述至少一个冗余版本进行合并,得到所述上行信息。
  20. 根据权利要求17所述的终端设备,其特征在于,所述发送单元还用于向所述网络设备发送第三控制信道,所述第三控制信道上承载有第三指示信息,所述第三指示信息用于指示所述终端设备基于所述捆绑信息确定的所述多个目标MAR,以便于所述网络设备根据所述捆绑信息和所述第三指示信息,在所述多个第一MAR中的目标MAR上接收所述至少一个冗余版本。
  21. 根据权利要求15至20中任一项所述的终端设备,其特征在于,所述至少一个冗余版本的版本号相同时,所述多个目标MAR上传输的上行数据相同。
  22. 一种网络设备,其特征在于,包括:
    接收单元,用于接收终端设备在多个目标多接入资源MAR上发送的至少一个冗余版本,所述多个目标MAR是所述终端设备从免授权资源中确定的,每个冗余版本至少包括所述终端设备需要发送给所述网络设备的上行信息,所述多个MAR能够通过频率分集或签名分集进行区分;
    处理单元,用于对所述至少一个冗余版本进行合并,得到所述上行信息。
  23. 根据权利要求22所述的网络设备,其特征在于,所述多个目标MAR能够通过频率分集、签名分集和时间分集的任意组合进行区分。
  24. 根据权利要求22或23所述的网络设备,其特征在于,所述处理单元具体用于根据捆绑信息,对所述至少一个冗余版本进行合并,得到所述上行信息,其中,所述捆绑信息是所述终端设备与所述网络设备预先约定的,所述捆绑信息中包括以下信息中的至少一个:发送所述上行信息时使用冗余版本的数量、发送所述上行信息时使用的冗余版本占用 MAR的数量和大小、所述多个第一MAR的位置、发送所述上行信息时使用的冗余版本与所述多个第一MAR的映射关系、每个第一MAR上承载冗余版本的数量和每个第一MAR能够使用的调制与编码策略MCS。
  25. 根据权利要求22或23所述的网络设备,其特征在于,所述接收单元具体用于接收所述终端设备发送的第一控制信道,所述第一控制信道承载有第一指示信息,所述第一指示信息用于指示所述多个目标MAR;
    以及,所述处理单元具体用于根据所述第一指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  26. 根据权利要求22或23所述的网络设备,其特征在于,所述多个目标MAR中的每个目标MAR携带终端设备的标识信息和所承载的冗余版本的版本号,每个目标MAR携带有第二控制信道,所述第二控制信道上承载有第二指示信息,所述第二指示信息用于指示所述标识信息和所述版本号,
    以及,所述处理单元具体用于根据所述第二指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  27. 根据权利要求24所述的网络设备,其特征在于,所述接收单元具体用于接收所述终端设备发送的第三控制信道,所述第三控制信道承载有第三指示信息,所述第三指示信息用于指示所述终端设备基于所述捆绑信息确定的所述多个目标MAR;
    以及,所述处理单元具体用于根据所述第三指示信息,对所述至少一个冗余版本进行合并,得到所述上行信息。
  28. 根据权利要求22至27中任一项所述的网络设备,其特征在于,所述至少一个冗余版本的版本号相同,所述多个目标MAR上传输的上行数据相同。
  29. 一种芯片系统,其特征在于,包括:
    处理器,用于从免授权资源中确定承载至少一个冗余版本的多个目标多接入资源MAR,每个冗余版本至少包括所述终端设备需要发送给网络设备的上行信息,所述多个目标MAR能够通过频率分集或签名分集进行区分;
    收发器,用于在所述多个目标MAR上向网络设备发送所述至少一个冗余版本。
  30. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机程序,所述计算机程序在计算机上执行时,使得计算机执行权利要求1至7中任一项所述的方法。
  31. 一种芯片系统,其特征在于,包括:
    收发器,用于接收终端设备在多个目标多接入资源MAR上发送的至少一个冗余版本,所述多个目标MAR是所述终端设备从免授权资源中确定的,每个冗余版本至少包括所述终端设备需要发送给所述网络设备的上行信息,所述多个MAR能够通过频率分集或签名分集进行区分;
    处理器,用于对所述至少一个冗余版本进行合并,得到所述上行信息。
  32. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质存储有计算机程序,所述计算机程序在计算机上执行时,使得计算机执行权利要求8至14中任一项所述的方法。
PCT/CN2017/099485 2016-09-30 2017-08-29 免授权的传输上行信息的方法、网络设备和终端设备 WO2018059173A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610870865.2 2016-09-30
CN201610870865.2A CN107889231B (zh) 2016-09-30 2016-09-30 免授权的传输上行信息的方法、网络设备和终端设备

Publications (1)

Publication Number Publication Date
WO2018059173A1 true WO2018059173A1 (zh) 2018-04-05

Family

ID=61763301

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/099485 WO2018059173A1 (zh) 2016-09-30 2017-08-29 免授权的传输上行信息的方法、网络设备和终端设备

Country Status (2)

Country Link
CN (1) CN107889231B (zh)
WO (1) WO2018059173A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505699A (zh) * 2018-05-20 2019-11-26 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
WO2021022284A1 (en) * 2019-07-26 2021-02-04 Qualcomm Incorporated Redundancy version identification in cross-carrier repetition
US10931349B2 (en) 2018-05-21 2021-02-23 Industrial Technology Research Institute User equipment and method for grant-free uplink transmission
CN112398574A (zh) * 2019-08-16 2021-02-23 大唐移动通信设备有限公司 一种传输调度的方法和设备
CN113242577A (zh) * 2018-12-20 2021-08-10 Oppo广东移动通信有限公司 一种资源调度方法、终端设备及网络设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108289331B (zh) 2017-01-09 2021-11-19 华为技术有限公司 一种上行传输方法、终端、网络侧设备
CN110381582B (zh) * 2018-04-12 2021-12-10 维沃移动通信有限公司 一种信号传输方法、相关设备及系统
WO2020063378A1 (zh) * 2018-09-28 2020-04-02 电信科学技术研究院有限公司 数据传输方法和设备
CN110971378B (zh) * 2018-09-28 2021-12-03 大唐移动通信设备有限公司 数据传输方法和设备
CN111130725B (zh) * 2018-10-31 2022-07-15 中国移动通信有限公司研究院 基于预调度的传输配置方法、参数确定方法及设备
CN113228772B (zh) * 2018-11-16 2024-06-21 上海诺基亚贝尔股份有限公司 数据传输控制
EP3869717A4 (en) * 2018-11-28 2021-10-27 Huawei Technologies Co., Ltd. COMMUNICATION PROCESS AND APPARATUS
CN110856262B (zh) * 2019-09-25 2022-03-01 西安交通大学 一种基于联合时频分集的免授权上行传输方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005655A (zh) * 2006-01-19 2007-07-25 华为技术有限公司 一种支持hsupa的软切换性能评估方法和移动终端
WO2015077964A1 (en) * 2013-11-28 2015-06-04 Telefonaktiebolaget L M Ericsson (Publ) Methods, apparatuses and user equipment for hybrid automatic repeat request transmission

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104901786B (zh) * 2015-05-21 2018-08-28 北京思朗科技有限责任公司 基于lte系统的harq软合并方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101005655A (zh) * 2006-01-19 2007-07-25 华为技术有限公司 一种支持hsupa的软切换性能评估方法和移动终端
WO2015077964A1 (en) * 2013-11-28 2015-06-04 Telefonaktiebolaget L M Ericsson (Publ) Methods, apparatuses and user equipment for hybrid automatic repeat request transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on grant-free transmission", 3GPP TSG RAN WG1 MEETING #86, R1-166095, 22 August 2016 (2016-08-22) - 26 August 2016 (2016-08-26), XP051125210 *
LG ELECTRONICS , HUAWEI HISILICON ETRI [MEDIATEK]: "WF on further clarification on grant-free transmission for mMTC.", 3GPP TSG RAN WG1 MEETING #86, RL-168538, 26 August 2016 (2016-08-26), XP051144433 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110505699A (zh) * 2018-05-20 2019-11-26 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
CN110505699B (zh) * 2018-05-20 2023-04-18 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
US10931349B2 (en) 2018-05-21 2021-02-23 Industrial Technology Research Institute User equipment and method for grant-free uplink transmission
CN113242577A (zh) * 2018-12-20 2021-08-10 Oppo广东移动通信有限公司 一种资源调度方法、终端设备及网络设备
WO2021022284A1 (en) * 2019-07-26 2021-02-04 Qualcomm Incorporated Redundancy version identification in cross-carrier repetition
US11632198B2 (en) 2019-07-26 2023-04-18 Qualcomm Incorporated Redundancy version identification in cross-carrier repetition
CN112398574A (zh) * 2019-08-16 2021-02-23 大唐移动通信设备有限公司 一种传输调度的方法和设备
CN112398574B (zh) * 2019-08-16 2022-04-29 大唐移动通信设备有限公司 一种传输调度的方法和设备

Also Published As

Publication number Publication date
CN107889231A (zh) 2018-04-06
CN107889231B (zh) 2021-03-23

Similar Documents

Publication Publication Date Title
WO2018059173A1 (zh) 免授权的传输上行信息的方法、网络设备和终端设备
WO2019233339A1 (zh) 传输信息的方法和通信设备
JP2020506594A (ja) 上りリンク・チャネル電力割り当て方法および装置
WO2014000514A1 (zh) 设备间通信方法、用户设备和基站
JP2022551321A (ja) 通信方法及び装置
EP3595220B1 (en) Method and apparatus for sending and receiving feedback information
JP2024073619A (ja) 端末、通信方法及び集積回路
US11705992B2 (en) Infrastructure equipment, wireless telecommunications system and method
WO2019007182A1 (zh) 一种数据传输方法及装置
TWI702871B (zh) 用於行動通訊系統之使用者裝置及基地台
US20220225316A1 (en) Sidelink control information sending and receiving method, terminal apparatus, and system
JP7303378B2 (ja) 物理サイドリンクフィードバックチャネルリソースを決定するための方法及び装置
CN118199831A (zh) 资源指示方法、装置和终端
WO2021062638A1 (zh) 发送、接收反馈信息的方法和设备
JP2024109710A (ja) 端末装置、通信方法及び集積回路
US20220140957A1 (en) HARQ Feedback Technique for Communication Systems
US20210105745A1 (en) Data transmission method, network device and terminal device
JP7352647B2 (ja) リソース割り当て方法ならびにデバイス、記憶媒体および端末
JP2023520688A (ja) サイドリンク伝送方法及び装置
WO2023011218A1 (zh) 一种资源共享方法及通信装置
JP7339439B2 (ja) 通信方法及び装置
CN113285789B (zh) 辅链路控制信息的资源指示方法与装置、终端设备
JP2020519178A (ja) データが破損しているかどうかを判断するための方法および装置
WO2021035541A1 (zh) 一种数据传输方法及相关设备
WO2020156002A1 (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: 17854625

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

Country of ref document: EP

Kind code of ref document: A1