Communication method and device
By performing beam scanning at different cycles and setting a priority mechanism in the IoT system, the problem of high beam scanning overhead in base stations is solved, achieving high charging efficiency and scanning effect.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-26
- Publication Date
- 2026-03-27
AI Technical Summary
In IoT scenarios, the overhead of beam scanning performed by base stations is relatively large. How to balance the overhead of beam scanning with the charging efficiency is a current research problem.
By performing at least two beam scans of the first domain and then performing a beam scan of the second domain based on the scan results, different cycle durations are set to reduce overhead. A priority mechanism is used to ensure that the beam scan of the second domain is performed first in case of time conflicts, thus ensuring charging efficiency.
It effectively reduces beam scanning overhead while ensuring charging efficiency, thus improving both beam scanning performance and charging efficiency.
Smart Images

Figure CN121751183A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology
[0002] In the Internet of Things (IoT) scenario, IoT nodes are typically characterized by low cost and small size, but cannot carry large-capacity batteries, and also face the problem of short standby life. Therefore, wireless energy transfer (WPT) via base stations is one of the important ways to solve the short standby life of IoT nodes in the future. Specifically, the base station can first perform beam scanning to determine, based on feedback from the IoT node, which beam will provide the best charging efficiency for the IoT node. Then, the base station can send that beam to the IoT node to charge it.
[0003] However, the overhead of beam scanning performed by base stations is usually large. How to balance the overhead of beam scanning with the guarantee of charging efficiency is a problem that is currently being studied. Summary of the Invention
[0004] This application provides a communication method and apparatus to achieve both charging efficiency and beam scanning overhead.
[0005] To achieve the above objectives, this application adopts the following technical solution:
[0006] Firstly, a communication method is provided. This method can be executed by a network device, a component of the network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the network device. The method includes: performing at least two beam scans of a first domain, and, based on the scan results of the first domain beam scan, performing a beam scan of a second domain to determine a first beam, which is used for charging, based on the scan results of the second domain beam scan. The first domain differs from the second domain; the period of the beam scan in the first domain is a first cycle, and the period of the beam scan in the second domain is a second cycle, the duration of which is longer than the duration of the first cycle.
[0007] Therefore, network devices can set different cycle lengths according to different situations to perform different numbers of beam scans. For example, if the beam used for charging changes more slowly in the second domain, the duration of the second cycle can be longer than the duration of the first cycle. This allows the network device to perform fewer beam scans in the second domain, such as performing at least two beam scans in the first domain first, followed by one beam scan in the second domain. This reduces overhead, and because the beam changes relatively slowly, even if the cycle length is relatively long, the beam used for charging may not change within that duration, thus ensuring charging efficiency.
[0008] In one possible design, performing a beam scan in the second domain based on the scanning results of the beam scan in the first domain includes: when the beam scans in the first domain and the beam scans in the second domain overlap in time, performing a beam scan in the second domain based on the scanning results of the beam scan in the first domain.
[0009] Optionally, if the time of beam scanning in the first domain overlaps with that of beam scanning in the second domain, beam scanning in the second domain is performed based on the scanning result of beam scanning in the first domain, including: if the priority of beam scanning in the second domain is higher than that of beam scanning in the first domain, then beam scanning in the second domain is performed based on the scanning result of beam scanning in the first domain.
[0010] In other words, if the duration of the second cycle is longer than that of the first cycle, the second cycle may contain the first cycle, causing a time conflict, or time overlap, between the beam scanning of the first domain and the beam scanning of the second domain. In this case, the beam scanning of the second domain can be performed by defaulting to a higher priority, or by defining the beam scanning of the second domain as having a higher priority, to ensure the beam charging effect.
[0011] In one possible design, performing at least two beam scans of the first domain includes performing at least two beam scans of the first domain when the beam scans of the first domain and the beam scans of the second domain overlap in time. Specifically, if the beam scan of the second domain is defined as having a higher priority, the network device can perform a beam scan of the second domain by default in the event of a time overlap, to ensure that a beam scan of the second domain can be performed during the overall scanning process, thereby ensuring beam charging efficiency.
[0012] In one possible design, before performing at least two beam scans of the first domain, the method of the first aspect may further include: performing a beam scan of the second domain. To this end, performing at least two beam scans of the first domain includes: performing at least two beam scans of the first domain based on the scanning results of the beam scans of the second domain.
[0013] It can be seen that beam scanning in the first domain and beam scanning in the second domain can be performed based on each other's scanning results to achieve iterative execution of beam scanning in different domains, thereby further improving the beam scanning effect and thus further improving the charging efficiency.
[0014] Optionally, performing beam scanning in the second domain includes performing beam scanning in the second domain when the time of beam scanning in the first domain overlaps with that of beam scanning in the second domain.
[0015] Furthermore, in cases where the beam scans of the first and second domains overlap in time, the beam scan of the second domain is performed. This includes: if the priority of the beam scan of the second domain is higher than that of the beam scan of the first domain, then the beam scan of the second domain is performed. In other words, in cases of time conflict, by performing the beam scan of the second domain using either a default or defined priority method, a sufficient number of beam scans of the second domain can be performed during the overall scanning process, thereby ensuring beam charging efficiency.
[0016] Optionally, based on the scanning results of the second domain beam scan, at least two beam scans of the first domain are performed, including: if the beam scans of the first and second domains overlap in time, and if the priority of the first domain beam scan is higher than that of the second domain beam scan, then at least two beam scans of the first domain are performed based on the scanning results of the second domain beam scan. In other words, in the event of a time conflict, by defining a higher priority for the second domain beam scan, a sufficient number of second domain beam scans can be performed during the overall scanning process, thereby ensuring beam charging efficiency.
[0017] In one possible design, the second period is k times the first period, where k is an integer greater than 2. The time of the first p periods in the second period is configured to perform p beam scans of the first domain, and the time of the last q periods in the second period is configured to perform beam scans of the second domain, where p and q are positive integers, and p + q = k, so that the beam scans of the first and second domains can be performed in an orderly manner.
[0018] In one possible design, the method described in the first aspect may further include: performing a beam scan of a first domain and receiving first information feedback regarding the beam scan of the first domain, so as to perform a beam scan of a second domain based on the first information. That is, if the beam scan of the first domain is ineffective, the terminal device can instruct the user to switch to performing a beam scan of the second domain by feeding back the first information, so as to perform subsequent beam scans of the first domain based on the scanning results of the second domain, thereby ensuring the charging effect of the first domain.
[0019] In one possible design, the method described in the first aspect may further include: performing beam scanning in a first domain or a second domain, receiving first information feedback regarding the beam scanning in the first domain or the second domain, and stopping the beam scanning in the first domain and the second domain based on the first information. That is, if the terminal device does not need beam scanning, such as when the terminal device has finished charging, the terminal device can instruct the cessation of beam scanning by feeding back the first information to avoid wasting overhead by performing redundant beam scanning.
[0020] In one possible design, the method described in the first aspect may further include: sending configuration information indicating beam scanning configuration of the first domain and / or beam scanning configuration of the second domain.
[0021] Optionally, the configuration information also indicates the priority relationship between beam scanning in the first domain and beam scanning in the second domain, so that in the event of a time conflict between beam scanning in the first domain and beam scanning in the second domain, the terminal device can determine which type of beam scanning the network device is currently performing based on the priority relationship, so as to correspond to the received beam.
[0022] Optionally, the beam scanning configuration of the first domain includes at least one of the following: the duration of the first period, the starting time domain position of the first period, the time for performing beam scanning of the first domain within the first period, or the number of beams scanned in the first domain, so that the terminal device can align the time-frequency resources of the beam scanning of the first domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0023] Optionally, the beam scanning configuration of the second domain includes at least one of the following: the duration of the second period, the starting time domain position of the second period, the time for performing beam scanning of the second domain within the second period, or the number of beams scanned in the second domain, so that the terminal device can align the time-frequency resources of the beam scanning of the second domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0024] Optionally, the configuration information also indicates time-frequency resources for carrying the scanning results of beam scanning of the first domain, and / or time-frequency resources for carrying the scanning results of beam scanning of the second domain, so that the terminal device can feed back the corresponding scanning results on the time-frequency resources so that the network device can successfully receive the scanning results.
[0025] Secondly, a communication method is provided. This method can be executed by a terminal device, a component of the terminal device (e.g., a processor, chip, or chip system), or a logic node, logic module, or software capable of implementing all or part of the terminal device's functions. The method includes: receiving a beam group of a first domain transmitted by a network device; feeding back first information to the network device by measuring the beam group of the first domain, the first information instructing the network device to transmit a beam group of a second domain; receiving a beam group of the second domain from the network device; determining a first beam by measuring the beam group of the second domain, the first beam belonging to the beam group of the second domain; feeding back second information to the network device, the second information indicating the first beam, the first beam being used for charging.
[0026] In one possible design scheme, the first information is fed back to the network device by measuring the beam group of the first domain, including: measuring the beam group of the first domain to obtain the measurement result; and feeding back the first information to the network device when the measurement result meets the preset conditions.
[0027] Optionally, the measurement results satisfying preset conditions include at least one of the following: the signal strength of all beams in the beam group of the first domain is less than the signal strength threshold; the voltage used for charging of all beams in the beam group of the first domain is less than the voltage threshold; the current used for charging of all beams in the beam group of the first domain is less than the current threshold; the power used for charging of all beams in the beam group of the first domain is less than the power threshold; or the energy used for charging of all beams in the beam group of the first domain is less than the energy threshold.
[0028] In one possible design, the method described in the second aspect may further include: receiving configuration information from a network device, the configuration information indicating the configuration of a beam group in a first domain and / or the configuration of a beam group in a second domain.
[0029] Optionally, the configuration information also indicates the priority relationship between the beamgroups of the first domain and the beamgroups of the second domain.
[0030] Optionally, the configuration of the beam group in the first domain includes at least one of the following: the duration of the first period, the starting time-domain position of the first period, the time-domain position of the beam group in the first domain, or the number of beams in the beam group in the first domain; the configuration of the beam group in the second domain includes at least one of the following: the duration of the second period, the starting time-domain position of the second period, the time-domain position of the beam group in the second domain, or the number of beams in the beam group in the second domain.
[0031] Optionally, the configuration information also indicates the time-frequency resources used to carry information fed back from the terminal device to the network device.
[0032] Optionally, the configuration information may also indicate at least one of the above thresholds: signal strength threshold, voltage threshold, current threshold, power threshold, or energy threshold.
[0033] It is understandable that the technical effects of the method described in the second aspect can also refer to the relevant introduction of the method described in the first aspect above, and will not be repeated here.
[0034] Thirdly, a communication method is provided, which can be executed by a terminal device, a component of the terminal device (e.g., a processor, a chip, or a chip system), or a logic node, logic module, or software capable of implementing all or part of the functions of the terminal device. The method includes: receiving a beam group from a network device; and, when the energy of the terminal device meets preset conditions, feeding back first information to the network device, the first information instructing the network device to stop transmitting the beam group.
[0035] In one possible design, the energy of the terminal device meets the preset conditions, including at least one of the following: the energy of the terminal device reaches a preset energy value, or the energy of the terminal device is saturated.
[0036] Optionally, the beam group includes a beam group in a first domain and / or a beam group in a second domain. The period for the terminal device to receive the beam group in the first domain is a first period, and the period for the terminal device to receive the beam group in the second domain is a second period. The duration of the second period is longer than the duration of the first period.
[0037] In one possible design, the method described in the third aspect may further include: receiving configuration information from a network device, the configuration information indicating the configuration of a beam group in a first domain and / or the configuration of a beam group in a second domain.
[0038] Optionally, the configuration information also indicates the priority relationship between the beamgroups of the first domain and the beamgroups of the second domain.
[0039] Optionally, the configuration of the beam group in the first domain includes at least one of the following: the duration of the first period, the starting time-domain position of the first period, the time-domain position of the beam group in the first domain, or the number of beams in the beam group in the first domain; the configuration of the beam group in the second domain includes at least one of the following: the duration of the second period, the starting time-domain position of the second period, the time-domain position of the beam group in the second domain, or the number of beams in the beam group in the second domain.
[0040] Optionally, the configuration information also indicates the time-frequency resources used to carry information fed back from the terminal device to the network device.
[0041] Optionally, the configuration information also indicates the aforementioned preset energy value.
[0042] It is understandable that the technical effects of the method described in the third aspect can be referred to the relevant introduction of the method described in the first aspect above, and will not be repeated here.
[0043] Fourthly, a communication device is provided. This communication device is used to perform the communication method described in any implementation of the first or third aspect.
[0044] In this application, the communication device described in the fourth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the fourth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.
[0045] It should be understood that the communication apparatus described in the fourth aspect includes modules, units, or means that implement the communication method described in either the first or third aspect. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units for performing the functions involved in the aforementioned communication method.
[0046] Fifthly, a communication device is provided. The communication device includes a processor configured to execute the communication method described in any possible implementation of the first or third aspect.
[0047] In one possible design, the communication device described in the fifth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fifth aspect and other communication devices.
[0048] In one possible design, the communication device described in the fifth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the communication method described in either the first or third aspect.
[0049] In this application, the communication device described in the fifth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the fifth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.
[0050] A sixth aspect provides a communication device. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory, such that the communication device performs the communication method described in any possible implementation of the first or third aspect.
[0051] In one possible design, the communication device described in the sixth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the sixth aspect and other communication devices.
[0052] In this application, the communication device described in the sixth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the sixth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.
[0053] A seventh aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method described in any one of the first or third aspects.
[0054] In one possible design, the communication device described in the seventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.
[0055] In this application, the communication device described in the seventh aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the seventh aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.
[0056] Eighthly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading a computer program from the memory, executing a communication method as described in any implementation of the first or third aspect according to the computer program.
[0057] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.
[0058] In this application, the communication device described in the eighth aspect can be a terminal device, a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. Alternatively, the communication device described in the eighth aspect can be a network device, a component of a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.
[0059] A ninth aspect provides a processor. The processor is configured to execute the communication method described in any possible implementation of the first or third aspect.
[0060] A tenth aspect provides a communication system. The communication system includes a network device for performing the method described in the first aspect, and a terminal device for performing the method described in the second or third aspect.
[0061] Eleventhly, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, the computer causes the computer to perform the communication method described in any possible implementation of the first or third aspect.
[0062] In a twelfth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any possible implementation of the first or third aspect. Attached Figure Description
[0063] Figure 1 This is a schematic diagram of a wireless power transmission scenario.
[0064] Figure 2 A schematic diagram of the wireless power transfer process. Figure 1 ;
[0065] Figure 3 A schematic diagram of the wireless power transfer process. Figure 2 ;
[0066] Figure 4 Schematic diagram of the communication system architecture provided in the embodiments of this application Figure 1 ;
[0067] Figure 5 Schematic diagram of the communication system architecture provided in the embodiments of this application Figure 2 ;
[0068] Figure 6 Schematic diagram of the communication system architecture provided in the embodiments of this application Figure 3 ;
[0069] Figure 7 Schematic diagram of the communication system architecture provided in the embodiments of this application Figure 4 ;
[0070] Figure 8 This is a schematic diagram illustrating an application scenario of the communication system provided in the embodiments of this application;
[0071] Figure 9 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;
[0072] Figure 10 This application scenario illustrates the application scenarios of the communication method provided in the embodiments of this application. Figure 1 ;
[0073] Figure 11 This application scenario illustrates the application scenarios of the communication method provided in the embodiments of this application. Figure 2 ;
[0074] Figure 12 This is a flowchart illustrating the communication method provided in the embodiments of this application in an application scenario.
[0075] Figure 13 This application scenario illustrates the application scenarios of the communication method provided in the embodiments of this application. Figure 3 ;
[0076] Figure 14 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;
[0077] Figure 15 This application scenario illustrates the application scenarios of the communication method provided in the embodiments of this application. Figure 4 ;
[0078] Figure 16 Flowchart of the communication method provided in the embodiments of this application Figure 3 ;
[0079] Figure 17 This application scenario illustrates the application scenarios of the communication method provided in the embodiments of this application. Figure 5 ;
[0080] Figure 18 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;
[0081] Figure 19 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation
[0082] The technical solutions of this application embodiment can be applied to various communication systems, such as Wi-Fi wireless network systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.
[0083] The technical terms and related technical solutions in this application will be described below with reference to the accompanying drawings.
[0084] WPT:
[0085] With the development of wireless networks and the evolution of business needs, a massive number of IoT nodes exist in the network. These IoT nodes are low-cost and small in size, but cannot carry large-capacity batteries, resulting in short standby life. To solve this problem, many manufacturers have proposed using environmental energy harvesting methods to provide a continuous power source for IoT nodes. Radio frequency energy is one of the candidate energy sources, with advantages such as controllable energy amount and source, as well as certain penetration and relatively long transmission distance.
[0086] Current radio frequency (RF) energy harvesting solutions primarily focus on collecting radio electromagnetic waves present in the natural environment. However, due to the lack of matching and coordinated optimization of energy sources, the energy harvesting efficiency is extremely low, failing to meet the daily usage needs of IoT nodes. Observations show that cellular mobile communication networks have deployed numerous base stations. These base stations possess multiple antennas, capable of emitting arbitrarily designed electromagnetic waves and providing directional beams to enhance RF energy in certain directions, frequency bands, and time periods. This can significantly improve the low efficiency of energy transmission. Therefore, implementing wireless power transfer (WPT) through base stations is one of the important ways to address the short battery life issue in IoT devices in the future. WPT is also known as wireless power transfer, wireless charging, etc., and the specific terminology is not limited.
[0087] To improve charging efficiency, Multiple-Input Multiple-Output (MIMO) is considered an effective solution. Multi-antenna technology at the energy transmitter, through digital beamforming or so-called energy beamforming, helps to concentrate the transmitted wireless energy in the direction of the energy receiver. Meanwhile, multiple antennas at the energy receiver increase the effective area for harvesting received radio frequency energy, both contributing to a significant improvement in energy transmission efficiency. However, both transmitter and receiver beamforming technologies rely on channel state information (CSI).
[0088] There are roughly two ways to obtain CSI:
[0089] Method 1: The energy receiver (such as the energy transmission terminal) sends a reference signal, and the energy transmitter (such as the base station) performs channel estimation and uses the reciprocity of the channel to infer the CSI of the downlink channel from the CSI of the uplink channel. However, this method is usually applicable to time-division duplex (TDD) systems.
[0090] Method 2: The energy transmitter (e.g., a base station) sends a downlink reference signal, and the energy receiver (e.g., a power transfer terminal) performs channel estimation. However, this method requires additional baseband signal processing for channel estimation at the energy receiver. But low-cost power transfer terminals typically do not support baseband signal processing; for example, ... Figure 1 As shown, after receiving a radio frequency (RF) signal, the energy receiver can convert it into a direct current (DC) signal through a rectifier, and then use the DC signal to charge the rechargeable battery. Subsequently, the energy meter can feed back the battery's charge level to the energy transmitter via a backhaul link. It can be seen that the energy receiver does not have baseband signal processing capabilities, therefore, method 2 is difficult to implement for low-cost energy transfer terminals without baseband signal processing hardware. Furthermore, for energy transfer terminals with baseband signal processing hardware, high-power measurement operations are not suitable during the low-power (cold start) phase when the battery is insufficient to support the measurement. Therefore, a high-efficiency, low-power energy measurement feedback scheme needs to be designed.
[0091] To address the aforementioned technical issues, current technologies consider only feeding back the received signal strength and offer the following two solutions.
[0092] Option 1:
[0093] like Figure 2As shown, the base station can perform an initial beam scan on the terminal. The terminal determines one of the beams with a signal reception strength greater than a preset charging threshold as the initial beam and feeds back the information of that beam. The base station then uses that beam as the initial beam to charge the terminal. For example, the beam energy received by the terminal will increase its voltage value. If the voltage value is greater than a preset voltage threshold, the terminal will continuously send a wireless charging command to the base station. If the terminal feeds back the information of that beam, it will trigger the base station to use that beam to wirelessly charge the terminal.
[0094] In Scheme 1, the initial beam is the first beam whose received energy meets the preset threshold. It does not traverse all available beams, resulting in fast selection speed and low feedback overhead. However, it fails to guarantee that the most suitable beam can be selected in each beam scan, leading to low energy transfer efficiency. In addition, if the preset threshold is set unreasonable, there may be problems such as not finding a usable beam after scanning all beams.
[0095] Option 2:
[0096] like Figure 3 As shown, the terminal needs to determine the signal reception strength of each beam corresponding to the base station, and select the beam with a reception strength greater than a preset charging threshold as the first beam. Beam scanning stops when the scanning time exceeds a preset time threshold or when the number of first beams exceeds a preset quantity threshold. Then, the base station further determines an initial beam from the determined first beam and uses the initial beam for wireless charging.
[0097] In Scheme 2, a first beam is selected by setting a charging threshold, and then the beam with the strongest received signal strength is chosen as the initial beam. However, this approach has two drawbacks. First, the determination of the first beam is limited by time and quantity thresholds, meaning the determined maximum beam may not be the one with the highest energy transfer efficiency among all beams. Second, selecting the initial beam from the first beam requires storing the received signal strength corresponding to each beam in the first beam, which may not be supported by the hardware of a low-cost energy transfer terminal.
[0098] To address the aforementioned technical problems, this application proposes the following technical solutions. The technical solutions in this application will now be described in conjunction with the accompanying drawings.
[0099] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.
[0100] Furthermore, in the embodiments of this application, words such as "exemplarily" and "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as an "example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Rather, the use of the word "example" is intended to present the concept in a specific manner.
[0101] First, in this application, "for indicating" can include both direct and indirect indication. When describing "information" for indicating A, it can include whether the information directly indicates A or indirectly indicates A, but does not necessarily mean that the information carries A.
[0102] The information indicated by a given piece of information is called the information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as, but not limited to, directly indicating the information to be indicated, such as the information to be indicated itself or its index. It can also be indirectly indicated by indicating other information, where there is a relationship between the other information and the information to be indicated. It can also indicate only a part of the information to be indicated, while the other parts are known or pre-agreed upon. For example, the indication of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing the indication overhead to some extent. At the same time, common parts of various pieces of information can be identified and indicated uniformly to reduce the indication overhead caused by individually indicating the same information.
[0103] Furthermore, the specific indication method can also be any existing indication method, such as, but not limited to, the above-mentioned indication methods and their various combinations. Specific details of various indication methods can be found in existing technologies, and will not be repeated here. As described above, for example, when multiple pieces of information of the same type need to be indicated, the indication methods for different pieces of information may differ. In the specific implementation process, the required indication method can be selected according to specific needs. This application embodiment does not limit the selected indication method; therefore, the indication methods involved in this application embodiment should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated.
[0104] The information to be instructed can be sent as a whole or divided into multiple sub-information messages, and the sending period and / or timing of these sub-information messages can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device. This configuration information can include, for example, but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling, and physical layer signaling. MAC layer signaling includes, for example, a MAC control element (CE); physical (PHY) layer signaling includes, for example, downlink control information (DCI).
[0105] Second, in the embodiments shown below, the first, second, and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. For example, to distinguish different indication information.
[0106] Third, "pre-defined," "pre-configured," or "pre-specified" can be achieved by pre-saving corresponding codes, tables, or other means of indicating relevant information in the device (e.g., including terminal devices and network devices), or by pre-defining them in a protocol. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.
[0107] Fourth, the “protocol” involved in the embodiments of this application may refer to standard protocols in the field of communication, such as 3GPP’s LTE protocols (such as technical specification (TS) 36, i.e., the TS36 series of technical specifications), NR protocols (such as the TS38 series of technical specifications), and related protocols applied to future communication systems. This application does not limit this.
[0108] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0109] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0110] To facilitate understanding of the embodiments of this application, let's first take... Figure 4 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 4 This is a schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application applies.
[0111] Figure 4 This is a schematic diagram of the architecture of a communication system, which mainly includes: terminal devices and network equipment.
[0112] A terminal device can be a terminal with transceiver capabilities, a component of a terminal device (such as a processor, chip, or chip system), or a logical node, logical module, or software that can implement all or part of the functions of a terminal device. This terminal device can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminal devices in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, and roadside units with terminal functions. The terminal device in this application can also be an onboard module, onboard unit, onboard component, onboard chip, or onboard unit, which is built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in D2D communication. The embodiments of this application do not limit the device form of the terminal device. The device used to implement the terminal function can be a terminal device; it can also be a device that supports the terminal in implementing the function, such as a chip system. This device can be installed in the terminal or used in conjunction with the terminal.In this embodiment of the application, the chip system may be composed of chips or may include chips and other discrete devices.
[0113] Network equipment can be access network equipment. Access network equipment is also called radio access network (RAN) node, or network equipment with core network logical functions. RAN nodes can be 3GPP-related cellular systems, such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN nodes can also be open RAN (O-RAN or ORAN), cloud radio access network (CRAN), or wireless fidelity (WiFi) systems. RAN nodes can also be communication systems that integrate two or more of the above systems. RAN nodes are sometimes also called access network equipment, RAN entities, or access nodes, etc., and constitute part of the communication system to help terminals achieve wireless access. Multiple RAN nodes in a communication system can be nodes of the same type or nodes of different types.
[0114] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a Wi-Fi system. The RAN node can be a macro base station, a micro base station or indoor station, a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in V2X technology can be an RSU. All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions and corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions. The equipment form of RAN nodes can be pole stations, micro base stations, base stations, small stations, macro stations, etc., with no specific restrictions.
[0115] In another possible scenario, such as Figure 5As shown, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes implementing some of the base station's functions. For example, RAN nodes can be baseband units (BBUs) and radio units (RUs). BBUs and RUs may or may not be co-located. A BBU includes a central unit (CU) and a distributed unit (DU), which communicate via a midhaul link. The BBU communicates with the core network via a backhaul link, the DU communicates with the RU via a fronthaul link, and the RU communicates with at least one UE via an air interface. An integrated DU includes the functions of both the DU and RU.
[0116] Figure 6 This is a schematic diagram of a common RAN chip architecture, such as... Figure 6 As shown, the CU / DU hardware includes a chassis platform, motherboard, peripherals, and cooling system. The motherboard contains processing units, memory, internal I / O interfaces, and external connection ports. Its hardware accelerators are designed with interfaces, and hardware functional components include: storage for software, hardware, and system debugging interfaces, and a single-board management controller. DU systems are typically implemented using multi-core processors and one or more hardware accelerators. Parts of the DU protocol stack can be implemented in software running on a multi-core processor, with computationally intensive Layer 1 (L1) and Layer 2 (L2) functions offloaded to field-programmable gate array (FPGA) / graphics processing unit (GPU) hardware accelerators; or all L1 functions can be offloaded to FPGA / GPU-based hardware accelerators, while other protocol stack content is implemented in software running on the processor; or the entire protocol stack can be implemented in software running on the processor. The hardware accelerator supports interconnection with x86 or non-x86 processors. Similarly, the accelerator has a multi-channel high-speed serial computer expansion bus standard (PCIe) interface pointing to the central processing unit (CPU) and external connections via gigabit ethernet (GbE) connections.
[0117] The RU can comprise three parts: an O-RAN processing unit (OPU), a digital processing unit (DPU), and an RF processing unit. The OPU forwards Enhanced Common Public Radio Interface (eCPRI) frames and performs fronthaul interface operations, the lowest level L1 layer (coding, scrambling, modulation, layer mapping, precoding), synchronization, beamforming, and resource unit mapping. The OPU can be implemented as a CPU, FPGA, or application-specific integrated circuit (ASIC). The DPU performs synchronization, digital downconversion (DDC) in the uplink (UL), digital upconversion (DUC) in the downlink (DL), crest factor reduction (CFR), and digital pre-distortion (DPD), improving power amplifier efficiency by reducing the peak-to-average power ratio (PAPR) / adjacent channel leakage ratio (ACLR) of the RF front-end. The DPU can be implemented as an FPGA or ASIC. The O-RU's RF processing unit includes a transceiver module, up / down converters, power amplifiers (PA), low-noise amplifiers (LNA), and transmitter (Tx) / receiver (Rx) filters. All conversions between the analog and digital domains (such as digital-to-analog converters (DACs) and analog-to-digital converters (ADCs), RF sampling, frequency conversion using RF in up-conversion and down-conversion, and mixing of intermediate frequency (IF) and local oscillator (LO) are performed within the transceiver module. Physical and logical partitioning within the RF processing unit does not require specific boundaries.
[0118] In different systems, CU, DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU, DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.
[0119] In the ORAN system, RAN nodes communicate with the core network via backhaul links and with terminals via air interfaces. The ORAN system also includes RAN intelligent controllers (RICs), which can be further divided into non-real-time (Non-RT) RAN intelligent controllers and near-real-time (Near-RT) RAN intelligent controllers. The Non-RT RIC is used to implement non-real-time intelligent management of RAN functions and is located within the Service Management and Orchestration Framework (SMO) module. The Near-RT RIC is used to implement near-real-time intelligent management of the RAN, achieving near-real-time control and optimization of ORAN modules and resources through data collection and related operations on the E2 interface.
[0120] In the embodiments of this application, such as Figure 7 As shown, there are many ways to connect network devices and terminal devices. For example, network devices and terminals can have a point-to-point single connection, or a multi-hop single connection through a relay device, or a dual connection (DC), or a multi-hop multi-connection through a relay device, etc. There are no specific restrictions. As long as any network-side device in the cellular network can charge other devices, it is a network architecture that can be used by this invention.
[0121] In this communication system, the interaction between network devices and terminal devices can be applied to wireless communication / charging between communication devices. Wireless communication / charging between communication devices can include: wireless communication / charging between network devices and terminals, wireless communication / charging between network devices, and wireless communication / charging between terminals. In this embodiment, the term "wireless communication" can also be abbreviated as "communication," and can also be described as "data transmission" or "information transmission." The term "wireless charging" can also be abbreviated as "charging," "energy transfer," or "charging," and can also be described as "wireless energy transfer," "wireless charging," "wireless energy transmission," "radio frequency energy transmission," "radio frequency energy transfer," "radio frequency charging," "radio frequency charging," etc.
[0122] Specifically, network devices can set different period durations according to different situations to perform beam scans of different numbers in different domains. For example, taking a first domain and a second domain as an example, the first domain and the second domain are different; for example, the first domain can be the frequency domain and the second domain can be the spatial domain, or the first domain can be the spatial domain and the second domain can be the frequency domain. For ease of understanding, this application uses the example of the first domain being the frequency domain and the second domain being the spatial domain for illustration; other cases can be understood by referring to this example.
[0123] For example, when the mobility of the terminal device is limited, the change in the beam used to charge the terminal may be slower than the change in the spatial domain, which in turn is slower than the change in the frequency domain. Therefore, the network device can set (or predefine) the period of beam scanning in the first domain (i.e., the frequency domain) to be shorter than the period of beam scanning in the second domain (i.e., the spatial domain). This allows the network device to perform at least two beam scans in the first domain, and then, based on the results of these two scans, perform one beam scan in the second domain. The beam used to charge the terminal device is then determined based on the results of the second domain scan, and this beam is used to charge the terminal device. Since the number of beam scans in the second domain is relatively less than that in the first domain, beam scanning overhead is reduced. Furthermore, even if the period is relatively long, the beam used to charge the terminal device may not change during the relatively slower beam change period, thus ensuring charging efficiency.
[0124] The following is a description of the terms used in the embodiments of this application:
[0125] 1) Beam scanning in the first domain:
[0126] The first domain is the frequency domain. Beam scanning in the first domain can also be called frequency domain scanning, or frequency domain beam scanning. Specifically, it can involve the network device sending one beam from multiple beams to the terminal in multiple frequency domain units to determine the frequency domain unit containing the beam that powers the terminal device. The period of beam scanning in the first domain is the first period, meaning the network device can periodically perform beam scanning in the first domain. For example, as... Figure 8 As shown, the period of the first domain beam scan is T_f, meaning that the first domain beam scan is performed once every T_f time-domain units. T_f can be adjusted according to actual conditions. For example, if the channel fading in the frequency domain is slowly changing, the network device can set T_f to a larger value accordingly; conversely, if the channel fading in the frequency domain is rapidly changing, the network device can set T_f to a smaller value accordingly. The specific value can be set according to actual conditions, and this embodiment does not impose any restrictions.
[0127] 2) A time-domain unit can be any combination of one or more of the following: symbol, slot, subframe, frame, radio frame, or other time-domain resources / units of granularity, without specific restrictions. A time-domain unit can also be referred to as a time-domain resource. Taking a symbol as an example, a time-domain unit can contain one or more symbols, with no specific limit, and can be selected according to the actual situation. Multiple time-domain units can be predefined or pre-configured by the protocol, or multiple time-domain units can be dynamically determined by the network device. It can be understood that the positions of multiple time-domain units in the time domain can be continuous or non-contiguous, without specific restrictions; please refer to the relevant introduction below for details.
[0128] 3) A frequency domain unit can be any of the following: a subcarrier, a subcarrier group, a carrier, a carrier group, or other frequency domain resources of granularity, without specific limitations. Frequency domain unit can also be replaced with frequency domain resource. Taking a subcarrier as an example, a frequency domain unit can contain one or more subcarriers; the specific number is not limited and can be selected according to the actual situation. Multiple frequency domain units can be predefined or preconfigured by the protocol, or multiple frequency domain units can be dynamically determined by the network device. For example, the network device can determine which frequency bands / bandwidths / partial bandwidths the terminal supports through capability negotiation with the terminal, and then determine the corresponding frequency domain units from among them. It can be understood that the positions of multiple frequency domain units in the frequency domain can be continuous or non-contiguous, without specific limitations; please refer to the relevant introduction below for details.
[0129] 4) A beam can refer to a directional, special transmission effect formed by the transmitter of a network device through an antenna array. The beam can be a wide beam, a narrow beam, or other types of beams. The beamforming technology can be beamforming technology, such as digital beamforming, analog beamforming, or hybrid digital / analog beamforming, or other technologies, without specific limitations. It should be understood that "beam" is an exemplary term, and can be replaced by digital beam, analog beam, spatial domain filter, spatial filter, spatial parameter, transmission configuration index (TCI), TCI-state, etc.
[0130] 5) Multiple beams can be all the beams that a network device can shape. For example, suppose the antenna panel of a network device can shape 32 beams, and these 32 beams point in different directions in space. Multiple beams refer to these 32 beams; that is, during spatial scanning, the network device can scan all the beams once. Alternatively, multiple beams can also be a subset of the beams that a network device can shape. For example, the network device can select the beam pointing towards the terminal's location based on the terminal's position. Continuing with the above assumption, if 12 of the 32 beams point towards the terminal's location, then multiple beams refer to these 12 beams.
[0131] 6) Beam scanning in the second domain:
[0132] The second domain is the spatial domain. Beam scanning in the second domain can also be called spatial domain scanning, or spatial domain beam scanning. Specifically, it can involve the network device sending multiple beams to the terminal device in one of multiple frequency domain units to determine the beam that powers the terminal device from among the multiple beams. For details, please refer to the relevant introduction below, which will not be repeated here. The period of beam scanning in the second domain is the second period, meaning that the network device can periodically perform beam scanning in the second domain. For example, as... Figure 8 As shown, the period of the second domain beam scan is T_b, meaning that the second domain beam scan is performed once every T_b time domain units. T_b can be adjusted according to actual conditions. For example, if the terminal device has relatively weak mobility and the signal changes slowly in the spatial domain, the network device can set the duration T_b to be relatively large; conversely, if the terminal device has strong mobility and the signal changes quickly in the spatial domain, the network device can set the duration T_b to be relatively small. The specific value can be set according to actual conditions, and this application embodiment does not impose any restrictions.
[0133] It is understandable that due to the settings of the first and second cycles, there may be a time conflict between beam scanning of the first domain in a certain first cycle and beam scanning of the second domain in a certain second cycle. Therefore, network devices can determine whether to perform a beam scan of the first domain or the second domain within a certain time frame according to a certain strategy. For details, please refer to the relevant introduction below, which will not be repeated here. In other words, for two adjacent beam scans of the first or second domain, in the absence of a time conflict, the interval between them may be longer than the cycle length. In the absence of a time conflict, the interval length is the cycle length.
[0134] The above is a brief introduction to some terms used in the embodiments of this application. The specific process of beam scanning in the first and second domains of the above-described communication system is described below through method embodiments.
[0135] Figure 9 This is a flowchart illustrating a communication method provided in the embodiments of the application. This communication method can be applied to the aforementioned communication systems, such as interactions between a terminal device and a network device. The terminal device can be the terminal device itself, a component of the terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the terminal device's functions. For ease of understanding, the following method is described using a terminal device as an example. The network device can be the network device itself, a component of the network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the network device's functions. For ease of understanding, the following method is described using a network device as an example.
[0136] like Figure 9 As shown, the flow of this communication method is as follows:
[0137] S901, the network device performs at least two beam scans of the first domain.
[0138] Taking any one of the at least two beam scans in the first domain as an example, the specific process of that beam scan can be as follows:
[0139] During the first cycle, the network device can transmit the second beam of multiple beams to the terminal device on multiple frequency domain units. This second beam can be a preset beam; for example, if no beam scan of the second domain was performed before the current beam scan of the first domain, the current beam scan can use a protocol-defined or pre-configured beam, such as the second beam. Alternatively, the second beam can also be a beam determined by performing a beam scan of the second domain, such as the beam determined in the previous second domain beam scan.
[0140] In one possible implementation, the network device can continuously transmit the second beam to the terminal across multiple frequency domain units, and each second beam can be carried on a corresponding time domain unit, meaning the multiple transmissions of the second beam are sequential in time. For ease of understanding, as... Figure 10 As shown in (a), assuming multiple frequency domain units include frequency domain unit #1, frequency domain unit #2, frequency domain unit #3, and frequency domain unit #4, the network device transmits beam #1 in frequency domain unit #1 and time domain unit #1, then transmits beam #1 in frequency domain unit #2 and the next time domain unit #2 adjacent to time domain unit #1, then transmits beam #1 in frequency domain unit #3 and the next time domain unit #3 adjacent to time domain unit #2, and finally transmits beam #1 in frequency domain unit #4 and the next time domain unit #4 adjacent to time domain unit #3.
[0141] It is understood that "#1, #2, #3, etc." in the embodiments of this application are mainly used for differentiation; for example, time domain unit #1 represents one time domain unit, time domain unit #2 represents another time domain unit, and beam scan #1 represents a beam scan of the first domain / second domain executed once, while beam scan #2 represents another beam scan of the first domain / second domain executed once; for another example, scan result #1 represents the scan result of one beam scan, and scan result #2 represents the scan result of another beam scan. The relevant content below can be understood by reference and will not be repeated here.
[0142] Alternatively, in another possible implementation, the network device may also transmit the second beam to the terminal discontinuously across multiple frequency domain units; that is, the multiple transmissions of the second beam are not sequential in time. For ease of understanding, as... Figure 10 As shown in (b), the network device can transmit beam #1 in frequency domain unit #1 and time domain unit #1, then transmit beam #1 in frequency domain unit #2 and time domain unit #3 (one time domain unit apart from time domain unit #1), then transmit beam #1 in frequency domain unit #3 and time domain unit #5 (one time domain unit apart from time domain unit #3), and finally transmit beam #1 in frequency domain unit #4 and time domain unit #7 (one time domain unit apart from time domain unit #5). Of course, the above example uses a one-time-domain-unit interval and is not a limitation; it can also use several time domain units, and the number of time domain units between each two adjacent beam scans can also be different.
[0143] It is understood that the above example uses each second beam carried on a corresponding time-domain unit as an example, but it is not intended to be limiting. For example, the number of time-domain units where each second beam is located can be different, and the duration of each second beam can also be considered different, such as the duration of the first transmission being 1 time slot or symbol, and the duration of the second transmission being 2 time slots or symbols, etc. The specific duration can be selected by the network device according to the actual situation, or it can be directly defined by the protocol. This application embodiment does not impose specific limitations.
[0144] Additionally, the above example uses multiple consecutive frequency domain units, but these multiple frequency domain units can also be non-consecutive. For example, the network device transmits beam #1 in frequency domain unit #1 and time domain unit #1, then transmits beam #1 in frequency domain unit #3 (separated by one frequency domain unit from frequency domain unit #2) and time domain unit #2, then transmits beam #1 in frequency domain unit #5 (separated by one frequency domain unit from frequency domain unit #3) and time domain unit #3, and finally transmits beam #1 in frequency domain unit #7 (separated by one frequency domain unit from frequency domain unit #5) and time domain unit #4. Of course, the above example uses a one-frequency-domain-unit interval and is not a limitation; it can also use several frequency domain units as intervals, and the number of frequency domain units between each two adjacent beam scans can also be different.
[0145] The terminal device can perform multiple reception detections within the first cycle. For the terminal device, the time of the first cycle and the time-domain resources (or time units) for multiple reception detections can be predefined by the protocol or pre-configured by the network device; details can be found in the relevant descriptions below, and will not be repeated here. For example, the terminal device can perform signal detection on each time-domain unit containing the second beam to determine the signal strength on that time-domain unit, denoted as signal strength #1, and multiple signal strengths #1 can be determined. The signal strength can be represented by the reference signal receiving power (RSRP), or it can be represented in other ways, such as the strength / amplitude of the received signal, or the DC power stored after the received signal passes through a rectifier, without limitation. As another example, the terminal device can also use the energy received on each time-domain unit containing the second beam for charging to determine the charging result, denoted as charging result #1. Specifically, this could be the charging voltage, current, power, and quantity (or energy), and multiple charging results #1 can be determined.
[0146] It should be understood that the primary purpose of the terminal device receiving the beam is for power charging, such as collecting energy across the entire frequency band through an antenna. The terminal device may not need to know the frequency domain cell where the received beam resides, nor whether a beam scan is being performed in the first or second domain. Therefore, the network device may also not need to inform the terminal of the frequency domain cell where the beam resides, or whether a beam scan is being performed in the first or second domain. The terminal device can perform full-band reception detection at each time domain cell. Of course, if the terminal device needs to perceive the frequency domain cell where the beam resides, and whether a beam scan is being performed in the first or second domain, the network device can pre-configure this information for the terminal device. In this case, the terminal device can also perform reception detection at the frequency domain cell corresponding to each time domain cell.
[0147] The terminal device can feed back the scanning results of the beam scan in the first domain to the network device based on multiple signal strengths #1 and / or multiple charging results #1, denoted as scanning result #1. Scanning result #1 can be used to indicate the frequency domain information of the optimal beam, such as the first frequency domain unit. The first frequency domain unit is the frequency domain unit where the beam used to charge the terminal device is located, or in other words, the frequency domain unit where the optimal beam is located.
[0148] Scan result #1 implicitly indicates the first frequency domain unit by indicating which of the multiple reception detections by the terminal device was optimal. For example, if there are M frequency domain units, where M is an integer greater than 1, meaning the second beam is transmitted M times by the network device, it can also be considered that the terminal device performed M reception detections. Therefore, scan result #1 indicates that the x-th reception detection was optimal, and the frequency domain unit containing the beam of the x-th reception detection is the first frequency domain unit, thus implicitly indicating the first frequency domain unit. In one possible implementation, scan result #1 includes first information, which can be K1 bits of information, 2 K1 If the value is greater than or equal to M, for example, M=10, K1=4, the first information is 4 bits. 0000 indicates that the first reception detection was optimal, 0001 indicates that the second reception detection was optimal, and so on, with 1001 indicating that the tenth reception detection was optimal. Of course, if the terminal device knows which frequency domain unit the reception detection is performed in each time, the scan result #1 can also directly indicate the first frequency domain unit, such as the frequency value containing the first frequency domain unit.
[0149] In one possible approach, the terminal device can immediately report the scan result #1 to the network device after the beam scan of the first domain is completed. For example, the time domain unit where scan result #1 is located is the next time domain unit after the time domain unit of the last transmitted second beam among multiple second beams, to ensure the utilization of time domain resources. Alternatively, the terminal device can wait for a period of time after the beam scan of the first domain is completed before reporting the scan result #1 to the network device. Of course, the specific time domain resource on which the terminal device reports the scan result can be predefined by the protocol or preconfigured by the network device, as detailed in the relevant introduction below, and will not be elaborated further here. In addition, the specific frequency domain resource on which the terminal device reports the scan result can also be predefined by the protocol or preconfigured by the network device, as detailed in the relevant introduction below, and will not be elaborated further here.
[0150] After receiving scan result #1, the network device can send a second beam to the terminal device in the first frequency domain unit based on scan result #1. For example, if scan result #1 indicates that the x-th reception detection is optimal, the network device can determine that the x-th reception detection is the x-th second beam to be sent, and determine that the frequency domain unit containing the x-th second beam is the first frequency domain unit. During the remaining time of the first cycle, the network device can send the second beam to the terminal device in the first frequency domain unit. Correspondingly, the terminal device can receive the second beam to recharge.
[0151] S902, the network device performs a beam scan of the second domain (referred to as beam scan #1 of the second domain) based on the scanning results of the beam scan of the first domain.
[0152] In S902, the scanning result of the beam scan of the first domain can be recorded as scanning result #2. Scanning result #2 can be the scanning result of the last beam scan of the first domain among the above at least two beam scans of the first domain. If the beam scan of the first domain described in S901 is the last beam scan of the first domain, then scanning result #1 and scanning result #2 are the same scanning result.
[0153] Based on the scan result #2, the network device can determine the frequency domain unit. For ease of understanding, taking the frequency domain unit as the first frequency domain unit mentioned above as an example, the beam scan #1 process of the second domain can be as follows:
[0154] During the second cycle and in the first frequency domain unit, the network device can send multiple beams to the terminal device respectively.
[0155] In one possible implementation, the network device can continuously transmit multiple beams to the terminal device, and each beam can be carried on a corresponding time-domain unit, meaning the transmission of multiple beams is sequential in time. For ease of understanding, an example will be provided, such as... Figure 10 As shown in (c), assuming multiple beams include beam #1, beam #2, beam #3, and beam #4, the network device first transmits beam #1 in frequency domain unit #1 and time domain unit #1, then transmits beam #2 in frequency domain unit #1 and the next time domain unit #2 adjacent to time domain unit #1, then transmits beam #3 in frequency domain unit #1 and the next time domain unit #3 adjacent to time domain unit #2, and finally transmits beam #4 in frequency domain unit #1 and the next time domain unit #4 adjacent to time domain unit #3.
[0156] Alternatively, in another possible implementation, the network device may also send multiple beams to the terminal device discontinuously, meaning the transmission of multiple beams is not sequential in time. For example, as Figure 10 As shown in (d), assuming multiple beams include beam #1, beam #2, beam #3, and beam #4, the network device can transmit beam #1 in frequency domain unit #1 and time domain unit #1, then transmit beam #2 in frequency domain unit #1 and time domain unit #3 (which is one time domain unit away from time domain unit #1), then transmit beam #3 in frequency domain unit #1 and time domain unit #5 (which is one time domain unit away from time domain unit #3), and finally transmit beam #4 in frequency domain unit #1 and time domain unit #7 (which is one time domain unit away from time domain unit #5). Of course, the above example uses a one-time-domain-unit interval and is not a limitation; it can also use several time domain units, and the number of time domain units between each two adjacent beam scans can also be different.
[0157] It is understood that the above example uses each beam carried on a corresponding time-domain unit as an example, but it is not intended to be limiting. For example, the number of time-domain units where each beam is located can be different, and the duration of each beam can also be considered to be different, such as the duration of the first transmitted beam being one time slot or symbol, and the duration of the second transmitted beam being two time slots or symbols, etc. The specific duration can be selected by the network device according to the actual situation, or it can be directly defined by the protocol. This application embodiment does not impose specific limitations.
[0158] For the terminal device, similar to the first cycle described above, the duration of the second cycle and the time-domain resources (or time units) for multiple reception and detection by the terminal device can be predefined by the protocol or pre-configured by the network device. Please refer to the relevant descriptions below for details, which will not be repeated here. During the second cycle, the terminal device can also perform signal detection on each time-domain unit containing each beam to determine the signal strength on that time-domain unit, denoted as signal strength #2, with multiple signal strengths #2 determined. Alternatively, the terminal device can also use the energy received on each time-domain unit containing the beam for charging to determine the charging result, denoted as charging result #2, with multiple charging results #2 determined.
[0159] It should also be understood that, similar to beam scanning in the first domain, in beam scanning in the second domain, the network device may not need to inform the terminal of the frequency domain cell where the beam is located, or whether a beam scan of the first or second domain is being performed. Of course, if the terminal device needs to perceive the frequency domain cell where the beam is located, and whether a beam scan of the first or second domain is being performed, then the network device can pre-configure this information to the terminal device. In this case, the terminal device can also perform reception detection on the frequency domain cell corresponding to each time domain cell.
[0160] The terminal device can feed back the scanning result of beam scan #1 in the second domain to the network device based on multiple signal strengths #2 and / or multiple charging results #2, such as scanning result #3. Scanning result #3 can be used for the spatial information of the optimal beam, such as the beam indicated by the beam index in the spatial domain, such as the first beam. It also indicates that the first beam is the optimal beam in the spatial domain, that is, the beam that can be used for charging.
[0161] Scan result #3 implicitly indicates the first beam by indicating which of the multiple reception detections performed by the terminal device was optimal. For example, if there are N beams, where N is an integer greater than 1, it can be assumed that the terminal device performs N reception detections. Therefore, scan result #3 indicates that the y-th reception detection was optimal, and the beam detected in the y-th reception is the first beam, thus implicitly indicating the first beam. In one possible implementation, scan result #3 includes second information, which can be K² bits of information. K2 If N is greater than or equal to N, for example, M=6, K2=3, the second information is 3 bits: 000 indicates the first reception detection was optimal, 001 indicates the second reception detection was optimal, and so on, with 100 indicating the eighth reception detection was optimal. Of course, if the terminal device knows the index / identifier of the beam for each reception detection through pre-configuration or protocol pre-definition, then scan result #3 can also directly indicate the first beam, such as by including the index / identifier of the first beam.
[0162] It is understandable that the first piece of information and the second piece of information can be different information elements, or they can be the same information element, without any restrictions.
[0163] Specifically, the terminal device can immediately send back the scan result #3 to the network device after the beam scan #1 in the second domain is completed. For example, the time domain unit where the scan result #3 is located is the next time domain unit after the time domain unit of the last transmitted beam among multiple beams, to ensure the utilization of time domain resources. Alternatively, the terminal device can wait for a period of time after the beam scan #1 in the second domain is completed before sending back the scan result #3 to the network device. Of course, the specific time domain resource on which the terminal device sends back the scan result can be predefined by the protocol or preconfigured by the network device, as detailed in the relevant introduction below, and will not be repeated here. In addition, the specific frequency domain resource on which the terminal device sends back the scan result can also be predefined by the protocol or preconfigured by the network device, as detailed in the relevant introduction below, and will not be repeated here.
[0164] S903, the network device determines the first beam based on the scanning results of the beam scan of the second domain (scanning result #3 above).
[0165] The first beam is used for charging, or in other words, the first beam is the beam used for charging.
[0166] For example, if scan result #3 indicates that the y-th reception detection is optimal, the network device can determine that the y-th reception detection is the network device sending the first beam, i.e., determining the first beam. During the remaining time of the second cycle, the network device can send the first beam to the terminal device on the first frequency domain unit. Correspondingly, the terminal device can receive the first beam to recharge.
[0167] It is understandable that, during the period between the terminal device reporting scan result #3 and the next beam scan of the first domain, if no beam scan of the second domain is performed during this time (i.e., no new frequency domain unit is determined), the network device can continuously send the first beam to the terminal device on the first frequency domain unit to power the terminal device until the next beam scan of the first domain is performed. If a beam scan of the second domain is performed during this period and a new frequency domain unit is determined, then the network device can send the first beam to the terminal device on the new frequency domain unit until the next beam scan of the first domain is performed.
[0168] For ease of understanding, the following is a specific process to introduce S901-S903.
[0169] The above is an overall introduction to the S901-S903 process. The following section introduces some special cases in this process.
[0170] In this embodiment, if the first or second cycle is long enough, or if beam scanning of the first and second domains needs to be performed alternately to adjust the power transmission beam in a timely manner, the beam scanning of the first and second domains may overlap in time. If the beam scanning of the first and second domains overlaps in time, the network device can determine whether to perform beam scanning of the first or second domain during the overlapping time based on the priority relationship between the beam scanning of the first and second domains. Alternatively, it can default to performing beam scanning of the first or second domain during the overlapping time. The following describes the situation in conjunction with the above S901-S902.
[0171] Case 1: S901 is the first beam scan performed by the network device, and the beam scan of the second domain has a higher priority than the beam scan of the first domain.
[0172] For S901, when the beam scans of the first domain and the second domain overlap in time, the network device can perform at least two beam scans of the first domain, such as by default performing at least two beam scans of the first domain.
[0173] As an example, let's denote the first cycle as the small cycle and the second cycle as the large cycle, and so on. We'll take an example where one large cycle contains three small cycles. In the first small cycle, the beam scanning time of the first domain overlaps with the beam scanning time of the second domain. The network device performs a beam scan of the first domain once by default within the first small cycle. Then, the time allotted for the second and third small cycles within the first large cycle is for charging, which does not conflict with the beam scanning within the large cycle. Therefore, the network device performs another beam scan of the first domain within the second and third small cycles.
[0174] For S902, when the beam scans of the first domain and the second domain overlap in time, the network device can perform a beam scan #1 of the second domain based on scan result #2. For example, if the priority of the beam scan of the second domain is higher than the priority of the beam scan of the first domain, the network device can perform a beam scan #1 of the second domain based on scan result #2. Continuing the example above, in the fourth small cycle, when the time of the beam scan of the first domain overlaps with the time of the beam scan of the second domain, the network device can perform a beam scan #1 of the second domain in the fourth small cycle based on scan result #2 and the fact that the priority of the beam scan of the second domain is higher than the priority of the beam scan of the first domain. This process continues in the same manner, without further elaboration.
[0175] It can be seen that if the beam scanning of the second domain is defined as having a higher priority, the network device can execute the beam scanning of the second domain by default in the case of a certain time overlap, so as to ensure that the beam scanning of the second domain can be executed in the overall scanning process, so as to ensure the beam charging effect.
[0176] To make it easier to understand, we will use a specific scenario as an example below.
[0177] like Figure 11 As shown in (a), assuming the duration T_b of the large period is 18 time-domain units and the duration T_f of the small period is 6 time-domain units, i.e., T_b = 3 * T_f, the start times of the large and small periods are aligned. The beam scan in the first domain is a frequency domain scan, and the beam scan in the second domain is a spatial domain scan, with M = 2 and N = 3. Each scan (or each beam) occupies one time-domain unit. The specific process is as follows:
[0178] In the first sub-cycle, the spatial domain scan takes place from time domain unit #1 to time domain unit #3, and the frequency domain scan takes place from time domain unit #1 to time domain unit #2, resulting in a time conflict. The network device defaults to performing a frequency domain scan in the first sub-cycle. For example, it performs the first frequency domain scan in time domain units #1 to #2, receives the scan result from the terminal in time domain unit #3, and charges the terminal in time domain units #4 to #6 based on this result. For the second sub-cycle, the network device performs the second frequency domain scan in time domain units #7 to #8, receives the scan result from the terminal in time domain unit #9, and charges the terminal in time domain units #10 to #12 based on this result. For the third small cycle, the network device performs the third frequency domain scan in time domain units #13 to #14, receives the scan result fed back by the terminal for the third frequency domain scan in time domain unit #15, and charges the terminal in time domain units #16 to #18 according to the scan result.
[0179] Within the fourth sub-cycle, the spatial domain scan takes place from time domain units #19 to #21, and the frequency domain scan takes place from time domain units #19 to #20, resulting in a time conflict. The network device, prioritizing spatial domain scanning over frequency domain scanning, performs a spatial domain scan in the fourth sub-cycle. For example, the first spatial domain scan is performed in time domain units #19 to #21. The device then receives the scan result from the terminal regarding the first spatial domain scan in time domain unit #22 and, based on this result, powers the terminal in time domain units #23 to #24. This process continues in the same manner, without further elaboration.
[0180] Scenario 2: S901 is not the first beam scan performed by the network device, and the beam scan of the second domain has a higher priority than the beam scan of the first domain.
[0181] Prior to S901, the first beam scan that a network device could perform, such as a beam scan of the second domain, was denoted as beam scan of the second domain #2.
[0182] For example, when the beam scans of the first and second domains overlap in time, the network device can perform beam scan #2 of the second domain, if the priority of the second domain beam scan is higher than that of the first domain beam scan. As an example, consider a large period containing three small periods; other cases can be referenced. In the first small period, the beam scan times of the first and second domains overlap, and the network device performs beam scan #2 of the second domain within the first small period because the priority of the second domain beam scan is higher than that of the first domain beam scan.
[0183] For S901, the beam scanning time of the first domain does not overlap with the beam scanning time of the second domain. The network device can normally perform at least two beam scans of the first domain based on the scanning result of beam scan #2 of the second domain (referred to as scan result #4). Specifically, the network device can determine the second beam based on scan result #4, and use the second beam to perform at least two beam scans of the first domain. The specific principle of the network device determining the second beam is similar to that of determining the first beam, and can be understood by referring to it; it will not be repeated here. Continuing the example above, the time of the second and third small cycles within the first large cycle is the charging time, which does not conflict with the beam scanning within the large cycle. Therefore, within the second and third small cycles, the network device performs two beam scans of the first domain respectively based on scan result #4.
[0184] For S902, when the beam scans of the first domain and the second domain overlap in time, the network device can perform beam scan #1 of the second domain, if the priority of the beam scan of the second domain is higher than the priority of the beam scan of the first domain. Continuing the above example, if the time of the beam scan of the first domain overlaps with the time of the beam scan of the second domain in the first small cycle, the network device performs beam scan #1 of the second domain in the fourth small cycle, based on the higher priority of the beam scan of the second domain.
[0185] To make it easier to understand, we will use a specific scenario as an example below.
[0186] like Figure 11As shown in (b), assuming the duration T_b of the large cycle is 18 time-domain units and the duration T_f of the small cycle is 6 time-domain units, i.e., T_b = 3 * T_f, the start times of the large cycle and the small cycle are aligned, and M = 2, N = 3, each scan occupies one time-domain unit, and the specific process is as follows:
[0187] In the first sub-cycle, the spatial domain scan takes place from time domain units #1 to #3, and the frequency domain scan takes place from time domain units #1 to #2, resulting in a time conflict. The network device prioritizes the spatial domain scan over the frequency domain scan, performing the spatial domain scan in the first sub-cycle. For example, the first spatial domain scan is performed in time domain units #1 to #3. The device then receives the scan result from the terminal in time domain unit #4 and, based on this result, powers the terminal in time domain units #5 to #6. In the second sub-cycle, the network device performs the first frequency domain scan in time domain units #7 to #8, receives the scan result from the terminal in time domain unit #9, and, based on this result, powers the terminal in time domain units #10 to #12. For the third small cycle, the network device performs the second frequency domain scan in time domain units #13 to #14, receives the scan result fed back by the terminal for the second frequency domain scan in time domain unit #15, and charges the terminal in time domain units #16 to #18 according to the scan result.
[0188] Within the fourth sub-cycle, the spatial domain scan takes place from time domain units #19 to #21, and the frequency domain scan takes place from time domain units #19 to #20, resulting in a time conflict. The network device, prioritizing spatial domain scanning over frequency domain scanning, performs a spatial domain scan in the fourth sub-cycle. For example, it performs a second spatial domain scan in time domain units #19 to #21, receives the scan results from the terminal regarding the second scan in time domain unit #20, and then charges the terminal in time domain units #21 to #24 based on these results. This process continues thereafter.
[0189] Scenario 3: S901 is not the first beam scan performed by the network device, and the priority of beam scan in the first domain is higher than that of beam scan in the second domain.
[0190] Prior to S901, the first beam scan that a network device could perform, such as a beam scan of the second domain, was still referred to as beam scan of the second domain #2.
[0191] For example, if the beam scans of the first and second domains overlap in time, the network device can execute beam scan #2 of the second domain, as is the default. As an example, consider a large cycle containing three small cycles; other cases can be referenced. In the first small cycle, the beam scan times of the first and second domains overlap, and the network device defaults to executing beam scan #2 of the second domain in the first small cycle. Subsequently, the second and third small cycles are charging times within the first large cycle, which do not conflict with the beam scan within the large cycle, and the network device continues to execute beam scan of the first domain.
[0192] For S901, when the beam scans of the first domain and the second domain overlap in time, the network device can perform at least two beam scans of the first domain. For example, if the priority of the beam scan of the first domain is higher than the priority of the beam scan of the second domain, the network device can perform at least two beam scans of the first domain based on scan result #4. Scan result #4 can be referred to the relevant description above and will not be repeated here. Continuing the example above, in the fourth small cycle, the time of the beam scan of the first domain overlaps with the time of the beam scan of the second domain. Based on scan result #4 and the fact that the priority of the beam scan of the first domain is higher than the priority of the beam scan of the second domain, the network device can perform one beam scan of the first domain in the fourth small cycle. Afterwards, the fifth and sixth small cycles are charging times within the first large cycle, which do not conflict with the beam scans within the large cycle. Therefore, in the fifth and sixth small cycles, the network device performs two more beam scans of the first domain, respectively.
[0193] For S902, when the beam scan of the first domain overlaps with the beam scan of the second domain, the network device can perform beam scan #1 of the second domain, such as by default performing beam scan #2 of the second domain. The specific execution is similar to the above-mentioned execution of beam scan #2 of the second domain, which can be understood by reference and will not be repeated here.
[0194] It can be seen that, in the event of a time conflict, defining the beam scan of the second domain as having a higher priority ensures that a sufficient number of beam scans of the second domain are performed during the overall scanning process, thereby guaranteeing beam charging efficiency. Additionally, when the beam scan of the second domain is given a higher priority, the network device also needs to perform beam scans of the second domain by default at certain times.
[0195] To make it easier to understand, we will use a specific scenario as an example below.
[0196] like Figure 11As shown in (c), assuming the duration T_b of the large cycle is 18 time-domain units and the duration T_f of the small cycle is 6 time-domain units, i.e., T_b = 3 * T_f, the start times of the large cycle and the small cycle are aligned, and M = 2, N = 3, each scan occupies one time-domain unit, and the specific process is as follows:
[0197] In the first sub-cycle, the spatial domain scan takes place from time domain unit #1 to time domain unit #3, and the frequency domain scan takes place from time domain unit #1 to time domain unit #2, resulting in a time conflict. The network device defaults to performing a spatial domain scan in the first sub-cycle. For example, if the first spatial domain scan is performed in time domain units #1 to #3, the device receives the scan result from the terminal in time domain unit #4 and, based on this result, charges the terminal in time domain units #5 to #6. For the second sub-cycle, the network device performs the first frequency domain scan in time domain units #7 to #8, receives the scan result from the terminal in time domain unit #9, and, based on this result, charges the terminal in time domain units #10 to #12. For the third small cycle, the network device performs the second frequency domain scan in time domain units #13 to #14, receives the scan result fed back by the terminal for the second frequency domain scan in time domain unit #15, and charges the terminal in time domain units #16 to #18 according to the scan result.
[0198] In the fourth sub-cycle, the spatial domain scan takes place from time domain units #19 to #21, and the frequency domain scan takes place from time domain units #19 to #20, resulting in a time conflict. The network device, prioritizing frequency domain scanning over spatial domain scanning, performs a frequency domain scan within the fourth sub-cycle. For example, the third frequency domain scan is performed in time domain units #19 to #20. The device receives the scan result from the terminal regarding the third frequency domain scan in time domain unit #21 and, based on this result, powers the terminal in time domain units #22 to #24. For the fifth and sixth sub-cycles, the network device continues to perform frequency domain scans.
[0199] Within the 7th sub-cycle, the spatial domain scan takes place from time domain units #37 to #39, and the frequency domain scan takes place from time domain units #37 to #38, resulting in a time conflict. The network device defaults to performing a spatial domain scan in the 7th sub-cycle. For example, if a second spatial domain scan is performed in time domain units #37 to #39, the device receives the scan result from the terminal regarding the second spatial domain scan in time domain unit #40, and based on this result, charges the terminal in time domain units #41 to #42. This process continues thereafter.
[0200] It is understood that the above example assumes the start times of the large and small cycles are aligned, the large cycle is an integer multiple of the small cycle, and the duration of the small cycle is greater than the duration of the spatial domain scan. However, this is not a limitation. If the start times of the large and small cycles are not aligned, or the large cycle is not an integer multiple of the small cycle, or the duration of the small cycle is less than or equal to the duration of the spatial domain scan, some special situations may arise between the spatial domain scan and the frequency domain scan. For example, the time for a particular spatial domain scan and subsequent charging may overlap with the time of at least two small cycles. In this case, the network device can perform a spatial domain scan within these at least two small cycles and charge the terminal based on the scan results. Additionally, for this situation, the large cycle needs to be three times or more than three times the duration of the small cycle to ensure that there is still time available to perform a frequency domain scan within the large cycle.
[0201] To make it easier to understand, we will also use a specific scenario to illustrate this below.
[0202] like Figure 11 As shown in (d), assuming that the duration T_b of the large cycle is 18 time-domain units and the duration T_f of the small cycle is 6 time-domain units, i.e., T_b = 3 * T_f, M = 2, N = 7, and each scan occupies one time-domain unit, the specific process is as follows:
[0203] Within the first large cycle, the spatial domain scan takes place in time domain units #1 to #7, which is longer than the duration of a small cycle. Therefore, spatial domain scanning and charging can be performed during the first and second small cycles. For example, the network device performs the first spatial domain scan in time domain units #1 to #7, receives the scan result from the terminal in time domain unit #8, and charges the terminal in time domain units #9 to #12 based on the scan result. Then, for the third small cycle, the network device performs the first frequency domain scan in time domain units #13 to #14, receives the scan result from the terminal in time domain unit #15, and charges the terminal in time domain units #16 to #19 based on the scan result. This process continues in the same manner, without further elaboration.
[0204] It is understandable that the above example of setting beam scanning priority or selecting a default beam scan is merely one example. Network devices can also resolve time conflict issues by defining the order of beam scans in the first and second domains. For example, the second period is k times the first period, where k is an integer greater than 2. The time of the first p periods in the second period is configured to execute p beam scans of the first domain, and the time of the last q periods in the second period is configured to execute beam scans of the second domain, where p and q are positive integers, and p + q = k, so that beam scans in both the first and second domains can be executed in an orderly manner.
[0205] In summary, network devices can set different cycle lengths to perform different numbers of beam scans depending on the situation. For example, if the beam used for charging changes more slowly in the second domain, the duration of the second cycle can be longer than the duration of the first cycle. This allows the network device to perform fewer beam scans in the second domain, such as performing at least two beam scans in the first domain first, followed by one beam scan in the second domain. This reduces overhead, and because the beam changes relatively slowly, even if the cycle length is relatively long, the beam used for charging may not change within that duration, thus ensuring charging efficiency.
[0206] Optionally, in conjunction with the above S901-S903, the method further includes: the network device sending configuration information, and correspondingly, the terminal device receiving the configuration information.
[0207] The configuration information can indicate the beam scanning configuration of the first domain and / or the beam scanning configuration of the second domain.
[0208] The beam scanning configuration of the first domain may include at least one of the following: the duration of the first period, the starting time domain position of the first period, the time for performing beam scanning of the first domain within the first period, or the number of beams scanned in the first domain, so that the terminal device can align the time and frequency resources of the beam scanning of the first domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0209] The duration of the first period is the time interval between two beam scans in the first domain, denoted as T_f. The starting time-domain position of the first period can be understood as the start time of the beam scan in the first domain. The time for performing the beam scan in the first domain within the first period can include the time-domain position of each beam in the beam scan, specifically the index of the time-domain cell. It can be understood that during the beam scan in the first domain, the network device can transmit the same beam on different frequency domain cells, i.e., the same beam is transmitted multiple times. Therefore, it can be considered as transmitting a beam group, or the beam group of the first domain. Thus, the time-domain position of each beam can also be understood as the time-domain position of the beam group in the first domain. The number of beams scanned in the first domain can be the same as the number of multiple frequency domain cells, such as M mentioned above, which can also be understood as the number of beams in the beam group of the first domain. It should be understood that if the configuration information does not indicate the duration of the first cycle and the starting time domain position, the network device can also issue the time for executing the first domain beam scan before each execution of the first domain beam scan, that is, configure the corresponding time domain resources for each scan.
[0210] The beam scanning configuration of the second domain may include at least one of the following: the duration of the second period, the starting time domain position of the second period, the time for performing beam scanning of the second domain within the second period, or the number of beams scanned in the second domain, so that the terminal device can align the time-frequency resources of the beam scanning of the second domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0211] The duration of the second period is the time interval between two beam scans in the second domain, denoted as T_b. The starting time-domain position of the second period can be understood as the start time of the beam scan in the second domain. The time for performing the beam scan in the second domain within the second period can include the time-domain position of each beam in the beam scan, or specifically, the index of the time-domain cell. It can be understood that during the beam scan in the second domain, the network device can transmit multiple beams on the same frequency domain cell; these multiple beams can also be considered a beam group, such as the beam group in the second domain. Therefore, the time-domain position of each beam can also be understood as the time-domain position of the beam group in the second domain. The number of beams scanned in the second domain can be the same as the number of multiple beams, such as N mentioned above, which can also be understood as the number of beams in the beam group of the second domain. It should be understood that if the configuration information does not indicate the duration and starting time domain position of the second cycle, the network device can also issue the time for performing the second domain beam scan before each beam scan of the second domain, that is, configure the corresponding time domain resources for each scan.
[0212] Optionally, the configuration information can also indicate the priority relationship between beam scanning in the first domain and beam scanning in the second domain, or the priority relationship between beam groups in the first domain and beam groups in the second domain. For example, the configuration information can include priority information, which is 1 bit, where 0 indicates that the priority of beam scanning in the first domain is higher than that of beam scanning in the second domain, and 1 indicates that the priority of beam scanning in the second domain is higher than that of beam scanning in the first domain. Thus, when the terminal device determines, based on the period information and the beam scanning time, that the time of beam scanning in the first domain overlaps with that of beam scanning in the second domain, the terminal device can determine, based on the priority relationship, whether to receive the beam group in the first domain or the beam group in the second domain during that time. Of course, if the priority relationship between beam scanning in the first domain and beam scanning in the second domain is predefined by the protocol, then the configuration information does not need to indicate this.
[0213] Additionally, if the network device resolves timing conflicts by defining the order of beam scanning in the first and second domains, the configuration information can also indicate the order of beam scanning in the first and second domains. For example, the configuration information could include the p and q values mentioned above, indicating that the first p periods of the first cycle in the second period are configured for performing p beam scans of the first domain, and the last q periods of the second cycle are configured for performing beam scans of the second domain. Of course, if the order of beam scanning in the first and second domains is predefined by the protocol, then the configuration information does not need to indicate this order.
[0214] Optionally, for the initial beam scan, if the network device performs it in the default manner, the configuration information can also indicate whether the initial beam scan is a beam scan of the first domain or the second domain. For example, the configuration information can include information about the initial beam scan, such as 1 bit, where 0 indicates that the initial beam scan is a beam scan of the first domain, and 1 indicates that the initial beam scan is a beam scan of the second domain. Of course, if whether the initial beam scan is a beam scan of the first domain or the second domain is predefined by the protocol, then the configuration information does not need to indicate this.
[0215] Optionally, the configuration information may also indicate time-frequency resources (as denoted as first time-frequency resources) for carrying the scanning results of beam scanning of the first domain, and / or time-frequency resources (as denoted as second time-frequency resources) for carrying the scanning results of beam scanning of the second domain.
[0216] Taking the first time-frequency resource as an example, the second time-frequency resource can be understood with reference to the following:
[0217] For example, the configuration information may include the time-domain location information of the first time-frequency resource. The time-domain location information of the first time-frequency resource may be a time-domain offset, such as the time-domain offset relative to the end of beam scanning. The granularity of the time-domain offset may be a time-domain unit, such as how many time-domain units to offset. For example, a time-domain offset of 1 indicates the next time-domain unit after beam scanning ends, i.e., the immediate feedback of the scanning result mentioned above. Another example is a time-domain offset of 2, indicating waiting for one time-domain unit after beam scanning ends before feedback. The specific value of the time-domain offset can be selected according to the actual situation, and this application embodiment does not impose any limitations.
[0218] For example, the configuration information may also include the frequency domain location information of the first time-frequency resource. In one possible implementation, the frequency domain location information may be a frequency resource indicator value (FRIV) field, which may be used to indicate which sub-channels the frequency domain location of the first time-frequency resource is located in, as shown in equation (1).
[0219]
[0220] in, L represents the starting frequency domain cell in the frequency domain resource. subCH This refers to the number of frequency domain units occupied by the frequency domain resource.
[0221] Alternatively, the frequency domain location information of the first time-frequency resource can also be indicated by a frequency domain offset, such as the frequency domain offset relative to a frequency domain reference position predefined or preconfigured by a certain protocol.
[0222] Of course, if the time-frequency position of the first time-frequency resource is predefined by the protocol, then the configuration information does not need to be indicated.
[0223] It should also be understood that if the time-domain offsets of the first and second time-frequency resources are the same, such as when the next time-domain cell is fed back after the beam scan is completed, then the time-domain position information of the first and second time-frequency resources can also be the same information, such as offset = 1.
[0224] For ease of understanding, the following is a specific process to introduce S901-S904.
[0225] like Figure 12 As shown, in a specific scenario, the terminal device mentioned above is a UE, and the network device mentioned above is a gNB. The specific process is as follows:
[0226] S1201, gNB sends configuration information to UE.
[0227] The configuration information indicates the beam scanning configuration of the first and second domains, the time-frequency position of the first time-frequency resource, and the priority relationship between the beam scanning of the first domain and the beam scanning of the second domain. For details, please refer to the relevant introduction of S904.
[0228] S1202, gNB sends M beams #1 to UE.
[0229] In the first cycle T_f, a frequency domain scan is performed. The gNB sends beam #1 to the UE on M frequency domain elements, for a total of M beams #1. Beam #1 can be an initially preset beam.
[0230] S1203, the UE feeds back frequency domain unit x to the gNB.
[0231] S1204, gNB sends beam #1 to UE on frequency domain unit x.
[0232] S1204 is used to charge the UE.
[0233] S1205, gNB sends M beams #1 to UE.
[0234] In the second second cycle T_f, gNB continues to perform frequency domain scanning, such as sending beam #1 to UE on M frequency domain units, for a total of M beams #1.
[0235] S1206, the UE feeds back the frequency domain unit y to the gNB.
[0236] S1207, gNB sends beam #1 to UE in frequency domain unit y.
[0237] S1207 is used to charge the UE.
[0238] It is understandable that S1202-S1207 can also refer to the relevant introduction of S901 above, and will not be repeated here.
[0239] S1208, gNB sends N beams to UE in frequency domain unit y.
[0240] During the third second cycle T_f, the gNB performs a spatial scan, such as sending N beams to the UE in frequency domain cell y. Beam #1 also belongs to the N beams.
[0241] S1209, UE feeds back beam #2 to gNB.
[0242] Beam #2 is the charging beam.
[0243] S1210, gNB sends beam #2 to UE in frequency domain unit y.
[0244] S1210 is used to charge the UE.
[0245] It is understandable that S1208-S1210 can also refer to the relevant introductions of S902-S903 mentioned above, and will not be repeated here.
[0246] And so on, without further explanation.
[0247] It is understood that the solutions in the embodiments of this application have the following technical effects:
[0248] like Figure 13 As shown in (a), to improve the power transfer efficiency of wireless power transfer terminals, it is necessary to determine the optimal beam based on feedback from both the spatial and frequency domains. Therefore, the base station can perform a global scan in both the spatial and frequency domains, such as performing a full-spatial beam scan of all frequency domain units within the power transfer frequency band in a specific order. Figure 13As shown by the dashed line #2 in (b) of the diagram, the power transfer efficiency after a global scan is relatively high. However, the disadvantage of global scanning is its long scan time, and if a mechanism requiring feedback from the terminal for each scan is adopted, the number of terminal feedbacks is also high, and the energy consumed by feedback is also high. In other words, global scanning cannot balance scan latency and overhead. Alternatively, the network device can fix a certain frequency domain unit and perform full-space beam scanning on that frequency domain unit, thereby reducing the number of scans and ensuring scan latency and overhead. However, as... Figure 13 As shown by the dashed line #1 in (b) of the diagram, the disadvantage of this scheme is its relatively low energy transfer efficiency. Based on this, since the scheme in this embodiment can not only perform frequency domain scanning and spatial domain scanning, but also reduces the number of spatial domain scans by setting the period size, in this case, as shown... Figure 13 As shown by the solid line in (b) in the figure, both scanning overhead and energy transfer efficiency can be achieved.
[0249] Optionally, in conjunction with the above S901-S903, the method of this application embodiment may also have other processes, such as... Figure 14 As shown, the method also includes:
[0250] S1401, the network device performs beam scanning of the first domain, and the terminal device receives the beam group of the first domain sent by the network device.
[0251] The network device performs beam scanning of the first domain by sending the beam group of the first domain to the terminal device, which can then receive the beam group of the first domain. Beam scanning of the first domain can be the initial scan or any scan after the initial scan; there are no specific restrictions. The specific implementation principle of beam scanning of the first domain can be found in the relevant description of S901 above, and will not be repeated here.
[0252] S1402, the terminal device feeds back first information to the network device by measuring the beam group of the first domain.
[0253] In S1402, the first information can instruct the network device to send the beam group of the second domain, or in other words, instruct the network device to perform a beam scan of the second domain or to perform a global scan.
[0254] For example, the first information in S1402 can be the same as the first information in S901. For instance, in S1602, the first information can be a special value, such as denoted as the first value. Taking the first information as 4 bits, the first value can be a reserved value used to indicate values outside the beam, such as 1111, to indicate that the feedback content does not indicate a specific beam, but rather instructs the network device to send a beam group of the second domain. Alternatively, the first information in S1402 and the first information in S901 can be different information, such as independent handshake information, or other forms, without limitation.
[0255] The terminal device can measure the beamgroup of the first domain and obtain measurement results. These measurement results may include at least one of the following: the signal strength of the beamgroup of the first domain (e.g., the signal strength of each beam), the voltage used for charging the beamgroup of the first domain, the current used for charging the beamgroup of the first domain, the power used for charging the beamgroup of the first domain, or the energy used for charging the beamgroup of the first domain, etc. If the measurement results meet preset conditions, the terminal device feeds back first information to the network device.
[0256] For example, the measurement results meeting preset conditions may include at least one of the following: the signal strength of all beams in the beamgroup of the first domain is less than a signal strength threshold; the voltage used for charging of all beams in the beamgroup of the first domain is less than a voltage threshold; the current used for charging of all beams in the beamgroup of the first domain is less than a current threshold; the power used for charging of all beams in the beamgroup of the first domain is less than a power threshold; or the energy used for charging of all beams in the beamgroup of the first domain is less than an energy threshold. These thresholds are pre-configured by the network device. The configuration information may also indicate at least one of the above thresholds: a signal strength threshold, a voltage threshold, a current threshold, a power threshold, or an energy threshold. Alternatively, the terminal device may determine these thresholds itself without specific limitations.
[0257] S1403, the network device performs beam scanning of the second domain according to the first information, and correspondingly, the terminal device receives the beam group of the second domain from the network device.
[0258] The network device performs a beam scan in the second domain by sending a beam group of the second domain to the terminal device, which can then receive the beam group. This second-domain beam scan can be performed once or multiple times by the network device. For example, the network device can perform a second-domain beam scan on a specific frequency unit, or on every frequency unit; that is, the network device can perform only a second-domain beam scan or a full-domain scan. It should be understood that the network device can perform a second-domain beam scan immediately, without considering the second cycle, starting immediately after receiving the first information, or it can perform the second-domain beam scan according to the time interval of the second cycle; there are no specific restrictions.
[0259] For full-domain scanning, if the network device has pre-deployed the full-domain scanning configuration to the terminal device, such as the beam scanning order of the first and second domains, the number of beams in the full-domain scan, the start time of the full-domain scan, and the time-frequency position of the terminal device's feedback for the full-domain scan, or if the full-domain scanning configuration is predefined by the protocol, then the network device can directly execute the full-domain scan. Otherwise, the network device can first send the full-domain scan configuration to the terminal device and then execute the full-domain scan. Furthermore, the same principle applies to beam scanning of the second domain, and will not be elaborated further.
[0260] It should be understood that the specific implementation principle of beam scanning in the second domain can also be referred to the relevant introduction of S902 above, and will not be repeated here.
[0261] S1404, the terminal device determines the first beam by measuring the beam group of the second domain.
[0262] The first beam belongs to the beam group of the second domain. The first beam is used for charging. When the network device performs a full domain scan, the terminal device can also determine the frequency domain unit where the first beam is located, such as the first frequency domain unit. The specific implementation principle can be referred to the relevant introduction of S902-S903 above, and will not be repeated here.
[0263] S1405, the terminal device sends the second information back to the network device.
[0264] The second information can be used to indicate the first beam. When the terminal device determines the first frequency domain unit, the second information can also be used to indicate the first frequency domain unit. The specific implementation principle can be referred to the relevant introduction of S902-S903 above, and will not be repeated here.
[0265] As can be seen, during beam scanning in the first domain, it is possible that none of the beams scanned within that domain reach the activation voltage. If none of the beams can charge the terminal device, the terminal device cannot calculate the energy of each beam, or it can be understood that the energy collected under each beam is 0 (or close to 0). Therefore, the terminal device cannot compare and provide feedback on the optimal beam. In this case, the terminal device can intervene in or release the subsequent beam scanning scheme by feeding back a special code, such as a first value, to adjust and correct the entire beam scanning process in a timely manner, thereby determining the beam that can be used for charging and ensuring the subsequent charging effect.
[0266] To make it easier to understand, we will use a specific scenario as an example below.
[0267] like Figure 15 As shown, assuming M=2 and N=3, each scan occupies one time-domain unit, and the specific process is as follows:
[0268] The network device performs a frequency domain scan in the first small cycle, such as performing a first frequency domain scan in time domain units #1 to #2, and receiving the scan result fed back by the terminal for the first frequency domain scan in time domain unit #3. This scan result indicates a first value. Based on the first value, the network device determines to switch to a full-domain scan. The network device performs a full-domain scan in time domain units #4 to #9, such as transmitting beams #1 to #3 in frequency domain unit #1 and in time domain units #4 to #6 respectively, and transmitting beams #1 to #3 in frequency domain unit #2 and in time domain units #7 to #9 respectively. The network device receives the scan result fed back by the terminal device for the full-domain scan in time domain unit #10, such as frequency domain unit #2 and beam #2. The network device transmits beam #2 to the terminal device in frequency domain unit #2 for charging, and the duration of this charging is not limited in this embodiment. Subsequently, the network device can perform beam scanning of the first and second domains sequentially, following a large-cycle and a small-cycle pattern, as detailed above. Figure 9 The relevant information will not be repeated here.
[0269] Optionally, in conjunction with the above S901-S903, the method of this application embodiment may also have other processes, such as... Figure 16 As shown, the method also includes:
[0270] S1601, the network device performs beam scanning of the first or second domain, and the terminal device receives beam groups from the network device.
[0271] Specifically, the network device performs beam scanning of the first domain or the second domain by sending beam groups of the first domain and / or the second domain to the terminal device. The terminal device can then receive the beam groups, which may include beam groups of the first domain and / or beam groups of the second domain. The specific implementation principle can be referred to the relevant introductions in S901-S902 above, and will not be repeated here.
[0272] S1602, if the terminal device's energy meets preset conditions, it feeds back first information to the network device. The network device receives the first information fed back by beam scanning for the first domain or the second domain.
[0273] The energy of the terminal device meeting the preset conditions can include at least one of the following: the energy of the terminal device reaches a preset energy value, or the energy of the terminal device is saturated. The preset energy value can be pre-configured by the network device, such as the configuration information mentioned above, or it can be determined by the terminal device itself; there are no specific limitations.
[0274] In S1602, the first message can instruct the network device to stop transmitting beam groups.
[0275] In S1602, the first information can be the same as the first information in S901. For example, in S1602, the first information can be a special value, such as the second value. Taking the first information as 4 bits, the second value can be a reserved value used to indicate something other than the beam, such as 1110, to indicate that the feedback does not indicate a specific beam, but rather indicates to stop beam scanning in the first and second domains. Alternatively, the first information in S1602 can be different from the first information in S901, such as independent handshake information, or other forms, without limitation. Or, the terminal device may not send feedback, implicitly indicating to perform beam scanning in the first and second domains.
[0276] It is understandable that if the first information in S1602 and the first information in S1402 both reuse the same information, then the first value and the second value need to be distinguished, such as the first value being 1111 and the second value being 1110.
[0277] S1603, the network device stops performing beam scanning of the first and second domains based on the first information.
[0278] It can be seen that during beam scanning in the first or second domain, there may be a situation where the terminal device has sufficient power. In this case, the terminal device can stop subsequent beam scanning by feeding back a special code, such as a second value, and the relevant time and frequency resources can be released for communication use to improve communication capacity.
[0279] like Figure 17 As shown in the diagram, assuming the duration T_b of the large cycle is 12 time-domain units and the duration T_f of the small cycle is 6 time-domain units, i.e., T_b = 3 * T_f, the start times of the large cycle and the small cycle are aligned, and M = 2, N = 3, each scan occupies one time-domain unit, and the specific process is as follows:
[0280] In the first sub-cycle, the spatial domain scan takes place from time domain unit #1 to time domain unit #3, and the frequency domain scan takes place from time domain unit #1 to time domain unit #2, resulting in a time conflict. The network device performs a frequency domain scan in the first sub-cycle, performing the first frequency domain scan in time domain units #1 to #2. It then receives the scan results from the terminal in time domain unit #3 and, based on these results, charges the terminal in time domain units #4 to #6. For the second sub-cycle, the network device performs a second frequency domain scan in time domain units #7 to #8, receives the scan results from the terminal in time domain unit #9, and, based on these results, charges the terminal in time domain units #10 to #12. During the third small cycle, the network device performs a spatial scan, such as performing a first spatial scan in time domain units #13 to #15, and receiving the scan result from the terminal for the first spatial scan in time domain unit #16. This scan result indicates the second value. Based on the second value, the network device determines to stop performing both spatial and frequency domain scans. Time domain unit #16 and subsequent time domain units are then used for communication.
[0281] The following is combined with Figure 5 The process of the method of the embodiments of this application in the ORAN scenario is described.
[0282] Step 1-1: The core network can send beam scanning commands to the access network devices via the backhaul link. The beam scanning command includes request information and the contents of the aforementioned configuration information, such as the beam scanning configuration of the first domain, the beam scanning configuration of the second domain, and the first and second time-frequency resources. Additionally, it may include the number of cycles, i.e., the number of scans. The request information can be used to request beam scanning. The access network device's CU receives the beam scanning command; alternatively, the CU may not receive the beam scanning command from the core network, i.e., step 1-1 is optional.
[0283] Step 1-2: The CU sends a beam scanning command to the DU.
[0284] Steps 1-3: The DU sends a beam scanning command to the RU via the fronthaul link. The RU sends a beam to the UE to perform beam scanning, that is, to perform a beam scan for a certain period, such as a beam scan of the first domain or a beam scan of the second domain.
[0285] Steps 1-4: The terminal device receives the beam and feeds back the scanning results at the specified time-frequency location (i.e., the first time-frequency resource or the second time-frequency resource mentioned above).
[0286] Steps 1-5: The RU receives the scan results from the terminal device, downconverts the scan results, and then sends them back to the DU for further processing.
[0287] Steps 1-6: The DU processes the received baseband signal and transmits the processed scan results to the CU via the mid-pass link.
[0288] Steps 1-7: The CU continues to perform beam scanning for the next cycle, repeating steps 1-3 to 1-6 until the specified number of cycles, i.e. the number of iterations, is reached. The CU obtains the spatial domain information (such as the beam index) and frequency domain information (such as the frequency domain cell) of the optimal beam.
[0289] Steps 1-7: The CU can return the spatial and frequency domain information of the optimal beam to the core network, or it can choose not to return specific information, such as directly returning an indication that the scan is complete, or it can choose not to return any information to the core network equipment and directly send the optimal beam to power the terminal.
[0290] Steps 1-8: If the core network receives information from the CU, such as the spatial and frequency domain information of the optimal beam, the core network can send a charging command to the CU based on the information fed back by the CU. After receiving the command, the CU sends it to the RU through the midhaul and fronthaul, and the RU sends the optimal beam according to the charging command to charge the terminal.
[0291] It is understood that the beam scanning involving the first and second domains in steps 1-1 to 1-8 above can also refer to the relevant descriptions in S901-S903 above, and will not be repeated here. Additionally, regarding the above... Figure 14 and Figure 16 The method shown can also be applied to ORAN scenarios. For details, please refer to steps 1-1 to 1-8 above. It will not be repeated here.
[0292] It should also be understood that requesting beam scanning from the access network equipment via the core network, or having the CU actively trigger beam scanning, and completing the terminal beam scanning through cooperation between the CU / DU / RU, and finally, charging the power supply using the spatial and frequency information of the optimal beam based on the scanning results, helps improve charging efficiency. The number of scans (or iterations at this point) can be determined by the core network or the access network. When the core network issues configuration information, the DU can determine the spatial and frequency information of the power transmission signal based on the configuration information and the processing status of the baseband signal, thereby improving power transmission efficiency.
[0293] The following is combined with Figure 6 The present application describes the process of the method in the chip architecture of the embodiments.
[0294] Step 2-1: The core network sends beam scanning commands to the access network equipment via the backhaul link. For details, please refer to the relevant description in Step 1-1, which will not be repeated here. The CU of the access network equipment receives the beam scanning commands. The CU includes an x86 or ARM architecture CPU and FPGA / GPU / other accelerator chips. The x86 type chip or the ARM-based chip processes the beam scanning commands from the core network. Some of the underlying logical operations, such as simple summation, are handled by the FPGA / GPU / other accelerator. After processing, the result is fed back to the CPU, which performs further control operations, such as determining whether to send control commands to the DU. The interface between the CPU and the FPGA / GPU / other accelerator can be PCIe. Alternatively, the CU may not receive beam scanning commands from the core network, i.e., Step 1-1 is optional.
[0295] Step 2-2: The CU sends a beam scanning command to the DU, and the DU receives the scan command. The DU also includes an x86 or ARM architecture CPU and FPGA / GPU / other accelerator chips; the x86 or ARM-based chip processes the request command from the CU. Some of the underlying logical operations, such as simple summation, are handled by the FPGA / GPU / other accelerator. After processing, the result is fed back to the CPU, which then performs further control operations, such as determining whether to send a control command to the RU. The interface between the CPU and the FPGA / GPU / other accelerator can be PCIe.
[0296] Steps 2-3: The DU sends a beam scanning command to the RU via the fronthaul link. The RU includes a fronthaul processing unit (FSU) for processing indication signaling from the DU. The FSU can be a CPU or a dedicated chip, such as an FPGA / ASIC chip. Based on the DU's instructions, the FSU schedules the digital signal processing module for processing. The digital signal processing module performs operations including FFT, modulation and demodulation, etc. The digital signal processing module triggers the RF processing model for processing, as in step 2-4.
[0297] Steps 2-4: The RF processing module performs a beam scan for a specific cycle, such as a beam scan of the first domain or the second domain, and receives the scan results fed back by the terminal device. The RF processing module's processing mainly includes down-conversion and spectrum splicing / shifting operations. After processing the scan results, the RF processing module feeds them back to the DU through the digital signal processing module and the fronthaul processing unit.
[0298] Steps 2-5: The DU processes the received baseband signal and transmits the processed scanning result to the CU through the mid-pass link.
[0299] Steps 2-6: The CU continues to scan the beam for the next cycle, repeating steps 2-2 to 2-6 until the number of iterations is reached, at which point the CU obtains the spatial and frequency domain information of the optimal beam.
[0300] Steps 2-7: The CU can return the spatial and frequency domain information of the optimal beam to the core network, or it can choose not to return specific information, such as directly returning an indication that the scan is complete, or it can choose not to return any information to the core network equipment and directly send the optimal beam to power the terminal.
[0301] Steps 2-8: If the core network receives information from the CU, such as the spatial and frequency domain information of the optimal beam, the core network can send a charging command to the CU based on the information fed back by the CU. After receiving the command, the CU sends it to the RU through midhaul and fronthaul. The RU then sends the optimal beam according to the charging command to charge the terminal.
[0302] It is understood that the beam scanning involving the first and second domains in steps 2-1 to 2-8 above can also refer to the relevant descriptions in S901-S903 above, and will not be repeated here. Additionally, regarding the above... Figure 14 and Figure 16 The method shown can also be applied to ORAN scenarios. For details, please refer to steps 2-1 to 2-8 above. It will not be repeated here.
[0303] It is understandable that the collaboration between different chips within the access network equipment—for example, the CPU primarily controls logic decisions, the accelerator handles simple parallel calculations, and the digital processing chip specializes in digital signal processing—improves efficiency. This chip collaboration enables an efficient beam scanning process, thereby enhancing power transmission efficiency. Furthermore, in addition to performing beam scanning, the chips in the access network equipment also need to specify the number of cycles and the time-frequency positions of relevant time-frequency resources, and analyze the scanning results fed back by the terminal device to ultimately determine the optimal spatial and frequency domain information of the beam.
[0304] Figure 18 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 For example, such as Figure 18 As shown, the communication device 1800 includes a transceiver module 1802 and a processing module 1801. For ease of explanation, Figure 18 Only the main components of the communication device are shown.
[0305] In one possible implementation, the communication device 1800 can be used to achieve the above. Figure 9 , Figure 14 or Figure 16 The function of the network device in the method shown.
[0306] For example, processing module 1801 controls transceiver module 1802 to perform at least two beam scans of the first domain. Processing module 1801 is also used to control transceiver module 1802 to perform a beam scan of the second domain based on the scanning results of the first domain beam scan, and to determine the first beam based on the scanning results of the second domain beam scan. The first beam is used for charging. The first domain differs from the second domain; the period of the beam scan in the first domain is a first cycle; the period of the beam scan in the second domain is a second cycle, and the duration of the second cycle is longer than the duration of the first cycle.
[0307] In one possible design, the processing module 1801 is used to control the transceiver module 1802 to perform beam scanning in the second domain based on the scanning result of the beam scanning in the first domain when the beam scanning in the first domain overlaps with the beam scanning in the second domain.
[0308] Optionally, the processing module 1801 is configured to, when the beam scanning of the first domain and the beam scanning of the second domain overlap in time, if the priority of the beam scanning of the second domain is higher than the priority of the beam scanning of the first domain, control the transceiver module 1802 to perform the beam scanning of the second domain according to the scanning result of the beam scanning of the first domain.
[0309] In one possible design, the processing module 1801 is used to control the transceiver module 1802 to perform at least two beam scans of the first domain when the beam scans of the first domain and the second domain overlap in time.
[0310] In one possible design, the processing module 1801 controls the transceiver module 1802 to perform a beam scan of a second domain before performing at least two beam scans of the first domain. To this end, the processing module 1801 is also configured to control the transceiver module 1802 to perform at least two beam scans of the first domain based on the scanning results of the beam scan of the second domain.
[0311] Optionally, the processing module 1801 is used to control the transceiver module 1802 to perform beam scanning in the second domain when the beam scanning in the first domain overlaps with the beam scanning in the second domain.
[0312] Furthermore, the processing module 1801 is configured to control the transceiver module 1802 to perform beam scanning in the second domain if the beam scanning in the second domain has a higher priority than the beam scanning in the first domain when the beam scanning in the first domain overlaps with the beam scanning in the second domain.
[0313] Optionally, the processing module 1801 is configured to, when the beam scanning of the first domain overlaps with the beam scanning of the second domain, if the priority of the beam scanning of the first domain is higher than the priority of the beam scanning of the second domain, control the transceiver module 1802 to perform at least two beam scans of the first domain based on the scanning result of the beam scanning of the second domain.
[0314] In one possible design, the second period is k times the first period, where k is an integer greater than 2. The time of the first p periods in the second period is configured to perform p beam scans of the first domain, and the time of the last q periods in the second period is configured to perform beam scans of the second domain, where p and q are positive integers, and p + q = k, so that the beam scans of the first and second domains can be performed in an orderly manner.
[0315] In one possible design, the processing module 1801 controls the transceiver module 1802 to perform beam scanning in the first domain, the transceiver module 1802 receives first information feedback from the beam scanning in the first domain, and the processing module 1801 controls the transceiver module 1802 to perform beam scanning in the second domain based on the first information.
[0316] In one possible design, the processing module 1801 controls the transceiver module 1802 to perform beam scanning in a first domain or a second domain, the transceiver module 1802 receives first information feedback on the beam scanning of the first domain or the second domain, and the processing module 1801 controls the transceiver module 1802 to stop performing beam scanning of the first domain and the second domain according to the first information.
[0317] In one possible design, the transceiver module 1802 is also used to send configuration information indicating the beam scanning configuration of the first domain and / or the beam scanning configuration of the second domain.
[0318] Optionally, the configuration information also indicates the priority relationship between beam scanning in the first domain and beam scanning in the second domain, so that in the event of a time conflict between beam scanning in the first domain and beam scanning in the second domain, the terminal device can determine which type of beam scanning the network device is currently performing based on the priority relationship, so as to correspond to the received beam.
[0319] Optionally, the beam scanning configuration of the first domain includes at least one of the following: the duration of the first period, the starting time domain position of the first period, the time for performing beam scanning of the first domain within the first period, or the number of beams scanned in the first domain, so that the terminal device can align the time-frequency resources of the beam scanning of the first domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0320] Optionally, the beam scanning configuration of the second domain includes at least one of the following: the duration of the second period, the starting time domain position of the second period, the time for performing beam scanning of the second domain within the second period, or the number of beams scanned in the second domain, so that the terminal device can align the time-frequency resources of the beam scanning of the second domain with the network device, so that the terminal device can receive the beam at the corresponding time domain position.
[0321] Optionally, the configuration information also indicates time-frequency resources for carrying the scanning results of beam scanning of the first domain, and / or time-frequency resources for carrying the scanning results of beam scanning of the second domain, so that the terminal device can feed back the corresponding scanning results on the time-frequency resources so that the network device can successfully receive the scanning results.
[0322] Optionally, the transceiver module 1802 may include a transmitting module ( Figure 18 (not shown in the image) and receiving module ( Figure 18 (Not shown in the diagram). The transmitting module is used to implement the transmitting function of the communication device 1800, and the receiving module is used to implement the receiving function of the communication device 1800.
[0323] Optionally, the communication device 1800 may also include a storage module. Figure 18 (Not shown in the image), the storage module stores programs or instructions. When the processing module 1801 executes the program or instructions, the communication device 1800 can perform the aforementioned... Figure 9 , Figure 14 or Figure 16 The method shown describes the functions of the network device.
[0324] It is understood that the communication device 1800 may be a network device, or a component of a network device (such as a processor, chip, or chip system), or a logical node, logical module, or software that can implement all or part of the functions of a network device. This application does not limit this.
[0325] In another possible implementation, the communication device 1800 can be used to achieve the above. Figure 14 The function of the terminal device in the method shown.
[0326] The transceiver module 1802 is used to receive beam groups of a first domain sent by the network device; the processing module 1801 is used to control the transceiver module 1802 to feed back first information to the network device by measuring the beam groups of the first domain, the first information instructing the network device to send beam groups of a second domain; the transceiver module 1802 is used to receive beam groups of the second domain from the network device; the processing module 1801 is used to determine a first beam by measuring the beam groups of the second domain, the first beam belonging to the beam groups of the second domain; the transceiver module 1802 is used to feed back second information to the network device, the second information indicating the first beam, the first beam being used for charging.
[0327] In one possible design, the processing module 1801 measures the beam group of the first domain and obtains the measurement results; if the measurement results meet the preset conditions, it controls the transceiver module 1802 to feed back the first information to the network device.
[0328] Optionally, the measurement results satisfying preset conditions include at least one of the following: the signal strength of all beams in the beam group of the first domain is less than the signal strength threshold; the voltage used for charging of all beams in the beam group of the first domain is less than the voltage threshold; the current used for charging of all beams in the beam group of the first domain is less than the current threshold; the power used for charging of all beams in the beam group of the first domain is less than the power threshold; or the energy used for charging of all beams in the beam group of the first domain is less than the energy threshold.
[0329] In one possible design, the transceiver module 1802 is further configured to receive configuration information from the network device, the configuration information indicating the configuration of the beam group of the first domain and / or the configuration of the beam group of the second domain.
[0330] Optionally, the configuration information also indicates the priority relationship between the beamgroups of the first domain and the beamgroups of the second domain.
[0331] Optionally, the configuration of the beam group in the first domain includes at least one of the following: the duration of the first period, the starting time-domain position of the first period, the time-domain position of the beam group in the first domain, or the number of beams in the beam group in the first domain; the configuration of the beam group in the second domain includes at least one of the following: the duration of the second period, the starting time-domain position of the second period, the time-domain position of the beam group in the second domain, or the number of beams in the beam group in the second domain.
[0332] Optionally, the configuration information also indicates the time-frequency resources used to carry information fed back from the terminal device to the network device.
[0333] Optionally, the configuration information may also indicate at least one of the above thresholds: signal strength threshold, voltage threshold, current threshold, power threshold, or energy threshold.
[0334] Optionally, the transceiver module 1802 may include a transmitting module ( Figure 18(not shown in the image) and receiving module ( Figure 18 (Not shown in the diagram). The transmitting module is used to implement the transmitting function of the communication device 1800, and the receiving module is used to implement the receiving function of the communication device 1800.
[0335] Optionally, the communication device 1800 may also include a storage module. Figure 18 (Not shown in the image), the storage module stores programs or instructions. When the processing module 1801 executes the program or instructions, the communication device 1800 can perform the aforementioned... Figure 14 The method shown describes the function of the terminal device.
[0336] It is understood that the communication device 1800 can be a terminal device, or it can be executed by a component of the terminal device (such as a processor, chip, or chip system), or it can be a logic node, logic module, or software that can realize all or part of the functions of the terminal device. This application does not limit it in this regard.
[0337] In another possible implementation, the communication device 1800 can be used to achieve the above. Figure 16 The function of the terminal device in the method shown.
[0338] For example, the transceiver module 1802 is used to receive beam groups from the network device; when the energy of the terminal device meets the preset conditions, the processing module 1801 is used to control the transceiver module 1802 to feed back first information to the network device, and the first information instructs the network device to stop transmitting beam groups.
[0339] In one possible design, the energy of the terminal device meets the preset conditions, including at least one of the following: the energy of the terminal device reaches the preset energy value, or the energy of the terminal device is saturated.
[0340] Optionally, the beam group includes a beam group in a first domain and / or a beam group in a second domain. The period for the terminal device to receive the beam group in the first domain is a first period, and the period for the terminal device to receive the beam group in the second domain is a second period. The duration of the second period is longer than the duration of the first period.
[0341] In one possible design, the transceiver module 1802 is used to receive configuration information from the network device, the configuration information indicating the configuration of the beam group of the first domain and / or the configuration of the beam group of the second domain.
[0342] Optionally, the configuration information also indicates the priority relationship between the beamgroups of the first domain and the beamgroups of the second domain.
[0343] Optionally, the configuration of the beam group in the first domain includes at least one of the following: the duration of the first period, the starting time-domain position of the first period, the time-domain position of the beam group in the first domain, or the number of beams in the beam group in the first domain; the configuration of the beam group in the second domain includes at least one of the following: the duration of the second period, the starting time-domain position of the second period, the time-domain position of the beam group in the second domain, or the number of beams in the beam group in the second domain.
[0344] Optionally, the configuration information also indicates the time-frequency resources used to carry information fed back from the terminal device to the network device.
[0345] Optionally, the configuration information also indicates the aforementioned preset energy value.
[0346] Optionally, the transceiver module 1802 may include a transmitting module ( Figure 18 (not shown in the image) and receiving module ( Figure 18 (Not shown in the diagram). The transmitting module is used to implement the transmitting function of the communication device 1800, and the receiving module is used to implement the receiving function of the communication device 1800.
[0347] Optionally, the communication device 1800 may also include a storage module. Figure 18 (Not shown in the image), the storage module stores programs or instructions. When the processing module 1801 executes the program or instructions, the communication device 1800 can perform the aforementioned... Figure 16 The method shown describes the function of the terminal device.
[0348] It is understood that the communication device 1800 can be a terminal device, or it can be executed by a component of the terminal device (such as a processor, chip, or chip system), or it can be a logic node, logic module, or software that can realize all or part of the functions of the terminal device. This application does not limit it in this regard.
[0349] Furthermore, the technical effects of the communication device 1800 can be referenced from the technical effects of the communication method described above, and will not be repeated here.
[0350] Figure 19 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 For example, the communication device can be a terminal device, or it can be executed by a component of a terminal device (e.g., a processor, chip, or chip system), or it can be a logical node, logical module, or software that can implement all or part of the functions of the terminal device; alternatively, the communication device can be a network device, or it can be executed by a component of a network device (e.g., a processor, chip, or chip system), or it can be a logical node, logical module, or software that can implement all or part of the functions of the network device. Figure 19As shown, the communication device 1900 may include a processor 1901. Optionally, the communication device 1900 may also include a memory 1902 and / or a transceiver 1903. The processor 1901 is coupled to the memory 1902 and the transceiver 1903, for example, they may be connected via a communication bus.
[0351] The following is combined with Figure 19 A detailed description of each component of the communication device 1900 is provided below:
[0352] The processor 1901 is the control center of the communication device 1900. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1901 can be one or more CPUs, an ASIC, or one or more integrated circuits configured to implement the embodiments of this application, such as one or more microprocessors (digital signal processors, DSPs), or one or more FPGAs.
[0353] Optionally, the processor 1901 can perform various functions of the communication device 1900 by running or executing software programs stored in the memory 1902 and calling data stored in the memory 1902, such as performing the aforementioned functions. Figure 9 , Figure 14 or Figure 16 The communication method shown.
[0354] In a specific implementation, as one example, the processor 1901 may include one or more CPUs, for example... Figure 19 CPU0 and CPU1 are shown in the diagram.
[0355] In a specific implementation, as one example, the communication device 1900 may also include multiple processors, for example... Figure 19 The processors 1901 and 1904 are shown. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).
[0356] The memory 1902 is used to store the software program that executes the solution of this application, and is controlled by the processor 1901 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.
[0357] Optionally, the memory 1902 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1902 may be integrated with the processor 1901 or may exist independently, and may be connected via the interface circuit of the communication device 1900. Figure 19 (Not shown in the image) is coupled to processor 1901, and this embodiment of the application does not specifically limit this.
[0358] Transceiver 1903 is used for communication with other communication devices. For example, if communication device 1900 is a terminal, transceiver 1903 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1900 is a network device, transceiver 1903 can be used to communicate with a terminal or with another network device.
[0359] Alternatively, transceiver 1903 may include a receiver and a transmitter. Figure 19 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.
[0360] Alternatively, the transceiver 1903 can be integrated with the processor 1901, or it can exist independently and be connected via the interface circuit of the communication device 1900. Figure 19 (Not shown in the image) is coupled to processor 1901, and this embodiment of the application does not specifically limit this.
[0361] Understandable, Figure 19 The structure of the communication device 1900 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0362] Furthermore, the technical effects of the communication device 1900 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.
[0363] It should be understood that the processor in the embodiments of this application can be a CPU, but it can also be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.
[0364] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).
[0365] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.
[0366] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication.
[0367] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.
[0368] This application also provides a communication system, which includes a first device and a second device for performing the communication method provided above.
[0369] This application also provides a chip, which may include a processor that executes the communication method described above. Optionally, the chip may further include a memory coupled to the processor, the memory storing a program for executing the communication method described above.
[0370] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.
[0371] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.
[0372] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0373] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0374] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0375] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0376] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0377] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0378] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0379] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method, characterized in that, The method includes: Perform at least two beam scans of the first domain, the period of which is the first cycle; Based on the scanning results of the beam scan in the first domain, a beam scan in the second domain is performed. The first domain is different from the second domain. The period of the beam scan in the second domain is a second period, and the duration of the second period is longer than the duration of the first period. Based on the scanning results of the beam scan in the second domain, a first beam is determined, which is used for charging.
2. The method according to claim 1, characterized in that, The step of performing a beam scan in the second domain based on the scanning results of the beam scan in the first domain includes: When the beam scans of the first domain and the second domain overlap in time, the beam scan of the second domain is performed based on the scanning results of the beam scan of the first domain.
3. The method according to claim 2, characterized in that, When the beam scans of the first domain and the second domain overlap in time, the beam scan of the second domain is performed based on the scanning result of the beam scan of the first domain, including: If the beam scans of the first domain and the second domain overlap in time, and the priority of the beam scan of the second domain is higher than that of the beam scan of the first domain, then the beam scan of the second domain shall be performed according to the scanning result of the beam scan of the first domain.
4. The method according to claim 1, characterized in that, The execution of at least two beam scans of the first domain includes: If the beam scan of the first domain overlaps with the beam scan of the second domain in time, the at least two beam scans of the first domain are performed.
5. The method according to claim 1, characterized in that, Prior to performing at least two beam scans of the first domain, the method further includes: Perform beam scanning of the second domain; The execution of at least two beam scans of the first domain includes: Based on the scanning results of the beam scan in the second domain, perform the at least two beam scans in the first domain.
6. The method according to claim 5, characterized in that, The beam scanning of the second domain includes: If the beam scan of the first domain overlaps with the beam scan of the second domain in time, the beam scan of the second domain is performed.
7. The method according to claim 6, characterized in that, When the beam scan of the first domain overlaps with the beam scan of the second domain in time, performing a beam scan of the second domain includes: If the beam scans of the first domain and the second domain overlap in time, and the beam scan of the second domain has a higher priority than the beam scan of the first domain, then the beam scan of the second domain is performed.
8. The method according to claim 5, characterized in that, The step of performing at least two beam scans of the first domain based on the scanning results of the second domain includes: If the beam scans of the first domain and the second domain overlap in time, and the priority of the beam scan of the first domain is higher than that of the beam scan of the second domain, then the at least two beam scans of the first domain are performed according to the scanning result of the beam scan of the second domain.
9. The method according to claim 1, characterized in that, The second period is k times the first period, where k is an integer greater than 2. The time of the first p periods in the second period is configured to perform p beam scans of the first domain. The time of the last q periods in the second period is configured to perform beam scans of the second domain. p and q are positive integers, and p + q = k.
10. The method according to any one of claims 1-9, characterized in that, The method further includes: Perform beam scanning of the first domain; Receive first information from beam scanning feedback for the first domain; Based on the first information, perform beam scanning of the second domain.
11. The method according to any one of claims 1-9, characterized in that, The method further includes: Perform beam scanning of the first domain or the second domain; Receive first information in response to the beam scan feedback; Based on the first information, beam scanning of the first and second domains is stopped.
12. The method according to any one of claims 1-11, characterized in that, The method further includes: Send configuration information, which indicates the beam scanning configuration of the first domain and / or the beam scanning configuration of the second domain.
13. The method according to claim 12, characterized in that, The configuration information also indicates the priority relationship between beam scanning in the first domain and beam scanning in the second domain.
14. The method according to claim 12 or 13, characterized in that, The beam scanning configuration of the first domain includes at least one of the following: the duration of the first period, the starting time domain position of the first period, the time for performing beam scanning of the first domain within the first period, or the number of beams scanned in the first domain.
15. The method according to claim 12 or 13, characterized in that, The beam scanning configuration of the first domain includes at least one of the following: the duration of the second period, the starting time domain position of the second period, the time for performing beam scanning of the second domain within the second period, or the number of beams scanned in the second domain.
16. The method according to any one of claims 12-15, characterized in that, The configuration information also indicates time-frequency resources for carrying the scanning results of beam scanning of the first domain, and / or time-frequency resources for carrying the scanning results of beam scanning of the second domain.
17. The method according to any one of claims 1-16, characterized in that, The first domain is the frequency domain and the second domain is the spatial domain; or the first domain is the spatial domain and the second domain is the frequency domain.
18. A communication device, characterized in that, The communication device includes a module for performing the method as described in any one of claims 1-17.
19. A communication device, characterized in that, include: processor; The processor is configured to be coupled to a memory for storing computer instructions, which, when executed by the processor, cause the communication device to perform the method as described in any one of claims 1-17.
20. The communication device according to claim 19, characterized in that, The communication device is a chip.
21. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-17.