Method and apparatus for node used for wireless communication beam management

Abstract

The present application discloses a method and apparatus for a node used for wireless communication beam management. A first node transmits a first information block and a second information block, the first information block indicating the transmission of the second information block, and the second information block comprising report information of beam management. The transmission of the first information block is triggered by an event; the first information block is transmitted on a PUCCH, and a resource occupied by the second information block is non-dynamically scheduled; a start moment of the first information block to a start moment of the second information block are a first time window; and a PUSCH time domain resource indicated by dynamic scheduling received by the first node in the first time window is orthogonal to a time domain resource occupied by the second information block. The present application establishes a common configuration between a base station and a terminal, ensuring reliable transmission of the report information.

Description

A method and apparatus in a node used for wireless communication beam management

[0001] The present application claims priority from the Chinese patent application No. 2024110304276, filed on July 29, 2024, and entitled "A method and apparatus in a node used for wireless communication beam management", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to a signal transmission method and apparatus in a wireless communication system, and in particular to a method and apparatus in a node used for wireless communication beam management. BACKGROUND

[0003] Multi-antenna technology and beamforming are key technologies in 3GPP (3rd Generation Partner Project) LTE (Long-Term Evolution) systems and NR (New Radio) systems; by configuring multiple antennas at a communication node, such as a base station or a UE (User Equipment), additional spatial degrees of freedom are obtained. Multiple antennas form beams pointing in a specific direction through beamforming to improve communication quality, and when multiple antennas belong to multiple TRPs (Transmitter Receiver Points) / panels, additional diversity gain can also be obtained by utilizing the spatial differences between different TRPs / panels. In the NR system, beam management is crucial to maintaining efficient communication, and the beam reporting mechanism enables the base station to understand the quality of each beam in real time, so as to select the best beam for communication. The problem with the traditional beam management mechanism is that frequent reporting will result in a large amount of uplink and control signaling overhead, which not only increases the power consumption of the UE, but also leads to waste of uplink resources.

[0004] In December 2023, the WI (Work Item) of NR MIMO Phase 5 was passed in the RAN (Radio Access Network) #102 plenary meeting. The RAN1 working group aims to implement UE-initiated / event-driven beam management for the single-TRP (sTRP) scenario of FR2 (Frequency Radio range 2) based on unified TCI (Transmission Configuration Indicator) configuration in the traditional CSI (Channel State Information) measurement and reporting configuration framework in the Rel-19 stage. The purpose is to reduce the uplink reporting overhead and control signaling overhead by UE actively monitoring and reporting beam quality changes, improve the efficiency and response speed of beam management, and thus improve the overall network performance. SUMMARY

[0005] One implementation of UE-initiated / event-driven beam management is that the UE first sends an uplink indication on the PUCCH channel to inform the base station that the UE will carry the uplink report of beam management in the preconfigured uplink channel later. The inventors have found through research that after the UE sends the PUCCH carrying the uplink indication, the UE may still receive uplink scheduling signaling from the base station. Whether the UE transmits the uplink report on the PUSCH resource scheduled by the uplink scheduling signaling is a problem that needs to be solved.

[0006] To solve the above problems, a solution is disclosed in the present application. It should be noted that in the description of the above problems, the NR system is taken as an example, and the present application is also applicable to scenarios such as future 6G systems, and achieves similar technical effects to the NR system. Further, although the original intention of the present application is for MIMO scenarios, the present application can also be applied to other non-MIMO scenarios. Further, a unified design scheme for different scenarios (such as other non-MIMO scenarios, including but not limited to Vehicle to Everything (V2X), capacity enhancement systems, near distance communication systems, NTN (Non Terrestrial Network), IoT (Internet of Things), URLLC (Ultra Reliable Low Latency Communication) networks, etc.) can also help to reduce hardware complexity and cost. In the case of no conflict, the embodiments in any node of the present application and the features in the embodiments can be applied to any other node. In the case of no conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0007] In particular, the explanation of the terminology, nouns, functions, and variables in the present application (if not specifically stated) can refer to the definitions in TS38 series and TS37 series in the technical standards (Technical Specification, TS) of 3GPP (the 3rd Generation Partnership Project). If necessary, TS38.211, TS38.212, TS38.213, TS38.214, TS38.215, TS38.300, TS38.304, TS38.305, TS38.321, TS38.331, TS37.355, TS38.423 in the 3GPP technical standards can be referred to for the understanding of the present application.

[0008] As an embodiment, the explanation of the terminology in the present application is based on the definition of the specification agreement TS38 series of 3GPP.

[0009] As an embodiment, the explanation of the terminology in the present application is based on the definition of the specification agreement TS37 series of 3GPP.

[0010] As an embodiment, the explanation of the terminology in the present application is based on the definition of the specification agreement TS40 series of 3GPP.

[0011] As an embodiment, the interpretation of the terms in this application is referred to the definitions in the specification agreement TS 39 series of 3GPP.

[0012] As an embodiment, the interpretation of the terms in this application is referred to the definitions in the specification agreement Rel-17 version of 3GPP.

[0013] As an embodiment, the interpretation of the terms in this application is referred to the definitions in the specification agreement Rel-18 version of 3GPP.

[0014] As an embodiment, the interpretation of the terms in this application is referred to the definitions in the specification agreement Rel-19 version of 3GPP.

[0015] As an embodiment, the interpretation of the terms in this application is referred to the definitions in the specification agreement Rel-20 version of 3GPP.

[0016] The present application discloses a method for a first node in wireless communication beam management, comprising:

[0017] transmitting a first information block and a second information block, the first information block indicating the transmission of the second information block, and the second information block comprising reporting information of beam management;

[0018] wherein the transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the starting time of the first information block to the starting time of the second information block is a first time window; and the PUSCH time domain resource indicated by dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0019] As an embodiment, the problem to be solved by the present application includes the implementation of UE-initiated / event-driven beam measurement and reporting mechanism.

[0020] As an embodiment, the problem to be solved by the present application includes whether the first node transmits the measurement report of beam management on the PUSCH indicated by dynamic scheduling.

[0021] As an embodiment, the characteristics of the above method include that the first node receives uplink scheduling signaling of the base station after transmitting the uplink indication of PUCCH and before transmitting the measurement report of beam management, and the first node does not transmit the measurement report of beam management on the PUSCH indicated by the uplink scheduling signaling.

[0022] As an embodiment, the characteristics of the above method include that the first node is a terminal.

[0023] As an embodiment, the method has the feature that the beam management report occupies non-dynamically scheduled resources, data scheduled by the legacy system has a higher priority than wireless signals transmitted in the non-dynamically scheduled resources, and wireless signals transmitted in the non-dynamically scheduled resources are discarded. When uplink data scheduled by the dynamic scheduling and the beam management report overlap in the time domain, the first node transmits the beam management report.

[0024] As an embodiment, the method has the feature that the base station sends the dynamic scheduling signaling before decoding the first information block, and the base station does not know that the first node will transmit the beam management report in the preconfigured resources before making the scheduling decision and sending the scheduling.

[0025] As an embodiment, the method has the feature that the base station sends the dynamic scheduling signaling before decoding the first information block, and when uplink data scheduled by the dynamic scheduling signaling and the beam management report conflict, the first node gives up the transmission of the uplink data and ensures the transmission of the beam management report.

[0026] As an embodiment, the method has the feature that the base station decodes the first information block after determining to send the dynamic scheduling signaling, and when uplink data scheduled by the dynamic scheduling signaling and the beam management report conflict, the first node gives up the transmission of the uplink data and ensures the transmission of the beam management report.

[0027] As an embodiment, the method has the feature that the base station ensures that uplink data scheduled by the dynamic scheduling signaling and the beam management report do not conflict.

[0028] As an embodiment, the method has the feature that the first node considers that uplink data scheduled by the dynamic scheduling signaling and the beam management report do not conflict.

[0029] As an embodiment, the method has the benefit of supporting UE-initiated / event-driven beam measurement and reporting, reducing uplink reporting overhead and control signaling overhead, improving the efficiency and response speed of beam management, and thus improving the overall network performance.

[0030] As an embodiment, the method has the benefit of establishing a consensus between the base station and the terminal and ensuring the reliable transmission of the reported information.

[0031] As an embodiment, the method has the benefit of optimizing resource utilization.

[0032] According to an aspect of the present application, the method has the feature that the duration of the first time window in the time domain is not less than a first threshold, and the first threshold is fixed or configurable.

[0033] As an embodiment, the above method has the advantages of: configurable first threshold value helps the network to optimize network resources according to different deployment scenarios and UE capabilities, and reduce transmission delay.

[0034] As an embodiment, the above method has the advantages of: helping to improve the reliability of signaling transmission.

[0035] As an embodiment, the above method has the advantages of: ensuring that the base station has enough time to receive the first information block and confirm its content.

[0036] According to an aspect of the present application, the above method is characterized in that the first threshold value depends on at least one of:

[0037] The packet assembly capability of the uplink data channel of the first node;

[0038] The decoding capability of the uplink reception of the receiver of the first information block.

[0039] As an embodiment, the above method has the advantages of: the first threshold value is reported by the first node.

[0040] As an embodiment, the above method has the advantages of: the first threshold value is configured by the receiver of the first information block based on the UE capability reported by the first node.

[0041] As an embodiment, the above method has the advantages of: ensuring that the base station has enough time to receive the first information block and confirm its content, and ensuring transmission reliability.

[0042] As an embodiment, the above method has the advantages of: good compatibility.

[0043] According to an aspect of the present application, the above method is characterized in that the reporting information of the beam management includes CRI and RSRP.

[0044] As an embodiment, the above method has the advantages of: the reporting information of the beam management includes downlink reference signal indication and corresponding RSRP.

[0045] As an embodiment, the above method has the advantages of: the RSRP includes one of L1-RSRP, filter-based RSRP, and RSRP difference.

[0046] As an embodiment, the above method has the advantages of: helping the base station to learn the channel quality of each beam in time, selecting the best beam according to the latest channel information, and ensuring the optimization of communication quality.

[0047] As an embodiment, benefits of the above method include: enhanced flexibility of beam management.

[0048] According to an aspect of the present application, the above method is characterized in that the non-dynamically scheduled resources include configured grant resources, or the non-dynamically scheduled resources include pre-configured resources.

[0049] As an embodiment, the above method includes: the pre-configured resources include PUCCH resources.

[0050] As an embodiment, benefits of the above method include: pre-configured resources can be optimized in the network planning phase, reducing resource conflicts between different UEs, thereby improving the overall system performance.

[0051] As an embodiment, benefits of the above method include: reducing dynamic control signaling overhead.

[0052] As an embodiment, benefits of the above method include: reusing existing configured grant resources has good compatibility.

[0053] According to an aspect of the present application, the above method is characterized in that the reporting information of the beam management is predicted, and the first threshold value depends on the ID associated with the reporting information of the beam management for prediction.

[0054] As an embodiment, the above method includes: the ID is Identify.

[0055] As an embodiment, the above method includes: the ID is Identification.

[0056] As an embodiment, the above method includes: the ID is Identity.

[0057] As an embodiment, the above method includes: the ID is Identifier.

[0058] As an embodiment, the above method includes: the ID is identity.

[0059] As an embodiment, the above method includes: the ID is identification.

[0060] As an embodiment, the above method includes: the ID includes an AI / ML model ID.

[0061] As an embodiment, the above method includes: the ID includes an AI / ML function ID.

[0062] As an embodiment, the method has the feature that the ID comprises an AI / ML entity.

[0063] As an embodiment, the method has the benefit of supporting the fusion of AI and communications, improving the adaptability and intelligence level of the communication system, and thus improving the performance, efficiency, and user experience of the communication system.

[0064] As an embodiment, the method has the benefit of introducing different AI / ML models to optimize the reporting speed and accuracy of the beam management report.

[0065] As an embodiment, the method has the benefit of reducing the probability of RLF occurrence.

[0066] According to an aspect of the present application, the method has the feature that it comprises:

[0067] receiving a first reference signal;

[0068] wherein the reporting information of the beam management depends on channel measurement for the first reference signal, and the interval between the time domain resources occupied by the first reference signal and the time domain resources occupied by the first information block is not less than a second threshold, the second threshold being fixed or configurable.

[0069] As an embodiment, the method has the feature that the first reference signal occupies one or more CSI-RS resources.

[0070] As an embodiment, the method has the feature that the first reference signal occupies one or more SSBs.

[0071] As an embodiment, the method has the feature that for the existing UE initial / event-triggered beam management report, the definition of the reference signal referred to by the existing reporting is changed from the time of reporting CSI to calculate the reference signal to the time of determining the reporting of beam management information, in order to optimize the performance.

[0072] As an embodiment, the method has the benefit of ensuring the accuracy of measurement and calculation, and reducing measurement error.

[0073] As an embodiment, the method has the benefit of enhancing system robustness.

[0074] According to an aspect of the present application, the method has the feature that the reporting information of the beam management is predicted, and the second threshold depends on the ID associated with the reporting information of the beam management for prediction.

[0075] As one embodiment, the method has the feature that the ID is Identify.

[0076] As one embodiment, the method has the feature that the ID is Identification.

[0077] As one embodiment, the method has the feature that the ID is Identity.

[0078] As one embodiment, the method has the feature that the ID is Identifier.

[0079] As one embodiment, the method has the feature that the ID is identity.

[0080] As one embodiment, the method has the feature that the ID is identification.

[0081] As one embodiment, the method has the feature that the ID includes an AI / ML model ID.

[0082] As one embodiment, the method has the feature that the ID includes an AI / ML function ID.

[0083] As one embodiment, the method has the feature that the ID includes an AI / ML entity.

[0084] As one embodiment, the method has the benefit of supporting the fusion of AI and communication, improving the adaptability and intelligence level of the communication system, and thus improving the performance, efficiency and user experience of the communication system.

[0085] As one embodiment, the method has the benefit of introducing different AI / ML models to optimize the reporting speed and accuracy of beam management reports.

[0086] As one embodiment, the method has the benefit of reducing the probability of RLF occurrence.

[0087] According to one aspect of the present application, the method has the feature that the second information block occupies a given time domain resource block in K1 time domain resource blocks included in the first time domain resource set; K1 is a positive integer greater than 1; the given time domain resource block is the earliest one of the K1 time domain resource blocks after the time domain resource occupied by the first information block delays a first time offset value; the first time offset value is fixed, or the first time offset value is configurable.

[0088] As one embodiment, the method has the feature that the first time domain resource set is pre-configured.

[0089] As one embodiment, the method has the feature that the first node completes packetization of the uplink data channel within the first time offset value.

[0090] As one embodiment, the method has the feature that the receiver of the first information block completes decoding of the uplink reception within the first time offset value.

[0091] As one embodiment, the method has the benefit of reducing requirements on terminals and reducing deployment costs.

[0092] As one embodiment, the method has the benefit of reducing signaling overhead while establishing consensus between the base station and the terminal.

[0093] As one embodiment, the method has the benefit of ensuring that the entire beam reporting process is completed in the shortest possible time.

[0094] According to one aspect of the present application, the method has the feature that the first node is a user equipment.

[0095] According to one aspect of the present application, the method has the feature that the first node is a terminal.

[0096] The present application discloses a method in a second node for wireless communication beam management, comprising:

[0097] receiving a first information block and a second information block, the first information block indicating reception of the second information block, the second information block comprising reporting information for beam management;

[0098] wherein the sending of the first information block is event-triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the starting time of the first information block to the starting time of the second information block is a first time window; the sender of the first information block receives dynamically scheduled PUSCH time domain resources in the first time window, and the time domain resources occupied by the second information block are orthogonal.

[0099] As one embodiment, the method has the feature that the second node is a base station.

[0100] As one embodiment, the method has the feature that the second node is an eNB.

[0101] As one embodiment, the method has the feature that the second node is a gNB.

[0102] According to an aspect of the present application, the method is characterized in that a time duration of the first time window in time domain is not less than a first threshold, the first threshold is fixed, or the first threshold is configurable.

[0103] According to an aspect of the present application, the method is characterized in that the first threshold depends on at least one of the following:

[0104] a packet assembling capability of an uplink data channel of a transmitter of the first information block;

[0105] a decoding capability of uplink reception of the second node.

[0106] According to an aspect of the present application, the method is characterized in that the reporting information of the beam management comprises CRI and RSRP.

[0107] According to an aspect of the present application, the method is characterized in that the non-dynamic scheduling resource comprises a configuration granted resource, or the non-dynamic scheduling resource comprises a preconfigured resource.

[0108] According to an aspect of the present application, the method is characterized in that the reporting information of the beam management is predicted, and the first threshold depends on an ID associated with the reporting information of the beam management for prediction.

[0109] According to an aspect of the present application, the method is characterized in that it comprises:

[0110] transmitting a first reference signal;

[0111] wherein the transmitter of the first information block receives the first reference signal, the reporting information of the beam management depends on a channel measurement of the transmitter of the first information block on the first reference signal, and an interval between a time domain resource occupied by the first reference signal and a time domain resource occupied by the first information block is not less than a second threshold, the second threshold is fixed, or the second threshold is configurable.

[0112] According to an aspect of the present application, the method is characterized in that the reporting information of the beam management is predicted by the transmitter of the first information block, and the second threshold depends on an ID associated with the reporting information of the beam management for prediction.

[0113] According to an aspect of the present application, the method is characterized in that the second information block occupies a given time domain resource block in K1 time domain resource blocks included in the first time domain resource set; K1 is a positive integer greater than 1; the given time domain resource block is the earliest one in the K1 time domain resource blocks after the time domain resource occupied by the first information block delays a first time offset value; the first time offset value is fixed, or the first time offset value is configurable.

[0114] According to an aspect of the present application, the method is characterized in that the second node is a base station.

[0115] The present application discloses a device for a first node in wireless communication beam management, comprising:

[0116] The first transmitter transmits a first information block and a second information block, the first information block indicates transmission of the second information block, and the second information block includes reported information of beam management.

[0117] The transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the first time window is from the starting time of the first information block to the starting time of the second information block; and the PUSCH time domain resource indicated by dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0118] The present application discloses a device for a second node in wireless communication beam management, comprising:

[0119] The second receiver receives a first information block and a second information block, the first information block indicates reception of the second information block, and the second information block includes reported information of beam management.

[0120] The transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the first time window is from the starting time of the first information block to the starting time of the second information block; and the PUSCH time domain resource indicated by dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0121] As an embodiment, compared with the conventional scheme, the present application has the following advantages, but is not limited to:

[0122] The application supports UE-initiated / event-driven beam measurement and reporting, reduces uplink reporting overhead and control signaling overhead, improves the efficiency and response speed of beam management, and thus improves the overall network performance.

[0123] Establishes consensus between the base station and the terminal to ensure reliable transmission of reported information.

[0124] Supports the integration of AI and communication, improves the adaptability and intelligence level of the communication system, and thus improves the performance, efficiency and user experience of the communication system. BRIEF DESCRIPTION OF DRAWINGS

[0125] Other features, objects and advantages of the application will become more apparent after reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0126] Figure 1 shows a flowchart of transmission by a first node according to one embodiment of the application;

[0127] Figure 2 shows a schematic diagram of a network architecture according to one embodiment of the application;

[0128] Figure 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to one embodiment of the application;

[0129] Figure 4 shows a schematic diagram of a first communication device and a second communication device according to one embodiment of the application;

[0130] Figure 5 shows a flowchart of transmission between a first node and a second node according to one embodiment of the application;

[0131] Figure 6 shows a schematic diagram of a first time window and a first threshold relationship according to one embodiment of the application;

[0132] Figure 7 shows a schematic diagram of a first set of time domain resources and a first time offset value according to one embodiment of the application;

[0133] Figure 8 shows a schematic diagram of a relationship between a first reference signal, a first information block and a second information block according to one embodiment of the application;

[0134] Figure 9 shows a schematic diagram of a first threshold according to one embodiment of the application;

[0135] Figure 10 shows a schematic diagram of a second threshold according to one embodiment of the application;

[0136] Figure 11 shows a schematic diagram of RAN domain AI / ML function deployment according to one embodiment of the application;

[0137] FIG. 12 shows a schematic diagram of AI / ML function deployment of a UE according to an embodiment of the present application;

[0138] FIG. 13 shows a schematic diagram of an artificial intelligence or machine learning based processing system according to an embodiment of the present application;

[0139] FIG. 14 shows a schematic diagram of artificial intelligence or machine learning according to an embodiment of the present application;

[0140] FIG. 15 shows a structural block diagram of a processing apparatus for use in a first node according to an embodiment of the present application;

[0141] FIG. 16 shows a structural block diagram of a processing apparatus for use in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0142] The technical solutions of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily without conflict. Based on performance, flexibility, complexity, overhead and compatibility, etc., the person skilled in the art has the motivation to flexibly combine the embodiments in different drawings without conflict, including but not limited to the embodiments in FIG. 1 and the embodiments in FIGS. 5-16, the embodiments in FIG. 5 and the embodiments in FIGS. 6-16, etc.

[0143] Embodiment 1

[0144] Embodiment 1 illustrates a flowchart of a first node transmission according to an embodiment of the present application, as shown in FIG. 1. In FIG. 1, each block represents a step. In particular, the order of the steps in the blocks does not represent a specific time sequence between the steps.

[0145] The first node transmits a first information block and a second information block in step 101, the first information block indicating transmission of the second information block, and the second information block including reporting information of beam management.

[0146] In embodiment 1, the transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the starting time of the first information block to the starting time of the second information block is a first time window; and the PUSCH time domain resource indicated by dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0147] As an embodiment, the first node is a UE (User Equipment).

[0148] As one embodiment, the first node is a terminal.

[0149] As one embodiment, the PUCCH refers to Physical Uplink Control CHannel.

[0150] As one embodiment, the PUSCH refers to Physical Uplink Shared CHannel.

[0151] As one embodiment, the first node is the first node in the present application.

[0152] As one embodiment, the first node transmits the first information block.

[0153] As one embodiment, the first information block carries one-bit indication information.

[0154] As one embodiment, the first information block includes UCI (Uplink Control Information).

[0155] As one embodiment, the first information block includes SR (Scheduling Request).

[0156] As one embodiment, the first information block includes BRI (Beam Report Indicator).

[0157] As one embodiment, the first information block includes UCI, which is different from the type of UCI in Rel-18 (Release-18) and previous versions.

[0158] As one sub-embodiment of this embodiment, the type of UCI in Rel-18 and previous versions includes at least SR, HARQ (Hybrid Automatic Repeat reQuest) -ACK

[0159] (ACKnowledgment, confirmation) and CSI (Channel State Information).

[0160] As one embodiment, the first information block indicates the transmission of the second information block.

[0161] As one embodiment, the first information block is used to notify (inform or indicate) the transmission of the second information block.

[0162] As one embodiment, one bit indication information carried by the first information block is used to notify the transmission of the second information block.

[0163] As one embodiment, the first information block indicates that the first node transmits the second information block.

[0164] As one embodiment, the first information block indicates that the first node will transmit the second information block later.

[0165] As one embodiment, the first node transmits the second information block.

[0166] As one embodiment, the first information block is located before the second information block in time domain.

[0167] As one embodiment, the second information block is located after the first information block in time domain.

[0168] As one embodiment, the second information block is carried by dynamic signaling.

[0169] As one embodiment, the second information block is carried by MAC (Medium Access Control) layer signaling.

[0170] As one embodiment, the second information block includes MAC CE (Control Element).

[0171] As one embodiment, the second information block is carried by physical layer signaling.

[0172] As one embodiment, the second information block includes UCI.

[0173] As one embodiment, the second information block includes the reporting information of the beam management.

[0174] As one embodiment, the second information block carries the reporting information of the beam management.

[0175] As one embodiment, the second information block includes beam report.

[0176] As one embodiment, the second information block includes N reporting beams, and the N is a positive integer.

[0177] As one sub-embodiment of this embodiment, the N is configured.

[0178] As one sub-embodiment of this embodiment, the N beams all satisfy the condition of Event-2.

[0179] As one sub-example of this embodiment, the N reported beams respectively correspond to N CSI-RS (Channel State Information Reference Signal) resources.

[0180] As one sub-example of this embodiment, the N reported beams respectively correspond to N

[0181] NZP-CSI-RS-ResourceId.

[0182] As one sub-example of this embodiment, the N reported beams respectively correspond to N CRI (CSI-RS Resource Indicator).

[0183] As one sub-example of this embodiment, the N reported beams respectively correspond to N SSB.

[0184] As one sub-example of this embodiment, the N reported beams respectively correspond to N ssb-Index.

[0185] As one sub-example of this embodiment, the N reported beams respectively correspond to N SSBRI (SS / PBCH Block Resource indicator).

[0186] As one sub-example of this embodiment, the N reported beams respectively correspond to N TCI (Transmission Configuration Indicator).

[0187] As one sub-example of this embodiment, the N reported beams respectively correspond to N TCI State.

[0188] As one sub-example of this embodiment, the N reported beams respectively correspond to N TCI-StateId.

[0189] As one sub-example of this embodiment, the N reported beams respectively correspond to N RSRP (Reference Signal Received Power).

[0190] As an embodiment, the TCI state described in the present application includes parameters of QCL relationship between DMRS ports of one or two reference signals and PDSCH (Physical Downlink Shared CHannel), DMRS ports of PDCCH (Physical Downlink Control Channel) or CSI-RS ports of CSI-RS resource.

[0191] As an embodiment, the SSB described in the present application refers to: Synchronization Signal Block.

[0192] As an embodiment, the SSB described in the present application refers to: SS (Synchronization Signal) / PBCH (Physical Broadcast CHannel) block.

[0193] Typically, the receiving occasions of PBCH, PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal) are in consecutive symbols, and form the SS / PBCH block.

[0194] As an embodiment, the reporting information of the beam management includes downlink reference signal indication and RSRP.

[0195] As an embodiment, the reporting information of the beam management includes CRI and RSRP.

[0196] As an embodiment, the reporting information of the beam management includes SSBRI and RSRP.

[0197] As an embodiment, the reporting information of the beam management includes N CRIs and corresponding N RSRPs, and the N is a positive integer.

[0198] As an embodiment, the reporting information of the beam management includes N SSBRIs and corresponding N RSRPs, and the N is a positive integer.

[0199] As an embodiment, the RSRP comprised in the reporting information for the beam management in the present application comprises L1-RSRP.

[0200] As an embodiment, the RSRP comprised in the reporting information for the beam management in the present application is layer 1 filtered RSRP.

[0201] As an embodiment, the RSRP comprised in the reporting information for the beam management in the present application is the differential value between the RSRP of the current beam and the RSRP of the new beam.

[0202] As an embodiment, the RSRP comprised in the reporting information for the beam management in the present application is the differential value between the RSRP of the new beam and the RSRP of the current beam.

[0203] As an embodiment, the transmission of the first information block is event triggered.

[0204] As an embodiment, the event triggering the transmission of the first information block is Event-2.

[0205] As a sub-embodiment of this embodiment, the Event-2 means that the quality of at least one new beam becomes better than the quality of the current beam by a given threshold.

[0206] As a sub-embodiment of this embodiment, the first node triggers the transmission of the first information block when the number of Event-2 instances of at least one same new beam within a given time window is greater than or equal to M, the M being configurable.

[0207] As an embodiment, the first node triggers the transmission of the first information block when the condition that the quality of at least one same new beam becomes better than the quality of the current beam by a given threshold is satisfied at least M times, the M being configurable.

[0208] As an embodiment, the metric of the quality of the beam in the present application comprises at least the L1-RSRP.

[0209] As an embodiment, the new beam in the present application means the beam corresponding to the reference signal in the set of reference signals associated to the beam reporting configuration information.

[0210] As an embodiment, the new beam in the present application means the beam corresponding to the reference signal in the set of reference signals for beam reporting configured by the higher layer parameter.

[0211] As an embodiment, the new beam in the present application refers to a subset of beams corresponding to reference signals in a set of reference signals configured by higher layer parameters for beam reporting.

[0212] As an embodiment, the current beam in the present application refers to a beam corresponding to an indicated TCI state.

[0213] As an embodiment, the current beam in the present application refers to a beam corresponding to a reference signal QCLed with an indicated TCI state.

[0214] As an embodiment, the current beam in the present application refers to an SSB QCLed with a beam corresponding to an indicated TCI state.

[0215] As an embodiment, the current beam in the present application refers to a beam corresponding to a reference signal configured by higher layer signaling parameters for beam reporting.

[0216] As an embodiment, the current beam in the present application refers to a beam corresponding to a reference signal indicated by a MAC CE.

[0217] As a sub-embodiment of the embodiment, the subset of beams is activated or indicated by a MAC CE.

[0218] As a sub-embodiment of the embodiment, the subset of beams is indicated or activated by an indicated TCI state.

[0219] As an embodiment, the QCL in the present application refers to Quasi Co-Location.

[0220] As an embodiment, the QCL in the present application refers to Quasi Co-Located.

[0221] As an embodiment, the QCL type in the present application includes typeA, typeB, typeC and typeD.

[0222] As an embodiment, the QCL parameters of the QCL Type A described in the present application include Doppler shift, Doppler spread, average delay, and delay spread; the QCL parameters of the QCL Type B include Doppler shift and Doppler spread; the QCL parameters of the QCL Type C include Doppler shift and average delay; and the QCL parameters of the QCL Type D include spatial Rx parameter.

[0223] As an embodiment, the specific definitions of the type A, the type B, the type C, and the type D described in the present application refer to the clause 5.1.5 of the 3GPP TS (Technical Specification) 38.214.

[0224] As an embodiment, the first information block is transmitted on the PUCCH.

[0225] As an embodiment, the physical layer channel occupied by the first information block includes the PUCCH.

[0226] As an embodiment, the physical layer channel occupied by the first information block is the PUCCH.

[0227] As an embodiment, the first information block occupies the PUCCH resource.

[0228] As an embodiment, the PUCCH resource occupied by the first information block is the periodic PUCCH resource.

[0229] As an embodiment, the PUCCH resource occupied by the first information block is configured through the dedicated RRC (Radio Resource Control) signaling.

[0230] As an embodiment, the PUCCH format adopted by the first information block is the PUCCH format 0 or the PUCCH format 1.

[0231] As an embodiment, the resource occupied by the second information block is not dynamically scheduled.

[0232] As one embodiment, the non-dynamically scheduled resources comprise transmission without dynamic grant resources.

[0233] As one embodiment, the transmission without dynamic grant resources are configured by higher layer signaling.

[0234] As one embodiment, the transmission without dynamic grant resources are configured by RRC signaling.

[0235] As one embodiment, the non-dynamically scheduled resources comprise Configured Grant (CG) resources.

[0236] As one embodiment, the non-dynamically scheduled resources comprise Configured Grant (CG) resources.

[0237] As one embodiment, the Configured Grant resources are configured by higher layer signaling.

[0238] As one embodiment, the Configured Grant resources are configured by RRC signaling.

[0239] As one embodiment, the Configured Grant resources comprise Configured Grant Type 1 resources.

[0240] As one embodiment, the Configured Grant resources comprise Configured Grant Type 2 resources.

[0241] As one embodiment, the Configured Grant resources comprise Configured Grant Type 3 resources.

[0242] As one sub-embodiment of this embodiment, the Configured Grant Type 3 resources are configured by RRC signaling and activated by the first information block.

[0243] As one sub-embodiment of this embodiment, the Configured Grant Type 3 resources are configured by RRC signaling and implicitly indicated to be activated by the first information block.

[0244] As one sub-embodiment of this embodiment, the Configured Grant Type 3 resources are configured by RRC signaling and are on-demand transmissions.

[0245] As one embodiment, the non-dynamically scheduled resources comprise preconfigured resources.

[0246] As one embodiment, the preconfigured resources are configured by higher layer signaling.

[0247] As an embodiment, the preconfigured resource is configured by RRC signaling.

[0248] As an embodiment, the preconfigured resource is cell-common.

[0249] As an embodiment, the preconfigured resource is UE-specific.

[0250] As an embodiment, the preconfigured resource comprises PUCCH resource.

[0251] As an embodiment, the preconfigured resource comprises cell-common PUCCH resource.

[0252] As an embodiment, the preconfigured resource comprises PUSCH resource.

[0253] As an embodiment, the preconfigured resource is only used for transmission of the reporting information of the beam management.

[0254] As an embodiment, a starting time of the first information block to a starting time of the second information block is a first time window.

[0255] As an embodiment, the starting time of the first information block refers to a corresponding time slot index of a time slot occupied by a PUCCH occupied by the first information block.

[0256] As an embodiment, the starting time of the first information block refers to a starting time of a first multi-carrier symbol occupied by a PUCCH occupied by the first information block.

[0257] As an embodiment, the starting time of the first information block refers to a corresponding symbol index of a first multi-carrier symbol occupied by a PUCCH occupied by the first information block.

[0258] As an embodiment, the starting time of the second information block refers to a corresponding time slot index of a time slot occupied by a physical layer channel occupied by the second information block.

[0259] As an embodiment, the starting time of the second information block refers to a starting time of a first multi-carrier symbol occupied by a physical layer channel occupied by the second information block.

[0260] As an embodiment, the starting time of the second information block refers to a corresponding symbol index of a first multi-carrier symbol occupied by a physical layer channel occupied by the second information block.

[0261] As an embodiment, the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window are orthogonal to the time domain resources occupied by the second information block.

[0262] As an embodiment, the dynamic scheduling received by the first node in the first time window comprises UL Grant (Uplink Grant).

[0263] As an embodiment, the dynamic scheduling received by the first node in the first time window comprises PDCCH (Physical Downlink Control CHannel).

[0264] As an embodiment, the dynamic scheduling received by the first node in the first time window comprises DCI (Downlink Uplink Control).

[0265] As an embodiment, the dynamic scheduling received by the first node in the first time window comprises DCI, and the format of the DCI is one of DCI format 0_0, DCI format 0_1, DCI format 0_1 and DCI format 0_3.

[0266] As an embodiment, the time domain resources occupied by the second information block refer to the time domain resources occupied by the physical layer channel occupied by the second information block.

[0267] As an embodiment, the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window are orthogonal to the time domain resources occupied by the second information block, which means that the second information block does not occupy the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0268] As an embodiment, the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window are orthogonal to the time domain resources occupied by the second information block, which means that the time domain resources occupied by the second information block do not belong to the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0269] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node does not send the reporting information of the beam management on the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0270] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node assumes that there is no overlap between the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window and the time domain resources occupied by the second information block.

[0271] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node is not assumed to receive the overlap between the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window and the time domain resources occupied by the second information block.

[0272] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node considers that there is no overlap between the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window and the time domain resources occupied by the second information block.

[0273] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node is not considered to receive the overlap between the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window and the time domain resources occupied by the second information block.

[0274] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the first node is not expected to receive the overlap between the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window and the time domain resources occupied by the second information block.

[0275] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that the PUSCH time domain resources indicated by the dynamic scheduling and the time domain resources occupied by the second information block do not overlap.

[0276] As an embodiment, the meaning that the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window is orthogonal to the time domain resources occupied by the second information block includes that there is no time domain resource unit belonging to the PUSCH time domain resources indicated by the dynamic scheduling and the time domain resources occupied by the second information block at the same time.

[0277] As a sub-embodiment of the embodiment, the time domain resource unit is a time slot.

[0278] As a sub-embodiment of the embodiment, the time domain resource unit is a multi-carrier symbol.

[0279] As a sub-embodiment of the embodiment, the time domain resource unit is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0280] As an embodiment, the time domain resource in the present application includes one or more time domain resource units.

[0281] As an embodiment, the time domain resource in the present application includes one or more time slots.

[0282] As an embodiment, the time domain resource in the present application includes one or more OFDM symbols.

[0283] As an embodiment, the time domain resource in the present application includes one or more multi-carrier symbols.

[0284] As an embodiment, the time domain symbol in the present application includes DFT-s-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing).

[0285] As an embodiment, the multi-carrier symbol in the present application includes an OFDM symbol.

[0286] As an embodiment, the multi-carrier symbol in the present application includes an enhanced OFDM symbol.

[0287] As an embodiment, the multicarrier symbol in the present application is an OFDM symbol including a CP (Cyclic Prefix).

[0288] As an embodiment, the multicarrier symbol in the present application includes one or more of an FBMC (Filter Bank Multi Carrier) symbol, a UFMC (Universal Filtered Multi Carrier) symbol, an F-OFDM (Filtered-OFDM) symbol, an OCDM-OFDM (Orthogonal Chirp Division Multiplexing-OFDM) symbol.

[0289] Embodiment 2

[0290] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG. 2.

[0291] FIG. 2 illustrates a network architecture 200. The network architecture 200 is a network architecture for LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), 5G systems, 5G-Advanced, and future 6G systems. The network architecture for LTE, LTE-A, 5G systems, 5G-Advanced, and future 6G systems is referred to as EPS (Evolved Packet System). The 5G NR or LTE network architecture can be referred to as 5GS (5G System) / EPS or some other suitable terminology; the 6G network architecture can be referred to as 6GS (6G System) / EPS or some other suitable terminology. The network architecture 200 can include one or more UEs 201, a RAN (Next Generation Radio Access Network) 202, a core network 210, a HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The network architecture 200 can be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown in FIG. 2, the network architecture 200 provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application are amenable to use with networked systems providing circuit-switched services. The RAN 202 includes Node Bs 203 and other nodes 204. The Node Bs 203 provide user and control plane protocol terminations toward the UEs 201. The Node Bs 203 can be connected to the other nodes 204 via an Xn interface (e.g., backhaul). The Node Bs 203 can also be referred to as base stations, base transceiver stations, radio base stations, radio transceivers, transceiver functions, basic service sets (BSSs), extended service sets (ESSs), TRPs (Transmitter Receiver Points), or some other suitable terminology. The Node Bs 203 provide access points to the core network 210 for the UEs 201; the core network 210 is a 5GC (5G Core Network) / EPC (Evolved Packet Core), or alternatively, the core network 210 is a 6GC.Examples of a UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, a flying vehicle, a narrowband physical web device, a machine type communication device, a land transport vehicle, a car, a wearable device, or any other similar functional device. Those skilled in the art will also The node 203 is connected by an SI / NG interface to the core network 210. The core network 210 includes a MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, a S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that processes the signaling between the UE 201 and the 5G-CN / EPC 210. The MME / AMF / SMF 211 generally provides bearer and connection management. All user Internet Protocol (IP) packets are transferred through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation as well as other functions. The P-GW / UPF 213 is connected to the Internet services 230. The Internet services 230 include operator- correspondent Internet Protocol services, which can specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched services.

[0292] As one embodiment, the first node described in this application includes the UE 201.

[0293] As one embodiment, the second node described in the present application comprises the node 203.

[0294] As one embodiment, the node 203 is a macro cell base station.

[0295] As one embodiment, the node 203 is a micro cell base station.

[0296] As one embodiment, the node 203 is a pico cell base station.

[0297] As one embodiment, the node 203 is a femto cell.

[0298] As one embodiment, the node 203 is a base station device supporting large latency difference.

[0299] As one embodiment, the node 203 is a flying platform device.

[0300] As one embodiment, the node 203 is a satellite device.

[0301] As one embodiment, the node 203 is a test device (e.g. a transceiver simulating part of the functions of a base station, a signaling tester).

[0302] As one embodiment, the UE 201 comprises a mobile phone.

[0303] As one embodiment, the UE 201 comprises a vehicle, including a car.

[0304] As one embodiment, the wireless link from the UE 201 to the node 203 is an uplink, which is used to perform uplink transmission.

[0305] As one embodiment, the wireless link from the node 203 to the UE 201 is a downlink, which is used to perform downlink transmission.

[0306] As one embodiment, the wireless link between the node 203 and the UE 201 comprises a cellular network link.

[0307] As one embodiment, the node 203 and the UE 201 are connected through a Uu air interface.

[0308] As one embodiment, the sender of the first information block described in the present application comprises the UE 201.

[0309] As one embodiment, the sender of the first information block in the present application comprises the UE 201.

[0310] As one embodiment, the sender of the second information block in the present application comprises the UE 201.

[0311] As one embodiment, the receiver of the second information block in the present application comprises the node 203.

[0312] As one embodiment, the sender of the first reference signal in the present application comprises the node 203.

[0313] As one embodiment, the receiver of the first reference signal in the present application comprises the UE 201.

[0314] As one embodiment, the UE 201 supports UE-initiated / Event-driven beam measurement.

[0315] As one embodiment, the node 203 supports UE-initiated / Event-driven beam measurement.

[0316] As one embodiment, the UE 201 supports Unified TCI framework.

[0317] As one embodiment, the node 203 supports Unified TCI framework.

[0318] As one embodiment, the UE 201 supports 5G system.

[0319] As one embodiment, the node 203 supports 5G system.

[0320] As one embodiment, the UE 201 supports at least 6G system.

[0321] As one embodiment, the node 203 supports at least 6G system.

[0322] Embodiment 3

[0323] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for user plane and control plane, according to one embodiment of the present application, as shown in FIG. 3.

[0324] Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3 shows the radio protocol architecture for the control plane 300 between a first communication node device (UE or RSU (Road Side Unit) in V2X (Vehicle to Everything), a vehicle mounted device or a vehicle mounted communication module) and a second node device (gNB, UE or RSU in V2X, a vehicle mounted device or a vehicle mounted communication module), or between two UEs, using three layers: Layer 1 (L1), Layer 2 (L2) and Layer 3 (L3). L1 is the lowest layer and implements various PHY (PHYsical layer) signal processing functions. L1 will be referred to as the PHY 301 herein. Layer 2 305 is above the PHY 301 and is responsible for the link between the first node device and the second node device, or between two UEs, through the PHY 301. Layer 2 305 includes a MAC (Medium Access Control) sublayer 302, a RLC (Radio Link Control) sublayer 303 and a PDCP (Packet Data Convergence Protocol) sublayer 304, which are terminated at the second node device. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security, by encrypting data packets, and handover support for the first communication node device between second communication node devices. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat reQuest). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating the various radio resources (e.g., resource blocks) in one cell among the UEs. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second communication node device and the first communication node device.The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2), which are substantially the same as the corresponding layers and sublayers in the control plane 300 for the first communication node device and the second communication node device, for the physical layer 351, the PDCP sublayer 354 in L2 355, the RLC sublayer 353 in L2 355, and the MAC sublayer 352 in L2 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. Also included in L2 355 in the user plane 350 is the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS (Quality of Service) flows and data radio bearers (DRBs) to support diverse traffic types. Although not illustrated, the first communication node device can have several upper layers above L2 355, including a network layer (e.g., IP (Internet Protocol) layer) that terminates at the P-GW on the network side and an application layer that terminates at the other end of the connection (e.g., a remote UE, a server, etc.).

[0325] As one embodiment, the radio protocol architecture in FIG. 3 is applicable to the first node in the present application.

[0326] As one embodiment, the radio protocol architecture in FIG. 3 is applicable to the second node in the present application.

[0327] As one embodiment, the first information block is generated at the PHY 301 or the PHY 351.

[0328] As one embodiment, the second information block is generated at the MAC 302 or the MAC 352.

[0329] As one embodiment, the second information block is generated at the PHY 301 or the PHY 351.

[0330] As one embodiment, the higher layer in the present application refers to a layer above the physical layer.

[0331] As one embodiment, the higher layer in the present application includes the RRC layer.

[0332] As one embodiment, the higher layer signaling in the present application includes the RRC IE.

[0333] As one embodiment, the higher layer signaling in the present application includes the RRC message.

[0334] As one embodiment, the higher layer described in the present application comprises a MAC layer.

[0335] As one embodiment, the higher layer signaling described in the present application comprises a MAC CE.

[0336] Embodiment 4

[0337] Embodiment 4 illustrates a schematic diagram of a first communication device and a second communication device according to one embodiment of the present application, as shown in FIG. 4. FIG. 4 is a block diagram of a first communication device 410 and a second communication device 450 communicating with each other in an access network.

[0338] The first communication device 410 comprises a controller / processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418 and an antenna 420.

[0339] The second communication device 450 comprises a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0340] In transmissions from the first communication device 410 to the second communication device 450, at the first communication device 410, upper layer packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements functionality of L2. In DL, the controller / processor 475 provides header compression, ciphering, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocations for second communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the second communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for Ll (i.e., physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 450 and mapping onto signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-ary phase shift keying (M-PSK), M-ary quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial pre-coding of the coded and modulated symbols, including codebook-based and non-codebook-based pre-coding and beamforming processing, to generate one or more parallel streams. The transmit processor 416 then maps to each of the parallel streams to subcarriers, multiplexes the modulated symbols in time domain and / or frequency domain with reference signals (e.g., pilot) and then performs an inverse fast Fourier transform (IFFT) to generate time domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs transmit analog pre-coding / beamforming operations on the time domain multicarrier symbol streams. Each transmitter 418 converts the baseband multicarrier symbol streams provided by the multi-antenna transmit processor 471 into radio frequency signals that are transmitted via the corresponding antennas 420.

[0341] In transmission from the first communication device 410 to the second communication device 450, at the second communication device 450, each receiver 454 receives a signal through its respective antenna 452. Each receiver 454 recovers information modulated onto an RF carrier and converts the RF stream into a baseband, multicarrier symbol stream to receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various signal processing functions of the LI. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operation on the baseband, multicarrier symbol stream from the receivers 454. The receive processor 456 converts the baseband, multicarrier symbol stream from the receive analog precoding / beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals are demultiplexed by the receive processor 456, where the reference signals will be used for channel estimation, and the data signals are recovered after multi-antenna detection in the multi-antenna receive processor 458 for any parallel streams destined to the second communication device 450. The symbols on each parallel stream are demodulated and recovered in the receive processor 456 and generate soft decisions. The receive processor 456 then decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the first communication device 410 on the physical channels. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2. The controller / processor 459 can be associated with a memory 460 that stores program codes and data. The memory 460 can be referred to as a computer-readable medium. In the DL, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2. Various control signals can also be provided to the L3 for L3 processing. The controller / processor 459 is also responsible for error detection using an ACK and / or negative ACK (NACK) protocol to support HARQ operations.

[0342] In the transmission from the second communication device 450 to the first communication device 410, at the second communication device 450, a data source 467 is used to provide upper layer packets to a controller / processor 459. The data source 467 represents all protocol layers above L2. Similar to the transmit function described at the first communication device 410 in the DL, the controller / processor 459 implements header compression, ciphering, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocations for the first communication device 410, implements L2 layer functionality for the user plane and control plane. The controller / processor 459 is also responsible for HARQ operations, retransmission of lost packets, and signaling to the first communication device 410. A transmit processor 468, in conjunction with a multi-antenna transmit processor 457, performs modulation mapping, channel coding processing, digital multi-antenna spatial pre-coding including codebook-based and non-codebook-based precoding, and beamforming processing, and then the transmit processor 468 generates parallel streams of symbols that are modulated onto different carriers, and the modulated symbol streams are then provided to different antennas 452 via transmitters 454 after analog pre-coding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 converts a baseband symbol stream into a radio frequency signal that is transmitted via the corresponding antenna 452.

[0343] In the transmission from the second communication device 450 to the first communication device 410, the functionality at the first communication device 410 is similar to the functionality described in connection with the reception at the second communication device 450 in the transmission from the first communication device 410 to the second communication device 450. Each receiver 418 receives a radio frequency signal through its respective antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 together implement L1 functionality. A controller / processor 475 implements L2 functionality. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer-readable medium. The controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the second communication device 450. Upper layer packets from the controller / processor 475 can be provided to a core network. The controller / processor 475 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0344] As one embodiment, the second communication device 450 comprises: at least one processor and at least one memory including a computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the second communication device 450 to perform at least the following: sending the first information block and the second information block, the first information block indicating the sending of the second information block, the second information block comprising the reporting information for beam management; the sending of the first information block is event triggered; the first information block is transmitted on PUCCH, the resource occupied by the second information block is non-dynamically scheduled; the first time window between the starting time of the first information block and the starting time of the second information block; the PUSCH time domain resource indicated by the dynamic scheduling received by the sender of the first information block in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0345] As one embodiment, the second communication device 450 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, causes the second communication device 450 to perform at least the following: sending the first information block and the second information block.

[0346] As one embodiment, the first communication device 410 comprises: at least one processor and at least one memory including a computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the first communication device 410 to perform at least the following: receiving the first information block and the second information block, the first information block indicating the receiving of the second information block, the second information block comprising the reporting information for beam management; the sending of the first information block is event triggered; the first information block is transmitted on PUCCH, the resource occupied by the second information block is non-dynamically scheduled; the first time window between the starting time of the first information block and the starting time of the second information block; the PUSCH time domain resource indicated by the dynamic scheduling received by the sender of the first information block in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0347] As one embodiment, the first communication device 410 comprises: a memory storing a computer readable program of instructions which, when executed by at least one processor, causes the first communication device 410 to perform at least the following: receiving the first information block and the second information block.

[0348] As one embodiment, the first node comprises the second communication device 450.

[0349] As an embodiment, the second node described in the present application comprises the first communication device 410.

[0350] As an embodiment, at least one of {the antenna 452, the transmitter 454, the transmission processor 468, the multi-antenna transmission processor 457, the controller / processor 459, the memory 460, the data source 467} is used to send the first information block described in the present application; at least one of {the antenna 420, the receiver 418, the reception processor 470, the multi-antenna reception processor 472, the controller / processor 475, the memory 476} is used to receive the first information block described in the present application.

[0351] As an embodiment, at least one of {the antenna 452, the transmitter 454, the transmission processor 468, the multi-antenna transmission processor 457, the controller / processor 459, the memory 460, the data source 467} is used to send the second information block described in the present application; at least one of {the antenna 420, the receiver 418, the reception processor 470, the multi-antenna reception processor 472, the controller / processor 475, the memory 476} is used to receive the second information block described in the present application.

[0352] As an embodiment, at least one of {the antenna 420, the transmitter 418, the transmission processor 416, the multi-antenna transmission processor 471, the controller / processor 475, the memory 476} is used to send the first reference signal described in the present application; at least one of {the antenna 452, the receiver 454, the reception processor 456, the multi-antenna reception processor 458, the controller / processor 459, the memory 460, the data source 467} is used to receive the first reference signal described in the present application.

[0353] Embodiment 5

[0354] Embodiment 5 illustrates a flowchart of the transmission between the first node and the second node according to an embodiment of the present application, as shown in FIG. 5. In FIG. 5, the first node U1 communicates with the second node N2 through a wireless link, and the steps in block F51 are optional. It is particularly pointed out that the order in this embodiment does not limit the order of signal transmission and implementation in the present application.

[0355] For the first node U1, the first reference signal is received in step S5110; the first information block is sent in step S510; and the second information block is sent in step S511.

[0356] For the second node N2, the first reference signal is transmitted in step S5210; the first information block is received in step S520; and the second information block is received in step S521.

[0357] In embodiment 5, the first information block indicates transmission of the second information block, the second information block comprising beam management reporting information; the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the first time window is from the starting time of the first information block to the starting time of the second information block; and the PUSCH time domain resource dynamically scheduled and received by the first node U1 in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0358] As an embodiment, the first node U1 is the first node in the present application.

[0359] As an embodiment, the second node N2 is the second node in the present application.

[0360] As an embodiment, the air interface between the second node N2 and the first node U1 comprises a wireless interface between a base station device and a user equipment.

[0361] As an embodiment, the air interface between the second node N2 and the first node U1 comprises a wireless interface between a relay node device and a user equipment.

[0362] As an embodiment, the air interface between the second node N2 and the first node U1 comprises a wireless interface between a user equipment and a user equipment.

[0363] As an embodiment, the second node N2 and the first node U1 communicate through a Uu interface.

[0364] As an embodiment, the second node N2 is a serving cell maintenance base station of the first node U1.

[0365] As an embodiment, the physical layer channel occupied by the second information block comprises a PUCCH.

[0366] As an embodiment, the physical layer channel occupied by the second information block comprises a PUSCH.

[0367] As an embodiment, the step S510 is before the step S511; and the step S520 is before the step S521.

[0368] As an embodiment, the block 51 in figure 5 is present; the method applied to the first node in the present application comprises: receiving a first reference signal; the reporting information of the beam management depends on the channel measurement for the first reference signal, the interval between the time domain resources occupied by the first reference signal and the time domain resources occupied by the first information block is not less than a second threshold, the second threshold is fixed, or the second threshold is configurable.

[0369] As an embodiment, the first reference signal occurs multiple times in time domain.

[0370] As an embodiment, the first reference signal occurs only once in time domain.

[0371] As an embodiment, the first reference signal is periodic in time domain.

[0372] As an embodiment, the reporting information of the beam management comprises the measurement result of the channel measurement for the first reference signal.

[0373] As an embodiment, the reporting information of the beam management comprises the prediction result of the channel measurement for the first reference signal.

[0374] As an embodiment, the reporting information of the beam management does not comprise the measurement result of the channel measurement for the first reference signal.

[0375] As an embodiment, whether the reporting information of the beam management comprises the measurement result of the channel measurement for the first reference signal depends on the configuration or indication of the second node N2.

[0376] As an embodiment, whether the first node U1 triggers the first information block depends on the channel measurement for the first reference signal.

[0377] As an embodiment, the first reference signal corresponds to the current beam in the present application.

[0378] As an embodiment, the first reference signal corresponds to the new beam in the present application.

[0379] As an embodiment, the first reference signal corresponds to one or more of the N reporting beams in the present application.

[0380] As an embodiment, the first reference signal comprises CSI-RS.

[0381] As an embodiment, the first reference signal is CSI-RS.

[0382] As an embodiment, the first reference signal occupies one or more CSI-RS resources.

[0383] As an embodiment, the first reference signal occupies one or more NZP (Non Zero Power) CSI-RS resources.

[0384] As an embodiment, the first reference signal comprises SSB.

[0385] As an embodiment, the first reference signal is SSB.

[0386] As an embodiment, the first reference signal occupies one or more resources corresponding to ssb-Index.

[0387] As an embodiment, the block 51 in FIG. 5 exists; the step S5110 is before the step S510; the step S5210 is before the step S520.

[0388] Embodiment 6

[0389] Embodiment 6 illustrates a diagram of a first time window and a first threshold value relationship according to an embodiment of the present application, as shown in FIG. 6. In FIG. 6, the horizontal axis represents time, the diamond cross-filled rectangle represents the time-domain resources occupied by the first information block in time, and the cross cross-filled rectangle represents the time-domain resources occupied by the second information block in time; the starting time of the first information block to the starting time of the second information block is the first time window, and the duration of the first time window in time domain is not less than the first threshold value.

[0390] In embodiment 6, the first threshold value is fixed, or the first threshold value is configurable.

[0391] As an embodiment, the duration of the first time window in time domain is not less than the first threshold value, and the first threshold value is fixed or configurable.

[0392] As an embodiment, the unit of the first threshold value is slot.

[0393] As an embodiment, the unit of the first threshold value is millisecond (ms).

[0394] As an embodiment, the unit of the first threshold value is microsecond (μs).

[0395] As an embodiment, the unit of the first threshold value is OFDM symbol.

[0396] As an embodiment, the unit of the first threshold is a multi-carrier symbol.

[0397] As an embodiment, the first threshold is a positive integer.

[0398] As an embodiment, the first threshold is a positive real number.

[0399] As an embodiment, the first threshold is fixed.

[0400] As an embodiment, the first threshold being fixed means that the first threshold is predefined.

[0401] As an embodiment, the first threshold being fixed means that the first threshold is default.

[0402] As an embodiment, the first threshold being fixed means that the first threshold is default.

[0403] As an embodiment, the first threshold being fixed means that the first threshold is reported by the first node.

[0404] As an embodiment, the first threshold being fixed means that the first threshold does not need to be indicated by a base station.

[0405] As an embodiment, the first threshold being fixed means that the first threshold does not need to be configured or updated by higher layer signaling.

[0406] As an embodiment, the first threshold being fixed means that the first threshold cannot be configured or updated by higher layer signaling.

[0407] As an embodiment, the first threshold is configurable.

[0408] As an embodiment, the first threshold being configurable means that the first threshold can be configured by higher layer signaling.

[0409] As an embodiment, the first threshold being configurable means that the first threshold can be configured by RRC signaling.

[0410] As an embodiment, the first threshold being configurable means that the first threshold is dependent on a higher layer parameter configuration.

[0411] As an embodiment, the first threshold is dependent on a Capability of the first node.

[0412] As an embodiment, the first threshold is dependent on a capability report of the first node.

[0413] As one embodiment, the first threshold depends on a UE capability information element (UE capability information element) of the first node.

[0414] As one embodiment, the first threshold depends on a Category of the first node.

[0415] As one embodiment, the first threshold depends on at least one of a packetization capability of an uplink data channel of the first node and a decoding capability of an uplink reception of a receiver of the first information block.

[0416] As one embodiment, the first threshold depends on a packetization capability of an uplink data channel of the first node.

[0417] As one sub-embodiment of this embodiment, the stronger the packetization capability of the uplink data channel of the first node, the smaller the first threshold; the weaker the packetization capability of the uplink data channel of the first node, the larger the first threshold.

[0418] As one sub-embodiment of this embodiment, the stronger the packetization capability of the uplink data channel of the first node corresponds to the faster the packetization speed of the uplink data channel of the first node; the weaker the packetization capability of the uplink data channel of the first node corresponds to the slower the packetization speed of the uplink data channel of the first node.

[0419] As one sub-embodiment of this embodiment, the first threshold is reported by the first node.

[0420] As one embodiment, the first threshold depends on a decoding capability of an uplink reception of a receiver of the first information block.

[0421] As one sub-embodiment of this embodiment, the stronger the decoding capability of the uplink reception of the receiver of the first information block, the smaller the first threshold; the weaker the decoding capability of the uplink reception of the receiver of the first information block, the larger the first threshold.

[0422] As one sub-embodiment of this embodiment, the stronger the decoding capability of the uplink reception of the receiver of the first information block corresponds to the faster the decoding speed of the uplink reception of the receiver of the first information block; the weaker the decoding capability of the uplink reception of the receiver of the first information block corresponds to the slower the decoding speed of the uplink reception of the receiver of the first information block.

[0423] As one sub-embodiment of this embodiment, the first threshold is configured by the higher layer signaling.

[0424] As an embodiment, the first threshold value depends on both a packetization capability of an uplink data channel of the first node and a decoding capability of uplink reception of the receiver of the first information block.

[0425] As a sub-embodiment of this embodiment, the first threshold value is configured by the receiver of the first information block, and the configuration is supported according to a capability indication of the first node.

[0426] Embodiment 7

[0427] Embodiment 7 illustrates a schematic diagram of a first time domain resource set and a first time offset value according to an embodiment of the present application, as shown in FIG. 7. In FIG. 7, the horizontal axis represents time, the diamond cross-filled rectangle represents time domain resources occupied by the first information block in time, the cross cross-filled rectangle represents time domain resources occupied by the second information block in time, and the rectangle with a thick line frame represents time domain resources occupied by one time domain resource block in the K1 time domain resource blocks included in the first time domain resource set in time; the time domain resources occupied by the second information block belong to a given time domain resource block in the first time domain resource set, and the given time domain resource block is the earliest one in the K1 time domain resource blocks after delaying the time domain resources occupied by the first information block by the first time offset value.

[0428] In embodiment 7, the K1 is a positive integer greater than 1, the first time offset value is fixed, or the first time offset value is configurable.

[0429] As an embodiment, the second information block occupies a given time domain resource block in the K1 time domain resource blocks included in the first time domain resource set; the K1 is a positive integer greater than 1; the given time domain resource block is the earliest one in the K1 time domain resource blocks after delaying the time domain resources occupied by the first information block by the first time offset value; and the first time offset value is fixed or the first time offset value is configurable.

[0430] As an embodiment, the first time domain resource set includes K1 time domain resource blocks.

[0431] As an embodiment, the K1 time domain resource blocks are periodic.

[0432] As an embodiment, the K1 time domain resource blocks are cell-common.

[0433] As an embodiment, the K1 time domain resource blocks are UE-specific.

[0434] As an embodiment, the K1 time domain resource blocks are pre-configured by the second node in the present application.

[0435] As one embodiment, the first time offset value is a positive integer.

[0436] As one embodiment, the first time offset value is a positive real number.

[0437] As one embodiment, the first time offset value is greater than the first threshold value.

[0438] As one embodiment, the first time offset value being fixed means that the first time offset value is predefined.

[0439] As one embodiment, the first time offset value being fixed means that the first time offset value is default.

[0440] As one embodiment, the first time offset value being fixed means that the first time offset value is default.

[0441] As one embodiment, the first time offset value being fixed means that the first time offset value is reported by the first node.

[0442] As one embodiment, the first time offset value being fixed means that the first time offset value does not need to be indicated by a base station.

[0443] As one embodiment, the first time offset value being fixed means that the first time offset value does not need to be configured or updated by higher layer signaling.

[0444] As one embodiment, the first time offset value being fixed means that the first time offset value cannot be configured or updated by higher layer signaling.

[0445] As one embodiment, the first time offset value is configurable.

[0446] As one embodiment, the first time offset value being configurable means that the first time offset value can be configured by RRC signaling.

[0447] As one embodiment, the first time offset value being configurable means that the first time offset value can be configured by higher layer signaling.

[0448] As one embodiment, the first time offset value being configurable means that the first time offset value is dependent on a higher layer parameter configuration.

[0449] As one embodiment, the given time domain resource block is the earliest one of the K1 time domain resource blocks after the time domain resource occupied by the first information block is delayed by the first time offset value.

[0450] As an embodiment, the given time domain resource block is the earliest one of the K1 time domain resource blocks after the starting time of the time domain resource occupied by the first information block is delayed by the first time offset value.

[0451] As an embodiment, the given time domain resource block is the earliest one of the K1 time domain resource blocks after the ending time of the time domain resource occupied by the first information block is delayed by the first time offset value.

[0452] As an embodiment, the given time domain resource block is the earliest one of the K1 time domain resource blocks after the time slot where the time domain resource occupied by the first information block is located is delayed by the first time offset value.

[0453] As an embodiment, the given time domain resource block is the first resource block that occurs after the starting time of the time domain resource occupied by the first information block in the first set of time domain resources is delayed by the first time offset value.

[0454] As an embodiment, the given time domain resource block is the first resource block that occurs after the ending time of the time domain resource occupied by the first information block in the first set of time domain resources is delayed by the first time offset value.

[0455] As an embodiment, the given time domain resource block is the first resource block that occurs after the time slot where the time domain resource occupied by the first information block in the first set of time domain resources is located is delayed by the first time offset value.

[0456] Embodiment 8

[0457] Embodiment 8 illustrates a schematic diagram of the relationship of the first reference signal, the first information block and the second information block according to an embodiment of the present application, as shown in FIG. 8. In FIG. 8, the horizontal axis represents time, the diamond cross-filled rectangle represents the time domain resource occupied by the first information block in time, the cross cross-filled rectangle represents the time domain resource occupied by the second information block in time, and the gray solid-filled rectangle represents the time domain resource occupied by the first reference signal in time; the interval between the time domain resource occupied by the first reference signal and the time domain resource occupied by the first information block is not less than the second threshold value.

[0458] In embodiment 8, the second threshold value is fixed, or the second threshold value is configurable.

[0459] As an embodiment, the unit of the second threshold value is millisecond.

[0460] As one embodiment, the unit of the second threshold is microsecond.

[0461] As one embodiment, the unit of the second threshold is time slot.

[0462] As one embodiment, the unit of the second threshold is OFDM symbol.

[0463] As one embodiment, the unit of the second threshold is multicarrier symbol.

[0464] As one embodiment, the second threshold is positive integer.

[0465] As one embodiment, the second threshold is positive real number.

[0466] As one embodiment, the second threshold is fixed, or the second threshold is configurable.

[0467] As one embodiment, the second threshold is fixed.

[0468] As one embodiment, the second threshold is fixed means that the second threshold is predefined.

[0469] As one embodiment, the second threshold is fixed means that the second threshold is default.

[0470] As one embodiment, the second threshold is fixed means that the second threshold is default.

[0471] As one embodiment, the second threshold is fixed means that the second threshold is reported by the first node.

[0472] As one embodiment, the second threshold is fixed means that the second threshold does not need to be indicated by base station.

[0473] As one embodiment, the second threshold is fixed means that the second threshold does not need to be configured or updated by higher layer signaling.

[0474] As one embodiment, the second threshold is fixed means that the second threshold cannot be configured or updated by higher layer signaling.

[0475] As one embodiment, the second threshold is configurable.

[0476] As one embodiment, the second threshold is configurable means that the second threshold can be configured by higher layer signaling.

[0477] As one embodiment, the second threshold is configurable means that the second threshold can be configured by RRC signaling.

[0478] As one embodiment, the second threshold is configurable, meaning that the second threshold depends on a higher layer parameter configuration.

[0479] As one embodiment, a gap between time domain resources occupied by the first reference signal and time domain resources occupied by the first information block is not less than the second threshold.

[0480] As one embodiment, a gap between an ending time of time domain resources occupied by the first reference signal and a starting time of time domain resources occupied by the first information block is not less than the second threshold.

[0481] As one embodiment, a gap between a last symbol of time domain resources occupied by the first reference signal and a first symbol of time domain resources occupied by the first information block is not less than the second threshold.

[0482] As one embodiment, a gap between a slot where time domain resources occupied by the first reference signal are located and a slot where time domain resources occupied by the first information block are located is not less than the second threshold.

[0483] As one embodiment, a gap between an ending time of time domain resources occupied by the first reference signal and a starting time of time domain resources occupied by a physical layer channel of the first information block is not less than the second threshold.

[0484] As one embodiment, a gap between a last symbol of time domain resources occupied by the first reference signal and a first symbol of time domain resources occupied by a physical layer channel of the first information block is not less than the second threshold.

[0485] As one embodiment, a gap between a slot where time domain resources occupied by the first reference signal are located and a slot where time domain resources occupied by a physical layer channel of the first information block are located is not less than the second threshold.

[0486] As one embodiment, an ending time of time domain resources occupied by the first reference signal is at least the second threshold earlier than a starting time of time domain resources occupied by the first information block.

[0487] As one embodiment, a last symbol of time domain resources occupied by the first reference signal is at least the second threshold earlier than a first symbol of time domain resources occupied by the first information block.

[0488] As one embodiment, a slot where time domain resources occupied by the first reference signal are located is at least the second threshold earlier than a slot where time domain resources occupied by the first information block are located.

[0489] As an embodiment, an ending time of the time-domain resource occupied by the first reference signal is at least the second threshold ahead of a starting time of the time-domain resource occupied by the physical layer channel occupied by the first information block.

[0490] As an embodiment, a last symbol of the time-domain resource occupied by the first reference signal is at least the second threshold ahead of a first symbol of the time-domain resource occupied by the physical layer channel occupied by the first information block.

[0491] As an embodiment, a time slot where the time-domain resource occupied by the first reference signal is located is at least the second threshold ahead of a time slot where the time-domain resource occupied by the physical layer channel occupied by the first information block is located.

[0492] Embodiment 9

[0493] Embodiment 9 illustrates a schematic diagram of the first threshold according to an embodiment of the present application, as shown in FIG. 9. In FIG. 9, the first threshold depends on an ID associated with the reported information of the beam management for prediction.

[0494] In embodiment 9, the reported information of the beam management is prediction.

[0495] As an embodiment, the ID refers to identity.

[0496] As an embodiment, the ID refers to Identify.

[0497] As an embodiment, the ID refers to Identification.

[0498] As an embodiment, the ID refers to Identity.

[0499] As an embodiment, the ID refers to Identifier.

[0500] As an embodiment, the ID refers to Index.

[0501] As an embodiment, the reported information of the beam management is prediction, and the first threshold depends on an ID associated with the reported information of the beam management for prediction.

[0502] As an embodiment, the meaning of prediction in the present application includes AI (Artificial Intelligence) inference.

[0503] As an embodiment, the meaning of the prediction in this application includes ML (Machine Learning) inference.

[0504] As an embodiment, the meaning of the prediction in this application includes AI / ML inference.

[0505] As an embodiment, the meaning of the prediction in this application includes AI / ML model generation.

[0506] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the generation of the reporting information of the beam management is based on prediction.

[0507] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the generation of the reporting information of the beam management is based on AI / ML.

[0508] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the generation of the reporting information of the beam management is based on LCM (Life Cycle Management).

[0509] As an embodiment, the LCM in this application includes AI / ML model LCM, and the AI / ML model LCM includes one or more of model training, model inference, model monitoring, model selection, and model update.

[0510] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the triggering of the reporting information of the beam management is based on prediction.

[0511] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the triggering of the reporting information of the beam management is based on AI / ML.

[0512] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the triggering of the reporting information of the beam management is based on LCM.

[0513] As an embodiment, the meaning of the prediction in the reporting information of the beam management includes that the reporting information of the beam management includes a prediction result.

[0514] As an embodiment, the ID associated with the reporting information of the beam management for prediction includes an AI / ML model ID (model ID) for prediction.

[0515] As an embodiment, the AI / ML model identified by the model ID described in the present application can be logical, and the mapping relationship from the logical AI / ML model to the physical AI / ML model is usually implemented by the device manufacturer itself; and the model ID corresponding to the same AI / ML model in different stages of the LCM can be different, that is, the model ID described in the present application can not be globally unique.

[0516] As an embodiment, the ID associated with the reporting information of the beam management for prediction includes an AI / ML functionality ID (functionality ID) for prediction.

[0517] As an embodiment, the functionality described in the present application refers to an AI / ML-enabled feature or feature group (FG) enabled by configuration, wherein the configuration is supported according to the UE capability indication.

[0518] As an embodiment, the ID associated with the reporting information of the beam management for prediction includes an AI entity for prediction.

[0519] As an embodiment, the entity described in the present application includes an AI entity, and the embodiments of the present application do not limit the specific implementation of the AI entity. The AI entity can be located on the network side and interact with the network device, or be located inside the network device; or be located on the user side and interact with the UE (User Equipment, user equipment), or be located inside the UE.

[0520] As an embodiment, one possible implementation of the AI entity described in the present application is that the AI entity is deployed in a server or a cloud device of an Over The Top (OTT) system. Optionally, the cloud device is located in one or more of the user equipment side, the network device side, or the core network side.

[0521] As an embodiment, the ID associated with the reporting information of the beam management for prediction includes a reference signal set ID for spatial prediction associated with the reporting information of the beam management.

[0522] As an embodiment, the ID associated with the reporting information of the beam management for prediction includes a reference signal set ID for time domain prediction associated with the reporting information of the beam management.

[0523] As an embodiment, the ID for prediction associated with the reporting information of the beam management comprises: whether the beam management use case associated with the reporting information of the beam management is BM-Case1 or BM-Case2.

[0524] Embodiment 10

[0525] Embodiment 10 illustrates a schematic diagram of the second threshold according to an embodiment of the present application, as shown in FIG. 10. In FIG. 10, the second threshold depends on the ID for prediction associated with the reporting information of the beam management.

[0526] In embodiment 10, the reporting information of the beam management is prediction.

[0527] As an embodiment, the reporting information of the beam management is prediction, and the second threshold depends on the ID for prediction associated with the reporting information of the beam management.

[0528] As an embodiment, the second threshold depends on the AI / ML model ID for prediction.

[0529] As an embodiment, the second threshold depends on the AI / ML function ID for prediction.

[0530] As an embodiment, the second threshold depends on the AI entity for prediction.

[0531] As an embodiment, the second threshold depends on the reference signal set ID for spatial domain prediction.

[0532] As an embodiment, the second threshold depends on the reference signal set ID for time domain prediction.

[0533] As an embodiment, the second threshold depends on whether the beam management use case is BM-Case1 or BM-Case2.

[0534] Embodiment 11

[0535] Embodiment 11 illustrates a schematic diagram of RAN domain AI / ML function deployment according to an embodiment of the present application, as shown in FIG. 11. In FIG. 11, the gNB can be replaced by a network device such as eNB, or 6G base station, etc.

[0536] In embodiment 11, the management of the ML inference functions of the plurality of base stations is done by the RAN domain management function 1102, i.e. data interaction with the RAN domain MnS (Management Service) consumer / cross-domain management 1101 (as shown by the dashed arrow in Fig. 11). The RAN domain ML training function 1103 is located in the RAN domain management function 1102; while the ML inference functions are located in the base stations, i.e. the AI / ML inference function 1104 is located in the gNB 1105, the AI / ML inference function 1106 is located in the gNB 1107, and so on.

[0537] The AI / ML related functions include ML training function (also referred to as AI training, or AI / ML training), ML testing function, ML inference function (also referred to as AI inference, or AI / ML inference), and so on. The ML training function, the ML testing function, and the ML inference function can be deployed independently, or can be co-located. The deployment of the AI / ML related functions can be implemented by software, e.g. the download and / or running of executable files; or can be implemented by software in combination with hardware, e.g. specific computing units are accelerated by hardware to improve the operation speed or save power consumption.

[0538] For the ML training function, it can be deployed in a cross-domain management system, or a domain-specific management system for managing a RAN domain or a CN (Core Network) domain. For example, for the ML training function of MDA (Management Data Analytics), it can be deployed in a MDAF (Management Data Analytic Function); for the ML training of network data analytics, it can be deployed in a NWDAF (NetWork Data Analytics Function), i.e. the ML training function is a MTLF (Model Training Logical Function).

[0539] For the ML inference function, it can also be deployed in a cross-domain management system, or a domain-specific management system; for example, the ML inference function is a MDAF, or the ML inference function is an AnLF (Analytics Logical Function) located in a NWDAF.

[0540] Similarly, the ML inference function can also be deployed in the cross-domain management system, or the domain-specific management system.

[0541] Optionally, the management of the ML inference function can also be completed by the base station itself, i.e., each base station can independently interact with the RAN domain MnS consumer / cross-domain management 1101.

[0542] It should be noted that embodiment 11 is only one non-limiting implementation; optionally, the ML training function of the RAN domain can also be deployed in the base station; or optionally, part of the base stations deploy the ML inference function and the ML training function of the RAN domain, and part of the base stations only deploy the ML inference function.

[0543] As an embodiment, one gNB (or base station) in embodiment 11 is the second node of the application.

[0544] Embodiment 12

[0545] Embodiment 12 illustrates a schematic diagram of AI / ML function deployment of a UE according to an embodiment of the application, as shown in FIG. 12. In FIG. 12, the RAN domain ML training function 1204 is optional.

[0546] The UE function 1203 is deployed in the first node of the application, and the UE function 1203 includes an AI / ML inference function 1205; the AI / ML inference function 1205 uses a ML model (also referred to as an AI model) for inference; a ML model is usually trained before being used for AI / ML inference.

[0547] As an embodiment, the UE function 1203 includes a RAN domain ML training function 1204, which runs training data through a ML model to derive a related loss, and adjusts parameters of the ML model based on the calculated loss; the ML training includes at least one of ML initial training, ML re-training, and reinforcement learning.

[0548] The above embodiments can reduce the complexity of the base station, or save the air interface resources caused by reporting training data; however, the above embodiments have higher requirements for the processing capability of the UE side.

[0549] Optionally, the UE function 1203 also includes a CN domain ML training function (not included in FIG. 12).

[0550] Optionally, the UE function 1203 further comprises an AI / ML deployment function - not included in Figure 12 - for loading ML models and data.

[0551] As an embodiment, the first node indicates whether the ML training function (RAN domain or CN domain) is supported through capability reporting, which is RRC signaling or NAS (Non-Access Stratum) signaling.

[0552] As an embodiment, the ML model, and related metadata, is loaded by the first node from a network device or a remote server.

[0553] Optionally, the UE function 1203 is a MnS producer providing data to the CN domain MnF and / or RAN domain MnF and / or cross-domain management system 1201 for management or analytics (as indicated by double-headed arrow 1202).

[0554] Optionally, the UE function 1203 is a MnS consumer loading data from the CN domain MnF and / or RAN domain MnF and / or cross-domain management system 1201 for AI / ML related management, such as management data requests, ML model activation, and / or ML training, etc. (as indicated by double-headed arrow 1202).

[0555] As an embodiment, the second information block in the present application is obtained through inference by the AI / ML inference function 1105.

[0556] As an embodiment, the reporting information of the beam management in the present application is obtained through inference by the AI / ML inference function 1105.

[0557] As an embodiment, the ML model is based on a NN.

[0558] As an embodiment, the ML model is based on an ANN.

[0559] As an embodiment, the ML model is based on a CNN.

[0560] As an embodiment, the ML model is based on a LLM architecture.

[0561] As an embodiment, the ML model is based on a Transformer architecture.

[0562] As one embodiment, the ML model is based on LSTM.

[0563] As one embodiment, the ML model is based on MLP.

[0564] As one embodiment, the ML model is based on GAN.

[0565] As one embodiment, the ML model is based on a light-weight neural network.

[0566] As one sub-embodiment of this embodiment, the light-weight neural network includes one or more of MobileNet, ShuffleNet, and SqueezeNet.

[0567] Embodiment 13

[0568] Embodiment 13 illustrates a schematic diagram of an artificial intelligence or machine learning based processing system according to one embodiment of the present application, as shown in FIG. 13. In FIG. 13, the artificial intelligence or machine learning based processing system includes a first processing machine, a second processing machine, a third processing machine, and a fourth processing machine.

[0569] In embodiment 13, the first processing machine sends a first data set to the second processing machine, and sends a second data set to the third processing machine; the second processing machine generates a target first-type parameter group according to the first data set, and sends the generated target first-type parameter group to the third processing machine; the third processing machine processes the second data set using the target first-type parameter group to obtain a first-type output, and optionally, sends the first-type output to the fourth processing machine. In FIG. 13, a first-type feedback and a second-type feedback are optional; the second processing machine includes an ML training function; and the third processing machine includes an ML inference function.

[0570] As one embodiment, the fourth processing machine includes an ML testing function.

[0571] As one embodiment, the fourth processing machine includes performance monitoring / evaluation of the ML model.

[0572] As one embodiment, the third processing machine sends a first-type feedback to the second processing machine; and the first-type feedback is used to trigger re-computation or update of the target first-type parameter group, i.e., trigger ML initial training or ML re-training.

[0573] As an embodiment, the fourth processor sends second type feedback to the first processor; the second type feedback is used to generate the first data set or the second data set, or the second type feedback is used to trigger sending of the first data set or sending of the second data set.

[0574] As an embodiment, the first processor generates the first data set and the second data set according to measurement of a reference signal.

[0575] As an embodiment, the third processor belongs to the first node, and the fourth processor belongs to the second node.

[0576] As an embodiment, the first data set includes training data.

[0577] As an embodiment, the second processor is used to train an ML model, and the trained model is described by the target first type parameter group.

[0578] As an embodiment, the second processor belongs to the first node; the above method avoids passing the first data set to the second node.

[0579] As an embodiment, the second processor belongs to the second node; the above method supports joint training and optimizes system performance.

[0580] As an embodiment, the second processor belongs to a core network; the above method supports network-wide joint training and further optimizes system performance.

[0581] As an embodiment, the second data set includes inference data.

[0582] As an embodiment, the third processor belongs to the first node.

[0583] As an embodiment, the third processor constructs a model according to the target first type parameter group, and then inputs the second data set into the constructed model to obtain the first type output.

[0584] As an embodiment, the second data set includes the first reference signal.

[0585] As an embodiment, the second data set includes L1 measurement results obtained by measuring the first reference signal.

[0586] As an embodiment, the second data set includes beam-level measurement results obtained by measuring the first reference signal.

[0587] As one embodiment, the second data set comprises L1 prediction results generated by the first node based on the first reference signal.

[0588] As one embodiment, the second data set comprises beam level prediction results generated by the first node based on the first reference signal.

[0589] As one embodiment, the first type of output comprises the second information block.

[0590] As one embodiment, the first type of output comprises the beam management reporting information.

[0591] As one embodiment, the first type of output comprises whether to send the first information block.

[0592] As one embodiment, the first type of output comprises the first threshold.

[0593] As one embodiment, the first type of output comprises the second threshold.

[0594] As one embodiment, the first type of output comprises a time predicted by the first node at which the first information block is triggered based on the first reference signal.

[0595] As one embodiment, the first type of output comprises a time predicted by the first node at which RLF (Radio Link Failure) occurs based on the first reference signal.

[0596] As one embodiment, the third processor generates a recovery data set according to the first type of output, and errors of the recovery data set and the second data set are used to generate the first type of feedback.

[0597] As one embodiment, the first type of feedback is used to reflect performance of the trained model; when the performance of the trained model cannot meet requirements, the second processor recalculates the target first type of parameter group.

[0598] As one embodiment, when the error is too large or the time for updating is too long, the performance of the trained model is considered to be unable to meet requirements.

[0599] As one embodiment, the target first type of parameter group comprises one or more of a convolution kernel, a pool core, a pooling function, an activation function, a parameter of the pooling function, or a parameter of the activation function.

[0600] As an example, the target first-type parameter group comprises one or more of a convolution kernel size, a convolution layer number, a convolution stride, a pooling kernel size, a pooling kernel stride, a pooling function, an activation function, or a feature map number.

[0601] Embodiment 14

[0602] Embodiment 14 illustrates an AI / ML based schematic diagram according to an embodiment of the present application, as shown in FIG. 14. In FIG. 14, the first operation and the second operation belong to a first phase, the third operation belongs to a second phase, the fourth operation belongs to a third phase, and the fifth operation belongs to a fourth phase; the arrowed line represents the order of the flow.

[0603] As an example, the first operation comprises AI / ML training, the second operation comprises AI / ML testing, the third operation comprises AI / ML emulation, the fourth operation comprises AI / ML entity loading, and the fifth operation comprises AI / ML inference.

[0604] As an example, the first phase comprises a training phase, the second phase comprises an emulation phase, the third phase comprises a deployment phase, and the fourth phase comprises an inference phase.

[0605] As an example, the first phase comprises AI / ML model training.

[0606] As an example, the first phase comprises AI / ML model training and AI / ML testing.

[0607] As an example, the AI / ML model training comprises initial training and re-training of one or a group of AI / ML entities.

[0608] As an example, the AI / ML model training relies on training data.

[0609] As an example, the AI / ML model training comprises AI / ML entity validation.

[0610] As an example, the AI / ML entity validation is used to evaluate the performance of the AI / ML entity.

[0611] As one embodiment, the AI / ML entity validation relies on validation data.

[0612] As one embodiment, if the result of the AI / ML entity validation does not meet expectations, the AI / ML model will be retrained.

[0613] As one embodiment, the AI / ML testing includes testing the validated AI / ML entity to estimate the performance of the trained AI / ML model.

[0614] As one embodiment, if the result of the AI / ML testing meets expectations, the AI / ML entity proceeds to the next stage; otherwise, the AI / ML model will be retrained.

[0615] As one embodiment, the AI / ML testing relies on testing data.

[0616] As one embodiment, the second stage includes AI / ML simulation, which simulates the inference of the AI / ML entity in a simulation environment.

[0617] As one embodiment, the AI / ML simulation estimates the performance of the inference of the AI / ML entity in a simulation environment before the AI / ML entity is used.

[0618] As one embodiment, the second stage is optional.

[0619] As one embodiment, the third stage includes AI / ML entity loading, which is to obtain the trained AI / ML entity to obtain the desired AI / ML inference function.

[0620] As one embodiment, the third stage is optional.

[0621] As one embodiment, the third stage is no longer needed when the training function and the inference function are co-located.

[0622] As one embodiment, the fourth stage includes AI / ML inference.

[0623] Embodiment 15

[0624] Embodiment 15 illustrates a structural block diagram of a processing device in a first node according to one embodiment of the present application, as shown in FIG. 15. In FIG. 15, the processing device 1500 in the first node includes a first receiver 1501 and a first transmitter 1502, where the first receiver 1501 is optional.

[0625] In embodiment 15, the first transmitter 1502 transmits a first information block and a second information block, the first information block indicates transmission of the second information block, and the second information block comprises reporting information of beam management.

[0626] In embodiment 15, the transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the starting time of the first information block to the starting time of the second information block is a first time window; and the PUSCH time domain resource dynamically indicated by the first node received in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0627] As an embodiment, the duration of the first time window in time domain is not less than a first threshold, and the first threshold is fixed or configurable.

[0628] As an embodiment, the first threshold depends on at least one of the following:

[0629] The packetization capability of the uplink data channel of the first node;

[0630] The decoding capability of the uplink reception of the receiver of the first information block.

[0631] As an embodiment, the reporting information of the beam management comprises CRI and RSRP.

[0632] As an embodiment, the non-dynamically scheduled resource comprises a configuration granted resource or a preconfigured resource.

[0633] As an embodiment, the reporting information of the beam management is predicted, and the first threshold depends on the ID associated with the reporting information of the beam management for prediction.

[0634] As an embodiment, the first receiver 1501 receives a first reference signal; the reporting information of the beam management depends on the channel measurement of the first reference signal, and the interval between the time domain resource occupied by the first reference signal and the time domain resource occupied by the first information block is not less than a second threshold, and the second threshold is fixed or configurable.

[0635] As an embodiment, the reporting information of the beam management is predicted, and the second threshold depends on the ID associated with the reporting information of the beam management for prediction.

[0636] As an embodiment, the second information block occupies one given time domain resource block among K1 time domain resource blocks included in the first set of time domain resources; the K1 is a positive integer greater than 1; the given time domain resource block is the earliest one among the K1 time domain resource blocks after a first time offset value from the time domain resource occupied by the first information block; the first time offset value is fixed, or the first time offset value is configurable.

[0637] As an embodiment, the first information block is used to notify the transmission of the second information block.

[0638] As an embodiment, the reporting information of the beam management includes SSBRI and RSRP.

[0639] As an embodiment, the event triggering the transmission of the first information block is Event-2.

[0640] As a sub-embodiment of this embodiment, the Event-2 means that the quality of at least one new beam becomes better than the quality of the current beam by a given threshold.

[0641] As a sub-embodiment of this embodiment, when the number of Event-2 instances of at least one same new beam is greater than or equal to M within a given time window, the first node triggers the transmission of the first information block, the M being configurable.

[0642] As an embodiment, the first node triggers the transmission of the first information block when the condition that the quality of at least the same new beam becomes better than the quality of the current beam by a given threshold is satisfied at least M times, the M being configurable.

[0643] As an embodiment, the second information block does not occupy the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0644] As an embodiment, the time domain resources occupied by the second information block do not belong to the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0645] As an embodiment, the first node does not transmit the reporting information of the beam management on the PUSCH time domain resources indicated by the dynamic scheduling received by the first node in the first time window.

[0646] As an embodiment, the first node assumes that there is no overlap between the PUSCH time domain resources indicated by the dynamic scheduling and the time domain resources occupied by the second information block in the first time window.

[0647] As an embodiment, the first node does not assume that there is overlap between the PUSCH time domain resources indicated by dynamic scheduling received in the first time window and the time domain resources occupied by the second information block.

[0648] As an embodiment, the first node assumes that there is no overlap between the PUSCH time domain resources indicated by dynamic scheduling received in the first time window and the time domain resources occupied by the second information block.

[0649] As an embodiment, the first node does not assume that there is overlap between the PUSCH time domain resources indicated by dynamic scheduling received in the first time window and the time domain resources occupied by the second information block.

[0650] As an embodiment, the first node does not expect that there is overlap between the PUSCH time domain resources indicated by dynamic scheduling received in the first time window and the time domain resources occupied by the second information block.

[0651] As an embodiment, whether the reporting information of the beam management includes the measurement result of the channel measurement of the first node for the first reference signal depends on the configuration or indication of the receiver of the first information block.

[0652] As an embodiment, whether the first node triggers the first information block depends on the channel measurement for the first reference signal.

[0653] As an embodiment, the first node 1500 is a user equipment.

[0654] As an embodiment, the first node 1500 is a terminal.

[0655] As an embodiment, the first node 1500 is a relay node device.

[0656] As an embodiment, the first receiver 1501 includes at least one of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, the data source 467} in Embodiment 4.

[0657] As an embodiment, the first transmitter 1502 includes at least one of {the antenna 452, the transmitter 454, the transmitting processor 468, the multi-antenna transmitting processor 457, the controller / processor 459, the memory 460, the data source 467} in Embodiment 4.

[0658] Embodiment 16

[0659] Embodiment 16 illustrates a structure block diagram of a processing apparatus in a second node according to an embodiment of the present application, as shown in FIG. 16. In FIG. 16, the processing apparatus 1600 in the second node includes a second transmitter 1601 and a second receiver 1602, wherein the second transmitter 1601 is optional.

[0660] In Embodiment 16, the second receiver 1602 receives a first information block and a second information block, the first information block indicates the reception of the second information block, and the second information block includes reporting information of beam management.

[0661] In Embodiment 16, the transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the starting time of the first information block to the starting time of the second information block is a first time window; and the PUSCH time domain resource indicated by dynamic scheduling received by the transmitter of the first information block in the first time window is orthogonal to the time domain resource occupied by the second information block.

[0662] As an embodiment, the duration of the first time window in time domain is not less than a first threshold, and the first threshold is fixed or configurable.

[0663] As an embodiment, the first threshold depends on at least one of the following:

[0664] The packet assembling capability of the uplink data channel of the transmitter of the first information block;

[0665] The decoding capability of the uplink reception of the second node.

[0666] As an embodiment, the reporting information of the beam management includes CRI and RSRP.

[0667] As an embodiment, the non-dynamically scheduled resource includes a configuration granted resource or a pre-configured resource.

[0668] As an embodiment, the reporting information of the beam management is predicted by the transmitter of the first information block, and the first threshold depends on the ID associated with the reporting information of the beam management for prediction.

[0669] As an embodiment, the second transmitter 1601 transmits a first reference signal; a transmitter of the first information block receives the first reference signal, the reporting information of the beam management depends on a channel measurement of the transmitter of the first information block on the first reference signal, an interval between a time domain resource occupied by the first reference signal and a time domain resource occupied by the first information block is no less than a second threshold, the second threshold is fixed, or the second threshold is configurable.

[0670] As an embodiment, the reporting information of the beam management is predicted by the transmitter of the first information block, and the second threshold depends on an ID associated with the reporting information of the beam management for prediction.

[0671] As an embodiment, the second information block occupies a given time domain resource block in K1 time domain resource blocks included in a first time domain resource set; K1 is a positive integer greater than 1; the given time domain resource block is the earliest one of the K1 time domain resource blocks after a first time offset value from a time domain resource occupied by the first information block; the first time offset value is fixed, or the first time offset value is configurable.

[0672] As an embodiment, the first information block is used to notify the second node of reception of the second information block.

[0673] As an embodiment, the reporting information of the beam management includes SSBRI and RSRP.

[0674] As an embodiment, an event triggering the transmitter of the first information block to transmit the first information block is Event-2.

[0675] As a sub-embodiment of this embodiment, the Event-2 means that the quality of at least one new beam becomes better than the quality of the current beam by a given threshold.

[0676] As a sub-embodiment of this embodiment, when the number of Event-2 instances of at least one same new beam is greater than or equal to M within a given time window, the transmitter of the first information block triggers transmission of the first information block, and M is configurable.

[0677] As an embodiment, when the condition that the quality of at least the same new beam becomes better than the quality of the current beam by a given threshold is satisfied at least M times, the transmitter of the first information block triggers transmission of the first information block, and M is configurable.

[0678] As one embodiment, the second information block does not occupy PUSCH time domain resources indicated by dynamic scheduling received by the first information block's transmitter in the first time window.

[0679] As one embodiment, the second information block occupies PUSCH time domain resources not indicated by dynamic scheduling received by the first information block's transmitter in the first time window.

[0680] As one embodiment, the first information block's transmitter does not transmit the beam management reporting information on PUSCH time domain resources indicated by dynamic scheduling received by the first information block's transmitter in the first time window.

[0681] As one embodiment, the first information block's transmitter assumes that there is no overlap between PUSCH time domain resources indicated by dynamic scheduling received in the first time window and time domain resources occupied by the second information block.

[0682] As one embodiment, the first information block's transmitter does not assume that there is overlap between PUSCH time domain resources indicated by dynamic scheduling received in the first time window and time domain resources occupied by the second information block.

[0683] As one embodiment, the first information block's transmitter believes that there is no overlap between PUSCH time domain resources indicated by dynamic scheduling received in the first time window and time domain resources occupied by the second information block.

[0684] As one embodiment, the first information block's transmitter does not believe that there is overlap between PUSCH time domain resources indicated by dynamic scheduling received in the first time window and time domain resources occupied by the second information block.

[0685] As one embodiment, the first information block's transmitter does not expect that there is overlap between PUSCH time domain resources indicated by dynamic scheduling received in the first time window and time domain resources occupied by the second information block.

[0686] As one embodiment, whether the first information block's transmitter includes measurement results of the channel measurement for the first reference signal in the beam management reporting information depends on configuration or indication of the second node.

[0687] As one embodiment, whether the first information block's transmitter triggers the first information block depends on the channel measurement for the first reference signal.

[0688] As one embodiment, the second node 1600 is a base station device.

[0689] As one embodiment, the second node 1600 is a user equipment.

[0690] As one embodiment, the second node 1600 is a TRP.

[0691] As one embodiment, the second transmitter 1601 includes at least one of {the antenna 420, the transmitter 418, the transmit processor 416, the multi-antenna transmit processor 471, the controller / processor 475, the memory 476} in embodiment 4.

[0692] As one embodiment, the second receiver 1602 includes at least one of {the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller / processor 475, the memory 476} in embodiment 4.

[0693] Those skilled in the art can understand that all or part of the steps in the foregoing method can be instructed by programs to related hardware, and the programs can be stored in a computer readable storage medium, such as a read-only memory, a hard disk, an optical disk or the like. Alternatively, all or part of the steps of the foregoing embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the foregoing embodiments can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in the present application include but are not limited to unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebook computers, vehicle-mounted communication devices, vehicles, vehicles, RSUs, wireless sensors, network cards, Internet of Things terminals, RFID (Radio Frequency Identification) terminals, NB-IoT (Narrow Band Internet of Things) terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base station or system device in the present application includes but is not limited to macro cellular base stations, micro cellular base stations, small cellular base stations, home base stations, relay base stations, eNB (evolved Node B), gNB, TRP, GNSS (Global Navigation Satellite System), relay satellites, satellite base stations, air base stations, RSUs, unmanned aerial vehicles, test equipment such as wireless communication devices that simulate part of the functions of base stations or signaling testers, and the like.

[0694] Those skilled in the art will understand that the application can be implemented by other specified forms without departing from the core or essential characteristics thereof. Therefore, the presently disclosed embodiments should in no way be considered as descriptive rather than limiting. The scope of the application is determined by the appended claims rather than the preceding description, and all modifications within the equivalent meaning and range of the claims are considered to be included therein.

Claims

1. A method in a node used for wireless communication beam management, characterized by, Comprising: transmitting a first information block and a second information block, the first information block indicating transmission of the second information block, the second information block comprising reporting information for beam management; wherein the transmission of the first information block is event triggered; the first information block is transmitted on PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; the first time window from the starting moment of the first information block to the starting moment of the second information block; the PUSCH time domain resource indicated by dynamic scheduling received by the terminal in the first time window is orthogonal to the time domain resource occupied by the second information block.

2. The method of claim 1, wherein, The duration of the first time window in the time domain is not less than a first threshold, and the first threshold is fixed or configurable.

3. The method of claim 2, wherein, The first threshold depends on at least one of the following: The packet assembly capability of the uplink data channel of the terminal; The decoding capability of the uplink reception of the receiver of the first information block.

4. The method according to any one of claims 1 to 3, characterized in that, The reporting information for beam management includes CRI and RSRP.

5. The method according to any one of claims 1 to 4, characterized in that, The non-dynamically scheduled resource includes a configuration granted resource, or the non-dynamically scheduled resource includes a preconfigured resource.

6. The method of any one of claims 2-3, wherein, The reporting information for beam management is predicted, and the first threshold depends on the ID associated with the prediction of the reporting information for beam management.

7. The method according to any one of claims 1 to 6, characterized in that, Comprising: receiving a first reference signal; wherein the reporting information for beam management depends on the channel measurement for the first reference signal, and the interval between the time domain resource occupied by the first reference signal and the time domain resource occupied by the first information block is not less than a second threshold, and the second threshold is fixed or configurable.

8. The method of claim 7, wherein, The reporting information for beam management is predicted, and the second threshold depends on the ID associated with the prediction of the reporting information for beam management.

9. The method according to any one of claims 1 to 8, characterized in that, The second information block occupies a given time domain resource block in the K1 time domain resource blocks included in the first time domain resource set; K1 is a positive integer greater than 1; the given time domain resource block is the earliest one of the K1 time domain resource blocks after the time domain resource occupied by the first information block is delayed by a first time offset value; the first time offset value is fixed or configurable.

10. A terminal, characterized in that, the terminal comprises one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, the computer program code comprising computer instructions, and the one or more processors invoke the computer instructions to cause the terminal to execute the method of any one of claims 1-9.

11. A method in a node used for wireless communication beam management, characterized by, Comprising: receiving a first information block and a second information block, the first information block indicating transmission of the second information block, the second information block comprising reporting information for beam management; The sending of the first information block is event triggered; the first information block is transmitted on a PUCCH, and the resource occupied by the second information block is non-dynamically scheduled; a starting time of the first information block to a starting time of the second information block is a first time window; and a PUSCH time domain resource indicated by dynamic scheduling and received by a sender of the first information block in the first time window is orthogonal to a time domain resource occupied by the second information block.

12. The method of claim 11, wherein, A duration of the first time window in a time domain is not less than a first threshold, and the first threshold is fixed or configurable.

13. The method of claim 12, wherein, The first threshold depends on at least one of the following: a packet assembling capability of an uplink data channel of the sender of the first information block; a decoding capability of uplink reception of the base station.

14. The method according to any one of claims 11 to 13, characterized in that, The reported information of the beam management includes CRI and RSRP.

15. The method according to any one of claims 11 to 14, characterized in that, The non-dynamically scheduled resource includes a configuration granted resource or a preconfigured resource.

16. The method according to any one of claims 11 to 15, characterized in that, The reported information of the beam management is predicted, and the first threshold depends on an ID associated with the reported information of the beam management for prediction.

17. The method of any one of claims 11 to 16, wherein, The method comprises: sending a first reference signal; The sender of the first information block receives the first reference signal, the reported information of the beam management depends on channel measurement of the sender of the first information block on the first reference signal, and an interval between a time domain resource occupied by the first reference signal and a time domain resource occupied by the first information block is not less than a second threshold, and the second threshold is fixed or configurable.

18. The method of claim 17, wherein, The reported information of the beam management is predicted by the sender of the first information block, and the second threshold depends on an ID associated with the reported information of the beam management for prediction.

19. The method of any one of claims 11-18, wherein, The second information block occupies a given time domain resource block in K1 time domain resource blocks included in a first time domain resource set; K1 is a positive integer greater than 1; the given time domain resource block is the earliest one of the K1 time domain resource blocks after a time domain resource occupied by the first information block is delayed by a first time offset value; and the first time offset value is fixed or configurable.

20. A base station, comprising: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is configured to store computer program code including computer instructions, and the one or more processors are configured to invoke the computer instructions to enable the base station to perform the method according to any one of claims 11-19.

Images