A method, device and computer-readable storage medium for receiving millimeter wave (mmWave) communications

Abstract

In the first exemplary embodiment of the present disclosure, a control transmission part of a millimeter wave (mmWave) communication is received at a user equipment. The control transmission part is divided into a plurality of control transmission part sub-areas, each of which schedules data transmission of a corresponding sub-area of ​​a data transmission part of the mmWave communication. The first of the control transmission part sub-areas is then demodulated and decoded. Based on the first of the demodulated and decoded control transmission part sub-areas, a receiving analog antenna beamforming is arranged. Beamforming is performed on a first sub-area of ​​a data transmission part of the mmWave communication, the first sub-area of ​​the data transmission part corresponding to the first of the control transmission part sub-areas. During the arrangement and execution, the second of the control transmission part sub-areas is demodulated and decoded.

Description

[0001] The present application is a divisional application of the patent application entitled Device, network and method for receiving data transmission with scheduled decoding delay in millimeter wave communication and the patent application number is 201680025375.0. Technical Field

[0002] The present disclosure relates to devices, networks, and methods for wireless communications, and in specific embodiments, to devices and methods for receiving data transmissions with scheduling decoding delays in millimeter wave communications. Background Art

[0003] The amount of wireless data used in mobile networks has increased dramatically over the past few years, pushing the capacity of current macrocellular deployments. Cellular communication systems that utilize microwave spectrum bands (300MHz to 3GHz) have become capacity limited due to interference and traffic load. The use of high-frequency bands (e.g., 28, 38, 60, and 73GHz) where large amounts of bandwidth are available is considered a key technology for next-generation communication systems. Using these high-frequency bands can alleviate the capacity issues currently observed. Summary of the invention

[0004] Various methods and systems are provided for providing reception of millimeter wave (mmWave) communications using various delay techniques to ensure the best possible beamforming from the mmWave communications.

[0005] In a first exemplary embodiment, a method for receiving mmWave communications is provided. A control transmission portion of mmWave communications is received at a user equipment. The control transmission portion is divided into a plurality of control transmission portion sub-areas, each of which schedules data transmission for a corresponding sub-area of ​​a data transmission portion of mmWave communications. The first of the control transmission portion sub-areas is then demodulated and decoded. According to the first of the demodulated and decoded control transmission portion sub-areas, receive analog antenna beamforming is arranged. Beamforming is performed on a first sub-area of ​​the data transmission portion of mmWave communications, the first sub-area of ​​the data transmission portion corresponding to the first of the control transmission portion sub-areas. During the arrangement and execution, the second of the control transmission portion sub-areas is demodulated and decoded. After the beamforming on the first sub-area of ​​the data transmission portion of mmWave communications is completed, according to the second of the demodulated and decoded control transmission portion sub-areas, receive analog antenna beamforming is arranged, and beamforming is performed on a second sub-area of ​​the data transmission portion of mmWave communications, the second sub-area of ​​the data transmission portion corresponding to the second of the control transmission portion sub-areas.

[0006] In a second exemplary embodiment, another method for receiving millimeter wave (mmWave) communications is provided. A control transmission portion of the mmWave communication is received at a user equipment (UE). Scheduling restrictions are assigned to an earlier portion of the control transmission portion of the mmWave communication. Demodulation and decoding of the earlier portion of the control transmission portion are performed. Before the demodulation and decoding are completed, an earlier portion of the data transmission portion of the mmWave communication is received, the earlier portion of the data transmission portion of the mmWave communication corresponding to the earlier portion of the control transmission portion of the mmWave communication. Beamforming is then performed on the earlier portion of the data transmission portion of the mmWave communication using default parameters. Demodulation and decoding of a later portion of the control transmission portion is performed. Beamforming of the later portion of the data transmission portion of the mmWave communication is then performed using parameters obtained during the demodulation and decoding of the later portion of the control transmission portion. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] For a more complete understanding of the subject matter of the present invention and its benefits, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

[0008] Figure 1 An example of a hybrid beamforming architecture with a shared array is shown.

[0009] Figure 2 An example of another hybrid beamforming architecture with subarrays is shown.

[0010] Figure 3 It is described how transmission / reception from a controller to a UE is referred to as downlink (DL) transmission / reception, and how transmission / reception from a UE to a controller is referred to as uplink (UL) transmission / reception.

[0011] Figure 4 is a diagram illustrating example resource blocks according to an exemplary embodiment.

[0012] Figure 5 is a diagram illustrating example data grouping according to an exemplary embodiment.

[0013] Figure 6 is a diagram illustrating a control transmission region (eg, PDCCH) and a data transmission region (eg, PDSCH) according to an exemplary embodiment.

[0014] Figure 7 is a diagram illustrating a divided control transmission region and a divided data transmission region according to an exemplary embodiment.

[0015] Figure 8 is a diagram illustrating a delay of a start portion of data transmission according to an exemplary embodiment.

[0016] Fig. 9 is a flow chart illustrating a method for processing incoming data transmissions in mmWave communications according to an exemplary embodiment.

[0017] Fig.10 is a flow chart illustrating in more detail the division of the control transmission part and the data transmission part into sub-areas according to an exemplary embodiment.

[0018] Fig.11 is a flow chart illustrating in more detail the application of scheduling restrictions to an earlier portion of a data transmission according to an exemplary embodiment.

[0019] Fig.12 is a block diagram illustrating a representative software architecture that may be used in conjunction with the various hardware architectures described herein.

[0020] Fig.13 is a block diagram illustrating components of a machine capable of reading instructions from a machine-readable medium (eg, a machine-readable storage medium) and performing one or more of the methodologies discussed herein, according to some example embodiments. DETAILED DESCRIPTION

[0021] In the following description, reference is made to the accompanying drawings which form a part thereof, and in which the drawings show by way of illustration specific embodiments that can be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the subject matter disclosed herein, and it is understood that other embodiments may be used and structural, logical, and electrical changes may be made without departing from the scope of the present disclosure. Therefore, the following description of exemplary embodiments is not to be considered limiting.

[0022] In one embodiment, the functions or algorithms described herein may be implemented in software or a combination of software and manually implemented processes. The software may consist of computer executable instructions stored on a computer readable medium or a computer readable storage device such as one or more non-temporary memories or other types of hardware-based storage devices that are local or networked. In addition, these functions correspond to modules that may be software, hardware, firmware, or any combination thereof. Multiple functions may be performed in one or more modules as desired, and the described embodiments are merely examples. The software may be executed on a digital signal processor, an application-specific integrated circuit (ASIC), a microprocessor, or other type of processor operating on a computer system such as a personal computer, a server, or other computer system.

[0023] Propagation in the millimeter wave band (mmWave) is more challenging than in the microwave band, resulting in a tighter link budget in the mmWave band than in the microwave band. Equipping the transmitter and receiver with more antenna arrays is a viable solution to compensate for the additional path loss of mmWave through beamforming.

[0024] Since antenna size is inversely proportional to carrier frequency, using these high frequency bands significantly reduces antenna size. This opens the door to using a greater number of transmit and receive antenna arrays both on the network side and on the terminal side.

[0025] Hybrid antenna architectures are likely to be used to trade off hardware complexity, power consumption, and system performance and coverage. Hybrid antenna architectures typically include both analog (phase shifters) and digital (baseband precoder) beamforming components.

[0026] A base station may include one or more radio frequency (RF) chains, and each RF chain is connected to an analog phase shifter and an antenna array. A UE receiver may include one or more RF chains connected to a receiver analog phase shifter and an antenna array.

[0027] There are different types of analog beamforming architectures: shared array and subarray. Figure 1An example of a hybrid beamforming architecture 100 with a shared array is shown. The architecture 100 includes a baseband beamforming transmitter 102 and a baseband beamforming receiver 104. In an exemplary embodiment, the baseband beamforming transmitter 102 can be implemented as a baseband beamforming transmission device. In another exemplary embodiment, the baseband beamforming receiver 104 can be implemented as a baseband beamforming reception device. The baseband beamforming transmitter 102 includes a plurality of precoders 106A-106B. The precoders 106A-106B are used to exploit transmit diversity by weighting information streams. In an exemplary embodiment, each precoder 106A-106B can be implemented as a precoding device. Digital-to-Analog converters (DACs) 108A, 108B are then used to convert the precoded digital signals into analog signals for transmission to the transmitter shared array 110. In an exemplary embodiment, each DAC 108A, 108B can be implemented as a digital-to-analog conversion device. In another exemplary embodiment, the transmitter sharing array 110 may be implemented as a transmitter sharing array device. Then, the receiver sharing array 112 receives the transmitted signal, and one or more analog-to-digital converters (ADCs) 114A, 114B convert the received signal into digital. In an exemplary embodiment, the receiver sharing array 112 may be implemented as a receiver sharing array device. In another exemplary embodiment, each of the ADCs 114A, 114B may be implemented as an analog-to-digital conversion device. Finally, one or more equalizers 116A, 116B are used to equalize the digital signal. In an exemplary embodiment, each of the equalizers 116A, 116B may be implemented as an equalization device.

[0028] Figure 2 An example of another hybrid beamforming architecture 200 with subarrays is shown. This architecture 200 provides a Figure 1 However, the remainder of the architecture 200 is similar to Figure 1The architecture 200 is the same as the shared hybrid beamforming architecture 100 of FIG. The architecture 200 includes a baseband beamforming transmitter 202 and a baseband beamforming receiver 204. In an exemplary embodiment, the baseband beamforming transmitter 202 may be implemented as a baseband beamforming transmission device. In another exemplary embodiment, the baseband beamforming receiver 204 may be implemented as a baseband beamforming reception device. The baseband beamforming transmitter 202 includes a plurality of precoders 206A-206B. The precoders 206A-206B are used to exploit transmit diversity by weighting information streams. In an exemplary embodiment, each precoder 206A-206B may be implemented as a precoding device. Then digital-to-analog converters (DACs) 208A, 208B are used to convert the precoded digital signals into analog signals for transmission to the transmitter subarray 210. In an exemplary embodiment, each of the DACs 208A, 208B may be implemented as a digital-to-analog conversion device. In another exemplary embodiment, the transmitter subarray 210 may be implemented as a transmitter shared array device. Then, the receiver subarray 212 receives the transmitted signal, and one or more analog-to-digital converters (ADCs) 214A, 214B convert the received signal to digital. In an exemplary embodiment, the receiver subarray 212 can be implemented as a receiver subarray device. In another exemplary embodiment, each of the ADCs 214A, 214B can be implemented as an analog-to-digital conversion device. Finally, one or more equalizers 216A, 216B equalize the digital signal. In an exemplary embodiment, each of the equalizers 216A, 216B can be implemented as an equalization device.

[0029] Figure 3 It is described how transmission / reception from the controller 300 to the UE 302 is referred to as downlink (DL) transmission / reception, and how transmission / reception from the UE 304 to the controller 300 is referred to as uplink (UL) transmission / reception.

[0030] In modern wireless communication systems such as the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) compatible communication systems, multiple cells or evolved NodeBs (eNBs) (also commonly referred to as NodeBs, base stations (BSs), base stations, communication controllers, network controllers, controllers, access points (APs), etc.) can be arranged into a cluster of cells, each cell having multiple transmit antennas. In addition, each cell or eNB can serve multiple users (also commonly referred to as User Equipment (UE), mobile stations, users, subscribers, terminals, etc.) based on priority metrics such as fairness, proportional fairness, round-robin, etc. over a period of time. It should be noted that the terms cell, transmission point, and eNB can be used interchangeably. A distinction between cells, transmission points, and eNBs will be made when necessary.

[0031] In an orthogonal frequency-division multiplexing (OFDM) system, the frequency bandwidth is divided into multiple subcarriers in the frequency domain. In the time domain, one subframe is divided into multiple OFDM symbols. OFDM symbols may have a cyclic prefix to avoid inter-symbol interference due to multiple path delays. A resource element (RE) is defined by the time-frequency resources within one subcarrier and one OFDM symbol. Reference signals and other signals, such as data channels, such as physical downlink shared channel (PDSCH) and control channels, such as physical downlink control channel (PDCCH), are orthogonalized and multiplexed in different resource elements in the time domain. In addition, the signals are modulated and mapped into the resource elements. Using an inverse Fourier transform for each OFDM symbol, the signal in the frequency domain is transformed into a signal in the time domain and sent with an additional cyclic prefix to avoid inter-symbol interference.

[0032] Each resource block (RB) contains multiple REs. Figure 4is a diagram showing an example resource block 400 according to an exemplary embodiment. Resource block 400 includes many different resource units, such as resource unit 402. For each resource block 400, there are 14 OFDM symbols labeled from 0 to 13 in each subframe. Symbols 0 to 6 in each subframe correspond to even time slots, and symbols 7 to 13 in each subframe correspond to odd time slots. In the figure, only seven OFDM symbols (404) are shown. There are also 12 subcarriers (406) in each resource block 400, so in this example, there are 132 REs in an RB. In each subframe, there are multiple RBs, and the number can depend on the bandwidth (BW).

[0033] Figure 5 is a diagram showing example data packets 500A, 500B according to an exemplary embodiment. The data channel that transmits the data packet 500A from the eNB to the UE in the physical layer is referred to as a physical downlink shared channel (PDSCH) 502 and 511, and the data channel that transmits the data packet 500B from the UE to the eNB in ​​the physical layer is referred to as a physical uplink shared channel (PUSCH) 504 and 505. The corresponding physical control channel sent from the eNB to the UE indicates where the corresponding PDSCH 502 and 511 and / or PUSCH 504 and 505 are located in the frequency domain, and in which manner the PDSCH 502 and 511 and / or PUSCH 504 and 505 are transmitted, which is referred to as a physical downlink control channel (PDCCH) 502, 503 and 505. In Figure 5 In the embodiment, PDCCH 501 may indicate signaling of PDSCH 502 or PUSCH 504.

[0034] UE measures the channel state, especially for multiple antennas. PMI / CQI / RI and other feedback can be based on the measurement of reference signals. PMI is the precoding matrix indicator, CQI is the channel quality indicator, and RI is the rank indicator of the precoding matrix. Multiple reference signal resources can be configured for the UE. Specific time-frequency resources and scrambling codes are allocated by the eNB for each reference signal resource.

[0035] Typically, eNBs may be arranged close to each other so that a decision made by a first eNB may have an impact on a second eNB. For example, the eNBs may use their transmit antenna arrays to form beams towards their UEs when serving them. This may mean that if the first eNB decides to serve the first UE in a specific time-frequency resource, it may form a beam directed towards that UE. However, the directed beam may extend into the coverage area of ​​the second eNB and cause interference to the UE served by the second eNB. Inter-cell interference (ICI) in small cell wireless communication systems is often referred to as an interference-limited cell scenario, which may be different from the noise-limited cell scenario seen in large cell wireless communication systems.

[0036] In an exemplary embodiment, the eNodeB can control one or more cells. Multiple remote wireless units can be connected to the same baseband unit of the eNodeB via optical cables, and the latency between the baseband unit and the remote wireless units is quite small. Therefore, the same baseband unit can handle the coordinated transmission / reception of multiple cells. For example, the eNodeB can coordinate the transmission of multiple cells to the UE, which is called coordinated multiple point (CoMP) transmission. The eNodeB can also coordinate the reception of multiple cells from the UE, which is called CoMP reception. In this case, the backhaul link between these cells with the same eNodeB is a fast backhaul, and the scheduling of PDSCHs transmitted in different cells for the UE can be easily coordinated in the same eNodeB.

[0037] In a typical system design such as LTE, the PDCCH channel containing control information for receiving data transmission is sent first, followed by the corresponding data transmission. Upon receiving the PDCCH signal, the UE starts baseband processing of the control signal, i.e., demodulation and decoding of the control message. Since the baseband processing takes some time to complete, the UE must receive the data transmission signal before the control signal processing is completed. This is not a problem for typical low-band systems because the UE buffers the received signal.

[0038] Due to the large path loss characteristics of the high frequency band, the control message decoding delay poses a serious problem for mmWave system design. In order to properly receive the data signal, the UE needs to apply the correct analog receive beamforming that matches the analog transmit beamforming adopted at the eNodeB transmitter. Once the control message is decoded, information about the scheduled data transmission is available, such as rank, PMI, etc., and then the UE can find out the analog transmit beam corresponding to the data transmission and apply the matching analog receive beamforming to receive the signal. However, due to the control message decoding delay, in mmWave communication, the UE cannot apply the analog receive beamforming that matches the transmit beamforming before the data signal reception starts. Even if the UE buffer has the received signal, the signal will be invalid due to the mismatch of the analog transmit and receive beamforming until the decoding result of the control message becomes available. Only in this way can the UE apply the matching analog receive beamforming according to the decoding result of the control message.

[0039] Figure 6 6 is a diagram depicting a control transmission region (e.g., PDCCH) and a data transmission region (e.g., PDSCH) according to an exemplary embodiment. As can be seen, the control transmission region 600 is received first, followed by the data transmission region 602. At time 604, PDSCH receive beamforming may be ready, but the PDCCH demodulation and decoding results are not ready until time 606.

[0040] In an exemplary embodiment, an apparatus and method for dividing a control transmission region 600 (e.g., PDCCH) and a data transmission region 602 (e.g., PDSCH) into sub-regions are provided. Each control sub-region schedules data transmission of a corresponding data transmission sub-region. Since a gap is introduced between the transmission of the control message and the scheduled data, the UE can complete decoding of the control message and apply matching analog receive beamforming before the corresponding data transmission reception begins. In other words, due to the delay gap introduced between the scheduling and transmission of the corresponding sub-region, the UE can support its receive analog beamforming according to the corresponding control sub-region decoding result to receive the data sub-region transmission.

[0041] Figure 77 is a diagram showing a divided control transmission area and a divided data transmission area according to an exemplary embodiment. Here, the control transmission area 700 has been divided into sub-area 702A and sub-area 702B, and the data transmission area 704 has been divided into sub-area 706A and sub-area 706B. In this way, before the data transmission area sub-area 706A is ready for receiving beamforming at time 710, the system can demodulate and decode sub-area 702A at time 708. Similarly, before the data transmission area sub-area 706B is ready for receiving beamforming at time 714, the system can demodulate and decode sub-area 702B at time 712.

[0042] In an alternative exemplary embodiment, a device and method for imposing scheduling restrictions on data transmission from the start of the data transmission timeline is provided. In this case, the UE scheduled for data transmission applies the default simulated receive beamforming for data signal reception, such as the simulated transmit beamforming corresponding to the latest reported characterization of the UE, including rank, PMI, simulated transmit beamforming, etc. Correspondingly, the network also applies the default simulated transmit beamforming, rank and PMI in the data transmission of these specific scheduled UEs.

[0043] Although a delay is imposed at the start of data transmission, in an exemplary embodiment, no restriction is imposed on the portion of the data transmission (eg, PDSCH) that starts from a later portion of the data transmission timeline. Figure 8 8 is a diagram illustrating a delay of a beginning portion of a data transmission according to an exemplary embodiment. Here, demodulation and decoding of a first portion 800 of a control transmission region 802 is performed first, which is completed at time 804, and demodulation and decoding of a second portion 806 of the control transmission region 802 is performed second, which is completed at time 808. Data transmission begins at time 810; however, scheduling restrictions are applied to a transmission time interval (TTI). 1 )812, resulting in TTI 1 The beamforming for TTI is performed using default parameters (described in more detail below). 2 814, since the second portion 806 of the control transmission region 802 is demodulated and decoded at time 808, the TTI at time 816 2 The beamforming may be performed using the actual parameters collected from the demodulated and decoded second portion 806. There are no scheduling restrictions on the remainder of the data transmission region 818.

[0044] In an exemplary embodiment, the above-mentioned Figure 7 and Figure 8 Describes a combination of features. Fig. 99 is a flow chart illustrating a method 900 for processing incoming data transmission in mmWave communication according to an exemplary embodiment. The mmWave communication may include a control transmission portion and a data transmission portion. At operation 902, a determination is made as to whether scheduling restrictions should be applied to an earlier portion of the data transmission. If not, at operation 904, the scheduling restrictions are applied using the method described above with reference to FIG. Figure 7 Specifically, the control transmission part and the data transmission part are divided into sub-areas, and decoding and demodulation of the sub-areas of the control transmission part are performed before beamforming of the corresponding sub-areas of the data transmission part. If it is determined in operation 902 that the scheduling restriction should be applied to the earlier part of the data transmission, then in operation 906, the scheduling restriction is applied to the earlier part of the data transmission.

[0045] Fig.10 FIG. 2 is a diagram showing how the control transmission part and the data transmission part are divided into sub-areas in more detail according to an exemplary embodiment. Fig. 9 FIG. 10 is a flowchart of an embodiment of the present invention (operation 904 of the present invention). At operation 1000, a control transmission portion of mmWave communication is received. At operation 1002, the control transmission portion is divided into a plurality of control transmission portion sub-areas, each of which schedules data transmission for a corresponding sub-area of ​​the data transmission portion. Then, a loop is started for each control transmission portion sub-area. At operation 1004, the UE demodulates and decodes the control transmission portion sub-area. At operation 1006, the UE arranges receive analog antenna beamforming according to the demodulated and decoded control transmission portion sub-area. At operation 1008, the UE performs receive beamforming on the corresponding sub-area of ​​the data transmission portion. At operation 1010, it is determined whether there are more control transmission portion sub-areas. If so, the processing loops to operation 1004 of the next control transmission portion sub-area. If not, the process ends.

[0046] It should be noted that each aspect of the execution of the loop may be performed in parallel, so operations 1004-1010 are not necessarily performed in the order depicted. For example, when the UE is performing operations 1006 and 1008 for one control transmission portion sub-area, it may be performing (or may have performed) operation 1004 for a subsequent control transmission portion sub-area at the same time.

[0047] Fig.11 is a more detailed illustration of applying scheduling restrictions to an earlier portion of a data transmission portion according to an exemplary embodiment ( Fig. 9906 of the present invention). At operation 1100, a control transmission portion of a mmWave communication is received. At operation 1102, scheduling restrictions may be assigned to an earlier portion of the control transmission portion. These scheduling restrictions may indicate a delay time for beamforming to be performed on a corresponding earlier portion of the data transmission portion. At operation 1104, demodulation and decoding of an earlier portion and a later portion of the control transmission portion are started. At operation 1106, a data transmission portion of the mmWave communication is received. At operation 1108, beamforming of an earlier portion of the data transmission portion is performed using default parameters because the earlier portion of the data transmission portion is subject to scheduling restrictions of a corresponding earlier portion of the control transmission portion. These parameters may, for example, correspond to the parameters last reported by the UE for beamforming. At operation 1110, demodulation and decoding of a later portion of the control transmission portion of the mmWave communication is completed. At operation 1112, beamforming of a later portion of the data transmission portion is performed using parameters obtained from demodulating and decoding the later portion of the control transmission portion of the mmWave communication.

[0048] The decision as to which parts of the data transmission portion are categorized as "earlier portions" (and therefore have delays applied) can be based on the actual performance of the UE in demodulation and decoding. For example, a performance metric of the UE can be tracked to determine the average amount of time it takes to demodulate and decode a portion of the control transmission portion. The demarcation between the earlier portions (delayed) and the later portions (not delayed) can then be set based on this average amount of time (possibly with some padding) to ensure that the later portions of the data transmission portion are beamformed using information parameters from the demodulated and decoded corresponding control transmission portions, while minimizing the number of data transmission portions that are categorized as earlier portions (and therefore are subject to default parameters during beamforming). Return to reference Figure 8 , it can be seen that any TTI scheduled to be beamformed after time 808 may not have scheduling restrictions applied to it. As described above, time 808 may be determined a priori based on average demodulation and decoding times. Alternatively, time 808 may be determined dynamically at runtime such that when a particular portion of the control transmission portion is determined to have been demodulated and decoded, the corresponding portion of the data transmission portion is beamformed without scheduling restrictions, and any subsequent portions of the data transmission portion are also beamformed without scheduling restrictions.

[0049] The following figures are diagrams of processing systems that may be used to implement the apparatus and methods disclosed herein. A particular device may utilize all of the components shown, or only a subset of the components, and the degree of integration may vary from device to device.

[0050] Certain embodiments are described herein as including logical or multiple components, modules, or mechanisms. A module may constitute a software module (e.g., code implemented on a machine-readable medium) or a hardware module. A "hardware module" is a tangible unit that is capable of performing certain operations and that may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more computer systems (e.g., a stand-alone computer system, a client computer system, or a server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.

[0051] In some embodiments, the hardware module may be implemented mechanically, electronically, or in any appropriate combination thereof. For example, the hardware module may include dedicated circuits or logic that are permanently configured to perform certain operations. For example, the hardware module may be a dedicated processor, such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware module may also include programmable logic or circuits that are temporarily configured by software to perform certain operations. For example, the hardware module may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware module becomes a specific machine (or a specific component of a machine) that is specifically tailored to perform the configured functions rather than a general-purpose processor. It will be understood that the decision to mechanically implement the hardware module in a dedicated and permanently configured circuit or in a temporarily configured circuit (e.g., configured by software) may be driven by cost and time considerations.

[0052] Therefore, the phrase "hardware module" should be understood to include a tangible entity, i.e., an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner or perform certain operations described herein. As used herein, a "hardware-implemented module" refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), each hardware module does not need to be configured or instantiated at any one point in time. For example, in the case where the hardware module includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be configured as a special-purpose processor (e.g., including different hardware modules) that is different at different times. Therefore, the software configures a specific processor accordingly, for example, to constitute a specific hardware module at one point in time, and to constitute different hardware modules at different points in time.

[0053] Hardware modules can provide information to other hardware modules and receive information from other hardware modules. Therefore, the described hardware modules can be considered to be communicatively coupled. In the case of multiple hardware modules being present at the same time, communication can be achieved by signal transmission between two or more hardware modules (e.g., through appropriate circuits and buses). In an embodiment where multiple hardware modules are configured or instantiated at different times, communication between such hardware modules can be achieved, for example, by storing and retrieving information in a memory structure that multiple hardware modules can access. For example, a hardware module can perform an operation and store the output of the operation in a memory device that is communicatively coupled to it. Then, another hardware module can access the memory device at a later time to retrieve and process the stored output. The hardware module can also initiate communication with an input or output device and can operate on a resource (e.g., a collection of information).

[0054] The various operations of the exemplary methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, these processors may constitute processor-implemented modules that operate to perform one or more operations or functions described herein. As used herein, a "processor-implemented module" refers to a hardware module implemented using one or more processors.

[0055] Similarly, the methods described herein may be implemented at least in part by a processor, a particular processor or processors being examples of hardware. For example, at least some of the operations of the method may be performed by one or more processors or processor-implemented modules. In addition, one or more processors may also operate to support the performance of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some operations may be performed by a group of computers (as an example of a machine including a processor), which may be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., application program interface (API)).

[0056] The performance of certain operations may be distributed among the processors, not only residing within a single machine, but also deployed across multiple machines. In some exemplary embodiments, the processor or processor-implemented modules may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other exemplary embodiments, the processor or processor-implemented modules may be distributed across multiple geographic locations.

[0057] Machine and software architecture

[0058] In some embodiments, in combination Figure 1-11 The described modules, methods, applications, etc. are implemented in the context of a machine and associated software architecture. The following sections describe representative software architectures and machine (eg, hardware) architectures suitable for the disclosed embodiments.

[0059] Software architectures are used in conjunction with hardware architectures to create devices and machines that are tailored for specific purposes. For example, a specific hardware architecture combined with a specific software architecture will create a mobile device, such as a mobile phone, a tablet device, and the like. Slightly different hardware and software architectures may produce smart devices used in the "Internet of Things," while another combination produces a server computer used within a cloud computing architecture. Not all combinations of such software and hardware architectures are presented here, as one skilled in the art can readily understand how to implement the subject matter of the present invention in circumstances different from the disclosure contained herein.

[0060] Software Architecture

[0061] Fig.12 is a block diagram 1200 illustrating a representative software architecture 1202 that may be used in conjunction with the various hardware architectures described herein. Fig.12 The software architecture 1202 is merely a non-limiting example, and it should be understood that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1202 may be implemented in a variety of environments such as Fig.13 The machine 1300 is executed on hardware that includes, among other things, a processor 1310, memory / storage 1330, and I / O components 1350. Representative hardware layers 1204 are shown and may represent, for example, Fig.13 The representative hardware layer 1204 includes one or more processing units 1206 having associated executable instructions 1208. The executable instructions 1208 represent executable instructions of the software architecture 1202, including Figure 1-9 The hardware layer 1204 also includes a memory and / or storage module 1210 that also has executable instructions 1208. The hardware layer 1204 may also include other hardware 1212 that represents any other hardware of the hardware layer 1204, such as other hardware shown as part of the machine 1300.

[0062] exist Fig.12In the exemplary architecture of , the software architecture 1202 can be conceptualized as a stack of layers, where each layer provides specific functionality. For example, the software architecture 1202 may include layers such as an operating system 1214, a library 1216, a framework / middleware 1218, an application 1220, and a presentation layer 1244. In operation, the application 1220 and / or other components within the layer may call an application programming interface (API) call 1224 through the software stack and receive a message 1226 in response to the API call 1224, such as a response, a return value, etc. The layers shown are representative in nature, and not all software architectures 1202 have all layers. For example, some mobile or dedicated operating systems may not provide a framework / middleware 1218, while others may provide such a layer. Other software architectures may include additional or different layers.

[0063] The operating system 1214 can manage hardware resources and provide public services. The operating system 1214 can include, for example, a kernel 1228, services 1230, and drivers 1232. The kernel 1228 can act as an abstraction layer between the hardware and other software layers. For example, the kernel 1228 can be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, etc. The service 1230 can provide other public services to other software layers. The driver 1232 can be responsible for controlling or interfacing with the underlying hardware. For example, the driver 1232 can include a display driver, a camera driver, a Bluetooth driver, a flash driver, a serial communication driver (e.g., a Universal Serial Bus (USB) driver), a Wi-Fi driver, an audio driver, a power management driver, etc., depending on the hardware configuration.

[0064] Libraries 1216 may provide a common infrastructure that may be used by applications 1220 and / or other components and / or layers. Libraries 1216 generally provide functionality that allows other software modules to perform tasks in a simpler manner than directly interfacing with underlying operating system 1214 functionality (e.g., kernel 1228, services 1230, and / or drivers 1232). Libraries 1216 may include system libraries 1234 (e.g., C standard libraries) that may provide functionality such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, libraries 1216 may include API libraries 1236, such as media libraries (e.g., libraries that support rendering and manipulation of various media formats such as MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.), graphics libraries (e.g., OpenGL frameworks that may be used to render 2D and 3D in graphical content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The library 1216 may also include a variety of other libraries 1238 to provide numerous other APIs to the application 1220 and other software components / modules.

[0065] Framework / middleware 1218 (also sometimes referred to as middleware) may provide a higher level common infrastructure that may be used by applications 1220 and / or other software components / modules. For example, framework / middleware 1218 may provide various graphical user interface (GUI) capabilities, advanced resource management, advanced location services, etc. Framework / middleware 1218 may provide a wide range of other APIs that may be used by applications 1220 and / or other software components / modules, some of which may be specific to a particular operating system 1214 or platform.

[0066] Applications 1220 include built-in applications 1240 and / or third-party applications 1242. Representative examples of built-in applications 1240 may include, but are not limited to, a contact application, a browser application, a book reader application, a location application, a media application, a messaging application, and / or a game application. Third-party applications 1242 may include any of the built-in applications 1240 as well as a wide variety of other applications. In a specific example, third-party applications 1242 (e.g., applications created by an entity other than the vendor of a particular platform using Android TM or iOS TMThe application developed by the software development kit (SDK) can be mobile software running on a mobile operating system such as iOS™, Android™, Windows® Phone or other mobile operating systems. In this example, the third-party application 1242 can call API calls 1224 provided by the mobile operating system such as the operating system 1214 to facilitate the functions described herein.

[0067] Applications 1220 can utilize built-in operating system functionality (e.g., kernel 1228, services 1230, and / or drivers 1232), libraries (e.g., system libraries 1234, API libraries 1236, and other libraries 1238), and frameworks / middleware 1218 to create a user interface that interacts with a user of the system. Alternatively or additionally, in some systems, interaction with the user may occur through a presentation layer (such as presentation layer 1244). In these systems, the application / module "logic" may be separated from aspects of the application / module that interact with the user.

[0068] Some software architectures make use of virtual machines. Fig.12 In the example of , this is illustrated by virtual machine 1248. A virtual machine creates a software environment where applications / modules can be run as if they were on a hardware machine (e.g., Fig.13 The virtual machine 1248 is executed by the host operating system ( Fig.12 The software architecture 1202 is hosted by an operating system 1214 in a virtual machine 1248 and typically (although not always) has a virtual machine monitor 1246 that manages the operation of the virtual machine 1248 and interfaces with the host operating system (i.e., the operating system 1214). The software architecture 1202 is executed within the virtual machine 1248 such as an operating system 1250, libraries 1252, frameworks / middleware 1254, applications 1256, and / or a presentation layer 1258. These software architecture layers executed within the virtual machine 1248 may be the same as or may be different from the corresponding layers described previously.

[0069] Example machine architecture and machine-readable medium

[0070] Fig.13 is a block diagram illustrating components of a machine 1300 capable of reading instructions 1316 from a machine-readable medium (eg, a machine-readable storage medium) and executing any one or more of the methods discussed herein below, according to some exemplary embodiments. Specifically, Fig.13A diagrammatic representation of a machine 1300 in the example form of a computer system is shown in which instructions 1316 (e.g., software, a program, an application, an applet, an application, or other executable code) are used by the machine 1300 to perform any one or more of the methodologies discussed herein. For example, the instructions 1316 may cause the machine 1300 to perform Fig. 9 and 10 Additionally or alternatively, instruction 1316 may implement Figure 1-11 Modules, etc. Instructions 1316 convert a general non-programmed machine 1300 into a specific machine that is programmed to perform the functions described and shown in the described manner. In alternative embodiments, the machine 1300 operates as a standalone device, or can be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1300 can operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer (or distributed) network environment. The machine 1300 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a notebook, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a network device, a network router, a network switch, a network bridge, or any machine capable of executing instructions 1316, which specifies the actions to be taken by the machine 1300 in sequence or otherwise. Further, while a single machine 1300 is illustrated, the term "machine" shall also be taken to include any collection of machines 1300 that individually or jointly execute instructions 1316 to perform any one or more of the methodologies discussed herein.

[0071] The machine 1300 may include a processor 1310, a memory / storage 1330, and an I / O component 1350, which may be configured to communicate with each other, for example, via a bus 1302. In an exemplary embodiment, the processor 1310 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1312 and a processor 1314 that may execute instructions 1316. The term "processor" is intended to include multi-core processors 1312, 1314, which may include two or more independent processors 1312, 1314 (sometimes referred to as "cores") that may execute instructions 1316 simultaneously. Although Fig.13 Multiple processors 1310 are shown, and the machine 1300 may include a single processor 1312, 1314 with a single core, a single processor 1312, 1314 with multiple cores (e.g., a multi-core processor 1312, 1314), multiple processors 1312, 1314 with a single core, multiple processors 1312, 1314 with multiple cores, or any combination thereof.

[0072] The memory / storage 1330 may include a memory 1332, such as a main memory or other memory storage, and a storage unit 1336, both of which may be accessible to the processor 1310, for example, via the bus 1302. The storage unit 1336 and the memory 1332 store instructions 1316 that implement any one or more of the methods or functions described herein. During execution by the machine 1300, the instructions 1316 may also reside, in whole or in part, within at least one of the processors 1310 (e.g., within a cache memory of the processors 1312, 1314), or any suitable combination thereof. Thus, the memory 1332, the storage unit 1336, and the memory of the processor 1310 are examples of machine-readable media.

[0073] As used herein, a "machine-readable medium" refers to a device capable of temporarily or permanently storing instructions 1316 and data, and may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of memory (e.g., erasable programmable read-only memory (EEPROM)), and / or any suitable combination thereof. The term "machine-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) capable of storing instructions 1316. The term "machine-readable medium" should also be taken to include any medium or combination of multiple media capable of storing instructions (e.g., instructions 1316) executed by a machine (e.g., machine 1300) such that when instructions 1316 are executed by one or more processors of machine 1300 (e.g., processor 1310), the machine 1300 is caused to perform any one or more of the methods described herein. Thus, a "machine-readable medium" refers to both a single storage device or apparatus as well as a "cloud-based" storage system or storage network that includes multiple storage devices or apparatuses. The term "machine-readable medium" does not include the signal itself.

[0074] I / O components 1350 may include a wide variety of components for receiving input, providing output, generating output, sending information, exchanging information, capturing measurements, etc. The specific I / O components 1350 included in a particular machine 1300 will depend on the type of machine 1300. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine may not include such a touch input device. It should be understood that I / O components 1350 may be included in Fig.131350 are grouped according to function merely to simplify the following discussion, and the grouping is by no means limiting. In various exemplary embodiments, the I / O components 1350 may include output components 1352 and input components 1354. The output components 1352 may include visual components (e.g., displays such as plasma display panels (PDP), light emitting diode (LED) displays, liquid crystal displays (LCD), projectors, or cathode ray tubes (CRT), etc.), acoustic components (e.g., speakers), tactile components (e.g., vibration motors, resistor mechanisms), other signal generators, and the like. Input components 1354 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, touch pad, trackball, joystick, motion sensor, or other pointing instrument), tactile input components (e.g., physical buttons that provide location and / or force of a touch or touch gesture, a touch screen, or other tactile input components), audio input components (e.g., a microphone), and the like.

[0075] In further exemplary embodiments, the I / O component 1350 may include, among other components, a biometric component 1356, a motion component 1358, an environmental component 1360, or a position component 1362. For example, the biometric component 1356 may include a component for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweating, or brain waves), identifying a person (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1358 may include an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, a rotation sensor component (e.g., a gyroscope), etc. The environment component 1360 may include, for example, an illumination sensor component (e.g., a photometer), a temperature sensor component (e.g., one or more thermometers that detect ambient temperature), a humidity sensor component, a pressure sensor component (e.g., a barometer), an acoustic sensor component (e.g., one or more microphones that detect background noise), a proximity sensor component (e.g., an infrared sensor that detects nearby objects), a gas sensor (e.g., a gas detection sensor for detecting safe concentrations of hazardous gases or measuring pollutants in the air), or other components that may provide indications, measurements, or signals corresponding to the surrounding physical environment. The position component 1362 may include a position sensor component (e.g., a Global Position System (GPS) receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects atmospheric pressure, from which altitude can be derived), a direction sensor component (e.g., a magnetometer), and the like.

[0076] A wide variety of technologies may be used to implement communications. I / O components 1350 may include a communications component 1364 that is operable to couple machine 1300 to network 1380 or device 1370 via coupling 1382 and coupling 1372, respectively. For example, communications component 1364 may include a network interface component or other suitable device that interfaces with network 1380. In further examples, communications component 1364 may include a wired communications component, a wireless communications component, a cellular communications component, a nearfield communications (NFC) component, a Bluetooth® component (e.g., Bluetooth® Low Energy), a Wi-Fi® component, and other communications components that provide communications through other modes. Device 1370 may be another machine or any one of a number of peripheral devices (e.g., a peripheral device coupled via a universal serial bus (USB)).

[0077] In addition, the communication component 1364 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 1364 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as Universal Product Code (UPC) codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar codes, and other optical codes), or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 1364, such as location via Internet Protocol (IP) geolocation, location via Wi-Fi signal triangulation, location by detecting NFC beacon signals that may indicate a specific location, and the like.

[0078] Transmission medium

[0079] In various exemplary embodiments, one or more portions of network 1380 may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of a public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi network, another type of network, or a combination of two or more such networks. For example, network 1380 or a portion of network 1380 may include a wireless or cellular network, and coupling 1382 may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, coupling 1382 can implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, including the Third Generation Partnership Project (3GPP) of 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standards, other standards defined by various standards setting organizations, other long-range protocols, or other data transmission technologies.

[0080] Instructions 1316 may be sent or received using transmission media over network 1380 via a network interface device (e.g., a network interface component included in communication component 1364) and using any of a number of well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)). Similarly, instructions 1316 may be sent or received to device 1370 via coupling 1392 (e.g., a peer-to-peer coupling) using transmission media. The term "transmission medium" shall be deemed to include any intangible medium that is capable of storing, encoding, or carrying instructions 1316 for execution by machine 1300, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

[0081] language

[0082] Throughout the specification, multiple instances may implement components, operations or structures described as a single instance. Although the individual operations of one or more methods are shown and described as individual operations, one or more individual operations may be performed in parallel, and the operations do not need to be performed in the order shown. The structures and functions presented as individual components in the example configuration may be implemented as combined structures or components. Similarly, the structures and functions presented as individual components may be implemented as individual components. These and other changes, modifications, additions and improvements fall within the scope of the subject matter of this article.

[0083] Although an overview of the inventive subject matter has been described with reference to specific exemplary embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of the embodiments of the present disclosure. These embodiments of the inventive subject matter may be referred to herein, individually or collectively, as the term "invention" merely for convenience and without intending to limit the scope of the present application to any single disclosure or inventive concept, if more than one is actually disclosed.

[0084] The embodiments described herein are described in sufficient detail to enable those skilled in the art to practice the disclosed teachings. Other embodiments may be used and derived, so that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Therefore, the specific embodiments should not be considered restrictive, and the scope of the various embodiments is limited only by the appended claims and the full scope of equivalents granted by these claims.

[0085] As used herein, the term "or" may be interpreted in an inclusive or exclusive manner. In addition, multiple instances may be provided for the resources, operations, or structures described herein as a single instance. In addition, the boundaries between the various resources, operations, modules, engines, and data stores are somewhat arbitrary, and specific operations are shown in the context of a specific illustrative configuration. Other allocations of functionality are contemplated and may fall within the scope of various embodiments of the present disclosure. Typically, structures and functions presented as separate resources in an example configuration may be implemented as a combined structure or resource. Similarly, structures and functions presented as a single resource may be implemented as separate resources. These and other changes, modifications, additions, and improvements fall within the scope of embodiments of the present disclosure. Therefore, the specification and drawings are to be considered illustrative rather than restrictive.

Claims

1. A communication method, characterized in that: The method comprises: When a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is equal to or greater than a duration, receiving the PDSCH according to analog beamforming parameters carried by control information of the PDCCH; When a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is less than the duration, receiving the PDSCH according to a default analog beamforming parameter; The duration includes the time for demodulating and decoding the PDCCH to obtain the analog beamforming parameters and the time for applying the analog beamforming parameters.

2. The method according to claim 1, characterized in that The analog beamforming parameters are used for receiving beamforming, and the default analog beamforming parameters are used for receiving beamforming.

3. The method according to claim 1, characterized in that The default analog beamforming parameters are determined based on the analog beamforming information most recently reported by the terminal device.

4. The method according to any one of claims 1 to 3, characterized in that: The communication method is applied to millimeter wave (mmWave) communication.

5. The method according to claim 1, characterized in that The method further comprises: receiving a beamforming reference signal on a corresponding reference signal resource; Reporting the best beam pair information based on the measurement of the beamforming reference signal.

6. A communication device, characterized in that: The device comprises: a transceiver unit and a processing unit; The processing unit is configured to receive the PDSCH through the transceiver unit according to the analog beamforming parameters carried by the control information of the PDCCH when determining that the time gap between the reception of the physical downlink control channel PDCCH and the reception of the physical downlink shared channel PDSCH is equal to or greater than a duration; The processing unit is further configured to receive the PDSCH through the transceiver unit according to the default analog beamforming parameters when it is determined that the time gap between the reception of the physical downlink control channel PDCCH and the reception of the physical downlink shared channel PDSCH is less than the duration; The duration includes the time for demodulating and decoding the PDCCH to obtain the analog beamforming parameters and the time for applying the analog beamforming parameters.

7. The device according to claim 6, characterized in that The analog beamforming parameters are used for receiving beamforming, and the default analog beamforming parameters are used for receiving beamforming.

8. The device according to claim 6, characterized in that The default analog beamforming parameters are determined based on the analog beamforming information most recently reported by the terminal device.

9. The device according to any one of claims 6 to 8, characterized in that: The communication device is applied to millimeter wave (mmWave) communication.

10. The device according to claim 6, characterized in that The transceiver unit is further configured to receive a beamforming reference signal on a corresponding reference signal resource; The processing unit is further configured to measure the beamforming reference signal; The transceiver unit is further used to report the best beam pair information according to the measurement result measured by the processing unit.

11. The device according to any one of claims 6 to 8, characterized in that: The processing unit is a processor, the transceiver unit is a transceiver, and the device is a terminal device.

12. A communication method, characterized in that: The method comprises: When a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is equal to or greater than a duration, transmitting the PDSCH according to a transmit beam corresponding to an analog beamforming parameter carried by control information of the PDCCH; When a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is less than the duration, transmitting the PDSCH according to a transmit beam corresponding to a default analog beamforming parameter; The duration includes the time it takes for the terminal device to demodulate and decode the PDCCH to obtain the analog beamforming parameters and the time it takes to apply the analog beamforming parameters.

13. The method according to claim 12, characterized in that The analog beamforming parameters are used for receiving beamforming, and the default analog beamforming parameters are used for receiving beamforming.

14. The method according to claim 12, characterized in that The default analog beamforming parameters are determined based on the analog beamforming information most recently reported by the terminal device.

15. The method according to any one of claims 12 to 14, characterized in that: The communication method is applied to millimeter wave (mmWave) communication.

16. The method according to claim 12, characterized in that The method further comprises: Transmitting a beamforming reference signal on a corresponding reference signal resource; Receive the best beam pair information reported by the terminal device based on the measurement of the beamforming reference signal.

17. A communication device, characterized in that: The device comprises: a transceiver unit and a processing unit; The processing unit is configured to, when determining that a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is equal to or greater than a duration, transmit the PDSCH through the transceiver unit using a transmit beam corresponding to an analog beamforming parameter carried by control information of the PDCCH; The processing unit is further configured to, when determining that a time gap between receiving a physical downlink control channel PDCCH and receiving a physical downlink shared channel PDSCH is less than the duration, transmit the PDSCH through the transceiver unit according to a transmit beam corresponding to a default analog beamforming parameter; The duration includes the time it takes for the terminal device to demodulate and decode the PDCCH to obtain the analog beamforming parameters and the time it takes to apply the analog beamforming parameters.

18. The device according to claim 17, characterized in that The analog beamforming parameters are used for receiving beamforming, and the default analog beamforming parameters are used for receiving beamforming.

19. The device according to claim 17, characterized in that The default analog beamforming parameters are determined based on the analog beamforming information most recently reported by the terminal device.

20. The device according to any one of claims 17 to 19, characterized in that The communication device is applied to millimeter wave (mmWave) communication.

21. The device according to claim 17, characterized in that The transceiver unit is further used to transmit a beamforming reference signal on a corresponding reference signal resource; and receive optimal beam pair information reported by the terminal device based on measurement of the beamforming reference signal.

22. The device according to any one of claims 17 to 19, characterized in that The processing unit is a processor, the transceiver unit is a transceiver, and the device is a network device.

23. A communication device, characterized in that: The device comprises a processor, wherein the processor is used to be coupled to a memory, read a program in the memory, and control the communication device to implement the method according to any one of claims 1 to 5 and 12 to 16.

24. The device according to claim 23, characterized in that The communication device further comprises the memory.

25. The device according to claim 24, characterized in that The memory is arranged in the processor, or The memory is independently arranged from the processor.

26. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a computer, the method according to any one of claims 1 to 5 and 12 to 16 is implemented.

27. A computer program product comprising a computer program, characterized in that When the program is executed by a computer, the method according to any one of claims 1 to 5 and 12 to 16 is implemented.

Images