Resource request sending method, communication node, and storage medium

Abstract

A resource request sending method, comprising: in response to obtaining beam event instances, starting a monitoring timer for a beam corresponding to beam information in the beam event instances; and before a monitoring timer for a first beam corresponding to beam information in first beam event instances times out, in response to the quantity of acquired first beam event instances reaching a first sample quantity threshold, sending a resource request to a second communication node, wherein the first beam event instances are beam event instances, among all the acquired beam event instances, of which quantity reaches a sample quantity threshold corresponding to the beam before the monitoring timer for the beam corresponding to the beam information times out.

Description

Resource request sending method, communication node and storage medium TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, for example to a resource request sending method, a communication node and a storage medium. BACKGROUND

[0002] In a mobile communication network, whether a terminal device performs handover is determined by a base station according to a measurement report of the terminal device. The terminal device has multiple measurement items and multiple methods (for example, periodic or event triggered) to measure the signal quality of a serving cell and a neighboring cell. The measurement items here can include Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ) or Signal to Interference plus Noise Ratio (SINR). Ideally, the base station allows the terminal device to report the signal quality of the serving cell and the neighboring cell, and triggers handover through a single measurement. However, in reality, frequent ping-pong handover can cause the base station to be overloaded. In order to avoid this situation, the 3rd Generation Partnership Project (3GPP) specification proposes a set of measurement and reporting mechanisms. These measurement and reporting types are called "events". The "events" that the terminal device must report are notified to the terminal device by the base station through Radio Resource Control (RRC) signaling messages.

[0003] In order to reduce the switching interruption delay and reduce the switching signaling overhead, the 5th-generation (5G) introduces L1 / L2 triggered mobility (LTM). In LTM, the base station sends a cell switching command based on a MAC control element (CE) to the terminal device to trigger the process of cell switching. The terminal device switches to the target cell in the LTM candidate cell configuration according to the cell switching command. The base station implements the pre-configuration of the LTM candidate cell configuration by sending RRC signaling to the terminal device. The overall process of LTM includes four parts: LTM preparation, early synchronization, LTM cell switching execution and LTM cell switching completion. Continuous LTM can reuse the pre-configured LTM candidate cell configuration, complete cell switching by repeatedly performing early synchronization, LTM cell switching execution and LTM cell switching completion, and does not need to release other LTM candidate cell configurations after each LTM cell switching completion.

[0004] In the discussion of 3GPP Release 19 (R19) Multiple Input Multiple Output (MIMO) issues, in order to reduce the delay and reduce the signaling overhead, the terminal device triggered L1 measurement event reporting is also proposed. In such a mechanism, the base station can configure the relevant event parameters, and when the terminal device meets the conditions, it will trigger the corresponding reporting. For example, the base station configures one or more event lists, which can be used for beam management or mobility management.

[0005] In the scenario of beam management, the terminal device will trigger a resource request when the beam meets certain events. However, the existing resource request management method is not applicable to this scenario, and the resource request process in this scenario needs to be redesigned. SUMMARY

[0006] The embodiment of the present application provides a resource request sending method, which is applied to a first communication node, and the method comprises the following steps:

[0007] In response to obtaining a beam event sample, a monitoring timer corresponding to the beam information in the beam event sample is started;

[0008] Before a monitoring timer of a first beam corresponding to the beam information of the first beam event instance expires, in response to the quantity of the obtained first beam event instances reaching a first instance quantity threshold, a resource request is sent to a second communication node, wherein the first beam event instance is a beam event instance in all obtained beam event instances, before a monitoring timer of a beam corresponding to the beam information expires, the quantity of which reaches a quantity threshold of instances corresponding to the beam.

[0009] Embodiments of the present application provide a communication node, comprising: a processor; the processor is configured to implement the resource request sending method of any of the above embodiments when executing a computer program.

[0010] Embodiments of the present application also provide a computer readable storage medium, which stores a computer program, and the computer program is configured to implement the method of any of the above embodiments when executed by a processor. BRIEF DESCRIPTION OF DRAWINGS

[0011] FIG. 1 is a networking schematic diagram of a wireless communication system according to an embodiment of the present application;

[0012] FIG. 2 is a flow diagram of a resource request sending method according to an embodiment of the present application;

[0013] FIG. 3 is a flow diagram of another resource request sending method according to an embodiment of the present application;

[0014] FIG. 4 is an interaction diagram of yet another resource request sending method according to an embodiment of the present application;

[0015] FIG. 5 is an interaction diagram of still another resource request sending method according to an embodiment of the present application;

[0016] FIG. 6 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0017] FIG. 7 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0018] FIG. 8 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0019] FIG. 9 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0020] FIG. 10 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0021] FIG. 11 is an interaction diagram of another resource request sending method according to an embodiment of the present application;

[0022] FIG. 12 is a flow diagram of another method for sending a resource request according to an embodiment of the present application;

[0023] FIG. 13 is a diagram of resource request configuration information according to an embodiment of the present application;

[0024] FIG. 14 is a diagram of another resource request configuration information according to an embodiment of the present application;

[0025] FIG. 15 is a diagram of event configuration information according to an embodiment of the present application;

[0026] FIG. 16 is a diagram of another event configuration information according to an embodiment of the present application;

[0027] FIG. 17 is a diagram of yet another event configuration information according to an embodiment of the present application;

[0028] FIG. 18 is a diagram of still another event configuration information according to an embodiment of the present application;

[0029] FIG. 19 is a diagram of a MAC CE indicating only a PL offset corresponding to a currently used TCI state according to an embodiment of the present application;

[0030] FIG. 20 is a diagram of a MAC CE indicating a PL offset corresponding to a currently activated TCI state according to an embodiment of the present application;

[0031] FIG. 21 is a diagram of a MAC CE indicating a PL offset corresponding to a currently activated TCI state according to another embodiment of the present application;

[0032] FIG. 22 is a diagram of a MAC CE indicating a PL offset corresponding to a currently activated TCI state according to yet another embodiment of the present application;

[0033] FIG. 23 is a diagram of a MAC CE indicating a PL offset corresponding to a currently activated TCI state according to yet another embodiment of the present application;

[0034] FIG. 24 is a diagram of a structure of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0035] It should be understood that the specific embodiments described herein are merely exemplary and do not limit the application. The embodiments of the present application will be described in detail hereinafter with reference to the attached drawings.

[0036] In the measurement and reporting of conventional wireless resource management, the following events are defined to realize handover of a terminal device in a cell.

[0037] A1 event: The serving cell is above a threshold. It is typically used to cancel an ongoing handover procedure. It can be triggered when a terminal device moves to the cell edge and starts a mobility procedure, but then moves back to a well-covered area before the mobility procedure is completed.

[0038] A2 event: The serving cell is below a threshold. It is typically used to trigger a terminal device to move to the cell edge. Event A2 does not involve any measurements of neighboring cells, it can be used to trigger any mobility procedure or to trigger measurements of neighboring cells; it can be used in a measurement-based mobility procedure. The base station can configure measurement gaps for inter-frequency or inter-system measurements after event A2 is triggered. This means that inter-frequency / inter-system measurements need to be completed in the case where the coverage conditions are relatively poor and there is a high probability that a handover is required.

[0039] A3 event: A neighbor cell is above a hysteresis offset from the primary serving cell. It is typically used for intra- or inter- frequency handover procedures. When event A2 is triggered, measurement gaps, measurement inter- frequency objects, and event A3 for inter- frequency handover can be configured. Event A3 provides a handover trigger mechanism based on relevant measurement results, for example, it can be configured to trigger when a neighbor cell RSRP is stronger than a particular cell (i.e., the primary serving cell) RSRP.

[0040] A4 event: A neighbor cell is above a threshold. Event A4 can be used for handover procedures that are not dependent on the coverage of the serving cell. For example, in a load balancing function, a terminal device is decided to be handed over from a serving cell based on load conditions rather than radio conditions. In this case, the terminal device only needs to detect that the signal level of the target cell is above a certain signal level and that it provides sufficient coverage.

[0041] A5 event: The serving cell is below a threshold 1 and a neighbor cell is above a threshold 2. Event A5 is typically used for intra- or inter- frequency handover procedures. After event A2 is triggered, a terminal device that is configured for inter- frequency handover can be configured with measurement gaps and event A5. Event A5 provides a handover trigger mechanism based on absolute measurement results. It can be used to trigger a critical handover event: the current serving cell becomes poor and a handover to another cell is required; it does not meet the A3 event handover criteria.

[0042] A6 event: A neighbor cell exceeds a hysteresis offset from the serving cell. This measurement reporting event is applicable for carrier aggregation, i.e., there is a connection to a secondary neighbor cell in addition to the primary serving cell.

[0043] B1 event: An inter-system neighbor cell is above a threshold of the serving cell.

[0044] B2 event: The serving cell is below a threshold 1 and an inter-system neighbor cell is above a threshold 2.

[0045] In the discussion of 3GPP R19 MIMO issues, the base station can configure the reference signal type corresponding to each event, the measurement quantity (also referred to as the measurement item) of the reference signal, the sample quantity threshold corresponding to each event, the related configuration of the event trigger, and the event reporting interval, etc. Among them, the reference signal type can include at least one of the following: Channel State Information Reference Signal (CSI-RS) and Synchronization Signal / PBCH Block (SSB), etc. The measurement quantity of the reference signal can include at least one of the following: RSRP, RSRQ, and SINR. The following takes the event configured by the base station for beam management as an example to introduce the configuration information of several possible beam events.

[0046] Beam event BM1: the channel quality of the current beam is lower than a threshold. Beam event BM2: the channel quality of a new beam is better than the channel quality of the current beam, and the difference between the two channel qualities is greater than a threshold. Beam event BM3: the channel quality of a new beam is better than the channel quality of the worst / best M-th beam corresponding to the reference signal of the activated Transmission Configuration Indication (TCI) state, and the difference between the two channel qualities is greater than a threshold. The base station can configure the configuration information of each event through RRC signaling.

[0047] Optionally, the configuration information of the beam event BM1 configured by the base station can include the following contents. RS type: that is, the reference signal type, which can be SSB or CSI-RS, etc. ReportThreshold A: that is, the threshold of the beam event BM1. Window length: that is, the monitoring duration, with the window length as the duration, within the time window corresponding to the window length, the samples of the beam event BM1 are counted. InstanceMaxCount: that is, the maximum sample value, when the samples of the beam event BM1 within the window as above reach the maximum sample value, the terminal device can perform corresponding beam event reporting. reportInterval: that is, the frequency or period of beam event reporting, which can be one or more periods of the corresponding reference signal. reportAmount: that is, the total number of consecutive beam event reports, when the number of consecutive beam event reports reaches the value, stop reporting, which is cleared after beam switching. ReportOnleave: that is, indicating the base station when the terminal device measures the beam channel quality no longer meets the condition. Ttransmission Mode: that is, the transmission mode.

[0048] Optionally, the configuration information of the beam event BM2 configured by the base station can include the following. NewBeamRsConfig: the configuration of the reference signal corresponding to the new beam, including the reference signal type, which can be SSB or CSI-RS, etc., and also including the configuration corresponding to the reference signal type, etc. ReportThreshold B: the threshold of the beam event BM2. Window length: the monitoring duration, which is the window duration, and within the time window corresponding to the window duration, the samples of the beam event BM2 are counted. InstanceMaxCount: the maximum value of the samples, when the samples of the beam event BM2 within the window as above reach the maximum value of the samples, the terminal device can perform the corresponding beam event reporting. reportInterval: the frequency or period of the beam event reporting, which can be one or more periods of the corresponding reference signal. reportAmount: the total number of consecutive beam event reporting, when the number of consecutive beam event reporting reaches the value, the reporting is stopped, and the value is cleared after the beam switching. ReportOnleave: indicating the base station when the beam channel quality measured by the terminal device no longer meets the condition. ReportBeamNumber: indicating the number of report beams. IncludeCurrentBeam: whether the current beam number is included in the reporting. Ttransmission Mode: transmission mode.

[0049] Optionally, the configuration information of the beam event BM3 configured by the base station can include the following. NewBeamRsConfig: the configuration of the reference signal corresponding to the new beam includes the reference signal type, which can be SSB or CSI-RS, etc., and also includes the configuration corresponding to the reference signal type, etc. ReportThreshold C: the threshold of the beam event BM3. Window length: the monitoring duration, and the number of beam event BM3 samples is counted within the time window corresponding to the window length. InstanceMaxCount: the maximum value of the sample, and when the number of beam event BM3 samples counted within the window reaches the maximum value of the sample, the terminal device can perform corresponding beam event reporting. reportInterval: the frequency or period of beam event reporting, which can be one or more periods of the corresponding reference signal. reportAmount: the total number of consecutive beam event reports, and when the number of consecutive beam event reports reaches the value, the reporting is stopped. The value is cleared to 0 after beam switching. ReportOnleave: indicates the base station when the terminal device measures the beam quality that no longer meets the condition. ReportBeamNumber: indicates the number of report beams. IncludeCurrent Beam: whether the current beam number is included in the report. Ttransmission Mode: transmission mode.

[0050] Optionally, the transmission mode in the configuration information above can include the following two transmission modes. Transmission mode A: Transmission mode A includes three operations, i.e., the terminal device sends a resource scheduling request to the base station, the base station allocates scheduling resources, and the terminal device sends a beam event report on the resources allocated by the base station. Transmission mode B: Based on the preconfigured resource, the terminal device sends a beam event report on the preconfigured resource, which includes two operations. Step 1: The terminal device indicates to the base station that it will send a beam event report on the preconfigured resource. Step 2: The terminal device sends a beam event report to the base station on the preconfigured resource.

[0051] In the configuration information as above, it can be seen that the terminal device side needs to count the number of instances within a time window. Taking the beam event BM2 as an example, the number of instances is counted within the Window Length, and if the InstanceMaxCount value configured by the network is reached, it is considered that the corresponding beam event can be triggered. Once the beam event is triggered, in the scenario where the transmission mode is transmission mode A, the terminal device needs to send a corresponding resource request indication to the base station, so as to let the base station allocate corresponding resources, and then the terminal device sends a beam event report on the allocated resources. In the scenario where the transmission mode is transmission mode B, the terminal device indicates to the base station that it will send a beam event report on the preconfigured resources, and then sends a beam event report to the base station on the preconfigured resources.

[0052] The resource request management method in the related art is not applicable to resource request in the beam management scenario. The resource request sending method provided in the embodiment is used to solve how the first communication node sends a resource request to the second communication node when the number of instance samples of a certain beam event reaches the corresponding sample quantity threshold in the beam management scenario, that is, before sending a beam event report.

[0053] The resource request sending method provided in the present application can be applied to various wireless communication systems, such as a long term evolution (LTE) system, a 4th-generation (4G) system, a 5G system, a mixed architecture system of LTE and 5G, a 5G new radio (NR) system, and a new communication system to be appeared in future communication development, such as a 6th-generation (6G) system. FIG. 1 is a networking schematic diagram of a wireless communication system according to an embodiment of the present application. As shown in FIG. 1, the wireless communication system includes a terminal device 110, an access network device 120, and a core network device 130.

[0054] The terminal device 110 can be a device with wireless transceiving function, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted, etc.), on water (such as ships, etc.), or in the air (such as airplanes, balloons and satellites, etc.). Some examples of the terminal device 110 include passive terminals, user equipment (UE), mobile phones, mobile stations, tablet computers, notebook computers, ultra-mobile personal computers (UMPC), handheld computers, netbooks, personal digital assistants (PDA) and other network-enabled user equipment, or virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, Internet of Things nodes in Internet of Things, vehicle communication devices in Internet of Vehicles, entertainment, game devices or systems, global positioning system devices, etc. Embodiments of the present application do not limit the specific technology and specific device form of the terminal device, and in addition, the terminal device can be referred to simply as a terminal.

[0055] The access network device 120 is an access device through which the terminal device 110 accesses the wireless communication system in a wireless manner, and can be a reader / writer, a base station, an evolved NodeB (eNB or eNodeB) in Long Term Evolution advanced (LTEA), a transmission reception point (TRP), a base station or next generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, an access node in a Wireless Fidelity (WiFi) system, or the like. The base station can include various macro base stations, micro base stations, home base stations, wireless remote units, routers, WIFI devices, various network side devices such as primary cells and secondary cells, and a location management function (LMF) device. The access network device 120 can also be a module or unit that completes part of the functions of the base station, for example, can be a central unit (CU) or a distributed unit (DU). Embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device. In addition, the access network device can be referred to simply as a base station.

[0056] The core network device 130 can include an access and mobility management network element and a session management network element. Optionally, the terminal device 110 can access the core network through the access network device 120, thereby realizing data transmission.

[0057] In the embodiments of the present application, a resource request sending method, a communication node and a storage medium that can run in the above wireless communication system are provided to solve the problem of how the first communication node sends a resource request to the second communication node when the number of beam event samples reaches the corresponding sample number threshold in a beam management scenario, i.e., before sending a beam event report. Moreover, the resource request sending method can realize counting the number of beam event samples based on the monitoring timer of the beam corresponding to the beam information in the beam event sample, i.e., counting the number of beam event samples based on the beam granularity, which realizes a fine-grained beam event sample number counting, avoids the situation of false resource request or missed resource request due to counting error when counting the number of beam event samples, and thus improves the reliability in the resource request sending process.

[0058] Next, the resource request sending method, the communication node and the technical effects thereof are described.

[0059] FIG. 2 is a flow diagram of a resource request sending method according to an embodiment of the present application. The resource request sending method according to the embodiment can be applied to a first communication node. The first communication node in the embodiment can be the terminal device in FIG. 1. As shown in FIG. 2, the resource request sending method according to the embodiment includes the following operations.

[0060] 201: In response to obtaining a beam event instance, starting a monitoring timer of a beam corresponding to beam information in the beam event instance.

[0061] In beam management, the first communication node can perform beam measurement. When a certain beam measurement process meets the configuration information of a certain beam event, the relevant information in the beam measurement process is referred to as a beam event instance of the beam event. The beam event in the embodiment includes the beam event BM1, the beam event BM2, or the beam event BM3 as described above. For example, it is assumed that in a certain beam measurement, the channel quality of a current beam is lower than the configured threshold, and the relevant information in the beam measurement process is a beam event instance of the beam event BM1.

[0062] In the embodiment, in response to obtaining a beam event instance, a monitoring timer of a beam corresponding to beam information in the beam event instance is started. In the embodiment, in order to achieve fine-grained beam event instance quantity statistics, each beam corresponds to a monitoring timer, that is, the management of the monitoring timer is based on each beam. The beam event instance in the embodiment includes beam information. For example, the beam information can be a beam identity (ID).

[0063] Optionally, the beam event instance in the embodiment further includes a beam event identity to indicate a beam event type.

[0064] A possible implementation process of 201 is as follows: after obtaining a beam event instance, beam information in the beam event instance is determined; in response to determining that a monitoring timer of a beam corresponding to the beam information is not started, the monitoring timer of the beam corresponding to the beam information in the beam event instance is started, and the quantity of the beam event instance is counted; when it is determined that the monitoring timer of the beam corresponding to the beam information is started, the monitoring timer does not need to be started, and the quantity of the beam event instance is directly counted.

[0065] Optionally, the number of the beam event instance can be counted by a monitoring counter of the beam corresponding to the beam information in the beam event instance. When it is determined that the monitoring counter of the beam corresponding to the beam information is not started, the monitoring counter of the beam corresponding to the beam information in the beam event instance is started; when it is determined that the monitoring counter of the beam corresponding to the beam information is started, the number of the beam event instance is counted directly based on the monitoring counter of the beam corresponding to the beam information in the beam event instance.

[0066] The number of the beam event instance in the embodiment is at least one. When the number of the beam event instance is multiple, the number of the beam event instance is counted in the embodiment in the granularity of the included beam, that is, the number of the beam event instance is counted in the granularity of the included beam. For example, it is assumed that 4 beam event instances 1 including beam information 1 are acquired, and 5 beam event instances 2 including beam information 2 are acquired, and then the number of the beam event instances 1 and the number of the beam event instances 2 are counted respectively in the embodiment.

[0067] 202: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, in response to the number of the acquired first beam event instances reaching a first instance number threshold, a resource request is sent to a second communication node.

[0068] If the number of the acquired first beam event instances reaches the first instance number threshold before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, it indicates that the first beam triggers a beam event report. In order to send the beam event report to the second communication node, the resource request is sent to the second communication node in 202. The second communication node in the embodiment can be the access network device in FIG. 1.

[0069] The first beam event instance in the embodiment refers to any beam event instance that reaches the corresponding instance number threshold before the corresponding monitoring timer expires among all the beam event instances acquired in 201.

[0070] The first instance number threshold, the monitoring duration of the monitoring timer and the transmission mode in the embodiment can be information pre-configured by the second communication node for the first communication node. The second communication node can pre-send event configuration information and resource request configuration information to the first communication node. The event configuration information can include the instance number threshold, the monitoring duration and the transmission mode corresponding to each event. The configuration process will be described in detail in subsequent embodiments.

[0071] In an implementation, the resource request in the embodiment includes a scheduling request (SR). In another implementation, the resource request in the embodiment includes new uplink control information (UCI).

[0072] Optionally, after the resource request is sent to the second communication node, the method can further include the following operation: before the monitoring timer of the first beam expires, the number of the first beam event instances is continuously accumulated when the first beam event instances are continuously received.

[0073] Optionally, based on the transmission mode A, after the resource request is sent to the second communication node, the method can further include the following operation: receiving resource configuration information sent by the second communication node; and sending a beam event report on the resource corresponding to the resource configuration information. It can be understood that the beam event report is the beam event report triggered by the first beam.

[0074] Optionally, based on the transmission mode B, the resource request is used to indicate resource information of the beam event report. After the resource request is sent to the second communication node, the method can further include the following operation: sending a beam event report on the resource corresponding to the resource information indicated by the resource request.

[0075] Optionally, the resource request in the embodiment can be used in a dual connection architecture, carrier aggregation (CA), or a single carrier architecture.

[0076] The resource request sending method provided in the embodiment sends a resource request to a second communication node when the number of first beam event instances reaches a corresponding first instance threshold, i.e., before a beam event report is sent, thereby implementing a resource request in a beam management scenario. Moreover, the resource request sending method can count the number of beam event instances based on a monitoring timer of a beam corresponding to beam information in the beam event instance, i.e., count the number of beam event instances based on a beam granularity, thereby implementing a fine-grained counting of the number of beam event instances, avoiding the situation of false sending or missing sending of a resource request due to counting errors when counting the number of beam event instances, and thereby improving the reliability in the resource request sending process.

[0077] FIG. 3 is a flow diagram of another resource request sending method provided in an embodiment of the application. The embodiment makes a detailed description of the operation after a resource request is sent to a second communication node based on the embodiment shown in FIG. 2 and various optional implementations. As shown in FIG. 3, the resource request sending method provided in the embodiment includes the following operations.

[0078] 301: In response to obtaining the beam event sample, start a monitoring timer of a beam corresponding to the beam information in the beam event sample.

[0079] 302: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event sample expires, in response to the number of obtained first beam event samples reaching the first sample number threshold, send a resource request to the second communication node.

[0080] The implementation process and technical principles of 301 and 201, and 302 and 202 are similar, and will not be repeated here.

[0081] 303: Start a prohibit timer corresponding to the resource request, and prohibit sending the resource request again before the prohibit timer corresponding to the resource request expires.

[0082] Optionally, the prohibit duration of the prohibit timer corresponding to the resource request can be included in the resource request configuration information configured by the second communication node for the first communication node. The prohibit timer is configured based on each resource request.

[0083] Optionally, after the prohibit timer corresponding to the resource request expires, if no feedback is received from the second communication node, the resource request can be sent again.

[0084] 303 can avoid signaling storm caused by frequent sending of resource requests to the second communication node.

[0085] 304: Start counting the number of times of sending the resource request.

[0086] Optionally, the resource request configuration information can further include a resource request number threshold. In operation 304, in order to avoid the number of times of sending the resource request exceeding the resource request number threshold corresponding thereto, the number of times of sending the resource request needs to be counted.

[0087] The resource request number threshold in the embodiment can be included in the resource request configuration information pre-configured by the second communication node for the first communication node. The configuration process will be described in detail in subsequent embodiments.

[0088] 305: Suspend the resource request.

[0089] The pending resource request in the embodiment refers to waiting for the response of the resource request from the second communication node. During the pending resource request, the first communication node will not repeatedly send the resource request to the second communication node, so as to quickly respond to the resource request sent by the first communication node.

[0090] It should be noted that in the resource request sending method provided in the embodiment, at least one operation in 303 to 305 can be performed.

[0091] The resource request sending method provided by the embodiment can start a prohibit timer corresponding to the resource request, and prohibit the sending of the resource request again before the prohibit timer corresponding to the resource request expires, thereby avoiding a signaling storm. The resource request sending method can also count the number of times of sending the resource request, so as to avoid the number of times of sending the resource request exceeding a resource request quantity threshold corresponding to the resource request. The resource request sending method can also suspend the resource request, so that the second communication node can quickly respond to the sent resource request.

[0092] FIG. 4 is an interaction diagram of another resource request sending method provided by an embodiment of the application. The embodiment is based on the embodiment shown in FIG. 2, the embodiment shown in FIG. 3, and various optional implementation manners, and describes in detail the interaction process between different layers of the first communication node and the interaction process between the first communication node and the second communication node in the resource request sending process. As shown in FIG. 4, the resource request sending method provided by the embodiment includes the following operations.

[0093] 401: The resource request sending layer of the first communication node sends a beam event sample to the resource request triggering layer of the first communication node.

[0094] Optionally, the resource request sending layer of the first communication node in the embodiment can be a physical layer. The resource request triggering layer of the first communication node can be a physical layer or a MAC layer. The resource request sending layer of the first communication node and the resource request triggering layer of the first communication node can be the same or different. The embodiment is not limited in this way.

[0095] For example, the resource request sending layer of the first communication node in the embodiment can be a physical layer, and the resource request triggering layer of the first communication node can be a MAC layer.

[0096] Optionally, the beam event sample in the embodiment can include an event ID and a beam ID.

[0097] In 401, after the resource request sending layer completes beam measurement and the measurement value meets the triggering condition of the beam event sample, the resource request sending layer can send the beam event sample to the resource request triggering layer.

[0098] 402: In response to receiving the beam event sample, the resource request triggering layer starts a monitoring timer of a beam corresponding to the beam information in each beam event sample.

[0099] Each beam corresponds to one monitoring timer.

[0100] The implementation process of 402 is similar to that of 201, which will not be described here.

[0101] The resource request sending layer can continue to send the first beam event instance to the resource request triggering layer until the Nth first beam event instance is sent.

[0102] 403: In response to the number of acquired first beam event instances reaching the first instance quantity threshold before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0103] Optionally, the resource request triggering information in the embodiment includes at least one of the following: event information and related beam information of the beam event instance, wherein the event information can be an event ID, and the related beam information can be a beam ID.

[0104] Exemplarily, the resource request triggering information has the following three implementation schemes.

[0105] Scheme 1: The resource request triggering information includes event information. In this scheme, the resource request triggering information does not include related beam information of the first beam event instance.

[0106] Scheme 2: The resource request triggering information includes event information and related beam information of the first beam event instance or other beam event instance information. For example, when the number of second beam event instances reaches a second instance quantity threshold, the related beam information of the second beam event instance can also be included. Here, the second instance quantity threshold can be the same as or different from the first instance quantity threshold.

[0107] Scheme 3: The resource request triggering information includes event information, and when the beam information corresponding to the previous resource request triggering information is different from the beam information corresponding to the resource request triggering information, the resource request triggering information further includes related beam information of the first beam event instance. For example, the first resource request triggering information is triggered by (event 2 + first beam), and the second resource request triggering information is also triggered by (event 2 + first beam), then the second resource request triggering information only includes event information and does not include related beam information. If the second resource request triggering information is triggered by other events or other beams, the related beam information is also indicated in the resource request triggering information.

[0108] It should be noted that the related beam information of the first beam event instance in the embodiment includes the beam information corresponding to the first beam. In addition to this, the related beam information of the first beam event instance can also include other beam information related to the first beam event instance.

[0109] 404: After receiving the resource request triggering information, the resource request sending layer sends a resource request to the second communication node.

[0110] Optionally, the resource request sending method further includes the following operation.

[0111] 405: The resource request triggering layer starts a prohibit timer corresponding to the resource request.

[0112] Optionally, after sending the resource request triggering information to the resource request sending layer, the resource request triggering layer starts a prohibit timer corresponding to the resource request. Within the prohibit time length of the prohibit timer, the resource request of this type is prohibited from being triggered again.

[0113] 406: The resource request triggering layer starts counting the number of sending times of the resource request.

[0114] Optionally, after sending the resource request triggering information to the resource request sending layer, the resource request triggering layer starts counting the number of sending times of the resource request.

[0115] 407: The resource request triggering layer suspends the resource request.

[0116] Optionally, after sending the resource request triggering information to the resource request sending layer, the resource request triggering layer suspends the resource request.

[0117] Optionally, the resource request sending method further includes the following operation.

[0118] 408: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0119] Optionally, the first end indication is an indication sent by the resource request sending layer at any one of the following time points: a time point after sending the resource request, a time point after receiving the resource configuration information sent by the second communication node, and a time point after sending the beam event report to the second communication node.

[0120] Optionally, the first end indication includes: a resource request sending indication, or beam information related to the beam event. The beam information related to the beam event includes at least one of the following: beam information corresponding to the first beam, beam information corresponding to a beam satisfying the triggering condition of the beam event report, and all beam information included in the beam event report.

[0121] 409: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0122] Optionally, the ending operation comprises at least one of the following: stopping the monitoring timer of the first beam; stopping the monitoring timer of the beam corresponding to the beam information related to the beam event; stopping the monitoring timer of all beams; clearing the monitoring counter of the first beam, i.e., clearing the statistical number of beam event instances; clearing the monitoring counter of the beam corresponding to the beam information related to the beam event; clearing the monitoring counter of all beams; stopping the prohibit timer corresponding to the resource request; clearing the number of times of sending the resource request; deleting the pending resource request.

[0123] Optionally, in the scenario of the transmission mode A, the resource request sending method further comprises the following operation.

[0124] 410a: The second communication node sends resource configuration information to the first communication node.

[0125] 410b: The resource request sending layer sends the beam event report on the resource corresponding to the resource configuration information.

[0126] Optionally, the resource request sending method further comprises the following operation.

[0127] 411a: The second communication node sends a second ending indication to the first communication node.

[0128] 411b: In response to receiving the second ending indication sent by the second communication node, the resource request triggering layer performs an ending operation.

[0129] It should be noted that, based on different implementation manners of the second ending indication, the physical layer, the MAC layer or the high layer above the MAC layer of the first communication node can receive the second ending indication.

[0130] Optionally, the second ending indication comprises at least one of the following: an indication of changing the current beam of the first communication node; an updated new beam list indication; an activated TCI state (TCI sate) update information indication; network reconfiguration information.

[0131] Optionally, the ending operation in 410b can comprise at least one of the following: stopping the monitoring timer of the first beam; stopping the monitoring timer of the beam corresponding to the beam information related to the beam event; stopping the monitoring timer of all beams; clearing the monitoring counter of the first beam; clearing the monitoring counter of the beam corresponding to the beam information related to the beam event; clearing the monitoring counter of all beams; stopping the prohibit timer corresponding to the resource request; clearing the number of times of sending the resource request; deleting the pending resource request; stopping or clearing the monitoring timer of the beam corresponding to the beam information indicated in the second ending indication.

[0132] Optionally, the resource request sending method provided by the embodiment further includes the following operations: after the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer stops the monitoring timer of the first beam; in response to receiving the first end indication, the resource request triggering layer stops the monitoring timer of the first beam; and the monitoring timer of the first beam times out. In other words, the three implementation manners above provide the end monitoring timer.

[0133] In the scenario where the resource request sending layer of the first communication node is a physical layer and the resource request triggering layer of the first communication node is a MAC layer, the resource request sending method provided by the embodiment can implement beam management reporting based on the physical layer.

[0134] In the existing resource request method, the SR indication is triggered by a MAC protocol data unit (PDU) or a MAC CE, that is, the trigger source and the resource request are generated at the same layer. In the existing resource request configuration, a cell group can be configured with multiple scheduling requests. Each scheduling request includes: a scheduling request identifier, a scheduling request prohibition duration, and a maximum number of scheduling request transmissions. For a logical channel (LCH), only one uplink control channel resource for SR can be configured on each bandwidth part (BWP), and the configuration of each SR can be given to one or more logical channels, that is, one or more logical channels can share one SR configuration, and of course some logical channels can not have a corresponding SR. It can be seen that the traditional SR is triggered by a MAC PDU / MAC CE, and in the scenario where the resource request sending layer of the first communication node is a physical layer and the resource request triggering layer of the first communication node is a MAC layer, the beam management reporting based on the physical layer can be implemented.

[0135] The resource request sending method provided in the embodiment, on the one hand, the resource request sending layer of the first communication node sends a beam event example to the resource request triggering layer of the first communication node, when the resource request triggering layer receives the beam event example, starts a monitoring timer of a beam corresponding to the beam information in the beam event example, wherein each beam corresponds to a monitoring timer, the resource request triggering layer sends resource request triggering information to the resource request sending layer, and after receiving the resource request triggering information, the resource request sending layer sends a resource request to the second communication node, which realizes the resource request sending based on the resource request sending layer of the first communication node and the resource request triggering layer of the first communication node, and realizes the resource request management at a finer level. On the other hand, the resource request sending layer sends a first end instruction to the resource request triggering layer, when the resource request triggering layer receives the first end instruction, performs an end operation, or when receiving a second end instruction sent by the second communication node, the resource request triggering layer performs an end operation, which realizes the flexible end operation according to the instruction to release the resource and save the processing resource of the first communication node.

[0136] FIG. 5 is an interaction diagram of another resource request sending method provided in an embodiment of the application. The embodiment describes a scenario after sending a resource request on the basis of the embodiments shown in FIGS. 2 to 4 and various optional implementation manners. As shown in FIG. 5, the resource request sending method provided in the embodiment includes the following operations.

[0137] 501: The resource request sending layer of the first communication node sends a first beam event example to the resource request triggering layer of the first communication node.

[0138] In the embodiment, the beam event example sent by the resource request sending layer to the resource request triggering layer is taken as an example to describe the first beam event example.

[0139] Exemplarily, the first beam event example in the embodiment can include an event ID and a beam ID1.

[0140] 502: In response to receiving the first beam event example, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event example.

[0141] 503: The resource request sending layer continues to send the first beam event example to the resource request triggering layer until the Nth first beam event example is sent.

[0142] 504: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event example expires, in response to the quantity of the acquired first beam event examples reaching a first example quantity threshold, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0143] Optionally, the first sample quantity threshold is less than or equal to N, where N is a sample maximum value.

[0144] 505: The resource request sending layer sends a resource request to the second communication node after receiving the resource request triggering information.

[0145] 506: The resource request triggering layer starts a prohibit timer corresponding to the resource request after sending the resource request triggering information to the resource request sending layer.

[0146] 507: The resource request triggering layer starts counting the number of times of sending the resource request after sending the resource request triggering information to the resource request sending layer.

[0147] 508: The resource request triggering layer suspends the resource request after sending the resource request triggering information to the resource request sending layer.

[0148] In this embodiment, in response to monitoring that the second communication node does not send the resource configuration information, the resource request is sent to the second communication node after the prohibit timer corresponding to the resource request expires. The resource request sending method provided in this embodiment can implement the above process through 509a and 509b as follows.

[0149] 509a: In response to monitoring that the second communication node does not send the resource configuration information, the resource request triggering layer sends the resource request triggering information to the resource request sending layer after the prohibit timer corresponding to the resource request expires.

[0150] Optionally, in 509a, in response to monitoring that the second communication node does not send the resource configuration information, the resource request triggering layer sends the resource request triggering information to the resource request sending layer after the prohibit timer corresponding to the resource request expires, and in response to the number of times of sending the resource request not reaching a resource request quantity threshold.

[0151] 509b: The resource request sending layer sends the resource request to the second communication node after receiving the resource request triggering information.

[0152] Optionally, in the scenario of transmission mode A, the resource request sending method further includes the following operation.

[0153] 510a: The second communication node sends the resource configuration information to the first communication node.

[0154] 510b: The resource request sending layer sends the beam event report on the resource corresponding to the resource configuration information.

[0155] Optionally, the resource request sending method further includes the following operation.

[0156] 511: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0157] 512: In response to receiving the first end indication, the resource request sending layer performs an end operation.

[0158] Optionally, the resource request sending method further includes the following operation.

[0159] 513a: The second communication node sends a second end indication to the first communication node.

[0160] 513b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0161] The resource request sending method provided by the embodiment is different from the embodiment shown in FIG. 4 in that, when the sent resource request does not obtain a response from the second communication node, after the prohibition timer corresponding to the resource request expires, the resource request triggering layer sends the resource request to the second communication node again, so as to improve the reliability of the resource request sending.

[0162] FIG. 6 is an interaction schematic diagram of another resource request sending method provided by an embodiment of the present application. The embodiment describes in detail a scenario after sending a resource request on the basis of the embodiments shown in FIGS. 2 to 5 and various optional implementation manners. As shown in FIG. 6, the resource request sending method provided by the embodiment includes the following operations.

[0163] 601: The resource request sending layer of the first communication node sends a first beam event sample to the resource request triggering layer of the first communication node.

[0164] In the embodiment, the beam event sample sent by the resource request sending layer to the resource request triggering layer is taken as an example for description.

[0165] Exemplarily, the first beam event sample in the embodiment can include an event ID and a beam ID1.

[0166] 602: In response to receiving the first beam event sample, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event sample.

[0167] 603: The resource request sending layer continues to send the first beam event sample to the resource request triggering layer until the Nth first beam event sample is sent.

[0168] 604: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event sample expires, in response to the quantity of the acquired first beam event samples reaching a first sample quantity threshold, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0169] Optionally, the first sample quantity threshold is less than or equal to N.

[0170] 605: The resource request sending layer sends the resource request to the second communication node after receiving the resource request triggering information.

[0171] 606: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer starts the prohibition timer corresponding to the resource request.

[0172] 607: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer starts counting the number of times of sending the resource request.

[0173] 608: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer suspends the resource request.

[0174] In this embodiment, in response to monitoring that the second communication node does not send the resource configuration information until the monitoring timer of the first beam expires, the resource request is sent to the second communication node after the prohibition timer corresponding to the resource request expires, and in response to the number of times of sending the resource request not reaching the resource request quantity threshold. The resource request sending method provided in this embodiment can implement the above process through 609a and 609b as follows.

[0175] 609a: In response to monitoring that the second communication node does not send the resource configuration information until the monitoring timer of the first beam expires, the resource request triggering layer sends the resource request triggering information to the resource request sending layer after the prohibition timer corresponding to the resource request expires, and in response to the number of times of sending the resource request not reaching the resource request quantity threshold.

[0176] 609b: The resource request sending layer sends the resource request to the second communication node after receiving the resource request triggering information.

[0177] Optionally, 609a and 609b can be repeatedly executed. In FIG. 6, two repeated executions are taken as an example for illustration.

[0178] Optionally, in the scenario of transmission mode A, the resource request sending method further includes the following operation.

[0179] 610a: The second communication node sends the resource configuration information to the first communication node.

[0180] 610b: The resource request sending layer sends the beam event report on the resource corresponding to the resource configuration information.

[0181] Optionally, the resource request sending method further includes the following operation.

[0182] 611: The resource request sending layer sends the first end indication to the resource request triggering layer.

[0183] 612: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0184] Optionally, the resource request sending method further includes the following operation.

[0185] 613a: The second communication node sends a second end indication to the first communication node.

[0186] 613b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0187] The resource request sending method provided by the embodiment is different from the embodiment shown in FIG. 4 in that, in response to the monitoring timer of the first beam expiring and the second communication node being monitored to not send resource configuration information, the resource request is sent to the second communication node again after the prohibition timer corresponding to the resource request expires and in response to the number of times of sending the resource request not reaching the resource request quantity threshold, so as to improve the reliability of sending the resource request.

[0188] FIG. 7 is an interaction schematic diagram of another resource request sending method provided by an embodiment of the present application. The embodiment is based on the embodiments shown in FIGS. 2 to 6 and various optional implementation manners, and describes in detail a scenario after sending a resource request. As shown in FIG. 7, the resource request sending method provided by the embodiment includes the following operations.

[0189] 701: The resource request sending layer of the first communication node sends a first beam event sample to the resource request triggering layer of the first communication node.

[0190] In the embodiment, the beam event sample sent by the resource request sending layer to the resource request triggering layer is taken as an example to be described.

[0191] Exemplarily, the first beam event sample in the embodiment can include an event ID and a beam ID1.

[0192] 702: In response to receiving the first beam event sample, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event sample.

[0193] 703: The resource request sending layer continues to send the first beam event sample to the resource request triggering layer until the Nth first beam event sample is sent.

[0194] 704: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event sample expires, in response to the number of acquired first beam event samples reaching a first sample quantity threshold, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0195] Optionally, the first example quantity threshold is less than or equal to N.

[0196] 705: The resource request sending layer sends the resource request to the second communication node after receiving the resource request triggering information.

[0197] 706: The resource request triggering layer starts the prohibition timer corresponding to the resource request after sending the resource request triggering information to the resource request sending layer.

[0198] 707: The resource request triggering layer starts counting the number of times of sending the resource request after sending the resource request triggering information to the resource request sending layer.

[0199] 708: The resource request triggering layer suspends the resource request after sending the resource request triggering information to the resource request sending layer.

[0200] In this embodiment, in response to monitoring that the second communication node does not send the resource configuration information until the monitoring timer of the first beam expires, the resource request is sent to the second communication node after the prohibition timer corresponding to the resource request expires, and in response to the number of times of sending the resource request not reaching the resource request quantity threshold. The resource request sending method provided in this embodiment can implement the above process through 709a and 709b as follows.

[0201] 709a: In response to monitoring that the second communication node does not send the resource configuration information until the monitoring timer of the first beam expires, the resource request triggering layer sends the resource request triggering information to the resource request sending layer after the prohibition timer corresponding to the resource request expires, and in response to the number of times of sending the resource request not reaching the resource request quantity threshold.

[0202] 709b: The resource request sending layer sends the resource request to the second communication node after receiving the resource request triggering information.

[0203] In this embodiment, 709a and 709b are repeatedly executed until the number of times of sending the resource request reaches the resource request quantity threshold. The resource request sending method provided in this embodiment further includes 710 as follows.

[0204] 710: In response to the number of times of sending the resource request reaching the resource request quantity threshold, the resource request triggering layer performs an end operation.

[0205] Optionally, after 710, the resource request sending method provided in this embodiment includes the following two implementation manners.

[0206] Implementation 1: performing the random access procedure based on the preconfigured random access resource of the second communication node. This implementation can enable the first communication node to quickly access the network, and avoid affecting the normal data transmission of the first communication node.

[0207] Implementation 2: not triggering the random access procedure. This implementation does not require the second communication node to preconfigure additional random access resources, thereby saving access resources.

[0208] It should be noted that the implementation 1 and 710 can be executed simultaneously or in any order. The implementation 2 and 710 can be executed simultaneously or in any order.

[0209] The ending operation in 710 can include: stopping the monitoring timer of the first beam; stopping the monitoring timer of the beam corresponding to the beam information related to the beam event; stopping the monitoring timer corresponding to all beams; clearing the monitoring counter of the first beam; clearing the monitoring counter of the beam corresponding to the beam information related to the beam event; clearing the monitoring counter corresponding to all beams; stopping the prohibition timer corresponding to the resource request; clearing the number of times of sending the resource request; or deleting the pending resource request.

[0210] Optionally, after 710, 701 can be re-executed.

[0211] Optionally, the resource request sending method can further include 611 and 612 in FIG. 6. Details are not described herein.

[0212] Optionally, the resource request sending method can further include 613a and 613b in FIG. 6. Details are not described herein.

[0213] The resource request sending method provided in this embodiment can enable the resource request triggering layer to perform the ending operation when the number of times of sending the resource request reaches the resource request quantity threshold, so as to release the resources of the first communication node and save the processing resources of the first communication node.

[0214] FIG. 8 is an interaction schematic diagram of another resource request sending method provided by an embodiment of the present application. This embodiment describes the interaction process between different layers of the first communication node and the interaction process between the first communication node and the second communication node in the resource request sending process based on the embodiments and various optional implementations shown in FIGS. 2 to 7. As shown in FIG. 8, the resource request sending method provided by this embodiment includes the following operations.

[0215] 801a: The resource request sending layer of the first communication node sends a first beam event example to the resource request triggering layer of the first communication node.

[0216] Exemplarily, the first beam event example in the embodiment can include: an event ID and a beam ID1.

[0217] 801b: In response to receiving the first beam event example, the resource request triggering layer starts a monitoring timer of the first beam corresponding to the beam information in the first beam event example.

[0218] 802a: The resource request sending layer sends a second beam event example to the resource request triggering layer.

[0219] Exemplarily, the second beam event example in the embodiment can include: an event ID and a beam ID2.

[0220] 802b: In response to receiving the second beam event example, the resource request triggering layer starts a monitoring timer of the second beam corresponding to the beam information in the second beam event example.

[0221] 803a: The resource request sending layer sends a third beam event example to the resource request triggering layer.

[0222] Exemplarily, the third beam event example in the embodiment can include: an event ID and a beam ID3.

[0223] 803b: In response to receiving the third beam event example, the resource request triggering layer starts a monitoring timer of the third beam corresponding to the beam information in the third beam event example.

[0224] Based on 801a to 803b, it can be seen that the management of the monitoring timer in the embodiment is based on each beam, thereby realizing the number statistics of the beam event example with fine granularity.

[0225] 804: The resource request sending layer continues to send the first beam event example to the resource request triggering layer until the Nth first beam event example is sent.

[0226] 805: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event example expires, in response to the number of the acquired first beam event examples reaching a first example number threshold, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0227] Optionally, the first example number threshold is less than or equal to N.

[0228] Exemplarily, the resource request triggering information can include the beam ID1.

[0229] Optionally, in the embodiment, before the monitoring timer of the first beam expires, when the first beam event example continues to be received, the number of the first beam event examples continues to be accumulated.

[0230] 806: The resource request sending layer sends a resource request to the second communication node after receiving the resource request triggering information.

[0231] 807: The resource request triggering layer starts a prohibit timer corresponding to the resource request after sending the resource request triggering information to the resource request sending layer.

[0232] 808: The resource request triggering layer starts counting the number of sending times of the resource request after sending the resource request triggering information to the resource request sending layer.

[0233] 809: The resource request triggering layer suspends the resource request after sending the resource request triggering information to the resource request sending layer.

[0234] Optionally, in the scenario of transmission mode A, the resource request sending method further includes the following operation.

[0235] 810a: The second communication node sends resource configuration information to the first communication node.

[0236] 810b: The resource request sending layer sends a beam event report on the resource corresponding to the resource configuration information.

[0237] Optionally, the resource request sending method further includes the following operation.

[0238] 811: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0239] The implementation manner of the first end indication in the embodiment is the same as that of the first end indication shown in the foregoing embodiments, which will not be described here again.

[0240] 812: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0241] The implementation manner of the end operation in the embodiment 812 is the same as that of the end operation shown in the foregoing embodiments, which will not be described here again.

[0242] Optionally, in the embodiment, if only the monitoring timer of the related beam is stopped or the monitoring counter of the related beam is cleared, other beam event samples can continue to be counted.

[0243] Optionally, in the embodiment, the prohibit timer corresponding to the resource request can also not be stopped, or the number of sending times of the resource request can not be cleared. In the embodiment, the number of sending times of the resource request can be counted by a resource request sending time counter.

[0244] Optionally, in the embodiment, after the prohibition timer corresponding to the resource request is stopped, if the other beam event instance meets the condition, the resource request can continue to be triggered.

[0245] Optionally, the resource request sending method further includes the following operations.

[0246] 813a: The second communication node sends a second end indication to the first communication node.

[0247] 813b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0248] The implementation mode of the second end indication in the embodiment is the same as that shown in the foregoing embodiments, and will not be described here again.

[0249] The implementation mode of the end operation in the embodiment 813b is the same as that shown in the foregoing embodiments, and will not be described here again.

[0250] The resource request sending method provided in the embodiment can realize resource request sending in a scenario where multiple beam event instances are obtained.

[0251] FIG. 9 is an interaction schematic diagram of another resource request sending method provided by an embodiment of the present application. The embodiment is based on the embodiments shown in FIGS. 2 to 8 and various optional implementation modes, and describes in detail the interaction process between different layers of the first communication node and the interaction process between the first communication node and the second communication node in the resource request sending process. As shown in FIG. 9, the resource request sending method provided by the embodiment includes the following operations.

[0252] 901a: The resource request sending layer of the first communication node sends a first beam event instance to the resource request triggering layer of the first communication node.

[0253] Exemplarily, the first beam event instance in the embodiment can include an event ID and a beam ID1.

[0254] 901b: In response to receiving the first beam event instance, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event instance.

[0255] 902a: The resource request sending layer sends a second beam event instance to the resource request triggering layer.

[0256] Exemplarily, the second beam event instance in the embodiment can include an event ID and a beam ID2.

[0257] 902b: In response to receiving the second beam event instance, the resource request triggering layer starts a monitoring timer of the second beam corresponding to the beam information in the second beam event instance.

[0258] 903a: The resource request sending layer sends a third beam event instance to the resource request triggering layer.

[0259] Exemplarily, the third beam event instance in the embodiment can include: an event ID and a beam ID3.

[0260] 903b: In response to receiving the third beam event instance, the resource request triggering layer starts a monitoring timer of the third beam corresponding to the beam information in the third beam event instance.

[0261] Based on 901a-903b, it can be seen that the management of the monitoring timer in the embodiment is based on each beam, thereby realizing the number statistics of the beam event instance with fine granularity.

[0262] 904: The resource request sending layer continues to send the first beam event instance to the resource request triggering layer until the Nth first beam event instance is sent.

[0263] 905: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, in response to the number of the acquired first beam event instances reaching a first instance number threshold, the resource request triggering layer sends resource request triggering information to the resource request sending layer.

[0264] Optionally, the first instance number threshold is less than or equal to N.

[0265] Exemplarily, the resource request triggering information can include the beam ID1.

[0266] Optionally, in the embodiment, before the monitoring timer of the first beam expires, when the first beam event instance continues to be received, the number of the first beam event instances continues to be accumulated.

[0267] 906: After receiving the resource request triggering information, the resource request sending layer sends a resource request to the second communication node.

[0268] 907: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, a prohibition timer corresponding to the resource request is started.

[0269] 908: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the count of the sending times of the resource request is started.

[0270] 909: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request is suspended.

[0271] In this embodiment, during the suspension of the resource request, the resource request sending layer stops reporting all beam event samples to the resource request triggering layer, so as to avoid the first communication node from running incorrectly and improve the running stability of the first communication node.

[0272] Optionally, in the scenario of the transmission mode A, the resource request sending method further includes the following operation.

[0273] 910a: The second communication node sends resource configuration information to the first communication node.

[0274] 910b: The resource request sending layer sends a beam event report on the resource corresponding to the resource configuration information.

[0275] Optionally, the resource request sending method further includes the following operation.

[0276] 911: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0277] The implementation manner of the first end indication in this embodiment is the same as that of the first end indication shown in the foregoing embodiments, and thus will not be described herein.

[0278] 912: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0279] The implementation manner of the end operation in this embodiment 912 is the same as that of the end operation shown in the foregoing embodiments, and thus will not be described herein.

[0280] Optionally, in this embodiment, if only the monitoring timer of the relevant beam is stopped or the monitoring counter of the relevant beam is cleared, other beam event samples can continue to be counted.

[0281] Optionally, in this embodiment, the prohibition timer corresponding to the resource request can also not be stopped, or the sending times of the resource request can not be cleared. In this embodiment, the sending times of the resource request can be counted by a resource request sending times counter.

[0282] Optionally, in this embodiment, after the prohibition timer corresponding to the resource request is stopped, if other beam event samples meet the condition, the resource request can continue to be triggered.

[0283] Optionally, the resource request sending method further includes the following operation.

[0284] 913a: The second communication node sends a second end indication to the first communication node.

[0285] 913b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0286] The resource request sending method provided in the embodiment suspends the reporting of all beam event samples from the resource request sending layer to the resource request triggering layer during the suspension of the resource request, so as to avoid the running error of the first communication node and improve the running stability of the first communication node.

[0287] FIG. 10 is an interaction schematic diagram of another resource request sending method provided in an embodiment of the present application. The embodiment is based on the embodiments shown in FIGS. 2 to 8 and various optional implementation manners, and describes in detail the interaction process between different layers of the first communication node and the interaction process between the first communication node and the second communication node in the resource request sending process. As shown in FIG. 10, the resource request sending method provided in the embodiment includes the following operations.

[0288] 1001a: The resource request sending layer of the first communication node sends a first beam event sample to the resource request triggering layer of the first communication node.

[0289] Exemplarily, the first beam event sample in the embodiment can include an event ID and a beam ID1.

[0290] 1001b: In response to receiving the first beam event sample, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event sample.

[0291] 1002a: The resource request sending layer sends a second beam event sample to the resource request triggering layer.

[0292] Exemplarily, the second beam event sample in the embodiment can include an event ID and a beam ID2.

[0293] 1002b: In response to receiving the second beam event sample, the resource request triggering layer starts a monitoring timer of a second beam corresponding to the beam information in the second beam event sample.

[0294] 1003a: The resource request sending layer sends a third beam event sample to the resource request triggering layer.

[0295] Exemplarily, the third beam event sample in the embodiment can include an event ID and a beam ID3.

[0296] 1003b: In response to receiving the third beam event sample, the resource request triggering layer starts a monitoring timer of a third beam corresponding to the beam information in the third beam event sample.

[0297] Based on 1001a to 1003b, it can be seen that the management of the monitoring timer in the embodiment is based on each beam, thereby realizing the number statistics of the beam event samples with fine granularity.

[0298] 1004: The resource request sending layer continues to send the first beam event instance to the resource request triggering layer until the Nth first beam event instance is sent.

[0299] 1005: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, the resource request triggering layer sends the resource request triggering information to the resource request sending layer in response to the number of acquired first beam event instances reaching the first instance number threshold.

[0300] Optionally, the first instance number threshold is less than or equal to N.

[0301] Exemplarily, the resource request triggering information can include the beam ID1.

[0302] Optionally, in this embodiment, when the first beam event instance continues to be received before the monitoring timer of the first beam expires, the number of first beam event instances continues to be accumulated.

[0303] 1006: After receiving the resource request triggering information, the resource request sending layer sends the resource request to the second communication node.

[0304] 1007: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the inhibition timer corresponding to the resource request is started.

[0305] 1008: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the count of the sending times of the resource request is started.

[0306] 1009: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request is suspended.

[0307] In this embodiment, during the suspension of the resource request, the resource request sending layer can continue to report the beam event instance to the resource request triggering layer. When the number of acquired second beam event instances reaches the second instance number threshold before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the resource request corresponding to the beam event report of the second beam event instance is sent to the second communication node. This process can be implemented through 1010a and 1010c as follows.

[0308] 1010a: The resource request sending layer continues to send the second beam event instance to the resource request triggering layer until the Rth second beam event instance is sent.

[0309] 1010b: In response to the number of the acquired second beam event instances reaching the second instance quantity threshold before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the resource request triggering layer sends another resource request triggering information to the resource request sending layer.

[0310] Optionally, the second instance quantity threshold is less than or equal to R.

[0311] Exemplarily, the another resource request triggering information can include the beam ID 2.

[0312] Optionally, in the scenario where the prohibit timer is shared by multiple different resource requests, in 1010b, in response to the number of the acquired second beam event instances reaching the second instance quantity threshold before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, and after the prohibit timer corresponding to the resource request expires, the resource request triggering layer sends another resource request triggering information to the resource request sending layer.

[0313] Optionally, in the scenario where the prohibit timer is configured based on the granularity of the resource request, in 1010b, in response to the number of the acquired second beam event instances reaching the second instance quantity threshold before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the resource request triggering layer can directly send another resource request triggering information to the resource request sending layer.

[0314] For example, after the resource request triggered by event 2+beam 1, event 1+beam 2 or event 2+beam 3 meets the triggering condition, the event / beam meeting the condition can be further notified to the resource request indication sending layer.

[0315] 1010c: The resource request sending layer sends a resource request of a beam event report corresponding to the second beam event instance to the second communication node after receiving the another resource request triggering information.

[0316] Optionally, in the scenario of transmission mode A, the resource request sending method further includes the following operations.

[0317] 1011a: The second communication node sends resource configuration information to the first communication node.

[0318] 1011b: The resource request sending layer sends a beam event report on the resource corresponding to the resource configuration information.

[0319] Optionally, in 1011a, the resource configuration information can be for the resource request in 1006, or for the resource request corresponding to the second beam event instance in 1010c. In 1011b, the beam event report triggering the resource request can be sent based on the resource request corresponding to the resource configuration information.

[0320] Optionally, the resource request sending method further includes the following operations.

[0321] 1012: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0322] The implementation of the first end indication in this embodiment is the same as that shown in the foregoing embodiments, and will not be described here again.

[0323] 1013: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0324] The implementation of the end operation in this embodiment 1013 is the same as that shown in the foregoing embodiments, and will not be described here again.

[0325] Optionally, in this embodiment, if only the monitoring timer of the related beam is stopped, or the monitoring counter of the related beam is cleared, other beam event instances can continue to be counted.

[0326] Optionally, in this embodiment, the prohibition timer corresponding to the resource request can also not be stopped, or the sending number of the resource request can not be cleared. In this embodiment, the sending number of the resource request can be counted by a resource request sending number counter.

[0327] Optionally, in this embodiment, after the prohibition timer corresponding to the resource request is stopped, if other beam event instances meet the conditions, the resource request can continue to be triggered.

[0328] Optionally, the resource request sending method further includes the following operations.

[0329] 1014a: The second communication node sends a second end indication to the first communication node.

[0330] 1014b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0331] The resource request sending method provided in this embodiment can continue to report the beam event instance to the resource request triggering layer during suspension of the resource request, so as to avoid affecting the normal business execution of the first communication node.

[0332] FIG. 11 is an interaction diagram of another resource request sending method according to an embodiment of the present application. Based on the embodiments shown in FIGS. 2 to 10 and various optional implementations, this embodiment describes the interaction process between different layers of the first communication node and the interaction process between the first communication node and the second communication node in the resource request sending process. As shown in FIG. 11, the resource request sending method provided by this embodiment includes the following operations.

[0333] 1101a: The resource request sending layer of the first communication node sends a first beam event example to the resource request triggering layer of the first communication node.

[0334] Exemplarily, the first beam event example in this embodiment can include an event ID and a beam ID1.

[0335] 1101b: In response to receiving the first beam event example, the resource request triggering layer starts a monitoring timer of a first beam corresponding to the beam information in the first beam event example.

[0336] 1102a: The resource request sending layer sends a second beam event example to the resource request triggering layer.

[0337] Exemplarily, the second beam event example in this embodiment can include an event ID and a beam ID2.

[0338] 1102b: In response to receiving the second beam event example, the resource request triggering layer starts a monitoring timer of a second beam corresponding to the beam information in the second beam event example.

[0339] 1103a: The resource request sending layer sends a third beam event example to the resource request triggering layer.

[0340] Exemplarily, the third beam event example in this embodiment can include an event ID and a beam ID3.

[0341] 1103b: In response to receiving the third beam event example, the resource request triggering layer starts a monitoring timer of a third beam corresponding to the beam information in the third beam event example.

[0342] Based on 1101a to 1103b, it can be seen that the management of the monitoring timer in this embodiment is based on each beam, thereby realizing the number statistics of the beam event example with fine granularity.

[0343] 1104: The resource request sending layer continues to send the first beam event example to the resource request triggering layer until the Nth first beam event example is sent.

[0344] 1105: Before the monitoring timer of the first beam corresponding to the beam information in the first beam event instance expires, the resource request triggering layer sends resource request triggering information to the resource request sending layer in response to the number of the first beam event instances reaching the first instance number threshold.

[0345] Optionally, the first instance number threshold is less than or equal to N.

[0346] Exemplarily, the resource request triggering information can include the beam ID1.

[0347] Optionally, in this embodiment, when the first beam event instances continue to be received before the monitoring timer of the first beam expires, the number of the first beam event instances continues to be accumulated.

[0348] 1106: After receiving the resource request triggering information, the resource request sending layer sends a resource request to the second communication node.

[0349] 1107: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer starts a prohibit timer corresponding to the resource request.

[0350] 1108: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer starts counting the number of times of sending the resource request.

[0351] 1109: After the resource request triggering layer sends the resource request triggering information to the resource request sending layer, the resource request triggering layer suspends the resource request.

[0352] In this embodiment, during the suspension of the resource request, the resource request sending layer can continue to report the beam event instances to the resource request triggering layer. When the number of the second beam event instances reaches a second instance number threshold before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the resource request corresponding to the beam event report of the second beam event instance is sent to the second communication node. This process can be implemented through 1110a and 1110c as follows.

[0353] 1110a: The resource request sending layer continues to send the second beam event instances to the resource request triggering layer until the Rth second beam event instance is sent.

[0354] 1110b: Before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the resource request triggering layer sends another resource request triggering information to the resource request sending layer in response to the number of the second beam event instances reaching the second instance number threshold.

[0355] Optionally, the second instance number threshold is less than or equal to R.

[0356] Exemplarily, the another resource request trigger information can comprise the beam ID 2.

[0357] Optionally, in the scenario where the prohibit timer is shared by multiple different resource requests, in 1110b, before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, the number of the acquired second beam event instances reaches the second instance number threshold, and after the prohibit timer corresponding to the resource request expires, the resource request trigger layer sends another resource request trigger information to the resource request sending layer.

[0358] Optionally, in the scenario where the prohibit timer is configured based on the granularity of the resource request, in 1110b, before the monitoring timer of the second beam corresponding to the beam information in the second beam event instance expires, in response to the number of the acquired second beam event instances reaching the second instance number threshold, the resource request trigger layer can directly send another resource request trigger information to the resource request sending layer.

[0359] 1110c: After receiving the another resource request trigger information, the resource request sending layer sends the resource request of the beam event report corresponding to the second beam event instance to the second communication node.

[0360] Based on the embodiment shown in FIG. 7, if the resource configuration information sent by the second communication node is not received until the monitoring timer of the first beam expires, after the prohibit timer corresponding to the resource request expires, and when the number of the sent resource requests does not reach the resource request number threshold, the resource request is sent to the second communication node. Or, if the resource configuration information sent by the second communication node is not received until the monitoring timer of the second beam expires, after the prohibit timer corresponding to the resource request expires, and when the number of the sent resource requests does not reach the resource request number threshold, the resource request is sent to the second communication node. This process is repeated until the number of the sent resource requests reaches the resource request number threshold. The resource request sending method provided in this embodiment further comprises the following 1111.

[0361] 1111: In response to the number of the sent resource requests reaching the resource request number threshold, the resource request trigger layer performs an end operation.

[0362] In one scenario, the resource request number threshold in this embodiment can be shared by multiple resource requests. In this scenario, when the number of the resource requests in 1106 and the resource requests in 1110c accumulatively exceeds the resource request number threshold, 1111 is performed.

[0363] In another scenario, the resource request quantity threshold in this embodiment is configured based on resource request granularity, that is, each resource request corresponds to a resource request quantity threshold. In this scenario, the sending times of the resource request in 1106 exceed the corresponding resource request quantity threshold and the sending times of the resource request in 1110c exceed the corresponding resource request quantity threshold, and any one of the two conditions is met, 1111 is executed.

[0364] Optionally, after 1111, the resource request sending method provided in this embodiment includes the following two implementation manners.

[0365] Implementation manner 1: performing a random access procedure based on the random access resource pre-configured by the second communication node. This implementation manner can enable the first communication node to quickly access the network and avoid affecting the normal data transmission of the first communication node.

[0366] Implementation manner 2: not triggering the random access procedure. This implementation manner does not require the second communication node to pre-configure additional random access resources, thereby saving access resources.

[0367] It should be noted that the implementation manner 1 and 1111 can be executed simultaneously or in any order. The implementation manner 2 and 1111 can be executed simultaneously or in any order.

[0368] Optionally, the resource request sending method further includes the following operations.

[0369] 1112: The resource request sending layer sends a first end indication to the resource request triggering layer.

[0370] The implementation manner of the first end indication in this embodiment is the same as the implementation manner of the first end indication shown in the foregoing embodiments, which will not be described here.

[0371] 1113: In response to receiving the first end indication, the resource request triggering layer performs an end operation.

[0372] The implementation manner of the end operation in this embodiment 1113 is the same as the implementation manner of the end operation shown in the foregoing embodiments, which will not be described here.

[0373] Optionally, in this embodiment, if only the monitoring timer of the related beam is stopped or the monitoring counter of the related beam is cleared, other beam event samples can continue to be counted.

[0374] Optionally, in this embodiment, the prohibition timer corresponding to the resource request can also not be stopped, or the sending times of the resource request can not be cleared. In this embodiment, the sending times of the resource request can be counted by a resource request sending times counter.

[0375] Optionally, in the embodiment, after the prohibition timer corresponding to the resource request is stopped, if other beam event instances meet the condition, the resource request can continue to be triggered.

[0376] Optionally, the resource request sending method further includes the following operations.

[0377] 1114a: The second communication node sends a second end indication to the first communication node.

[0378] 1114b: In response to receiving the second end indication sent by the second communication node, the resource request triggering layer performs an end operation.

[0379] The resource request sending method provided in the embodiment can perform an end operation by the resource request triggering layer when the number of times of sending the resource request reaches the resource request quantity threshold, so as to release the resource of the first communication node and save the processing resource of the first communication node.

[0380] FIG. 12 is a flow diagram of another resource request sending method provided in an embodiment of the application. The embodiment describes in detail the implementation of the second communication node preconfiguring the event configuration information and the resource request configuration information for the first communication node on the basis of the embodiments shown in FIGS. 2 to 11 and various optional implementation manners. As shown in FIG. 12, the resource request sending method provided in the embodiment further includes the following operations.

[0381] 1201: Receive the event configuration information and the resource request configuration information sent by the second communication node.

[0382] The resource request configuration information includes the prohibition duration of the prohibition timer of the resource request and the resource request quantity threshold. The resource request configuration information is configured based on at least one of the following granularities: based on each event configuration; based on each beam configuration of each event; based on each cell configuration; and based on each cell group configuration.

[0383] Optionally, in the scenario where the resource request configuration information is configured based on each cell group, for all terminal devices in the cell group, the resource request triggered by the beam event report (or referred to as the beam event instance) applies a set of resource request configurations.

[0384] It should be noted that the resource request quantity threshold in the embodiment can also be referred to as the maximum retransmission number of the resource request or the maximum number of sending the resource request.

[0385] For the first communication node, there can be multiple resource request configuration information corresponding thereto. For example, the cell group to which the first communication node belongs corresponds to resource request configuration information 1, the cell to which the first communication node belongs corresponds to resource request configuration information 2, and a certain event of the first communication node corresponds to resource request configuration information 3. For the first communication node, the finally corresponding resource request configuration information should satisfy resource request configuration information 1, resource request configuration information 2 and resource request configuration information 3 at the same time. In other words, the first communication node takes the intersection of the multiple granularity resource configuration information corresponding thereto to satisfy the constraint of any one granularity resource configuration information. For another example, based on the resource request configuration information of each cell group, the corresponding resource configuration information can be configured on the primary cell (Pcell) or the secondary cell (Scell).

[0386] Optionally, the resource request configuration information can further include resource request identification, which can be represented by UEIBR (UE Initiate Beam Report, UE triggered beam report) SR request ID.

[0387] FIG. 13 is a schematic diagram of resource request configuration information according to an embodiment of the present application. As shown in FIG. 13, it shows that the resource request configuration information is configured based on each cell. A certain cell group includes n cells, and the resource request configuration information corresponding to each cell can be configured. In FIG. 13, the cell group is represented by a cell group MAC entity. In FIG. 13, cell 1 is taken as an example of Pcell.

[0388] It should be noted that the cell in the embodiment can also be referred to as a component carrier (CC).

[0389] FIG. 14 is a schematic diagram of another resource request configuration information according to an embodiment of the present application. As shown in FIG. 14, it shows that the resource request configuration information is configured based on each cell. A certain cell group includes n cells. In the upper part of FIG. 14, the resource request configuration information corresponding to cell 1 (Pcell) is configured. In the lower part of FIG. 14, the resource request configuration information corresponding to cell 2 is configured.

[0390] Optionally, the event configuration information in the embodiment includes the following three implementation manners.

[0391] Implementation 1: Event configuration information based on mixed configuration of cell group level and cell level. Implementation 2: Event configuration information based on mixed configuration of cell group level and bandwidth part level. Implementation 3: Event configuration information based on mixed configuration of cell group level, cell level and bandwidth part level.

[0392] FIG. 15 is a schematic diagram of event configuration information according to an embodiment of the present application. As shown in FIG. 15, the event configuration information based on mixed configuration of cell group level and cell level includes: a report configuration list corresponding to the cell group, wherein the report configuration list (ReportConfigList) includes multiple report configuration information (denoted as ReportConfig1, ReportConfig2, …, ReportConfigX); the report configuration information corresponding to the cell in the report configuration list in the cell group, and the new beam list (NewBeamIDList) corresponding to the cell.

[0393] In FIG. 15, the resource request configuration information is configured based on each cell group as an example. As shown in FIG. 15, a resource request identifier for triggering a bottom beam event is configured, for example, UEIBR SR request ID. The resource request identifier can be associated with a resource request list configured based on the cell group. The resource request list of the cell group includes multiple elements, and each element includes: a resource request identifier, a prohibit duration of a resource request interval / prohibit timer, and a maximum number of resource request transmissions. As shown in FIG. 15, a report configuration list corresponding to the cell group also needs to be configured. The report configuration list includes multiple report configuration information. In this embodiment, each report configuration information includes at least one of the following: an event identifier, a reference signal type, a threshold value, a monitoring duration of a monitoring timer, a threshold value of a sample quantity, a frequency or period of event reporting, a total number of continuous event reporting, a transmission mode, a number of reported beams, and whether the current beam number is included in the reporting. The threshold value in this embodiment refers to the threshold value of the beam event.

[0394] It should be noted that for one beam event, it can correspond to one or more report configuration information. In other words, an event can appear multiple times in the report configuration list. The report configuration information in this embodiment does not include new beam information.

[0395] For each cell in FIG. 15, the report configuration information corresponding to the cell in the report configuration list of the cell group and the new beam list corresponding to the cell also need to be configured. For example, the report configuration information in the report configuration list of the cell group can be indexed by the identifier (ReportConfigID) of the report configuration information.

[0396] Optionally, the new beam list corresponding to the cell can include a new beam identifier.

[0397] In this embodiment, the reporting configuration information corresponding to the cell in the reporting configuration list and the new beam list corresponding to the cell can be referred to as UEIBRConfig. Each cell can correspond to at least one UEIBRConfig. In FIG. 15, cell 1 corresponds to UEIBRConfig 1, UEIBRConfig 2, and UEIBRConfig 3 as an example.

[0398] It should be noted that part or all of the content in the reporting configuration information can also be configured at the cell level. For example, the event identifier, reference signal type, or threshold of each cell is configured.

[0399] Based on the implementation, the resource request sending method provided in this embodiment further includes the following operations: on the activated BWP, determining the new beam list used on the activated BWP from the new beam list corresponding to the cell where the first communication node is located; and performing beam measurement and beam event report on the new beam list used on the activated BWP. Corresponding to this operation, in the new beam list corresponding to the cell, the beam identifier can be indicated by the resource identifier corresponding to the SSB or CSI. The first communication node can further indicate the BWP where it is located by the resource identifier corresponding to the SSB or CSI (hereinafter referred to as CSI identifier). For example, in the new beam list, the following CSI identifiers are indicated, and the corresponding BWP relationship is as follows: CSI identifiers 1-8, wherein CSI identifiers 1-3 correspond to BWP 1, CSI identifiers 4-5 correspond to BWP 2, CSI identifiers 6-7 correspond to BWP 3, and CSI identifier 8 corresponds to BWP 4. In this way, when the first communication node works on BWP 1, it only needs to consider the beams corresponding to CSI identifiers 1-3, and when it works on BWP 2, it only needs to consider the beams corresponding to CSI identifiers 4-5. Similarly.

[0400] FIG. 16 is a schematic diagram of another event configuration information provided in an embodiment of the present application. As shown in FIG. 16, the event configuration information based on the mixed configuration at the cell group level and the partial bandwidth level includes: a reporting configuration list corresponding to the cell group, wherein the reporting configuration list includes multiple reporting configuration information; and the BWP of the cell in the cell group corresponding to the reporting configuration information in the reporting configuration list and the new beam list corresponding to the BWP.

[0401] The difference between FIG. 16 and FIG. 15 is that the configuration based on the cell in FIG. 15 becomes the configuration based on the BWP. In FIG. 16, part or all of the reporting configuration list based on the cell group can also be configured as the granularity of the BWP.

[0402] FIG. 16 takes the cell including BWP1, BWP2, BWP3 and BWP4 as an example for illustration. In FIG. 16, each BWP corresponds to a UEIBRConfigList. The UEIBRConfigList includes at least one UEIBRConfigID. In FIG. 16, the UEIBRConfigList of BWP1 of cell 1 includes UEIBRConfig1, UEIBRConfig2 and UEIBRConfig3 for example. Each UEIBRConfigID includes the report configuration information (ReportConfigID) corresponding to the BWP in the report configuration list and the new beam list corresponding to the BWP.

[0403] FIG. 17 is a schematic diagram of another event configuration information according to an embodiment of the present application. As shown in FIG. 17, the event configuration information based on the mixed configuration of the cell group level, the cell level and the partial bandwidth level includes: the report configuration list corresponding to the cell group, wherein the report configuration list includes multiple report configuration information; the report configuration information corresponding to the cell in the report configuration list in the cell group; and the new beam list corresponding to the BWP of the cell.

[0404] The difference between FIG. 17 and FIG. 15 is that the new beam list is configured based on each BWP. The ReportConfigIDList in FIG. 17 is used to indicate the report configuration information corresponding to the cell in the report configuration list.

[0405] FIG. 18 is a schematic diagram of another event configuration information according to an embodiment of the present application. As shown in FIG. 18, the event configuration information based on the mixed configuration of the cell group level, the cell level and the partial bandwidth level includes: the report configuration list corresponding to the cell group, wherein the report configuration list includes multiple report configuration information; the new beam pool corresponding to the cell in the cell group; the report configuration information corresponding to the BWP of the cell in the report configuration list and the new beam list corresponding to the new beam pool.

[0406] FIG. 18 differs from FIG. 16 in that a new beam pool is configured at the cell level. Based on the BWP granularity, each BWP is configured with corresponding report configuration information in the report configuration list and corresponding new beam list in the new beam pool. Exemplarily, the BWP can be configured with the corresponding new beam list in the new beam pool through a new beam index. The UEIBRConfigList includes at least one UEIBRConfigID. In FIG. 18, the UEIBRConfigList of BWP1 of cell 1 includes UEIBRConfig1, UEIBRConfig2, and UEIBRConfig3 as an example. Each UEIBRConfigID includes corresponding report configuration information (ReportConfigID) in the report configuration list and the corresponding new beam list in the new beam pool.

[0407] In this configuration mode, the report configuration information can also be configured based on the cell or based on the BWP granularity.

[0408] The resource request sending provided by the embodiment can be based on the event configuration information and the resource request configuration information configured in different granularities, thereby achieving flexible configuration of the event configuration information and the resource request configuration information, improving the flexibility and applicability of the resource request sending, and meeting different service requirements.

[0409] The embodiment further provides a path loss (PL) offset reporting method.

[0410] In a conventional base station, an uplink and a downlink are simultaneously provided by one base station, and the uplink path loss can be estimated through the downlink. With the introduction of a transmission and reception point (TRP), when a certain TRP only serves as an uplink transmission point, the path loss between a UE and the uplink TRP can be inconsistent with the downlink path loss between the base station and the UE. Thus, when the UE performs uplink path loss estimation, an uplink path loss offset needs to be added to the downlink path loss.

[0411] PL(UL) = PL(DL) + PL offset. In closed-loop power control, the PL offset is usually configured by the network.

[0412] For the scenario that one UE can perform uplink transmission with multiple TRPs, the network can configure PL offset for each activated TCI state of each TRP, and when the PL offset changes, the change of the PL offset can also be indicated by a MAC CE (MAC Control element). Thus, the MAC CE needs to be designed to be compatible with the scenario of one or multiple TRPs. In this application, two TRPs are taken as an example, and the same logic can be extended to the scenario of more than two TRPs.

[0413] When the TRP PL offset is indicated by the MAC CE, there are two schemes as follows. Scheme 1: Only the PL offset corresponding to the currently used TCI state is indicated.

[0414] FIG. 19 is a schematic diagram of the MAC CE for indicating only the PL offset corresponding to the currently used TCI state according to an embodiment of the present application. As shown in FIG. 19, in this scheme:

[0415] In the first byte: ServingCell ID is used to indicate the cell identification using the PL offset MAC CE;

[0416] BWP ID: is used to indicate the BWP identification of the uplink;

[0417] In the second byte: P1, P2 are used as follows:

[0418] P1 is used to indicate whether the PL offset corresponding to the first TCI state exists, and P2 is used to indicate whether the PL offset corresponding to the second TCI state exists. Pathloss Offset 1 indicates the PL offset corresponding to the first TCI state, and Pathloss Offset 2 indicates the PL offset corresponding to the second TCI state.

[0419] As an optimization scheme, if only one of P1 and P2 indicates the existence (for example, set to 1), Pathloss Offset 1 can be used as the PL offset of the corresponding TCI state. For example:

[0420] P1P2=10, the pathloss offset 1 indicates the PL offset corresponding to the first TCI state;

[0421] P1P2=01, the pathloss offset 1 indicates the PL offset corresponding to the second TCI state;

[0422] P1P2=11: the pathloss offset 1 indicates the PL offset corresponding to the first TCI state;

[0423] The pathloss offset 2 indicates the PL offset corresponding to the second TCI state.

[0424] The third byte exists only when both P1 / P2 indicate 1, for indicating the second TCI state.

[0425] The roles of P1 and P2 as above can also be exchanged: P1 is used to indicate whether the PL offset corresponding to the second TCI state exists, and P2 is used to indicate whether the PL offset corresponding to the first TCI state exists.

[0426] Scheme 2: Indicate the PL offset corresponding to the currently activated TCI state. Generally, there are 8 activated TCI states for each TRP.

[0427] Scheme 2.1

[0428] FIG. 20 is a schematic diagram of a MAC CE for indicating the PL offset corresponding to the currently activated TCI state according to an embodiment of the present application. As shown in FIG. 20, in scheme 2.1:

[0429] In the first byte: ServingCell ID is used to indicate the cell identification using the PL offset MAC CE;

[0430] BWP ID: used to indicate the BWP identification of the uplink;

[0431] The bit in the second and third bytes is used to indicate whether the PL offset needs to be updated on the corresponding TCI state. Wherein F i,j is used to indicate the i-th TCI state group. Here, a total of 8 TCI state groups can be indicated, corresponding to 8 codepoints in the downlink control information (DCI). Each state group contains two TCI states, and j (j = 1 or 2) indicates the PL offset of the j-th TCI state in the two TCI states.

[0432] In the subsequent bytes, in turn, F i,j = 1 corresponds to the PL offset of the TCI state. For example, the second and third bytes are set as follows:

[0433] F 1,1 = 1 / F 2.2 = 1 / F 8.1 = 1, the fourth byte corresponds to the PL offset of the first TCI state in the first TCI state group, the fifth byte corresponds to the PL offset of the second TCI state in the second TCI state group, and the sixth byte corresponds to the PL offset of the first TCI state in the eighth TCI state group.

[0434] Scheme 2.2

[0435] Figure 21 is a schematic diagram of a MAC CE indicating the PL offsets corresponding to the currently activated TCI states according to another embodiment of the present application. As shown in Figure 21, the meanings of the first to third bytes are the same as described in Scheme 2.1. However, in order to save signaling, the PL offsets corresponding to the TCI states with F i,j = 1 will be listed in the subsequent bit positions in turn. For example, the first PL offset occupies the last 5 bit positions of the fourth byte, the second PL offset occupies the first 3 bit positions of the fourth byte and the last two bit positions of the fifth byte, and so on.

[0436] In this way, if there are some bit positions left in the last byte, the reserved (R) bit can be used to fill in the bit positions. Here, if there are m F i,j = 1 in the second and third bytes, (m*5) mod 8 reserved bits are needed to fill in, as shown in the above figure.

[0437] Scheme 2.3

[0438] Figure 22 is a schematic diagram of a MAC CE indicating the PL offsets corresponding to the currently activated TCI states according to yet another embodiment of the present application. As shown in Figure 22, as another optimization scheme: the meaning of the first byte is the same as described in Scheme 2.1.

[0439] In the second byte, F i = 1 is used to indicate the i-th TCI state group. Here, a total of 8 TCI state groups can be indicated, corresponding to 8 code points in the downlink control information (DCI). As described in Scheme 2.1, each state group contains two TCI states, and when any one or all of the TCI states need to be updated, the corresponding F i = 1.

[0440] In the subsequent bytes, P1, P2 are used as follows:

[0441] P1 is used to indicate whether the PL offset corresponding to the first TCI state in the corresponding TCI state group exists, and P2 is used to indicate whether the PL offset corresponding to the second TCI state exists. As shown in the third and fourth bytes in the figure, Pathloss Offset 1 indicates the PL offset corresponding to the first TCI state, and Pathloss Offset 2 indicates the PL offset corresponding to the second TCI state. The same logic is used in the subsequent bytes.

[0442] As an optimization scheme, if only one of P1 and P2 indicates the existence (for example, set to 1), the Pathloss Offset in the same byte can be used as the PL offset of the corresponding TCI state. For example, take the third and fourth bytes as an example (the same logic is used in the subsequent bytes):

[0443] P1P2 = 10, the pathloss offset 1 indicates the PL offset corresponding to the first TCI state;

[0444] P1P2 = 01, the pathloss offset 1 indicates the PL offset corresponding to the second TCI state;

[0445] P1P2 = 11: the pathloss offset 1 indicates the PL offset corresponding to the first TCI state;

[0446] The pathloss offset 2 indicates the PL offset corresponding to the second TCI state.

[0447] As above, the roles of P1 and P2 can also be exchanged: P1 is used to indicate whether the PL offset corresponding to the second TCI state exists, and P2 is used to indicate whether the PL offset corresponding to the first TCI state exists.

[0448] FIG. 23 is a schematic diagram of a MAC CE indicating the PL offset corresponding to the currently activated TCI state according to another embodiment of the present application. For the MAC CE as shown in FIG. 23, F2 / F3 / F5 = 1 ， which represents that the three TCI state groups will have the PL offset updated.

[0449] Then see here the third byte, P1 / P2=11, so for F2, 2 bytes are needed to indicate the PL offset of the first and second TCI state in the corresponding TCI state group, i.e. the third and fourth bytes.

[0450] Here in the fifth byte, P0=0 / P2=1, then the PL offset of the second TCI state in the corresponding TCI state group of F3 needs to be indicated, i.e. indicated by the PL offset in the fifth byte.

[0451] In the sixth byte, P0=1 / P2=0, then the PL offset of the first TCI state in the corresponding TCI state group of F5 needs to be indicated, i.e. indicated by the PL offset in the sixth byte.

[0452] That is, here F i For determining whether there is a PL offset update for the corresponding TCI state group, and the corresponding P1 / P2 is used to determine whether there is a PL offset for each state in each state group.

[0453] Based on the MAC CE, the UE can do the following processing:

[0454] When receiving the MAC CE, the pathloss value of the TCI state is updated in combination with the PL information in the corresponding TCI state indication in the RRC signaling. There are two ways to update:

[0455] The first is to adjust the PL offset based on the downlink-based pathloss indicated by the RRC in combination with the PL offset indicated in the MAC CE.

[0456] The second is to adjust the PL offset based on the downlink-based pathloss and the pathloss offset indicated by the RRC in combination with the PL offset indicated in the MAC CE.

[0457] When the UE receives the PL offset MAC CE containing the TCI state indication for the second time, if the indication indicates a new PL offset indication for the TCI state, the UE can have the following four operation modes to adjust the PL.

[0458] The first is to adjust the PL offset based on the downlink-based pathloss indicated by the RRC in combination with the PL offset indicated in the second MAC CE.

[0459] The second is to adjust based on the downlink-based pathloss indicated by RRC, combined with the PL offset indicated by the first MAC CE and combined with the PL offset indicated by the second MAC CE.

[0460] The third is to adjust based on the downlink-based pathloss and pathloss offset indicated by RRC, combined with the PL offset indicated by the second MAC CE.

[0461] The fourth is to adjust the PL offset based on the downlink-based pathloss and pathloss offset indicated by RRC, combined with the PL offset indicated by the first MAC CE and combined with the PL offset indicated by the second MAC CE.

[0462] In addition, for a certain TCI state, the PL offset is indicated in the first MAC CE, and then the deactivation indication of the TCI state is received, and when the TCI state is activated again, there are two adjustment methods as follows.

[0463] The first is to adjust according to the pathloss information indicated by RRC, which includes downlink-based pathloss information, pathloss offset information, etc.

[0464] The second is to adjust according to the pathloss information before deactivation, that is, to adjust the pathloss information indicated by the previous MAC CE in combination with the pathloss information indicated by RRC.

[0465] After the TCI state is activated again, if the network further indicates the PL offset information through the MAC CE, the UE has two adjustment methods.

[0466] The first is to adjust according to the pathloss information indicated by RRC, combined with the PL offset information indicated by the latest received MAC CE, which includes downlink-based pathloss information, pathloss offset information, etc.

[0467] The second is to adjust according to the pathloss information before deactivation (that is, to adjust the pathloss information indicated by the previous MAC CE in combination with the pathloss information indicated by RRC), combined with the PL offset information indicated by the current received MAC CE.

[0468] As above, when receiving the MAC CE indicating the PL offset, there are two reference bases as follows:

[0469] One is the Pathloss information indicated by the RRC, which includes the downlink-based pathloss information, pathloss offset information, etc.

[0470] One is the Pathloss information indicated by the RRC (which includes the downlink-based pathloss information, pathloss offset information, etc.) combined with the Pathloss offset information indicated by the previous MAC CE.

[0471] Embodiments of the present application also provide a communication node, comprising: a processor configured to implement a method as provided in any of the embodiments of the present application when executing a computer program. Illustratively, the communication node can be a first communication node. The first communication node comprises: a processor configured to implement a resource request sending method as provided in any of the embodiments of the present application when executing a computer program. Illustratively, the first communication node can be a terminal such as a UE provided in any of the embodiments of the present application. The present application does not make specific limitations in this regard.

[0472] Illustratively, the following embodiments provide a communication node as a terminal device structure schematic diagram.

[0473] FIG. 24 is a structure schematic diagram of a terminal provided in an embodiment of the present application. The terminal can be implemented in various forms, and the terminal in the present application can include, but is not limited to, mobile terminal devices such as mobile phones, smart phones, notebook computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (PADs), portable media players (PMPs), navigation devices, vehicle-mounted terminal devices, vehicle-mounted display terminals, vehicle-mounted electronic rearview mirrors, etc., and fixed terminal devices such as digital televisions (TVs), desktop computers, etc.

[0474] As shown in FIG. 24, the terminal 50 can include a wireless communication unit 51, an audio / video (A / V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, a processor 58, and a power supply unit 59, etc. FIG. 24 shows a terminal including various components, but it is understood that implementation of all of the illustrated components is not required. More or fewer components can alternatively be implemented.

[0475] In the present embodiment, the wireless communication unit 51 allows radio communication between the terminal 50 and a base station or a network. The A / V input unit 52 is configured to receive audio or video signals. The user input unit 53 can generate key input data according to a user input command to control various operations of the terminal 50. The sensing unit 54 monitors a current state of the terminal 50, a location of the terminal 50, a presence or absence of a user's touch input with respect to the terminal 50, an orientation of the terminal 50, acceleration or deceleration movement and direction of the terminal 50, and the like, and generates a command or a signal for controlling the operation of the terminal 50. The interface unit 57 serves as an interface through which at least one external device can be connected to the terminal 50. The output unit 55 is configured to provide an output signal in a form of visual, audio, and / or tactile. The memory 56 can store software programs and the like for processing and control operations performed by the processor 58, or can temporarily store data that has been output or is to be output. The memory 56 can include at least one type of storage medium. Also, the terminal 50 can cooperate with a network storage device that performs a storage function of the memory 56 through a network connection. The processor 58 generally controls overall operations of the terminal 50. The power supply unit 59 receives external power or internal power under the control of the processor 58 and provides appropriate power required for operating various elements and components.

[0476] The processor 58 performs at least one function application and data processing, such as implementing the method provided by the embodiments of the present application, by running programs stored in the memory 56.

[0477] The embodiments of the present application also provide a computer readable storage medium, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the method provided by any of the embodiments of the present application.

[0478] The computer storage medium of the embodiments of the present application can adopt any combination of one or more computer readable media. The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. The computer readable storage medium includes, but is not limited to, a non-exhaustive list: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus.

[0479] The computer readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, bearing computer readable program code. Such propagated data signal can take on many forms, including but not limited to electro-magnetic, optical or any suitable combination thereof. The computer readable signal medium can also be any computer readable medium that is not a computer readable storage medium and that can be used to carry or store program code used by or in conjunction with an instruction execution system, device or apparatus.

[0480] The program code contained on the computer readable medium can be transmitted using any suitable medium, including but not limited to wireless, wire line, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0481] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, Ruby, Go, or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0482] Those skilled in the art will appreciate that the term user terminal encompasses any appropriate type of wireless user equipment, such as a mobile phone, a portable data processing apparatus, a portable web browser, or a vehicle mounted mobile station.

[0483] In general, the various embodiments of the application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in

[0484] Embodiments of the application can be implemented by the data processor of a mobile device executing computer program instructions, for example in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be in assemblies, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or in any combination of one or more programming languages, executed on one or more computing devices.

[0485] The block diagrams of any logical flow of the present application in the drawings can represent program operations, or can represent interconnecting logical circuits, modules and functions, or can represent a combination of program operations and logical circuits, modules and functions. The computer program can be stored on a memory. The memory can have any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as, but not limited to, read only memory (ROM), random access memory (RAM), optical storage devices, and systems such as digital versatile disc (DVD) or CD-ROM, and the like. The computer readable media can include non-transitory storage media. The data processor can be of any type suitable for the local technical environment, and can include, but is not limited to, general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and processors based on multi-core processor architectures, as examples.

Claims

A resource request sending method applied to a first communication node, comprising: starting a monitoring timer of a beam corresponding to beam information in a beam event sample in response to obtaining the beam event sample; sending a resource request to a second communication node in response to a quantity of obtained first beam event samples reaching a first sample quantity threshold before a monitoring timer of a first beam corresponding to beam information in the first beam event sample expires, wherein the first beam event sample is a beam event sample in which a quantity of beam event samples obtained before a monitoring timer of a beam corresponding to beam information expires reaches a sample quantity threshold corresponding to the beam. The method of claim 1, after the sending of the resource request to the second communication node, further comprising: starting a prohibit timer corresponding to the resource request, and prohibiting the sending of the resource request again before the prohibit timer corresponding to the resource request expires; starting counting of a sending quantity of the resource request; suspending the resource request. The method of claim 2, wherein, The starting of the monitoring timer of the beam corresponding to the beam information in the beam event sample in response to the obtaining of the beam event sample comprises: sending, by a resource request sending layer of the first communication node, the beam event sample to a resource request triggering layer of the first communication node; starting, by the resource request triggering layer, the monitoring timer of the beam corresponding to the beam information in the beam event sample in response to the receiving of the beam event sample, wherein each beam corresponds to a monitoring timer. The method of claim 3, wherein, The sending of the resource request to the second communication node comprises: sending, by the resource request triggering layer, resource request triggering information to the resource request sending layer; sending, by the resource request sending layer, the resource request to the second communication node in response to the receiving of the resource request triggering information. The method of claim 4, wherein, The resource request triggering information comprises at least one of event information and related beam information of the beam event sample. The method of claim 4, wherein, The starting of the prohibit timer corresponding to the resource request comprises: starting, by the resource request triggering layer, the prohibit timer corresponding to the resource request. The method of claim 6, further comprising: sending, by the resource request sending layer, a first end indication to the resource request triggering layer; performing, by the resource request triggering layer, an end operation in response to the receiving of the first end indication. The method of claim 7, wherein, The first end indication is an indication sent by the resource request sending layer at any one of the following times: after the sending of the resource request; after the receiving of resource configuration information sent by the second communication node; or after the sending of a beam event report to the second communication node. The method of claim 7, wherein, The first end indication comprises the resource request sending indication or beam information related to the beam event. The beam information related to the beam event comprises at least one of the following: beam information corresponding to the first beam, beam information corresponding to a beam satisfying a triggering condition of a beam event report, or all beam information included in the beam event report. The method of claim 9, wherein, The end operation comprises at least one of the following: stopping the monitoring timer of the first beam; stopping a monitoring timer of a beam corresponding to the beam event related beam information; stopping monitoring timers of all beams; clearing a monitoring counter of the first beam; clearing a monitoring counter of a beam corresponding to the beam event related beam information; clearing monitoring counters of all beams; stopping a prohibit timer corresponding to the resource request; clearing a number of times of sending the resource request; or deleting the suspended resource request. The method of claim 3, further comprising: in response to receiving a second end indication sent by the second communication node, the resource request trigger layer performing an end operation. The method of claim 11, wherein, The second end indication comprises at least one of: an indication of changing a current beam of the first communication node; an updated new beam list indication; an activated transmission configuration indicator state (TCI) state update information indication; or network reconfiguration information. The method of claim 1, after sending the resource request to the second communication node, the method further comprising: continuing to accumulate a number of the first beam event instances when the first beam event instances continue to be received before a monitoring timer of the first beam expires. The method of claim 4, further comprising any one of: in response to sending resource request trigger information to the resource request sending layer, the resource request trigger layer stopping the monitoring timer of the first beam; in response to receiving a first end indication, the resource request trigger layer stopping the monitoring timer of the first beam; or the monitoring timer of the first beam expires. The method of claim 1, after sending the resource request to the second communication node, further comprising: receiving resource configuration information sent by the second communication node; sending a beam event report on a resource corresponding to the resource configuration information. The method of claim 2, after sending the resource request to the second communication node, further comprising: in response to monitoring that the second communication node does not send resource configuration information, sending the resource request to the second communication node after a prohibit timer corresponding to the resource request expires. The method of claim 2, after sending the resource request to the second communication node, further comprising: in response to monitoring that the second communication node does not send resource configuration information until the monitoring timer of the first beam expires, sending the resource request to the second communication node after a prohibit timer corresponding to the resource request expires and in response to a number of times of sending the resource request not reaching a resource request quantity threshold. The method of claim 3, further comprising: in response to the number of times of sending the resource request reaching the resource request quantity threshold, the resource request trigger layer performing an end operation. The method of claim 18, further comprising: performing a random access procedure based on a random access resource preconfigured by the second communication node. The method of claim 3, further comprising: during suspending the resource request, the resource request sending layer stopping reporting all beam event instances to the resource request trigger layer. The method of claim 3, further comprising: during the suspension of the resource request, the resource request sending layer continues to report beam event instances to the resource request triggering layer; when the number of the second beam event instances reaches a second instance number threshold before a monitoring timer of a second beam corresponding to beam information in a second beam event instance expires, sending a resource request of a beam event report corresponding to the second beam event instance to the second communication node. The method of claim 1, wherein, The resource request is used to indicate resource information of beam event report sending; The method further comprises: sending a beam event report on a resource corresponding to the resource information indicated by the resource request. The method of claim 1, wherein, The beam event instance comprises a beam event identifier, and the resource request comprises a scheduling request or a new uplink control information (UCI). The method of claim 1, further comprising: receiving event configuration information and resource request configuration information sent by the second communication node, wherein the resource request configuration information comprises a prohibit duration of a prohibit timer of a resource request and a resource request number threshold, and the resource request configuration information is configured based on at least one of the following granularities: per-event configuration, per-event-per-beam configuration, per-cell configuration, and per-cell group configuration. The method of claim 24, wherein, The event configuration information comprises: event configuration information configured based on a hybrid of a cell group level and a cell level; event configuration information configured based on a hybrid of a cell group level and a partial bandwidth level; event configuration information configured based on a hybrid of a cell group level, a cell level, and a partial bandwidth level. The method of claim 25, wherein, The event configuration information configured based on a hybrid of a cell group level and a cell level comprises: a report configuration list corresponding to a cell group, wherein the report configuration list comprises a plurality of report configuration information; report configuration information corresponding to a cell in the cell group in the report configuration list, and a new beam list corresponding to the cell. The method of claim 26, further comprising: on an activated partial bandwidth (BWP), determining a new beam list used on the activated BWP from a new beam list corresponding to a cell in which the first communication node is located; performing beam measurement and beam event report reporting for the new beam list used on the activated BWP. The method of claim 25, wherein, The event configuration information configured based on a hybrid of a cell group level and a partial bandwidth level comprises: a report configuration list corresponding to a cell group, wherein the report configuration list comprises a plurality of report configuration information; report configuration information corresponding to a BWP of a cell in the cell group in the report configuration list, and a new beam list corresponding to the BWP. The method of claim 25, wherein, The event configuration information configured based on a hybrid of a cell group level, a cell level, and a partial bandwidth level comprises: a report configuration list corresponding to a cell group, wherein the report configuration list comprises a plurality of report configuration information; report configuration information corresponding to a cell in the cell group; a new beam list corresponding to a BWP of the cell. The method of claim 25, wherein, The event configuration information configured based on a hybrid of a cell group level, a cell level, and a partial bandwidth level comprises: A report configuration list corresponding to the cell group, wherein the report configuration list comprises a plurality of report configuration information; A new beam pool corresponding to a cell in the cell group; BWP of the cell corresponding to report configuration information in the report configuration list and a new beam list corresponding to the new beam pool. The method of any one of claims 26 to 30, wherein, Each of the report configuration information comprises at least one of the following: Event identification, reference signal type, threshold, monitoring duration of a monitoring timer, sample quantity threshold, frequency or period of event reporting, total number of continuous event reporting, transmission mode, number of reported beams, and whether to include the current beam number in the reporting. A communication node, comprising: A processor; The processor is configured to implement the resource request sending method according to any one of claims 1-31 when executing the computer program. A computer readable storage medium storing a computer program, wherein the computer program is configured to implement the resource request sending method according to any one of claims 1-31 when executed by a processor.

Images