WO2025161030A1 - Event-driven beam management method and apparatus - Google Patents
Event-driven beam management method and apparatusInfo
- Publication number
- WO2025161030A1 WO2025161030A1 PCT/CN2024/075846 CN2024075846W WO2025161030A1 WO 2025161030 A1 WO2025161030 A1 WO 2025161030A1 CN 2024075846 W CN2024075846 W CN 2024075846W WO 2025161030 A1 WO2025161030 A1 WO 2025161030A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- event
- information
- beam management
- configuration information
- driven beam
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/24—Cell structures
- H04W16/28—Cell structures using beam steering
Definitions
- the embodiments of the present application relate to the field of communication technologies.
- High-frequency millimeter-wave communication is one of the key technical directions of 5G NR (fifth-generation new wireless).
- 5G NR frequency division multiple access
- high-frequency communications face challenges such as high transmission path loss and susceptibility to obstruction.
- the transmitter uses a large number of densely distributed antenna units, using beamforming to form beams pointing in specific directions to improve coverage.
- the receiver uses beamforming to receive beams in specific directions. This requires the transmitter to select an appropriate transmit beam and the receiver to select an appropriate receive beam to form a beam pair, which together maintain a good wireless link.
- Beam Management can establish and maintain such beam pairs.
- beam management is primarily initiated by the base station.
- the base station configures a reference signal (RS) for beam management for the terminal.
- the terminal reports its measurement results.
- the base station decides whether to initiate beam management based on these measurements and sends relevant signaling.
- the base station then performs the corresponding beam management operations based on the signaling. This type of beam management results in high signaling overhead, long latency, and significantly limited flexibility.
- event-driven beam management UE-initiated or event-driven beam management (hereinafter referred to as event-driven beam management) initiated by UE (called user equipment, terminal equipment, terminal, user, etc.) has been identified as one of the project contents.
- the UE can monitor the downlink beam quality.
- an event related to beam management is detected, it can actively initiate a beam management (such as beam switching) request to the base station, which can effectively reduce the delay of beam management, reduce signaling overhead, and improve network coverage.
- a beam management such as beam switching
- an embodiment of the present application provides an event-driven beam management method and device to reduce the latency of beam management, reduce signaling overhead, and improve network coverage.
- an event-driven beam management method comprising:
- the terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
- the terminal device sends event-driven beam management information based on the CSI reporting configuration information and/or the SR resource configuration information.
- the above-mentioned configuration information includes the above-mentioned CSI reporting configuration information and the above-mentioned SR resource configuration information.
- the terminal device detects a beam management event, the terminal device sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management in the above-mentioned SR resource configuration information, and receives the uplink scheduling authorization information sent by the network device.
- SR scheduling request
- the terminal device sends a CSI report, which includes the above-mentioned event-driven beam management information.
- the above-mentioned configuration information includes the above-mentioned CSI reporting configuration information
- the terminal device sends the above-mentioned event-driven beam management information according to the above-mentioned CSI reporting configuration information.
- the above-mentioned configuration information includes the above-mentioned SR resource configuration information.
- the terminal device detects a beam management event, it sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management according to the above-mentioned SR resource configuration information, and receives the uplink scheduling authorization information sent by the network device, and sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information.
- SR scheduling request
- One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, by reporting event-driven beam management information (such as event-driven beam switching information) through uplink control information, the delay of beam management can be effectively reduced, the signaling overhead can be reduced, and the network coverage can be improved.
- event-driven beam management information such as event-driven beam switching information
- FIG1 is a schematic diagram of an event-driven beam management method according to an embodiment of the present application.
- FIG2 is a schematic diagram of a terminal device sending event-driven beam management information according to CSI reporting configuration information and SR resource configuration information;
- FIG3 is a schematic diagram of a terminal device sending event-driven beam management information according to CSI reporting configuration information
- FIG4 is a schematic diagram of a terminal device reporting event-driven beam management information
- FIG5 is a schematic diagram of a terminal device sending event-driven beam management information according to SR resource configuration information
- FIG6 is a schematic diagram of a configuration method of event-driven beam management according to an embodiment of the present application.
- FIG7 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application.
- FIG8 is a schematic diagram of a configuration device for event-driven beam management according to an embodiment of the present application.
- FIG9 is a schematic diagram of a communication system according to an embodiment of the present application.
- FIG10 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application.
- FIG11 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
- the terms “first”, “second”, etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms.
- the term “and/or” includes any one and all combinations of one or more of the associated listed terms.
- the terms “comprising”, “including”, “having”, etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.
- the term “communication network” or “wireless communication network” may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), 5G (5Generation) New Radio (NR), etc.
- LTE Long Term Evolution
- LTE-A enhanced Long Term Evolution
- WCDMA Wideband Code Division Multiple Access
- HSPA High-Speed Packet Access
- 5G (5Generation) New Radio (NR) etc.
- communication between devices in the communication system may be carried out according to communication protocols of any stage, for example including but not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G new wireless, etc., and/or other communication protocols currently known or to be developed in the future.
- communication protocols for example including but not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G new wireless, etc., and/or other communication protocols currently known or to be developed in the future.
- network device refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services for the terminal device.
- Network devices may include, but are not limited to, base stations (BS), access points (AP), transmission reception points (TRP), broadcast transmitters, mobile management entities (MME), gateways, servers, radio network controllers (RNC), base station controllers (BSC), and the like.
- base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB), and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.).
- NodeB NodeB
- eNodeB or eNB evolved NodeB
- gNB 5G base station
- base station can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area.
- the term “cell” can refer to a base station and/or its coverage area, depending on the context in which the term is used.
- the term "user equipment” (UE) or “terminal equipment” (TE) refers to a device that accesses a communication network through a network device and receives network services.
- a terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.
- terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.
- PDAs personal digital assistants
- wireless modems wireless communication devices
- handheld devices machine-type communication devices
- machine-type communication devices laptop computers
- cordless phones smart phones
- smart watches digital cameras
- terminal devices can also monitor
- the machines or devices for control or measurement may include, but are not limited to, machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and the like.
- MTC machine type communication
- D2D device-to-device
- M2M machine-to-machine
- network side or “network device side” refers to one side of the network, which can be a base station or one or more network devices as described above.
- user side or “terminal side” or “terminal device side” refers to the user or terminal side, which can be a UE or one or more terminal devices as described above.
- device can refer to either network equipment or terminal equipment.
- uplink control information mainly includes Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK), Scheduling Request (SR), Channel State Information (CSI), etc.
- HARQ-ACK Hybrid Automatic Repeat Request Acknowledgement
- SR Scheduling Request
- CSI Channel State Information
- Uplink control information can be transmitted on the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Shared Channel (PUSCH).
- PUCCH Physical Uplink Control Channel
- PUSCH Physical Downlink Shared Channel
- SR is a type of UCI sent by the UE to the gNB via the PUCCH to request uplink resources from the network.
- Radio Resource Control pre-configures dedicated periodic PUCCH resources, which the UE uses to send SRs on the PUCCH.
- the RRC Information Element (IE) SchedulingRequestConfig configures SR parameters.
- the physical layer resources corresponding to the SR are configured in the schedulingRequestResourceToAddModList or schedulingRequestResourceToAddModListExt fields in PUCCH-Config. These two fields are lists, with the list elements representing the SR resource configuration, SchedulingRequestResourceConfig.
- CSI is also a type of UCI.
- the UE feeds back CSI to the base station in the form of CSI report, which can provide the base station with the parameters required for transmission.
- the relevant resources for CSI reporting are configured by the high-level parameter CSI-ReportConfig, and the specific CSI reporting content is configured by the reportQuantity field in CSI-ReportConfig.
- reportQuantity can be configured as:
- 'cri-RSRP' which provides feedback including the CSI-RS Resource Indicator (CRI) and Layer 1 Reference Signal Received Power (L1-RSRP), which represent beam index information and beam quality information, respectively, and can be used for CSI-RS-based beam management.
- CRI CSI-RS Resource Indicator
- L1-RSRP Layer 1 Reference Signal Received Power
- the SR resource configuration information may be included in the information element PUCCH-Config.
- a new field may be added to the information element PUCCH-Config to configure the SR resource configuration information associated with event-driven beam management.
- the SchedulingRequestResourceConfigExt-EventBM may include a switch field for indicating whether event-driven beam management is used.
- this switch field is called eventBeamManagementFlag and has a single value, such as "enabled.” If this switch field is configured, it indicates that the current SR resource is used for event-driven beam management.
- the SchedulingRequestResourceConfigExt-EventBM may also include a field indicating priority, such as phy-PriorityIndex, whose value can be any one of p0, p1, and p2, with the corresponding priorities from high to low being p2>p1>p0. If this field is not configured, the default priority is p0, which is the lowest priority.
- priority such as phy-PriorityIndex
- the SR resource configuration information may also be in other forms, or called other.
- the above switch field and/or the field indicating the priority contained in the SR resource configuration information may also be called other, and is not limited to the examples in the above example.
- the terminal device when it detects a beam management event, it can send the above SR information to the network device.
- the SR information can be carried by the dedicated SR resources configured for event-driven beam management by the above RRC resource configuration information, so as to inform the network device that the SR information is used for event-driven beam management.
- the terminal device can receive uplink scheduling authorization information sent by the network device.
- the uplink scheduling authorization information is used to schedule PUSCH and can be carried by DCI (downlink control information) format 0_1 or DCI format 0_2 or DCI format 0_3 (DCI format 0_1/0_2/0_3).
- the uplink scheduling grant information also needs to include a CSI request field. Used to trigger aperiodic CSI reporting.
- the terminal device after receiving the above uplink scheduling authorization information sent by the network device, the terminal device can send a CSI report on the PUSCH scheduled by the above uplink scheduling authorization information according to the above CSI reporting configuration information, and the CSI report includes the above event-driven beam management information.
- the PUSCH scheduled by the uplink scheduling grant information may carry uplink control information (UCI), which is the CSI reporting described above and includes event-driven beam management information. For example, if the UL-SCH indicator field in the uplink scheduling grant information is set to 0, the scheduled PUSCH only carries the UCI (CSI reporting).
- UCI uplink control information
- the PUSCH scheduled by the uplink scheduling grant information may also carry an uplink shared channel (UL-SCH).
- UL-SCH uplink shared channel
- the scheduled PUSCH not only carries the UL-SCH but also carries the UCI (CSI reporting), i.e., the UCI (CSI reporting) is multiplexed on the PUSCH.
- the terminal device can report event-driven beam management information based on the CSI reporting configuration information and SR resource configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
- the terminal device sends event-driven beam management information according to the above CSI reporting configuration information.
- FIG3 is a schematic diagram of this embodiment. As shown in FIG3, the method includes:
- the terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information associated with event-driven beam management.
- the terminal device sends event-driven beam management information according to the CSI reporting configuration information.
- the CSI reporting configuration information is, for example, a symbol CSI-ReportConfig, and its time domain characteristics, i.e., the reporting type (reportConfigType), is periodic (periodic) or semi-persistent (semiPersistentOnPUCCH or semiPersistentOnPUSCH).
- the terminal device sends corresponding event-driven beam management information after detecting an event-driven beam management event based on the CSI reporting configuration information.
- the CSI reporting configuration information may include a first field, and the first field is used to indicate that the CSI reporting configuration information is used for event-driven beam management.
- the first field may be a new field in CSI-ReportConfig, used to indicate that the user's current CSI reporting configuration information is used to report events and information related to event-driven beam management.
- the first field is called eventBeamManagementFlag, for example, which can be a switch field with only one value, called “enabled”. If the field eventBeamManagementFlag is configured, it indicates that the current CSI-ReportConfig For event-driven beam management.
- eventBeamManagementFlag included in the CSI-ReportConfig: ... eventBeamManagementFlag ENUMERATED ⁇ enabled ⁇ OPTIONAL,--Need M ...
- the above takes the first field called eventBeamManagementFlag as an example, but the present application is not limited to this.
- the first field can also be called other names as long as it can be used to indicate that the CSI reporting configuration information is used for event-driven beam management.
- the CSI reporting configuration information includes a second field, the value of which includes a first reporting option, and the first reporting option is used for event-driven beam management.
- the second field is, for example, the existing field reportQuantity in CSI-ReportConfig
- the first reporting option is, for example, the field EventBMInfo.
- the field EventBMInfo can be in a list format, and the list content is zero to multiple candidate beam information.
- the value of EventBMInfo is newBeamToAddModList in the form of a list (SEQUENCE), and the specific content of the list is zero to multiple candidate beam information (NewBeamInfo), with the maximum number not exceeding maxNrofNewBeam.
- the specific content of the candidate beam information is as described above and will not be repeated here.
- the terminal device may send event-driven beam management information according to the above CSI reporting configuration information when the above CSI reporting configuration information is effective or activated.
- the terminal device receives a dedicated periodic CSI reporting configuration information and the configuration takes effect, or receives a dedicated semi-persistent CSI reporting configuration and is activated through MAC-CE or DCI, then the terminal device reports the information of the new beam A and the new beam B at a reporting time (time T1) that meets the requirements of the CSI reporting configuration information, reports the information of the new beam A, the new beam B, and the new beam C at the next reporting time (time T2), does not report any new beam information at the next reporting time (time T3), and reports the new beam information at the next reporting time (time T4).
- Time T4 reports the new beam A, new beam C information... until the terminal device receives new high-level configuration, or receives the signaling to activate the reporting of "event-driven beam management events".
- the terminal device can report event-driven beam management information based on the CSI reporting configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
- the terminal device sends event-driven beam management information according to the above SR resource configuration information.
- FIG5 is a schematic diagram of this embodiment. As shown in FIG5, the method includes:
- the terminal device receives configuration information sent by the network device, where the configuration information includes SR resource configuration information associated with event-driven beam management.
- the terminal device When the terminal device detects a beam management event, it sends a scheduling request (SR) message to the network device on the dedicated SR resource configured for event-driven beam management.
- SR scheduling request
- the terminal device receives uplink scheduling authorization information sent by the network device;
- the terminal device sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
- the SR resource configuration information may be included in the information element PUCCH-Config.
- a new field may be added to the information element PUCCH-Config to configure the SR resource configuration information associated with event-driven beam management.
- the SR resource configuration information may be a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust SR resources related to event-driven beam management.
- the list element in the SR resource configuration information may be SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
- the SchedulingRequestResourceConfigExt-EventBM may include a switch field for indicating whether event-driven beam management is used. For example, it is called eventBeamManagementFlag, which has only one value, such as "enabled”. If the switch field eventBeamManagementFlag is configured, it indicates that the current SR resource is used for event-driven beam management.
- the SchedulingRequestResourceConfigExt-EventBM may also include a field indicating priority, such as phy-PriorityIndex, whose value can be any one of p0, p1, and p2, with the corresponding priorities from high to low being p2>p1>p0. If this field is not configured, the default priority is p0, which is the lowest priority.
- priority such as phy-PriorityIndex
- the SR resource configuration information may also be in other forms, or called other.
- the above switch field and/or the field indicating the priority contained in the SR resource configuration information may also be called other, and is not limited to the examples in the above example.
- the terminal device when it detects a beam management event, it can send the above SR information to the network device.
- the SR information can be carried by the dedicated SR resources configured for event-driven beam management by the above RRC resource configuration information, so as to inform the network device that the SR information is used for event-driven beam management.
- the terminal device can receive uplink scheduling authorization information sent by the network device.
- the uplink scheduling authorization information is used to schedule PUSCH and can be carried by DCI format 0_1 or DCI format 0_2 or DCI format 0_3 (DCI format 0_1/0_2/0_3).
- the terminal device after receiving the above uplink scheduling grant information sent by the network device, the terminal device can send the above event-driven beam management information on the PUSCH scheduled by the above uplink scheduling grant information.
- the PUSCH scheduled by the uplink scheduling grant information carries an uplink shared channel (UL-SCH), and the UL-SCH includes the above event-driven beam management information.
- the value of the UL-SCH indicator field in the uplink scheduling grant information is 1, indicating that the UL-SCH includes the above event-driven beam management information.
- the terminal device can report event-driven beam management information based on the SR resource configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
- the delay of beam management is effectively reduced according to the configuration of the network equipment. Reduces signaling overhead and improves network coverage.
- An embodiment of the present application provides a configuration method for event-driven beam management, which is explained from the side of the network device. This method is the processing on the network device side corresponding to the method of the embodiment of the first aspect, and the content that is the same as the embodiment of the first aspect is not repeated.
- FIG6 is a schematic diagram of a configuration method for event-driven beam management according to an embodiment of the present application. As shown in FIG6 , the method includes:
- the network device receives event-driven beam management information sent by the terminal device.
- FIG6 above is only a schematic illustration of the embodiment of the present application, and the present application is not limited thereto.
- other operations may be added or some operations may be reduced.
- Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG6 above.
- the network device may also receive scheduling request information sent by the terminal device, and send uplink scheduling authorization information to the terminal device, and the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting.
- the terminal device can send a CSI report containing the above-mentioned event-driven beam management information to the terminal device according to the above-mentioned CSI reporting configuration information.
- the network device can receive a CSI report containing the above-mentioned event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
- the network device can also receive event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
- the network device may further receive scheduling request information sent by the terminal device and send uplink scheduling authorization information to the terminal device.
- the terminal device may send the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information.
- the network device may receive the above-mentioned event-driven beam management information sent by the terminal device on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
- the delay of beam management is effectively reduced, the signaling overhead is reduced, and the network coverage is improved through the configuration of network equipment.
- the embodiment of the present application provides an event-driven beam management device.
- the device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device.
- the contents that are the same as those in the first and second aspects are not repeated here.
- FIG7 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application.
- the event-driven beam management device 700 according to an embodiment of the present application includes:
- a receiving unit 710 configured to receive configuration information sent by a network device, the configuration information including CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
- a sending unit 720 sends event-driven beam management information according to the CSI reporting configuration information and/or the SR resource configuration information.
- the sending unit 720 sends event-driven beam management information according to the above-mentioned CSI reporting configuration information and the above-mentioned SR resource configuration information.
- the sending unit 720 when the terminal device detects a beam management event, sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management in the above SR resource configuration information; the receiving unit 710 receives the uplink scheduling authorization information sent by the network device, and the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting; the sending unit 720 sends a CSI report on the PUSCH scheduled by the above uplink scheduling authorization information according to the above CSI reporting configuration information, and the CSI report includes the above event-driven beam management information.
- SR scheduling request
- the reporting type (reportConfigType) of the CSI reporting configuration information is aperiodic.
- the SR resource configuration information may be included in the information element PUCCH-Config.
- the SR resource configuration information is a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust SR resources related to event-driven beam management.
- the list element in the SR resource configuration information is SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
- SchedulingRequestResourceConfigExt-EventBM may further include a switch field (eventBeamManagementFlag) for indicating whether to use event-driven beam management and/or a field indicating priority (phy-PriorityIndex).
- EventBeamManagementFlag indicating whether to use event-driven beam management
- phy-PriorityIndex indicating priority
- the uplink scheduling grant information may be carried by DCI format 0_1, DCI format 0_2, or DCI format 0_3.
- the uplink scheduling grant information may further include a CSI request field, and the CSI request field is used to trigger aperiodic CSI reporting.
- the PUSCH scheduled by the uplink scheduling grant information can carry the above CSI reporting (including event-driven beam management information).
- the PUSCH scheduled by the uplink scheduling grant information may also carry an uplink shared channel (UL-SCH).
- UL-SCH uplink shared channel
- the sending unit 720 sends event-driven beam management information according to the above-mentioned CSI reporting configuration information.
- the reporting type (reportConfigType) of the above CSI reporting configuration information is periodic (periodic) or semi-persistent (semiPersistentOnPUCCH or semiPersistentOnPUSCH).
- the CSI reporting configuration information may include a first field, where the first field is used to indicate that the CSI reporting configuration information is used for event-driven beam management.
- the CSI reporting configuration information may be the information element CSI-ReportConfig
- the first field may be eventBeamManagementFlag
- the first field may be a switch field.
- the CSI reporting configuration information may include a second field, the value of the second field includes a first reporting option, and the first reporting option is used for event-driven beam management.
- the CSI reporting configuration may be the information element CSI-ReportConfig
- the second field may be reportQuantity
- the first reporting option may be the field EventBMInfo.
- the field EventBMInfo is in list form, and the list content is zero to multiple candidate beam information.
- the terminal device may send event-driven beam management information according to the CSI reporting configuration information when the above CSI reporting configuration information is effective or activated.
- the sending unit 720 sends an event-driven wave according to the above SR resource configuration information. Bundle management information.
- the sending unit 720 when the terminal device detects a beam management event, sends a scheduling request (SR) information to the network device on a dedicated SR resource whose SR resource configuration information is event-driven beam management configuration; the receiving unit 710 receives the uplink scheduling authorization information sent by the network device; the sending unit 720 sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information.
- SR scheduling request
- the SR resource configuration information may be included in the information element PUCCH-Config.
- the list element in the SR resource configuration information may be SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
- the PUSCH scheduled by the uplink scheduling grant information may carry the UL-SCH, which includes the above event-driven beam management information.
- the value of the UL-SCH indicator field in the uplink scheduling authorization information is 1.
- the present application also provides an event-driven beam management configuration device.
- the device can be, for example, a network device, or one or more components or assemblies configured on the network device. The same contents as those in the first and second aspects are not repeated here.
- FIG8 is a schematic diagram of a configuration device for event-driven beam management according to an embodiment of the present application.
- the configuration device 800 for event-driven beam management according to an embodiment of the present application includes:
- a sending unit 810 configured to send configuration information to a terminal device, the configuration information including CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
- the receiving unit 820 receives event-driven beam management information sent by the terminal device.
- the receiving unit 820 may further receive the scheduling request information sent by the terminal device, and the sending unit 810 may further send an uplink scheduling request to the terminal device.
- Authorization information, the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting, and the receiving unit 820 can also receive the CSI report containing the above-mentioned event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
- the receiving unit 820 may also receive event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
- the receiving unit 820 can also receive scheduling request information sent by the terminal device, the sending unit 810 can also send uplink scheduling authorization information to the terminal device, and the receiving unit 820 can also receive the above-mentioned event-driven beam management information sent by the terminal device on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
- Apparatuses 700 and 800 may also include other components or modules, and for details of these components or modules, reference may be made to related art.
- Figures 7 and 8 only illustrate the connection relationships or signal paths between various components or modules.
- various related technologies such as bus connections can be used.
- the above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.
- the delay of beam management is effectively reduced, the signaling overhead is reduced, and the network coverage is improved.
- An embodiment of the present application also provides a communication system, which includes a network device and a terminal device.
- FIG9 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example.
- a communication system 900 may include a network device 901 and terminal devices 902 and 903.
- FIG9 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.
- existing services or future services can be sent between the network device 901 and the terminal devices 902 and 903.
- these services may include but are not limited to: enhanced mobile broadband (eMBB, enhanced Mobile Broadband), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), etc.
- eMBB enhanced mobile broadband
- mMTC massive Machine Type Communication
- URLLC Ultra-Reliable and Low-Latency Communication
- Figure 9 shows that both terminal devices 902 and 903 are within the coverage range of network device 901, but the present application is not limited thereto. Both terminal devices 902 and 903 may not be within the coverage range of network device 901, or one terminal device 902 may be within the coverage range of network device 901 while the other terminal device 903 is outside the coverage range of network device 901.
- the terminal device includes the apparatus 700 described in the embodiment of the second aspect, and is configured to perform the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.
- the network device includes the apparatus 800 described in the embodiment of the second aspect, and is configured to perform the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.
- An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other devices.
- a terminal device which may be, for example, a UE, but the present application is not limited thereto and may also be other devices.
- FIG 10 is a schematic diagram of a terminal device according to an embodiment of the present application.
- terminal device 1000 may include a processor 1010 and a memory 1020.
- Memory 1020 stores data and programs and is coupled to processor 1010. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.
- the processor 1010 may be configured to execute a program to implement the method described in the embodiment of the first aspect.
- the terminal device 1000 may further include: a communication module 1030, an input unit 1040, a display 1050, and a power supply 1060.
- the functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all of the components shown in Figure 10 , and these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10 , for which reference may be made to the prior art.
- An embodiment of the present application further provides a network device, which may be, for example, a gNB, but the present application is not limited thereto and may also be other network devices.
- a network device which may be, for example, a gNB, but the present application is not limited thereto and may also be other network devices.
- FIG11 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
- the network device 1100 may include: a processor 1110 (e.g., a central processing unit (CPU)) and a memory 1120; the memory 1120 is coupled to the processor 1110.
- the memory 1120 may store various data; in addition, it may store an information processing program 1130, and The program 1130 is executed under the control of the processor 1110 .
- the processor 1110 may be configured to execute a program to implement the method as described in the embodiment of the second aspect.
- the network device 1100 may further include: a transceiver 1140 and an antenna 1150, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the network device 1100 does not necessarily include all the components shown in FIG11 ; in addition, the network device 1100 may also include components not shown in FIG11 , and reference may be made to the prior art for details.
- An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.
- An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.
- An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.
- An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.
- the above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software.
- the present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above.
- the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
- the method/device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
- one or more of the functional block diagrams shown in the figure and/or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules.
- These software modules can respectively correspond to the various steps shown in the figure.
- These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
- FPGA field programmable gate array
- the software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
- a storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor.
- the processor and the storage medium may be located in an ASIC.
- the software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal.
- the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device. In the device.
- a terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method:
- configuration information sent by a network device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
- a network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method:
- configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
本申请实施例涉及通信技术领域。The embodiments of the present application relate to the field of communication technologies.
高频段毫米波通信是5G NR(第五代新无线)的重要技术方向之一。相对于低频段通信,例如6GHz以下频段的通信,高频段通信会面临传输路径损耗大、传输路径易受遮挡等挑战。为克服这些挑战,发送端会使用大量密集分布的天线单元,通过波束赋形(beamforming)所形成的指向特定方向的波束(beam)来提高覆盖范围;与之对应的是接收端通过波束赋形来接收特定方向的波束。这就需要发送端选择合适的发送波束,接收端选择合适的接收波束,形成波束对(beam pair),联合起来保持良好的无线链路。波束管理(Beam Management,BM)可以建立和维护这样的波束对。High-frequency millimeter-wave communication is one of the key technical directions of 5G NR (fifth-generation new wireless). Compared to low-frequency communications, such as those below 6 GHz, high-frequency communications face challenges such as high transmission path loss and susceptibility to obstruction. To overcome these challenges, the transmitter uses a large number of densely distributed antenna units, using beamforming to form beams pointing in specific directions to improve coverage. Correspondingly, the receiver uses beamforming to receive beams in specific directions. This requires the transmitter to select an appropriate transmit beam and the receiver to select an appropriate receive beam to form a beam pair, which together maintain a good wireless link. Beam Management (BM) can establish and maintain such beam pairs.
传统通信系统(3GPP Rel-15~Rel-18,第三代合作伙伴计划的版本15至版本18)中的波束管理主要由基站发起,基站为终端配置用于波束管理的参考信号(Reference Signal,RS),终端上报测量结果,基站根据终端的测量结果决定是否发起波束管理,并发送相关信令(signaling),基站根据信令执行相应的波束管理操作。这种波束管理的信令开销大,延时长,灵活性受到很大限制。In traditional communication systems (3GPP Rel-15 to Rel-18), beam management is primarily initiated by the base station. The base station configures a reference signal (RS) for beam management for the terminal. The terminal then reports its measurement results. The base station then decides whether to initiate beam management based on these measurements and sends relevant signaling. The base station then performs the corresponding beam management operations based on the signaling. This type of beam management results in high signaling overhead, long latency, and significantly limited flexibility.
应该注意,上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明,并方便本领域技术人员的理解而阐述的,不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.
发明内容Summary of the Invention
发明人发现,在3GPP Rel-19中,由UE(称为用户设备,终端设备,终端,用户等)发起的(UE-initiated)或事件驱动(event-driven)的波束管理(下文统一称之为事件驱动的波束管理)已经被确定为立项内容之一。在UE发起的波束管理中,UE可监测下行波束质量,当监测到波束管理有关的事件(event)时,可向基站主动发起波束管理(如波束切换)请求,可以有效降低波束管理的时延、降低信令开销、改善网络覆盖。目前,关于事件驱动的波束管理的标准化工作尚未开始。因此,如何上报事件驱动的波 束管理事件以及具体的上报内容等,成为亟待解决的问题。The inventors found that in 3GPP Rel-19, UE-initiated or event-driven beam management (hereinafter referred to as event-driven beam management) initiated by UE (called user equipment, terminal equipment, terminal, user, etc.) has been identified as one of the project contents. In the beam management initiated by UE, the UE can monitor the downlink beam quality. When an event related to beam management is detected, it can actively initiate a beam management (such as beam switching) request to the base station, which can effectively reduce the delay of beam management, reduce signaling overhead, and improve network coverage. At present, the standardization work on event-driven beam management has not yet begun. Therefore, how to report event-driven beam management is a key issue. Bundle management events and specific reporting content have become issues that need to be urgently addressed.
针对上述问题的至少之一或其他类似问题,本申请实施例提供一种事件驱动的波束管理方法和装置,以降低波束管理的时延、降低信令开销、改善网络覆盖。In response to at least one of the above problems or other similar problems, an embodiment of the present application provides an event-driven beam management method and device to reduce the latency of beam management, reduce signaling overhead, and improve network coverage.
根据本申请实施例的一个方面,提供一种事件驱动的波束管理方法,所述方法包括:According to one aspect of an embodiment of the present application, an event-driven beam management method is provided, the method comprising:
终端设备接收网络设备发送的配置信息,所述配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;The terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
所述终端设备根据所述CSI上报配置信息和/或所述SR资源配置信息,发送事件驱动的波束管理信息。The terminal device sends event-driven beam management information based on the CSI reporting configuration information and/or the SR resource configuration information.
在一些实施例中,上述配置信息包括上述CSI上报配置信息和上述SR资源配置信息,终端设备在检测到波束管理事件时,在上述SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息,并接收网络设备发送的上行调度授权信息,根据上述CSI上报配置信息,发送CSI上报,该CSI上报包括上述事件驱动的波束管理信息。In some embodiments, the above-mentioned configuration information includes the above-mentioned CSI reporting configuration information and the above-mentioned SR resource configuration information. When the terminal device detects a beam management event, the terminal device sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management in the above-mentioned SR resource configuration information, and receives the uplink scheduling authorization information sent by the network device. According to the above-mentioned CSI reporting configuration information, the terminal device sends a CSI report, which includes the above-mentioned event-driven beam management information.
在另一些实施例中,上述配置信息包括上述CSI上报配置信息,终端设备根据上述CSI上报配置信息发送上述事件驱动波束管理信息。In other embodiments, the above-mentioned configuration information includes the above-mentioned CSI reporting configuration information, and the terminal device sends the above-mentioned event-driven beam management information according to the above-mentioned CSI reporting configuration information.
在又一些实施例中,上述配置信息包括上述SR资源配置信息,终端设备在检测到波束管理事件时,在上述SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息,并接收网络设备发送的上行调度授权信息,在该上行调度授权信息所调度的PUSCH上发送上述事件驱动的波束管理信息。In some further embodiments, the above-mentioned configuration information includes the above-mentioned SR resource configuration information. When the terminal device detects a beam management event, it sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management according to the above-mentioned SR resource configuration information, and receives the uplink scheduling authorization information sent by the network device, and sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information.
本申请实施例的有益效果之一在于:根据本申请实施例,通过上行控制信息上报事件驱动的波束管理信息(例如事件驱动的波束切换信息),可有效降低波束管理的时延、降低信令开销、改善网络覆盖。One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, by reporting event-driven beam management information (such as event-driven beam switching information) through uplink control information, the delay of beam management can be effectively reduced, the signaling overhead can be reduced, and the network coverage can be improved.
参照后文的说明和附图,详细公开了本申请的特定实施方式,指明了本申请的原理可以被采用的方式。应该理解,本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内,本申请的实施方式包括许多改变、修改和等同。With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用,与其它实施方式中的特征相组合,或替代其它实施方式中的特征。Features described and/or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.
应该强调,术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在,但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。 It should be emphasized that the term "include/comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components.
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外,在附图中,类似的标号表示几个附图中对应的部件,并可用于指示多于一种实施方式中使用的对应部件。The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.
图1是本申请实施例的事件驱动的波束管理方法的一示意图;FIG1 is a schematic diagram of an event-driven beam management method according to an embodiment of the present application;
图2是终端设备根据CSI上报配置信息和SR资源配置信息发送事件驱动的波束管理信息的一示意图;FIG2 is a schematic diagram of a terminal device sending event-driven beam management information according to CSI reporting configuration information and SR resource configuration information;
图3是终端设备根据CSI上报配置信息发送事件驱动的波束管理信息的一示意图;FIG3 is a schematic diagram of a terminal device sending event-driven beam management information according to CSI reporting configuration information;
图4是终端设备上报事件驱动的波束管理信息的一示意图;FIG4 is a schematic diagram of a terminal device reporting event-driven beam management information;
图5是终端设备根据SR资源配置信息发送事件驱动的波束管理信息的一示意图;FIG5 is a schematic diagram of a terminal device sending event-driven beam management information according to SR resource configuration information;
图6是本申请实施例的事件驱动的波束管理的配置方法的一示意图;FIG6 is a schematic diagram of a configuration method of event-driven beam management according to an embodiment of the present application;
图7是本申请实施例的事件驱动的波束管理装置的一示意图;FIG7 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application;
图8是本申请实施例的事件驱动的波束管理的配置装置的一示意图;FIG8 is a schematic diagram of a configuration device for event-driven beam management according to an embodiment of the present application;
图9是本申请实施例的通信系统的示意图;FIG9 is a schematic diagram of a communication system according to an embodiment of the present application;
图10是本申请实施例的终端设备的构成示意图;FIG10 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application;
图11是本申请实施例的网络设备的构成示意图。FIG11 is a schematic diagram of the structure of a network device according to an embodiment of the present application.
参照附图,通过下面的说明书,本申请的前述以及其它特征将变得明显。在说明书和附图中,具体公开了本申请的特定实施方式,其表明了其中可以采用本申请的原则的部分实施方式,应了解的是,本申请不限于所描述的实施方式,相反,本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.
在本申请实施例中,术语“第一”、“第二”等用于对不同元素从称谓上进行区分,但并不表示这些元素的空间排列或时间顺序等,这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在,但并不排除存在或添加一个或多个其他特征、元素、元件或组件。In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and/or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.
在本申请实施例中,单数形式“一”、“该”等包括复数形式,应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义;此外术语“所述”应理解为既包括单数形式也包括复数形式,除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”, 术语“基于”应理解为“至少部分基于……”,除非上下文另外明确指出。In the embodiments of the present application, the singular forms "a", "the", etc. include plural forms and should be broadly understood as "a" or "a type" rather than being limited to the meaning of "one"; in addition, the term "the" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. In addition, the term "according to" should be understood as "at least in part according to...", The term "based on" should be understood to mean "based, at least in part, on..." unless the context clearly dictates otherwise.
在本申请实施例中,术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络,例如长期演进(LTE,Long Term Evolution)、增强的长期演进(LTE-A,LTE-Advanced)、宽带码分多址接入(WCDMA,Wideband Code Division Multiple Access)、高速报文接入(HSPA,High-Speed Packet Access)、5G(5Generation)新无线(NR,New Radio)等等。In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), 5G (5Generation) New Radio (NR), etc.
并且,通信系统中设备之间的通信可以根据任意阶段的通信协议进行,例如可以包括但不限于如下通信协议:1G、2G、2.5G、2.75G、3G、4G、4.5G以及5G新无线等等,和/或其他目前已知或未来将被开发的通信协议。Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example including but not limited to the following communication protocols: 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G new wireless, etc., and/or other communication protocols currently known or to be developed in the future.
在本申请实施例中,术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备:基站(BS,Base Station)、接入点(AP、Access Point)、发送接收点(TRP,Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC,Radio Network Controller)、基站控制器(BSC,Base Station Controller)等等。In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services for the terminal device. Network devices may include, but are not limited to, base stations (BS), access points (AP), transmission reception points (TRP), broadcast transmitters, mobile management entities (MME), gateways, servers, radio network controllers (RNC), base station controllers (BSC), and the like.
其中,基站可以包括但不限于:节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB),等等,此外还可包括远端无线头(RRH,Remote Radio Head)、远端无线单元(RRU,Remote Radio Unit)、中继(relay)或者低功率节点(例如femeto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能,每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域,这取决于使用该术语的上下文。Among them, base stations may include but are not limited to: NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB), and 5G base station (gNB), etc., and may also include remote radio heads (RRH, Remote Radio Head), remote radio units (RRU, Remote Radio Unit), relays or low-power nodes (such as femeto, pico, etc.). The term "base station" can include some or all of their functions. Each base station can provide communication coverage for a specific geographical area. The term "cell" can refer to a base station and/or its coverage area, depending on the context in which the term is used.
在本申请实施例中,术语“用户设备”(UE,User Equipment)或者“终端设备”(TE,Terminal Equipment或Terminal Device)例如是指通过网络设备接入通信网络并接收网络服务的设备。终端设备可以是固定的或移动的,并且也可以称为移动台(MS,Mobile Station)、终端、用户台(SS,Subscriber Station)、接入终端(AT,Access Terminal)、站,等等。In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.
其中,终端设备可以包括但不限于如下设备:蜂窝电话(Cellular Phone)、个人数字助理(PDA,Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机,等等。Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.
再例如,在物联网(IoT,Internet of Things)等场景下,终端设备还可以是进行监 控或测量的机器或装置,例如可以包括但不限于:机器类通信(MTC,Machine Type Communication)终端、车载通信终端、设备到设备(D2D,Device to Device)终端、机器到机器(M2M,Machine to Machine)终端,等等。For example, in scenarios such as the Internet of Things (IoT), terminal devices can also monitor The machines or devices for control or measurement may include, but are not limited to, machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and the like.
此外,术语“网络侧”或“网络设备侧”是指网络的一侧,可以是某一基站,也可以包括如上的一个或多个网络设备。术语“用户侧”或“终端侧”或“终端设备侧”是指用户或终端的一侧,可以是某一UE,也可以包括如上的一个或多个终端设备。本文在没有特别指出的情况下,“设备”可以指网络设备,也可以指终端设备。In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.
为了方便理解,下面对本申请实施例涉及的一些概念进行说明。To facilitate understanding, some concepts involved in the embodiments of this application are explained below.
在本申请实施例中,上行控制信息(Uplink Control Iniformation,UCI),主要包括混合自动请求确认(HARQ-ACK,Hybrid Automatic Repeat Request Acknowledgement)、调度请求(Scheduling Request,SR)、信道状态信息(Channel State Information,CSI)等。上行控制信息可在物理上行控制信道(Physical uplink control channel,PUCCH)或物理上行共享信道(Physical downlink shared channel,PUSCH)上传输。In the embodiments of the present application, uplink control information (UCI) mainly includes Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK), Scheduling Request (SR), Channel State Information (CSI), etc. Uplink control information can be transmitted on the Physical Uplink Control Channel (PUCCH) or the Physical Downlink Shared Channel (PUSCH).
SR是UCI的一种,由UE通过PUCCH向gNB发送,用于向网络侧请求上行资源。RRC(无线资源控制)中会预先配置专用的周期性PUCCH资源,UE使用这些资源在PUCCH上发送SR。RRC信元(Information Element,IE)SchedulingRequestConfig可配置SR的参数,SR对应的物理层资源在PUCCH-Config中的字段schedulingRequestResourceToAddModList或字段schedulingRequestResourceToAddModListExt中配置。上述两个字段是列表形式,列表元素为SR资源配置SchedulingRequestResourceConfig。SR is a type of UCI sent by the UE to the gNB via the PUCCH to request uplink resources from the network. Radio Resource Control (RRC) pre-configures dedicated periodic PUCCH resources, which the UE uses to send SRs on the PUCCH. The RRC Information Element (IE) SchedulingRequestConfig configures SR parameters. The physical layer resources corresponding to the SR are configured in the schedulingRequestResourceToAddModList or schedulingRequestResourceToAddModListExt fields in PUCCH-Config. These two fields are lists, with the list elements representing the SR resource configuration, SchedulingRequestResourceConfig.
CSI也是UCI的一种,UE以CSI上报(CSI report)的形式将CSI反馈给基站,可为基站提供传输所需参数。CSI上报的相关资源由高层参数CSI-ReportConfig配置,具体的CSI上报内容由CSI-ReportConfig中的字段reportQuantity配置。比如reportQuantity可配置为:CSI is also a type of UCI. The UE feeds back CSI to the base station in the form of CSI report, which can provide the base station with the parameters required for transmission. The relevant resources for CSI reporting are configured by the high-level parameter CSI-ReportConfig, and the specific CSI reporting content is configured by the reportQuantity field in CSI-ReportConfig. For example, reportQuantity can be configured as:
●‘cri-RSRP’,反馈内容包括CSI-RS资源指示(CSI-RS Resource Indicator,CRI)和层1参考信号接收功率(Layer 1Reference Signal Receiving Power,L1-RSRP),分别为波束的索引信息和波束的质量信息,可用于基于CSI-RS的波束管理;'cri-RSRP', which provides feedback including the CSI-RS Resource Indicator (CRI) and Layer 1 Reference Signal Received Power (L1-RSRP), which represent beam index information and beam quality information, respectively, and can be used for CSI-RS-based beam management.
●‘ssb-Index-RSRP’,反馈内容包括同步信号块资源指示(Synchronization Singal Block Resource Indicator,SSBRI)和L1-RSRP,分别为波束的索引信息和波束的质量信息,可用于基于SSB的波束管理; 'ssb-Index-RSRP': This feedback includes the synchronization signal block resource indicator (SSBRI) and L1-RSRP, which are beam index information and beam quality information, respectively. This can be used for SSB-based beam management.
●等等。●And so on.
目前,协议中并不包括与事件驱动的波束管理相关的上报内容。若引入事件驱动的波束管理,UE会按照特定准则检测需要发起波束管理的事件(event),这里的波束管理至少包括波束切换,具体准则内容在本申请中不做限制。为了方便说明,下文将与波束管理相关的事件(包括波束切换事件)统称为“波束管理事件”,在本申请实施例中,以“波束切换事件”为例进行说明。Currently, the protocol does not include reporting content related to event-driven beam management. If event-driven beam management is introduced, the UE will detect events (events) that require initiation of beam management according to specific criteria. The beam management here includes at least beam switching. The specific criteria are not limited in this application. For the sake of convenience, events related to beam management (including beam switching events) are collectively referred to as "beam management events" below. In the embodiments of this application, "beam switching events" are used as an example for explanation.
在检测到波束切换事件以后,UE可以主动上报该事件和其他跟波束切换有关的信息,比如可选地包括如下关于新波束(待选的目标波束,也即候选波束)信息中的一种或多种:After detecting a beam switching event, the UE may proactively report the event and other information related to the beam switching, such as one or more of the following information about the new beam (the target beam to be selected, also known as the candidate beam):
●CRI/SSBRI信息;CRI/SSBRI information;
●L1-RSRP/L1-SINR(Layer 1Signal Interference Noise Ratio,层1信干噪比)信息;L1-RSRP/L1-SINR (Layer 1 Signal Interference Noise Ratio) information;
●物理小区标识(Physical cell ID)信息;Physical cell ID information;
●传输配置指示状态标识(unified Transmission Configuration Indication State ID,TCI-StateId);●Transmission configuration indication state ID (unified Transmission Configuration Indication State ID, TCI-StateId);
●等等。●And so on.
为了方便说明,下文将这些信息统称为“波束切换信息”。值得注意的是,该波束切换信息可以属于CSI,即可以作为CSI的一种,但本申请不限于此,该波束切换信息也可以不属于CSI。For ease of explanation, this information is collectively referred to as “beam switching information” below. It is worth noting that the beam switching information may belong to CSI, that is, may be a type of CSI, but the present application is not limited thereto, and the beam switching information may not belong to CSI.
此外,当前协议中也不包括如何上报事件驱动的波束切换事件和波束切换信息,UE可能通过不同途径上报波束切换事件和波束切换信息,比如可通过MAC-CE(媒体接入控制控制元素)上报,可通过UCI上报,等等。In addition, the current protocol does not include how to report event-driven beam switching events and beam switching information. The UE may report beam switching events and beam switching information through different channels, such as through MAC-CE (Media Access Control Element), through UCI, and so on.
下面结合附图和具体实施方式对本申请实施例进行说明。The embodiments of the present application are described below with reference to the accompanying drawings and specific implementation methods.
第一方面的实施例Embodiments of the first aspect
本申请实施例提供一种事件驱动的波束管理方法,从终端设备的一侧进行说明。An embodiment of the present application provides an event-driven beam management method, which is described from the perspective of a terminal device.
图1是本申请实施例的事件驱动的波束管理方法的一示意图,如图1所示,该方法包括:FIG1 is a schematic diagram of an event-driven beam management method according to an embodiment of the present application. As shown in FIG1 , the method includes:
110,终端设备接收网络设备发送的配置信息,该配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息; 110. The terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management.
120,终端设备根据上述CSI上报配置信息和/或上述SR资源配置信息,发送事件驱动的波束管理信息。120. The terminal device sends event-driven beam management information according to the above-mentioned CSI reporting configuration information and/or the above-mentioned SR resource configuration information.
值得注意的是,以上附图1仅对本申请实施例进行了示意性说明,但本申请不限于此。例如可以增加其他的一些操作或者减少其中的某些操作,此外,还可以调整上述操作的对象。本领域的技术人员可以根据上述内容进行适当地变型,而不仅限于上述附图1的记载。It is worth noting that FIG1 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced, and the objects of the above operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG1 above.
根据本申请实施例,通过UCI上报事件驱动的波束管理信息(例如波束切换信息),有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to an embodiment of the present application, by reporting event-driven beam management information (such as beam switching information) through UCI, the delay of beam management is effectively reduced, the signaling overhead is reduced, and the network coverage is improved.
在上述实施例中,关于事件驱动的波束切换信息已经在前面做了说明,此处不再赘述。In the above embodiment, the event-driven beam switching information has been described above and will not be repeated here.
在一些实施例中,在操作120中,终端设备接根据上述CSI上报配置信息和SR资源配置信息发送上述事件驱动的波束管理信息。图2是该实施例的一示意图,如图2所示,该方法包括:In some embodiments, in operation 120, the terminal device sends the event-driven beam management information according to the CSI reporting configuration information and the SR resource configuration information. FIG2 is a schematic diagram of this embodiment. As shown in FIG2, the method includes:
210:终端设备接收网络设备发送的配置信息,该配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和SR资源配置信息;210: The terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information and SR resource configuration information associated with event-driven beam management.
220:终端设备在检测到波束管理事件时,在上述SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息;220: When the terminal device detects a beam management event, it sends a scheduling request (SR) message to the network device on the dedicated SR resource configured for event-driven beam management.
230:终端设备接收网络设备发送的上行调度授权信息,该上行调度授权信息能够用于触发非周期CSI上报;230: The terminal device receives uplink scheduling grant information sent by the network device. The uplink scheduling grant information can be used to trigger aperiodic CSI reporting.
240:终端设备根据上述CSI上报配置信息,在所述上行调度授权信息所调度的PUSCH上发送CSI上报,该CSI上报包括上述事件驱动的波束管理信息。240: The terminal device sends a CSI report on the PUSCH scheduled by the uplink scheduling authorization information according to the above CSI reporting configuration information, and the CSI report includes the above event-driven beam management information.
在上述实施例中,CSI上报配置信息例如为信元CSI-ReportConfig,可选的,其时域特性也即上报类型(reportConfigType)为非周期性的(aperiodic),终端设备可以在接收到网络设备发送的上述上行调度授权信息后,根据该CSI上报配置信息发送包含上述事件驱动的波束管理信息的CSI上报。In the above embodiment, the CSI reporting configuration information is, for example, a signal element CSI-ReportConfig. Optionally, its time domain characteristic, that is, the reporting type (reportConfigType), is aperiodic. After receiving the above uplink scheduling authorization information sent by the network device, the terminal device can send a CSI report containing the above event-driven beam management information according to the CSI reporting configuration information.
在上述实施例中,SR资源配置信息可以包含于信元PUCCH-Config中,例如可以在该信元PUCCH-Config中增加新的字段(field)来配置与事件驱动的波束管理关联的该SR资源配置信息。In the above embodiment, the SR resource configuration information may be included in the information element PUCCH-Config. For example, a new field may be added to the information element PUCCH-Config to configure the SR resource configuration information associated with event-driven beam management.
例如,该SR资源配置信息可以为列表schedulingRequestResourceToAddModListExt-EventBM,用于增加或调整与事件驱动的波 束管理有关的SR资源。该SR资源配置信息中的列表元素可以是SchedulingRequestResourceConfigExt-EventBM,用于配置与事件驱动的波束管理有关的SR资源。For example, the SR resource configuration information may be a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust event-driven wave The list element in the SR resource configuration information may be SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
在上述实施例中,该SchedulingRequestResourceConfigExt-EventBM可以包括用于指示是否用作事件驱动的波束管理的开关字段。例如该开关字段称为eventBeamManagementFlag,其取值只有一个,例如称为“enabled”;如果配置了该开关字段eventBeamManagementFlag,表示当前SR资源用于事件驱动的波束管理。In the above embodiment, the SchedulingRequestResourceConfigExt-EventBM may include a switch field for indicating whether event-driven beam management is used. For example, this switch field is called eventBeamManagementFlag and has a single value, such as "enabled." If this switch field is configured, it indicates that the current SR resource is used for event-driven beam management.
在上述实施例中,该SchedulingRequestResourceConfigExt-EventBM还可以包括表示优先级的字段。例如称为phy-PriorityIndex,其取值例如可以是p0,p1,p2中的任意一个,对应的优先级从高到低是p2>p1>p0;如果未配置该字段,默认优先级为p0,即优先级最低。In the above embodiment, the SchedulingRequestResourceConfigExt-EventBM may also include a field indicating priority, such as phy-PriorityIndex, whose value can be any one of p0, p1, and p2, with the corresponding priorities from high to low being p2>p1>p0. If this field is not configured, the default priority is p0, which is the lowest priority.
下面是根据上述实施例的该SR资源配置信息的一个示例:
The following is an example of the SR resource configuration information according to the above embodiment:
值得注意的是,以上只是举例说明,在上述实施例中,该SR资源配置信息也可以是其他形式,或者称为其他,该SR资源配置信息所包含的上述开关字段和/或表示优先级的字段也可以称为其他,不限于上述示例中的举例。It is worth noting that the above is just an example. In the above embodiment, the SR resource configuration information may also be in other forms, or called other. The above switch field and/or the field indicating the priority contained in the SR resource configuration information may also be called other, and is not limited to the examples in the above example.
在上述实施例中,在操作220中,终端设备在检测到波束管理事件时,其可以向网络设备发送上述SR信息,该SR信息可以由上述RRC资源配置信息为事件驱动的波束管理配置的专用SR资源承载,用于告知网络设备该SR信息用于事件驱动的波束管理。In the above embodiment, in operation 220, when the terminal device detects a beam management event, it can send the above SR information to the network device. The SR information can be carried by the dedicated SR resources configured for event-driven beam management by the above RRC resource configuration information, so as to inform the network device that the SR information is used for event-driven beam management.
在上述实施例中,在操作230中,终端设备可以接收网络设备发送的上行调度授权信息,该上行调度授权信息用于调度PUSCH,可以由DCI(下行控制信息)格式0_1或DCI格式0_2或DCI格式0_3(DCI format 0_1/0_2/0_3)承载。In the above embodiment, in operation 230, the terminal device can receive uplink scheduling authorization information sent by the network device. The uplink scheduling authorization information is used to schedule PUSCH and can be carried by DCI (downlink control information) format 0_1 or DCI format 0_2 or DCI format 0_3 (DCI format 0_1/0_2/0_3).
在上述实施例中,该上行调度授权信息还需要包括CSI请求字段,该CSI请求字段 用于触发非周期CSI上报。In the above embodiment, the uplink scheduling grant information also needs to include a CSI request field. Used to trigger aperiodic CSI reporting.
在上述实施例中,在操作240中,终端设备在收到网络设备发送的上述上行调度授权信息之后,可以根据上述CSI上报配置信息,在上述上行调度授权信息调度的PUSCH上发送CSI上报,该CSI上报包含了上述事件驱动的波束管理信息。In the above embodiment, in operation 240, after receiving the above uplink scheduling authorization information sent by the network device, the terminal device can send a CSI report on the PUSCH scheduled by the above uplink scheduling authorization information according to the above CSI reporting configuration information, and the CSI report includes the above event-driven beam management information.
在上述实施例中,上述上行调度授权信息调度的PUSCH可以承载上行控制信息(UCI),该UCI为上述CSI上报,包含了事件驱动的波束管理信息。例如,该上行调度授权信息中的UL-SCH indicator字段设置为0,被调度的PUSCH仅承载上述UCI(CSI上报)。In the above embodiment, the PUSCH scheduled by the uplink scheduling grant information may carry uplink control information (UCI), which is the CSI reporting described above and includes event-driven beam management information. For example, if the UL-SCH indicator field in the uplink scheduling grant information is set to 0, the scheduled PUSCH only carries the UCI (CSI reporting).
本申请不限于此,该上行调度授权信息调度的PUSCH还可以承载上行共享信道(UL-SCH)。例如,该上行调度授权信息中的UL-SCH indicator字段设置为1,则被调度的PUSCH上除了承载UL-SCH,还承载上述UCI(CSI上报),即该UCI(CSI上报)复用(multiplex)在上述PUSCH上。The present application is not limited thereto. The PUSCH scheduled by the uplink scheduling grant information may also carry an uplink shared channel (UL-SCH). For example, if the UL-SCH indicator field in the uplink scheduling grant information is set to 1, the scheduled PUSCH not only carries the UL-SCH but also carries the UCI (CSI reporting), i.e., the UCI (CSI reporting) is multiplexed on the PUSCH.
根据上述实施例,终端设备可以根据CSI上报配置信息和SR资源配置信息上报事件驱动的波束管理信息,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to the above embodiment, the terminal device can report event-driven beam management information based on the CSI reporting configuration information and SR resource configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
在另一些实施例中,在操作120中,终端设备根据上述CSI上报配置信息发送事件驱动的波束管理信息。图3是该实施例的一示意图,如图3所示,该方法包括:In some other embodiments, in operation 120, the terminal device sends event-driven beam management information according to the above CSI reporting configuration information. FIG3 is a schematic diagram of this embodiment. As shown in FIG3, the method includes:
310:终端设备接收网络设备发送的配置信息,该配置信息包括与事件驱动的波束管理关联的CSI上报配置信息;310: The terminal device receives configuration information sent by the network device, where the configuration information includes CSI reporting configuration information associated with event-driven beam management.
320:所述终端设备根据所述CSI上报配置信息发送事件驱动的波束管理信息。320: The terminal device sends event-driven beam management information according to the CSI reporting configuration information.
在上述实施例中,该CSI上报配置信息例如为信元CSI-ReportConfig,其时域特性也即上报类型(reportConfigType)是周期性的(periodic)或者是半持续的(semiPersistentOnPUCCH或semiPersistentOnPUSCH)。终端设备根据该CSI上报配置信息在检测到事件驱动的波束管理事件后发送相应的事件驱动的波束管理信息。In the above embodiment, the CSI reporting configuration information is, for example, a symbol CSI-ReportConfig, and its time domain characteristics, i.e., the reporting type (reportConfigType), is periodic (periodic) or semi-persistent (semiPersistentOnPUCCH or semiPersistentOnPUSCH). The terminal device sends corresponding event-driven beam management information after detecting an event-driven beam management event based on the CSI reporting configuration information.
在上述实施例中,可选的,该CSI上报配置信息可以包括第一字段,通过该第一字段来指示该CSI上报配置信息用于事件驱动的波束管理。In the above embodiment, optionally, the CSI reporting configuration information may include a first field, and the first field is used to indicate that the CSI reporting configuration information is used for event-driven beam management.
在上述实施例中,该第一字段可以是CSI-ReportConfig中的新增字段,用于指示用户当前CSI上报配置信息用于上报与事件驱动的波束管理相关的事件和信息。该第一字段例如称为eventBeamManagementFlag,其可以是一个开关字段,取值只有一个,称为“enabled”,如果配置了该字段eventBeamManagementFlag,表示当前CSI-ReportConfig 用于事件驱动的波束管理。In the above embodiment, the first field may be a new field in CSI-ReportConfig, used to indicate that the user's current CSI reporting configuration information is used to report events and information related to event-driven beam management. The first field is called eventBeamManagementFlag, for example, which can be a switch field with only one value, called "enabled". If the field eventBeamManagementFlag is configured, it indicates that the current CSI-ReportConfig For event-driven beam management.
下面是该CSI-ReportConfig所包含的eventBeamManagementFlag的一个示例:
…
eventBeamManagementFlag ENUMERATED{enabled} OPTIONAL,--Need M
…The following is an example of the eventBeamManagementFlag included in the CSI-ReportConfig:
…
eventBeamManagementFlag ENUMERATED{enabled} OPTIONAL,--Need M
…
上述以第一字段称为eventBeamManagementFlag为例,本申请不限于此,该第一字段也可以称为其他,只要能够用于指示该CSI上报配置信息用于事件驱动的波束管理即可。The above takes the first field called eventBeamManagementFlag as an example, but the present application is not limited to this. The first field can also be called other names as long as it can be used to indicate that the CSI reporting configuration information is used for event-driven beam management.
在上述实施例中,可选的,还可以复用CSI-ReportConfig中的已有字段。例如,该CSI上报配置信息包括第二字段,该第二字段的取值中包括第一上报选项,该第一上报选项用于事件驱动的波束管理。In the above embodiment, optionally, existing fields in CSI-ReportConfig may be reused. For example, the CSI reporting configuration information includes a second field, the value of which includes a first reporting option, and the first reporting option is used for event-driven beam management.
在上述实施例中,第二字段例如为CSI-ReportConfig中的已有字段reportQuantity,该第一上报选项例如为字段EventBMInfo,该字段EventBMInfo可以是列表形式,列表内容为零到多个候选波束信息。例如,EventBMInfo的取值为列表(SEQUENCE)形式的newBeamToAddModList,列表的具体内容为零个到多个候选波束信息(NewBeamInfo),最大个数不超过maxNrofNewBeam,候选波束信息的具体内容如前文所述,此处不再赘述。In the above embodiment, the second field is, for example, the existing field reportQuantity in CSI-ReportConfig, and the first reporting option is, for example, the field EventBMInfo. The field EventBMInfo can be in a list format, and the list content is zero to multiple candidate beam information. For example, the value of EventBMInfo is newBeamToAddModList in the form of a list (SEQUENCE), and the specific content of the list is zero to multiple candidate beam information (NewBeamInfo), with the maximum number not exceeding maxNrofNewBeam. The specific content of the candidate beam information is as described above and will not be repeated here.
下面是该CSI-ReportConfig中的已有字段reportQuantity中新增的字段EventBMInfo的一个示例:
The following is an example of adding the new field EventBMInfo to the existing field reportQuantity in the CSI-ReportConfig:
在上述实施例中,在操作320中,终端设备可以在上述CSI上报配置信息生效或者被激活的情况下,根据上述CSI上报配置信息发送事件驱动的波束管理信息。In the above embodiment, in operation 320, the terminal device may send event-driven beam management information according to the above CSI reporting configuration information when the above CSI reporting configuration information is effective or activated.
例如,如图4所示,终端设备接收到专用的周期性的CSI上报配置信息且配置生效,或接收到专用的半持续性的CSI上报配置且通过MAC-CE或DCI激活,则终端设备在符合该CSI上报配置信息要求的某上报时刻(时间T1)上报新波束A、新波束B的信息,在下一个上报时刻(时间T2)上报新波束A、新波束B、新波束C的信息,在接下来的一个上报时刻(时间T3)不上报任何新波束信息,在接下来的一个上报时刻(时 间T4)上报新波束A、新波束C信息……直至终端设备收到新的高层配置,或收到去激活上报“事件驱动的波束管理事件”的信令。For example, as shown in Figure 4, the terminal device receives a dedicated periodic CSI reporting configuration information and the configuration takes effect, or receives a dedicated semi-persistent CSI reporting configuration and is activated through MAC-CE or DCI, then the terminal device reports the information of the new beam A and the new beam B at a reporting time (time T1) that meets the requirements of the CSI reporting configuration information, reports the information of the new beam A, the new beam B, and the new beam C at the next reporting time (time T2), does not report any new beam information at the next reporting time (time T3), and reports the new beam information at the next reporting time (time T4). Time T4) reports the new beam A, new beam C information... until the terminal device receives new high-level configuration, or receives the signaling to activate the reporting of "event-driven beam management events".
根据上述实施例,终端设备可以根据CSI上报配置信息上报事件驱动的波束管理信息,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to the above embodiment, the terminal device can report event-driven beam management information based on the CSI reporting configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
在另一些实施例中,在操作120中,终端设备根据上述SR资源配置信息发送事件驱动的波束管理信息。图5是该实施例的一示意图,如图5所示,该方法包括:In some other embodiments, in operation 120, the terminal device sends event-driven beam management information according to the above SR resource configuration information. FIG5 is a schematic diagram of this embodiment. As shown in FIG5, the method includes:
510:终端设备接收网络设备发送的配置信息,该配置信息包括与事件驱动的波束管理关联的SR资源配置信息;510: The terminal device receives configuration information sent by the network device, where the configuration information includes SR resource configuration information associated with event-driven beam management.
520:终端设备在检测到波束管理事件时,在上述SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息;520: When the terminal device detects a beam management event, it sends a scheduling request (SR) message to the network device on the dedicated SR resource configured for event-driven beam management.
530:终端设备接收网络设备发送的上行调度授权信息;530: The terminal device receives uplink scheduling authorization information sent by the network device;
540:终端设备在所上述上行调度授权信息所调度的PUSCH上,发送上述事件驱动的波束管理信息。540: The terminal device sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
在上述实施例中,SR资源配置信息可以包含于信元PUCCH-Config中,例如可以在该信元PUCCH-Config中增加新的字段(field)来配置与事件驱动的波束管理关联的该SR资源配置信息。In the above embodiment, the SR resource configuration information may be included in the information element PUCCH-Config. For example, a new field may be added to the information element PUCCH-Config to configure the SR resource configuration information associated with event-driven beam management.
例如,该SR资源配置信息可以为列表schedulingRequestResourceToAddModListExt-EventBM,用于增加或调整与事件驱动的波束管理有关的SR资源。该SR资源配置信息中的列表元素可以是SchedulingRequestResourceConfigExt-EventBM,用于配置与事件驱动的波束管理有关的SR资源。For example, the SR resource configuration information may be a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust SR resources related to event-driven beam management. The list element in the SR resource configuration information may be SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
在上述实施例中,该SchedulingRequestResourceConfigExt-EventBM可以包括用于指示是否用作事件驱动的波束管理的开关字段。例如称为eventBeamManagementFlag,其取值只有一个,例如称为“enabled”;如果配置了该开关字段eventBeamManagementFlag,表示当前SR资源用于事件驱动的波束管理。In the above embodiment, the SchedulingRequestResourceConfigExt-EventBM may include a switch field for indicating whether event-driven beam management is used. For example, it is called eventBeamManagementFlag, which has only one value, such as "enabled". If the switch field eventBeamManagementFlag is configured, it indicates that the current SR resource is used for event-driven beam management.
在上述实施例中,该SchedulingRequestResourceConfigExt-EventBM还可以包括表示优先级的字段。例如称为phy-PriorityIndex,其取值例如可以是p0,p1,p2中的任意一个,对应的优先级从高到低是p2>p1>p0;如果未配置该字段,默认优先级为p0,即优先级最低。In the above embodiment, the SchedulingRequestResourceConfigExt-EventBM may also include a field indicating priority, such as phy-PriorityIndex, whose value can be any one of p0, p1, and p2, with the corresponding priorities from high to low being p2>p1>p0. If this field is not configured, the default priority is p0, which is the lowest priority.
下面是根据上述实施例的该SR资源配置信息的一个示例:
The following is an example of the SR resource configuration information according to the above embodiment:
值得注意的是,以上只是举例说明,在上述实施例中,该SR资源配置信息也可以是其他形式,或者称为其他,该SR资源配置信息所包含的上述开关字段和/或表示优先级的字段也可以称为其他,不限于上述示例中的举例。It is worth noting that the above is just an example. In the above embodiment, the SR resource configuration information may also be in other forms, or called other. The above switch field and/or the field indicating the priority contained in the SR resource configuration information may also be called other, and is not limited to the examples in the above example.
在上述实施例中,在操作520中,终端设备在检测到波束管理事件时,其可以向网络设备发送上述SR信息,该SR信息可以由上述RRC资源配置信息为事件驱动的波束管理配置的专用SR资源承载,用于告知网络设备该SR信息用于事件驱动的波束管理。In the above embodiment, in operation 520, when the terminal device detects a beam management event, it can send the above SR information to the network device. The SR information can be carried by the dedicated SR resources configured for event-driven beam management by the above RRC resource configuration information, so as to inform the network device that the SR information is used for event-driven beam management.
在上述实施例中,在操作530中,终端设备可以接收网络设备发送的上行调度授权信息,该上行调度授权信息用于调度PUSCH,可以由DCI格式0_1或DCI格式0_2或DCI格式0_3(DCI format 0_1/0_2/0_3)承载。In the above embodiment, in operation 530, the terminal device can receive uplink scheduling authorization information sent by the network device. The uplink scheduling authorization information is used to schedule PUSCH and can be carried by DCI format 0_1 or DCI format 0_2 or DCI format 0_3 (DCI format 0_1/0_2/0_3).
在上述实施例中,在操作540中,终端设备在收到网络设备发送的上述上行调度授权信息之后,可以在上述上行调度授权信息调度的PUSCH上发送上述事件驱动的波束管理信息。In the above embodiment, in operation 540, after receiving the above uplink scheduling grant information sent by the network device, the terminal device can send the above event-driven beam management information on the PUSCH scheduled by the above uplink scheduling grant information.
在上述实施例中,上述上行调度授权信息调度的PUSCH承载上行共享信道(UL-SCH),该UL-SCH包含上述事件驱动的波束管理信息。在该实施例中,该上行调度授权信息中的UL-SCH indicator字段的取值为1,表明该UL-SCH包含上述事件驱动的波束管理信息。In the above embodiment, the PUSCH scheduled by the uplink scheduling grant information carries an uplink shared channel (UL-SCH), and the UL-SCH includes the above event-driven beam management information. In this embodiment, the value of the UL-SCH indicator field in the uplink scheduling grant information is 1, indicating that the UL-SCH includes the above event-driven beam management information.
根据上述实施例,终端设备可以根据SR资源配置信息上报事件驱动的波束管理信息,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to the above embodiment, the terminal device can report event-driven beam management information based on the SR resource configuration information, which effectively reduces the delay of beam management, reduces signaling overhead, and improves network coverage.
以上各个实施例仅对本申请实施例进行了示例性说明,但本申请不限于此,还可以在以上各个实施例的基础上进行适当的变型。例如,可以单独使用上述各个实施例,也可以将以上各个实施例中的一种或多种结合起来。The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
根据本申请实施例的方法,根据网络设备的配置,有效降低了波束管理的时延、降 低了信令开销、改善了网络覆盖。According to the method of the embodiment of the present application, the delay of beam management is effectively reduced according to the configuration of the network equipment. Reduces signaling overhead and improves network coverage.
第二方面的实施例Embodiments of the second aspect
本申请实施例提供一种事件驱动的波束管理的配置方法,从网络设备的一侧进行说明,该方法是与第一方面的实施例的方法对应的网络设备侧的处理,其中与第一方面的实施例相同的内容不再赘述。An embodiment of the present application provides a configuration method for event-driven beam management, which is explained from the side of the network device. This method is the processing on the network device side corresponding to the method of the embodiment of the first aspect, and the content that is the same as the embodiment of the first aspect is not repeated.
图6是本申请实施例的事件驱动的波束管理的配置方法的一示意图,如图6所示,该方法包括:FIG6 is a schematic diagram of a configuration method for event-driven beam management according to an embodiment of the present application. As shown in FIG6 , the method includes:
610:网络设备向终端设备发送配置信息,该配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;610: The network device sends configuration information to the terminal device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management.
620:网络设备接收终端设备发送的事件驱动的波束管理信息。620: The network device receives event-driven beam management information sent by the terminal device.
值得注意的是,以上附图6仅对本申请实施例进行了示意性说明,但本申请不限于此。例如可以增加其他的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型,而不仅限于上述附图6的记载。It is worth noting that FIG6 above is only a schematic illustration of the embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG6 above.
根据本申请实施例,网络设备为终端设备配置与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息,由此终端设备可以进行事件驱动的波束管理信息的上报,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to an embodiment of the present application, the network device configures CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management for the terminal device, so that the terminal device can report event-driven beam management information, effectively reducing the delay of beam management, reducing signaling overhead, and improving network coverage.
在一些实施例中,与第一方面的实施例中图2所示的方法对应的,网络设备还可以接收终端设备发送的调度请求信息,并向终端设备发送上行调度授权信息,该上行调度授权信息能够用于触发非周期CSI上报。由此,终端设备可以根据上述CSI上报配置信息向终端设备发送包含上述事件驱动的波束管理信息的CSI上报。相应的,网络设备可以接收终端设备根据上述CSI上报配置信息发送的包含上述事件驱动的波束管理信息的CSI上报。In some embodiments, corresponding to the method shown in Figure 2 in the embodiment of the first aspect, the network device may also receive scheduling request information sent by the terminal device, and send uplink scheduling authorization information to the terminal device, and the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting. Thus, the terminal device can send a CSI report containing the above-mentioned event-driven beam management information to the terminal device according to the above-mentioned CSI reporting configuration information. Accordingly, the network device can receive a CSI report containing the above-mentioned event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
在一些实施例中,与第一方面的实施例中图3所示的方法对应的,网络设备还可以接收终端设备根据上述CSI上报配置信息发送的事件驱动的波束管理信息。In some embodiments, corresponding to the method shown in Figure 3 in the embodiment of the first aspect, the network device can also receive event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
在一些实施例中,与第一方面的实施例中图5所示的方法对应的,网络设备还可以接收终端设备发送的调度请求信息,并向终端设备发送上行调度授权信息。由此,终端设备可以在该上行调度授权信息所调度的PUSCH上,发送上述事件驱动的波束管理信息。相应的,网络设备可以接收终端设备在上述上行调度授权信息所调度的PUSCH上发送的上述事件驱动的波束管理信息。 In some embodiments, corresponding to the method shown in FIG5 of the embodiment of the first aspect, the network device may further receive scheduling request information sent by the terminal device and send uplink scheduling authorization information to the terminal device. Thus, the terminal device may send the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information. Correspondingly, the network device may receive the above-mentioned event-driven beam management information sent by the terminal device on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
以上各个实施例仅对本申请实施例进行了示例性说明,但本申请不限于此,还可以在以上各个实施例的基础上进行适当的变型。例如,可以单独使用上述各个实施例,也可以将以上各个实施例中的一种或多种结合起来。The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
根据本申请实施例的方法,通过网络设备的配置,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to the method of the embodiment of the present application, the delay of beam management is effectively reduced, the signaling overhead is reduced, and the network coverage is improved through the configuration of network equipment.
第三方面的实施例Embodiments of the third aspect
本申请实施例提供一种事件驱动的波束管理装置。该装置例如可以是终端设备,也可以是配置于终端设备的某个或某些部件或者组件,与第一方面和第二方面的实施例相同的内容不再赘述。The embodiment of the present application provides an event-driven beam management device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. The contents that are the same as those in the first and second aspects are not repeated here.
图7是本申请实施例的事件驱动的波束管理装置的一示意图。如图7所示,本申请实施例的事件驱动的波束管理装置700包括:FIG7 is a schematic diagram of an event-driven beam management device according to an embodiment of the present application. As shown in FIG7 , the event-driven beam management device 700 according to an embodiment of the present application includes:
接收单元710,其接收网络设备发送的配置信息,所述配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;a receiving unit 710 configured to receive configuration information sent by a network device, the configuration information including CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
发送单元720,其根据所述CSI上报配置信息和/或所述SR资源配置信息,发送事件驱动的波束管理信息。A sending unit 720 sends event-driven beam management information according to the CSI reporting configuration information and/or the SR resource configuration information.
在一些实施例中,发送单元720根据上述CSI上报配置信息和上述SR资源配置信息,发送事件驱动的波束管理信息。In some embodiments, the sending unit 720 sends event-driven beam management information according to the above-mentioned CSI reporting configuration information and the above-mentioned SR resource configuration information.
在上述实施例中,在终端设备在检测到波束管理事件时,发送单元720在上述SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息;接收单元710接收网络设备发送的上行调度授权信息,该上行调度授权信息能够用于触发非周期CSI上报;发送单元720根据上述CSI上报配置信息,在上述上行调度授权信息所调度的PUSCH上发送CSI上报,该CSI上报包括上述事件驱动的波束管理信息。In the above embodiment, when the terminal device detects a beam management event, the sending unit 720 sends a scheduling request (SR) information to the network device on the dedicated SR resource configured for event-driven beam management in the above SR resource configuration information; the receiving unit 710 receives the uplink scheduling authorization information sent by the network device, and the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting; the sending unit 720 sends a CSI report on the PUSCH scheduled by the above uplink scheduling authorization information according to the above CSI reporting configuration information, and the CSI report includes the above event-driven beam management information.
在上述实施例中,可选的,CSI上报配置信息的上报类型(reportConfigType)是非周期性的(aperiodic)。In the above embodiment, optionally, the reporting type (reportConfigType) of the CSI reporting configuration information is aperiodic.
在上述实施例中,可选的,SR资源配置信息可以包含于信元PUCCH-Config中。In the above embodiment, optionally, the SR resource configuration information may be included in the information element PUCCH-Config.
在上述实施例中,可选的,SR资源配置信息为列表schedulingRequestResourceToAddModListExt-EventBM,用于增加或调整与事件驱动的波束管理有关的SR资源。 In the above embodiment, optionally, the SR resource configuration information is a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust SR resources related to event-driven beam management.
在一些可能的实现方式中,该SR资源配置信息中的列表元素为SchedulingRequestResourceConfigExt-EventBM,用于配置与事件驱动的波束管理有关的SR资源。In some possible implementations, the list element in the SR resource configuration information is SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
在上述实现方式中,SchedulingRequestResourceConfigExt-EventBM还可以包括用于指示是否用作事件驱动的波束管理的开关字段(eventBeamManagementFlag)和/或表示优先级的字段(phy-PriorityIndex)。In the above implementation, SchedulingRequestResourceConfigExt-EventBM may further include a switch field (eventBeamManagementFlag) for indicating whether to use event-driven beam management and/or a field indicating priority (phy-PriorityIndex).
在上述实施例中,上行调度授权信息可以由DCI格式0_1或DCI格式0_2或DCI格式0_3承载。In the above embodiment, the uplink scheduling grant information may be carried by DCI format 0_1, DCI format 0_2, or DCI format 0_3.
在上述实施例中,上行调度授权信息还可以包括CSI请求字段,所述CSI请求字段用于触发非周期CSI上报。In the above embodiment, the uplink scheduling grant information may further include a CSI request field, and the CSI request field is used to trigger aperiodic CSI reporting.
在上述实施例中,上行调度授权信息所调度的PUSCH可以承载上述CSI上报(包含事件驱动的波束管理信息)。In the above embodiment, the PUSCH scheduled by the uplink scheduling grant information can carry the above CSI reporting (including event-driven beam management information).
在上述实施例中,上行调度授权信息所调度的PUSCH还可以承载上行共享信道(UL-SCH)。In the above embodiment, the PUSCH scheduled by the uplink scheduling grant information may also carry an uplink shared channel (UL-SCH).
在另一些实施例中,发送单元720根据上述CSI上报配置信息发送事件驱动的波束管理信息。In other embodiments, the sending unit 720 sends event-driven beam management information according to the above-mentioned CSI reporting configuration information.
在上述实施例中,上述CSI上报配置信息的上报类型(reportConfigType)为周期性的(periodic)或者半持续的(semiPersistentOnPUCCH或semiPersistentOnPUSCH)。In the above embodiment, the reporting type (reportConfigType) of the above CSI reporting configuration information is periodic (periodic) or semi-persistent (semiPersistentOnPUCCH or semiPersistentOnPUSCH).
在上述实施例中,CSI上报配置信息可以包括第一字段,该第一字段用于指示所述CSI上报配置信息用于事件驱动的波束管理。In the above embodiment, the CSI reporting configuration information may include a first field, where the first field is used to indicate that the CSI reporting configuration information is used for event-driven beam management.
在上述实施例中,CSI上报配置信息可以为信元CSI-ReportConfig,第一字段可以为eventBeamManagementFlag,并且,该第一字段可以是开关字段。In the above embodiment, the CSI reporting configuration information may be the information element CSI-ReportConfig, the first field may be eventBeamManagementFlag, and the first field may be a switch field.
在上述实施例中,CSI上报配置信息可以包括第二字段,该第二字段的取值中包括第一上报选项,该第一上报选项用于事件驱动的波束管理。In the above embodiment, the CSI reporting configuration information may include a second field, the value of the second field includes a first reporting option, and the first reporting option is used for event-driven beam management.
在上述实施例中,CSI上报配置可以为信元CSI-ReportConfig,第二字段可以为reportQuantity,第一上报选项可以为字段EventBMInfo,该字段EventBMInfo是列表形式,列表内容为零到多个候选波束信息。In the above embodiment, the CSI reporting configuration may be the information element CSI-ReportConfig, the second field may be reportQuantity, and the first reporting option may be the field EventBMInfo. The field EventBMInfo is in list form, and the list content is zero to multiple candidate beam information.
在上述实施例中,终端设备可以在上述CSI上报配置信息生效或者被激活的情况下,根据该CSI上报配置信息发送事件驱动的波束管理信息。In the above embodiment, the terminal device may send event-driven beam management information according to the CSI reporting configuration information when the above CSI reporting configuration information is effective or activated.
在又一些实施例中,发送单元720根据上述SR资源配置信息,发送事件驱动的波 束管理信息。In some other embodiments, the sending unit 720 sends an event-driven wave according to the above SR resource configuration information. Bundle management information.
在上述实施例中,在终端设备检测到波束管理事件时,发送单元720在SR资源配置信息为事件驱动的波束管理配置的专用SR资源上,向网络设备发送调度请求(SR)信息;接收单元710接收网络设备发送的上行调度授权信息;发送单元720在该上行调度授权信息所调度的PUSCH上发送上述事件驱动的波束管理信息。In the above embodiment, when the terminal device detects a beam management event, the sending unit 720 sends a scheduling request (SR) information to the network device on a dedicated SR resource whose SR resource configuration information is event-driven beam management configuration; the receiving unit 710 receives the uplink scheduling authorization information sent by the network device; the sending unit 720 sends the above-mentioned event-driven beam management information on the PUSCH scheduled by the uplink scheduling authorization information.
在上述实施例中,SR资源配置信息可以包含于信元PUCCH-Config中。In the above embodiment, the SR resource configuration information may be included in the information element PUCCH-Config.
在上述实施例中,SR资源配置信息可以是列表schedulingRequestResourceToAddModListExt-EventBM,用于增加或调整与事件驱动的波束管理有关的SR资源。In the above embodiment, the SR resource configuration information may be a list schedulingRequestResourceToAddModListExt-EventBM, which is used to add or adjust SR resources related to event-driven beam management.
在上述实施例中,SR资源配置信息中的列表元素可以是SchedulingRequestResourceConfigExt-EventBM,用于配置与事件驱动的波束管理有关的SR资源。In the above embodiment, the list element in the SR resource configuration information may be SchedulingRequestResourceConfigExt-EventBM, which is used to configure SR resources related to event-driven beam management.
在上述实施例中,SchedulingRequestResourceConfigExt-EventBM可以包括用于指示是否用作事件驱动的波束管理的开关字段(eventBeamManagementFlag)和/或表示优先级的字段(phy-PriorityIndex)。In the above embodiment, SchedulingRequestResourceConfigExt-EventBM may include a switch field (eventBeamManagementFlag) for indicating whether to use event-driven beam management and/or a field indicating a priority (phy-PriorityIndex).
在上述实施例中,上行调度授权信息可以由DCI格式0_1或DCI格式0_2或DCI格式0_3承载。In the above embodiment, the uplink scheduling grant information may be carried by DCI format 0_1, DCI format 0_2, or DCI format 0_3.
在上述实施例中,上行调度授权信息所调度的PUSCH可以承载UL-SCH,该UL-SCH包含上述事件驱动的波束管理信息。In the above embodiment, the PUSCH scheduled by the uplink scheduling grant information may carry the UL-SCH, which includes the above event-driven beam management information.
在上述实施例中,上行调度授权信息中的UL-SCH indicator字段取值为1。In the above embodiment, the value of the UL-SCH indicator field in the uplink scheduling authorization information is 1.
本申请实施例还提供一种事件驱动的波束管理的配置装置。该装置例如可以是网络设备,也可以是配置于网络设备的某个或某些部件或者组件,与第一至第二方面的实施例相同的内容不再赘述。The present application also provides an event-driven beam management configuration device. The device can be, for example, a network device, or one or more components or assemblies configured on the network device. The same contents as those in the first and second aspects are not repeated here.
图8是本申请实施例的事件驱动的波束管理的配置装置的一示意图。如图8所示,本申请实施例的事件驱动的波束管理的配置装置800包括:FIG8 is a schematic diagram of a configuration device for event-driven beam management according to an embodiment of the present application. As shown in FIG8 , the configuration device 800 for event-driven beam management according to an embodiment of the present application includes:
发送单元810,其向终端设备发送配置信息,该配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;a sending unit 810 configured to send configuration information to a terminal device, the configuration information including CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
接收单元820,其接收终端设备发送的事件驱动的波束管理信息。The receiving unit 820 receives event-driven beam management information sent by the terminal device.
在一些实施例中,与第一方面的实施例中图2所示的方法对应的,接收单元820还可以接收终端设备发送的调度请求信息,发送单元810还可以向终端设备发送上行调度 授权信息,该上行调度授权信息能够用于触发非周期CSI上报,接收单元820还可以接收终端设备根据上述CSI上报配置信息发送的包含上述事件驱动的波束管理信息的CSI上报。In some embodiments, corresponding to the method shown in FIG. 2 in the embodiment of the first aspect, the receiving unit 820 may further receive the scheduling request information sent by the terminal device, and the sending unit 810 may further send an uplink scheduling request to the terminal device. Authorization information, the uplink scheduling authorization information can be used to trigger non-periodic CSI reporting, and the receiving unit 820 can also receive the CSI report containing the above-mentioned event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
在一些实施例中,与第一方面的实施例中图3所示的方法对应的,接收单元820还可以接收终端设备根据上述CSI上报配置信息发送的事件驱动的波束管理信息。In some embodiments, corresponding to the method shown in FIG3 in the embodiment of the first aspect, the receiving unit 820 may also receive event-driven beam management information sent by the terminal device according to the above-mentioned CSI reporting configuration information.
在一些实施例中,与第一方面的实施例中图5所示的方法对应的,接收单元820还可以接收终端设备发送的调度请求信息,发送单元810还可以向终端设备发送上行调度授权信息,接收单元820还可以接收终端设备在上述上行调度授权信息所调度的PUSCH上发送的上述事件驱动的波束管理信息。In some embodiments, corresponding to the method shown in Figure 5 in the embodiment of the first aspect, the receiving unit 820 can also receive scheduling request information sent by the terminal device, the sending unit 810 can also send uplink scheduling authorization information to the terminal device, and the receiving unit 820 can also receive the above-mentioned event-driven beam management information sent by the terminal device on the PUSCH scheduled by the above-mentioned uplink scheduling authorization information.
以上各个实施例仅对本申请实施例进行了示例性说明,但本申请不限于此,还可以在以上各个实施例的基础上进行适当的变型。例如,可以单独使用上述各个实施例,也可以将以上各个实施例中的一种或多种结合起来。The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.
值得注意的是,以上仅对与本申请相关的各部件或模块进行了说明,但本申请不限于此。装置700和800还可以包括其他部件或者模块,关于这些部件或者模块的具体内容,可以参考相关技术。It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. Apparatuses 700 and 800 may also include other components or modules, and for details of these components or modules, reference may be made to related art.
此外,为了简单起见,图7和图8中仅示例性示出了各个部件或模块之间的连接关系或信号走向,但是本领域技术人员应该清楚的是,可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现;本申请实施并不对此进行限制。In addition, for the sake of simplicity, Figures 7 and 8 only illustrate the connection relationships or signal paths between various components or modules. However, those skilled in the art should be aware that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.
根据本申请实施例的装置,有效降低了波束管理的时延、降低了信令开销、改善了网络覆盖。According to the device of the embodiment of the present application, the delay of beam management is effectively reduced, the signaling overhead is reduced, and the network coverage is improved.
第四方面的实施例Embodiments of the fourth aspect
本申请实施例还提供一种通信系统,该通信系统包括网络设备和终端设备。An embodiment of the present application also provides a communication system, which includes a network device and a terminal device.
图9是本申请实施例的通信系统的示意图,示意性说明了以终端设备和网络设备为例的情况,如图9所示,通信系统900可以包括网络设备901和终端设备902、903。为简单起见,图9仅以两个终端设备和一个网络设备为例进行说明,但本申请实施例不限于此。FIG9 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG9 , a communication system 900 may include a network device 901 and terminal devices 902 and 903. For simplicity, FIG9 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.
在本申请实施例中,网络设备901和终端设备902、903之间可以进行现有的业务或者未来可实施的业务发送。例如,这些业务可以包括但不限于:增强的移动宽带(eMBB, enhanced Mobile Broadband)、大规模机器类型通信(mMTC,massive Machine Type Communication)和高可靠低时延通信(URLLC,Ultra-Reliable and Low-Latency Communication),等等。In the embodiment of the present application, existing services or future services can be sent between the network device 901 and the terminal devices 902 and 903. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB, enhanced Mobile Broadband), massive Machine Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC), etc.
值得注意的是,图9示出了两个终端设备902、903均处于网络设备901的覆盖范围内,但本申请不限于此。两个终端设备902、903可以均不在网络设备901的覆盖范围内,或者一个终端设备902在网络设备901的覆盖范围之内而另一个终端设备903在网络设备901的覆盖范围之外。It is worth noting that Figure 9 shows that both terminal devices 902 and 903 are within the coverage range of network device 901, but the present application is not limited thereto. Both terminal devices 902 and 903 may not be within the coverage range of network device 901, or one terminal device 902 may be within the coverage range of network device 901 while the other terminal device 903 is outside the coverage range of network device 901.
在一些实施例中,终端设备包括第二方面的实施例所述的装置700,被配置为执行第一方面的实施例所述的方法。由于在第一方面的实施例中,已经对该方法进行了详细说明,其内容被合并于此,不再重复说明。In some embodiments, the terminal device includes the apparatus 700 described in the embodiment of the second aspect, and is configured to perform the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.
在一些实施例中,网络设备包括第二方面的实施例所述的装置800,被配置为执行第二方面的实施例所述的方法。由于在第二方面的实施例中,已经对该方法进行了详细说明,其内容被合并于此,不再重复说明。In some embodiments, the network device includes the apparatus 800 described in the embodiment of the second aspect, and is configured to perform the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.
本申请实施例还提供一种终端设备,该终端设备例如可以是UE,但本申请不限于此,还可以是其他的设备。An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other devices.
图10是本申请实施例的终端设备的示意图。如图10所示,该终端设备1000可以包括处理器1010和存储器1020;存储器1020存储有数据和程序,并耦合到处理器1010。值得注意的是,该图是示例性的;还可以使用其他类型的结构,来补充或代替该结构,以实现电信功能或其他功能。Figure 10 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 10 , terminal device 1000 may include a processor 1010 and a memory 1020. Memory 1020 stores data and programs and is coupled to processor 1010. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.
例如,处理器1010可以被配置为执行程序而实现如第一方面的实施例所述的方法。For example, the processor 1010 may be configured to execute a program to implement the method described in the embodiment of the first aspect.
如图10所示,该终端设备1000还可以包括:通信模块1030、输入单元1040、显示器1050、电源1060。其中,上述部件的功能与现有技术类似,此处不再赘述。值得注意的是,终端设备1000也并不是必须要包括图10中所示的所有部件,上述部件并不是必需的;此外,终端设备1000还可以包括图10中没有示出的部件,可以参考现有技术。As shown in Figure 10 , the terminal device 1000 may further include: a communication module 1030, an input unit 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all of the components shown in Figure 10 , and these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10 , for which reference may be made to the prior art.
本申请实施例还提供一种网络设备,例如可以是gNB,但本申请不限于此,还可以是其他的网络设备。An embodiment of the present application further provides a network device, which may be, for example, a gNB, but the present application is not limited thereto and may also be other network devices.
图11是本申请实施例的网络设备的构成示意图。如图11所示,网络设备1100可以包括:处理器1110(例如中央处理器CPU)和存储器1120;存储器1120耦合到处理器1110。其中该存储器1120可存储各种数据;此外还存储信息处理的程序1130,并且 在处理器1110的控制下执行该程序1130。FIG11 is a schematic diagram of the structure of a network device according to an embodiment of the present application. As shown in FIG11 , the network device 1100 may include: a processor 1110 (e.g., a central processing unit (CPU)) and a memory 1120; the memory 1120 is coupled to the processor 1110. The memory 1120 may store various data; in addition, it may store an information processing program 1130, and The program 1130 is executed under the control of the processor 1110 .
例如,处理器1110可以被配置为执行程序而实现如第二方面的实施例所述的方法。For example, the processor 1110 may be configured to execute a program to implement the method as described in the embodiment of the second aspect.
此外,如图11所示,网络设备1100还可以包括:收发机1140和天线1150等;其中,上述部件的功能与现有技术类似,此处不再赘述。值得注意的是,网络设备1100也并不是必须要包括图11中所示的所有部件;此外,网络设备1100还可以包括图11中没有示出的部件,可以参考现有技术。In addition, as shown in FIG11 , the network device 1100 may further include: a transceiver 1140 and an antenna 1150, etc.; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the network device 1100 does not necessarily include all the components shown in FIG11 ; in addition, the network device 1100 may also include components not shown in FIG11 , and reference may be made to the prior art for details.
本申请实施例还提供一种计算机程序,其中当在终端设备中执行所述程序时,所述程序使得所述终端设备执行第一方面的实施例所述的方法。An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.
本申请实施例还提供一种存储有计算机程序的存储介质,其中所述计算机程序使得终端设备执行第一方面的实施例所述的方法。An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.
本申请实施例还提供一种计算机程序,其中当在网络设备中执行所述程序时,所述程序使得所述网络设备执行第二方面的实施例所述的方法。An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.
本申请实施例还提供一种存储有计算机程序的存储介质,其中所述计算机程序使得网络设备执行第二方面的实施例所述的方法。An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.
本申请以上的装置和方法可以由硬件实现,也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序,当该程序被逻辑部件所执行时,能够使该逻辑部件实现上文所述的装置或构成部件,或使该逻辑部件实现上文所述的各种方法或步骤。本申请还涉及用于存储以上程序的存储介质,如硬盘、磁盘、光盘、DVD、flash存储器等。The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如,图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合,既可以对应于计算机程序流程的各个软件模块,亦可以对应于各个硬件模块。这些软件模块,可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。The method/device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and/or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器,从而使处理器能够从该存储介质读取信息,且可向该存储介质写入信息;或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中,也可以存储在可插入移动终端的存储卡中。例如,若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置,则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存 装置中。The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device. In the device.
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合,可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合,还可以实现为计算设备的组合,例如,DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。One or more of the functional blocks and/or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and/or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.
以上结合具体的实施方式对本申请进行了描述,但本领域技术人员应该清楚,这些描述都是示例性的,并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改,这些变型和修改也在本申请的范围内。The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.
1.一种终端设备,包括存储器和处理器,所述存储器存储有计算机程序,所述处理器被配置为执行所述计算机程序而实现如下所述的方法:1. A terminal device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method:
接收网络设备发送的配置信息,所述配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;receiving configuration information sent by a network device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
根据所述CSI上报配置信息和/或所述SR资源配置信息,发送事件驱动的波束管理信息。Send event-driven beam management information according to the CSI reporting configuration information and/or the SR resource configuration information.
2.一种网络设备,包括存储器和处理器,所述存储器存储有计算机程序,所述处理器被配置为执行所述计算机程序而实现如下所述的方法:2. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method:
向终端设备发送配置信息,所述配置信息包括与事件驱动的波束管理关联的CSI上报配置信息和/或SR资源配置信息;Sending configuration information to the terminal device, where the configuration information includes CSI reporting configuration information and/or SR resource configuration information associated with event-driven beam management;
接收所述终端设备根据所述CSI上报配置信息和/或所述SR资源配置信息发送的事件驱动的波束管理信息。Receive event-driven beam management information sent by the terminal device according to the CSI reporting configuration information and/or the SR resource configuration information.
3.一种通信系统,包括附记2所述的网络设备和附记1所述的终端设备。 3. A communication system comprising the network device described in Note 2 and the terminal device described in Note 1.
Claims (20)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/075846 WO2025161030A1 (en) | 2024-02-04 | 2024-02-04 | Event-driven beam management method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2024/075846 WO2025161030A1 (en) | 2024-02-04 | 2024-02-04 | Event-driven beam management method and apparatus |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2025161030A1 true WO2025161030A1 (en) | 2025-08-07 |
Family
ID=96589428
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2024/075846 Pending WO2025161030A1 (en) | 2024-02-04 | 2024-02-04 | Event-driven beam management method and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2025161030A1 (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110447295A (en) * | 2017-03-22 | 2019-11-12 | Lg 电子株式会社 | Method and user equipment for performing beam restoration and method and base station for supporting same |
| US20220131583A1 (en) * | 2019-02-01 | 2022-04-28 | Lg Electronics Inc. | Method by which terminal reports state information in wireless communication system, and terminal and base station for supporting same |
| WO2023050049A1 (en) * | 2021-09-28 | 2023-04-06 | 北京小米移动软件有限公司 | Information reporting method and apparatus, beam switching method and apparatus, and storage medium |
| WO2024000606A1 (en) * | 2022-07-01 | 2024-01-04 | 北京小米移动软件有限公司 | Beam measurement result reporting method and apparatus |
-
2024
- 2024-02-04 WO PCT/CN2024/075846 patent/WO2025161030A1/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110447295A (en) * | 2017-03-22 | 2019-11-12 | Lg 电子株式会社 | Method and user equipment for performing beam restoration and method and base station for supporting same |
| US20220131583A1 (en) * | 2019-02-01 | 2022-04-28 | Lg Electronics Inc. | Method by which terminal reports state information in wireless communication system, and terminal and base station for supporting same |
| WO2023050049A1 (en) * | 2021-09-28 | 2023-04-06 | 北京小米移动软件有限公司 | Information reporting method and apparatus, beam switching method and apparatus, and storage medium |
| WO2024000606A1 (en) * | 2022-07-01 | 2024-01-04 | 北京小米移动软件有限公司 | Beam measurement result reporting method and apparatus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP7040617B2 (en) | Signaling instruction and reception method, device and communication system | |
| EP3550733A1 (en) | Communication method, network device, and terminal device | |
| WO2022151299A1 (en) | Indication information reporting method and apparatus, and indication information receiving method and apparatus | |
| JP7609265B2 (en) | Wireless communication method, device and system | |
| CN118985110A (en) | AI monitoring device and method | |
| CN112567839A (en) | Method for evaluating quality of wireless link, parameter configuration method, device and system | |
| WO2022205408A1 (en) | Uplink data transmission method, apparatus and system | |
| WO2025161030A1 (en) | Event-driven beam management method and apparatus | |
| WO2024031696A1 (en) | Channel state information reporting method and apparatus | |
| US20230261723A1 (en) | Apparatus, Method, and Computer Program | |
| WO2025166695A1 (en) | Event-driven beam management method and apparatus | |
| WO2022077309A1 (en) | Wireless communication method, apparatus, and system | |
| WO2025208293A1 (en) | Beam management method and apparatus | |
| US20250365600A1 (en) | Information transceiving method and apparatus | |
| US20250374131A1 (en) | Information transceiving method and apparatus | |
| WO2025030496A1 (en) | Data sending method and apparatus, and data receiving method and apparatus | |
| WO2025208439A1 (en) | Method and apparatus for sending or receiving information, and communication system | |
| WO2025171645A1 (en) | Transmission configuration method and apparatus | |
| WO2019157664A1 (en) | Resource selection method and apparatus for beam failure recovery, and communication system | |
| WO2025160813A1 (en) | Information reporting method and apparatus, and information receiving method and apparatus | |
| WO2024168585A1 (en) | Information receiving and sending method and apparatus | |
| WO2024207295A1 (en) | Information receiving/transmitting method and apparatus | |
| WO2025160837A1 (en) | Sounding reference signal sending method and apparatus, and sounding reference signal receiving method and apparatus | |
| WO2024168761A1 (en) | Repeater, beam instruction method therefor, network device, and communication system | |
| WO2025208510A1 (en) | Information processing method and apparatus, and communication system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 24921083 Country of ref document: EP Kind code of ref document: A1 |