WO2021174558A1 - 资源指示方法、终端设备和网络设备 - Google Patents

资源指示方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2021174558A1
WO2021174558A1 PCT/CN2020/078313 CN2020078313W WO2021174558A1 WO 2021174558 A1 WO2021174558 A1 WO 2021174558A1 CN 2020078313 W CN2020078313 W CN 2020078313W WO 2021174558 A1 WO2021174558 A1 WO 2021174558A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
config
mac
spatial relationship
terminal device
Prior art date
Application number
PCT/CN2020/078313
Other languages
English (en)
French (fr)
Inventor
付喆
徐婧
林亚男
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to KR1020227009522A priority Critical patent/KR20220152184A/ko
Priority to PCT/CN2020/078313 priority patent/WO2021174558A1/zh
Priority to CN202210477741.3A priority patent/CN114793363B/zh
Priority to EP20923464.0A priority patent/EP4017185A4/en
Priority to JP2022533239A priority patent/JP2023516531A/ja
Priority to CN202080059216.9A priority patent/CN114287157A/zh
Publication of WO2021174558A1 publication Critical patent/WO2021174558A1/zh
Priority to US17/654,540 priority patent/US20220201506A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/046—Wireless resource allocation based on the type of the allocated resource the resource being in the space domain, e.g. beams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands

Definitions

  • This application relates to the field of communications, and more specifically, to a resource indication method, terminal equipment, and network equipment.
  • the requirements of the fifth-generation wireless communication technology 5G include three application scenarios: enhanced mobile broadband eMBB, massive machine communication mMTC, and high-reliability and low-latency communication uRLLC. Furthermore, the requirements of 5G Industrial Internet of Things (IIoT) include supporting the transmission of services such as Industrial Automation (Factory Automation), Transmission Automation (Transport Industry), and Intelligent Power Distribution (Electrical Power Distribution) in 5G systems.
  • Industrial Automation Fractory Automation
  • Transmission Automation Transmission Automation
  • Intelligent Power Distribution Electronic Power Distribution
  • the IIoT system can support the transmission of URLLC services and eMBB services, and in order to support different services, it is sometimes necessary to configure multiple sets of resources for terminal devices. Compared with the situation where only one set of resources is configured in the past, how to implement multiple sets of resource information Accurate instructions are currently a problem that needs to be resolved.
  • embodiments of the present application provide a resource indication method, terminal device, and network device, which can be used to accurately indicate multiple sets of resource information.
  • the embodiment of the present application provides a resource indication method, which is applied to a terminal device, and includes:
  • the terminal device receives first indication information, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config;
  • the terminal device determines at least one PUCCH-config corresponding to the spatial relationship information among multiple PUCCH-configs according to the first indication information.
  • the embodiment of the present application provides a resource indication method, which is applied to a network device, and includes:
  • the network device sends first indication information to the terminal device, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config.
  • An embodiment of the present application also provides a terminal device, including:
  • a receiving module configured to receive first indication information, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config;
  • the determining module is configured to determine at least one PUCCH-config corresponding to the spatial relationship information among multiple PUCCH-configs according to the first indication information.
  • the embodiment of the present application also provides a network device, including:
  • the sending module is configured to send first indication information to the terminal device, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config.
  • An embodiment of the present application also provides a terminal device, including: a processor and a memory, the memory is used to store a computer program, the processor calls and runs the computer program stored in the memory, and executes the resource instruction as described above method.
  • An embodiment of the present application also provides a network device, including: a processor and a memory, the memory is used to store a computer program, the processor calls and runs the computer program stored in the memory, and executes the resource instruction as described above method.
  • An embodiment of the present application also provides a chip, including a processor, configured to call and run a computer program from a memory, so that the device installed with the chip executes the resource indication method as described above.
  • An embodiment of the present application also provides a computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the resource indication method as described above.
  • the embodiments of the present application also provide a computer program product, including computer program instructions, wherein the computer program instructions cause a computer to execute the resource indication method as described above.
  • the embodiments of the present application also provide a computer program that enables a computer to execute the resource indication method as described above.
  • the terminal device can distinguish the PUCCH configuration corresponding to the spatial relationship information according to the first indication information, and can clearly indicate the PUCCH configuration corresponding to the spatial relationship information when multiple PUCCH configurations are configured, eliminating the need for the terminal device and There may be ambiguities in understanding between network devices.
  • Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
  • Figure 2 is a schematic diagram of a PUCCH spatial relationship activation/deactivation MAC CE format.
  • FIG. 3 is a flowchart of a method for indicating resources on a terminal device side according to an embodiment of the present application.
  • Fig. 4 is a flowchart of a method for indicating resources on a network device side according to an embodiment of the present application.
  • Figures 5-8 are schematic diagrams of the improved PUCCH spatial relationship activation/deactivation MAC CE format of multiple embodiments of the present application.
  • FIG. 9 is a schematic structural block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural block diagram of a network device according to an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a chip of an embodiment of the present application.
  • FIG. 13 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NR system evolution system LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum
  • NR NR-based access to unlicensed spectrum
  • NR-U non-terrestrial communication network
  • UMTS Universal Mobile Telecommunication System
  • UMTS wireless local area network
  • WLAN Wireless Local Area Networks
  • WLAN wireless fidelity
  • WiFi Fifth-generation communication
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC machine type communication
  • V2V vehicle to vehicle
  • V2X vehicle to everything
  • the communication system in the embodiments of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, can also be applied to a dual connectivity (DC) scenario, and can also be applied to a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC dual connectivity
  • SA standalone
  • the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
  • the terminal equipment may also be referred to as User Equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, and remote station. Station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • the terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, and personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or in the future Terminal equipment in the evolved Public Land Mobile Network (PLMN) network.
  • STAION, ST station
  • WLAN Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • land including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • First class can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites).
  • the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, and wireless terminal equipment in smart grid , Wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • Mobile Phone Mobile Phone
  • a tablet computer Pad
  • a computer with wireless transceiver function a virtual reality (VR) terminal device
  • an augmented reality (Augmented Reality, AR) terminal Equipment Wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, and wireless terminal equipment in smart grid , Wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
  • AR Augmented Reality
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • the network device may be a device used to communicate with mobile devices, the network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA , It can also be a base station (NodeB, NB) in WCDMA, or an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or vehicle equipment, wearable devices, and NR networks Network equipment (gNB) in the PLMN network or network equipment in the PLMN network that will evolve in the future.
  • AP access point
  • BTS Base Transceiver Station
  • NodeB base station
  • eNB evolved base station
  • gNB Network Equipment
  • the network device may have mobile characteristics, for example, the network device may be a mobile device.
  • the network equipment can be a satellite or a balloon station.
  • the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, or a high elliptical orbit (High Elliptical Orbit, HEO). ) Satellite etc.
  • the network device may also be a base station installed in a location such as land or water.
  • the network equipment may provide services for the cell, and the terminal equipment communicates with the network equipment through the transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network equipment ( For example, the cell corresponding to the base station.
  • the cell can belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here can include: Metro cell, Micro cell, and Pico cell. Pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.
  • FIG. 1 schematically shows one network device 1100 and two terminal devices 1200.
  • the wireless communication system 1000 may include multiple network devices 1100, and the coverage of each network device 1100 may include other numbers
  • the terminal device of this application does not limit this.
  • the wireless communication system 1000 shown in FIG. 1 may also include other network entities such as mobility management entities (Mobility Management Entity, MME), access and mobility management functions (Access and Mobility Management Function, AMF).
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the base station can configure one or more corresponding PUCCH-config, and the corresponding configuration will be configured in PUCCH-config PUCCH resources.
  • the base station when the base station configures the PUCCH resource, it can be configured according to the PUCCH resource set (PUCCH-ResourceSet), or according to the PUCCH resource (PUCCH-Resource). Among them, for each PUCCH resource set, a corresponding PUCCH resource set identifier ID (PUCCH-ResourceSetId) and at least one PUCCH resource are configured. For each PUCCH resource, a corresponding PUCCH resource ID (PUCCH-ResourceId) and a specific PUCCH resource are configured. Among them, specific PUCCH resources can be configured according to the PUCCH format (format), and when the PUCCH format is configured, at least the PUCCH resource length and the offset parameter of the PUCCH resource relative to the reference point are indicated.
  • PUCCH resource set for each PUCCH resource set, a corresponding PUCCH resource set identifier ID (PUCCH-ResourceSetId) and at least one PUCCH resource are configured.
  • PUCCH resource set for each P
  • the base station when configuring PUCCH-config, the base station will also configure one or more sets of PUCCH Spatial Relation Info (PUCCH Spatial Relation Info) for configuring the spatial relationship between Reference Signal (RS) and PUCCH.
  • PUCCH Spatial Relation Info is used to configure the corresponding spatial setting for PUCCH transmission (the spatial setting for PUCCH transmission, such as the used RS) and the PUCCH power control parameters (the parameters for PUCCH power control).
  • Each set of PUCCH spatial relationship information includes PUCCH spatial relationship information ID (SpatialRelationInfoId).
  • MAC CE needs to be used to activate or indicate which set of PUCCH spatial relationship information is used.
  • Figure 2 shows a "PUCCH spatial relationship activation/deactivation MAC CE" (PUCCH spatial relation Activation/Deactivation MAC CE) format, which can indicate the elements in the PUCCH spatial relationship information list (list) The activation status.
  • PUCCH spatial relationship information list list
  • the PUCCH spatial relationship activation/deactivation MAC CE format illustrated in FIG. 2 can be identified by a MAC subheader (MAC subheader) with a specific logical channel identifier LCID.
  • the size of the MAC CE is 24 bits, including the serving cell ID (Serving Cell ID).
  • the Cell ID field, BWP ID field, PUCCH Resource ID field, Si field and R field have the following meanings:
  • ⁇ Serving Cell ID field indicates the identity of the serving cell corresponding to the MAC CE, and the length of this field is 7 bits.
  • the BWP ID field indicates an uplink BWP
  • the MAC CE is applied to the uplink BWP as the code bit of the specific DCI bandwidth part indicator field
  • the BWP ID field is 2 bits in length.
  • ⁇ PUCCH Resource ID field contains the identifier of the PUCCH resource ID identified by PUCCH-ResourceId, and the length of this field is 7 bits.
  • the S i field For the S i field, if there is a PUCCH spatial relationship information identified by PUCCH-SpatialRelationInfoId and configured for the uplink BWP indicated by the above BWP ID field, the S i field indicates that the PUCCH-SpatialRelationInfoId is the PUCCH spatial relationship corresponding to i+1 The activation status of the information; otherwise, the MAC entity ignores the S i field. Among them, if the above PUCCH spatial relationship information exists,
  • the above describes the PUCCH-config information currently configured by the base station for the UE.
  • the PUCCH spatial relationship activation/deactivation MAC CE shown in FIG. 2 can be used to indicate the PUCCH spatial relationship activation or deactivation information corresponding to the PUCCH-config.
  • the base station in order to support different services, it is possible for the base station to configure multiple PUCCH-config information for a BWP.
  • PUCCH-config information for a BWP.
  • -config, and another PUCCH-config configuration is used in the URLLC service.
  • the inventor of the present application has conducted in-depth research and found that when a BWP supports or is configured with multiple PUCCH-configs, the PUCCH spatial relationship activation/deactivation MAC CE described above cannot clearly indicate the activated PUCCH.
  • the spatial relationship belongs to which PUCCH-config among multiple PUCCH-configs, which will cause the problem of inconsistent understanding between the UE and the base station, resulting in a decrease in system performance.
  • an embodiment of the present application provides a resource indication method, which is applied to a terminal device.
  • the method includes:
  • a terminal device receives first indication information, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config;
  • the terminal device determines at least one PUCCH-config corresponding to the spatial relationship information among multiple PUCCH-configs according to the first indication information.
  • an embodiment of the present application also provides a resource indication method, which is applied to a network device.
  • the method includes:
  • a network device sends first indication information to a terminal device, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config.
  • the embodiment of the present application can separately indicate the spatial relationship information corresponding to multiple PUCCH-configs, such as spatial relationship activation or deactivation information, through the first instruction information, and the terminal device can distinguish the activated PUCCH spatial relationship correspondences according to the first instruction information. Therefore, it can avoid the problem of which PUCCH config of multiple PUCCH configs corresponds to the spatial relationship information indicated by the previous instructions, and eliminate the possible ambiguity between terminal equipment and network equipment
  • the network device may configure multiple PUCCH-configs for the terminal device, and each PUCCH-config information includes at least one set of spatial relationship information.
  • the terminal device receives multiple PUCCH-configs configured by the network device, it can perform corresponding PUCCH resource configuration according to the multiple PUCCH-configs.
  • the base station can configure multiple sets of PUCCH resources for the UE, and send multiple sets of PUCCH-config corresponding to the multiple sets of PUCCH resources to the UE, where each PUCCH -config can include at least one of the following items:
  • 1PUCCH resource set PUCCH resource set which includes PUCCH resource set ID and one or more PUCCH resources, and each PUCCH resource is configured with a PUCCH resource ID and specific resources.
  • 2PUCCH resource PUCCH resource which corresponds to a configured PUCCH resource ID and specific resources.
  • PUCCH-SpatialRelationInfo One or more sets of PUCCH spatial relationship information PUCCH-SpatialRelationInfo, where each set of PUCCH-SpatialRelationInfo includes the corresponding SpatialRelationInfoId and the corresponding RS configuration information.
  • the terminal device after performing corresponding PUCCH resource configuration according to the multiple PUCCH-configs, if the terminal device receives the first indication information, it needs to determine one or more sets of spatial relationships indicated in the first indication information The information corresponds to which PUCCH-config among multiple PUCCH-configs.
  • the first indication information includes a first MAC CE
  • the first MAC CE carries one or more sets of spatial relationship information corresponding to one or more PUCCH information, respectively. Therefore, the first MAC CE can indicate the spatial relationship information corresponding to at least one PUCCH-config in the multiple PUCCH-configs configured by the terminal device. In other words, the first MAC CE can indicate the first of the multiple PUCCH-configs.
  • multiple MAC CE formats are designed to carry the above-mentioned indication information.
  • the used MAC CE conforms to the first type PUCCH spatial relationship activation/deactivation MAC CE format; in other embodiments, the used MAC CE conforms to the second type PUCCH spatial relationship activation/deactivation MAC CE format .
  • the terminal equipment parses the MAC CE in different ways.
  • the MAC CE can implicitly or explicitly indicate the PUCCH-config or codebook corresponding to the activated/deactivated spatial relationship.
  • FIG 5 schematically shows one kind of application of the present embodiment MAC CE format, wherein the information comprises a plurality of PUCCH - identifying a plurality of P i - PUCCH spatial relationship information sets respectively corresponding to (S located in rows), And multiple PUCCH resource identifiers PUCCH Resource IDs respectively corresponding to each other.
  • the MAC CE format used in this embodiment belongs to an improved PUCCH spatial relationship activation/deactivation MAC CE format.
  • MAC CE indicates the spatial relationship information in a PUCCH S line was also used to indicate a plurality of PUCCH information field P, FIG. 5 identified as P i.
  • P i PUCCH information field
  • R is substituted with the new domain P, P i of a different place in the P field value, information may indicate that different PUCCH.
  • the MAC CE includes the PUCCH config index/id of each PUCCH-config and the activation or deactivation information of the spatial relationship corresponding to each PUCCH-config.
  • the PUCCH information refers to the PUCCH config identifier PUCCH config index/id, where different PUCCH config index/id corresponds to different PUCCH-config.
  • the correspondence relationship between PUCCH config index/id and spatial relationship information can be determined, that is, the correspondence relationship between PUCCH-config and spatial relationship information is determined.
  • P i indicates PUCCH config index / id. For example, if P i is 0, indicating that the representative PUCCH config index / id 0 (also referred to as other values, such as 1) PUCCH-config, the PUCCH-config spatial relationship information corresponding to the take value P i 0 S immediately adjacent rows.
  • P i is 1, indicating that the representative PUCCH config index / id 1 (also referred to as other values, such as 2) the PUCCH-config, the PUCCH-config spatial relationship information corresponding to the the value of P i 1 S immediately adjacent rows.
  • the MAC CE of this embodiment uses designated bits (for example, P bits) to indicate the first PUCCH config index, and uses a designated row (for example, S row) adjacent to the designated bit to indicate the first PUCCH config index.
  • designated bits for example, P bits
  • a designated row for example, S row
  • the MAC CE uses the P domain to identify each PUCCH config index/id (corresponding to multiple PUCCH-configs), and at the same time indicates the activated or deactivated PUCCH Spatial relationship information and PUCCH Resource ID information.
  • the value of the P field can be a preset value, such as 0, 1, 2, 3, 4, 5, 6, or 7, or it can be other values that can distinguish PUCCH-config, corresponding to S i in row S The value of can be 0 or 1.
  • the length of the MAC CE is related to the number of PUCCH-config.
  • the length of the MAC CE can be related to the number of PUCCH-config configured by the terminal, or it can also be related to the PUCCH-config activated at the same time. The number is related.
  • the length of the MAC CE may also be determined. In some embodiments, the length of the MAC CE is fixed.
  • each P bit represents the PUCCH config id/index of a PUCCH-config. Because an explicit indication is adopted, the value of each P bit is completely carried with the corresponding PUCCH spatial relationship information, so each set of There is no special requirement for the placing order of the PUCCH spatial relationship information, and it can be placed in a random order or in a certain order. Among them, the order that can be taken is, for example, the size order of multiple PUCCH config index/id, such as ascending or descending order.
  • the serving cell and/or BWP corresponding to different PUCCH-configs may be the same or different, they can be combined through the above MAC CE Give instructions.
  • the serving cell ID and BWP ID can be placed in the corresponding fields before the first P domain as shown in Figure 5; if different PUCCH-configs At least one of the corresponding serving cell Serving Cell and BWP is different, and corresponding fields can be added before the corresponding P domain to place the corresponding serving cell ID and BWP ID to make the indication information comprehensive.
  • the new MAC CE format can carry accurate and comprehensive resource indication information.
  • the first type PUCCH spatial relationship activation/deactivation MAC CE format implicit indication
  • Fig. 6 schematically shows another MAC CE format according to an embodiment of the present application, including multiple sets of PUCCH spatial relationship information (located in row S) and multiple corresponding PUCCH Resource IDs.
  • the MAC CE format of the embodiment in FIG. 6 also belongs to the improved PUCCH spatial relationship activation/deactivation MAC CE format. Compared with the embodiment in FIG. 5, the main difference of this embodiment lies in:
  • the MAC CE format of this embodiment does not include the P field, but still retains the original reserved bits (such as the R field).
  • This embodiment does not give an explicit indication to PUCCH information, but adopts an implicit indication to realize resource indication.
  • multiple sets of PUCCH spatial relationship information are placed in a predetermined order.
  • the predetermined order refers to the ordering of the multiple PUCCH config index/id corresponding to the multiple PUCCH spatial relationship information, such as ascending order or descending order (that is, sorting from small to large or from large to small). Sort).
  • the UE can determine the corresponding PUCCH config according to the sequence of multiple sets of PUCCH spatial relationship information. index/id, and then determine the corresponding PUCCH-config. Therefore, without explicitly indicating the PUCCH information, both the base station and the UE can accurately parse the indication information, and there will be no problem of understanding ambiguity.
  • the length of the MAC CE is related to the number of PUCCH-config.
  • the length of the MAC CE can be related to the number of PUCCH-config configured by the terminal, or it can also be related to the PUCCH-config activated at the same time. The number is related.
  • the length of the MAC CE may also be determined. In some embodiments, the length of the MAC CE is fixed.
  • This embodiment is based on the improved PUCCH spatial relationship activation/deactivation MAC CE format, and by specifying the placement order of multiple sets of PUCCH spatial relationship information placed in multiple S rows, the new MAC CE format can carry accurate and comprehensive resources. Instructions.
  • the first type of PUCCH spatial relationship activation/deactivation MAC CE format MAC CE has a variable length
  • FIG. 7 schematically shows another MAC CE format according to an embodiment of the present application, which belongs to an improved PUCCH spatial relationship activation/deactivation MAC CE format.
  • MAC CE format of the present embodiment includes a P domain and P domain comprises a plurality of bits, each bit place a value I P.
  • MAC CE uses multiple bits in the designated field to indicate the spatial relationship activation or deactivation information corresponding to each PUCCH-config, or to indicate the spatial relationship indication corresponding to each PUCCH-config Appears or does not appear.
  • each of the multiple bits of the designated domain respectively represents the PUCCH config index/id of each PUCCH-config
  • the first bit of the multiple bits corresponds to the first PUCCH-config, and if the value of the first bit is the first specified value, then the MAC CE appears in the first PUCCH-config Spatial relationship information;
  • the second bit of the multiple bits corresponds to the second PUCCH-config, and if the value of the second bit is the second specified value, the second PUCCH-config does not appear in the MAC CE ⁇ spatial relationship information.
  • each of the multiple bits of the designated field respectively represents the PUCCH config index/id of each PUCCH-config; it can be placed in the order of multiple PUCCH config index/id agreed to correspond to each PUCCH-config.
  • One bit; the predetermined order refers to the ordering of the multiple PUCCH config index/id corresponding to the multiple PUCCH spatial relationship information, for example, ascending order or descending order.
  • MAC CE uses a plurality of bits placed in a plurality P P I domain values, P different represent different positions of i PUCCH config index / id, P. 5 Representative PUCCH config e.g. PUCCH-config with index/id of 5; further, the value of P i is used to indicate whether the PUCCH spatial relationship activation or deactivation information corresponding to the PUCCH-config appears in the MAC CE. For example, if the value of P 5 is 0, it indicates The spatial relationship information of the PUCCH-config whose PUCCH config index/id is 5 does not appear, and if the value of P 5 is 1, it appears.
  • the value of P 5 is 1, it indicates that the spatial relationship information of the PUCCH-config whose PUCCH config index/id is 5 does not appear, and if the value of P 5 is 0, it appears.
  • this embodiment can be understood as an explicit indication of PUCCH information.
  • the base station can set the P i value corresponding to the spatial relationship activation information in the MAC CE to 1, the corresponding S line appears in the MAC CE, and the spatial relationship deactivation information corresponds to the P i value of 0, and the corresponding S line is not Appears in MAC CE.
  • the length of the MAC CE according to the present embodiment is variable, the attribute decision information itself may be indicative of specific value is determined by the respective P i.
  • This embodiment is based on the improved PUCCH spatial relationship activation/deactivation MAC CE format, where multiple fields in the new P domain are used to represent different PUCCH-configs, and part of the spatial relationship information does not appear, the new MAC CE format can carry accurate , Comprehensive resource instruction information.
  • This embodiment provides yet another MAC CE format, which belongs to the improved PUCCH spatial relationship activation/deactivation MAC CE format.
  • the MAC CE uses multiple bits in the designated field to indicate the spatial relationship activation or deactivation information corresponding to each PUCCH-config, or to indicate whether to indicate the corresponding PUCCH-config information.
  • the present embodiment is the embodiment of FIG. 7 that the similarities, MAC CE format of the present embodiment includes a P domain and P domain comprises a plurality of bits, each bit place a value P I, except that , P i values of different meanings.
  • each of the multiple bits of the designated domain respectively represents the PUCCH config index/id of each PUCCH-config
  • the first bit of the multiple bits corresponds to the first PUCCH-config, and if the value of the first bit is the first specified value, the first PUCCH-config in the MAC CE is used.
  • the second bit of the multiple bits corresponds to the second PUCCH-config, and if the value of the second bit is the second specified value, the second PUCCH-config in the MAC CE is ignored ⁇ spatial relationship information.
  • the terminal may determine whether to use one or more sets of information corresponding to a spatial relationship according to the value P i.
  • the length of the MAC CE according to the present embodiment does not vary with the value of P i.
  • this embodiment can be understood as an explicit indication of PUCCH information.
  • Figure 8 schematically shows a MAC CE format of an embodiment of the present application, which belongs to an improved PUCCH spatial relationship activation/deactivation MAC CE format.
  • the main differences of this embodiment are It is that the MAC CE of this embodiment uses the reserved bits in the original PUCCH spatial relationship activation/deactivation MAC CE format to indicate the activation or deactivation of the spatial relationship corresponding to one PUCCH-config among multiple PUCCH-configs Information, that is, indicate PUCCH-config information.
  • the reserved bits can be R bits.
  • the reserved bit represents the PUCCH config index/id of one PUCCH-config among multiple PUCCH-configs, and the designated row (S row) next to the reserved bit indicates the corresponding PUCCH-
  • the spatial relationship activation or deactivation information of config is the spatial relationship activation or deactivation information of config.
  • the P field indicates PUCCH config index/id, if the value of P is 0, it means PUCCH config index/id is 0 (or other specified values) PUCCH-config, placed in the S row next to the P field
  • the spatial relationship activation or deactivation information corresponding to the PUCCH-config If the value of P is 1, it represents a PUCCH-config with PUCCH config index/id of 1 (or other specified values), and the adjacent S rows place the activation or deactivation information of the spatial relationship corresponding to the PUCCH-config.
  • the MAC CE in this embodiment carries one PUCCH-config spatial relationship activation or deactivation information at a time.
  • the embodiments of this application can use a new LCID, or use the existing PUCCH spatial relationship to activate/deactivate the original LCID corresponding to the MAC CE, which can all be implemented in this application.
  • the improved PUCCH spatial relationship provided by the example activates/deactivates MAC CE for correct reception and analysis. The two methods are described in detail below.
  • a network device sends an LCID (49) to a terminal device.
  • the terminal device can detect the LCID (49), and receive and decode the MAC CE corresponding to the LCID (49).
  • the terminal device meets at least one of the following conditions:
  • the terminal equipment supports the detection capability corresponding to the new LCID
  • the terminal equipment supports the improved MAC CE format detection capability
  • the terminal equipment is instructed to detect according to the improved MAC CE format
  • the terminal device is a terminal device that supports the specified protocol
  • the terminal device supports simultaneous activation of multiple PUCCH-configs
  • the terminal device is configured with multiple PUCCH-config;
  • the terminal equipment supports at least one designated service, such as URLLC service;
  • the terminal equipment supports multiple services, such as URLLC services and eMBB services;
  • the terminal device belongs to the terminal device described in the embodiment of this application, then the terminal device will receive and decode the new MAC CE format according to the improved MAC CE format described in the embodiment of this application to ensure that the PUCCH resources carried in the MAC CE
  • the instruction information is accurately and comprehensively analyzed.
  • the terminal device if the terminal device meets at least one of the above conditions a to condition i, even if the terminal device detects the original LDID (49), it will compare the new one according to the improved MAC CE format.
  • the MAC CE receives and decodes.
  • the corresponding new LCID (not 49) can be used.
  • the LCID is used to identify the corresponding MAC CE.
  • the new LCID is used to identify the improved MAC CE described in any of the above embodiments.
  • the new LCID can be a redefined LCID, which is different from the original LCID (49).
  • the network device may send a new LCID to the terminal device.
  • the terminal device will detect the new LCID.
  • the terminal device can clearly: it should receive and decode the new MAC CE format according to the improved MAC CE format.
  • the terminal device should understand the existing MAC CE according to the new meaning defined in the embodiments of this application.
  • the reserved R bit in the MAC CE format ensures accurate and comprehensive analysis of the PUCCH resource indication information carried in the MAC CE.
  • the network device may send the first LCID (for example, the original LCID) to the terminal device or send the second LCID (for example, the new LCID) to the terminal device.
  • the terminal device can detect the first LCID or detect the second LCID.
  • a terminal device for a terminal device that meets at least one of the conditions a to i described in the above "method 1", it can detect the first LCID, or in other words, detect according to the first LCID.
  • the terminal device can receive and decode the MAC CE corresponding to the first LCID according to the improved MAC CE format described in the embodiment of this application, and ensure that the PUCCH resource indication information carried in the MAC CE is processed. Accurate and comprehensive analysis.
  • a terminal device for a terminal device that meets at least one of the conditions a to i described in the above "method 1", it can detect the second LCID, or in other words, detect the second LCID.
  • the terminal device can receive and decode the MAC CE corresponding to the first LCID according to the improved MAC CE format described in the embodiment of this application, and ensure that the PUCCH resource indication information carried in the MAC CE is processed. Accurate and comprehensive analysis.
  • the terminal device if the terminal device detects the first LCID, it can still receive and decode the MAC CE according to the existing MAC CE format; if the terminal device detects the second LCID, it can receive it according to the improved MAC CE format according to the embodiment of this application And decode MAC CE.
  • the terminal device in the embodiment of the present application does not expect to receive MAC CEs in two formats or two LCIDs at the same time.
  • the terminal device can receive one of the MAC CE formats or one of the LCIDs.
  • the improved MAC CE also carries PUCCH resource identifiers PUCCH resource IDs corresponding to one or more PUCCH information respectively.
  • the embodiment of this application also provides a resource indication method for indicating the PUCCH-config corresponding to the spatial relationship activation/deactivation information. Specifically, it can rely on configuring a different PUCCH-resource ID for each PUCCH-config. The only difference is PUCCH-config.
  • the PUCCH-resource ID configured in different PUCCH-configs is different.
  • the terminal device configures multiple sets of PUCCH resources according to multiple PUCCH-config information
  • the PUCCH-resource IDs in different PUCCH-configs are also different.
  • the terminal device When the terminal device receives the MAC CE indicating the activated PUCCH spatial relationship information, it can obtain the PUCCH-resource ID corresponding to the PUCCH spatial relationship information it carries. Since the PUCCH resource ID in each PUCCH-config cannot be the same, then The UE can uniquely distinguish a PUCCH-config corresponding to the activated PUCCH spatial relationship according to the PUCCH resource ID.
  • the terminal device in order to uniquely determine the PUCCH-config corresponding to the PUCCH spatial relationship activation information, the terminal device does not expect to receive configurations with the same PUCCH-resource ID configured by different PUCCH-configs.
  • the embodiments of the present application are applicable to scenarios where multiple (or called multiple sets) of PUCCH-config are used simultaneously under one BWP. If the terminal device is configured with multiple PUCCH-configs, one PUCCH-config can be applied to, for example, eMBB services, and one PUCCH-confid can be applied to, for example, URLLC services.
  • a PUCCH-config corresponds to a codebook.
  • the base station can configure at least two hybrid automatic repeat request acknowledgement (HARQ-ACK) codebooks at the same time to support different service types of the UE. For example, one codebook supports URLLC service and one codebook supports eMBB service. At that time, the base station will configure different HARQ-ACK codebooks: PUCCH spatial relationship information and sub-slot configuration. Then, when indicating the activated PUCCH spatial relationship information, it is also necessary to indicate which codebook the activated PUCCH spatial relationship information corresponds to.
  • HARQ-ACK hybrid automatic repeat request acknowledgement
  • the embodiment of the present application can be applied to the above-mentioned scenarios, and the corresponding PUCCH-config can be indicated through the first indication information, and the corresponding codebook can be determined, which solves the problem of not being able to clearly indicate which codebook the activated PUCCH spatial relationship information corresponds to.
  • an embodiment of the present application further provides a terminal device 100. Referring to FIG. 9, it includes:
  • the receiving module 110 is configured to receive first indication information, where the first indication information is used to indicate spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config;
  • the determining module 120 is configured to determine at least one PUCCH-config corresponding to the spatial relationship information among multiple PUCCH-configs according to the first indication information.
  • an embodiment of the present application further provides a network device 200, referring to FIG. 10, which includes:
  • the sending module 210 sends first indication information to the terminal device, where the first indication information is used to indicate the spatial relationship information corresponding to one or more physical uplink control channel configurations PUCCH-config.
  • the terminal device 100 of the embodiment of the present application can implement the corresponding functions and processes implemented by the terminal device in each method of the embodiment of the present application.
  • the network device 200 of the embodiment of the present application can implement the corresponding functions and processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, I will not repeat them here.
  • Fig. 11 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device 600 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive information or data sent by other devices. .
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 600 may be a network device of an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • details are not described herein again.
  • the communication device 600 may be a terminal device of an embodiment of the present application, and the communication device 600 may implement corresponding procedures implemented by the terminal device in each method of the embodiments of the present application. For brevity, details are not described herein again.
  • FIG. 12 is a schematic structural diagram of a chip 700 according to an embodiment of the present application, where the chip 700 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip 700 may further include an input interface 730.
  • the processor 710 can control the input interface 730 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip can be applied to the terminal device in the above embodiments of the present application, and the chip can implement the corresponding procedures implemented by the terminal device in the various methods of the embodiments of the present application.
  • the chip can implement the corresponding procedures implemented by the terminal device in the various methods of the embodiments of the present application.
  • details are not described herein again.
  • chips mentioned in the embodiments of the present application may also be referred to as system-level chips, system-on-chips, system-on-chips, or system-on-chips.
  • the aforementioned processors can be general-purpose processors, digital signal processors (digital signal processors, DSP), ready-made programmable gate arrays (field programmable gate arrays, FPGAs), application specific integrated circuits (ASICs), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processors
  • FPGA field programmable gate arrays
  • ASIC application specific integrated circuits
  • the aforementioned general-purpose processor may be a microprocessor or any conventional processor.
  • the above-mentioned memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is to say, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.
  • FIG. 13 is a schematic block diagram of a communication system 800 according to an embodiment of the present application.
  • the communication system 800 includes a terminal device 810 and a network device 820.
  • the terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the methods of the various embodiments of the present application
  • the network device 820 can be used to implement the corresponding functions implemented by the network device in the methods of the various embodiments of the present application. Function. For the sake of brevity, I will not repeat them here.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instruction may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instruction may be transmitted from a website, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not correspond to the embodiments of the present application.
  • the implementation process constitutes any limitation. Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.
  • the above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Covered in the scope of protection of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请涉及一种资源指示方法、终端设备和网络设备，该资源指示方法包括：终端设备接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；所述终端设备根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。利用本申请实施例能够实现准确的资源指示。

Description

资源指示方法、终端设备和网络设备 技术领域
本申请涉及通信领域，更具体地，涉及一种资源指示方法、终端设备和网络设备。
背景技术
第五代无线通信技术5G的需求中包括增强型移动宽带eMBB、海量机器类通信mMTC、高可靠低时延通信uRLLC三种应用场景。进一步，5G工业互联网(Industrial Internet of Things，IIoT)的需求包括支持工业自动化(Factory Automation)、传输自动化(Transport Industry)和智能电力分配(Electrical Power Distribution)等业务在5G***的传输。
相应的，IIoT***可支持URLLC业务和eMBB业务的传输，并且为了支持不同业务有时需为终端设备配置多套资源，相较于以往仅配置一套资源的情况，如何实现对多套资源信息进行准确指示，是当前需要解决的问题。
发明内容
有鉴于此，本申请实施例提供一种资源指示方法、终端设备和网络设备，可用于实现对多套资源信息进行准确指示。
本申请实施例提供一种资源指示方法，应用于终端设备，包括：
终端设备接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
所述终端设备根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
本申请实施例提供一种资源指示方法，应用于网络设备，包括：
网络设备向终端设备发送第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
本申请实施例还提供一种终端设备，包括：
接收模块，用于接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
确定模块，用于根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
本申请实施例还提供一种网络设备，包括：
发送模块，用于向终端设备发送第一指示信息，第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
本申请实施例还提供一种终端设备，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器调用并运行所述存储器中存储的计算机程序，执行如上所述的资源指示方法。
本申请实施例还提供一种网络设备，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器调用并运行所述存储器中存储的计算机程序，执行如上所述的资源指示方法。
本申请实施例还提供一种芯片，包括处理器，用于从存储器中调用并运行计算机程序，使安装有所述芯片的设备执行如上所述的资源指示方法。
本申请实施例还提供一种计算机可读存储介质，用于存储计算机程序，其中，所述计算机程序使得计算机执行如上所述的资源指示方法。
本申请实施例还提供一种计算机程序产品，包括计算机程序指令，其中，所述计算 机程序指令使得计算机执行如上所述的资源指示方法。
本申请实施例还提供一种计算机程序，所述计算机程序使得计算机执行如上所述的资源指示方法。
利用本申请实施例，终端设备可根据第一指示信息区分空间关系信息对应的PUCCH配置，能够在配置有多个PUCCH配置的情况下，明确指示空间关系信息所对应的PUCCH配置，消除终端设备与网络设备之间可能存在的理解歧义。
附图说明
图1是本申请实施例的通信***架构的示意图。
图2是一种PUCCH空间关系激活/去激活MAC CE格式的示意图。
图3是本申请一个实施例的终端设备侧的资源指示方法的流程框图。
图4是本申请一个实施例的网络设备侧的资源指示方法的流程框图。
图5-8是本申请多个实施例的改进的PUCCH空间关系激活/去激活MAC CE格式的示意图。
图9是本申请一个实施例的终端设备的示意性结构框图。
图10是本申请一个实施例的网络设备的示意性结构框图。
图11是本申请实施例的通信设备示意性框图。
图12是本申请实施例的芯片的示意性框图。
图13是本申请实施例的通信***的示意性框图。
具体实施方式
下面结合本申请实施例的附图，对本申请实施例的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***，例如：全球移动通讯(Global System of Mobile communication，GSM)***、码分多址(Code Division Multiple Access，CDMA)***、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)***、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)***、先进的长期演进(Advanced long term evolution，LTE-A)***、新无线(New Radio，NR)***、NR***的演进***、免授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)***、免授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)***、非地面通信网络(Non-Terrestrial Networks，NTN)***、通用移动通信***(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)***或其他通信***等。
通常来说，传统的通信***支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信***将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信***。
可选地，本申请实施例中的通信***可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中，终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户 装置等。
终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信***例如NR网络中的终端设备，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
在本申请实施例中，终端设备可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中，终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality，VR)终端设备、增强现实(Augmented Reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中，网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备等。
作为示例而非限定，在本申请实施例中，网络设备可以具有移动特性，例如网络设备可以为移动的设备。可选地，网络设备可以为卫星、气球站。例如，卫星可以为低地球轨道(low earth orbit，LEO)卫星、中地球轨道(medium earth orbit，MEO)卫星、地球同步轨道(geostationary earth orbit，GEO)卫星、高椭圆轨道(High Elliptical Orbit，HEO)卫星等。可选地，网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中，网络设备可以为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示意性地示出了一个网络设备1100和两个终端设备1200，可选地，该无线通信***1000可以包括多个网络设备1100，并且每个网络设备1100的覆盖范围内可以 包括其它数量的终端设备，本申请实施例对此不做限定。可选地，图1所示的无线通信***1000还可以包括移动性管理实体(Mobility Management Entity，MME)、接入与移动性管理功能(Access and Mobility Management Function，AMF)等其他网络实体，本申请实施例对此不作限定。
应理解，本文中术语“***”和“网络”在本文中常可互换使用。本文中术语“和/或”用来描述关联对象的关联关系，例如表示前后关联对象可存在三种关系，举例说明，A和/或B，可以表示：单独存在A、同时存在A和B、单独存在B这三种情况。本文中字符“/”一般表示前后关联对象是“或”的关系。
为了清楚地阐述本申请实施例的思想，首先对通信***中相关资源配置的过程进行简要描述。
在本领域，关于物理上行控制信道配置PUCCH-config，针对每个服务小区(Serving Cell)的每个带宽部分BWP，基站可配置对应的一个或多个PUCCH-config，PUCCH-config中会配置对应的PUCCH资源。
具体地，基站配置PUCCH资源时，可以按照PUCCH资源集合(PUCCH-ResourceSet)进行配置，也可以按照PUCCH资源(PUCCH-Resource)进行配置。其中，对每个PUCCH资源集合，配置对应的PUCCH资源集合标识ID(PUCCH-ResourceSetId)和至少一个PUCCH资源。对每个PUCCH资源，配置对应的PUCCH资源ID(PUCCH-ResourceId)和具体的PUCCH资源。其中，可根据PUCCH格式(format)配置具体的PUCCH资源，配置PUCCH format时至少指示PUCCH资源长度和PUCCH资源相对参考点的偏移offset参数。
此外，基站在配置PUCCH-config时，还会配置一套或多套PUCCH空间关系信息(PUCCH Spatial Relation Info)，用于配置参考信号(Reference Signal，RS)和PUCCH的空间关系。具体的，PUCCH空间关系信息用于配置对应的PUCCH传输的空间设置(the spatial setting for PUCCH transmission，如使用的RS)和PUCCH功控参数(the parameters for PUCCH power control)。每套PUCCH空间关系信息中均包括PUCCH空间关系信息ID(SpatialRelationInfoId)。其中，当配置多套PUCCH空间关系信息时，需使用MAC CE激活或指示使用其中的哪一套PUCCH空间关系信息。
为此，图2示出了一种“PUCCH空间关系激活/去激活MAC CE”(PUCCH spatial relation Activation/Deactivation MAC CE)格式，该MAC CE格式可指示PUCCH空间关系信息列表(list)中的元素的激活状态。
具体地，图2示例的PUCCH空间关系激活/去激活MAC CE格式可由具有特定逻辑信道标识LCID的MAC子头(MAC subheader)标识，该MAC CE的大小为24比特，其中包括服务小区ID(Serving Cell ID)字段、BWP ID字段、PUCCH Resource ID字段、Si字段和R字段，含义如下：
●Serving Cell ID字段指示该MAC CE对应的服务小区的标识，该字段长度为7比特。
●BWP ID字段指示一上行BWP，该MAC CE作为特定的DCI带宽部分指示符字段的码位应用于该上行BWP，BWP ID字段长度为2比特。
●PUCCH Resource ID字段包含由PUCCH-ResourceId标识的PUCCH资源ID的标识符，该字段长度为7比特。
●对于S i字段，如果存在一个由PUCCH-SpatialRelationInfoId标识且是为上述BWP ID字段指示的上行BWP配置的PUCCH空间关系信息，则S i字段指示该PUCCH-SpatialRelationInfoId为i+1对应的PUCCH空间关系信息的激活状态；否则，MAC实体忽略该S i字段。其中，如果存在上述PUCCH空间关系信息，
有以下两种情况：
■若S i字段为1，表示PUCCH-SpatialRelationInfoId为i+1的PUCCH空间关系信息激活；
■若S i字段为0，表示PUCCH-SpatialRelationInfoId为i+1的PUCCH空间关系信息去激活。
●对于R字段，为预留比特位，通常设为0。
其中，一次指示只能为PUCCH资源激活一个PUCCH空间关系信息。
以上描述了目前对于基站为UE配置的一个PUCCH-config信息，可通过如图2示意的PUCCH空间关系激活/去激活MAC CE来指示该PUCCH-config对应的PUCCH空间关系激活或去激活信息。
目前，随着下一代无线通信技术的不断演进，以IIoT***为例，为支持不同的业务，基站有可能为一个BWP配置多个PUCCH-config信息，应用时，在eMBB业务中使用其中一个PUCCH-config，而在URLLC业务中使用另一个PUCCH-config配置。
在此情况下，经本申请发明人深入研究发现，当一个BWP支持或者说被配置多个PUCCH-config时，上文所述的PUCCH空间关系激活/去激活MAC CE已经不能明确指示激活的PUCCH空间关系属于多个PUCCH-config中哪一个PUCCH-config，这将带来UE和基站理解不一致的问题，导致***性能下降。
为此，本申请实施例提供一种资源指示方法，应用于终端设备，参考图3，该方法包括：
S101，终端设备接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
S102，终端设备根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
对应地，本申请实施例还提供一种资源指示方法，应用于网络设备，参考图4，该方法包括：
S201，网络设备向终端设备发送第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
本申请的实施例可通过第一指示信息对多个PUCCH-config各自对应的空间关系信息例如空间关系激活或去激活信息进行分别指示，终端设备可根据第一指示信息区别激活的PUCCH空间关系对应的PUCCH-config，因此能够避免按照以往指示方式无法明确所指示的空间关系信息对应多个PUCCH config中哪一个PUCCH config的问题，消除终端设备与网络设备之间可能存在的歧义
在本申请实施例中，网络设备向终端设备发送第一指示之前，网络设备可为终端设备配置多个PUCCH-config，每个PUCCH-config信息包括至少一套空间关系信息。终端设备接收到网络设备配置的多个PUCCH-config之后，可根据该多个PUCCH-config进行相应的PUCCH资源配置。
以下以网络设备为基站为例进行简要说明，在本申请实施例中，基站可为UE配置多套PUCCH资源，将多套PUCCH资源对应的多个PUCCH-config发送给UE，其中，每个PUCCH-config可包括以下多项中的至少一项：
①PUCCH资源集合PUCCH resource set，其包括PUCCH resource set ID以及其中的一个或多个PUCCH resource，其中每个PUCCH resource对应配置有一个PUCCH resource ID及具体的资源。
②PUCCH资源PUCCH resource，其对应配置的一个PUCCH resource ID及具体的资源。
③一套或多套PUCCH空间关系信息PUCCH-SpatialRelationInfo，其中每套PUCCH-SpatialRelationInfo包括对应的SpatialRelationInfoId和对应的RS配置等信息。
在本申请实施例中，在根据该多个PUCCH-config进行相应的PUCCH资源配置之后，如果终端设备接收到第一指示信息，需确定该第一指示信息中指示的一套或多套空间关系信息分别对应该多个PUCCH-config中的哪个PUCCH-config。
为此，在本申请实施例中，所述第一指示信息包括第一MAC CE，由所述第一MAC CE携带与一个或多个PUCCH信息分别对应的一套或多套空间关系信息。因此该第一MAC CE可指示在终端设备配置的多个PUCCH-config中的至少一个PUCCH-config对应的空间关系信息，换句话说，第一MAC CE可指示该多个PUCCH-config中的第一PUCCH-config对应的第一空间关系信息，和/或第二PUCCH-config对应的第二空间关系信息，和/或第三PUCCH-config对应的第三空间关系信息，等等。
在本申请的不同的实施方式中，设计了多种MAC CE格式用以携带上述指示信息。在一些实施方式中，使用的MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式；在另外一些实施方式中，使用的MAC CE符合第二类PUCCH空间关系激活/去激活MAC CE格式。
根据MAC CE格式的不同，终端设备对于MAC CE的解析方式也不同。总的来说，可以在MAC CE中，隐式地或显式地指示被激活/去激活的空间关系对应的PUCCH-config或codebook。
以下通过多个具体实施例并结合附图，对本申请实施例的MAC CE以及携带的资源指示信息进行详细描述。
I. 第一类PUCCH空间关系激活/去激活MAC CE格式：显式指示
图5示意性地示出了本申请实施例的一种MAC CE格式，其中包含多个PUCCH信息——标识为多个P i——分别对应的多套PUCCH空间关系信息(位于S行)，以及分别对应的多个PUCCH资源标识PUCCH Resource ID。
本实施例使用的MAC CE格式属于一种改进的PUCCH空间关系激活/去激活MAC CE格式。该MAC CE在S行指示PUCCH空间关系信息的同时，还使用P字段指示多个PUCCH信息，图5中标识为P i。与常规的MAC CE格式中预留R位相比，本实施例的MAC CE格式中的R位被新的P域取代，在P域中放置不同的P i值，可指示不同的PUCCH信息。
具体到本实施例，该MAC CE中包括每一个PUCCH-config的PUCCH config index/id以及与每一个PUCCH-config对应的空间关系激活或去激活信息。也就是说，所述的PUCCH信息指的是PUCCH config标识PUCCH config index/id，其中，不同的PUCCH config index/id对应不同的PUCCH-config。这里，如果能够确定PUCCH config index/id与空间关系信息的对应关系，也就是确定了PUCCH-config与空间关系信息的对应关系。
更具体地，参考图5，不同的P i值指示不同的PUCCH config index/id。例如，如果P i的值为0，代表指示的是PUCCH config index/id为0(也可记作其他数值，如1)的PUCCH-config，该PUCCH-config对应的空间关系信息为与该取值为0的P i紧邻的S行。
又如，如果P i的值为1，代表指示的是PUCCH config index/id为1(也可记作其他数值，如2)的PUCCH-config，该PUCCH-config对应的空间关系信息为与该取值为1的P i紧邻的S行。
其中，如果S行中的S i的值为1，表示激活PUCCH-SpatialRelationInfoId为i+1的 PUCCH空间关系信息；如果S i字段为0，表示对PUCCH-SpatialRelationInfoId为i+1的PUCCH空间关系信息去激活。
通过上述方式，本实施例的MAC CE使用指定比特位(例如P位)指示第一PUCCH config index，并使用与所述指定比特位紧邻的指定行(例如S行)来指示与所述第一PUCCH config index对应的PUCCH-config的空间关系激活或去激活信息。
对于图5实施例的MAC CE格式，可视为一种显示指示的方式，该MAC CE利用P域标识各个PUCCH config index/id(对应多个PUCCH-config)，同时指示激活或去激活的PUCCH空间关系信息以及PUCCH Resource ID信息。其中，P域的值可为预设值，例如可为0、1、2、3、4、5、6或7，也可为能够区别标识PUCCH-config的其他数值，对应S行的S i的值可为0或1。
在本实施例中，该MAC CE的长度与PUCCH-config的个数相关，例如，MAC CE的长度可以与终端配置的PUCCH-config的个数相关，或者，也可以与同时激活的PUCCH-config的个数相关。
在一些实施方式中，如果相关的PUCCH-config的个数确定，MAC CE的长度也可以确定。在一些实施方式中，MAC CE的长度固定不变。
在本实施例中，每个P位代表一个PUCCH-config的PUCCH config id/index，由于采取了显式指示的方式，各个P位的值与对应的PUCCH空间关系信息完整携带，因此对每套PUCCH空间关系信息的放置顺序没有特殊要求，既可以随机顺序放置，也可按照一定的顺序放置。其中，可以采取的顺序例如多个PUCCH config index/id的大小排序，如升序或降序。
此外，进一步地，在指示不同的PUCCH-config的过程中，由于不同的PUCCH-config所对应的服务小区Serving Cell和/或BWP有可能相同，也有可能不同，可通过上述MAC CE对此一并进行指示。
具体地，如果不同的PUCCH-config对应的服务小区Serving Cell和BWP均相同，可如图5所示在第一个P域之前的相应字段放置serving cell ID和BWP ID；如果不同的PUCCH-config对应的服务小区Serving Cell和BWP两者中有至少一项不同，可在对应的P域之前增加相应字段放置对应的serving cell ID和BWP ID，使指示信息全面。
通过本申请上述实施例，基于改进的PUCCH空间关系激活/去激活MAC CE格式，可实现以重新定义的P位直接或间接指示PUCCH-config，同时以紧连的S行指示对应的PUCCH空间关系激活或去激活信息，新的MAC CE格式能够携带准确、全面的资源指示信息。
II. 第一类PUCCH空间关系激活/去激活MAC CE格式：隐式指示
图6示意性地示出了本申请实施例的另一种MAC CE格式，包括多套PUCCH空间关系信息(位于S行)和对应的多个PUCCH Resource ID。
如图6实施例的MAC CE格式也属于改进的PUCCH空间关系激活/去激活MAC CE格式，与图5实施例相比，本实施例的不同之处主要在于：
1、本实施例的MAC CE格式中不包含P域，而是仍保留原有的预留比特位(如R字段)，
2、本实施例不对PUCCH信息做显式指示，而是采取隐式指示的方式实现资源指示。
具体地，本实施例的MAC CE格式中，多套PUCCH空间关系信息是按照预定的顺序放置的。
在一种实施方式中，所述预定的顺序指的是该多个PUCCH空间关系信息对应的多 个PUCCH config index/id的排序，例如升序或者降序(也就是从小到大排序或者从大到小排序)。
这里，由于多套PUCCH空间关系信息(对应多个S行)是按照约定的多个PUCCH config index/id的顺序放置，因此UE能够根据多套PUCCH空间关系信息的排列顺序自行确定对应的PUCCH config index/id，进而确定对应地PUCCH-config。因此，在不做显式指示PUCCH信息的情况下，基站和UE双方也能够准确解析指示信息，不会出现理解歧义的问题。
在本实施例中，该MAC CE的长度与PUCCH-config的个数相关，例如，MAC CE的长度可以与终端配置的PUCCH-config的个数相关，或者，也可以与同时激活的PUCCH-config的个数相关。
在一些实施方式中，如果相关的PUCCH-config的个数确定，MAC CE的长度也可以确定。在一些实施方式中，MAC CE的长度固定不变。
关于多个PUCCH Resource ID、serving cell ID和BWP ID等参数信息的设置，可采取与图5实施例类似的方式设置，在此不做赘述。
本实施例基于改进的PUCCH空间关系激活/去激活MAC CE格式，通过规定其中多个S行中放置的多套PUCCH空间关系信息的放置顺序，使新的MAC CE格式能够携带准确、全面的资源指示信息。
III. 第一类PUCCH空间关系激活/去激活MAC CE格式：MAC CE的长度可变
图7示意性地示出了本申请实施例的再一种MAC CE格式，属于改进的PUCCH空间关系激活/去激活MAC CE格式，与图5实施例相比，本实施例的不同之处主要在于，本实施例的MAC CE格式中包含P域，且P域中包含多个比特位，每个比特位放置一个P i值。
在本实施例中，MAC CE使用指定域中的多个比特位用于指示每一个PUCCH-config对应的空间关系激活或去激活信息，或者，用于指示每个PUCCH-config对应的空间关系指示出现或者不出现。
具体地，所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index/id；
其中，假设多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，则所述MAC CE中出现所述第一PUCCH-config的空间关系信息；
其中，假设多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，则所述MAC CE中不出现所述第二PUCCH-config的空间关系信息。
其中，所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index/id；可以按照约定的多个PUCCH config index/id的顺序放置，用以对应每一个比特位；所述预定的顺序指的是该多个PUCCH空间关系信息对应的多个PUCCH config index/id的排序，例如升序或者降序。
详细来看，参考图7，本实施例的MAC CE使用P域中的多个比特位放置多个P i值，不同位置的P i代表不同的PUCCH config index/id，例如P 5代表PUCCH config index/id为5的PUCCH-config；进一步，以P i的值指示该MAC CE中是否出现该PUCCH-config对应的PUCCH空间关系激活或去激活信息，例如，如果P 5的值为0，指示该PUCCH config index/id为5的PUCCH-config的空间关系信息不出现，如果P 5的值为1，则出现。又例如，如果P 5的值为1，指示该PUCCH config index/id为5的PUCCH-config的空间关系信息不出现，如果P 5的值为0，则出现。对于出现的情况， 指示方式可采取前述实施例中描述的方式，通过与P i紧连的S行指示该PUCCH-config对应的PUCCH空间关系激活或去激活信息。相应的，本实施例可以理解为对PUCCH信息的显式指示。
相应地，基站可设置该MAC CE中空间关系激活信息对应的P i值为1，对应的S行出现在MAC CE中，而空间关系去激活信息对应P i值为0，对应的S行不出现在MAC CE中。因此，本实施例的MAC CE的长度是可变的，可由指示信息本身的属性决定，具体可由各个P i的取值决定。
本实施例基于改进的PUCCH空间关系激活/去激活MAC CE格式，其中使用新的P域中多个字段代表不同的PUCCH-config，且部分空间关系信息不出现，新的MAC CE格式能够携带准确、全面的资源指示信息。
IV. 第一类PUCCH空间关系激活/去激活MAC CE格式：MAC CE的长度不变
本实施例提供再一种MAC CE格式，属于改进的PUCCH空间关系激活/去激活MAC CE格式。在本实施例中，MAC CE使用指定域中的多个比特位用于指示每一个PUCCH-config对应的空间关系激活或去激活信息，或者，用于指示是否指示对应的PUCCH-config的信息。
本实施例与图7实施例的相同之处在于，本实施例的MAC CE格式中包含P域，且P域中包含多个比特位，每个比特位放置一个P i值，不同之处在于，P i值含义不同。
具体地，所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index/id；
其中，假设多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，则使用所述MAC CE中的所述第一PUCCH-config的空间关系信息；
其中，假设多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，则忽略所述MAC CE中的所述第二PUCCH-config的空间关系信息。
本实施例中，对于MAC CE中出现的多套空间关系信息，终端可根据P i值确定是否使用对应的一套或多套空间关系信息。本实施例的MAC CE的长度不随P i的取值而变化。相应的，本实施例可以理解为对PUCCH信息的显式指示。
V. 第二类PUCCH空间关系激活/去激活MAC CE格式：使用预留位
图8示意性地示出了本申请实施例的一种MAC CE格式，属于改进的PUCCH空间关系激活/去激活MAC CE格式，与前述的各个实施例相比，本实施例的不同之处主要在于：本实施例的MAC CE使用原有的PUCCH空间关系激活/去激活MAC CE格式中的预留比特位，来指示多个PUCCH-config中的一个PUCCH-config对应的空间关系激活或去激活信息，也即指示PUCCH-config信息。其中，预留比特位可为R位。
在本申请实施例中，该预留比特位代表多个PUCCH-config中的一个PUCCH-config的PUCCH config index/id，与该预留比特位紧邻的指定行(S行)指示对应的PUCCH-config的空间关系激活或去激活信息。
例如，参考图8，P域指示PUCCH config index/id，若P取值为0，代表PUCCH config index/id为0(或其他指定数值)的PUCCH-config，与P域紧连的S行放置该PUCCH-config对应的空间关系激活或去激活信息。若P取值为1，代表PUCCH config index/id为1(或其他指定数值)的PUCCH-config，紧连的S行放置该PUCCH-config 对应的空间关系激活或去激活信息。本实施例的MAC CE一次携带一个PUCCH-config的空间关系激活或去激活信息。
以上通过多个实施例详细描述了多种改进的PUCCH空间关系激活/去激活MAC CE格式，均能够携带准确、全面的资源指示信息。
关于与MAC CE对应的逻辑信道标识LDID，本申请的实施例可以使用新的LCID，也可以使用现有的PUCCH空间关系激活/去激活MAC CE对应的原有的LCID，均能够实现对本申请实施例提供的改进的PUCCH空间关系激活/去激活MAC CE进行正确接收和解析。以下对两种方式分别进行详细描述。
方式一：使用原有的LDID(49)
通常，网络设备向终端设备发送LCID(49)，对应地，终端设备可检测该LCID(49)，并接收并解码该LCID(49)对应的MAC CE。
本申请实施例中，如果终端设备符合以下各项条件中的至少一项：
a)终端设备支持与新的LCID对应的检测能力；
b)终端设备支持改进的MAC CE格式的检测能力；
c)终端设备被指示按照改进的MAC CE格式进行检测；
d)终端设备为支持指定协议的终端设备；
e)终端设备支持同时激活多个PUCCH-config；
f)终端设备配置有多个PUCCH-config；
g)终端设备激活有多个PUCCH-config；
h)终端设备支持至少一种指定业务，例如URLLC业务；
i)终端设备支持多种业务，例如URLLC业务和eMBB业务；
这表明该终端设备属于本申请实施例描述的终端设备，那么该终端设备将按照本申请实施例描述的改进的MAC CE格式来接收并解码新的MAC CE，确保对MAC CE中携带的PUCCH资源指示信息进行准确、全面解析。
因此，在本申请实施例中，如果终端设备符合上述条件a至条件i中的至少一项，则即使终端设备检测到原有的LDID(49)，也将按照改进的MAC CE格式对新的MAC CE进行接收和解码。
需要说明，在其他实施例中，在上述情况下，终端设备仍有可能按照原有的MAC CE格式进行解码。
方式二：引入新的LDID(非49)
对于本申请实施例提出的改进的MAC CE格式，可使用对应的新的LCID(非49)。LCID用来标识对应的MAC CE，在本申请实施例中，所述的新的LCID用来标识以上任一实施例中描述的改进的MAC CE。这里，关于新的LCID可为重新定义的LCID，区别于原有的LCID(49)。
具体地，对于符合“方式一”中描述的条件a至条件i中至少一种条件的终端设备，网络设备可向该终端设备发送新的LCID。对应地，该终端设备将检测该新的LCID。这里，由于不同于原有的LCID，因此该终端设备可以明确：应按照改进的MAC CE格式来接收并解码新的MAC CE，例如，应按照本申请实施例定义的新的含义理解现有的MAC CE格式中的预留R位，确保对MAC CE中携带的PUCCH资源指示信息进行准确、全面解析。
基于以上描述的两种方式，应用中，网络设备可以向终端设备发送第一LCID(例如原有的LCID)或者向终端设备发送第二LCID(例如新的LCID)。对应地，终端设备可以检测第一LCID或者检测第二LCID。
在一些实施方式中，对于符合以上“方式一”中描述的条件a至条件i中至少一种 条件的终端设备，其可检测第一LCID，或者说按照第一LCID检测。对于该第一LCID对应的MAC CE，终端设备可按照本申请实施例描述的改进的MAC CE格式来接收并解码第一LCID对应的MAC CE，确保对该MAC CE中携带的PUCCH资源指示信息进行准确、全面解析。
在另一些实施方式中，对于符合以上“方式一”中描述的条件a至条件i中至少一种条件的终端设备，其可检测第二LCID，或者说按照第二LCID检测。对于该第二LCID对应的MAC CE，终端设备可按照本申请实施例描述的改进的MAC CE格式来接收并解码第一LCID对应的MAC CE，确保对该MAC CE中携带的PUCCH资源指示信息进行准确、全面解析。
在其他实施方式中，如果终端设备检测到第一LCID，仍可按照现有MAC CE格式接收并解码MAC CE；如果终端设备检测到第二LCID，则按照本申请实施例改进的MAC CE格式接收并解码MAC CE。
需要说明的是，本申请实施例的终端设备不期待同时收到两种格式的MAC CE，或者两种LCID。可选的，在不同时间或不同情况下(比如配置多个PUCCH-config，但不同时刻可以激活一个或者多个PUCCH-config)，终端设备可以收到其中一种MAC CE格式或一种LCID。
对于前述的各个实施例，参考图5-8，改进的MAC CE中还携带与一个或多个PUCCH信息分别对应的PUCCH资源标识PUCCH resource ID。基于此，本申请实施例还提供一种资源指示方法，用于指示空间关系激活/去激活信息对应的PUCCH-config，具体地，可依靠为每个PUCCH-config配置不同的PUCCH-resource ID来唯一区别PUCCH-config。
在本申请实施例中，网络设备为终端设备配置多个PUCCH-config时；不同的PUCCH-config中配置的PUCCH-resource ID不同。则终端设备根据多个PUCCH-config信息配置多套PUCCH资源时，不同的PUCCH-config中的PUCCH-resource ID也不同。
当终端设备接收到用于指示激活的PUCCH空间关系信息的MAC CE时，可获得其携带的PUCCH空间关系信息对应的PUCCH-resource ID，由于每个PUCCH-config中的PUCCH resource ID不可相同，则UE可以根据PUCCH resource ID唯一区别激活的PUCCH空间关系对应的一个PUCCH-config。
在本申请实施例中，为了唯一确定PUCCH空间关系激活信息所对应的PUCCH-config，终端设备不期待接收到不同的PUCCH-config所配置的PUCCH-resource ID相同的配置。
以上通过多个实施例从不同角度描述了本申请实施例的具体设置和实现方式。本申请的实施例适用于在一个BWP下同时使用多个(或称多套)PUCCH-config的场景。如果终端设备配置有多个PUCCH-config，其中一个PUCCH-config可应用于例如eMBB业务，一个PUCCH-confid可应用于例如URLLC业务。
在本领域，一个PUCCH-config即对应一种码本codebook。一种情况是，基站可同时配置至少两个混合自动重传请求确认(HARQ-ACK)码本(codebook)以支持UE的不同业务类型，例如一个codebook支持URLLC业务，一个codebook支持eMBB业务，这时基站会为不同的HARQ-ACK codebook分别配置：PUCCH空间关系信息和子时隙配置。那么，当指示激活的PUCCH空间关系信息时，还需要指示激活的PUCCH空间关系信息对应哪一个codebook。本申请的实施例可应用于上述场景，通过第一指示信息指示对应的PUCCH-config，进而可确定对应的codebook，解决无法明确指示激活的PUCCH空间关系信息对应哪一个codebook的问题。
与上述至少一个实施例的处理方法相对应地，本申请实施例还提供一种终端设备 100，参考图9，其包括：
接收模块110，用于接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
确定模块120，用于根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
与上述至少一个实施例的处理方法相对应地，本申请实施例还提供一种网络设备200，参考图10，其包括：
发送模块210，向终端设备发送第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
本申请实施例的终端设备100可以实现本申请实施例的各个方法中由终端设备实现的相应功能和流程。本申请实施例的网络设备200可以实现本申请实施例的各个方法中由网络设备实现的相应功能和流程。为了简洁，在此不再赘述。
图11是根据本申请实施例的通信设备600示意性结构图，其中通信设备600包括处理器610，处理器610可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，通信设备600还可以包括存储器620。其中，处理器610可以从存储器620中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器620可以是独立于处理器610的一个单独的器件，也可以集成在处理器610中。
可选地，通信设备600还可以包括收发器630，处理器610可以控制该收发器630与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备600可为本申请实施例的网络设备，并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备600可为本申请实施例的终端设备，并且该通信设备600可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
图12是根据本申请实施例的芯片700的示意性结构图，其中芯片700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，芯片700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，该芯片700还可以包括输入接口730。其中，处理器710可以控制该输入接口730与其他设备或芯片进行通信，具体地，可获取其他设备或芯片发送的信息或数据。
可选地，该芯片700还可以包括输出接口740。其中，处理器710可以控制该输出接口740与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请以上实施例中的终端设备，并且该芯片可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为***级芯片，***芯片，芯片***或 片上***芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、现成可编程门阵列(field programmable gate array，FPGA)、专用集成电路(application specific integrated circuit，ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中，上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图13是根据本申请实施例的通信***800的示意性框图，该通信***800包括终端设备810和网络设备820。
其中，该终端设备810可以用于实现本申请各个实施例的方法中由终端设备实现的相应的功能，以及该网络设备820可以用于实现本申请各个实施例的方法中由网络设备实现的相应的功能。为了简洁，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。所属技术领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。以上所述仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (46)

  1. 一种资源指示方法，应用于终端设备，所述方法包括：
    终端设备接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
    所述终端设备根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述终端设备接收来自网络设备的多个PUCCH-config信息；
    所述终端设备根据所述多个PUCCH-config信息配置多套PUCCH资源；其中，每个所述PUCCH-config信息包括至少一套空间关系信息。
  3. 根据权利要求1或2所述的方法，其中，
    所述第一指示信息包括媒介访问控制层控制单元MAC CE，所述MAC CE携带与一个或多个PUCCH信息分别对应的一套或多套空间关系信息。
  4. 根据权利要求3所述的方法，其中，
    所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式；
    或者，
    所述MAC CE符合第二类PUCCH空间关系激活/去激活MAC CE格式。
  5. 根据权利要求4所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    在所述MAC CE中，多套空间关系激活或去激活信息是按照预设顺序放置的。
  6. 根据权利要求5所述的方法，其中，
    所述预设顺序是根据所述多套空间关系激活或去激活信息对应的多个PUCCH-config的PUCCH config标识index确定的顺序。
  7. 根据权利要求4所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用指定比特位指示第一PUCCH config index，并使用与所述指定比特位紧邻的指定行来指示与所述第一PUCCH config index对应的PUCCH-config的空间关系激活或去激活信息。
  8. 根据权利要求7所述的方法，其中，
    所述MAC CE中包括每一个PUCCH-config的PUCCH config index以及与每一个PUCCH-config对应的空间关系激活或去激活信息。
  9. 根据权利要求4所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用指定域中的多个比特位指示每一个PUCCH-config对应的空间关系激活或去激活信息。
  10. 根据权利要求9所述的方法，其中，
    所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index；
    所述多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，则所述MAC CE中出现所述第一PUCCH-config的空间关系信息；
    所述多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，则所述MAC CE中不出现所述第二PUCCH-config的空间关系信息。
  11. 根据权利要求9所述的方法，其中，
    所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index；
    所述多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，使用所述第一PUCCH-config的空间关系信息；
    所述多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，忽略所述第二PUCCH-config的空间关系信息。
  12. 根据权利要求3-11中任一项所述的方法，其中，
    所述MAC CE中设置有至少一个服务小区标识字段和至少一个带宽部分BWP标识字段，用于指示各个PUCCH-config分别对应的服务小区和BWP。
  13. 根据权利要求4所述的方法，其中，
    在所述MAC CE符合第二类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用预留比特位指示所述多个PUCCH-config中的一个PUCCH-config对应的空间关系信息。
  14. 根据权利要求13所述的方法，其中，
    所述预留比特位代表多个PUCCH-config中的一个PUCCH-config的PUCCH config index，与所述预留比特位紧邻的指定行用于指示对应的PUCCH-config的空间关系激活或去激活信息。
  15. 根据权利要求3-14中任一项所述的方法，其中，
    所述MAC CE还携带与一个或多个PUCCH信息分别对应的PUCCH资源标识PUCCH resource ID。
  16. 根据权利要求3-15中任一项所述的方法，其中，所述方法还包括：
    所述终端设备检测第一逻辑信道标识LCID，所述第一LCID为指定LCID；
    或者，
    所述终端设备检测第二LCID，所述第二LCID与所述MAC CE对应，所述终端设备按照所述第一类PUCCH空间关系激活/去激活MAC CE格式或者所述第二类PUCCH空间关系激活/去激活MAC CE格式，解析所述MAC CE。
  17. 根据权利要求16所述的方法，其中，
    在符合预定条件的情况下，所述终端设备检测所述第一LCID，或者，检测所述第二LCID，
    所述预定条件包括以下各者中的至少一者：
    所述终端设备支持与所述第二LCID对应的检测能力；
    所述终端设备支持所述MAC CE格式的检测能力；
    所述终端设备被指示按照所述MAC CE格式进行检测；
    所述终端设备为支持指定协议的终端设备；
    所述终端设备支持同时激活多个PUCCH config；
    所述终端设备配置有多个PUCCH-config；
    所述终端设备激活有多个PUCCH-config；
    所述终端设备支持至少一种指定业务；
    所述终端设备支持多种业务。
  18. 根据权利要求2所述的方法，其中，
    在所述多个PUCCH-config中，不同的PUCCH-config中配置的PUCCH资源标识PUCCH-resource ID不同。
  19. 根据权利要求18所述的方法，其中，
    所述第一指示信息包括MAC CE，所述MAC CE中携带有与一个或多个 PUCCH-resource ID分别对应的一套或多套空间关系信息；
    所述终端设备根据所述多个PUCCH-config中每一个PUCCH-config中的PUCCH-resource ID以及所述一套或多套空间关系信息对应的PUCCH-resource ID，确定所述一套或多套空间关系信息分别对应的一个或多个PUCCH-config。
  20. 根据权利要求1-19中任一项所述的方法，其中，
    所述终端设备不期待接收到的多个PUCCH-config中不同的PUCCH-config所配置的PUCCH-resource ID相同。
  21. 一种资源指示方法，应用于网络设备，所述方法包括：
    网络设备向终端设备发送第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
  22. 根据权利要求21所述的方法，其中，所述方法还包括：
    网络设备为终端设备配置多个PUCCH-config，每个所述PUCCH-config信息包括至少一套空间关系信息；
    所述网络设备向所述终端设备发送所述多个PUCCH-config。
  23. 根据权利要求21或22所述的方法，其中，
    所述第一指示信息包括MAC CE，所述MAC CE携带与一个或多个PUCCH信息分别对应的一套或多套空间关系信息。
  24. 根据权利要求23所述的方法，其中，
    所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式；
    或者，
    所述MAC CE符合第二类PUCCH空间关系激活/去激活MAC CE格式。
  25. 根据权利要求24所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    在所述MAC CE中，多套空间关系激活或去激活信息是按照预设顺序放置的。
  26. 根据权利要求25所述的方法，其中，
    所述预设顺序是根据与所述多套空间关系激活或去激活信息分别对应的多个PUCCH-config的PUCCH config标识index确定的顺序。
  27. 根据权利要求24所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用指定比特位指示第一PUCCH config index，并使用与所述指定比特位紧邻的指定行来指示与所述第一PUCCH config index对应的PUCCH-config的空间关系激活或去激活信息。
  28. 根据权利要求25所述的方法，其中，
    所述MAC CE中包括每一个PUCCH-config的PUCCH config index以及与每一个PUCCH-config对应的空间关系激活或去激活信息。
  29. 根据权利要求24所述的方法，其中，
    在所述MAC CE符合第一类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用指定域中的多个比特位指示每一个PUCCH-config对应的空间关系激活或去激活信息。
  30. 根据权利要求29所述的方法，其中，
    所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index；
    所述多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，则所述MAC CE中出现所述第一PUCCH-config的空间关系信息；
    所述多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，则所述MAC CE中不出现所述第二PUCCH-config的空间关系信息。
  31. 根据权利要求29所述的方法，其中，
    所述指定域的多个比特位中的每一个比特位分别代表每一个PUCCH-config的PUCCH config index；
    所述多个比特位中的第一比特位对应第一PUCCH-config，若所述第一比特位的值为第一指定值，使用所述第一PUCCH-config的空间关系信息；
    所述多个比特位中的第二比特位对应第二PUCCH-config，若所述第二比特位的值为第二指定值，忽略所述第二PUCCH-config的空间关系信息。
  32. 根据权利要求23-31中任一项所述的方法，其中，
    所述MAC CE中设置有至少一个服务小区标识字段和至少一个带宽部分BWP标识字段，用于指示各个PUCCH-config对应的服务小区和BWP。
  33. 根据权利要求24所述的方法，其中，
    在所述MAC CE符合第二类PUCCH空间关系激活/去激活MAC CE格式的情况下，
    所述MAC CE使用预留比特位指示所述多个PUCCH-config中的一个PUCCH-config对应的空间关系激活或去激活信息。
  34. 根据权利要求33所述的方法，其中，
    所述预留比特位代表多个PUCCH-config中的一个PUCCH-config的PUCCH config index，与所述预留比特位紧邻的指定行用于指示对应的PUCCH-config的空间关系激活或去激活信息。
  35. 根据权利要求23-34中任一项所述的方法，其中，
    所述MAC CE还携带与一个或多个PUCCH信息分别对应的PUCCH资源标识PUCCH resource ID。
  36. 根据权利要求23-35中任一项所述的方法，其中，所述方法还包括：
    所述网络设备向所述终端设备发送第一LCID，所述第一LCID为指定LCID；
    或者，
    所述网络设备向所述终端设备发送第二LCID，所述第二LCID与所述MAC CE对应。
  37. 根据权利要求36所述的方法，其中，
    在符合预定条件的情况下，所述网络设备向所述终端设备发送所述第一LCID，或者，发送所述第二LCID，
    所述预定条件包括以下各者中的至少一者：
    所述终端设备支持与所述第二LCID对应的检测能力；
    所述终端设备支持所述MAC CE格式的检测能力；
    指示所述终端设备按照所述MAC CE格式进行检测；
    所述终端设备为支持指定协议的终端设备；
    所述终端设备支持同时激活多个PUCCH config；
    为所述终端设备配置有多个PUCCH-config；
    为所述终端设备激活有多个PUCCH-config；
    所述终端设备支持至少一种指定业务；
    所述终端设备支持多种业务。
  38. 根据权利要求22所述的方法，其中，
    所述网络设备为所述终端设备配置的多个PUCCH-config中，不同的PUCCH-config所配置的PUCCH-resource ID不同。
  39. 一种终端设备，包括：
    接收模块，用于接收第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息；
    确定模块，用于根据所述第一指示信息，在多个PUCCH-config中确定与所述空间关系信息对应的至少一个PUCCH-config。
  40. 一种网络设备，包括：
    发送模块，用于向终端设备发送第一指示信息，所述第一指示信息用于指示一个或多个物理上行控制信道配置PUCCH-config对应的空间关系信息。
  41. 一种终端设备，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器调用并运行所述存储器中存储的计算机程序，执行如权利要求1至20中任一项所述的方法。
  42. 一种网络设备，包括：处理器和存储器，所述存储器用于存储计算机程序，所述处理器调用并运行所述存储器中存储的计算机程序，执行如权利要求21至38中任一项所述的方法。
  43. 一种芯片，包括：
    处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至38中任一项所述的方法。
  44. 一种计算机可读存储介质，用于存储计算机程序，其中，所述计算机程序使得计算机执行如权利要求1至38中任一项所述的方法。
  45. 一种计算机程序产品，包括计算机程序指令，其中，所述计算机程序指令使得计算机执行如权利要求1至38中任一项所述的方法。
  46. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至38中任一项所述的方法。
PCT/CN2020/078313 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备 WO2021174558A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
KR1020227009522A KR20220152184A (ko) 2020-03-06 2020-03-06 자원 지시 방법, 단말 장치 및 네트워크 장치
PCT/CN2020/078313 WO2021174558A1 (zh) 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备
CN202210477741.3A CN114793363B (zh) 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备
EP20923464.0A EP4017185A4 (en) 2020-03-06 2020-03-06 RESOURCE INDICATION METHOD, TERMINAL DEVICE, AND NETWORK DEVICE
JP2022533239A JP2023516531A (ja) 2020-03-06 2020-03-06 リソース指示方法、端末装置、及びネットワーク装置
CN202080059216.9A CN114287157A (zh) 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备
US17/654,540 US20220201506A1 (en) 2020-03-06 2022-03-11 Resource indication method, terminal device, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/078313 WO2021174558A1 (zh) 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/654,540 Continuation US20220201506A1 (en) 2020-03-06 2022-03-11 Resource indication method, terminal device, and network device

Publications (1)

Publication Number Publication Date
WO2021174558A1 true WO2021174558A1 (zh) 2021-09-10

Family

ID=77614468

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/078313 WO2021174558A1 (zh) 2020-03-06 2020-03-06 资源指示方法、终端设备和网络设备

Country Status (6)

Country Link
US (1) US20220201506A1 (zh)
EP (1) EP4017185A4 (zh)
JP (1) JP2023516531A (zh)
KR (1) KR20220152184A (zh)
CN (2) CN114287157A (zh)
WO (1) WO2021174558A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118369982A (zh) * 2022-11-18 2024-07-19 北京小米移动软件有限公司 Pucch-sri指示方法、装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190230730A1 (en) * 2018-03-19 2019-07-25 Intel Corporation Pucch and pusch default beam considering beam failure recovery
CN110167126A (zh) * 2018-02-13 2019-08-23 电信科学技术研究院有限公司 一种多波束传输时pucch功率的控制方法及装置
US20190268961A1 (en) * 2018-02-23 2019-08-29 Mediatek Inc. Default Beam for Uplink Transmission after Connection Reestablishment
WO2020042981A1 (zh) * 2018-08-29 2020-03-05 ***通信有限公司研究院 空间相关信息的指示方法和设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200083589A (ko) * 2018-01-11 2020-07-08 후지쯔 가부시끼가이샤 업링크 신호 전송 방법, 업링크 신호 수신 방법, 디바이스, 및 시스템
US10986617B2 (en) * 2018-08-07 2021-04-20 FG Innovation Company Limited Method and apparatus for activating PUCCH spatial relation
WO2021072619A1 (en) * 2019-10-15 2021-04-22 Qualcomm Incorporated Enhanced physical uplink control channel spatial relation information in mac ce
BR112022015390A2 (pt) * 2020-02-05 2022-09-27 Ericsson Telefon Ab L M Métodos realizados por um dispositivo sem fio e por uma estação base, dispositivo sem fio, e, estação base

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110167126A (zh) * 2018-02-13 2019-08-23 电信科学技术研究院有限公司 一种多波束传输时pucch功率的控制方法及装置
US20190268961A1 (en) * 2018-02-23 2019-08-29 Mediatek Inc. Default Beam for Uplink Transmission after Connection Reestablishment
US20190230730A1 (en) * 2018-03-19 2019-07-25 Intel Corporation Pucch and pusch default beam considering beam failure recovery
WO2020042981A1 (zh) * 2018-08-29 2020-03-05 ***通信有限公司研究院 空间相关信息的指示方法和设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
LG ELECTRONICS: "Discussion on multi-beam based operations and enhancements", 3GPP DRAFT; R1-1904209 MULTI-BEAM_FINAL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. RAN WG1, no. Xi’an, China; 20190408 - 20190412, 30 March 2019 (2019-03-30), XP051691347 *
LG ELECTRONICS: "Updated feature lead summary of Enhancements on Multi-beam Operations", 3GPP DRAFT; R1-1905838 R1#96BIS UPDATED FEATURE LEAD SUMMARY OF MB1 AFTER THURSDAY OFFLINE SESSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), vol. RAN WG1, no. Xi’an, China; 20190408 - 20190412, 15 April 2019 (2019-04-15), XP051707884 *
See also references of EP4017185A4 *

Also Published As

Publication number Publication date
JP2023516531A (ja) 2023-04-20
CN114287157A (zh) 2022-04-05
CN114793363B (zh) 2023-11-28
CN114793363A (zh) 2022-07-26
KR20220152184A (ko) 2022-11-15
EP4017185A4 (en) 2022-10-19
US20220201506A1 (en) 2022-06-23
EP4017185A1 (en) 2022-06-22

Similar Documents

Publication Publication Date Title
WO2020063736A1 (zh) 一种干扰测量方法和装置
US10863578B2 (en) Data transmission method, device and system
WO2021163938A1 (zh) 天线切换方法、终端设备和通信设备
CN115413045B (zh) 信息传输方法、终端设备和网络设备
WO2019029333A1 (zh) 一种资源调度方法及装置
WO2021237675A1 (zh) 无线通信方法和终端设备
WO2020211096A1 (zh) 无线通信方法、终端设备和网络设备
US20220338262A1 (en) Information determination method, information indication method, terminal device, and network device
WO2020073257A1 (zh) 无线通信方法和终端设备
WO2022011555A1 (zh) 用于确定上行传输参数的方法和终端设备
WO2020051892A1 (zh) 无线通信的方法、终端设备和网络设备
WO2021184224A1 (zh) 侧行链路能力发送方法和终端设备
WO2021189367A1 (zh) 物理信道监测方法和终端设备
WO2021159413A1 (zh) 下行传输方法和终端设备
WO2021174558A1 (zh) 资源指示方法、终端设备和网络设备
US20230107139A1 (en) Relay discovery method and terminal
WO2021163967A1 (zh) 数据传输方法、终端设备和网络设备
WO2023197260A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022077346A1 (zh) 信道传输的方法、终端设备和网络设备
WO2023102848A1 (zh) 无线通信的方法和终端设备
WO2023150998A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022021448A1 (zh) 检测控制信息的方法、传输控制信息的方法、终端设备和网络设备
WO2023035144A1 (zh) 无线通信的方法、终端设备和网络设备
WO2022206914A1 (zh) 监听方法与装置、终端和网络设备
WO2022217443A1 (zh) 信道估计方法、终端设备、网络设备、芯片和存储介质

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: 20923464

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020923464

Country of ref document: EP

Effective date: 20220317

ENP Entry into the national phase

Ref document number: 2022533239

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE