WO2020001579A1 - 控制信息传输方法、网络设备、终端和计算机存储介质 - Google Patents

控制信息传输方法、网络设备、终端和计算机存储介质 Download PDF

Info

Publication number
WO2020001579A1
WO2020001579A1 PCT/CN2019/093504 CN2019093504W WO2020001579A1 WO 2020001579 A1 WO2020001579 A1 WO 2020001579A1 CN 2019093504 W CN2019093504 W CN 2019093504W WO 2020001579 A1 WO2020001579 A1 WO 2020001579A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnti
control information
harq
information
terminal
Prior art date
Application number
PCT/CN2019/093504
Other languages
English (en)
French (fr)
Inventor
沈嘉
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201980011118.5A priority Critical patent/CN111670599B/zh
Publication of WO2020001579A1 publication Critical patent/WO2020001579A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • This application relates to information processing technology, and in particular, to a control information transmission method, a network device, a terminal, and a computer storage medium.
  • the current 5G New Radio (NR) system introduces ultra-reliable ultra-low latency communication (URLLC), which is characterized by extreme latency (for example, 1ms) Achieve ultra-high reliability (e.g., 99.999%) transmission.
  • URLLC ultra-reliable ultra-low latency communication
  • eMBB Enhanced Mobile Bandwidth
  • the current system cannot independently optimize transmission according to different services, resulting in low transmission efficiency of the system, or delay requirements for transmission reliability that cannot meet business requirements.
  • the embodiments of the present application provide a control information transmission method, a network device, a terminal, and a computer storage medium.
  • an embodiment of the present application provides a control information transmission method, where the method includes:
  • the terminal receives control information for data scheduling
  • the terminal parses the control information based on a radio network temporary identifier (RNTI); the RNTI is a first RNTI or a first RNTI for scrambling a redundant check bit of the control information. Two RNTI.
  • RNTI radio network temporary identifier
  • an embodiment of the present application further provides a control information transmission method, where the method includes:
  • the network device determines control information used for data scheduling and an RNTI used for scrambling the redundant check bit of the control information; the control information is related to the RNTI; the RNTI includes a first RNTI or a second RNTI;
  • an embodiment of the present application further provides a terminal, where the terminal includes: a receiving unit and a parsing unit;
  • the receiving unit is configured to receive control information for data scheduling
  • the analysis unit is configured to analyze the control information based on an RNTI; the RNTI is a first RNTI or a second RNTI for scrambling a redundancy check bit of the control information.
  • an embodiment of the present application further provides a network device, where the network device includes: a determining unit and a sending unit; wherein,
  • the determining unit is configured to determine control information used for data scheduling and an RNTI used for scrambling the redundancy check bit of the control information; the control information is related to the RNTI; and the RNTI includes a first RNTI or Second RNTI;
  • the sending unit is configured to send the control information.
  • an embodiment of the present application further provides a computer-readable storage medium having computer instructions stored thereon.
  • the instructions When the instructions are executed by a processor, the instructions are applied to the first aspect or the second aspect described in the embodiments of the present application. Aspects of method steps.
  • an embodiment of the present application further provides a terminal, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor implements the embodiment of the application when the processor executes the program. The steps applied to the method of the first aspect described above.
  • an embodiment of the present application further provides a network device, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • the processor implements the implementation of the application when the processor executes the program. The steps described in the example apply to the method of the second aspect described above.
  • an embodiment of the present application further provides a chip, including: a processor, configured to call and run a computer program from a memory, so that a device installed with the chip executes the foregoing first aspect or the second aspect.
  • an embodiment of the present application further provides a computer program product, including computer program instructions, which causes the computer to execute the method described in the first aspect or the second aspect above.
  • an embodiment of the present application further provides a computer program, where the computer program causes a computer to execute the method described in the first aspect or the second aspect.
  • the network device determines the control information used for data scheduling and the RNTI used for scrambling the redundancy check bit of the control information, and sends the Control information; the control information is related to the RNTI; the RNTI includes a first RNTI or a second RNTI; the terminal receives control information for data scheduling; and analyzes the control information based on the RNTI, the RNTI is used for A first RNTI or a second RNTI that scrambles a redundancy check bit of the control information.
  • different RNTIs are determined based on different data scheduling by the network device, the RNTI related to the data scheduling is determined, and the control information related to the RNTI is determined, thereby realizing the data scheduling correspondence between the terminal and the network device
  • the control information is transmitted by data, thereby realizing independent and optimized transmission according to the data of different services, greatly improving the transmission efficiency, and meeting the requirements of data transmission reliability and delay of different services.
  • FIG. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
  • FIG. 2 is a first schematic flowchart of a control information transmission method according to an embodiment of the present application
  • FIG. 3 is a second schematic flowchart of a control information transmission method according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of an interaction process of a control information transmission method according to an embodiment of the present application
  • FIG. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a chip according to an embodiment of the present application.
  • GSM Global System
  • CDMA Code Division Multiple Access
  • Wideband Code Division Multiple Access Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with the terminal device 120 (or referred to as a communication terminal or terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • the network device may be a mobile switching center, relay station, access point, vehicle equipment, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in public land mobile networks (PLMN) that will evolve in the future.
  • PLMN public land mobile networks
  • the communication system 100 further includes at least one terminal device 120 located within a coverage area of the network device 110.
  • terminal equipment used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) devices.
  • PSTN Public Switched Telephone Networks
  • DSL Digital Subscriber Line
  • WLAN Wireless Local Area Networks
  • DVB-H Digital Video Broadband
  • satellite networks satellite networks
  • AM- FM broadcast transmitter AM- FM broadcast transmitter
  • IoT Internet of Things
  • a terminal device configured to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellite or cellular phones; personal communications systems (PCS) terminals that can combine cellular radiotelephones with data processing, facsimile, and data communications capabilities; can include radiotelephones, pagers, Internet PDA with network access, Web browser, notepad, calendar, and / or Global Positioning System (GPS) receiver; and conventional laptop and / or palm-type receivers or others including radiotelephone transceivers Electronic device.
  • PCS personal communications systems
  • GPS Global Positioning System
  • a terminal device can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or User device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing Assistant (PDA), and wireless communication.
  • the 5G system or 5G network may also be referred to as an NR system or an NR network.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. The embodiment does not limit this.
  • the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.
  • network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.
  • the device having a communication function in the network / system in the embodiments of the present application may be referred to as a communication device.
  • the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be specific devices described above, and will not be repeated here.
  • the communication device may also include other devices in the communication system 100, such as other network entities such as a network controller, a mobile management entity, and the like, which is not limited in the embodiments of the present application.
  • the terminal devices 120 in this example are all the terminals described in the embodiments of the present application.
  • FIG. 2 is a schematic flowchart of a control information transmission method according to an embodiment of the present application; as shown in FIG. 2, the method includes:
  • Step 101 The terminal receives control information for data scheduling.
  • Step 102 The terminal parses the control information based on an RNTI, and the RNTI is a first RNTI or a second RNTI for scrambling a redundant check bit of the control information.
  • the terminal receives a signal carrying control information and a scrambled redundancy check bit, and obtains control information for data scheduling based on the signal; as another implementation, In a manner, the terminal receives control information carrying a scrambled redundancy check bit.
  • the number of the redundancy check bits corresponding to the control information may be at least one.
  • the RNTI used to parse the control information may obtain a redundancy check bit by descrambling the control information or descrambling the scrambled redundancy check bit based on the first RNTI and / or the second RNTI. A check determination is performed, and the first RNTI or the second RNTI corresponding to the redundant check bit that passed the check is used to analyze the control information.
  • the control information is related to the RNTI; different data schedules correspond to different RNTIs, and thus correspond to different control information. It can be understood that the control information includes multiple types of information. For the configuration information, the first RNTI and the second RNTI respectively correspond to different information, and the different information includes the number of information and / or the content of the information.
  • the first RNTI and the second RNTI are both used for terminal-specific data scheduling. Then, the terminal obtains a cyclic redundancy check (CRC, Cyclic Redundancy Check) code based on the first RNTI or the second RNTI descrambling control information, checks the CRC code, and determines the first RNTI or the second RNTI that passes the check.
  • CRC Cyclic Redundancy Check
  • the first RNTI and the second RNTI are any two RNTIs in the RNTI data set; the RNTI data set includes at least two RNTIs. It can be understood that there are at least two RNTIs related to control information used for data scheduling, and different data scheduling corresponds to different RNTIs and corresponding to different control information.
  • the first RNTI is a Cell-Radio Network Temporary Identifier (C-RNTI).
  • C-RNTI Cell-Radio Network Temporary Identifier
  • control information includes at least one of the following information: Downlink Control Information Format (DCI), Redundancy Version, Hybrid Automatic Repeat Request Processes (Hybrid Automatic Repeat (request, process number, HARQ, process number), channel status information request (Channel status indicator, request (CSI) request), physical downlink shared channel and HARQ corresponding timing relationship (PDSCH-to-HARQ), physical uplink control channel resources Indication (PUCCH Resource Indicator), offset parameter (Betaoffset).
  • DCI Downlink Control Information Format
  • Redundancy Version Hybrid Automatic Repeat Request Processes
  • Hybrid Automatic Repeat request, process number, HARQ, process number
  • channel status information request Channel status indicator, request (CSI) request
  • PDSCH-to-HARQ physical downlink shared channel and HARQ corresponding timing relationship
  • PUCCH Resource Indicator physical uplink control channel resources Indication
  • Betaoffset offset parameter
  • control information includes at least one of Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, and Betaoffset, respectively
  • the control information corresponds to the first RNTI and the second
  • the same type of information in the RNTI contains different amounts of information and / or different content of the information.
  • the control information corresponding to the first RNTI and the second RNTI may include Redundancy Version and HARQ Process Number; then the Redundancy Version in the control information corresponding to the first RNTI may include 0, 2, 3, and 1 Versions, the number corresponding to the information contained is four.
  • the RedundancyVersion in the control information corresponding to the second RNTI may include two versions ⁇ 0, 3 ⁇ or ⁇ 0, 2 ⁇ , then the number of corresponding information is 2; therefore, the amount and content of the included information are different .
  • the HARQ ProcessNumber in the control information corresponding to the first RNTI may include 16 processes, and the HARQ ProcessNumber in the control information corresponding to the second RNTI may include 4 processes, so the amount and content of the included information are different.
  • control information includes the DCI Format
  • the effective lengths of the DCI Formats corresponding to the first RNTI and the second RNTI are different, or the domain information contained in the DCI Format is different.
  • the network equipment determines the RNTI related to the control information and then the control information used for data scheduling, that is, different data schedules determine different RNTIs, and data-based scheduling between the terminal and the network equipment is realized
  • the corresponding control information is transmitted by data, thereby realizing independent and optimized transmission of data according to different service types, greatly improving the transmission efficiency, and meeting the requirements for the reliability and delay of data transmission of different service types.
  • FIG. 3 is a second schematic flowchart of a control information transmission method according to an embodiment of the present application; as shown in FIG. 3, the method includes:
  • Step 201 The network device determines control information used for data scheduling and an RNTI used for scrambling the redundancy check bit of the control information; the control information is related to the RNTI; and the RNTI includes a first RNTI or a second RNTI.
  • Step 202 The network device sends the control information.
  • the network device may determine different RNTIs based on different data scheduling, and then determine control information related to the RNTI.
  • the network device may determine the RNTI based on the service type, and then determine the information included in the control information, and further determine the amount and / or content of the information included in the control information.
  • the control information includes multiple types of information.
  • the first RNTI and the second RNTI correspond to different information, and the different information includes the number of information and / or the content of the information.
  • the first RNTI and the second RNTI are any two RNTIs in the RNTI data set; the RNTI data set includes at least two RNTIs. It can be understood that there are at least two RNTIs related to control information used for data scheduling, and different data scheduling corresponds to different RNTIs and corresponding to different control information.
  • the network device can select the corresponding RNTI based on the current data scheduling, and then determine the corresponding control information.
  • the network device determines the control information, and determines a redundancy check bit corresponding to the control information.
  • the redundancy check bit can be specifically represented by a CRC.
  • the network device scrambles the CRC based on the determined RNTI, and adds the control information and the The scrambled redundancy check bits are channel coded and modulated, and mapped to time-frequency resources and sent.
  • the network device sends the control information and the scrambled redundancy check bit through a signal; as another implementation manner, the network device sends the control information, and the control information carries the scrambled information. Redundancy check digits.
  • control information includes at least one of the following information: DCI Format, Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, Betaoffset.
  • the control information includes at least one of Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, and Betaoffset
  • the control information corresponds to the first RNTI, respectively.
  • the number of information contained in the same type of information as the second RNTI is different and / or the content of the information is different.
  • the control information corresponding to the first RNTI and the second RNTI may include Redundancy Version and HARQ Process Number; then the Redundancy Version in the control information corresponding to the first RNTI may include 0, 2, 3, and 1 Versions, the number corresponding to the information contained is four.
  • the RedundancyVersion in the control information corresponding to the second RNTI may include two versions ⁇ 0,3 ⁇ or ⁇ 0,2 ⁇ , then the number of corresponding information is 2; therefore, the amount and content of the included information are different .
  • the HARQ ProcessNumber in the control information corresponding to the first RNTI may include 16 processes, and the HARQ ProcessNumber in the control information corresponding to the second RNTI may include 4 processes, so the amount and content of the included information are different.
  • control information includes the DCI Format
  • the effective lengths of the DCI Formats corresponding to the first RNTI and the second RNTI are different, or the domain information contained in the DCI Format is different.
  • the network equipment determines the RNTI related to the control information and then the control information used for data scheduling, that is, different data schedules determine different RNTIs, and data-based scheduling between the terminal and the network equipment is realized
  • the corresponding control information is transmitted by data, thereby realizing independent and optimized transmission of data according to different service types, greatly improving the transmission efficiency, and meeting the requirements for the reliability and delay of data transmission of different service types.
  • FIG. 4 is a schematic diagram of an interaction flow of a control information transmission method according to an embodiment of the present application; as shown in FIG. 4, the method includes:
  • Step 301 The network device determines control information used for data scheduling and an RNTI used for scrambling the redundancy check bits of the control information.
  • Step 302 The network device sends the control information.
  • Step 303 The terminal parses the control information based on an RNTI, where the RNTI is a first RNTI or a second RNTI for scrambling a redundancy check bit of the control information.
  • the control information includes various pieces of information in detail below.
  • the length may be 2 bits, and its four values correspond to four versions of 0, 2, 3, and 1 in the redundant version.
  • the length can be 1 bit, and its two values correspond to the two versions ⁇ 0, 3 ⁇ or ⁇ 0, 2 ⁇ in the redundant version. That is, the number of pieces of information corresponding to the Redundancy Version of the first RNTI and the second RNTI are different, and the content of the information is also different.
  • ⁇ 0, 3 ⁇ can obtain sufficient coding diversity gain. Therefore, configuring ⁇ 0,3 ⁇ for dynamic selection can not only satisfy sufficient incremental redundancy (IR, Incremental Redundancy) merger gains, but also reduce control signaling overhead.
  • IR Incremental Redundancy
  • For URLLC services reduce control signaling overhead, and Conducive to the reliability of control signaling. Therefore, for URLLC services, scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • the HARQ ProcessNumber in the control information scrambled based on the first RNTI can be 4 bits in length, and its 16 values correspond to 0-15 HARQ processes or 1-16 HARQ processes.
  • the length can be 2 bits, and its four values correspond to 0-3 HARQ processes or 1-4 HARQ processes.
  • the HARQ entity and / or HARQ buffer corresponding to the HARQ ProcessNumber in the control information scrambled based on the first RNTI and the HARQ entity and / or HARQ corresponding to the HARQ ProcessNumber in the control information scrambled based on the second RNTI The caches are independent of each other, even if the HARQ ProcessNumber is the same.
  • the HARQ entity and / or the HARQ cache corresponding to the HARQ ProcessNumber in the control information scrambled based on the first RNTI and the HARQ corresponding to the HARQ ProcessNumber in the control information scrambled based on the second RNTI The entities and / or HARQ caches are independent of each other, even if the HARQ ProcessNumber is the same.
  • the numbers of information corresponding to the HARQ Process Number of the first RNTI and the second RNTI are different, and the content of the information is also different.
  • the length of the CSI request in the scrambled control information based on the first RNTI can be 4 bits, and its 16 values correspond to 16 CSI reports.
  • at least one of the 16 CSI reports includes longer PUSCH symbols, or is based on a variety of non-zero power (NZP) -CSI / zero power (ZP) -CSI as measurement resources to support various signals and interference situations.
  • NZP non-zero power
  • ZP zero power
  • the length of the CSI Request in the control information scrambled based on the second RNTI can be 1 bit, and its two values correspond to two CSI reports.
  • At least one of the two CSI reports is based on a demodulation reference signal (Demodulation Reference Signal, DMRS) as a measurement resource and / or a time-domain measurement window that is the same as downlink data to reduce signaling overhead and improve downlink control Reliability. That is, the number of CSI requests corresponding to the first RNTI and the second RNTI is different, and the content of the information is also different.
  • DMRS Demodulation Reference Signal
  • scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • the PDSCH-to-HARQ in the control information scrambled based on the first RNTI may have a length of 3 bits, and its eight values correspond to ⁇ 3, 4, 5, 6, 8, 12, 16, 20 ⁇ .
  • the length of the PDSCH-to-HARQ in the control information scrambled based on the second RNTI can be 1 bit, and its two values correspond to ⁇ 0, 1 ⁇ . That is, the number of PDSCH-to-HARQ information corresponding to the first RNTI and the second RNTI is different, and the content of the information is also different.
  • PDSCH-to-HARQ for transmissions with severe delay requirements, PDSCH-to-HARQ feedback needs to be implemented as soon as possible, otherwise HARQ feedback has no meaning and no feedback is needed. Therefore, PDSCH-to-HARQ can choose fewer timings and use fewer bits.
  • the second RNTI scrambled control information corresponds to PDSCH-to-HARQ.
  • the first RNTI scrambled control information corresponds to PDSCH-to-HARQ.
  • fewer PDSCH-to-HARQ bits are helpful to improve the reliability of control information transmission.
  • scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • the PUCCH Resource Indicator in the control information scrambled based on the first RNTI may have a length of 3 bits, and its eight values correspond to those shown in Table 1.
  • Table 1 contains different lengths / PUCCH formats, different numbers of symbols (Number of symbols), different physical resource block (PRB, Physical Resource Block) offset values (offsets), and different initial CS index sets (Initial CS index indexes). Meet latency reliability requirements and pair transmission with other users to improve system transmission efficiency.
  • the length may be 3 bits, and its eight values correspond to Table 2.
  • Table 2 contains different starting symbols (Starting Symbols) to improve the flexibility of the time domain resources of the control channel and meet the requirements of low latency.
  • scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • the ⁇ Beta_offset for HARQ-ACK, Beta_offset for CSI ⁇ set corresponding to Beta_offset in the control information scrambled by the first RNTI can be 2 bits in length, and its four values correspond to ⁇ Beta_offset for HARQ-ACK, Beta_offset for CSI ⁇ set.
  • Table 3 contains values where Beta_offset is greater than 1.
  • the length can be 2 bits, and its four values correspond to ⁇ Beta_offset for HARQ-ACK Beta_offset for CSI ⁇ collection.
  • Table 4 contains values with Beta_offset less than 1.
  • scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • the second RNTI scrambling control information shown above is used to reduce the bits; the reduced bits can be used to indicate other information, such as the carrier indicator (Carrier Indicator), CSI request , Bandwidth Part (BWP) Indicator, or used to extend some existing domains, such as Time Domain Resource Assignment, PUCCH Resource Indicator, Downlink Assignment Index (DAI), etc. Increase transmission flexibility.
  • Carrier Indicator Carrier Indicator
  • BWP Bandwidth Part
  • DAI Downlink Assignment Index
  • the domain value included in the control information scrambled based on the first RNTI is shown in the Fallback DCI column shown in Table 5 or Table 6.
  • the domain value included in the control information scrambled based on the second RNTI As shown in Table 5 or Table 6 New DCI column.
  • New DCI reduces some domains because it is not necessary for the transmission of specific services, or it cannot significantly improve the transmission efficiency. But some additional domains are added, such as Carrier Indicator, CSI request, BWP Indicator, or some domains are extended, such as Time Domain Resource Assignment, PUCCH Resource Indicator, DAI, etc. to improve transmission flexibility, reduce transmission delay, and improve transmission efficiency. Therefore, for URLLC services, scrambling control information may be based on the second RNTI; for eMBB, scrambling control information may be based on the first RNTI.
  • FIG. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application. As shown in FIG. 5, the terminal includes: a receiving unit 31 and a parsing unit 32;
  • the receiving unit 31 is configured to receive control information for data scheduling
  • the analysis unit 32 is configured to analyze the control information received by the receiving unit 31 based on an RNTI, and the RNTI is a first RNTI or a first RNTI for scrambling a redundancy check bit of the control information. Second RNTI.
  • control information includes at least one of the following information: DCI Format, Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, Betaoffset.
  • control information when the control information includes at least one of Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, and Betaoffset, the control information
  • the pieces of information corresponding to the same type of information corresponding to the first RNTI and the second RNTI, respectively, have different numbers of information and / or different contents of the information.
  • the effective lengths of the DCI Format corresponding to the first RNTI and the second RNTI are different, or the domain information included in the DCI Format different.
  • both the first RNTI and the second RNTI are used for terminal-specific data scheduling.
  • the first RNTI is a C-RNTI.
  • the terminal provided in the foregoing embodiment performs control information transmission
  • only the above-mentioned division of the program modules is used as an example.
  • the above processing may be allocated by different program modules according to needs.
  • the internal structure of the terminal is divided into different program modules to complete all or part of the processing described above.
  • the terminal and the control information transmission method embodiments provided in the foregoing embodiments belong to the same concept. For specific implementation processes, refer to the method embodiments, and details are not described herein again.
  • the parsing unit 32 in the terminal may be implemented by a central processing unit (CPU), a digital signal processor (DSP), and a micro control in the terminal in practical applications.
  • Unit Microcontroller Unit, MCU
  • Programmable Gate Array Field-Programmable Gate Array, FPGA
  • the receiving unit 31 in the terminal can be used in the actual application through the communication module (including: basic communication suite, operating system , Communication modules, standardized interfaces and protocols, etc.) and transceiver antennas.
  • FIG. 6 is a schematic structural diagram of a network device according to an embodiment of the present application; as shown in FIG. 6, the network device includes: a determining unit 41 and a sending unit 42;
  • the determining unit 41 is configured to determine control information used for data scheduling and an RNTI used for scrambling the redundancy check bit of the control information; the control information is related to the RNTI; and the RNTI includes a first RNTI Or the second RNTI;
  • the sending unit 42 is configured to send the control information.
  • control information includes at least one of the following information: DCI Format, Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, Betaoffset.
  • the control information includes at least one of Redundancy Version, HARQ Process Number, CSI request, PDSCH-to-HARQ, PUCCH Resource Indicator, and Betaoffset
  • the control information corresponds to the first RNTI, respectively.
  • the number of information contained in the same type of information as the second RNTI is different and / or the content of the information is different.
  • control information includes the DCI Format
  • the effective lengths of the DCI Formats corresponding to the first RNTI and the second RNTI are different, or the domain information contained in the DCI Format is different.
  • both the first RNTI and the second RNTI are used for terminal-specific data scheduling.
  • the first RNTI is a C-RNTI.
  • the network device provided in the foregoing embodiment performs control information transmission
  • only the above-mentioned division of the program modules is used as an example.
  • the above processing may be allocated by different program modules according to requirements. That is, the internal structure of the network device is divided into different program modules to complete all or part of the processing described above.
  • the network device and the control information transmission method embodiments provided in the foregoing embodiments belong to the same concept. For specific implementation processes, refer to the method embodiments, and details are not described herein again.
  • the determining unit 41 in the network device may be implemented by a CPU, a DSP, an MCU, or an FPGA in the final network device in actual applications; the sending unit 42 in the network device may be Applications can be implemented through communication modules (including: basic communication suite, operating system, communication module, standardized interfaces and protocols, etc.) and transceiver antennas.
  • communication modules including: basic communication suite, operating system, communication module, standardized interfaces and protocols, etc.
  • FIG. 7 is a schematic block diagram of a communication device provided by an embodiment of the present application. As shown in FIG. The computer program is called and run to implement the method in the embodiment of the present application.
  • the communication device is a terminal, and when the processor executes the program, the processor implements: receiving control information for data scheduling; analyzing the control information based on an RNTI, and the RNTI is used for The first RNTI or the second RNTI that is scrambled by the redundant check bits of the control information.
  • the communication device is a network device, and when the processor executes the program, the processor implements: determining control information for data scheduling and an RNTI used for scrambling the redundant check bit of the control information; the The control information is related to the RNTI; the RNTI includes a first RNTI or a second RNTI; and the control information is sent.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may send information or data to other devices, or receive other devices Information or data sent.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include antennas, and the number of antennas may be one or more.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchronous DRAM Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM Enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory Synchrobus RAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (SDRAM), double data rate Synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM), direct memory bus random access memory (Direct RAMbus RAM, DR RAM) and so on. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.
  • the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability.
  • each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • a software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • an embodiment of the present application further provides a computer-readable storage medium, such as a memory including a computer program, and the computer program may be executed by a terminal or a processor of a network device to complete the steps in the foregoing method.
  • the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disk, or CD-ROM.
  • An embodiment of the present application further provides a computer-readable storage medium having computer instructions stored thereon, which are executed by a processor to implement: receiving control information for data scheduling; and analyzing the control information based on RNTI,
  • the RNTI is a first RNTI or a second RNTI for scrambling a redundant check bit of the control information; or, when the instruction is executed by a processor, the RNTI is implemented to determine control information and data for data scheduling.
  • the RNTI used for scrambling the redundancy check bit of the control information; the control information is related to the RNTI; the RNTI includes a first RNTI or a second RNTI; and the control information is transmitted.
  • FIG. 8 is a schematic block diagram of a chip provided in an embodiment of the present application.
  • the chip includes: a processor 710 configured to be called from the memory 720. And run a computer program, so that the device installed with the chip executes the method applied to a terminal according to the embodiment of the present application; or executes the method applied to a network device according to the embodiment of the present application.
  • the chip may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip may further include an input interface 730.
  • the processor 710 may control the input interface 730 to communicate with other devices or chips. Specifically, the processor 710 may obtain information or data sent by other devices or chips.
  • the chip may further include an output interface 740.
  • the processor 710 may control the output interface 740 to communicate with other devices or chips. Specifically, the processor 710 may output information or data to the other devices or chips.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal / terminal device in each method of the embodiment of the present application. For simplicity, here No longer.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system or a system-on-chip.
  • An embodiment of the present application further provides a computer program product, including computer program instructions, which causes a computer to execute the method applied to a terminal described in the embodiments of the present application; or the computer program instructions cause the computer to execute the implementation of the present application.
  • the method according to any one of the examples is applied to a network device.
  • An embodiment of the present application further provides a computer program that causes a computer to execute the method applied to a terminal according to the embodiment of the present application; or the computer program causes the computer to execute the application described in the embodiment of the present application.
  • a computer program that causes a computer to execute the method applied to a terminal according to the embodiment of the present application; or the computer program causes the computer to execute the application described in the embodiment of the present application.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • 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 on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the foregoing storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory) ROM, random access memory (Random Access Memory, RAM), magnetic disks or optical disks and other media that can store program codes .

Landscapes

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

Abstract

本申请实施例公开了一种控制信息传输方法、网络设备、终端和计算机存储介质。所述方法包括：终端接收用于数据调度的控制信息；所述终端基于用于无线网络临时标识(RNTI)解析所述控制信息；所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。

Description

控制信息传输方法、网络设备、终端和计算机存储介质 技术领域
本申请涉及信息处理技术，具体涉及一种控制信息传输方法、网络设备、终端和计算机存储介质。
背景技术
目前的5G的新无线(New Radio，NR)系统引入了超高可靠超低时延通信(Ultra-Reliable Low Latency Communication，URLLC),该业务的特征是在极端的时延内(例如，1ms)实现超高可靠性(例如，99.999％)的传输。为了实现这个目标，引入了更低码率的传输，提高传输的可靠性。因此，在5G系统中至少有两种业务，URLLC和增强移动带宽(Enhance Mobile Broadband，eMBB)共存，两者在可靠性和时延方面的要求差别较大。
但当前系统无法根据不同的业务独立优化传输，导致系统传输效率过低，或者传输可靠性时延要求无法满足业务需求。
发明内容
本申请实施例提供一种控制信息传输方法、网络设备、终端和计算机存储介质。
为达到上述目的，本申请实施例的技术方案是这样实现的：
第一方面，本申请实施例提供了一种控制信息传输方法，所述方法包括：
终端接收用于数据调度的控制信息；
所述终端基于无线网络临时标识(Radio Network Temporary Identifier，RNTI)对所述控制信息进行解析；所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
第二方面，本申请实施例还提供了一种控制信息传输方法，所述方法包括：
网络设备确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；
所述网络设备发送所述控制信息。
第三方面，本申请实施例还提供了一种终端，所述终端包括：接收单元和解析单元；其中，
所述接收单元，配置为接收用于数据调度的控制信息；
所述解析单元，配置为基于RNTI对所述控制信息进行解析；所述RNTI为用于对 所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
第四方面，本申请实施例还提供了一种网络设备，所述网络设备包括：确定单元和发送单元；其中，
所述确定单元，配置为确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；
所述发送单元，配置为发送所述控制信息。
第五方面，本申请实施例还提供了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现本申请实施例所述的应用于上述第一方面或第二方面的方法的步骤。
第六方面，本申请实施例还提供了一种终端，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现本申请实施例所述的应用于上述第一方面的方法的步骤。
第七方面，本申请实施例还提供了一种网络设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现本申请实施例所述的应用于上述第二方面的方法的步骤。
第八方面，本申请实施例还提供了一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行上述第一方面或第二方面所述的方法。
第九方面，本申请实施例还提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面或第二方面所述的方法。
第十方面，本申请实施例还提供了一种计算机程序，所述计算机程序使得计算机执行上述第一方面或第二方面所述的方法。
本申请实施例提供的控制信息传输方法、网络设备、终端和计算机存储介质，网络设备确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI，发送所述控制信息；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；终端接收用于数据调度的控制信息；基于RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。采用本发明实施例的技术方案，通过网络设备基于不同的数据调度确定不同的RNTI，确定与数据调度相关的RNTI进而确定与RNTI相关的控制信息，实现了终端与网络设备之间基于数据调度对应的控制信息进行数据传输，从而实现了根据不同业务的数据独立优化传输，大大提升了传输效率，满足了不同业务的数据的传输可靠性和时延要求。
附图说明
图1为本申请实施例的一种通信系统架构的示意图；
图2为本申请实施例的控制信息传输方法的流程示意图一；
图3为本申请实施例的控制信息传输方法的流程示意图二；
图4为本申请实施例的控制信息传输方法的交互流程示意图；
图5为本申请实施例的终端的组成结构示意图；
图6为本申请实施例的网络设备的组成结构示意图；
图7为本申请实施例提供的一种通信设备的示意性框图；
图8为本申请实施例提供的一种芯片的示意性框图。
具体实施方式
下面结合附图及具体实施例对本申请作进一步详细的说明。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统或5G系统等。
示例性的，本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110，网络设备110可以是与终端设备120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线 接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话；可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System，PCS)终端；可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System，GPS)接收器的PDA；以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端设备可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可选地，5G系统或5G网络还可以称为NR系统或NR网络。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
可选地，该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
应理解，本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例，通信设备可包括具有通信功能的网络设备110和终端设备120，网络设备110和终端设备120可以为上文所述的具体设备，此处不再赘述；通信设备还可包括通信系统100中的其他设备，例如网络控制器、移动管理实体等其他网络实体，本申请实施例中对此不做限定。
本示例中的终端设备120均为本申请实施例中所述的终端。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请实施例提供了一种控制信息传输方法，应用于终端。图2为本申请实施例的控制信息传输方法的流程示意图一；如图2所示，所述方法包括：
步骤101：终端接收用于数据调度的控制信息。
步骤102：所述终端基于RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
本实施例中，作为一种实施方式，所述终端接收承载有控制信息和加扰后的冗余校验位的信号，基于所述信号获得用于数据调度的控制信息；作为另一种实施方式，所述 终端接收携带有加扰后的冗余校验位的控制信息。其中，对应于所述控制信息的所述冗余校验位的数量可以为至少一个。
本实施例中，用于解析控制信息的RNTI，可基于第一RNTI和/或第二RNTI解扰所述控制信息或者解扰所述加扰后的冗余校验位获得冗余校验位并进行校验确定，校验通过的冗余校验位对应的第一RNTI或第二RNTI作为用于解析所述控制信息。
其中，所述控制信息与所述RNTI相关；不同的数据调度对应不同的RNTI，从而对应不同的控制信息。可以理解，控制信息包括多种信息，对于配置信息，第一RNTI和第二RNTI分别对应于不同的信息，所述不同的信息包括信息的数目和/或信息的内容不同。
这里，所述第一RNTI和第二RNTI均用于终端专属数据调度。则终端基于第一RNTI或第二RNTI解扰控制信息获得循环冗余校验(CRC，Cyclic Redundancy Check)码，对CRC码进行校验，确定校验通过的第一RNTI或第二RNTI。
其中，所述第一RNTI和第二RNTI为RNTI数据集中的任意两个RNTI；所述RNTI数据集中包括至少两个RNTI。可以理解，用于数据调度的控制信息相关的RNTI有至少两个，不同的数据调度对应于不同的RNTI，相应对应于不同的控制信息。
其中，所述第一RNTI为小区无线网络临时标识(C-RNTI，Cell-Radio Network Temporary Identifier)。
本实施例中，所述控制信息包括以下信息的至少之一：下行链路控制信息格式(Downlink Control Information Format，DCI Format)、冗余版本(Redundancy Version)、混合自动重传请求进程数(Hybrid Automatic Repeat reQuest Process Number，HARQ Process Number)、信道状态信息请求(Channel Status Indicator request，CSI request)、物理下行共享信道与HARQ对应的时序关系(PDSCH-to-HARQ)、物理上行链路控制信道资源指示(PUCCH Resource Indicator)、偏移量参数(Betaoffset)。
其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
例如，对应于第一RNTI和对应于第二RNTI的控制信息中均可包括Redundancy Version和HARQ Process Number；则对应于第一RNTI的控制信息中的Redundancy Version可包括0、2、3、1四个版本，则对应于包含的信息的数目为4。对应于第二RNTI的控制信息中的Redundancy Version可包括{0，3}或{0，2}两个版本，则对应于包含的信息的数目为2；因此包含的信息的数量和内容均不同。而对应于第一RNTI的控制信息中的HARQ Process Number可包括16个进程，对应于第二RNTI的控制信息中的HARQ Process Number可包括4个进程，因此包含的信息的数量和内容均不同。
其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
采用本申请实施例的技术方案，通过网络设备确定与控制信息相关的RNTI进而确定用于数据调度的控制信息，即不同的数据调度确定不同的RNTI，实现了终端与网络设备之间基于数据调度对应的控制信息进行数据传输，从而实现了根据不同业务类型的数据独立优化传输，大大提升了传输效率，满足了不同业务类型的数据的传输可靠性和时延要求。
本申请实施例还提供了一种控制信息传输方法，应用于网络设备。图3为本申请实施例的控制信息传输方法的流程示意图二；如图3所示，所述方法包括：
步骤201：网络设备确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI。
步骤202：所述网络设备发送所述控制信息。
本实施例中，网络设备可基于不同的数据调度确定不同的RNTI，进而确定与RNTI相关的控制信息。实际应用中，网络设备可基于业务类型确定RNTI，进而确定控制信息中包括的信息，进一步确定控制信息中包括的信息的数量和/或内容。可以理解，控制信息包括多种信息，对于同种信息，第一RNTI和第二RNTI分别对应于不同的信息，所述不同的信息包括信息的数目和/或信息的内容不同。
这里，所述第一RNTI和第二RNTI为RNTI数据集中的任意两个RNTI；所述RNTI数据集中包括至少两个RNTI。可以理解，用于数据调度的控制信息相关的RNTI有至少两个，不同的数据调度对应于不同的RNTI，相应对应于不同的控制信息。网络设备可基于当前的数据调度选择对应的RNTI，进而确定相应的控制信息。
这里，网络设备确定控制信息，以及确定该控制信息对应的冗余校验位，该冗余校验位具体可通过CRC表示；网络设备基于确定的RNTI对CRC进行加扰，将控制信息以及加扰后的冗余校验位进行信道编码调制，映射到时频资源上发出。
作为一种实施方式，网络设备将所述控制信息以及加扰后的冗余校验位通过信号发出；作为另一种实施方式，网络设备发送控制信息，所述控制信息中携带有加扰后的冗余校验位。
本实施例中，所述控制信息包括以下信息的至少之一：DCI Format、Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset。
其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
例如，对应于第一RNTI和对应于第二RNTI的控制信息中均可包括Redundancy Version和HARQ Process Number；则对应于第一RNTI的控制信息中的Redundancy Version可包括0、2、3、1四个版本，则对应于包含的信息的数目为4。对应于第二RNTI 的控制信息中的Redundancy Version可包括{0，3}或{0，2}两个版本，则对应于包含的信息的数目为2；因此包含的信息的数量和内容均不同。而对应于第一RNTI的控制信息中的HARQ Process Number可包括16个进程，对应于第二RNTI的控制信息中的HARQ Process Number可包括4个进程，因此包含的信息的数量和内容均不同。
其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
采用本申请实施例的技术方案，通过网络设备确定与控制信息相关的RNTI进而确定用于数据调度的控制信息，即不同的数据调度确定不同的RNTI，实现了终端与网络设备之间基于数据调度对应的控制信息进行数据传输，从而实现了根据不同业务类型的数据独立优化传输，大大提升了传输效率，满足了不同业务类型的数据的传输可靠性和时延要求。
本申请实施例还提供了一种控制信息传输方法。图4为本申请实施例的控制信息传输方法的交互流程示意图；如图4所示，所述方法包括：
步骤301：网络设备确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI。
步骤302：所述网络设备发送所述控制信息。
步骤303：终端基于RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
本实施例中各步骤的具体实施过程具体可参照前述实施例所述，这里不再赘述。
下面针对所述控制信息包括各信息进行详细说明。
1、Redundancy Version
作为一种实施方式，基于第一RNTI加扰的控制信息中的Redundancy Version，长度可以为2bit，其四个取值对应冗余版本中的0、2、3、1四个版本。基于第二RNTI加扰的控制信息中的Redundancy Version域，长度可以为1bit，其两个取值对应冗余版本中的{0，3}或{0，2}两个版本。即分别对应于所述第一RNTI和所述第二RNTI的Redundancy Version的信息的数目不同，信息的内容也不同。
本实施方式中，对于码率较低的数据，{0，3}可以获得足够的编码分集增益。因此，配置{0，3}供动态选择，既可以满足充足的增量冗余(IR，Incremental Redundancy)合并增益，也可以减少控制信令开销，对于URLLC业务，减少控制信令开销，还有利于控制信令的可靠性。因此，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
2、HARQ Process Number
作为一种实施方式，基于第一RNTI加扰的控制信息中的HARQ Process Number，长度为可以为4bit，其16个取值对应0-15HARQ进程或1-16HARQ进程。基于第二RNTI加扰的控制信息中的HARQ Process Number，长度可以为2bit，其4个取值对应0-3HARQ进程或1-4HARQ进程。
其中，基于第一RNTI加扰的控制信息中的HARQ Process Number所对应的HARQ实体和/或HARQ缓存与基于第二RNTI加扰的控制信息中的HARQ Process Number所对应的HARQ实体和/或HARQ缓存相互独立，即使HARQ Process Number相同。
作为另一种实施方式，基于第一RNTI加扰的控制信息中的HARQ Process Number所对应的HARQ实体和/或HARQ缓存与基于第二RNTI加扰的控制信息中的HARQ Process Number所对应的HARQ实体和/或HARQ缓存相互独立，即使HARQ Process Number相同。
即分别对应于所述第一RNTI和所述第二RNTI的HARQ Process Number的信息的数目不同，信息的内容也不同。
本实施方式中，对于处理速度较快的业务或数据，仅需要较少的HARQ Process，就不会造成传输资源浪费；减少HARQ Process，可以减少相应的下行信令开销，对于URLLC业务，通常会快速完成检测(满足时延要求)；因此，对于URLLC业务，可基于第二RNTI加扰控制信息，少量的HARQ Process比特，不仅不会造成资源浪费，而且还有利于控制信令的可靠性；对于eMBB，可基于第一RNTI加扰控制信息。
3、CSI request
作为一种实施方式，基于第一RNTI加扰的控制信息中的CSI request，长度为可以为4bit，其16个取值对应16个CSI报告(CSI report)。其中，16个CSI report中至少一个CSI report包括较长的PUSCH符号，或者基于多种非零功率(NZP)-CSI/零功率(ZP)-CSI作为测量资源，以支持各种信号和干扰情况下的测量。基于第二RNTI加扰的控制信息中的CSI Request，长度为可以为1bit，其2个取值对应2个CSI report。其中，2个CSI report中至少一个CSI report是基于解调参考信号(Demodulation Reference Signal，DMRS)作为测量资源和/或时域测量窗与下行数据相同等，以减少信令开销，提高下行控制信令可靠性。即分别对应于所述第一RNTI和所述第二RNTI的CSI request的信息的数目不同，信息的内容也不同。
本实施方式中，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
4、PDSCH-to-HARQ
作为一种实施方式，基于第一RNTI加扰的控制信息中的PDSCH-to-HARQ，长度可以为3bit，其8个取值对应{3，4，5，6，8，12，16，20}。基于第二RNTI加扰的控制信息中的PDSCH-to-HARQ，长度为可以为1bit，其2个取值对应{0，1}。即分别对应于所述第一RNTI和所述第二RNTI的PDSCH-to-HARQ的信息的数目不同，信息的内容也不同。
本实施方式中，对于时延要求苛刻的传输，PDSCH-to-HARQ反馈需要尽快实现，否则HARQ反馈没有任何意义，无需反馈。因此，PDSCH-to-HARQ可选择的时机较少，用较少的比特位，如选择第二RNTI加扰的控制信息中对应于PDSCH-to-HARQ。对于时延要求不高的传输，考虑的上下行资源分配的灵活性，上行控制传输的效率，存在多 个可选的PDSCH-to-HARQ时机，需要用较多的比特位提高系统效率，如选择第一RNTI加扰的控制信息中对应于PDSCH-to-HARQ。另外，较少的PDSCH-to-HARQ比特位有利于提高控制信息传输的可靠性。
因此，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
5、PUCCH Resource Indicator
作为一种实施方式，基于第一RNTI加扰的控制信息中的PUCCH Resource Indicator，长度可以为3bit，其8个取值对应表1所示。表1包含了不同长度/PUCCH format、不同符号数量(Number of symbols)、不同物理资源块(PRB，Physical Resource Block)偏移值(offset)、不同初始CS索引集(Initial CS index set)，以满足时延可靠性需求，同时与其他用户配对传输，提高系统传输效率。基于第二RNTI加扰的控制信息中的PUCCH Resource Indicator，长度可以为3bit，其8个取值对应表2所示。表2包含了不同开始符号(Starting Symbol)，提高控制信道的时域资源的灵活度，满足低时延需求。
表1
Figure PCTCN2019093504-appb-000001
表2
Figure PCTCN2019093504-appb-000002
Figure PCTCN2019093504-appb-000003
本实施方式中，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
6、Beta_offset
作为一种实施方式，基于第一RNTI加扰的控制信息中的Beta_offset对应的{Beta_offset for HARQ-ACK,Beta_offset for CSI}集合，长度可以为2bit，其4个取值对应表3所示的{Beta_offset for HARQ-ACK,Beta_offset for CSI}集合。表3包含了Beta_offset都是大于1的数值。基于第二RNTI加扰的控制信息中的Beta_offset对应的{Beta_offset for HARQ-ACK,Beta_offset for CSI}集合，长度为可以为2bit，其4个取值对应表4所示的{Beta_offset for HARQ-ACK,Beta_offset for CSI}集合。表4包含了Beta_offset小于1的数值。对于传输可靠性要求高的数据，控制信道相对于数据的可靠性要求相当或者更低，因此，包含一些较小的值比较合理。否则，控制信道的传输效率过低，浪费资源。因此，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
表3
Beta_offset indicator Beta_offset for HARQ-ACK Beta_offset for CSI
00 1 1.25
01 4 1.75
10 31 5
11 126 10
表4
Beta_offset indicator Beta_offset for HARQ-ACK Beta_offset for CSI
00 1 1.25
01 4 1.75
10 0.5 0.6
11 0.01 0.05
综上可知，为满足URLLC的业务需求，采用如上所示的第二RNTI加扰控制信息，缩减了比特位；缩减的比特位可以用于指示其他信息，例如承载指示(Carrier Indicator)、CSI request、带宽部分(BWP，BandWidth Part)Indicator，或者用于扩展一些现有域，例如时域资源分配(Time Domain Resource Assignment)、PUCCH Resource Indicator、下行分配指数(DAI，Downlink Assignment Index)等等，以提高传输的灵活性。
7、DCI format
作为一种实施方式，基于第一RNTI加扰的控制信息中所包含的域值，如表5或表6所示的Fallback DCI列；基于第二RNTI加扰的控制信息中所包含的域值，如表5或表6所示的New DCI列。New DCI相比Fallback DCI，缩减了部分域，因为其对于特定 业务的传输，不是必要的，或者无法明显提高传输效率。但额外增加了一些域，例如Carrier Indicator、CSI request、BWP Indicator.或者扩展一些域，例如Time Domain Resource Assignment、PUCCH Resource Indicator、DAI等等提高传输的灵活性，降低传输时延，提高传输效率。因此，对于URLLC业务，可基于第二RNTI加扰控制信息；对于eMBB，可基于第一RNTI加扰控制信息。
表5
Figure PCTCN2019093504-appb-000004
表6
Figure PCTCN2019093504-appb-000005
本申请实施例还提供了一种终端。图5为本申请实施例的终端的组成结构示意图；如图5所示，所述终端包括：接收单元31和解析单元32；其中，
所述接收单元31，配置为接收用于数据调度的控制信息；
所述解析单元32，配置为基于RNTI对所述接收单元31接收的所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
本实施例中，所述控制信息包括以下信息的至少之一：DCI Format、Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset。
在本申请的一种可选实施例中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
在本申请的一种可选实施例中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
本实施例中，所述第一RNTI和第二RNTI均用于终端专属数据调度。其中，所述第一RNTI为C-RNTI。
需要说明的是：上述实施例提供的终端在进行控制信息传输时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将终端的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的终端与控制信息传输方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例中，所述终端中的解析单元32，在实际应用中可由所述终端中的中央处理器(Central Processing Unit，CPU)、数字信号处理器(Digital Signal Processor，DSP)、微控制单元(Microcontroller Unit，MCU)或可编程门阵列(Field－Programmable Gate Array，FPGA)实现；所述终端中的接收单元31，在实际应用中可通过通信模组(包含：基础通信套件、操作系统、通信模块、标准化接口和协议等)及收发天线实现。
本申请实施例还提供了一种网络设备。图6为本申请实施例的网络设备的组成结构示意图；如图6所示，所述网络设备包括：确定单元41和发送单元42；其中，
所述确定单元41，配置为确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；
所述发送单元42，配置为发送所述控制信息。
本实施例中，所述控制信息包括以下信息的至少之一：DCI Format、Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset。
其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控 制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
本实施例中，所述第一RNTI和第二RNTI均用于终端专属数据调度。其中，所述第一RNTI为C-RNTI。
需要说明的是：上述实施例提供的网络设备在进行控制信息传输时，仅以上述各程序模块的划分进行举例说明，实际应用中，可以根据需要而将上述处理分配由不同的程序模块完成，即将网络设备的内部结构划分成不同的程序模块，以完成以上描述的全部或者部分处理。另外，上述实施例提供的网络设备与控制信息传输方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
本申请实施例中，所述网络设备中的确定单元41，在实际应用中均可由所述终网络设备中的CPU、DSP、MCU或FPGA实现；所述网络设备中的发送单元42，在实际应用中可通过通信模组(包含：基础通信套件、操作系统、通信模块、标准化接口和协议等)及收发天线实现。
本申请实施例还提供了一种通信设备，图7为本申请实施例提供的一种通信设备的示意性框图；如图7所示，通信设备包括处理器610，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，所述通信设备为终端，所述处理器执行所述程序时实现：接收用于数据调度的控制信息；基于RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
可选地，所述通信设备为网络设备，所述处理器执行所述程序时实现：确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；发送所述控制信息。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，如图7所示，通信设备还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
本申请实施例的终端或网络设备中，可以理解，可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过 示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
在示例性实施例中，本申请实施例还提供了一种计算机可读存储介质，例如包括计算机程序的存储器，上述计算机程序可由终端或网络设备的处理器执行，以完成前述方法所述步骤。计算机可读存储介质可以是FRAM、ROM、PROM、EPROM、EEPROM、Flash Memory、磁表面存储器、光盘、或CD-ROM等存储器。
本申请实施例还提供了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现：接收用于数据调度的控制信息；基于RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI；或者，该指令被处理器执行时实现：确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI 包括第一RNTI或第二RNTI；发送所述控制信息。
本申请实施例还提供了一种芯片，图8为本申请实施例提供的一种芯片的示意性框图，如图8所示，所述芯片包括：处理器710，用于从存储器720中调用并运行计算机程序，使得安装有所述芯片的设备执行本申请实施例所述的应用于终端的方法；或者，执行本申请实施例所述的应用于网络设备的方法。
可选地，芯片还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行本申请实施例所述的应用于终端的方法；或者，该计算机程序指令使得计算机执行本申请实施例任一项所述的应用于网络设备的方法。
本申请实施例还提供了一种计算机程序，所述计算机程序使得计算机执行如本申请实施例所述的应用于终端的方法；或者，所述计算机程序使得计算机执行本申请实施例所述的应用于网络设备的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单 元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (30)

  1. 一种控制信息传输方法，所述方法包括：
    终端接收用于数据调度的控制信息；
    所述终端基于无线网络临时标识RNTI对所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
  2. 根据权利要求1所述的方法，其中，所述控制信息包括以下信息的至少之一：下行链路控制信息格式DCI Format、冗余版本Redundancy Version、混合自动重传请求进程数HARQ Process Number、信道状态信息请求CSI request、物理下行共享信道与HARQ对应的时序关系PDSCH-to-HARQ、物理上行链路控制信道资源指示PUCCH Resource Indicator、偏移量参数Betaoffset。
  3. 根据权利要求1或2所述的方法，其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
  4. 根据权利要求1至3任一项所述的方法，其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
  5. 根据权利要求1至4任一项所述的方法，其中，所述第一RNTI为小区无线网络临时标识C-RNTI。
  6. 根据权利要求1至4任一项所述的方法，其中，所述第一RNTI和第二RNTI均用于终端专属数据调度。
  7. 一种控制信息传输方法，所述方法包括：
    网络设备确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；
    所述网络设备发送所述控制信息。
  8. 根据权利要求7所述的方法，其中，所述控制信息包括以下信息的至少之一：下行链路控制信息格式DCI Format、冗余版本Redundancy Version、混合自动重传请求进程数HARQ Process Number、信道状态信息请求CSI request、物理下行共享信道与HARQ对应的时序关系PDSCH-to-HARQ、物理上行链路控制信道资源指示PUCCH Resource Indicator、偏移量参数Betaoffset。
  9. 根据权利要求7或8所述的方法，其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
  10. 根据权利要求7至9任一项所述的方法，其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
  11. 根据权利要求7至10任一项所述的方法，其中，所述第一RNTI为小区无线网络临时标识C-RNTI。
  12. 根据权利要求7至10任一项所述的方法，其中，所述第一RNTI和第二RNTI均用于终端专属数据调度。
  13. 一种终端，所述终端包括：接收单元和解析单元；其中，
    所述接收单元，配置为接收用于数据调度的控制信息；
    所述解析单元，配置为基于无线网络临时标识RNTI对所述接收单元接收的所述控制信息进行解析，所述RNTI为用于对所述控制信息的冗余校验位进行加扰的第一RNTI或第二RNTI。
  14. 根据权利要求13所述的终端，其中，所述控制信息包括以下信息的至少之一：下行链路控制信息格式DCI Format、冗余版本Redundancy Version、混合自动重传请求进程数HARQ Process Number、信道状态信息请求CSI request、物理下行共享信道与HARQ对应的时序关系PDSCH-to-HARQ、物理上行链路控制信道资源指示PUCCH Resource Indicator、偏移量参数Betaoffset。
  15. 根据权利要求14所述的终端，其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
  16. 根据权利要求14所述的终端，其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
  17. 根据权利要求13至16任一项所述的终端，其中，所述第一RNTI为小区无线网络临时标识C-RNTI。
  18. 根据权利要求13至16任一项所述的终端，其中，所述第一RNTI和第二RNTI均用于终端专属数据调度。
  19. 一种网络设备，所述网络设备包括：确定单元和发送单元；其中，
    所述确定单元，配置为确定用于数据调度的控制信息以及所述控制信息的冗余校验位加扰采用的RNTI；所述控制信息与所述RNTI相关；所述RNTI包括第一RNTI或第二RNTI；
    所述发送单元，配置为发送所述控制信息。
  20. 根据权利要求19所述的网络设备，其中，所述控制信息包括以下信息的至少之一：下行链路控制信息格式DCI Format、冗余版本Redundancy Version、混合自动重传请求进程数HARQ Process Number、信道状态信息请求CSI request、物理下行共享信 道与HARQ对应的时序关系PDSCH-to-HARQ、物理上行链路控制信道资源指示PUCCH Resource Indicator、偏移量参数Betaoffset。
  21. 根据权利要求19或20所述的网络设备，其中，当所述控制信息包括Redundancy Version、HARQ Process Number、CSI request、PDSCH-to-HARQ、PUCCH Resource Indicator、Betaoffset中的至少一种信息时，所述控制信息中分别对应于所述第一RNTI和所述第二RNTI的同种信息包含的信息的数目不同和/或信息的内容不同。
  22. 根据权利要求19至21任一项所述的网络设备，其中，所述控制信息包括DCI Format时，分别对应于所述第一RNTI和所述第二RNTI的DCI Format的有效长度不同，或者DCI Format包含的域信息不同。
  23. 根据权利要求19至22任一项所述的网络设备，其中，所述第一RNTI为小区无线网络临时标识C-RNTI。
  24. 根据权利要求19至22任一项所述的网络设备，其中，所述第一RNTI和第二RNTI均用于终端专属数据调度。
  25. 一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现权利要求1至6任一项所述方法的步骤；或者，该指令被处理器执行时实现权利要求7至12任一项所述方法的步骤。
  26. 一种终端，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现权利要求1至6任一项所述方法的步骤。
  27. 一种网络设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述程序时实现权利要求7至12任一项所述方法的步骤。
  28. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至6任一项所述的方法；或者，执行如权利要求7至12任一项所述的方法。
  29. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至6任一项所述的方法；或者，该计算机程序指令使得计算机执行如权利要求7至12任一项所述的方法。
  30. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至6任一项所述的方法；或者，所述计算机程序使得计算机执行如权利要求7至12任一项所述的方法。
PCT/CN2019/093504 2018-06-28 2019-06-28 控制信息传输方法、网络设备、终端和计算机存储介质 WO2020001579A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201980011118.5A CN111670599B (zh) 2018-06-28 2019-06-28 控制信息传输方法、网络设备、终端和计算机存储介质

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810690454 2018-06-28
CN201810690454.4 2018-06-28

Publications (1)

Publication Number Publication Date
WO2020001579A1 true WO2020001579A1 (zh) 2020-01-02

Family

ID=68984492

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/093504 WO2020001579A1 (zh) 2018-06-28 2019-06-28 控制信息传输方法、网络设备、终端和计算机存储介质

Country Status (2)

Country Link
CN (1) CN111670599B (zh)
WO (1) WO2020001579A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111246588A (zh) * 2020-01-10 2020-06-05 北京邮电大学 Nr系统中的解决不同优先级业务之间无序调度的方法
WO2022105561A1 (zh) * 2020-11-17 2022-05-27 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质
CN114731663A (zh) * 2020-02-20 2022-07-08 Oppo广东移动通信有限公司 数据传输方法、终端设备和网络设备
CN114762421A (zh) * 2020-02-20 2022-07-15 Oppo广东移动通信有限公司 用于确定混合自动重传请求信息的方法、终端设备和网络设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112202503B (zh) * 2020-09-22 2022-08-26 展讯通信（上海）有限公司 一种干扰处理方法、终端设备和计算机可读存储介质
CN115174010A (zh) * 2021-04-06 2022-10-11 维沃移动通信有限公司 信息确定、信息指示方法、装置、终端及网络侧设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107078990A (zh) * 2014-11-07 2017-08-18 联发科技（新加坡）私人有限公司 资源分配的方法以及装置
CN107223319A (zh) * 2017-04-28 2017-09-29 北京小米移动软件有限公司 公共下行控制信息的传输、获取方法及装置
WO2018165872A1 (zh) * 2017-03-14 2018-09-20 广东欧珀移动通信有限公司 用于确定基础参数集的方法、终端和网络设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107734676B (zh) * 2016-08-12 2021-06-08 中兴通讯股份有限公司 一种数据传输的方法和装置
EP3535886A1 (en) * 2016-11-02 2019-09-11 IDAC Holdings, Inc. Shared data channel design

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107078990A (zh) * 2014-11-07 2017-08-18 联发科技（新加坡）私人有限公司 资源分配的方法以及装置
WO2018165872A1 (zh) * 2017-03-14 2018-09-20 广东欧珀移动通信有限公司 用于确定基础参数集的方法、终端和网络设备
CN107223319A (zh) * 2017-04-28 2017-09-29 北京小米移动软件有限公司 公共下行控制信息的传输、获取方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Indication of URLLC Configuration", 3GPP TSG-RAN WG1 MEETING #93 RI-1806017, 25 May 2018 (2018-05-25), XP051441235 *
LG ELECTRONICS: "Discussion on differentiation of eMBB and URLLC services", 3GPP TSG RAN WG1 MEETING #94BIS R1-1810297, 12 October 2018 (2018-10-12), XP051517711 *
QUALCOMM INCORPORATED: "Considerations on differentiating eMBB and URLLC", 3GPP TSG-RAN WG1 #93 RL-1807367, 25 May 2018 (2018-05-25), XP051442559 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111246588A (zh) * 2020-01-10 2020-06-05 北京邮电大学 Nr系统中的解决不同优先级业务之间无序调度的方法
CN111246588B (zh) * 2020-01-10 2021-10-26 北京邮电大学 Nr系统中的解决不同优先级业务之间无序调度的方法
CN114731663A (zh) * 2020-02-20 2022-07-08 Oppo广东移动通信有限公司 数据传输方法、终端设备和网络设备
CN114762421A (zh) * 2020-02-20 2022-07-15 Oppo广东移动通信有限公司 用于确定混合自动重传请求信息的方法、终端设备和网络设备
WO2022105561A1 (zh) * 2020-11-17 2022-05-27 中国移动通信有限公司研究院 数据传输方法、装置、相关设备及存储介质

Also Published As

Publication number Publication date
CN111670599B (zh) 2022-04-05
CN111670599A (zh) 2020-09-15

Similar Documents

Publication Publication Date Title
WO2020001579A1 (zh) 控制信息传输方法、网络设备、终端和计算机存储介质
WO2020051774A1 (zh) 通信方法、终端设备和网络设备
CN111641483B (zh) 一种反馈信息传输方法及装置、通信设备
US10827480B2 (en) Method for transmitting control information, user equipment, and network device
JP2020523893A (ja) 通信方法、端末デバイス、及びネットワークデバイス
WO2020001484A1 (zh) 一种上行信号的传输方法及终端设备、网络设备
WO2020062068A1 (zh) 无线通信方法、终端设备和网络设备
US20210211175A1 (en) Method for feeding back and receiving information, and device
US11856595B2 (en) Wireless communication method and apparatus
KR102683100B1 (ko) 상향 제어 정보의 결정 방법 및 통신 디바이스
WO2020073623A1 (zh) 一种资源配置方法及装置、通信设备
WO2020133457A1 (zh) 无线通信方法、网络设备和终端设备
WO2020061950A1 (zh) 通信方法、终端设备和网络设备
WO2020143052A1 (zh) 用于传输反馈信息的方法、终端设备和网络设备
TW202008827A (zh) 資源配置的方法、終端設備和網路設備
WO2020061776A1 (zh) 一种反馈资源的复用方法、终端设备及网络设备
CN114302408B (zh) 无线通信的方法、终端设备和网络设备
WO2021068140A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020034161A1 (zh) 一种下行信号传输方法、终端和计算机可读存储介质
CN109818716B (zh) 一种mcs配置方法及装置、终端设备、网络设备
WO2020024250A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021056557A1 (zh) Harq反馈的方法和终端设备
WO2020056719A1 (zh) 一种信息传输时间的确定方法、终端设备及网络设备
WO2020132992A1 (zh) 下行控制信号传输方法、终端设备、网络设备及存储介质
WO2020034166A1 (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: 19826867

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

Country of ref document: EP

Kind code of ref document: A1