Beam management method and apparatus
By transmitting condition satisfaction indicators for candidate beams between terminals and network devices, the validity of measurement reports is verified, thus solving the problem of poor beam management reliability and achieving more efficient and accurate beam management.
Patent Information
- Application Number
- PCT/CN2025/094090
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
The reliability of beam management in existing technologies is poor, making it difficult to effectively verify the validity of measurement reports submitted by the terminal, resulting in inaccurate beam management.
The validity of measurement reports is verified by transmitting condition satisfaction indicators of candidate beams between terminals and network devices, and beam management, including beam switching, reselection, and resource reallocation, is performed based on the verified measurement reports.
It improves the reliability and efficiency of beam management, ensures the accuracy and timeliness of beam management, and reduces signaling overhead.
Smart Images

Figure CN2025094090_12112026_PF_FP_ABST
Abstract
Description
Beam management method and device Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a beam management method and apparatus. Background Technology
[0002] For event-triggered Layer 1 reports, a new reporting variable has been introduced: the condition met indicator. Specifically, a 1-bit condition met indicator is added for each reporting beam. The value of the condition met indicator is 1 if, for M consecutive measurement periods, the difference between the signal quality of a candidate beam and the signal quality of the current beam is consistently greater than a preset threshold. Summary of the Invention
[0003] This disclosure presents a beam management method and apparatus to address the technical problem of poor beam management reliability in related technologies.
[0004] In a first aspect, embodiments of this disclosure provide a beam management method, executed by a network device, the method comprising:
[0005] Obtain a first measurement report; the first measurement report includes a second measurement report reported by the terminal at least twice; the second measurement report is an event-triggered Layer 1 measurement report; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam;
[0006] Verify the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report;
[0007] Beam management is based on the validated first measurement report.
[0008] Secondly, embodiments of this disclosure propose a beam management method, executed by a terminal, the method comprising:
[0009] A second measurement report is sent to the network device; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam; the condition satisfaction indicator is used to verify the validity of the second measurement report.
[0010] Thirdly, embodiments of this disclosure provide a communication device for performing the beam management method described in the first aspect or the beam management method described in the second aspect.
[0011] Fourthly, embodiments of this disclosure provide a communication system including a terminal and a network device, wherein the network device is configured to implement the beam management method described in the first aspect above, and the terminal is configured to implement the beam management method described in the second aspect above.
[0012] Fifthly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the beam management method described in the first aspect or the beam management method described in the second aspect.
[0013] In a sixth aspect, embodiments of this disclosure provide a program product, including at least one of a program and instructions, wherein when the program or instructions are executed by a communication device, they implement the beam management method described in the first aspect or the beam management method described in the second aspect.
[0014] The beam management method and apparatus proposed in this disclosure verify the measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the measurement report reported by the terminal, and perform beam management based on the verified measurement report, thereby improving the reliability of beam management. Attached Figure Description
[0015] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.
[0016] Figure 1 is an exemplary schematic diagram of the architecture of the communication system provided in an embodiment of this disclosure.
[0017] Figure 2 is one of the exemplary interactive schematic diagrams of the beam management method provided in the embodiments of this disclosure.
[0018] Figure 3 is a second exemplary interactive schematic diagram of the beam management method provided in the embodiments of this disclosure.
[0019] Figure 4 is a third exemplary interactive schematic diagram of the beam management method provided in this disclosure embodiment.
[0020] Figure 5A is a schematic diagram of the structure of the network device proposed in an embodiment of this disclosure.
[0021] Figure 5B is a schematic diagram of the structure of the terminal proposed in the embodiment of this disclosure.
[0022] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.
[0023] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation
[0024] This disclosure presents a beam management method and apparatus.
[0025] In a first aspect, embodiments of this disclosure provide a beam management method, executed by a network device, the method comprising:
[0026] Obtain a first measurement report; the first measurement report includes a second measurement report reported by the terminal at least twice; the second measurement report is an event-triggered Layer 1 measurement report; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam;
[0027] Verify the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report;
[0028] Beam management is based on the validated first measurement report.
[0029] In the above embodiments, the measurement report is verified based on the condition satisfaction indicator corresponding to the candidate beam in the measurement report reported by the terminal, and beam management is performed based on the verified measurement report, thereby improving the reliability of beam management.
[0030] In conjunction with some embodiments of the first aspect, in some embodiments, verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes:
[0031] The validity of each submitted second measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each submitted second measurement report;
[0032] The validity of the first measurement report is verified based on the validity of each second measurement report submitted.
[0033] In the above embodiments, the validity of each reported second measurement report is first determined based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report, and then the validity of the first measurement report is verified based on the validity of each reported second measurement report, making the verification process more refined.
[0034] In conjunction with some embodiments of the first aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0035] If at least one first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
[0036] In the above embodiments, if at least one beam is valid and the value of the indicator is 1, the layer 1 measurement report triggered by the current event is determined to be valid. This can prioritize the timeliness of event triggering and improve efficiency.
[0037] In conjunction with some embodiments of the first aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0038] If each first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
[0039] In the above embodiments, if all beams whose corresponding conditions satisfy the indicator value of 1 are valid, the layer 1 measurement report triggered by the event is determined to be valid. This can ensure that beams whose corresponding conditions satisfy the indicator value of 1 are truly valid, which is suitable for high-precision beam management scenarios.
[0040] In conjunction with some embodiments of the first aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0041] If each first candidate beam and each second candidate beam are valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event in all M measurement windows; the second candidate beam being valid means that the first candidate beam does not satisfy the triggering condition of the measurement event at least once in the M measurement windows; M is an integer greater than 1.
[0042] In the above embodiments, both beams with a value of 1 corresponding to the condition met and beams with a value of 0 corresponding to the condition met are verified, which can comprehensively verify the measurement and judgment capabilities of the terminal.
[0043] In conjunction with some embodiments of the first aspect, in some embodiments, verifying the validity of the first measurement report based on the validity of each reported second measurement report includes:
[0044] The first ratio of the number of valid second measurement reports to the total number of reports;
[0045] If the first ratio is greater than the first threshold, the first measurement report is determined to be valid.
[0046] In the above embodiments, the validity of the first measurement report is determined by comparing the ratio of the number of valid second measurement reports to the total number of reports with a preset threshold. This preset threshold can be predefined, reducing signaling overhead. The preset threshold can also be configured, improving flexibility.
[0047] In conjunction with some embodiments of the first aspect, in some embodiments, verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes:
[0048] The validity of the first measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report.
[0049] In the above embodiments, the validity of the first measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report, and the validity of each reported second measurement report is no longer verified, which can improve the verification efficiency.
[0050] In conjunction with some embodiments of the first aspect, in some embodiments, determining the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0051] The total number of valid first candidate beams and valid second candidate beams is determined. The first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report. The second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report. A valid first candidate beam indicates that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. A valid second candidate beam indicates that the first candidate beam fails to satisfy the triggering condition of the measurement event at least once within M measurement windows. M is an integer greater than 1.
[0052] Determine a second ratio of the sum to the total number of all candidate beams included in the first measurement report;
[0053] If the second ratio is greater than the second threshold, the first measurement report is determined to be valid.
[0054] In the above embodiments, both beams with a value of 1 corresponding to the condition indicator and beams with a value of 0 corresponding to the condition indicator are verified. This can comprehensively verify the measurement and judgment capabilities of the terminal while also taking into account verification efficiency.
[0055] In conjunction with some embodiments of the first aspect, in some embodiments, determining the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0056] The third ratio of the number of valid first candidate beams to the total number of all first candidate beams is determined; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1;
[0057] If the third ratio is greater than the third threshold, the first measurement report is determined to be valid.
[0058] In the above embodiments, beams whose corresponding conditions meet the indicator value of 1 are verified in a focused manner, which improves the efficiency of verification.
[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the beam management based on the verified first measurement report includes at least one of the following:
[0060] If the first measurement report is valid, beam switching is performed based on the first measurement report;
[0061] If the first measurement report is valid, beam reselection is performed based on the first measurement report;
[0062] If the first measurement report is valid, beam resources are reallocated based on the first measurement report;
[0063] If the first measurement report is invalid, instruct the terminal to re-perform the event-triggered Layer 1 measurement.
[0064] In the above embodiments, when the first measurement report is valid, beam switching, reselection, and beam resource reallocation are performed; when the first measurement report is invalid, the terminal is instructed to re-perform the event-triggered Layer 1 measurement, thus ensuring the reliability of beam switching, reselection, and beam resource reallocation.
[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0066] Send a first message to the terminal; the first message contains the number M of measurement windows during beam measurement, where M is an integer greater than 1.
[0067] In the above embodiments, the network device configures the number of measurement windows M for beam measurement of the terminal, which improves flexibility.
[0068] Secondly, embodiments of this disclosure propose a beam management method, executed by a terminal, the method comprising:
[0069] A second measurement report is sent to the network device; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam; the condition satisfaction indicator is used to verify the validity of the second measurement report.
[0070] In the above embodiments, the measurement report is verified based on the condition satisfaction indicator corresponding to the candidate beam in the measurement report reported by the terminal, and beam management is performed based on the verified measurement report, thereby improving the reliability of beam management.
[0071] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:
[0072] Obtain the indication information sent by the network device; the indication information is used to instruct the terminal to re-perform the event-triggered Layer 1 measurement;
[0073] Re-perform the layer 1 measurement triggered by the event.
[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:
[0075] Measure the signal quality of the candidate beam within M measurement windows; M is an integer greater than 1;
[0076] If all candidate beams in the M measurement windows meet the triggering conditions of the measurement event, the value of the condition satisfaction indicator corresponding to the candidate beams included in the second measurement report is marked as 1.
[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes:
[0078] Obtain the first message sent by the network device; the first message contains the value of M.
[0079] Thirdly, embodiments of this disclosure provide a network device implementation, including:
[0080] The transceiver module is used to acquire a first measurement report; the first measurement report includes a second measurement report reported by the terminal at least twice; the second measurement report is an event-triggered Layer 1 measurement report; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam;
[0081] The processing module is used to verify the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report; and to perform beam management based on the verified first measurement report.
[0082] In conjunction with some embodiments of the third aspect, in some embodiments, verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes:
[0083] The validity of each submitted second measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each submitted second measurement report;
[0084] The validity of the first measurement report is verified based on the validity of each second measurement report submitted.
[0085] In conjunction with some embodiments of the third aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0086] If at least one first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
[0087] In conjunction with some embodiments of the third aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0088] If each first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
[0089] In conjunction with some embodiments of the third aspect, in some embodiments, determining the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0090] If each first candidate beam and each second candidate beam are valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event in all M measurement windows; the second candidate beam being valid means that the first candidate beam does not satisfy the triggering condition of the measurement event at least once in the M measurement windows; M is an integer greater than 1.
[0091] In conjunction with some embodiments of the third aspect, in some embodiments, verifying the validity of the first measurement report based on the validity of each reported second measurement report includes:
[0092] The first ratio of the number of valid second measurement reports to the total number of reports;
[0093] If the first ratio is greater than the first threshold, the first measurement report is determined to be valid.
[0094] In conjunction with some embodiments of the third aspect, in some embodiments, verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes:
[0095] The validity of the first measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report.
[0096] In conjunction with some embodiments of the third aspect, in some embodiments, determining the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0097] The total number of valid first candidate beams and valid second candidate beams is determined. The first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report. The second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report. A valid first candidate beam indicates that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. A valid second candidate beam indicates that the first candidate beam fails to satisfy the triggering condition of the measurement event at least once within M measurement windows. M is an integer greater than 1.
[0098] Determine a second ratio of the sum to the total number of all candidate beams included in the first measurement report;
[0099] If the second ratio is greater than the second threshold, the first measurement report is determined to be valid.
[0100] In conjunction with some embodiments of the third aspect, in some embodiments, determining the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes:
[0101] The third ratio of the number of valid first candidate beams to the total number of all first candidate beams is determined; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1;
[0102] If the third ratio is greater than the third threshold, the first measurement report is determined to be valid.
[0103] In conjunction with some embodiments of the third aspect, in some embodiments, the beam management based on the verified first measurement report includes at least one of the following:
[0104] If the first measurement report is valid, beam switching is performed based on the first measurement report;
[0105] If the first measurement report is valid, beam reselection is performed based on the first measurement report;
[0106] If the first measurement report is valid, beam resources are reallocated based on the first measurement report;
[0107] If the first measurement report is invalid, instruct the terminal to re-perform the event-triggered Layer 1 measurement.
[0108] In conjunction with some embodiments of the third aspect, in some embodiments, the transceiver module is further configured to send a first message to the terminal; the first message contains the number M of measurement windows during beam measurement, where M is an integer greater than 1.
[0109] Fourthly, embodiments of this disclosure provide a terminal, including:
[0110] The transceiver module is used to send a second measurement report to the network device; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam; the condition satisfaction indicator is used to verify the validity of the second measurement report.
[0111] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to acquire indication information sent by the network device; the indication information is used to instruct the terminal to re-perform the event-triggered Layer 1 measurement;
[0112] The terminal also includes a processing module; the processing module is used to re-perform the event-triggered layer 1 measurement.
[0113] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal further includes a processing module; the processing module is used for:
[0114] Measure the signal quality of the candidate beam within M measurement windows; M is an integer greater than 1;
[0115] If all candidate beams in the M measurement windows meet the triggering conditions of the measurement event, the value of the condition satisfaction indicator corresponding to the candidate beams included in the second measurement report is marked as 1.
[0116] In conjunction with some embodiments of the fourth aspect, in some embodiments, the transceiver module is further configured to acquire a first message sent by the network device; the first message contains a value of M.
[0117] Fifthly, embodiments of this disclosure provide a communication device for performing the beam management method of the first aspect above, or the beam management method of the second aspect above.
[0118] In a sixth aspect, embodiments of this disclosure provide a communication system including a terminal and a network device, wherein the network device is configured to implement the beam management method of the first aspect described above, and the terminal is configured to implement the beam management method of the second aspect described above.
[0119] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the beam management method of the first aspect or the beam management method of the second aspect described above.
[0120] Eighthly, embodiments of this disclosure provide a program product including at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the beam management method of the first aspect or the beam management method of the second aspect described above.
[0121] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0122] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0123] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0124] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0125] In the embodiments of this disclosure, "multiple" refers to two or more.
[0126] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0127] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0128] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.
[0129] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0130] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0131] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0132] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0133] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0134] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0135] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0136] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.
[0137] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0138] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.
[0139] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0140] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0141] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0142] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0143] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure. As shown in Figure 1, the communication system 100 includes a terminal 101 and a network device 102.
[0144] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home, but is not limited thereto.
[0145] In some embodiments, network device 102 may include at least one of access network device and core network device.
[0146] In some embodiments, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system, but is not limited thereto.
[0147] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0148] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0149] In some embodiments, the core network equipment may be a single device, including a first network element, a second network element, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements may be virtual, such as servers deployed in the cloud, or physical, such as servers deployed locally. The core network may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0150] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0151] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are illustrative. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0152] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0153] Level 1 Reference Signal Received Power (L1-RSRP) is a key metric for beam management in wireless communication systems (especially 5G networks). It measures the power level of the reference signal received from the base station and is crucial for evaluating the quality of the wireless link.
[0154] The L1-RSRP measurement and reporting process is as follows:
[0155] Beam scanning: The base station (gNB) sends reference signals through beams in different directions (beam scanning);
[0156] Measurement: The terminal (UE) measures the received power (L1-RSRP) of these reference signals;
[0157] Reporting: The UE feeds back the L1-RSRP measurement results to the gNB;
[0158] Beam selection: Based on the analysis and reporting results of the gNB, the beam direction with the highest received power is selected for communication.
[0159] Traditional mechanisms only support periodic and semi-persistent reporting modes. UEs need to report measurement results periodically according to the network configuration, which generates significant signaling overhead.
[0160] Under the event-triggered mechanism, the UE does not need to report periodically; reporting is only triggered when the measurement results meet preset conditions. For example, if the L1-RSRP of the current beam is lower than that of other candidate beams, the UE will proactively report the index of the beam with better quality to the network. This approach significantly reduces signaling overhead and improves beam management efficiency.
[0161] For event-triggered Layer 1 measurement reports, a new reporting variable has been introduced: the condition met indicator.
[0162] Regarding UE-initiated / event-triggered beam reporting, the explanation of each codepoint of the supported 1-bit condition satisfaction indicator is as follows:
[0163] "0" indicates that the number of Channel State Information Reference Signal Resource Indicator (CSI-RS) / Synchronization Signals Block Resource Indicator (SSBRI) corresponding to Event 2 (Event-2) within the time window has not reached the configured threshold number M.
[0164] "1" indicates that the CRI / SSBRI corresponding to event 2 within the time window has reached or exceeded the configured threshold number M.
[0165] Whether to introduce a 1-bit condition satisfaction indicator for Event-7 and how to implement it requires further research.
[0166] For each reported beam, a 1-bit condition satisfaction indicator is added to mark whether the beam meets the event triggering condition within the measurement window. When the L1-RSRP difference between the candidate beam and the current beam is continuously greater than the threshold X for M consecutive measurement cycles, the condition satisfaction indicator corresponding to the candidate beam is marked as 1.
[0167] The event-triggered L1-RSRP reporting mechanism is used to have the terminal (UE) report the L1-RSRP measurement values of multiple beams and their corresponding condition satisfaction indicators to the base station (gNB) when a specific event occurs.
[0168] The detailed process of the reporting procedure is as follows:
[0169] 1. Network configuration.
[0170] Base Station (gNB): The base station sends measurement configuration information to the terminal based on network requirements and terminal capabilities. This configuration information includes the measurement object (such as beam, cell), event triggering conditions (Event 1, Event 2, Event 3, Event 4, Event 5, Event 6, Event 7a, Event 7b, Event 8, Event 9), measurement period, and report type (such as periodic report, event-triggered report), etc.
[0171] Terminal (UE): The terminal receives and parses the measurement configuration information and configures the corresponding measurement parameters.
[0172] 2. Measurement phase.
[0173] Terminal (UE): The terminal performs L1-RSRP measurements according to the configured measurement object and period. Each measurement includes L1-RSRP values for multiple beams.
[0174] Conditional Judgment: The terminal determines whether the L1-RSRP value of each beam meets the event triggering conditions. If the conditions are met, the corresponding condition-met indicator is set to 1; otherwise, it is set to 0.
[0175] 3. Event triggering.
[0176] Terminal (UE): The terminal continuously monitors the L1-RSRP value. When it detects that the L1-RSRP value of a certain beam meets the event triggering condition, it triggers the event reporting.
[0177] Condition met: The terminal records the beams that meet the conditions and their condition met indicators.
[0178] 4. Reporting stage.
[0179] Terminal (UE): The terminal prepares to report data, which includes at least one of the following:
[0180] Beam identifier: A unique identifier for each beam.
[0181] L1-RSRP value: The L1-RSRP measurement value for each beam.
[0182] Event type: The type of event that triggers the event.
[0183] Condition satisfied indicator.
[0184] Terminal (UE): The terminal sends the prepared reporting data to the base station (gNB).
[0185] 5. Receiving and processing.
[0186] Data reception: The base station receives data reported by the terminal, including L1-RSRP values of multiple beams and corresponding condition satisfaction indicators.
[0187] Data processing:
[0188] Base station (gNB): The base station performs further processing and decision-making based on the reported L1-RSRP value and the corresponding condition satisfaction indicator. For example:
[0189] Beam management: Adjust beam configuration based on L1-RSRP value and corresponding condition satisfaction indicator, and perform beam switching or reselection.
[0190] Resource allocation: Optimize resource allocation based on the reported data to improve network performance.
[0191] In related technologies, no correlation verification mechanism has been established between the condition fulfillment indicator and L1-RSRP, making it impossible to determine whether the condition fulfillment indicator truly reflects the continuous triggering conditions for M cycles. Furthermore, there is a lack of dual detection methods for "false alarm reporting" (the condition fulfillment indicator corresponding to the non-compliant beam is mistakenly marked as 1, which may lead to the network side selecting an unstable beam) and "missed alarms" (the condition fulfillment indicator corresponding to the compliant beam is mistakenly marked as 0, which may lead to missing high-quality beam resources), resulting in a decrease in the reliability and efficiency of network side decision-making.
[0192] Based on the above-mentioned technical problems, this disclosure proposes a beam management method and apparatus. The method verifies the measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the measurement report reported by the terminal, and performs beam management based on the verified measurement report, thereby improving the credibility / reliability of beam management.
[0193] Figure 2 is one of the exemplary interactive schematic diagrams of the beam management method provided in this disclosure embodiment. As shown in Figure 2, this disclosure embodiment provides a beam management method, which may include:
[0194] Step 201: Network device 102 sends a measurement configuration message to terminal 101. Terminal 101 receives the measurement configuration message sent by network device 102.
[0195] In some embodiments, the measurement configuration message may include the measurement object (such as a beam or cell), event triggering conditions (such as events such as event-1, event-2, event-3, event-4, event-5, event-6, event-7a, event-7b, event-8, event-9, etc.), measurement period, and report type (such as periodic report or event-triggered report).
[0196] Step 202: Terminal 101 performs Layer 1 measurement according to the measurement object and period parameters configured in the measurement configuration message.
[0197] In some embodiments, the terminal measures the signal quality of the candidate beam within M measurement windows.
[0198] For example, the terminal can measure the signal quality of a candidate beam within the most recent M consecutive measurement windows. The most recent M consecutive measurement windows refer to the most recent M consecutive measurement windows before each report.
[0199] In some embodiments, each measurement includes L1-RSRP values for multiple candidate beams.
[0200] The terminal determines whether the L1-RSRP value of each candidate beam meets the event triggering conditions. If the conditions are met, the corresponding condition-met indicator is set to 1; otherwise, it is set to 0.
[0201] In some embodiments, the event triggering conditions include at least one of the following events: event-1, event-2, event-3, event-4, event-5, event-6, event-7a, event-7b, event-8, and event-9.
[0202] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the first signal quality exceeding a fourth threshold within M measurement windows. The first signal quality is either the maximum value, the minimum value, or the average value of the signal quality of the active beam.
[0203] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding a fifth threshold within M measurement windows.
[0204] In some embodiments, the event triggering condition includes the signal quality of the candidate beams exceeding a sixth threshold within M measurement windows.
[0205] For example, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding -3dB within M consecutive measurement windows.
[0206] In some embodiments, the value of M can be predefined.
[0207] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold may be predefined.
[0208] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold can be configured by the network device.
[0209] In some embodiments, the measurement configuration message may be a first message. The first message may contain the number M of measurement windows when the terminal performs beam measurement. For example, the network device sends the first message to the terminal via Radio Resource Control (RRC) or Media Access Control Control Element (MAC CE).
[0210] In some embodiments, the number of candidate beams reported can be predefined.
[0211] In some embodiments, the number of candidate beams reported can be configured by the network device.
[0212] In some embodiments, the current beam may refer to the beam used when reporting measurement reports.
[0213] Step 203: Terminal 101 continuously reports event-triggered Layer 1 measurement reports to network device 102 multiple times. Network device 102 continuously receives the event-triggered Layer 1 measurement reports reported by terminal 101 multiple times.
[0214] In some embodiments, each reported event-triggered Layer 1 measurement report includes a condition satisfaction indicator corresponding to the candidate beam.
[0215] Step 204: Network device 102 performs joint verification of event triggering and condition fulfillment indicators.
[0216] In some embodiments, network device 102 first verifies the validity of each reported second measurement report, and then verifies the validity of the first measurement report based on the validity of each reported second measurement report.
[0217] In some embodiments, network device 102 may first verify whether the reporting time of the Layer 1 measurement report triggered by each reported event is less than a predefined reporting delay. If the reporting time exceeds the predefined reporting delay, the report can be directly determined to be invalid without further verification of the validity of the reported content. If the reporting time is less than (does not exceed) the predefined reporting delay, network device 102 determines the validity of the Layer 1 measurement report triggered by each reported event based on the content of the measurement report.
[0218] In some embodiments, the network device 102 determines that each reported second measurement report is valid if at least one first candidate beam is valid; otherwise, it is invalid. The first candidate beam is the candidate beam in each reported second measurement report whose condition satisfaction indicator value is 1. The first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. M is an integer greater than 1.
[0219] In some embodiments, the network device 102 determines that the second measurement report reported each time is valid if each first candidate beam is valid; otherwise, it is invalid. The first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report. The first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. M is an integer greater than 1.
[0220] In some embodiments, network device 102 determines that each reported second measurement report is valid if both the first candidate beam and the second candidate beam are valid; otherwise, it is invalid. The first candidate beam is the candidate beam in each reported second measurement report whose condition satisfaction indicator value is 1. The second candidate beam is the candidate beam in each reported second measurement report whose condition satisfaction indicator value is 0. The first candidate beam being valid indicates that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. The second candidate beam being valid indicates that the first candidate beam does not satisfy the triggering condition of the measurement event at least once within M measurement windows. M is an integer greater than 1.
[0221] In some embodiments, after determining the validity of a Layer 1 measurement report triggered by each reported event, the network device 102 determines a first ratio of the number of valid second measurement reports to the total number of reports; if the first ratio is greater than a first threshold, the first measurement report is determined to be valid; otherwise, it is invalid.
[0222] In some embodiments, the value of the first threshold may be predefined.
[0223] In some embodiments, the value of the first threshold can be configured by the network device. For example, it can be dynamically configured by the network device via RRC signaling to adapt to different scenario requirements.
[0224] Step 205: If the network device 102 determines that the first measurement report is invalid, the network device may not perform beam management and may send a remeasurement instruction message to the terminal, instructing the terminal to perform the measurement again.
[0225] Step 206: After receiving the remeasurement instruction sent by the network device 102, the terminal 101 re-executes the event-triggered layer 1 measurement.
[0226] Step 207: After the terminal 101 performs the measurement again, it will continuously report the Layer 1 measurement report triggered by the event multiple times.
[0227] Step 208: Network device 102 re-verifies the validity of the Layer 1 measurement reports triggered by the multiple reported events.
[0228] Step 209: If the network device 102 determines that the first measurement report is valid, the network device performs beam management.
[0229] In some embodiments, the network device performs beam switching if the network device 102 determines that the first measurement report is valid.
[0230] In some embodiments, the network device performs beam reselection if the network device 102 determines that the first measurement report is valid.
[0231] In some embodiments, if the network device 102 determines that the first measurement report is valid, the network device performs beam resource reallocation.
[0232] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0233] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.
[0234] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0235] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0236] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0237] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0238] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.
[0239] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0240] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”
[0241] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0242] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.
[0243] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.
[0244] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.
[0245] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0246] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0247] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0248] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0249] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0250] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.
[0251] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.
[0252] The beam management method disclosed in this embodiment may include at least one of steps 201 to 209. For example, steps 202+203+204 can be implemented as an independent embodiment, steps 201+202+203+204 can be implemented as an independent embodiment, steps 202+203+204+209 can be implemented as an independent embodiment, steps 201+202+203+204+209 can be implemented as an independent embodiment, and steps 201+202+203+204+205+206+207+208+209 can be implemented as an independent embodiment, but are not limited thereto.
[0253] In some embodiments, steps 201, 205, 206, 207, 208, and 209 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0254] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0255] Figure 3 is a second exemplary interactive schematic diagram of the beam management method provided in this embodiment of the present disclosure. As shown in Figure 3, this embodiment of the present disclosure provides a beam management method, which may include:
[0256] Step 301: Network device 102 sends a measurement configuration message to terminal 101. Terminal 101 receives the measurement configuration message sent by network device 102.
[0257] In some embodiments, the measurement configuration message may include the measurement object (such as a beam or cell), event triggering conditions (such as events such as event-1, event-2, event-3, event-4, event-5, event-6, event-7a, event-7b, event-8, event-9, etc.), measurement period, and report type (such as periodic report or event-triggered report).
[0258] Step 302: Terminal 101 performs Layer 1 measurement according to the measurement object and period parameters configured in the measurement configuration message.
[0259] In some embodiments, the terminal measures the signal quality of the candidate beam within M measurement windows.
[0260] For example, the terminal can measure the signal quality of a candidate beam within the most recent M consecutive measurement windows. The most recent M consecutive measurement windows refer to the most recent M consecutive measurement windows before each report.
[0261] In some embodiments, each measurement includes L1-RSRP values for multiple candidate beams.
[0262] The terminal determines whether the L1-RSRP value of each candidate beam meets the event triggering conditions. If the conditions are met, the corresponding condition-met indicator is set to 1; otherwise, it is set to 0.
[0263] In some embodiments, the event triggering conditions include at least one of the following: Event-1, Event-2, Event-3, Event-4, Event-5, Event-6, Event-7a, Event-7b, Event-8, and Event-9.
[0264] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the first signal quality exceeding a fourth threshold within M measurement windows. The first signal quality is either the maximum value, the minimum value, or the average value of the signal quality of the active beam.
[0265] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding a fifth threshold within M measurement windows.
[0266] In some embodiments, the event triggering condition includes the signal quality of the candidate beams exceeding a sixth threshold within M measurement windows.
[0267] For example, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding -3dB within M consecutive measurement windows.
[0268] In some embodiments, the value of M can be predefined.
[0269] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold may be predefined.
[0270] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold can be configured by the network device.
[0271] In some embodiments, the measurement configuration message may be a first message. The first message may contain the number M of measurement windows when the terminal performs beam measurement. For example, the network device sends the first message to the terminal via Radio Resource Control (RRC) or Media Access Control Control Element (MAC CE).
[0272] In some embodiments, the number of candidate beams reported can be predefined.
[0273] In some embodiments, the number of candidate beams reported can be configured by the network device.
[0274] In some embodiments, the current beam may refer to the beam used when reporting measurement reports.
[0275] Step 303: Terminal 101 continuously reports event-triggered Layer 1 measurement reports to network device 102 multiple times. Network device 102 continuously receives the event-triggered Layer 1 measurement reports reported by terminal 101 multiple times.
[0276] In some embodiments, each reported event-triggered Layer 1 measurement report includes a condition satisfaction indicator corresponding to the candidate beam.
[0277] Step 304: Network device 102 verifies the validity of the first measurement report only based on the condition satisfaction indicator.
[0278] In some embodiments, the validity of the Layer 1 measurement report triggered by each reported event can be verified individually, as detailed in the embodiments described above, and will not be repeated here.
[0279] In some embodiments, network device 102 determines the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report.
[0280] In some embodiments, network device 102 may first determine the sum of the number of valid first candidate beams and the number of valid second candidate beams; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event in all M measurement windows; the second candidate beam being valid means that the first candidate beam does not satisfy the triggering condition of the measurement event at least once in the M measurement windows; M is an integer greater than 1; then determine a second ratio of the sum to the total number of all candidate beams included in the first measurement report; if the second ratio is greater than a second threshold, the first measurement report is determined to be valid; otherwise, it is invalid.
[0281] In some embodiments, the value of the second threshold may be predefined.
[0282] In some embodiments, the value of the second threshold can be configured by the network device. For example, it can be dynamically configured by the network device via RRC signaling to adapt to different scenario requirements.
[0283] In some embodiments, network device 102 may first determine a third ratio of the number of valid first candidate beams to the total number of all first candidate beams; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1; then, if the third ratio is greater than a third preset threshold, the first measurement report is determined to be valid; otherwise, it is invalid.
[0284] In some embodiments, the value of the third threshold may be predefined.
[0285] In some embodiments, the value of the third threshold can be configured by the network device. For example, it can be dynamically configured by the network device via RRC signaling to adapt to different scenario requirements.
[0286] Step 305: If the network device 102 determines that the first measurement report is valid, the network device performs beam management.
[0287] In some embodiments, the network device performs beam switching if the network device 102 determines that the first measurement report is valid.
[0288] In some embodiments, the network device performs beam reselection if the network device 102 determines that the first measurement report is valid.
[0289] In some embodiments, if the network device 102 determines that the first measurement report is valid, the network device performs beam resource reallocation.
[0290] The beam management method disclosed in this embodiment may include at least one of steps 301 to 305. For example, steps 302+303+304 can be implemented as an independent embodiment, steps 301+302+303+304 can be implemented as an independent embodiment, steps 302+303+304+305 can be implemented as an independent embodiment, and steps 301+302+303+304+305 can be implemented as an independent embodiment, but are not limited thereto.
[0291] In some embodiments, steps 301 and 305 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0292] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0293] Figure 4 is a third exemplary interactive schematic diagram of the beam management method provided in this embodiment of the present disclosure. As shown in Figure 4, this embodiment of the present disclosure provides a beam management method, which may include:
[0294] Step 401: Terminal 101 performs layer 1 measurement according to predefined measurement parameters.
[0295] In some embodiments, predefined measurement parameters may include the measurement object (such as a beam or cell), event triggering conditions (such as events-1, event-2, event-3, event-4, event-5, event-6, event-7a, event-7b, event-8, event-9, etc.), measurement period, and report type (such as periodic report or event-triggered report).
[0296] In some embodiments, the terminal measures the signal quality of the candidate beam within M measurement windows.
[0297] For example, the terminal can measure the signal quality of a candidate beam within the most recent M consecutive measurement windows. The most recent M consecutive measurement windows refer to the most recent M consecutive measurement windows before each report.
[0298] In some embodiments, each measurement includes L1-RSRP values for multiple candidate beams.
[0299] The terminal determines whether the L1-RSRP value of each candidate beam meets the event triggering conditions. If the conditions are met, the corresponding condition-met indicator is set to 1; otherwise, it is set to 0.
[0300] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the first signal quality exceeding a fourth threshold within M measurement windows. The first signal quality is either the maximum value, the minimum value, or the average value of the signal quality of the active beam.
[0301] In some embodiments, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding a fifth threshold within M measurement windows.
[0302] In some embodiments, the event triggering condition includes the signal quality of the candidate beams exceeding a sixth threshold within M measurement windows.
[0303] For example, the event triggering condition includes the difference between the signal quality of the candidate beam and the signal quality of the current beam exceeding -3dB within M consecutive measurement windows.
[0304] In some embodiments, the value of M can be predefined.
[0305] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold may be predefined.
[0306] In some embodiments, the values of the fourth threshold, the fifth threshold, and the sixth threshold can be configured by the network device.
[0307] In some embodiments, the measurement configuration message may be a first message. The first message may contain the number M of measurement windows when the terminal performs beam measurement. For example, the network device sends the first message to the terminal via Radio Resource Control (RRC) or Media Access Control Control Element (MAC CE).
[0308] In some embodiments, the number of candidate beams reported can be predefined.
[0309] In some embodiments, the number of candidate beams reported can be configured by the network device.
[0310] In some embodiments, the current beam may refer to the beam used when reporting measurement reports.
[0311] Step 402: Terminal 101 continuously reports event-triggered Layer 1 measurement reports to network device 102 multiple times. Network device 102 continuously receives the event-triggered Layer 1 measurement reports reported by terminal 101 multiple times.
[0312] In some embodiments, each reported event-triggered Layer 1 measurement report includes a condition satisfaction indicator corresponding to the candidate beam.
[0313] Step 403: Network device 102 verifies the validity of the first measurement report.
[0314] In some embodiments, network device 102 can perform joint verification of event triggering and condition fulfillment indicators, as detailed in the above embodiments, which will not be repeated here.
[0315] In some embodiments, network device 102 may also verify the validity of the first measurement report only based on the condition satisfaction indicator. The validity of each Layer 1 measurement report triggered by a reported event can be verified separately. For details, please refer to the above embodiments, which will not be repeated here.
[0316] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0317] The beam management method in the above embodiments will be further illustrated with two examples below:
[0318] Example 1: Joint verification of event triggering and condition fulfillment indicators.
[0319] Step 1: Determine the validity of Layer 1 measurement reports triggered by a single reported event.
[0320] If the reporting time exceeds the predefined reporting delay, the report can be directly determined to be invalid, and there is no need to verify the validity of the reported content.
[0321] If the reporting time is less than (does not exceed) the predefined reporting delay, the validity of the Layer 1 measurement report triggered by each reported event is determined based on the content of the measurement report. Choose one of the following schemes: A / B / C.
[0322] Option A: At least one valid trigger candidate beam.
[0323] Judgment rules:
[0324] 1. Perform the following operations on each of the K candidate beams reported:
[0325] Check if the condition satisfaction indicator for each candidate beam is 1;
[0326] For each candidate beam marked as 1, verify whether the L1-RSRP difference (candidate beam of neighboring cell minus current beam of serving cell) in the most recent M measurement windows all exceed the preset threshold X.
[0327] 2. If at least one candidate beam meets the criteria, the report is considered valid.
[0328] 3. Repeatedly check all N reported records.
[0329] Parameter description:
[0330] M (Number of Measurement Windows): The number of consecutive measurements that must be continuously met to trigger the event.
[0331] X (Trigger Threshold): The minimum difference threshold between the L1-RSRP of the neighboring cell and the serving cell, in dB.
[0332] K (Number of reported candidate beams): The number of candidate beams included in a single measurement report.
[0333] Features:
[0334] Prioritize the timeliness of event triggering; allow false alarms for non-critical candidate beams (e.g., mislabeling a non-compliant candidate beam as 1).
[0335] Option B: Rigorously verify all candidate beams reporting 1.
[0336] Judgment rules:
[0337] 1. Perform the following operations on each of the K candidate beams reported:
[0338] Collect a list of all candidate beams marked with 1;
[0339] For each candidate beam in the list, check whether the RSRP difference of its most recent M windows continuously exceeds the threshold X.
[0340] 2. If all candidate beams marked as 1 meet the conditions, this report is considered valid.
[0341] 3. Any candidate beam that does not meet the conditions is considered an invalid report.
[0342] Features:
[0343] Ensures that all reported candidate beams are real and valid; suitable for high-precision candidate beam management scenarios.
[0344] Option C: Strict matching of all candidate beams.
[0345] Judgment rules:
[0346] 1. Perform the following operations on each of the K candidate beams reported:
[0347] Verify the actual state of each candidate beam (regardless of whether it is indicated as 0 or 1);
[0348] If the candidate beam consistently meets the criteria for M windows, the indicator should be 1.
[0349] If the target is not consistently met, the indicator should be 0.
[0350] 2. Only if the indication status of all candidate beams is correctly matched will this report be recorded as valid.
[0351] Features:
[0352] The test comprehensively verifies the UE's measurement and judgment capabilities; the testing standards are the most stringent.
[0353] Step 2: Calculate the overall pass rate.
[0354] Statistical methods:
[0355] 1. Accumulate all reports that have been marked as valid.
[0356] 2. Calculate the percentage of valid reports out of the total number of reports:
[0357] Pass rate = (Number of valid reports / Total number of reports) × 100%
[0358] 3. Judgment criteria: A pass rate of ≥90% is considered passing.
[0359] It should be noted that a pass rate of ≥90% indicates that the Layer 1 measurement reports triggered by multiple reported events are generally valid.
[0360] Example 2: Validation of event triggering and condition fulfillment indicators separately.
[0361] The verification of the validity of a Layer 1 measurement report triggered by a single event is the same as step one in Example 1, and will not be repeated here.
[0362] The following scheme is used to verify the overall validity of the measurement report based on the condition satisfaction indicator:
[0363] Method A: All data are statistically analyzed independently.
[0364] Verification steps:
[0365] 1. Collect the values of the condition satisfaction indicators corresponding to all K candidate beams reported N times.
[0366] 2. Perform verification on the value of each condition satisfaction indicator for each candidate beam:
[0367] If the value is 1: Check whether the corresponding candidate beam consistently meets the standard within the M window.
[0368] If the value is 0: Check whether the corresponding candidate beam does not meet the standard within the M window.
[0369] 3. Count the number of values of the indicator that satisfy all the conditions for correct judgment.
[0370] 4. Calculation accuracy:
[0371] Accuracy rate = (Number of correct indications / Total number of indications) × 100%
[0372] 5. Acceptance criteria: Accuracy rate ≥ 90%
[0373] It should be noted that an accuracy rate of ≥90% indicates that the Layer 1 measurement report triggered by multiple reported events is valid overall.
[0374] Method B: Focus on verifying the condition 1 indicator.
[0375] Verification steps:
[0376] 1. Collect all instruction records marked as 1.
[0377] 2. Perform verification for each candidate beam that reports 1:
[0378] Check whether the L1-RSRP difference of the most recent M windows has consistently exceeded the threshold X.
[0379] 3. Count the number of reports that truly meet the standards.
[0380] 4. Calculation accuracy:
[0381] Accuracy rate = (Number of times the actual score was achieved / Total number of times the score was achieved) × 100%
[0382] 5. Acceptance criteria: Accuracy rate ≥ 90%
[0383] It should be noted that an accuracy rate of ≥90% indicates that the Layer 1 measurement report triggered by multiple reported events is valid overall.
[0384] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.
[0385] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0386] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0387] Figure 5A is a schematic diagram of the structure of a network device proposed in an embodiment of this disclosure. The network device 5200 is used to execute any of the above methods. In some embodiments, as shown in Figure 5A, the network device 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to acquire a first measurement report; the first measurement report includes a second measurement report reported at least twice by the terminal; the second measurement report is an event-triggered Layer 1 measurement report; the second measurement report contains a condition satisfaction indicator corresponding to a candidate beam. The processing module 5202 is used to verify the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report; and to perform beam management based on the verified first measurement report. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps 201, 203, 205, 207, 301, 303, 402, but not limited thereto) performed by the network device in any of the above methods, which will not be elaborated further here. Optionally, the above processing module is used to execute at least one of the other steps (e.g., steps 204, 208, 209, 304, 305, 403, but not limited thereto) executed by the network device 102 in any of the above methods, which will not be elaborated here.
[0388] Figure 5B is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. Terminal 5100 is used to execute any of the above methods. In some embodiments, as shown in Figure 5B, terminal 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module is used to send a second measurement report to a network device; the second measurement report includes a condition satisfaction indicator corresponding to a candidate beam; the condition satisfaction indicator is used to verify the validity of the second measurement report. Optionally, the transceiver module is used to execute at least one of the communication steps (e.g., steps 201, 203, 205, 207, 301, 303, 402, but not limited thereto) executed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to execute at least one of other steps (e.g., steps 202, 206, 302, 401, but not limited thereto) executed by terminal 101 in any of the above methods, which will not be elaborated here.
[0389] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0390] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.
[0391] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.
[0392] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0393] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0394] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps 201, 203, 205, 207, 301, 303, 402, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps 204, 208, 209, 304, 305, 403, 202, 206, 302, 401, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be used interchangeably; terms such as transmitter, transmitter unit, transmitter, and transmitter circuit can be used interchangeably; and terms such as receiver, receiver unit, receiver, and receiver circuit can be used interchangeably.
[0395] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0396] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0397] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.
[0398] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0399] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0400] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps 201, 203, 205, 207, 301, 303, 402, but not limited thereto). The interface circuit 6202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 6202 performing data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps 204, 208, 209, 304, 305, 403, 202, 206, 302, 401, but not limited thereto).
[0401] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0402] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0403] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0404] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. A beam management method, executed by a network device, characterized in that, The method includes: Obtain a first measurement report; the first measurement report includes a second measurement report reported by the terminal at least twice; the second measurement report is an event-triggered Layer 1 measurement report; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam; Verify the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report; Beam management is based on the validated first measurement report.
2. The beam management method according to claim 1, characterized in that, The step of verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes: The validity of each submitted second measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each submitted second measurement report; The validity of the first measurement report is verified based on the validity of each second measurement report submitted.
3. The beam management method according to claim 2, characterized in that, The determination of the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes: If at least one first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
4. The beam management method according to claim 2, characterized in that, The determination of the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes: If each first candidate beam is valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each second measurement report reported each time; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1.
5. The beam management method according to claim 2, characterized in that, The determination of the validity of each reported second measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes: If each first candidate beam and each second candidate beam are valid, the second measurement report reported each time is determined to be valid; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event in all M measurement windows; the second candidate beam being valid means that the first candidate beam does not satisfy the triggering condition of the measurement event at least once in the M measurement windows; M is an integer greater than 1.
6. The beam management method according to any one of claims 2 to 5, characterized in that, The verification of the validity of the first measurement report based on the validity of each reported second measurement report includes: The first ratio of the number of valid second measurement reports to the total number of reports; If the first ratio is greater than the first threshold, the first measurement report is determined to be valid.
7. The beam management method according to claim 1, characterized in that, The step of verifying the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in the first measurement report includes: The validity of the first measurement report is determined based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report.
8. The beam management method according to claim 7, characterized in that, The determination of the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes: The total number of valid first candidate beams and valid second candidate beams is determined. The first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report. The second candidate beam is the candidate beam whose condition satisfaction indicator value is 0 in each reported second measurement report. A valid first candidate beam indicates that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows. A valid second candidate beam indicates that the first candidate beam fails to satisfy the triggering condition of the measurement event at least once within M measurement windows. M is an integer greater than 1. Determine a second ratio of the sum to the total number of all candidate beams included in the first measurement report; If the second ratio is greater than the second threshold, the first measurement report is determined to be valid.
9. The beam management method according to claim 7, characterized in that, The determination of the validity of the first measurement report based on the condition satisfaction indicator corresponding to the candidate beam in each reported second measurement report includes: The third ratio of the number of valid first candidate beams to the total number of all first candidate beams is determined; the first candidate beam is the candidate beam whose condition satisfaction indicator value is 1 in each reported second measurement report; the first candidate beam being valid means that the first candidate beam satisfies the triggering condition of the measurement event within M measurement windows; M is an integer greater than 1; If the third ratio is greater than the third threshold, the first measurement report is determined to be valid.
10. The beam management method according to any one of claims 1 to 9, characterized in that, The beam management based on the verified first measurement report includes at least one of the following: If the first measurement report is valid, beam switching is performed based on the first measurement report; If the first measurement report is valid, beam reselection is performed based on the first measurement report; If the first measurement report is valid, beam resources are reallocated based on the first measurement report; If the first measurement report is invalid, instruct the terminal to re-perform the event-triggered Layer 1 measurement.
11. The beam management method according to any one of claims 1 to 10, characterized in that, The method further includes: Send a first message to the terminal; the first message contains the number M of measurement windows during beam measurement, where M is an integer greater than 1.
12. A beam management method, executed by a terminal, characterized in that, The method includes: A second measurement report is sent to the network device; the second measurement report contains a condition satisfaction indicator corresponding to the candidate beam; the condition satisfaction indicator is used to verify the validity of the second measurement report.
13. The beam management method according to claim 12, characterized in that, The method includes: Obtain the indication information sent by the network device; the indication information is used to instruct the terminal to re-perform the event-triggered Layer 1 measurement; Re-perform the layer 1 measurement triggered by the event.
14. The beam management method according to any one of claims 12 to 13, characterized in that, The method includes: Measure the signal quality of the candidate beam within M measurement windows; M is an integer greater than 1; If all candidate beams in the M measurement windows meet the triggering conditions of the measurement event, the value of the condition satisfaction indicator corresponding to the candidate beams included in the second measurement report is marked as 1.
15. The beam management method according to claim 14, characterized in that, The method includes: Obtain the first message sent by the network device; the first message contains the value of M.
16. A communication device, characterized by The communication device is used to perform the beam management method according to any one of claims 1 to 11, or the beam management method according to any one of claims 12 to 15.
17. A communication system, characterized in that, The device includes a terminal and a network device, wherein the network device is configured to implement the beam management method according to any one of claims 1 to 11, and the terminal is configured to implement the beam management method according to any one of claims 12 to 15.
18. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the beam management method according to any one of claims 1 to 11, or the beam management method according to any one of claims 12 to 15.
19. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the beam management method according to any one of claims 1 to 11, or the beam management method according to any one of claims 12 to 15.
