Event monitoring method, communication apparatus, program product and storage medium

Abstract

An event monitoring method, a communication apparatus, a program product and a storage medium. In the method, in a timer, after the occurrence of an event is continuously detected within a duration of the timer of a terminal apparatus, or the number of times the occurrence of the event is continuously detected reaches a first number of times, the terminal apparatus reports information of one or more beams to a network apparatus. In this way, the number of times of reporting by a terminal device can be relatively reduced, unnecessary reporting or inappropriate scenario reporting can also be excluded to a certain extent, and therefore the accuracy and reliability of reporting beam information by the terminal apparatus can be improved. Moreover, the network apparatus can more accurately determine a mobility management policy on the basis of the reported beam information, thereby ensuring the quality of communication between the terminal apparatus and the network apparatus.

Description

Method of monitoring an event, communication device, program product and storage medium

[0001] Cross-reference to related applications

[0002] This application claims priority to the Chinese patent application No. 202411089162.7, filed on August 8, 2024, entitled "Method of monitoring an event, communication device, program product and storage medium", the entire content of which is incorporated herein by reference. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a method of monitoring an event, a communication device, a program product and a storage medium. BACKGROUND

[0004] Mobile management (MM) is a key component in wireless mobile communication, which determines the smooth switching and stable connection between terminal devices in different cells and beams. Layer 1 (L1) / layer 2 (L2) triggered mobility (LTM) is a technology for mobility management. Under the LTM technology, the terminal device can report the L1 measurement results to the base station, and the base station determines whether to switch the beam based on the L1 measurement results. In order to reduce the reporting, an event-triggered reporting mechanism is introduced. The event may be, for example, beam failure.

[0005] However, in the scenario where the speed of movement between the terminal device and the base station is relatively large, it may cause frequent triggering of events, thereby triggering the terminal device to report, resulting in low reliability of the reporting. SUMMARY

[0006] The present application provides a method of monitoring an event, a communication device, a program product and a storage medium, which are used to improve the reliability of the reporting.

[0007] In a first aspect, the embodiments of the present application provide a method for monitoring an event. Alternatively, the embodiments of the present application provide a method for detecting an event. The method can be applied to a terminal device side. The terminal device side can be the terminal device itself, or can be the terminal device or a module in the terminal device, such as a communication module in the terminal device, a circuit or a chip responsible for communication functions. The terminal device can be a server or a module in the server, such as a communication module in the server, a circuit or a chip responsible for communication functions, such as a modem chip, also known as a baseband chip, or a system on chip (SoC) chip or a system in package (SIP) chip containing a modem core, etc. For ease of description, the method performed by the terminal device is described below. The method comprises: starting a timer, and monitoring whether the event occurs within the timer; when the timer expires, determining whether the count value of a counter is equal to an initial value, the counter being used to accumulate the number of times that it is monitored that the event does not occur; if the counter is equal to the initial value, reporting the information of one or more beams that are monitored, or if the counter is not equal to the initial value, restarting the timer and resetting the counter.

[0008] For example, the event can be related to at least one of the one or more beams, such as the event can be used to monitor the quality of the one or more beams.

[0009] In the embodiments of the present application, in the case where the timer expires and the count value of the counter is equal to the initial value, the information (such as the information of the one or more beams) is reported, which is equivalent to reporting only when the event occurs continuously before the timer expires. In this way, the continuity of the event is ensured, which ensures that the event is reported after the event is stable, reduces unnecessary reporting or inappropriate scene reporting, and improves the reliability and accuracy of the reporting. Since the terminal device has higher reliability, the network side (such as a network device) can improve the accuracy and reliability of the mobility management based on the terminal device reporting to ensure the communication quality of the terminal device.

[0010] In a possible implementation, the method further comprises: within the timer, when the physical (PHY) layer of the terminal device monitors that the event does not occur once, the PHY layer sends first information to the media access control (MAC) layer of the terminal device, the first information indicating that the event does not occur; and the MAC layer of the terminal device adds a first value to the count value of the counter.

[0011] In this way, the MAC layer can be explicitly informed that no event occurs, so as to accurately count. In addition, since the probability that no event occurs is generally lower than the probability that an event occurs, the PHY layer informs the MAC layer that no event occurs, thereby reducing the number of interactions between the PHY layer and the MAC layer.

[0012] In a possible implementation, the method further includes: if the counter is equal to the initial value, restarting the timer and resetting the counter. In this way, the timer and the counter can be used for subsequent event monitoring.

[0013] In a possible implementation, the event includes: the quality of a serving beam of the terminal device is less than a threshold value, the serving beam belongs to one or more beams; the quality of a candidate beam of the terminal device is higher than the quality of the serving beam of the terminal device by a threshold value, the serving beam and the candidate beam belong to one or more beams; or, the absolute value of the difference between the quality of the serving beam of the terminal device and the quality of the candidate beam of the terminal device is less than a threshold value, the serving beam and the candidate beam belong to one or more beams.

[0014] In this way, the conditions of the serving beam and / or the candidate beam can be monitored, so that the network device can more accurately manage the switching of the beams and / or the cells based on the reported information of the serving beam and / or the candidate beam.

[0015] In a possible implementation, the method further includes: receiving third information, the third information being used to configure the timer.

[0016] In this way, the terminal device does not need to be built-in with the duration of the timer, and the network device can flexibly configure the duration of the timer.

[0017] In a second aspect, the embodiments of the present application provide a method for monitoring an event. Alternatively, the embodiments of the present application provide a method for detecting an event. The method can be applied to the terminal device side. The content of the terminal device side can refer to the content of the terminal device side discussed in the first aspect above, which will not be repeated here. The method includes: starting a timer, and monitoring whether an event occurs in the timer; if it is monitored that no event occurs, restarting the timer; or, if it is monitored that an event occurs and the timer is timed out, reporting information of one or more beams.

[0018] For example, the event can be related to at least one of the one or more beams, such as the event can be used to monitor the quality of the one or more beams.

[0019] In the embodiments of the present application, the reporting of information (such as information of one or more beams) in the case of expiration of the timer is equivalent to reporting only when the event continues to occur before expiration of the timer. In this way, the continuity of the event is ensured, which ensures reporting after the event is stable, reduces unnecessary reporting or inappropriate scene reporting, and improves the reliability and accuracy of reporting. Since the terminal device has higher reliability, the network side (such as a network device) can improve the accuracy and reliability of mobility management based on the reporting of the terminal device to ensure the communication quality of the terminal device. In addition, the determination of whether to report according to whether the timer expires can reduce the complexity and cost of monitoring the event.

[0020] In a possible implementation, if it is detected that the event does not occur, the timer is restarted, including: if the PHY layer of the terminal device detects that the event does not occur once within the timer, the first information is sent to the MAC layer of the terminal device, the first information indicating that the event does not occur; and the MAC layer restarts the timer.

[0021] In this way, the MAC layer can clearly determine that the event does not occur, so as to accurately count. In addition, since the probability of the event not occurring is generally lower than the probability of the event occurring, the PHY layer informs the MAC layer that the event does not occur, which can reduce the number of interactions between the PHY layer and the MAC layer.

[0022] In a possible implementation, the method further includes: if the PHY layer of the terminal device detects that the event occurs once within the timer, the second information is sent to the MAC layer of the terminal device, and the MAC layer of the terminal device continues to count the timer, wherein the second information indicates that the event occurs; or, the PHY layer of the terminal device detects that the event occurs once within the timer, and the MAC layer of the terminal device does not receive information from the PHY layer, the timer is continued to count.

[0023] In this way, two ways for the MAC layer to determine that the event does not occur are provided. In the way that the MAC layer can receive the second information from the PHY layer and clearly determine whether the event occurs, the MAC layer can directly determine whether the event occurs to accurately control the timer. Alternatively, the MAC layer determines that the event does not occur when no information is received from the PHY layer, which relatively reduces the interaction between the MAC layer and the PHY layer.

[0024] In a possible implementation, the method further includes: if the event is detected to occur and the timer expires, the timer is restarted. In this way, the timer can be used for subsequent event monitoring.

[0025] In a possible implementation, the event includes: a quality of a serving beam of the terminal device is less than a threshold, the serving beam belongs to one or more beams; a quality of a candidate beam of the terminal device is higher than the quality of the serving beam of the terminal device by a threshold, the serving beam and the candidate beam belong to the one or more beams; or, a difference between the quality of the serving beam of the terminal device and the quality of the candidate beam of the terminal device is less than a threshold, the serving beam and the candidate beam belong to the one or more beams.

[0026] In this way, the situation of the serving beam and / or the candidate beam can be monitored, and the network device can more accurately manage the switching of the beam and / or the cell based on the reported information of the serving beam and / or the candidate beam.

[0027] In a possible implementation, the method further includes: receiving third information, the third information being used for configuring the timer.

[0028] In this way, the terminal device does not need to have a built-in timer, and the network device can flexibly configure the duration of the timer.

[0029] In a third aspect, an embodiment of the present application provides a method for monitoring an event. Alternatively, an embodiment of the present application provides a method for detecting an event. The method can be applied to the terminal device side. The content of the terminal device side can refer to the content of the terminal device side discussed in the first aspect above, which is not repeated here. The method includes: starting a timer, and monitoring whether the event occurs in the timer; if it is monitored that the event does not occur, resetting a counter; or, if it is monitored that the event occurs and a count value of the counter reaches a first number of times, reporting information of one or more beams.

[0030] For example, the event can be related to at least one of the one or more beams, such as the event can be used to monitor the quality of the one or more beams.

[0031] In the embodiment of the present application, if the count value of the counter reaches the first number of times in the timer, the information (such as the information of the one or more beams) is reported, which is equivalent to continuously monitoring that the event occurs for the first number of times before reporting. In this way, the continuity of the event is ensured, which ensures that the reporting is performed after the event stably occurs, reduces unnecessary reporting or reporting in inappropriate scenarios, and improves the reliability and accuracy of the reporting. Since the terminal device has higher reliability, the network side (such as the network device) is facilitated to have higher accuracy and reliability in mobility management based on the reporting of the terminal device, so as to ensure the communication quality of the terminal device. In addition, whether to report is determined according to whether the counter exceeds the first number of times, which facilitates to reduce the modification of the counter and the timer, so as to reduce the cost of monitoring the event.

[0032] In a possible implementation, if it is monitored that the event does not occur, the counter is reset, including: in the timer, the PHY layer of the terminal device monitors that the event does not occur once, and sends first information to the MAC layer of the terminal device, the first information indicating that the event does not occur; and the MAC layer resets the counter.

[0033] In this way, the MAC layer can be informed that the event does not occur, so as to accurately count. In addition, since the probability that the event does not occur is generally lower than the probability that the event occurs, the PHY layer informs the MAC layer that the event does not occur, which is beneficial to reducing the number of interactions between the PHY layer and the MAC layer.

[0034] In a possible implementation, in the timer, the PHY layer of the terminal device monitors that the event occurs once, and sends second information to the MAC layer of the terminal device, where the second information indicates that the event occurs; and the MAC layer adds a first value to the count value of the counter, where the first value is, for example, 1, 2, or 3. In this way, the MAC layer can be informed that the event occurs, so as to accurately count.

[0035] In a possible implementation, the method further includes: if it is monitored that the event occurs and the count value of the counter reaches a first value, restarting the timer and resetting the counter. In this way, the timer and the counter can be used for subsequent event monitoring.

[0036] In a possible implementation, the event includes: the quality of a serving beam of the terminal device is less than a threshold value, the serving beam belongs to one or more beams; the quality of a candidate beam of the terminal device is higher than the quality of the serving beam of the terminal device by a threshold value, the serving beam and the candidate beam belong to one or more beams; or, the absolute value of the difference between the quality of the serving beam of the terminal device and the quality of the candidate beam of the terminal device is less than a threshold value, the serving beam and the candidate beam belong to one or more beams.

[0037] In this way, the conditions of the serving beam and / or the candidate beam can be monitored, so as to facilitate the network device to more accurately manage the switching of the beams and / or the cells based on the reported information of the serving beam and / or the candidate beam.

[0038] In a possible implementation, the method further includes: receiving third information, where the third information is used to configure the timer and the first number.

[0039] In this way, the terminal device does not need to be built-in with the duration of the timer and the first number, and the network device can flexibly configure the timer and the first number.

[0040] In a fourth aspect, the embodiments of the present application provide a method for monitoring an event. Alternatively, the embodiments of the present application provide a method for detecting an event. The method can be applied to a network device side. The network device side refers to a network device or a module in the network device. The module in the network device, for example, refers to a communication module in the network device, a circuit or a chip responsible for a communication function. The network device, for example, refers to a network device or a module in the network device. The module in the network device, for example, refers to a communication module in the network device, a circuit or a chip responsible for a communication function. The chip, for example, refers to a modem chip, also known as a baseband chip, or a SoC chip or a SIP chip containing a modem core. For ease of description, the method performed by the network device is taken as an example for description. The method comprises: sending third information, the third information being used for configuring a timer; and receiving information from one or more beams of a terminal device in a case where a counter of the terminal device is equal to an initial value, the counter being used for accumulating a number of times that an event is not detected within the timer.

[0041] In a possible implementation, the event can be related to at least one of the one or more beams.

[0042] In a possible implementation, the event comprises: a quality of a serving beam of the terminal device being less than a threshold value, the serving beam belonging to the one or more beams; a quality of a candidate beam of the terminal device being higher than a quality of the serving beam of the terminal device by a threshold value, the serving beam and the candidate beam belonging to the one or more beams; or, a difference between the quality of the serving beam of the terminal device and the quality of the candidate beam of the terminal device being less than a threshold value, the serving beam and the candidate beam belonging to the one or more beams.

[0043] In a fifth aspect, the embodiments of the present application provide a method for monitoring an event. Alternatively, the embodiments of the present application provide a method for detecting an event. The method can be applied to a network device side. The content of the network device side can refer to the content of the network device side discussed in the fourth aspect, which is not listed here. For ease of description, the method performed by the network device is taken as an example for description. The method comprises: sending third information, the third information being used for configuring a timer; and receiving information from one or more beams of a terminal device in a case where the timer is timed out, the timer being restarted in a case where the event is not detected, and the timer continuing to count in a case where the event is detected.

[0044] In a possible implementation, the event can be related to at least one of the one or more beams.

[0045] In a possible implementation, the event includes: a quality of a serving beam of the terminal device is less than a threshold, the serving beam belonging to the one or more beams; a quality of a candidate beam of the terminal device is higher than the quality of the serving beam of the terminal device by the threshold, the serving beam and the candidate beam belonging to the one or more beams; or, an absolute value of a difference between the quality of the serving beam of the terminal device and the quality of the serving beam of the terminal device is less than a threshold, the serving beam and the candidate beam belonging to the one or more beams.

[0046] In a sixth aspect, an embodiment of the present application provides a method for monitoring an event. Alternatively, an embodiment of the present application provides a method for detecting an event. The method can be applied to a network device side. The content of the network device side can refer to the content of the network device side discussed in the first aspect, which is not listed here. For ease of description, the following takes the network device executing the method as an example for introduction. The method includes: sending third information, the third information being used for configuring a timer and a first number of times; in a case where a count value of the counter reaches the first number of times, receiving information of one or more beams from a terminal device, the counter being restarted when it is monitored that the event does not occur, and continuing counting when it is monitored that the event occurs.

[0047] In a possible implementation, the event can be related to at least one of the one or more beams.

[0048] In a possible implementation, the event includes: a quality of a serving beam of the terminal device is less than a threshold, the serving beam belonging to the one or more beams; a quality of a candidate beam of the terminal device is higher than the quality of the serving beam of the terminal device by the threshold, the serving beam and the candidate beam belonging to the one or more beams; or, an absolute value of a difference between the quality of the serving beam of the terminal device and the quality of the serving beam of the terminal device is less than a threshold, the serving beam and the candidate beam belonging to the one or more beams.

[0049] In a seventh aspect, an embodiment of the present application provides a method for monitoring an event. Alternatively, an embodiment of the present application provides a method for detecting an event. The method can be applied to a MAC layer of a terminal device side. The content of the terminal device side can refer to the content of the terminal device side discussed in the first aspect, which is not listed here. The method includes: the MAC layer of the terminal device receiving first information from a physical (PHY) layer of the terminal device, the first information indicating that the event does not occur.

[0050] In a possible implementation, the method further includes: based on the first information, if it is determined that the event occurs continuously within a time length of a timer, or the number of times that the event occurs continuously within the timer reaches a first number of times, the MAC layer reports information of one or more beams.

[0051] In a possible implementation, the event occurs continuously within the time length of the timer, including:

[0052] In the case that the timer expires, the count value of the counter of the terminal device is equal to the initial value, wherein the count value of the counter is used to accumulate the number of times that the event is not monitored to occur within the timer.

[0053] In a possible implementation, after the MAC layer of the terminal device receives the first information from the physical (PHY) layer of the terminal device, the method further includes: adding the count value of the counter by a first value.

[0054] In a possible implementation, the method further includes: in the case that the event occurs within the timer, maintaining the count value of the counter.

[0055] In a possible implementation, the event is continuously monitored to occur within the duration of the timer, including: the timer expires, wherein the timer is restarted in the case that the event is not monitored to occur, and continues to count in the case that the event is monitored to occur.

[0056] The event is continuously monitored to occur within the duration of the timer, including: after the MAC layer of the terminal device receives the first information from the physical (PHY) layer of the terminal device, the method further includes: the MAC layer restarts the timer.

[0057] In a possible implementation, the method further includes: in the case that the MAC layer receives the second information from the PHY layer within the timer, the MAC layer continues to count the timer, wherein the second information indicates that the event occurs; or,

[0058] In the case that the MAC layer does not receive the information from the PHY layer of the terminal device within the timer, the timer continues to count.

[0059] In a possible implementation, the number of times that the event is continuously monitored to occur within the timer reaches a first number of times, including: the count value of the counter of the terminal device is equal to the first number of times, the count value of the counter is reset to an initial value in the case that the event is not monitored to occur, and continues to count in the case that the event is monitored to occur.

[0060] In a possible implementation, the method further includes: in the case that the MAC layer receives the first information from the PHY layer within the timer, the first information indicates that the event does not occur; the MAC layer resets the count value of the counter to the initial value.

[0061] In a possible implementation, the method further includes: in the case that the MAC layer of the terminal device receives the second information from the PHY layer within the timer, and the MAC layer adds the count value of the counter by a first value, wherein the second information indicates that the event occurs.

[0062] In a possible implementation, the method further includes: restarting the timer after the condition is met, where the condition includes at least one of the following: the event is continuously monitored within the first time length; the number of times that the event is continuously monitored within the timer reaches a first number; the related information of the event is reported; or, the timer is timed out.

[0063] In a possible implementation, the event is related to at least one of the one or more beams.

[0064] In a possible implementation, the event includes: a quality of a serving beam of the terminal device is less than a threshold, the serving beam belongs to the one or more beams; a quality of a candidate beam of the terminal device is higher than a quality of the serving beam of the terminal device by a threshold, the serving beam and the candidate beam belong to the one or more beams; or, a difference between a quality of a serving beam of the terminal device and a quality of a candidate beam of the terminal device is less than a threshold, the serving beam and the candidate beam belong to the one or more beams.

[0065] In an eighth aspect, an embodiment of the present application provides a method for monitoring an event. Alternatively, an embodiment of the present application provides a method for detecting an event. The method can be applied to a PHY layer of a terminal device side. The content of the terminal device side can refer to the content of the terminal device side discussed in the first aspect, which is not listed here. The method includes: within a timer, a physical layer PHY of the terminal device monitors that an event does not occur, and then sends first information to a medium access control MAC layer of the terminal device, where the first information indicates that the event does not occur.

[0066] In a possible implementation, the method further includes: within the timer, the PHY layer of the terminal device monitors that the event occurs, and then sends second information to the MAC layer of the terminal device, where the second information indicates that the event occurs.

[0067] In a ninth aspect, an embodiment of the present application provides a communication device. For example, the communication device includes a communication unit (sometimes also referred to as a communication module). Optionally, the communication device further includes a processing unit (sometimes also referred to as a processing module). The communication unit is configured to perform a transceiving operation, such as functions related to sending and receiving; the communication unit can be referred to as a transceiving unit; optionally, the communication unit includes a receiving unit and a sending unit. The processing unit is configured to perform a processing operation. Alternatively, the communication unit can be a transmitter and a receiver, or the communication unit is a transmitter and a receiver. Optionally, the communication device further includes a storage unit (sometimes also referred to as a storage module).

[0068] In a first embodiment, the communication device can be the terminal device side in the first aspect described above, or a module (for example, a chip system) configured in the terminal device side, etc. The communication device includes means or modules for performing the corresponding means or modules in the first aspect or any possible implementation of the first aspect.

[0069] For example, the processing unit is used to start a timer and monitor whether an event has occurred within the timer; when the timer expires, it determines whether the count value of the counter is equal to the initial value, and the counter is used to accumulate the number of times the event has not occurred; if the counter is equal to the initial value, the communication unit is used to report the information of one or more beams that have been monitored, or if the counter is not equal to the initial value, the processing unit is used to restart the timer and reset the counter.

[0070] In one possible implementation, the communication device may also implement the contents of any of the possible implementations in the first aspect described above, which will not be listed here.

[0071] In the second embodiment, the communication device can be the terminal device side described in the second aspect above, or a module (e.g., a chip system) configured in the terminal device side. This communication device includes corresponding means or modules for performing the second aspect or any possible implementation thereof.

[0072] For example, the processing unit is used to start a timer and monitor whether an event has occurred within the timer; if no event is detected, the processing unit restarts the timer; or, if an event is detected and the timer times out, the communication unit is used to report information from one or more beams.

[0073] In one possible implementation, the communication device may also implement any of the possible implementations in the second aspect described above, which will not be listed here.

[0074] In a third embodiment, the communication device can be the terminal device side described in the third aspect above, or a module (e.g., a chip system) configured in the terminal device side. This communication device includes corresponding means or modules for performing the third aspect or any possible implementation thereof.

[0075] For example, the processing unit is used to start a timer and monitor whether an event has occurred within the timer; if no event is detected, the processing unit is used to reset the counter; or, if an event is detected and the counter's count value reaches the first count, the communication unit is used to report information from one or more beams.

[0076] In one possible implementation, the communication device may also implement the contents of any of the possible implementations in the third aspect described above, which will not be listed here.

[0077] In a tenth aspect, an embodiment of the present application provides a communication apparatus. For example, the communication apparatus includes a communication unit (sometimes also referred to as a communication module). Optionally, the communication apparatus further includes a processing unit (sometimes also referred to as a processing module). The communication unit is configured to perform a transceiving operation, such as functions related to transmitting and receiving; the communication unit can be referred to as a transceiving unit; optionally, the communication unit includes a receiving unit and a transmitting unit. The processing unit is configured to perform a processing operation. Alternatively, the communication unit can be a transmitter and a receiver, or the communication unit is a transmitter and a receiver. Optionally, the communication apparatus further includes a storage unit (sometimes also referred to as a storage module).

[0078] In a first embodiment, the communication apparatus can be the network apparatus side in the fourth aspect above, or a module (e.g., a chip system) configured in the network apparatus side, etc. The communication apparatus includes corresponding means or modules for performing the fourth aspect above or any possible implementation of the fourth aspect.

[0079] For example, the communication unit is configured to transmit the first information, and receive the information from the one or more beams of the terminal apparatus in a case where a counter of the terminal apparatus is equal to an initial value.

[0080] In a possible implementation, the communication apparatus can further implement the content of any possible implementation of the fourth aspect above, which is not listed here.

[0081] In a second embodiment, the communication apparatus can be the network apparatus side in the fifth aspect above, or a module (e.g., a chip system) configured in the network apparatus side, etc. The communication apparatus includes corresponding means or modules for performing the fifth aspect above or any possible implementation of the fifth aspect.

[0082] For example, the communication unit is configured to transmit the first information, and receive the information from the one or more beams of the terminal apparatus in a case where the timer is expired.

[0083] In a possible implementation, the communication apparatus can further implement the content of any possible implementation of the fifth aspect above, which is not listed here.

[0084] In a third embodiment, the communication apparatus can be the network apparatus side in the sixth aspect above, or a module (e.g., a chip system) configured in the network apparatus side, etc. The communication apparatus includes corresponding means or modules for performing the sixth aspect above or any possible implementation of the sixth aspect.

[0085] For example, the communication unit is configured to transmit the first information, and receive the information from the one or more beams of the terminal apparatus in a case where a count value of the counter reaches a first number of times.

[0086] In a possible implementation, the communication apparatus can also implement the content of any possible implementation of the sixth aspect above, which is not listed here.

[0087] Optionally, the communication apparatus in the embodiments of the present application can also implement any method discussed in the seventh aspect, the eighth aspect, any possible implementation of the seventh aspect, or any possible implementation of the eighth aspect.

[0088] In an eleventh aspect, the embodiments of the present application provide a communication apparatus. The communication apparatus includes one or more processors. The one or more processors can execute computer programs or instructions in a memory, when the computer programs or instructions are executed, make the communication apparatus implement the method discussed in any of the first aspect to the eighth aspect and any possible implementation of the first aspect to the eighth aspect.

[0089] Optionally, the communication apparatus can include a memory, in which case the memory can be coupled with the one or more processors, or the memory can be independently disposed relative to the one or more processors. Alternatively, the memory exists independently relative to the communication apparatus.

[0090] In a possible design, the communication apparatus can also include an interface circuit, wherein the processor is configured to communicate with other apparatuses or components through the interface circuit.

[0091] In the implementation process, the communication apparatus can be a chip, and the processor can be a transistor, a gate circuit, a flip-flop, and various logic circuits, etc. The specific implementation of the processor is not limited in the embodiments of the present application.

[0092] In an implementation, the communication apparatus can be a wireless communication device, i.e., a computer device supporting wireless communication function. Specifically, the wireless communication device can be a terminal device such as a smart phone, or a network device such as a wireless access network device (e.g., a base station).

[0093] In yet another implementation, the communication apparatus can be part of a device in a wireless communication device, such as an integrated circuit product including a system chip or a communication chip. The system chip can also be referred to as a SoC or SoC chip. The communication chip can include a baseband processing chip and a radio frequency processing chip. The baseband processing chip is also sometimes referred to as a modem or a baseband chip. The radio frequency processing chip is also sometimes referred to as a radio frequency transceiver or a radio frequency chip. In physical implementation, part or all of the chips in the communication chip can be integrated inside the SoC chip. For example, the baseband processing chip is integrated in the SoC chip, and the radio frequency processing chip is not integrated with the SoC chip. The interface circuit can be a radio frequency processing chip in the wireless communication device, and the processor can be a baseband processing chip in the wireless communication device. The interface circuit can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuitry on the chip or chip system. The processor can also be embodied as a processing circuit or a logic circuit.

[0094] In yet another implementation, the communication apparatus can be a chip system, which can be composed of a chip or can include a chip and other discrete devices. The chip system can include, for example, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chip.

[0095] In a twelfth aspect, an embodiment of the present application provides a communication system.

[0096] In a possible embodiment, the communication system includes the communication apparatus of any one of the first embodiment of the first aspect to the ninth aspect, and the communication apparatus of any one of the first embodiment of the tenth aspect.

[0097] In another possible embodiment, the communication system includes the communication apparatus of any one of the second embodiment of the first aspect to the ninth aspect, and the communication apparatus of any one of the second embodiment of the tenth aspect.

[0098] In yet another possible implementation form of the communication system, the communication system comprises the communication device of any one of the third implementation form of the ninth aspect, and the communication device of any one of the third implementation form of the tenth aspect.

[0099] In a thirteenth aspect, an embodiment of the present application provides a chip system. The chip system comprises a processor. Optionally, the chip system further comprises an interface (e.g., a communication interface). The processor is configured to implement the method discussed in any one of the first aspect to the eighth aspect and any possible implementation form of the first aspect to the eighth aspect.

[0100] Optionally, the chip system further comprises a memory. The memory is configured to store a computer program (also referred to as code or instructions). The processor is configured to invoke and run the computer program from the memory, so that the device installed with the chip system performs the method discussed in any one of the first aspect to the eighth aspect and any possible implementation form of the first aspect to the eighth aspect. The implementation form of the chip system can refer to the content of the chip system involved in the foregoing, which will not be listed here.

[0101] In a fourteenth aspect, an embodiment of the present application provides a computer readable storage medium. The computer readable storage medium is configured to store a computer program or instructions, which, when executed, implement the method discussed in any one of the first aspect to the eighth aspect and any possible implementation form of the first aspect to the eighth aspect.

[0102] In a fifteenth aspect, an embodiment of the present application provides a computer program product. When the computer program product is executed, the processor performs the method discussed in any one of the first aspect to the eighth aspect and any possible implementation form of the first aspect to the eighth aspect. The computer program product comprises a computer program and / or instructions, etc.

[0103] The beneficial effects of any technical solution in the fourth aspect to the fifteenth aspect can refer to the beneficial effects of the corresponding technical solution in the first aspect to the third aspect, which will not be listed here. BRIEF DESCRIPTION OF DRAWINGS

[0104] FIG. 1 and FIG. 2 are schematic diagrams of architectures of two communication systems to which embodiments of the present application are applicable;

[0105] FIG. 3 is a schematic diagram of a control plane protocol stack of a terminal device and a network device to which embodiments of the present application are applicable;

[0106] FIG. 4 is a schematic diagram of an architecture of a network device;

[0107] FIG. 5 is a schematic diagram of a process for monitoring beam failure provided by an embodiment of the present application;

[0108] FIG. 6 is a schematic diagram of a network device switching a beam provided by an embodiment of the present application;

[0109] FIG. 7 is a schematic diagram of a method for monitoring an event according to an embodiment of the present application;

[0110] FIG. 8 is a schematic diagram of a process for monitoring an event according to an embodiment of the present application;

[0111] FIG. 9 is a schematic diagram of another method for monitoring an event according to an embodiment of the present application;

[0112] FIG. 10 is a schematic diagram of a process for monitoring an event according to an embodiment of the present application;

[0113] FIG. 11 is a schematic diagram of yet another method for monitoring an event according to an embodiment of the present application;

[0114] FIG. 12 is a schematic diagram of a process for monitoring an event according to an embodiment of the present application;

[0115] FIGS. 13 to 15 are schematic diagrams of three communication apparatuses according to embodiments of the present application. DETAILED DESCRIPTION

[0116] The embodiments of the present application will be described in further detail below with reference to the drawings.

[0117] The technical solutions of the present application can be applied to various communication systems including network apparatus sides and terminal apparatus sides. The network apparatus side can refer to the network apparatus itself, or a module in the network apparatus, or a logic module or software capable of realizing all or part of the functions. The terminal apparatus side can refer to the terminal apparatus itself, or a module in the terminal apparatus, or a logic module or software capable of realizing all or part of the functions.

[0118] The various communication systems (or communication networks, or systems, etc.) to which the embodiments of the present application are applicable include, for example, satellite communication systems, 5th-Generation (5G) New Radio (NR) systems, Long Term Evolution (LTE) systems, Wideband Code Division Multiple Access (WCDMA) systems, Global System for Mobile Communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wireless Local Area Network (WLAN) systems, Bluetooth systems, and Zigbee systems. thThe present application can be applied to a 5th generation, 5G, communication system or a new radio, NR, communication system, a future communication system, a device-to-device, D2D, communication system, a machine to machine, M2M, communication system, an internet of things, IoT, communication system, or other communication system, etc. The 5G communication system includes a non-standalone, NSA, 5G communication system and / or a standalone, SA, 5G communication system. In addition, various embodiments of the present application can also be applied to various converged communication systems, such as a converged system of a satellite communication system and a 5G communication system, etc. In addition, the technical solutions of the embodiments of the present application can also be applied to a wireless local area network, WLAN, etc. Optionally, various embodiments of the present application can also be applied to a multiple input multiple output, MIMO, system.

[0119] For ease of description, in various embodiments of the present application, the network device side is taken as the network device, and the terminal device side is taken as the terminal device. The network device in the following can be replaced by the network device side, and the terminal device can also be replaced by the terminal device side.

[0120] The communication system to which the embodiments of the present application are applicable will be described below with reference to the architecture diagram of the communication system shown in FIG. 1. As shown in FIG. 1, the communication system 1000 includes an access network (AN) 100. Optionally, the communication system can also include a core network (CN) 200 and an Internet 300. The access network 100 can include at least one network device (or network equipment, or network side equipment), such as 110a and 110b in FIG. 1. Among them, 110a is a base station, and 110b is a micro station. The communication system 1000 can also include at least one terminal device (or terminal equipment), such as 120a to 120j in FIG. 1. 120a, 120e, 120f and 120j are mobile phones, 120b is a car, 120c is a fuel dispenser, 120d is a home access point (HAP) arranged indoors or outdoors, 120g is a notebook computer, 120h is a printer, and 120i is a drone. The same terminal device or the same network device can provide different functions in different application scenarios. For example, the mobile phones in FIG. 1 are 120a, 120e, 120f and 120j, the mobile phone 120a can access the base station 110a, connect the car 120b, communicate directly with the mobile phone 120e and access the HAP, the car 120b can access the HAP and communicate directly with the mobile phone 120a, the mobile phone 120f can access the micro station 110b, connect the notebook computer 120g and the printer 120h, and the mobile phone 120j can control the drone 120i.

[0121] 1. Network device

[0122] The network device is a network side device with wireless transceiving function. The network device can be a device, equipment or module with corresponding communication function located at the network side of the communication system. The network device is usually provided with a communication module, circuit or chip for performing corresponding communication function, and a program instruction and corresponding program instruction for performing corresponding communication function. The network device can include a core network device and / or an access network device.

[0123] The access network device can be a device in a radio access network (RAN) that provides wireless communication functions for a terminal device, which can be referred to as a RAN device. The RAN can be an access network in the 3rd generation partnership project (3GPP), such as a 4G, 5G, or future-oriented communication network. The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a communication network of two or more of the above networks.

[0124] The RAN device can also be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, an access node in a WiFi system, or the like. The RAN device includes, for example, but is not limited to, a base station (BS), a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, home evolved Node B, or home Node B (HNB)), a baseband unit (BBU), a wireless fidelity (WiFi) access point (AP), a wireless relay node, a wireless backhaul node, a transmission and reception point (TRP; or, transmission point (TP)), and the like. Among them, the base station is a device deployed in a wireless access network that can provide wireless communication functions, and can also be referred to as a base station device, for example, an evolved Node B (eNB or e-NodeB) in an LTE system, a Node B (NB), a base station (gNodeB or gNB) in a 5G system, a base station in a future evolution system, and the like. The base station can include a BBU and a remote radio unit (RRU). The BBU and the RRU can be placed in different places, for example, RRU pullout, placed in a high traffic area, and the BBU placed in a central machine room. The BBU and the RRU can also be placed in the same machine room. The BBU and the RRU can also be different components under one rack. The base station can be in the form of a macro base station, a micro base station (also known as a small station), a pico base station, a relay station, an access point, or a balloon station, and the like.

[0125] The RAN device can also be a module or unit that completes the function of the base station part, for example, can be a centralized unit / control unit (CU), can also be a distributed unit (DU), and can also be a radio unit (RU). The CU and the DU can be separately arranged, or can also be included in the same network element, for example, in a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, for example, included in a remote radio unit (RRU), an active antenna processing unit (AAU), or a remote radio head (RRH). The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0126] In different systems, the CU (or central unit control plane (CU-CP), central unit user plane (CU-UP)), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be referred to as O-CU (open CU), the DU can also be referred to as O-DU, the CU-CP can also be referred to as O-CU-CP, the CU-UP can also be referred to as O-CU-UP, and the RU can also be referred to as O-RU. Any one of the CU (or CU-CP, CU-UP), DU and RU in the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module. The RAN device can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node, etc.

[0127] In the embodiments of the present application, the functions of the network device can also be performed by a module (such as a chip) in the network device, or by a control subsystem containing the functions of the network device. The control subsystem containing the functions of the network device herein can be a control center in the above-mentioned application scenarios such as smart grid, industrial control, intelligent transportation, and smart city.

[0128] 2, terminal device

[0129] A terminal device is a user-side device with wireless transceiving function. The terminal device can also be referred to as a terminal apparatus, a terminal, a user equipment (UE), a mobile station, a mobile terminal, etc. The terminal device can be widely applied to various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IOT), virtual reality, augmented reality, industrial control, automatic driving, remote medical, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, transportation safety, or smart home, etc.

[0130] The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a notebook computer, a palm computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, a mobile station (MS), a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handset, a laptop computer, or a machine type communication (MTC) terminal, etc. The wearable device can be, for example, a mobile internet device (MID), a wearable device, a head mounted display (HMD), a virtual reality (VR) device (such as VR glasses), an augmented reality (AR) device (such as AR glasses), a mixed reality (MR) device, or a road side unit (RSU), etc. The terminal device is usually provided with a communication module, circuit or chip that performs a corresponding communication function, and is also provided with program instructions configured to perform the corresponding communication function. In various embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system or a combination device or component that can implement the function of the terminal device, which can be installed in the terminal device. The embodiments of the present application do not limit the specific technology and specific equipment form adopted by the terminal device.

[0131] In the embodiments of the present application, the function of the terminal device can also be performed by a module (such as a chip or a modem) in the terminal device, or by a device containing the function of the terminal device.

[0132] The network device and the terminal device can be fixed in position or mobile. The network device and the terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can be deployed on water; and can be deployed on aircraft, balloons and artificial satellites in the air. Embodiments of the present application do not limit the application scenarios of the network device and the terminal device.

[0133] The roles of the network device and the terminal device can be relative. For example, the helicopter or the unmanned aerial vehicle 120i in FIG. 1 can be configured as a mobile network device, and for terminal devices 120j that access the wireless access network 100 through 120i, the terminal device 120i is a network device; but for the network device 110a, 120i is a terminal device, that is, 110a and 120i communicate through a wireless air interface protocol. Of course, 110a and 120i can also communicate through an interface protocol between network devices and network devices, and in this case, 120i is also a network device relative to 110a. Therefore, the network device and the terminal device can be collectively referred to as a communication device, and 110a and 110b in FIG. 1 can be referred to as a communication device with a network device function, and 120a-120j in FIG. 1 can be referred to as a communication device with a terminal device function.

[0134] FIG. 2 shows a schematic diagram of an architecture of a communication system to which embodiments of the present application are applicable. The communication system includes a terminal device and at least one network device. The terminal device is located in the coverage of one or more cells (or carriers) managed by the network device, and the cell providing services for the terminal device can be one or more. In the case where there are multiple cells providing services for the terminal device, the terminal device can work in a carrier aggregation (CA) or dual connectivity (DC) or coordinated multipoint transmission manner, and at least one of the multiple cells can provide at least two numerologies for the terminal device and provide wireless resources for the terminal device.

[0135] For example, FIG. 2 shows that the network device includes a network device #1, a network device #2 and a network device #3, and the terminal device is located in the coverage of the cell managed by the network device #1, the cell managed by the network device #2 and the cell managed by the network device #3. The network device #1 can be a macro base station (macro gNB or macro g-NodeB, etc.), and the network device #2 and the network device #3 can be small base stations (small gNB or small g-NodeB, etc.), without limiting the specific implementation of the network device.

[0136] FIG. 3 shows a schematic diagram of a control plane (CP) protocol stack of a terminal device and a network device to which embodiments of the present application are applicable. The control plane protocol stack refers to a protocol cluster used for control signaling transmission.

[0137] As shown in FIG. 3, the control plane protocol stack of the terminal device includes a non-access stratum (NAS) layer, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a media access control (MAC) layer, and a physical (PHY) layer. Among them, the PDCP layer, the RLC layer, and the MAC layer belong to the L2 layer. The PHY layer belongs to the L1 layer. The control plane protocol stack of the network device includes the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer.

[0138] The NAS layer of the terminal device can communicate with a core network element. The RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the terminal device can respectively communicate with the RRC layer, the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the network device.

[0139] FIG. 4 shows a schematic diagram of an architecture of a network device. FIG. 4 shows a network device of a CU-DU separation architecture, which can also be referred to as a distributed architecture or a distributed deployment architecture.

[0140] As shown in FIG. 4, the network device is logically divided into (or includes) a CU and one or more DUs. Each DU is connected to the CU through an F1 interface, and information exchange between different DUs can be completed based on forwarding of the CU. The CU and the DU can be physically arranged together or physically separated, which is not limited. The CU can support functions of the RRC layer, the PDCP layer, and a service data adaptation protocol (SDAP) layer, and the DU can support functions of the RLC layer, the MAC layer, and the PHY layer.

[0141] The network architecture and scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. It can be known by those skilled in the art that, with the evolution of network architecture and the appearance of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical scenarios or technical problems.

[0142] The network device performs beam failure management depending on the information reported by the terminal device. The following describes a mechanism for the terminal device to report beam failure.

[0143] In one possible mechanism, the terminal device can report beam failure based on event triggering. For example, the terminal device reports beam failure to the network device once the terminal device monitors (or detects) beam failure. In this mechanism, the terminal device frequently reports information about beam failure.

[0144] In another possible mechanism, the terminal device can report beam failure based on a timer (or also referred to as a time window) and a value M. M is a positive integer, and M represents the maximum number of times of beam failure. In this mechanism, if the terminal device monitors beam failure M times within the timer, the terminal device initiates reporting to the network device.

[0145] The following describes a process of monitoring beam failure with reference to a process diagram of monitoring beam failure shown in FIG. 5. In FIG. 5, the horizontal axis represents time, and “√” represents monitoring beam failure, and “×” represents not monitoring beam failure. In FIG. 5, the length of the timer T is 20 milliseconds (ms), and the value M is 5.

[0146] In FIG. 5, (1) shows a process diagram of monitoring beam failure. As shown in (1) of FIG. 5, the terminal device starts the timer at t0, that is, the timer starts counting from t0, and restarts the counter to 0, that is, the counter starts counting from 0. At t1, if the terminal device monitors beam failure, the counter value is added by a first value, for example, 1, that is, the counter value is 1, and the timer is restarted, that is, the timer starts counting from 0. At t2, if the terminal device monitors beam failure, the counter value is added by 1, that is, the counter value is 2, and the timer is restarted. At t3, if the terminal device monitors beam failure, the counter value is added by 1, that is, the counter value is 3, and the timer is restarted.

[0147] At the t4 moment, the terminal device does not monitor the beam failure, the counting value of the counter is kept, that is, the counting value of the counter is still 3, and the timer continues to count. At the t5 moment, the terminal device monitors the beam failure, the counting value of the counter is kept, that is, the counting value of the counter is increased by 1, and the timer is restarted. At the t6 moment, the terminal device does not monitor the beam failure, the counting value of the counter is kept, that is, the counting value of the counter is still 4, and the timer continues to count. At the t7 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 5. Since the counting value of the counter is 5, the terminal device reports the beam failure information, and restarts the timer and resets the counter.

[0148] Fig. 5 (2) shows an example of reporting the beam failure. As shown in Fig. 5 (2), the terminal device starts the timer at the t0 moment, and resets the counting value of the counter to 0. At the t1 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 1, and the timer is restarted. At the t2 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 2, and the timer is restarted. At the t3 moment, the terminal device does not monitor the beam failure, the counting value of the counter is kept, that is, the counting value of the counter is still 2, and the timer continues to count.

[0149] At the t4 moment, the terminal device does not monitor the beam failure, the counting value of the counter is kept, that is, the counting value of the counter is 2, and the timer continues to count. At the t5 moment, the timer is timed out, the timer is restarted and the counter is reset. At the t6 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 1, and the timer is restarted. At the t7 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 2, and the timer is restarted. At the t8 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 3, and the timer is restarted. At the t9 moment, the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 4, and the timer is restarted. At the t10 moment, the timer has not been timed out, and the terminal device monitors the beam failure, the counting value of the counter is increased by 1, that is, the counting value of the counter is 5. Since the counting value of the counter is 5, the terminal device reports the beam failure information, and restarts the timer and resets the counter.

[0150] In some scenarios, for example, the relative speed between the network device and the terminal device is large, the terminal device may report the beam failure information, resulting in the network device issuing an incorrect switching instruction.

[0151] The following introduces a network device switching beam in conjunction with a schematic diagram of a network device switching beam shown in FIG. 6. FIG. 6 is an example in which beam 1 is a service beam of a terminal device and beam 2 is another beam of a network device.

[0152] As shown in FIG. 6, the terminal device is initially located between the coverage ranges of the two beams, beam 1 and beam 2. The terminal device can monitor beam failure multiple times. After a period of time, the terminal device moves along a moving direction to a center position of the coverage range of beam 1 and can occasionally monitor beam failure one or two times, causing the count value of the counter to accumulate to M. Therefore, the terminal device sends information about beam failure to the network device. The network device issues an incorrect switching instruction based on the information about beam failure, such as switching the service beam of the terminal device from beam 1 to another beam, resulting in poor communication quality of the terminal device.

[0153] Therefore, the embodiments of the present application provide a scheme for monitoring an event. In the scheme, the terminal device reports information about one or more beams to the network device after continuously monitoring occurrence of the event within a time length of a timer or after continuously monitoring occurrence of the event a certain number of times (such as a first number of times). In this way, the number of times of reporting of the terminal device can be relatively reduced, and unnecessary reporting or inappropriate scene reporting can be excluded to some extent, thereby improving the accuracy and reliability of the terminal device reporting information about the beams. In addition, the network device can determine a mobility management strategy more accurately based on the reported information about the beams, thereby ensuring the communication quality between the terminal device and the network device.

[0154] The following introduces some nouns involved in the scheme for monitoring an event provided by the embodiments of the present application. When not particularly stated, these explanations are to support the meanings of the nouns and make the embodiments of the present application easier to understand, and should not be regarded as strict limitations on the terms in the claimed protection scope of the present application.

[0155] 1. A reference signal (RS), which can also be referred to as a pilot signal or pilot, for example, can be a signal provided by a transmitting end to a receiving end for channel estimation, channel sounding, or data demodulation, etc. The reference signal can include a demodulation reference signal (DMRS), a sounding reference signal (SRS), a channel state information-reference signal (CSI-RS), a cell-specific reference signal (C-RS / CRS), or a positioning reference signal (P-RS / PRS), a synchronization signal, a phase tracking reference signal (PTRS), or a sensing reference signal (SERS).

[0156] The DMRS can include, for example, a DMRS for physical uplink control channel (PUCCH) demodulation (which can be referred to as DMRS for PUCCH for short) and a DMRS for physical uplink share channel (PUSCH) demodulation (which can be referred to as DMRS for PUSCH for short).

[0157] The synchronization signal can be (or include) one or more of the following: a synchronization signal (SS), a synchronization signal block (SSB), or a synchronization signal and physical broadcast channel block (SS / PBCH block / SSB). The synchronization signal involved in various embodiments of the present application can also be replaced by a synchronization signal block (SSB), or a synchronization signal and PBCH block (ss-PBCH / SS-PBCH block / SSB), etc., which is not limited herein.

[0158] The reference signals that can be used for monitoring beam failure can be collectively referred to as beam failure detection (BFD) reference signals (RSs). The BFD RSs include, for example, SSBs or CSI-RSs.

[0159] There are various reference signals, and the names of the reference signals can change as the standards evolve, and more reference signals can also appear, which are not specifically limited.

[0160] 2. Mobility management is a key component in wireless mobile communication, which determines the smooth switching and stable connection between different cells and beams of a terminal device. In the idle state and the deactivated state of the terminal device, mobility management mainly involves cell selection and reselection processes; in the connected state, mobility management mainly refers to cell handover. Mobility management includes cell handover management and beam switching management, etc. LTM management is a technology for cell handover. Beam failure (or beam failure) management is a technology for switching beams.

[0161] The network device generally determines whether to perform cell selection / reselection, cell handover, or beam switching, etc. based on the monitoring of the terminal device on signals or events. Among them, monitoring can also be called detection or detection, etc. The name is not limited. Monitoring refers to monitoring whether a specific event exists within a period of time.

[0162] 3. Event refers to an event related to mobility management. The event can be used to trigger or trigger mobility management, or mobility management depends on the occurrence of the event, or the occurrence of the event is the basis of mobility management. The event involved in the embodiments of the present application can be an event related to cell selection / reselection, cell handover or beam switching, such as an event related to LTM management or an event related to beam failure management.

[0163] The content of the event can be various, and the embodiments of the present application do not specifically limit it. Optionally, the event can be used to monitor the quality of one or more beams. For example, the event in the embodiments of the present application includes but is not limited to any of the events shown in (1) to (16) below. (1) to (6) below are events related to LTM management. (7) to (16) below are events related to beam switching.

[0164] (1) Event LTM1, which means that the beam of the serving cell is better than an absolute threshold. Event LTM1 specifically, for example, means that the quality of the beam of the serving cell is greater than the absolute threshold. The quality of the beam can be represented, for example, by the reference signal received power (RSRP) corresponding to the beam. For example, the network device sends a reference signal to the terminal device through a certain beam, and the quality of the beam can be represented by the RSRP of the reference signal measured by the terminal device.

[0165] (2) Event LTM2, which means that the beam of the serving cell is worse than an absolute threshold. Event LTM2 specifically, for example, means that the quality of the beam of the serving cell is less than the absolute threshold.

[0166] (3) Event LTM3, which means that the beam of the candidate cell is better than the beam of the serving cell by a certain offset, or in other words, the beam of the serving cell is worse than the beam of the candidate cell by a certain offset. Event LTM3 specifically, for example, means that the quality of the beam of the candidate cell is greater than the quality of the beam of the serving cell by a certain threshold.

[0167] (4) Event LTM4, which means that the beam of the candidate cell is better than an absolute threshold. Event LTM4 specifically, for example, means that the quality of the beam of the candidate cell is greater than the absolute threshold.

[0168] (5) Event LTM5, which means that the beam of the serving cell is worse than an absolute threshold 1 and the beam of the candidate cell is better than an absolute threshold 2. Event LTM5 specifically, for example, means that the quality of the beam of the serving cell is less than the absolute threshold 1 but the quality of the beam of the candidate cell is greater than the absolute threshold 2.

[0169] (6) Event LTM6, which means that the beam of the candidate cell is better than the beam of the secondary cell by a certain offset. Event LTM6 specifically, for example, means that the quality of the beam of the candidate cell is higher than the quality of the beam of the secondary cell by a certain offset.

[0170] (7) Event-1, which means that the quality of the current beam is lower than a certain threshold.

[0171] (8) Event-2, which means that the L1-RSRP of a new beam is higher than the L1-RSRP of a current beam by a certain threshold.

[0172] (9) Event-3, which means that the quality of a new beam is better than a certain threshold.

[0173] (10) Event-4, which means that the quality of a current beam is worse than a threshold 1, and the quality of at least one new beam is better than a threshold 2.

[0174] (11) Event-5, which means that the absolute value of the difference between the quality of a current beam and the quality of at least one new beam is lower than a threshold.

[0175] (12) Event-6, which means that a current beam is not in the best K>1 beams. Event-6 generally occurs when the configured beams for measurement and reporting are not sufficient.

[0176] (13) Event-7a, which means that the quality of at least one new beam (e.g. L1-RSRP) is higher than the worst quality of the RS derived from the activated transmission configuration indication (TCI) state by a threshold.

[0177] (14) Event-7b, which means that the quality of at least one new beam (e.g. L1-RSRP) is higher than the best quality of the RS derived from the activated TCI state by a threshold.

[0178] (15) Event-8, which means that the quality of M>1 new beams, e.g. L1-RSRP, is higher than a current beam by a threshold.

[0179] (16) Event-9, which means that the quality of at least one new beam, e.g. L1-RSRP, is higher than the quality of a configured reference RS (which can be SSB or CSI-RS) by a threshold.

[0180] The above (1) to (16) are examples of events, and in fact, the content of the events may change as the standard evolves, or more events may appear, which are not specifically limited.

[0181] The current beam involved in any of the above (1) to (16) can be referred to or replaced as a serving beam of the terminal device, and the new beam can be regarded as or replaced as an alternative beam (or alternative beam) of the terminal device.

[0182] 4、 the information of the beam refers to the information of the beam reported by the terminal device to the network device after monitoring the event, the information is associated with (or related to or relevant to) the event monitored by the terminal device, or in other words, the beam is related to the event.

[0183] The information of the beam can include the identification (or index, number or serial number, etc.) of the beam, and the quality information of the beam. The beam may, for example, be a serving beam or an alternative beam of the terminal device, and the like, without limitation. The quality information of the beam reflects the quality of the beam, which may, for example, be represented by L1-RSRP. The information of the beam, for example, includes multiple qualities, average quality, maximum quality, or minimum quality of a certain beam monitored, and the like, without specific limitation. Optionally, the information of the beam is carried in a beam report, for example.

[0184] The scheme for monitoring the event provided by the embodiments of the present application will be described below with reference to the accompanying drawings. In the corresponding drawings of various embodiments of the present application, the steps represented by dashed lines are optional steps. In addition, the terminal device involved in various embodiments of the present application is, for example, any of the terminal devices involved in FIGS. 1 to 3, the PHY layer of the terminal device is, for example, the PHY layer involved in FIG. 3, the MAC layer of the terminal device is, for example, the MAC layer involved in FIG. 3, and the network device is, for example, any of the network devices involved in FIGS. 1, 2 or 4, or the CU and / or DU involved in FIG. 4, etc. In addition, as the standard continues to evolve, the name and / or function of the device may change, which is not limited.

[0185] The method for monitoring the event provided by the embodiments of the present application will be described below with reference to the flowchart of the method for monitoring the event shown in FIG. 7.

[0186] S701, the terminal device starts a timer and monitors whether the event occurs within the timer.

[0187] The timer can also be referred to as a time window. The timer can be set in the terminal device, for example, in the MAC layer of the terminal device. The timer can be a software timer, a hardware timer, or a combination of software and hardware timer, without limitation. The duration of the timer can be pre-configured or pre-defined in the terminal device, or indicated (or configured) by the network device to the terminal device. The duration of the timer can also be referred to as the timing duration of the timer or the duration of the timer. It is the maximum timing duration of the timer that is set. After the duration of the timer is exceeded, the timer is considered to have expired. For example, the duration of the timer is 40 ms, i.e., the timing duration of the timer is 40 ms. The duration of the timer may, for example, also be 20 ms, 30 ms, 60 ms or 80 ms, etc., without limitation on the value of the duration of the timer.

[0188] For example, the network device sends the third information to the terminal device. Correspondingly, the terminal device receives the third information from the network device. For example, the DU sends the third information to the terminal device, or the CU sends the third information to the terminal device through the DU. The third information is used to configure (indicate or determine) a timer. It can also be described as the third information is used to configure, used to indicate or used to determine the duration of the timer. For example, the third information includes information of the duration of the timer. The information of the duration of the timer includes, for example, the value of the duration of the timer, or the index of the duration of the timer, etc., which is not specifically limited. The third information can be carried in RRC signaling or other signaling, which is not specifically limited. After the terminal device receives the third information, the counter can be reset to an initial value. The initial value can be understood as the value of the counter when it is reset, or the value when the counter starts counting. The initial value is, for example, 0 or 1, etc., and the value of the initial value is not limited.

[0189] The terminal device can periodically or aperiodically monitor whether the event occurs within the timer. Within the timer means from the time after the timer starts to the time before the timer expires. Within the timer can also be understood as within the elapsed time of the timer. The elapsed time is the time counted after the timer starts. Optionally, the event can be used to monitor the quality of one or more beams. The one or more beams include, for example, the serving beam and / or the alternative beam of the terminal device, etc. The rest of the content of the event can refer to the content of the event discussed in the foregoing, which is not listed here. Optionally, the terminal device monitoring whether the event occurs can be that the PHY layer in the terminal device monitors that an event does not occur once.

[0190] If the terminal device periodically monitors whether the event occurs, the duration of the period in which the terminal device monitors whether the event occurs (or the period in which the terminal device monitors the event) is less than the duration of the timer. For the sake of description, the period in which the terminal device monitors whether the event occurs is simply referred to as the monitoring period below. The duration of the monitoring period is, for example, 1 / P of the duration of the timer, where P is a positive integer. The monitoring period can be indicated by the network device to the terminal device, such as the monitoring period can be carried in RRC signaling or other signaling. Optionally, the monitoring period can also be carried in the third information.

[0191] If the event is used to monitor the quality of one or more beams, the terminal device can monitor the quality of one or more beams, and thereby determine whether the event occurs based on the quality of one or more beams. The event can be, for example, any one of events (1) to (16) discussed in the foregoing explanatory section or other events. The content of the event is different, and the way in which the terminal device monitors whether the event occurs is also different, which is illustrated below by way of examples 1 to 3.

[0192] Example 1, the event is event-1 described above, i.e., the event is that the quality of the serving beam is less than a threshold. The serving beam is one of the one or more beams.

[0193] Under example 1, the terminal device, such as a PHY layer of the terminal device, can monitor the strength of the reference signal transmitted through the serving beam, determine the L1-RSRP, and determine whether the L1-RSRP is less than the threshold. If the L1-RSRP is less than the threshold, it is determined that the event occurs (event meet). If the L1-RSRP is greater than or equal to the threshold, it is determined that the event does not occur (event not meet).

[0194] Example 2, the event is event-2 described above, i.e., the L1-RSRP of the alternative beam is higher than the L1-RSRP of the serving beam by a threshold. The alternative beam and the serving beam are one of the one or more beams.

[0195] Under example 2, the terminal device can monitor the L1-RSRP of the reference signal transmitted through the serving beam, and monitor the L1-RSRP of the reference signal transmitted through the alternative beam, and if the L1-RSRP of the alternative beam is higher than the L1-RSRP of the serving beam by a threshold, it is determined that the event occurs. If the L1-RSRP of the alternative beam is less than or equal to the L1-RSRP of the serving beam by a threshold, it is determined that the event does not occur.

[0196] Example 3, the event is event-5 described above, i.e., the absolute value of the difference between the quality of the serving beam and the quality of at least one alternative beam is lower than a threshold. The at least one alternative beam and the serving beam are one of the one or more beams.

[0197] Under example 3, the terminal device can monitor the L1-RSRP of the reference signal transmitted through the serving beam, and monitor the L1-RSRP of the reference signal transmitted through the at least one alternative beam, and if the absolute value of the difference between the L1-RSRP of the at least one alternative beam and the L1-RSRP of the serving beam is less than a threshold, it is determined that the event occurs. If the absolute value of the difference between the L1-RSRP of any alternative beam and the L1-RSRP of the serving beam is greater than or equal to a threshold, it is determined that the event does not occur.

[0198] Examples 1 to 3 described above are examples of events, and in fact there are many possible events, which are not specifically limited.

[0199] S702, when the timer expires, the terminal device determines whether the count value of the counter is equal to the initial value.

[0200] If the count value of the counter is equal to the initial value when the timer expires, S703 is performed, i.e., the terminal device sends information of one or more beams to the network device. Correspondingly, the network device receives the information of one or more beams sent from the terminal device. If the count value of the counter is not equal to the initial value when the timer expires, S704 is performed, i.e., the timer is restarted and the counter is reset.

[0201] The counter of the embodiments of the present application can also be referred to as an event not meet counter. The counter can be arranged in the terminal device, for example, in the MAC layer of the terminal device. The counter can be a software counter, a hardware counter, or a combination of software and hardware counter, which is not limited. The counter is used to accumulate the number of times that the event is not met within the timer, or the count value of the counter represents the accumulated number of times (or the accumulation result) that the event is not met within the timer.

[0202] Any beam information in the information of one or more beams can refer to the content of the beam information discussed above. The one or more beams can be related (or associated or relevant) to the event. For example, at least one beam in the one or more beams can be the monitoring object of the event, for example, the event is used to monitor the communication between the network device and the terminal device, and the at least one beam is the beam on the network device side. For another example, at least one beam in the one or more beams can be the monitoring object of the event, for example, the event is used to monitor the quality of the at least one beam.

[0203] Optionally, after S703 is performed, the terminal device can also restart the timer and reset the counter. Restarting the timer means that the timer starts counting from 0, and resetting the counter means that the counter starts counting from the initial value. Optionally, in the case that the network device receives the information of one or more beams, mobility management can be performed, such as determining to switch the service beam or the service cell of the terminal device, etc. In the case of S704, it is equivalent that the terminal device does not need to report the information of one or more beams to the network device.

[0204] For example, the terminal device monitors whether the event occurs once in the timer. If the terminal device monitors that the event does not occur once, the terminal device adds a first value to the count value of the counter. The first value is, for example, 1, 2, 3, or 4, etc. The first value can be a fixed value pre-stored in the terminal device. If the terminal device monitors that the event occurs once, the terminal device keeps the count value of the counter, and the timer continues to count. Alternatively, the terminal device does not perform additional operations on the counter and the timer. If the terminal device performs one monitoring on whether the event occurs, and the monitoring monitors that the event does not occur, it means that the terminal device monitors that the event does not occur once. If the terminal device performs one monitoring on whether the event occurs, and the monitoring monitors that the event occurs, it means that the terminal device monitors that the event occurs.

[0205] By analogy, if the count value of the counter is still the initial value within the duration of the timer, it means that the event is continuously (or always) monitored within the duration of the timer. On the contrary, if the count value of the counter is not the initial value, it means that the event is monitored not to occur within the duration of the timer, i.e., the event is not continuously monitored within the duration of the timer.

[0206] In the case that the terminal device monitors whether the event occurs at the PHY layer of the terminal device, if the PHY layer monitors that the event does not occur, the PHY layer can send first information to the MAC layer of the terminal device. Correspondingly, the MAC layer receives the first information from the PHY layer. The first information indicates that the event does not occur. Optionally, if the event is associated with one or more beams, the first information can carry the identification of the one or more beams, which is used to indicate that the event does not occur. The MAC layer adds a first value to the count value of the counter, and continues to count the timer.

[0207] If the PHY layer monitors that the event occurs, the PHY layer can send second information to the MAC layer. Correspondingly, the MAC layer receives the second information from the PHY layer, and the MAC layer can keep the count value of the counter, and continue to count the timer. Optionally, if the event is associated with one or more beams, the second information can carry the identification of the one or more beams, which is used to indicate that the event occurs. Alternatively, if the PHY layer monitors that the event occurs, the PHY layer can not need to send information to the MAC layer. In this way, the MAC layer does not need to operate the counter, and the interaction between the PHY layer and the MAC layer can be reduced.

[0208] In another possible embodiment, the PHY layer sends the first information to the MAC layer, or the MAC layer receives the first information from the PHY layer can be as a mandatory step, and the other steps discussed in FIG. 7 can be as optional steps.

[0209] S703 and S704 are two cases that can occur during the monitoring event. If the counter is equal to the initial value, the steps of S703 are performed. If the counter is not equal to the initial value, the steps of S704 are performed.

[0210] For example, refer to FIG. 8, which is a process diagram of a monitoring event provided by an embodiment of the present application. FIG. 8(1) and FIG. 8(2) can be respectively regarded as a process diagram of a monitoring event, and both take the length of the timer as 60 ms, and take the first length as equal to the length of the timer as an example. The horizontal axis in FIG. 8 represents time, and “√” represents monitoring an event, and “×” represents not monitoring an event.

[0211] As shown in FIG. 8(1), the timer is started at t0. The PHY layer monitors an event at t1, and the count value of the counter is 0. The PHY layer monitors an event at t2, and the count value of the counter is 0. The PHY layer monitors that an event does not occur at t3, and notifies the MAC layer, and the MAC layer adds 1 to the count value of the counter. The PHY layer monitors an event at t4, and the count value of the counter is 1. The PHY layer monitors an event at t5, and the count value of the counter is 1. The PHY layer monitors an event at t6, and the count value of the counter is 1. At t7, the timer times out, and the count value of the counter is 1, which is not the initial value, so the terminal device does not report the information of one or more beams. In addition, the terminal device restarts the timer and resets the counter. At t8, the PHY layer monitors an event, and the count value is 0.

[0212] As shown in FIG. 8(2), the timer is started at t0. The PHY layer monitors an event at t1, and the count value of the counter is 0. The PHY layer monitors an event at t2, and the count value of the counter is 0. The PHY layer monitors an event at t3, and the count value of the counter is 0. The PHY layer monitors an event at t4, and the count value of the counter is 0. The PHY layer monitors an event at t5, and the count value of the counter is 0. The PHY layer monitors an event at t6, and the count value of the counter is 0. The PHY layer monitors an event at t7, and the count value of the counter is 0. The timer times out at t8, and the count value of the counter is 0, which is the initial value, so the terminal device reports the information of one or more beams. When the timer times out, the terminal device restarts the timer and resets the counter.

[0213] In the embodiments of the present application, the terminal device can report the information of one or more beams to the network device in the case that the terminal device continuously monitors the occurrence of the event within the timer. In this way, the reporting frequency of the terminal device can be reduced, and the accuracy and reliability of the information of the beams reported by the terminal device can be improved. In addition, the network device can determine the mobility management strategy more accurately based on the reported information of the beams, thereby ensuring the communication quality between the terminal device and the network device. Furthermore, the terminal device restarts the timer in the case that the count value of the counter of the terminal device is equal to the initial value when the timer expires, or in the case that the timer expires, without restarting the timer every time the occurrence of the event is monitored or not. Therefore, the operation of the terminal device on the timer can be reduced.

[0214] The method for monitoring an event provided by the embodiments of the present application will be described below in combination with the schematic diagram of a method for monitoring an event shown in FIG. 9.

[0215] S901, the terminal device starts a timer and monitors whether the event occurs within the timer.

[0216] The content of the timer, the content of the event, and the content of monitoring whether the event occurs can refer to the content of the timer, the content of the event, and the content of monitoring whether the event occurs discussed in S701 above, which will not be repeated here.

[0217] If the occurrence of the event is monitored and the timer expires, S902 is performed, that is, the terminal device sends the information of one or more beams to the network device. The content of the one or more beams, the content of the event, and the relationship between the one or more beams and the event can refer to the content of the one or more beams, the content of the event, and the relationship between the one or more beams and the event discussed in FIG. 7, which will not be repeated here. Correspondingly, the network device receives the information of one or more beams from the terminal device. Optionally, after S902 is performed, the terminal device restarts the timer. Optionally, in the case that the network device receives the information of one or more beams, mobility management can be performed, such as determining to switch the serving beam or the serving cell of the terminal device, and the like. If the occurrence of the event is not monitored, S903 is performed, that is, the timer is restarted.

[0218] If the terminal device monitors the occurrence of the event once within the timer, the timer is restarted based on the first information. If the terminal device monitors the occurrence of the event once within the timer, the MAC layer of the terminal device continues to count the timer. In this way, if the timer expires, it indicates that the occurrence of the event is continuously (or always) monitored within the time length of the timer. On the contrary, if the timer does not expire, it indicates that the occurrence of the event is not continuously monitored within the time length of the timer.

[0219] In the case that the terminal device's PHY layer monitors whether the event occurs, if the terminal device's PHY layer monitors that the event does not occur once within the timer, the terminal device's PHY layer sends first information to the terminal device's MAC layer. The first information indicates that the event does not occur. The terminal device's MAC layer restarts the timer based on the first information.

[0220] If the terminal device's PHY layer monitors that the event occurs once within the timer, the terminal device's PHY layer sends second information to the terminal device's MAC layer, and the terminal device's MAC layer continues to count the timer, the second information indicates that the event occurs. Or, if the terminal device's PHY layer monitors that the event occurs once within the timer, and the terminal device's MAC layer does not receive the information from the PHY layer, the terminal device's MAC layer continues to count the timer.

[0221] In another possible embodiment, the PHY layer sends the first information to the MAC layer, or in other words, the MAC layer receives the first information from the PHY layer can be as a mandatory step, in which case, the other steps discussed in FIG. 9 can be as optional steps.

[0222] For example, please refer to FIG. 10, which is an example diagram of monitoring the event provided by the embodiments of the present application. FIG. 10 takes the length of the timer as 40 ms as an example. In FIG. 10, the horizontal coordinate represents time, and “√” represents that the event is monitored, and “×” represents that the event is not monitored.

[0223] As shown in FIG. 10, the timer starts at t0. The PHY layer monitors that the event occurs at t1, and the timer continues to count. The PHY layer monitors that the event occurs at t2, and the timer continues to count. The PHY layer monitors that the event does not occur at t3, although the timer does not time out, but the timer is restarted, so the timer starts to count again from t3. The PHY layer monitors that the event occurs at t4, and the timer continues to count. The PHY layer monitors that the event occurs at t5, and the timer continues to count. The PHY layer monitors that the event occurs at t6, and the timer continues to count. The PHY layer monitors that the event occurs at t7, and the timer continues to count. The PHY layer monitors that the event occurs at t8, and the timer continues to count. The timer times out at t9, the terminal device reports the information of one or more beams, and restarts the timer.

[0224] In this embodiment, the terminal device can report information about one or more beams to the network device when it continuously detects events within a timer. This reduces the number of reports from the terminal device, improving the accuracy and reliability of the reported beam information. Furthermore, the network device can more accurately determine mobility management strategies based on the reported beam information, ensuring communication quality between the terminal device and the network device. Additionally, the terminal device can perform event monitoring based on a timer, eliminating the need for a counter and reducing the complexity and cost of event monitoring.

[0225] The following describes a method for monitoring events provided in this application, with reference to a schematic diagram of an event monitoring method shown in Figure 11.

[0226] S1101. The terminal device starts a timer to monitor whether an event has occurred within the timer.

[0227] The contents of the timer, the contents of the event, and the contents for monitoring whether an event has occurred can be referred to in the previous section S701 for the contents of the timer, the contents of the event, and the contents for monitoring whether an event has occurred, and will not be repeated here.

[0228] If an event is detected and the counter reaches its first count, S1102 is executed, whereby the terminal device sends information about one or more beams to the network device. Correspondingly, the network device receives information about one or more beams from the terminal device. Within the timer, after each detected event and incrementing the counter by the first value, the terminal device determines whether the counter has reached its first count. The content of the one or more beams, the content of the event, and the relationship between the one or more beams and the event can be described with reference to Figure 7, and will not be listed individually here. Optionally, after executing S1102, the terminal device restarts the timer and resets the counter. Optionally, when the network device receives information about one or more beams, mobility management can be performed, such as determining the serving beam or serving cell for the terminal device. If no event is detected, S1103 is executed, whereby the timer is restarted and the counter is reset.

[0229] The first number can be pre-configured or pre-defined in the terminal device, such as pre-configured or pre-defined in the terminal device by a protocol, or configured to the terminal device by a network device, such as the first number is carried in the third information, for example, the DU sends the third information to the terminal device, or the CU sends the third information to the terminal device through the DU, which is equivalent to that the network device configures the first number to the terminal device. The first number can be represented by M, where M is a positive integer greater than or equal to 1. The first number can be 3, 4, 5, 6, etc. The first number represents the maximum number of consecutive events detected. Alternatively, it can be understood that the first number can be used to trigger the terminal device to initiate reporting. For example, the third information includes the value of the first number, which is used to configure the first number.

[0230] For example, if the count value of the counter of the terminal device is equal to the first number, it is determined that the number of consecutive events detected in the timer reaches the first number. The counter resets to the initial value in the case of no event detection, and continues to count in the case of event detection. In this way, when the counter value of the counter is equal to the first number, it means that the event is continuously (or always) monitored in the duration of the timer. On the contrary, if the counter value of the counter is less than the first number, it means that the event is not continuously monitored in the duration of the timer, i.e., the event is not continuously monitored in the duration of the timer.

[0231] Optionally, if the counter value of the counter is less than the first number, but the timer is timed out, the terminal device also restarts the timer and the counter.

[0232] In the case that the terminal device monitors whether the event occurs at the PHY layer of the terminal device, when the terminal device monitors that no event occurs at the PHY layer of the terminal device, the first information is sent to the MAC layer of the terminal device. The content of the first information can refer to the content of the first information discussed above, which is not listed here. The MAC layer resets the count value of the counter to the initial value. If the terminal device monitors that an event occurs at the PHY layer of the terminal device within the timer, the second information is sent to the MAC layer of the terminal device, and the MAC layer adds 1 to the count value of the counter. The content of the second information can refer to the content of the second information discussed above, which is not listed here.

[0233] In one embodiment, the PHY layer sends the first information to the MAC layer, or the MAC layer receives the first information from the PHY layer, which can be an optional step. In this case, the other steps discussed in FIG. 11 can be optional steps.

[0234] For example, refer to FIG. 12, which is an example diagram of monitoring events according to an embodiment of the present application. In FIG. 12, the length of the timer is 80 ms, the first number M is 5, and the first value is 1. In FIG. 12, the horizontal axis represents time, and "√" represents monitoring an event, and "×" represents not monitoring an event.

[0235] As shown in FIG. 12, the timer is started at t0. The PHY layer monitors an event at t1, the counter is incremented by 1, the count value of the counter is 1, and the timer continues to count. The PHY layer monitors an event at t2, the counter is incremented by 1, the count value of the counter is 2, and the timer continues to count. The PHY layer monitors that an event does not occur at t3, the timer does not time out, the counter is reset, the counter is re-counted from t3, and the timer continues to count. The PHY layer monitors an event at t4, the counter is incremented by 1, the count value of the counter is 1, and the timer continues to count. The PHY layer monitors an event at t5, the counter is incremented by 1, the count value of the counter is 2, and the timer continues to count. The PHY layer monitors an event at t6, the counter is incremented by 1, the count value of the counter is 3, and the timer continues to count. The PHY layer monitors an event at t7, the counter is incremented by 1, the count value of the counter is 4, and the timer continues to count. The timer monitors an event at t8, the counter is incremented by 1, and the count value of the counter is 5. Since the count value of the counter reaches the first number at this time, the related information of the event is reported, and the timer is restarted and the counter is reset.

[0236] In an embodiment of the present application, the terminal device can report the information of one or more beams to the network device when the number of times of continuously monitoring an event reaches the first number. In this way, the number of times of reporting of the terminal device can be relatively reduced, and the accuracy and reliability of the terminal device reporting the information of the beam can be improved. In addition, the network device can determine the strategy of mobility management more accurately based on the reported information of the beam, and the communication quality between the terminal device and the network device is ensured. In addition, the terminal device can monitor an event according to the timer and the counter, and the change to the terminal device is relatively small.

[0237] Based on the same inventive concept, an embodiment of the present application provides a communication device. Any of the communication devices shown in FIGS. 13-15 is described below. The communication device can be any of the terminal devices shown in FIGS. 1-3, the PHY layer shown in FIG. 3, the MAC layer shown in FIG. 3, any of the network devices shown in FIGS. 1, 2, or 4, or the CU and / or DU shown in FIG. 4, and the like, or can be a module or the like of these devices, without specific limitation.

[0238] As shown in FIG. 13, the communication apparatus 1300 can include modules or units for implementing the above-described method embodiments. In one possible design, the communication apparatus 1300 includes a processing unit 1310 and a communication unit 1320. The communication unit 1320 is configured to perform transceiving operations, such as functions related to transmitting and receiving; the communication unit 1320 can be referred to as a transceiver; optionally, the communication unit 1320 includes a receiving unit and a transmitting unit. The processing unit 1310 is configured to perform processing operations. Alternatively, the communication unit 1320 can be a transmitter and a receiver, or the communication unit 1320 is a transmitter and a receiver. Optionally, the communication apparatus 1300 further includes a storage unit 1330. The storage unit 1330 is configured to store program codes or data of the apparatus. The storage unit 1330 is optional as shown in FIG. 13 by a dashed box.

[0239] In a first embodiment, the communication apparatus 1300 can be the terminal device in the method embodiments described above with reference to FIG. 7, a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device, or implement functions of the terminal device in the method embodiments shown in FIG. 7. For example, the communication apparatus 1300 is a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device.

[0240] In the above embodiment, the processing unit 1310 is configured to perform S701 and S702, and the communication unit 1320 is configured to perform the step of transmitting the information of one or more beams in S703, or the processing unit 1310 is configured to perform S704.

[0241] The communication apparatus 1300 can also implement other steps performed by the terminal device in the method embodiments described above with reference to FIG. 7, which are not listed one by one here.

[0242] In a second embodiment, the communication apparatus 1300 can be the network device in the method embodiments described above with reference to FIG. 7, a communication module in the network device, or a circuit or chip responsible for communication functions in the network device, or implement functions of the network device in the method embodiments shown in FIG. 7. For example, the communication apparatus 1300 is a communication module in the network device, or a circuit or chip responsible for communication functions in the network device.

[0243] In the above embodiment, the communication unit 1320 is configured to perform the step of receiving the information of one or more beams in S703, and optionally, is configured to perform the step of transmitting the third information.

[0244] The communication apparatus 1300 can also implement other steps performed by the network device in the method embodiments described above with reference to FIG. 7, which are not listed one by one here.

[0245] In a third embodiment, the communication apparatus 1300 can be the terminal device in the method embodiments of FIG. 9, a communication module in the terminal device, a circuit or chip responsible for communication functions in the terminal device, or the like, or implement the functions of the terminal device in the method embodiments of FIG. 9. For example, the communication apparatus 1300 is a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device.

[0246] In the above embodiments, the processing unit 1310 is configured to perform the steps of S901, and the communication unit 1320 is configured to perform the sending of the information of the one or more beams or the processing unit 1310 is configured to restart the timer, and the like.

[0247] The communication apparatus 1300 can also implement other steps performed by the terminal device in the method embodiments of FIG. 9, which are not listed one by one here.

[0248] In a fourth embodiment, the communication apparatus 1300 can be the network device in the method embodiments of FIG. 9, a communication module in the network device, a circuit or chip responsible for communication functions in the network device, or the like, or implement the functions of the network device in the method embodiments of FIG. 9. For example, the communication apparatus 1300 is a communication module in the network device, or a circuit or chip responsible for communication functions in the network device.

[0249] In the above embodiments, the communication unit 1320 is configured to perform the receiving of the information of the one or more beams, and the sending of the third information, and the like.

[0250] The communication apparatus 1300 can also implement other steps performed by the network device in the method embodiments of FIG. 9, which are not listed one by one here.

[0251] In a fifth embodiment, the communication apparatus 1300 can be the terminal device in the method embodiments of FIG. 11, a communication module in the terminal device, a circuit or chip responsible for communication functions in the terminal device, or the like, or implement the functions of the terminal device in the method embodiments of FIG. 11. For example, the communication apparatus 1300 is a communication module in the terminal device, or a circuit or chip responsible for communication functions in the terminal device.

[0252] In the above embodiments, the processing unit 1310 is configured to perform the steps of S1101, and the communication unit 1320 is configured to send the information of the one or more beams or the processing unit 1310 is configured to perform the steps of S1103, and the like.

[0253] The communication apparatus 1300 can also implement other steps performed by the terminal device in the method embodiments of FIG. 11, which are not listed one by one here.

[0254] In a sixth embodiment, the communication apparatus 1300 can be the network device, the communication module in the network device, the circuit or chip responsible for communication functions in the network device, or the like in the method embodiments of FIG. 11, or implement the functions of the network device in the method embodiments of FIG. 11. For example, the communication apparatus 1300 is the communication module in the network device, or the circuit or chip responsible for communication functions in the network device.

[0255] In the above embodiments, the communication unit 1320 is configured to perform the receiving of the information of one or more beams, the sending of the third information, and the like in S1102.

[0256] The communication apparatus 1300 can also implement other steps performed by the network device in the method embodiments of FIG. 11, which are not listed one by one here.

[0257] In a possible design, when the communication apparatus 1300 is the terminal device, the communication module in the terminal device, the access network device, or the communication module in the access network device, the function of the processing unit 1310 can be implemented by one or more processors. Specifically, the processor can include a Modem chip, or a System on Chip (SoC) chip or a SIP chip including a Modem core. The function of the communication unit 1320 can be implemented by the transceiver circuit.

[0258] In a possible design, when the communication apparatus 1300 is the circuit or chip responsible for communication functions in the terminal device, or the circuit or chip responsible for communication functions in the access network device, such as a Modem chip or a System on Chip (SoC) chip or a SIP chip including a Modem core, the function of the processing unit 1310 can be implemented by the circuit system including one or more processors or processor cores in the chip. The function of the communication unit 1320 can be implemented by the interface circuit or data transceiver circuit on the chip.

[0259] It can be understood that the division of the units in the above apparatus is only a logical function division, one function unit can be provided for each function, or two or more functions can be integrated in one function unit. In actual implementation, all or part of the units can be integrated into one physical entity, or distributed on different physical entities. In addition, the function units can be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is implemented in the form of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can implement the described functions by different methods for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0260] In one example, the functional units in any of the above apparatuses can be one or more integrated circuits configured to implement the above methods, for example, one or more application specific integrated circuits (ASICs), or, one or more central processing units (CPUs), one or more microcontroller units (MCUs), one or more DSPs, or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0261] In one example, the storage unit 1330 can include random access memory, flash memory, read only memory, programmable read only memory, electrically programmable read only memory, and / or registers, etc.

[0262] The communication apparatus shown in Fig. 14 is described below. As shown in Fig. 14, the communication apparatus 1400 includes a processor 1410. Optionally, the communication apparatus 1400 further includes an interface circuit 1420 and a memory 1430. The processor 1410 and the interface circuit 1420 are coupled to each other. It can be understood that the interface circuit 1420 can be a transceiver or an input / output interface. The memory 1430 is used to store instructions executed by the processor 1410 or to store input data required by the processor 1410 to execute instructions or to store data generated after the processor 1410 executes instructions. The interface circuit 1420 and the memory 1430 are optional modules, which are shown in a dashed box in Fig. 14. In addition, one processor 1410 and one memory 1430 are taken as an example in Fig. 14, and in fact, the number of the processor 1410 and the memory 1430 is not limited.

[0263] The communication apparatus 1400 is used to implement the method embodiments described in any of Figs. 7, 9 or 11. Optionally, the processor 1410 is used to implement the functions of the processing unit 1310 described above, and the interface circuit 1420 is used to implement the functions of the communication unit 1320 described above.

[0264] For example, the communication apparatus 1400 can be used to implement the functions of the terminal device in the method embodiments described in any of Figs. 7, 9 or 11, or the functions of the network device in the method embodiments described in any of Figs. 7, 9 or 11.

[0265] When the communication apparatus 1400 is a chip applied to a certain apparatus (such as the terminal apparatus or the network apparatus described above), the apparatus chip implements the functions of the apparatus in the method embodiments described above. The apparatus chip receives information from other modules (such as a radio frequency module or an antenna) in the apparatus, and the information is sent by other apparatuses to the apparatus; or the apparatus chip sends information to other modules (such as a radio frequency module or an antenna) in the apparatus, and the information is sent by the apparatus to other apparatuses. The communication apparatus 1400 here can be a baseband chip of a certain apparatus, or a DU or other modules, and the DU here can be a DU under the open radio access network (O-RAN) architecture.

[0266] The processor 1410 can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. The general-purpose processor can be a microprocessor or any conventional processor. In addition, the memory involved in each embodiment of the present application can include a volatile memory such as a random access memory (RAM). The memory can also include a non-volatile memory such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid state drive (SSD).

[0267] The communication apparatus shown in FIG. 15 is described below. As shown in FIG. 15, the communication apparatus 1500 includes a processor 1510 and a transceiver 1530. The processor 1510 can also be referred to as a processing unit, a processing board, a processing module, a processing apparatus, etc. The implementation of the processor 1510 can refer to the content of the processor 1410 in FIG. 14. The transceiver 1530 can also be referred to as a transceiving unit, a transceiver, a transceiving apparatus, etc. The transceiver 1530 includes a transmitter 1531, a receiver 1532 and an antenna 1533. Optionally, the transceiver 1530 can also include a radio frequency circuit, an input / output apparatus, etc., which are not limited in detail.

[0268] Optionally, the device in the transceiver 1530 for implementing the receiving function is regarded as a receiving module, and the device in the transceiver 1530 for implementing the sending function is regarded as a sending module, that is, the transceiver 1530 includes a receiver and a transmitter. The transceiver can also be referred to as a transceiver, a transceiving module, or a transceiving circuit, etc. The receiver can also be referred to as a receiver, a receiving module, or a receiving circuit, etc. The transmitter can also be referred to as a transmitter, a sending module, or a sending circuit, etc.

[0269] Optionally, the communication apparatus 1500 can further include a memory 1520, which can store computer program code and / or data.

[0270] The processor 1510 is mainly used for processing communication protocols and communication data, and controlling the communication apparatus 1500, executing software programs, processing data of the software programs, etc. The memory 1520 is mainly used for storing software programs and data. The radio frequency circuit is mainly used for conversion between baseband signals and radio frequency signals and processing of the radio frequency signals. The antenna 1533 is mainly used for transceiving radio frequency signals in the form of electromagnetic waves. The input / output apparatus, for example, a touch screen, a display screen, a keyboard, etc. is mainly used for receiving data input by a user and outputting data to the user.

[0271] When data needs to be sent, the processor 1510 performs baseband processing on the data to be sent, and outputs a baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and transmits a radio frequency signal through the antenna in the form of electromagnetic waves. When data is sent to the communication apparatus 1500, the radio frequency circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor 1510 converts the baseband signal into data and processes the data. For the convenience of description, only one memory 1520, one processor 1510 and one transceiver 1530 are shown in FIG. 15. In actual terminal products, there can be one or more processors 1510 and one or more memories 1520. The memory 1520 can also be referred to as a storage medium or a storage device, etc. The memory 1520 can be arranged independently of the processor 1510, or can be integrated with the processor 1510, which is not limited.

[0272] In the embodiments of the present application, the antenna and the radio frequency circuit having the transceiving function are regarded as the communication unit of the communication apparatus 1500, and the processor having the processing function is regarded as the processing unit of the communication apparatus 1500. The processor 1510 is used to perform the processing actions of the terminal apparatus or the network apparatus side in the method embodiments described in any one of FIG. 7, FIG. 9 or FIG. 11, and the transceiver 1530 is used to perform the transceiving actions of the terminal apparatus or the network apparatus side in the method embodiments described in any one of FIG. 7, FIG. 9 or FIG. 11.

[0273] When the communication device 1500 is a chip, the chip includes a processor and a transceiver. The transceiver can be an input / output circuit or a communication interface; the processor can be a processing module integrated on the chip or a microprocessor or an integrated circuit. Optionally, the chip can further include a memory. The sending operation of the terminal device or the network device in the method embodiments can be understood as the output of the chip, and the receiving operation of the terminal device or the network device in the method embodiments can be understood as the input of the chip.

[0274] The embodiments of the present application provide a communication system. The communication system includes a terminal device and a network device.

[0275] In a possible embodiment, the terminal device can implement the functions of the terminal device in the method embodiments shown in FIG. 7, and the network device can implement the functions of the network device in the method embodiments shown in FIG. 7.

[0276] In another possible embodiment, the terminal device can implement the functions of the terminal device in the method embodiments shown in FIG. 9, and the network device can implement the functions of the network device in the method embodiments shown in FIG. 9.

[0277] In yet another possible embodiment, the terminal device can implement the functions of the terminal device in the method embodiments shown in FIG. 11, and the network device can implement the functions of the network device in the method embodiments shown in FIG. 11.

[0278] The embodiments of the present application provide a chip system. The chip system includes a processor and an interface. The processor is configured to call and run instructions from the interface. When the processor executes the instructions, the method embodiments shown in any one of FIG. 7, FIG. 9 or FIG. 11 are implemented.

[0279] The embodiments of the present application provide a computer readable storage medium. The computer readable storage medium is configured to store computer programs or instructions. When the computer programs or instructions are executed, the method embodiments shown in any one of FIG. 7, FIG. 9 or FIG. 11 are implemented.

[0280] The embodiments of the present application provide a program product. When the program product is executed, the processor implements the method embodiments shown in any one of FIG. 7, FIG. 9 or FIG. 11. The program product is, for example, a computer program product, and specifically, for example, a computer program and / or instructions, etc. The processor is, for example, a processor running in a computer.

[0281] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are performed. The computer can be a general purpose computer, a special purpose computer, a computer network, a network device, a user equipment or other programmable apparatus. The computer programs or instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer programs or instructions can be transferred from one website site, computer, server or data center to another website site, computer, server or data center through wired or wireless manner. The computer readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center and the like integrated with one or more available media. The available media can be a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape; an optical medium, such as a digital video disc; a semiconductor medium, such as a solid state disk. The computer readable storage medium can be a volatile or non-volatile storage medium, or can include both volatile and non-volatile storage media.

[0282] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0283] The various digital numbers involved in the various embodiments of the present application are only used for differentiation for convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the serial number of the above processes does not mean the execution order, and the execution order of the processes should be based on its function and inherent logic.

Claims

1. A method of monitoring an event, characterized by, The method applied to a terminal device comprises: starting a timer, and monitoring whether an event occurs within the timer; when the timer expires, determining whether a count value of a counter is equal to an initial value, the counter being used to accumulate a number of times that it is monitored that the event does not occur; if the counter is equal to the initial value, reporting information of one or more beams that is monitored, or if the counter is not equal to the initial value, restarting the timer and resetting the counter.

2. The method of claim 1, wherein, The method further comprises: if, within the timer, a physical PHY layer of the terminal device monitors that the event does not occur once, sending first information to a medium access control MAC layer of the terminal device, the first information indicating that the event does not occur; the MAC layer adding a first value to the count value of the counter.

3. The method of claim 1, wherein, The method further comprises: if the counter is equal to the initial value, restarting the timer and resetting the counter.

4. A method of monitoring an event, characterized by, The method applied to a terminal device comprises: starting a timer, and monitoring whether an event occurs within the timer; if it is monitored that the event does not occur, restarting the timer; or if it is monitored that the event occurs and the timer expires, reporting information of one or more beams.

5. The method of claim 4, wherein, If it is monitored that the event does not occur, restarting the timer, comprising: if, within the timer, a physical PHY layer of the terminal device monitors that the event does not occur once, sending first information to a medium access control MAC layer of the terminal device, the first information indicating that the event does not occur; the MAC layer restarting the timer.

6. The method of claim 4, wherein, The method further comprises: if, within the timer, the PHY layer of the terminal device monitors that the event occurs once, sending second information to the MAC layer of the terminal device, and the MAC layer of the terminal device continuing to count the timer, wherein the second information indicates that the event occurs; or within the timer, the PHY layer of the terminal device monitors that the event occurs once, and the MAC layer of the terminal device does not receive information from the PHY layer, the MAC layer continuing to count the timer.

7. The method according to any one of claims 4-6, characterized in that, The method further comprises: if it is monitored that the event occurs and the timer expires, restarting the timer.

8. A method of monitoring an event, characterized by, The method applied to a terminal device comprises: starting a timer, and monitoring whether an event occurs within the timer; if it is monitored that the event does not occur, resetting a counter; or if it is monitored that the event occurs and a count value of the counter reaches a first number of times, reporting information of one or more beams.

9. The method of claim 8, wherein, If it is monitored that the event does not occur, resetting the counter, comprising: if, within the timer, a physical PHY layer of the terminal device monitors that the event does not occur once, sending first information to a medium access control MAC layer of the terminal device, the first information indicating that the event does not occur; the MAC layer resetting the counter.

10. The method of claim 8, wherein, The method further comprises: In the timer, the PHY layer of the terminal device monitors occurrence of the event once, and sends second information to the MAC layer of the terminal device, wherein the second information indicates occurrence of the event. The MAC layer adds a first value to the count value of the counter.

11. The method according to any one of claims 8-10, characterized in that, The method further comprises: If occurrence of the event is monitored and the count value of the counter reaches the first value, the timer is restarted and the counter is reset.

12. The method according to any one of claims 1 to 11, characterized in that, The event is used to monitor quality of the one or more beams.

13. The method according to any one of claims 1 to 12, characterized in that, The event comprises: Quality of a serving beam of the terminal device is less than a threshold value, the serving beam belonging to the one or more beams; Quality of an alternative beam of the terminal device is higher than quality of the serving beam of the terminal device by a threshold value, the serving beam and the alternative beam belonging to the one or more beams; or, An absolute value of a difference between quality of a serving beam of the terminal device and quality of an alternative beam of the terminal device is less than a threshold value, the serving beam and the alternative beam belonging to the one or more beams.

14. A communications device, characterized by The communication device comprises one or more processors configured to execute computer programs or instructions in a memory, so that the communication device implements the method of any one of claims 1-3 and 12-13, or implements the method of any one of claims 4-7 and 12-13, or implements the method of any one of claims 8-11 and 12-13.

15. A computer program product, characterised in that, The computer program product, when executed, causes the processor to implement the method of any one of claims 1-3 and 12-13, or implements the method of any one of claims 4-7 and 12-13, or implements the method of any one of claims 8-11 and 12-13.

16. A computer readable storage medium characterized by: The storage medium stores computer programs or instructions, which, when executed by the communication device, implement the method of any one of claims 1-3 and 12-13, or implement the method of any one of claims 4-7 and 12-13, or implement the method of any one of claims 8-11 and 12-13.

Images