WO2023122984A1

WO2023122984A1 - Srs triggering method and apparatus, and storage medium

Info

Publication number: WO2023122984A1
Application number: PCT/CN2021/142173
Authority: WO
Inventors: 高雪媛
Original assignee: 北京小米移动软件有限公司
Priority date: 2021-12-28
Filing date: 2021-12-28
Publication date: 2023-07-06
Also published as: CN116671210A

Abstract

The present disclosure relates to an SRS triggering method and apparatus, and a storage medium. The SRS triggering method is applied to a terminal, and comprises: acquiring downlink control information for non-data scheduling, wherein the downlink control information for non-data scheduling is used for indicating carrier information for triggering one or more SRS resource sets on an inactive bandwidth part (BWP), and BWP information; and triggering, on the basis of the carrier information and the BWP information, the one or more SRS resource sets on any one BWP of any one of one or more carriers. By means of the present disclosure, cross-carrier and cross-BWP SRS joint triggering can be realized.

Description

A kind of SRS triggering method, device and storage medium

technical field

The present disclosure relates to the field of communication technologies, and in particular to a sounding reference signal (sounding reference signal, SRS) triggering method, device and storage medium.

Background technique

In the communication system, different sounding reference signals (Sounding Reference Signal, SRS) are configured for different antenna switching configurations (antenna switching configurations) for terminals. Wherein, the network configures multiple uplink SRS resource sets for the terminal, and one resource set includes one or more SRS resources.

In related technologies, SRS triggering can be based on radio resource control (Radio Resource Control, RRC) semi-static time slot offset configuration, and supports the introduction of downlink control information (downlink control information, The dynamic slot offset indicated by DCI), the newly introduced DCI is used to indicate a specific offset value among multiple slot offsets configured by RRC. This kind of SRS triggering method can realize the flexible triggering of SRS, but in the SRS triggering method supported by the current protocol, only multiple SRS resource sets on a common carrier (Component Carrier, CC) can be triggered at the same time, but different CCs cannot be triggered at the same time A collection of different SRS resources on .

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides an SRS triggering method, device and storage medium.

According to the first aspect of the embodiments of the present disclosure, there is provided an SRS triggering method applied to a terminal, including:

Obtain downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP; based on the carrier information As well as the BWP information, the one or more SRS resource sets are jointly triggered on any BWP of any one of the one or more carriers.

In an implementation manner, the downlink control information includes an unused control information indication field, and the carrier information and the BWP information are carried in the unused control information indication field.

In an implementation manner, the unused control information indication field includes a carrier information indication field; the carrier information indication field is used to indicate carrier information corresponding to triggering one or more SRS resource sets on the inactive BWP.

In one embodiment, the downlink control information includes a BWP indication field for dynamically scheduling and activating BWP; the unused control information indication field includes the BWP indication field, and the BWP indication field is used to indicate that triggering a non-activation Activate the BWP information corresponding to one or more SRS resource sets on the BWP.

In one embodiment, the downlink control information does not include a BWP indication field for dynamically scheduling and activating BWP; the unused control information indication field includes other indication fields different from the BWP indication field; the other indication field BWP information used to indicate joint triggering of multiple SRS resource sets on an inactive BWP.

In one embodiment, the BWP information used to indicate joint triggering of multiple SRS resource sets on the inactive BWP in the other indication field includes a code point used to indicate the BWP information;

The code point includes at least one of the following: a redefined code point; a reserved code point.

In an implementation manner, the downlink control information includes downlink control information used for scheduling uplink data but not actually scheduling uplink data and channel state information.

In an implementation manner, the downlink control information includes downlink control information used for downlink data scheduling, but the downlink data is not actually scheduled.

In an implementation manner, the method further includes: reporting terminal capability information, where the terminal capability information is used to indicate whether the capability of triggering SRS resources on the inactive BWP through non-data-scheduled downlink control information is supported.

According to the second aspect of the embodiments of the present disclosure, an SRS triggering method is provided, which is applied to a network device, including:

Sending downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the BWP of the inactive partial bandwidth.

In one embodiment, the downlink control information does not include a BWP indication field for dynamically scheduling and activating the BWP;

The unused control information indication field includes other indication fields different from the BWP indication field; the other indication field is used to indicate the BWP information of jointly triggering multiple SRS resource sets on the inactive BWP.

In one embodiment, the method further includes: receiving terminal capability information, where the terminal capability information is used to indicate whether to support the capability of triggering SRS resources on the inactive BWP through downlink control information of non-data scheduling.

According to a third aspect of an embodiment of the present disclosure, an SRS triggering device is provided, including:

An acquiring unit, configured to acquire downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP; A processing unit, configured to jointly trigger the one or more SRS resource sets on any BWP of any one of the one or more carriers based on the carrier information and the BWP information.

In one embodiment, the SRS triggering device further includes a reporting unit, the reporting unit is configured to: report terminal capability information, and the terminal capability information is used to indicate whether to support triggering an inactive BWP through non-data-scheduled downlink control information Capabilities on SRS resources.

According to a fourth aspect of an embodiment of the present disclosure, an SRS triggering device is provided, including:

A sending unit, configured to send downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the BWP of the inactive partial bandwidth.

In one embodiment, the downlink control information includes an unused control information indication field, and the carrier information and the BWP information are carried in the unused control information indication field.

In one embodiment, the SRS triggering device further includes a receiving unit, the receiving unit is configured to receive terminal capability information, and the terminal capability information is used to indicate whether to support triggering the non-activated BWP on the downlink control information through non-data scheduling. The capabilities of the SRS resource.

According to a fifth aspect of an embodiment of the present disclosure, an SRS triggering device is provided, including:

processor; memory for storing instructions executable by the processor;

Wherein, the processor is configured to: execute the first aspect or the method described in any one implementation manner of the first aspect.

According to a sixth aspect of an embodiment of the present disclosure, an SRS triggering device is provided, including:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to: execute the method described in the second aspect or any implementation manner of the second aspect.

According to the seventh aspect of the embodiments of the present disclosure, a storage medium is provided, and instructions are stored in the storage medium, and when the instructions are executed by the processor of the terminal, the terminal can execute the first aspect or any one of the first aspect. The method described in the implementation.

According to the eighth aspect of the embodiments of the present disclosure, there is provided a storage medium, the storage medium stores instructions, and when the instructions are executed by the processor of the network device, the network device can execute the second aspect or any of the second aspects. A method described in one embodiment.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects: In the present disclosure, the terminal obtains non-data-scheduled downlink control information, and the non-data-scheduled downlink control information is used to indicate the triggering of one or more Carrier information and BWP information of an SRS resource set. Furthermore, based on the non-data-scheduled downlink control information, the terminal can jointly trigger one or more SRS resource sets on any BWP of any one of the one or more carriers to realize cross-carrier and cross-BWP SRS joint triggering .

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

Fig. 1 is a schematic diagram of a wireless communication system according to an exemplary embodiment.

Fig. 2 is a schematic diagram of an SRS mapping area within a time slot according to an exemplary embodiment.

Fig. 3 is a flow chart showing a method for triggering an SRS according to an exemplary embodiment.

Fig. 4 is a flow chart showing a method for triggering an SRS according to an exemplary embodiment.

Fig. 5 is a block diagram of an SRS triggering device according to an exemplary embodiment.

Fig. 6 is a block diagram of an SRS triggering device according to an exemplary embodiment.

Fig. 7 is a block diagram showing a device for SRS triggering according to an exemplary embodiment.

Fig. 8 is a block diagram showing a device for SRS triggering according to an exemplary embodiment.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure.

The SRS triggering method provided by the embodiments of the present disclosure can be applied to the wireless communication system shown in FIG. 1 . Referring to FIG. 1 , the wireless communication system includes network devices and terminals. The terminal is connected to the network equipment through wireless resources, and performs data transmission.

It can be understood that the wireless communication system shown in FIG. 1 is only for schematic illustration, and the wireless communication system may also include other network devices, such as core network devices, wireless relay devices, and wireless backhaul devices, etc. Not shown in Figure 1. The embodiment of the present disclosure does not limit the number of network devices and terminals included in the wireless communication system.

It can be further understood that the wireless communication system in the embodiment of the present disclosure is a network that provides a wireless communication function. Wireless communication systems can use different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division multiple access (TDMA) , frequency division multiple access (FDMA), orthogonal frequency-division multiple access (OFDMA), single carrier frequency-division multiple access (single Carrier FDMA, SC-FDMA), carrier sense Multiple Access/Conflict Avoidance (Carrier Sense Multiple Access with Collision Avoidance). According to the capacity, speed, delay and other factors of different networks, the network can be divided into 2G (English: generation) network, 3G network, 4G network or future evolution network, such as 5G network, 5G network can also be called a new wireless network ( New Radio, NR). For convenience of description, the present disclosure sometimes simply refers to a wireless communication network as a network.

Further, the network equipment involved in this disclosure may also be referred to as radio access network equipment. The wireless access network device may be: a base station, an evolved base station (evolved node B, base station), a home base station, an access point (access point, AP) in a wireless fidelity (wireless fidelity, WIFI) system, a wireless relay Node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be gNB in the NR system, or it can also be a component or a part of equipment that constitutes a base station wait. It should be understood that in the embodiments of the present disclosure, no limitation is imposed on the specific technology and specific device form adopted by the network device. In the present disclosure, a network device can provide communication coverage for a specific geographic area, and can communicate with terminals located in the coverage area (cell). In addition, when it is a vehicle-to-everything (V2X) communication system, the network device may also be a vehicle-mounted device.

Further, the terminals involved in this disclosure can also be referred to as terminal equipment, user equipment (User Equipment, UE), mobile station (Mobile Station, MS), mobile terminal (Mobile Terminal, MT), etc. A device providing voice and/or data connectivity, for example, a terminal may be a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminals are: Smartphone (Mobile Phone), Customer Premise Equipment (CPE), Pocket Personal Computer (PPC), PDA, Personal Digital Assistant (PDA) , laptops, tablets, wearable devices, or vehicle-mounted devices, etc. In addition, when it is a vehicle-to-everything (V2X) communication system, the terminal device may also be a vehicle-mounted device. It should be understood that the embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the terminal.

In related technologies, the network configures multiple uplink SRS resource sets for the terminal, and one resource set includes one or more SRS resources. Among them, in the 5G NR system, the uplink SRS can be configured, and the uplink SRS can be periodic SRS, semi-persistent SRS or aperiodic SRS. Narrowband or broadband, single port or multiport. The uplink SRS parameters are configured by the network device to the terminal, and include the number of ports, resource locations in the frequency domain, resource locations in the time domain, sequences, sequence cycle offsets, and the like. In a 5G NR system, SRS is mapped on up to six symbols of an uplink slot, as shown in Figure 2, which shows the SRS mapping area within a slot.

Wherein, the network device can configure multiple uplink SRS sets for the terminal, and one resource set includes one or more SRS resources. One SRS resource can be on N consecutive OFDM symbols, and N can occupy 1, 2, or 4 symbols.

In the latest standard version 17 (R17), it is defined that a terminal can send an SRS on any symbol, and the length of the SRS can also transmit a maximum of 14 symbols. The SRS resource set can be configured with different functions (usage). For example, it may include SRS for beam management, SRS for codebook-based transmission, SRS for non-codebook-based transmission, and SRS for antenna switching.

In standard version 16 (Rel-16), the aperiodic SRS is triggered by the SRS request indication field in the scheduling downlink control information (downlink control information, DCI) on the physical downlink control channel (physical downlink control channel, PDCCH).

In related technologies, the SRS resource set to be transmitted is represented by the SRS codepoint (codepoint)—that is, the value of the SRS request field. SRS resource sets with different functions can correspond to the same codepoint and be triggered by an SRS request indication DCI at the same time.

In R17, the SRS flexible enhancement method is supported. The SRS flexible enhancement method of R17 is defined as a DCI flexible indication scheme based on available time slots. The triggering of the SRS is based on adding the dynamic time slot offset indicated by the DCI on the basis of the semi-static time slot offset value. The RRC signaling configures multiple semi-static time slot offset values, and the newly introduced DCI is used to indicate a specific offset value among the multiple semi-static time slot offset values configured by RRC.

The SRS flexible trigger mode is compatible with the existing terminal implementation mode to the greatest extent, and at the same time realizes relatively flexible triggering of the SRS. This scheme improves the flexibility of triggering A-SRS (Aperiodic Sounding Reference Signal) while ensuring consistent behavior between network devices such as gNB and terminals to determine available slots depending on RRC configuration, while not considering any dynamic events. After the available time slots are determined, conflict handling between the triggered SRS resource set and other uplink signals/channels is performed.

In the SRS enhancement of R17, SRS triggering is supported without data scheduling and CSI reporting for DCI used for uplink data scheduling. For example, for DCI0-1 and DCI0-2 formats, SRS triggering without data scheduling and CSI reporting is supported. However, in this SRS triggering method, it is supported to trigger SRS on the active part of the bandwidth (Bandwidth Part BWP) of the current CC, but it cannot jointly (simultaneously) trigger SRS on different carriers (cross-carriers) and different BWPs (cross-BWP).

In view of this, the present disclosure provides an SRS triggering method, in which method, the SRS of the inactive BWP is scheduled through a non-data-scheduled DCI (also called non-scheduled DCI), and an instruction to trigger one or Carrier information and BWP information of multiple SRS resource sets. Based on the carrier information and BWP information of one or more SRS resource sets on the inactive BWP, the terminal jointly triggers different SRSs in multiple SRS resource sets on the inactive BWP on each of the multiple carriers in the carrier aggregation. Collection of resources.

Fig. 3 is a flow chart showing an SRS triggering method according to an exemplary embodiment. As shown in Fig. 3 , the SRS triggering method is used in a terminal and includes the following steps.

In step S11, non-scheduled DCI is obtained, and the non-scheduled DCI is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive BWP.

In step S12, based on the carrier information and the BWP information, one or more SRS resource sets are triggered on any BWP of any one of the one or more carriers.

In this disclosure, the carrier information and BWP information of one or more SRS resource sets triggered on the non-activated BWP are indicated by the non-scheduled DCI, so that the terminal can determine different SRS resources in multiple SRS resource sets based on the non-scheduled DCI Collected carrier information and BWP information, and then based on the carrier information and BWP information, on any BWP of any one of one or more carriers, jointly trigger one or more SRS resource sets to achieve cross-carrier and cross-BWP SRS joint trigger.

In an implementation manner of the present disclosure, the non-scheduled DCI includes an unused control information indication field. The carrier information and BWP information of one or more SRS resource sets on the inactive BWP are carried in the unused control information indication field. In other words, in this disclosure, the unused control information indication field in the non-scheduled DCI indicates the carrier information of one or more SRS resource sets on the inactive BWP and the information on the inactive BWP to jointly trigger the SRS resource set on the inactive BWP .

In the present disclosure, according to whether the terminal supports dynamic scheduling of the activated BWP capability, different ways may be used to indicate carrier information and inactive BWP information of multiple SRS resource sets.

On the one hand, in response to the terminal supporting dynamic scheduling to activate the BWP, that is, to support the use of DCI to change the activated BWP, the DCI includes a carrier information indicator field (carrier indicator) used to indicate the carrier information of multiple SRS resource sets on the activated BWP, and is used The BWP indicator field (Bandwidth part indicator) used to indicate the activation of the BWP.

In one embodiment, in this disclosure, in response to the fact that the carrier information indication field in the DCI does not indicate the carrier information of multiple SRS resource sets activated on the BWP, the DCI is a non-scheduled DCI. The carrier information indication field included in the non-scheduled DCI is an unused control information indication field, and the unused control information indication field is used to indicate the carrier information where the triggered SRS resource set is located.

In the present disclosure, the non-scheduled DCI includes an unused control information indication field. Wherein, the unused control information indication field includes the carrier information indication field. The carrier information indication field is used to indicate the carrier information corresponding to one or more SRS resource sets on the triggered inactive BWP.

In one embodiment, the carrier information indication field may be originally used to indicate the carrier information of multiple SRS resource sets on the activated BWP, but in the case that the carrier information corresponding to the activated BWP is not actually indicated, it indicates to trigger one on the inactive BWP. or carrier information of multiple SRS resource sets.

In another implementation manner, in response to the fact that the BWP indication field in the DCI of dynamically scheduled BWP switching does not indicate activation of the BWP, the DCI is a non-scheduled DCI. The BWP indication field included in the non-scheduled DCI can be used as an unused control information indication field to indicate the inactive BWP.

In the present disclosure, the non-scheduled DCI includes an unused control information indication field. Wherein, the unused control information indication field includes the BWP indication field for dynamically scheduling the active BWP, and the BWP indication field does not actually indicate the active BWP, but indicates the BWP information corresponding to one or more SRS resource sets on the inactive BWP.

In one embodiment of the present disclosure, the unused control information indication field included in the non-scheduled DCI is the carrier information indication field used to indicate the activation of the carrier information in the BWP but does not actually indicate the activation of the carrier information of the BWP, and is used to indicate the activation BWP but does not actually indicate the BWP indication field to activate BWP. Through the carrier information indication field and BWP indication field in non-scheduled DCI, jointly indicate the carrier and BWP where the triggered SRS is located, so as to realize the indication of multiple SRS resource sets across carriers and across BWPs, and realize the flexible triggering of SRS.

It can be understood that in the present disclosure, if the network device configures a carrier for the terminal, the carrier information indication field may not be used to indicate the carrier information, and the SRS resource information on the inactive BWP is indicated through the BWP indication field.

In this disclosure, in response to the fact that the terminal does not support using DCI to change the active BWP, the DCI does not include the BWP indication field for dynamically scheduling the active BWP, and the terminal will not interpret the BWP indication field. In this case, in this disclosure, an indication field different from the BWP indication field is used to indicate the inactive BWP information of multiple triggered SRS resource sets, so as to trigger multiple SRS resource sets on the inactive BWP.

In an example, in the present disclosure, a transmit power control (Transmit Power Control, TPC) indication field may be used to indicate the inactive BWP information of multiple triggered SRS resource sets. In another example, a redundancy version (Redundancy version, RV) indication field may be used to indicate the triggered inactive BWP information of multiple SRS resource sets. A plurality of BWPs are indicated by an indication field other than the BWP indication field, so as to implement switching of BWPs, and further implement triggering of SRS resource sets across BWPs.

In this disclosure, other indication fields than the BWP indication field include code points for indicating BWP information. The code point indicates the inactive BWP information of multiple SRS resource sets triggered. Wherein, the code point may be a redefined code point, or a reserved code point.

In an example, the present disclosure may redefine the code point indicating Time Domain Resource Allocation (TDRA), so as to indicate the inactive BWP information of multiple triggered SRS resource sets. Among them, in the present disclosure, the redefined code point can be used to indicate the handover inactive BWP information and carrier information, and then realize the indication of multiple SRS resource sets across carriers and BWPs, and realize the flexible triggering of SRS.

In another example, the present disclosure may indicate the inactive BWP information of the triggered multiple SRS resource sets by using a reserved code point in an indication field other than the BWP indication field. For example, the present disclosure may indicate the triggered inactive BWP information of multiple SRS resource sets through the reserved code point of the antenna port (antenna ports) indication field.

It can be understood that, in the present disclosure, the inactive BWP information of multiple triggered SRS resource sets may also be indicated by bit fields in other indication fields different from the BWP indication field.

In an implementation manner of the present disclosure, multiple triggered SRS resources may be jointly indicated to set carrier information and inactive BWP information.

In one example, in this disclosure, the carrier information indication field for indicating the carrier information in the activated BWP but not actually indicating the carrier information of the activated BWP may be used to indicate the carrier information of multiple SRS resource sets in the inactive BWP, and different from the BWP indication The other indication field of the domain indicates the inactive BWP.

For example, in the present disclosure, the carrier information indication field may be used to indicate the carrier information of multiple SRS resource sets in the inactive BWP, and the redefined code point or reserved code point in the indication field other than the BWP indication field may be used to indicate the inactive Activate the BWP to realize the indication of multiple SRS resource sets cross-carrier and cross-BWP, and realize the flexible triggering of SRS.

In another example, in this disclosure, the inactive BWP information and carrier information of multiple triggered SRS resource sets may also be indicated by using other indication fields different from the BWP indication field. For example, in this disclosure, by redefining code points or reserved code points, the inactive BWP information and carrier information of multiple SRS resource sets that are triggered can be jointly indicated to realize cross-carrier and cross-BWP multiple SRS resource sets. Indicates to realize the flexible triggering of SRS.

In the SRS triggering method provided in the present disclosure, on the one hand, the non-scheduled DCI may be used for uplink data scheduling, but the uplink data and CSI are not actually scheduled. For example, the non-scheduled DCI in this disclosure may be DCI0-1 or DCI0-2. That is, the present disclosure allows to use DCI0-1 or DCI0-2 to trigger SRS inactive BWP without data scheduling or CSI reporting.

In the SRS triggering method provided in the present disclosure, on the other hand, the non-scheduled DCI may be used for downlink data scheduling, but the downlink data is not actually scheduled. For example, the non-scheduled DCI in this disclosure may be DCI1-1 or DCI1-2. That is, the present disclosure allows the use of DCI1-1 or DCI1-2 to perform SRS inactive BWP triggering without data scheduling.

Further, in the embodiments of the present disclosure, the terminal may adopt the SRS triggering method involved in the above-mentioned embodiments of the present disclosure under the condition that the non-scheduled DCI is supported to schedule the SRS resource capability on the inactive BWP.

In the present disclosure, the terminal can report terminal capability information to the network device, and the terminal capability information is used to indicate whether to support the capability of scheduling SRS resources on the non-activated BWP through non-scheduled DCI. The network device receives the terminal capability information reported by the terminal. When the network device determines that the terminal supports non-scheduled DCI to schedule the SRS of the non-activated BWP, the non-scheduled DCI is used to schedule the SRS resources on the non-activated BWP for the terminal, so as to realize the cross-carrier and cross-BWP multiple SRS resource sets Indicates to realize the flexible triggering of SRS.

Based on the same idea, the present disclosure also provides an SRS triggering method applied to a network device.

Fig. 4 is a flow chart showing an SRS triggering method according to an exemplary embodiment. As shown in Fig. 4 , the SRS triggering method is used in a network device and includes the following steps.

In step S21, non-scheduled DCI is sent. Among them, the non-scheduled DCI is used to indicate the carrier information and BWP information that trigger one or more SRS resource sets on the inactive BWP.

In one embodiment, the non-scheduled DCI includes an unused control information indication field. The carrier information and BWP information of one or more SRS resource sets activated on the BWP are carried in the unused control information indication field.

In this disclosure, the unused control information indication field in the non-scheduled DCI indicates the carrier information of one or more SRS resource sets on the inactive BWP and the information on the inactive BWP, so as to jointly trigger the SRS resource set on the inactive BWP.

In an embodiment, the unused control information indication field includes a carrier information indication field, and the carrier information indication field is used to indicate carrier information corresponding to triggering one or more SRS resource sets on the inactive BWP.

In one implementation manner, the terminal supports dynamic scheduling of the active BWP, that is, supports using DCI to change the active BWP. The unused control information indication field in non-scheduled DCI includes the BWP indication field used for dynamic scheduling to activate BWP. The BWP indication field is used to indicate the BWP information corresponding to one or more SRS resource sets on the triggered inactive BWP.

In one embodiment, the BWP indication field in the DCI used to dynamically schedule the active BWP does not indicate the BWP information in the active BWP. The unused control information indication fields in non-scheduled DCI include other indication fields than the BWP indication field. The other indication field is used to indicate the BWP information that jointly triggers multiple SRS resource sets on the inactive BWP.

In an example, the other indication field may be a TPC indication field, and the TPC indication field indicates inactive BWP information of multiple triggered SRS resource sets. In another example, the other indication field may be an RV indication field, and the (RV) indication field indicates inactive BWP information of multiple triggered SRS resource sets.

In the embodiment of the present disclosure, the other indication fields mentioned above include a code point for indicating BWP information. The code point includes at least one of the following: a redefined code point; a reserved code point.

In an example, the code point used to indicate the BWP information in the present disclosure may be a code point that redefines the code point indicating TDRA. The redefined code point is used to indicate the triggered inactive BWP information of multiple SRS resource sets. Among them, in the present disclosure, the redefined code point can be used to indicate the handover inactive BWP information and carrier information, and then realize the indication of multiple SRS resource sets across carriers and BWPs, and realize the flexible triggering of SRS.

In another example, the code point used to indicate the BWP information in the present disclosure may be a reserved code point of another indication field different from the BWP indication field. The reserved code point indicates inactive BWP information of multiple triggered SRS resource sets. For example, the present disclosure may indicate the triggered inactive BWP information of multiple SRS resource sets through the reserved code point of the antenna port (antenna ports) indication field.

In the embodiment of the present disclosure, the terminal may receive terminal capability information, and the terminal capability information is used to indicate whether to support the capability of triggering SRS resources on the non-activated BWP through non-scheduled DCI. When the network device determines that the terminal supports non-scheduled DCI to schedule the SRS of the non-activated BWP, the non-scheduled DCI is used to schedule the SRS resources on the non-activated BWP for the terminal, so as to realize the cross-carrier and cross-BWP multiple SRS resource sets Instructions to realize flexible triggering of SRS.

It can be understood that the SRS triggering method applied to the network device in the embodiment of the present disclosure is similar to the SRS triggering method applied to the terminal. Therefore, the description of the SRS triggering method applied to the network device is not detailed enough. Reference may be made to the related content of the SRS triggering method applied to the terminal, which will not be described in detail here.

It can be further understood that the SRS triggering method provided by the embodiments of the present disclosure is applicable to a process in which a terminal interacts with a network device to implement SRS triggering control. During the interaction between the terminal and the network device to implement the SRS triggering control process, the terminal and the network device have the relevant functions in the foregoing embodiments.

It should be noted that those skilled in the art can understand that the various implementation modes/embodiments mentioned above in the embodiments of the present disclosure can be used in conjunction with the foregoing embodiments, or can be used independently. Whether it is used alone or in combination with the foregoing embodiments, its implementation principles are similar. During the implementation of the present disclosure, some embodiments are described in the manner of being used together. Of course, those skilled in the art can understand that such an illustration is not a limitation to the embodiments of the present disclosure.

Based on the same idea, the embodiment of the present disclosure also provides an SRS triggering device.

It can be understood that, in order to realize the above functions, the SRS triggering device provided by the embodiments of the present disclosure includes corresponding hardware structures and/or software modules for performing various functions. Combining the units and algorithm steps of each example disclosed in the embodiments of the present disclosure, the embodiments of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the technical solutions of the embodiments of the present disclosure.

Fig. 5 is a block diagram of an SRS triggering device according to an exemplary embodiment. Referring to FIG. 5 , the SRS triggering device 100 includes an acquisition unit 101 and a processing unit 102 . Wherein, the SRS triggering device 100 may be provided as the terminal involved in the above embodiments.

The acquiring unit 101 is configured to acquire downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP. The processing unit 102 is configured to jointly trigger one or more SRS resource sets on any BWP of any one of the one or more carriers based on the carrier information and the BWP information.

In one embodiment, the downlink control information includes an unused control information indication field, and carrier information and BWP information are carried in the unused control information indication field.

In an implementation manner, the unused control information indication field includes a carrier information indication field. The carrier information indication field is used to indicate the carrier information corresponding to one or more SRS resource sets on the triggered inactive BWP.

In an implementation manner, the downlink control information includes a BWP indication field for dynamically scheduling and activating the BWP. The unused control information indication field includes a BWP indication field, and the BWP indication field is used to indicate the BWP information corresponding to trigger one or more SRS resource sets on the inactive BWP.

In an implementation manner, the downlink control information does not include a BWP indication field for dynamically scheduling and activating the BWP. The unused control information indication field includes other indication fields than the BWP indication field. The other indication fields are used to indicate the BWP information that jointly triggers multiple SRS resource sets on the inactive BWP.

In an implementation manner, the other indication fields include code points for indicating BWP information.

The code point includes at least one of the following: redefining the code point. Reserve code points.

In one implementation manner, the downlink control information includes downlink control information used for scheduling uplink data but not actually scheduling uplink data and channel state information.

In one embodiment, the downlink control information includes the downlink control information used for downlink data scheduling, but the downlink data is not actually scheduled.

In an implementation manner, the SRS triggering device 100 further includes a reporting unit 103 . The reporting unit 103 is configured to: report terminal capability information, and the terminal capability information is used to indicate whether to support the capability of triggering SRS resources on the inactive BWP through non-data-scheduled downlink control information.

Fig. 6 is a block diagram of an SRS triggering device according to an exemplary embodiment. Referring to FIG. 6 , the SRS triggering device 200 includes a sending unit 201 . Wherein, the SRS triggering apparatus 200 may be provided as the network device involved in the foregoing embodiments.

The sending unit 201 is configured to send downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP.

In an implementation manner, the downlink control information does not include a BWP indication field for dynamically scheduling and activating the BWP.

The unused control information indication field includes other indication fields than the BWP indication field. The other indication fields are used to indicate the BWP information that jointly triggers multiple SRS resource sets on the inactive BWP.

In one embodiment, the downlink control information includes downlink control information used for downlink data scheduling, but the downlink data is not actually scheduled.

In an implementation manner, the SRS triggering device further includes a receiving unit 202 . The receiving unit 202 is configured to receive terminal capability information, and the terminal capability information is used to indicate whether to support the capability of triggering SRS resources on an inactive BWP through non-data-scheduled downlink control information.

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Fig. 7 is a block diagram of an apparatus 300 for SRS triggering according to an exemplary embodiment. For example, the apparatus 300 may be provided as a terminal. For example, the apparatus 300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, and the like.

7, apparatus 300 may include one or more of the following components: processing component 302, memory 304, power component 306, multimedia component 308, audio component 310, input/output (I/O) interface 312, sensor component 314, and communication component 316 .

The processing component 302 generally controls the overall operations of the device 300, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 302 may include one or more modules that facilitate interaction between processing component 302 and other components. For example, processing component 302 may include a multimedia module to facilitate interaction between multimedia component 308 and processing component 302 .

The memory 304 is configured to store various types of data to support operations at the device 300 . Examples of such data include instructions for any application or method operating on device 300, contact data, phonebook data, messages, pictures, videos, and the like. The memory 304 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

Power component 306 provides power to various components of device 300 . Power components 306 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 300 .

The multimedia component 308 includes a screen that provides an output interface between the device 300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 308 includes a front camera and/or a rear camera. When the device 300 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 310 is configured to output and/or input audio signals. For example, the audio component 310 includes a microphone (MIC), which is configured to receive external audio signals when the device 300 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 304 or sent via communication component 316 . In some embodiments, the audio component 310 also includes a speaker for outputting audio signals.

The I/O interface 312 provides an interface between the processing component 302 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 314 includes one or more sensors for providing various aspects of status assessment for device 300 . For example, the sensor component 314 can detect the open/closed state of the device 300, the relative positioning of components, such as the display and keypad of the device 300, and the sensor component 314 can also detect a change in the position of the device 300 or a component of the device 300 , the presence or absence of user contact with the device 300 , the device 300 orientation or acceleration/deceleration and the temperature change of the device 300 . The sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 314 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 316 is configured to facilitate wired or wireless communication between the apparatus 300 and other devices. The device 300 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 316 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 300 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods described above.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 304 including instructions, which can be executed by the processor 320 of the device 300 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

Fig. 8 is a block diagram of an apparatus 400 for SRS triggering according to an exemplary embodiment. For example, apparatus 400 may be provided as a network device. Referring to FIG. 8 , apparatus 400 includes processing component 422 , which further includes one or more processors, and a memory resource represented by memory 432 for storing instructions executable by processing component 422 , such as application programs. The application program stored in memory 432 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 422 is configured to execute instructions to perform the above method.

Device 400 may also include a power component 426 configured to perform power management of device 400 , a wired or wireless network interface 450 configured to connect device 400 to a network, and an input-output (I/O) interface 458 . The device 400 can operate based on an operating system stored in the memory 432, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as the memory 432 including instructions, which can be executed by the processing component 422 of the apparatus 400 to implement the above method. For example, the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

It can be further understood that "plurality" in the present disclosure refers to two or more, and other quantifiers are similar thereto. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship. The singular forms "a", "said" and "the" are also intended to include the plural unless the context clearly dictates otherwise.

It can be further understood that the terms "first", "second", etc. are used to describe various information, but the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another, and do not imply a specific order or degree of importance. In fact, expressions such as "first" and "second" can be used interchangeably. For example, without departing from the scope of the present disclosure, first information may also be called second information, and similarly, second information may also be called first information.

It can be further understood that although operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring that these operations be performed in the specific order shown or in a serial order, or that Do all of the operations shown to get the desired result. In certain circumstances, multitasking and parallel processing may be advantageous.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure .

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the scope of the appended claims.

Claims

An SRS triggering method, characterized in that it is applied to a terminal, including:

Acquiring downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP;

Based on the carrier information and the BWP information, the one or more SRS resource sets are triggered on any BWP of any one of the one or more carriers.
The method according to claim 1, wherein the downlink control information includes an unused control information indication field, and the carrier information and the BWP information are carried in the unused control information indication field.
The method according to claim 2, wherein the unused control information indication field includes a carrier information indication field;

The carrier information indication field is used to indicate the carrier information corresponding to one or more SRS resource sets on the triggered inactive BWP.
The method according to claim 2 or 3, wherein the downlink control information includes a BWP indication field for dynamically scheduling and activating the BWP;

The unused control information indication field includes the BWP indication field, and the BWP indication field is used to indicate the BWP information corresponding to one or more sets of SRS resources that trigger the inactive BWP.
The method according to claim 2 or 3, wherein the downlink control information does not include a BWP indication field for dynamically scheduling and activating the BWP;

The unused control information indication field includes other indication fields different from the BWP indication field;

The other indication field is used to indicate the BWP information of jointly triggering multiple SRS resource sets on the inactive BWP.
The method according to claim 5, wherein the BWP information used to indicate joint triggering of multiple SRS resource sets on the inactive BWP in the other indication field includes a code point used to indicate the BWP information;

The code point includes at least one of the following:

redefine code point;

Reserve code points.
The method according to claim 1, wherein the downlink control information includes downlink control information used for scheduling uplink data but not actually scheduling uplink data and channel state information.
The method according to claim 1, wherein the downlink control information includes downlink control information used for scheduling downlink data but actually not scheduling downlink data.
The method according to claim 1, further comprising:

Report terminal capability information, where the terminal capability information is used to indicate whether to support the capability of triggering the SRS resource on the inactive BWP through the downlink control information of the non-data scheduling.
A method for triggering SRS, characterized in that it is applied to network equipment, including:

Sending downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the BWP of the inactive partial bandwidth.
The method according to claim 10, wherein the downlink control information includes an unused control information indication field, and the carrier information and the BWP information are carried in the unused control information indication field.
The method according to claim 11, wherein the unused control information indication field includes a carrier information indication field;

The carrier information indication field is used to indicate the carrier information corresponding to one or more SRS resource sets on the triggered inactive BWP.
The method according to claim 11 or 12, wherein the downlink control information includes a BWP indication field for dynamically scheduling and activating the BWP;

The unused control information indication field includes the BWP indication field, and the BWP indication field is used to indicate the BWP information corresponding to one or more sets of SRS resources that trigger the inactive BWP.
The method according to claim 11 or 12, wherein the downlink control information does not include a BWP indication field for dynamically scheduling and activating the BWP;

The unused control information indication field includes other indication fields different from the BWP indication field;

The other indication field is used to indicate the BWP information that triggers multiple SRS resource sets on the inactive BWP.
The method according to claim 14, wherein the BWP information used to indicate joint triggering of multiple SRS resource sets on the inactive BWP in the other indication field includes a code point used to indicate the BWP information;

The code point includes at least one of the following:

redefine code point;

Reserve code points.
The method according to claim 10, wherein the downlink control information includes downlink control information used for scheduling uplink data but not actually scheduling uplink data and channel state information.
The method according to claim 10, wherein the downlink control information includes downlink control information used for downlink data scheduling, but the downlink data is not actually scheduled.
The method according to claim 10, characterized in that the method further comprises:

Receive terminal capability information, where the terminal capability information is used to indicate whether to support the capability of triggering SRS resources on the inactive BWP through non-data-scheduled downlink control information.
A kind of SRS trigger device, is characterized in that, comprises:

An acquiring unit, configured to acquire downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the inactive partial bandwidth BWP;

A processing unit, configured to trigger the one or more sets of SRS resources on any BWP of any one of the one or more carriers based on the carrier information and the BWP information.
The device according to claim 19, wherein the downlink control information includes an unused control information indication field, and the carrier information and the BWP information are carried in the unused control information indication field.
A kind of SRS trigger device, is characterized in that, comprises:

A sending unit, configured to send downlink control information for non-data scheduling, where the downlink control information for non-data scheduling is used to indicate carrier information and BWP information that trigger one or more SRS resource sets on the BWP of the inactive partial bandwidth.
A kind of SRS trigger device, is characterized in that, comprises:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to: execute the method described in any one of claims 1-9.
A kind of SRS trigger device, is characterized in that, comprises:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured to: execute the method described in any one of claims 10-18.
A storage medium, characterized in that instructions are stored in the storage medium, and when the instructions are executed by a processor of the terminal, the terminal can execute the method described in any one of claims 1-9.
A storage medium, characterized in that instructions are stored in the storage medium, and when the instructions are executed by a processor of the network device, the network device can execute the method described in any one of claims 10 to 18.