CN111837431A - Information transmission method, terminal equipment and network equipment - Google Patents
Information transmission method, terminal equipment and network equipment Download PDFInfo
- Publication number
- CN111837431A CN111837431A CN201880090974.XA CN201880090974A CN111837431A CN 111837431 A CN111837431 A CN 111837431A CN 201880090974 A CN201880090974 A CN 201880090974A CN 111837431 A CN111837431 A CN 111837431A
- Authority
- CN
- China
- Prior art keywords
- search space
- agreed
- coreset
- terminal device
- dci
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application discloses a method for transmitting information, terminal equipment and network equipment, wherein the method comprises the following steps: the terminal equipment adopts the aggregation level in the appointed aggregation level, or the DCI format based on the appointed DCI format, or carries out the DCI detection in the appointed search space type in the first search space or the search space corresponding to the first control resource set CORESET. The method, the terminal device and the network device in the embodiment of the application are beneficial to reducing the blind test times of the terminal device, thereby achieving the effects of reducing the blind test complexity and reducing the terminal power consumption and processing time.
Description
The embodiment of the application relates to the field of communication, in particular to a method for transmitting information, terminal equipment and network equipment.
In the related art, the terminal device usually performs blind detection on Downlink Control Information (DCI) sent by the network device according to a configuration of the network device on a search space or a Control Resource Set (core Set), so as to obtain scheduling Information.
When the terminal device performs blind detection, how to reduce the power loss and processing time of the terminal device is a problem to be solved.
Disclosure of Invention
The embodiment of the application provides an information transmission method, terminal equipment and network equipment, which are beneficial to reducing the blind detection times of the terminal equipment, thereby reducing the power loss and the processing time of the terminal equipment.
In a first aspect, a method for transmitting information is provided, the method including: the terminal equipment adopts the aggregation level in the appointed aggregation level, or the DCI format based on the appointed DCI format, or carries out the DCI detection in the appointed search space type in the first search space or the search space corresponding to the first control resource set CORESET.
In a second aspect, a method of transmitting information is provided, the method comprising: the network device configures a first search space or a search space corresponding to a first control resource set (CORESET) to a terminal device, wherein the aggregation level configured for the first search space or the search space corresponding to the first CORESET only includes an agreed aggregation level, or the DCI format of the downlink control information configured for the first search space or the search space corresponding to the first CORESET only includes an agreed DCI format, or the search space type configured for the first search space or the search space corresponding to the first CORESET only includes an agreed search space type.
In a third aspect, a terminal device is provided, configured to perform the method in the first aspect or each implementation manner thereof.
Specifically, the terminal device includes a functional module for executing the method in the first aspect or each implementation manner thereof.
In a fourth aspect, a network device is provided for performing the method of the second aspect or its implementation manners.
In particular, the network device comprises functional modules for performing the methods of the second aspect or its implementations described above.
In a fifth aspect, a terminal device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method in the first aspect or each implementation manner thereof.
In a sixth aspect, a network device is provided that includes a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory, and executing the method of the second aspect or each implementation mode thereof.
In a seventh aspect, a chip is provided for implementing the method in any one of the first to second aspects or its implementation manners.
Specifically, the chip includes: a processor configured to call and run the computer program from the memory, so that the device on which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manners thereof.
In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to perform the method of any one of the first to second aspects or implementations thereof.
In a ninth aspect, there is provided a computer program product comprising computer program instructions to cause a computer to perform the method of any one of the first to second aspects or implementations thereof.
A tenth aspect provides a computer program that, when run on a computer, causes the computer to perform the method of any one of the first to second aspects or implementations thereof.
Through the technical scheme, the terminal equipment only needs to perform blind test on the search space of the appointed search space type or adopt the appointed aggregation level and the DCI format in the first search space or the search space corresponding to the first CORESET, rather than performing blind test according to the configuration of the network equipment, so that the blind test times of the terminal equipment are favorably reduced, and the effects of reducing the blind test complexity and the terminal power consumption and the processing time are achieved.
Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.
Fig. 2 is a schematic diagram of a method for transmitting information according to an embodiment of the present application.
Fig. 3 is another schematic diagram of a method for transmitting information according to an embodiment of the present disclosure.
Fig. 4 is a schematic block diagram of a terminal device provided in an embodiment of the present application.
Fig. 5 is a schematic block diagram of a network device provided in an embodiment of the present application.
Fig. 6 is another schematic block diagram of a terminal device provided in an embodiment of the present application.
Fig. 7 is another schematic block diagram of a network device provided in an embodiment of the present application.
Fig. 8 is a schematic block diagram of a chip provided in an embodiment of the present application.
Fig. 9 is a schematic block diagram of a communication system according to an embodiment of the present application.
Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, New Radio (NR) System, Evolution System of NR System, LTE (LTE-a) System on unlicensed spectrum, NR (NR-b) System on unlicensed spectrum, UMTS (UMTS) System on Mobile communications (GSM) System, UMTS (UMTS) System, Wireless Local Area Network (WLAN) System, WiFi (Wireless Local Area network, WiFi) System on Wireless Local Area Network (WLAN) System, General Packet Radio Service (GPRS) System, LTE-a System, NR System, Evolution System on NR System, LTE-b (LTE-a) System on unlicensed spectrum, and Wireless Local Area network (WiFi) System on Wireless Local Area Network (WLAN) System on unlicensed spectrum, Next generation communication systems or other communication systems, etc.
Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technology, mobile Communication systems will support not only conventional Communication, but also, for example, Device-to-Device (D2D) Communication, Machine-to-Machine (M2M) Communication, Machine Type Communication (MTC), and Vehicle-to-Vehicle (V2V) Communication, and the embodiments of the present application can also be applied to these Communication systems.
The frequency spectrum of the application is not limited in the embodiment of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum.
Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.
The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal Equipment" includes, but is not limited to, User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, and the embodiments of the present invention are not limited thereto.
Optionally, a Device to Device (D2D) communication may be performed between the terminal devices 120.
Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.
Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Fig. 2 shows a schematic block diagram of a method 200 of transmitting information according to an embodiment of the present application. As shown in fig. 2, the method 200 includes some or all of the following:
s210, the terminal device detects the DCI in the first search space or the search space corresponding to the first control resource set CORESET by adopting the aggregation level in the appointed aggregation level, or based on the DCI format in the appointed DCI format, or in the appointed search space type.
In NR, multiple Transmission points (TRPs)/antenna panels (panels) may independently schedule uplink or downlink data of a terminal device. Data transmission between different TRPs/panels and terminal devices is typically scheduled by an independently configured CORESET or Physical Downlink Control Channel (PDCCH) in the search space, i.e. different CORESET or search space may correspond to different TRPs/panels. The terminal device needs to blind-detect DCI possibly transmitted by the network side in the configured multiple CORESET or search spaces, so as to obtain the scheduling information. The network side may configure a plurality of search spaces or a plurality of CORESET corresponding to the plurality of TRPs/panels for the terminal device, where the first search space may be one or more search spaces in the configured plurality of search spaces, the first CORESET may be one or more CORESET in the configured plurality of CORESET, and the search space corresponding to the first CORESET may also be one or more search spaces in all the search spaces corresponding to the configured plurality of CORESET. Specifically, the first search space may be a partial search space of the configured plurality of search spaces, and the first CORESET may be a partial CORESET of the configured plurality of CORESETs.
The network device may configure a plurality of search spaces or a plurality of CORESET to the terminal device through a physical layer or higher layer signaling, for example, the network device may send configuration information to the terminal device through a Radio Resource Control (RRC) signaling. The first search space or the first CORESET in the embodiment of the present application may be configured by the network device to the terminal device in advance, or may be predefined by the network device and the terminal device (for example, specified in a protocol). For example, the first search space may be at least one auxiliary search space specifically configured by the network device, and the first CORESET may be at least one auxiliary CORESET specifically configured by the network device. For another example, the first search space may be the core set other than the first core set among the plurality of core sets configured by the network device for scheduling data transmission.
The agreed aggregation level, the agreed DCI format and the agreed search space type may be agreed in advance by the terminal device and the network device, and may be, for example, a protocol agreement, and stored in the terminal device and the network device. Or may be indicated to the terminal device by the network device, for example, the network device may indicate the agreed aggregation level, the agreed DCI format, and the agreed search space type to the terminal device through DCI. It should be understood that for all three of the agreed aggregation level, the agreed DCI format and the agreed search space type, some agreed upon by the protocol and others indicated by the network device may be used.
The agreed aggregation level may comprise one or more aggregation levels. The terminal device detects the DCI by using an aggregation level in the agreed aggregation levels, which may be by using some or all of the agreed aggregation levels. For example, the agreed aggregation levels include 4, 8, and 16, and the terminal device may perform DCI detection using the aggregation levels 4 and 8, or may perform DCI detection directly according to the aggregation levels 4, 8, and 16.
Likewise, the agreed DCI format may include one or more DCI formats, and the terminal device performs DCI detection based on the DCI format in the agreed DCI format, which may be based on part or all of the DCI formats in the agreed DCI format. For example, the agreed DCI formats include 0_0, 0_1, 1_0, and 1_1, and the terminal device may use DCI formats 0_1 and 1_1 to perform DCI detection, or may directly perform DCI detection according to DCI formats 0_0, 0_1, 1_0, and 1_ 1.
The agreed search space type may include a common search space or a UE-specific search space.
If the number of the agreed aggregation levels used for DCI detection is smaller than the number of aggregation levels included in the configured aggregation levels, or the number of the agreed DCI formats used for DCI detection is smaller than the number of DCI formats included in the configured DCI formats, or the first search space or all search spaces corresponding to the first CORESET include both a search space configured as an agreed search space type and a search space configured as another search space type, the method in the embodiment of the present application can reduce the number of blind tests of the terminal device, thereby achieving the effects of reducing the complexity of blind tests and reducing the power consumption and processing time of the terminal device.
It should be understood that the aggregation level and DCI format may be regarded as parameters used for DCI detection, and the method of the embodiment of the present application is also applicable to other parameters used for DCI detection. In addition, the search space type may be divided into a common search space and a UE-specific search space, and the method of the embodiment of the present application is also applicable to search space types of other division modes, which should not be limited in the embodiment of the present application.
Optionally, in this embodiment of the application, the terminal device may determine the aggregation level used for DCI detection according to the aggregation level configured for the search space corresponding to the first search space or the first CORESET and the agreed aggregation level, or determine the DCI format used for DCI detection according to the DCI format configured for the search space corresponding to the first search space or the first CORESET and the agreed DCI format, or determine the search space to be DCI detected according to the search space type configured for the search space corresponding to the first search space or the first CORESET and the agreed search space type. And the terminal device can detect the DCI according to the selected aggregation level, the selected DCI format or the selected search space. Alternatively, the selected aggregation level, the selected DCI format, and the selected search space may be combined arbitrarily. For example, the terminal device may perform DCI detection in a first search space or a search space corresponding to a first CORESET by using the selected aggregation level and the selected DCI format. For another example, the terminal device may perform DCI detection in the selected search space by using the selected aggregation level and/or the selected DCI format.
Optionally, the terminal device may perform DCI detection by using an agreed aggregation level in all aggregation levels configured for the first search space or the search space corresponding to the first CORESET. For example, N aggregation levels are configured for the first search space or the search space corresponding to the first CORESET, where M aggregation levels are included in the agreed aggregation levels, and the terminal device only needs to perform DCI detection according to the M aggregation levels, and does not need to perform DCI detection according to other N-M aggregation levels in the N aggregation levels. The terminal device may also perform DCI detection using the aggregation level configured for the first search space or the search space corresponding to the first CORESET in all the agreed aggregation levels. The aggregation level configured for the first search space or the search space corresponding to the first CORESET may completely or partially coincide with the agreed aggregation level. Partial coincidence may be where the agreed-upon aggregation level is a proper subset of the configured aggregation level, or the configured aggregation level may be a proper subset of the agreed-upon aggregation level, or it may also be where the agreed-upon aggregation level intersects the configured aggregation level, but includes other aggregation levels, respectively. For example, configured aggregation levels include aggregation levels 2,4, 8, and 16, while agreed-upon aggregation levels include aggregation levels 8 and 16. As another example, the agreed aggregation levels include aggregation levels 2,4, 8, and 16, and the configured aggregation levels include aggregation levels 8 and 16. As another example, the agreed aggregation levels include aggregation levels 2, 8, and 16, and the configured aggregation levels include aggregation levels 4, 8, and 16.
Optionally, the terminal device also does not expect that the aggregation level configured by the network device for the first search space or the search space corresponding to the first CORESET includes an aggregation level other than the agreed aggregation level. In other words, the terminal device expects that the aggregation level configured by the network device for the first search space or the search space corresponding to the first CORESET includes only the aggregation level in the agreed aggregation levels, and does not include the aggregation levels other than the agreed aggregation level. Then, the aggregation level configured by the network device for the first search space or the search space corresponding to the first CORESET may include only the agreed aggregation level. If the terminal device receives that the aggregation level configured for the first search space or the search space corresponding to the first CORESET includes an aggregation level other than the agreed aggregation level, the terminal device may consider that the configuration is an incorrect configuration, and may not perform DCI detection in the first search space or the search space corresponding to the first CORESET. At this time, if the first CORESET corresponds to a plurality of search spaces, and only some aggregation levels configured in the search spaces include aggregation levels other than the agreed aggregation level, the terminal device may not perform DCI detection only in the search spaces including aggregation levels other than the agreed aggregation level, or may not perform DCI detection in all the search spaces corresponding to the first CORESET.
Optionally, the terminal device may perform DCI detection by using an agreed DCI format among all DCI formats configured for the first search space or the search space corresponding to the first CORESET. For example, N DCI formats are configured for the first search space or the search space corresponding to the first CORESET, where M DCI formats are included in the agreed DCI formats, at this time, the terminal device may perform DCI detection based on only the M DCI formats, and does not need to perform DCI detection based on other N-M DCI formats in the N DCI formats. The terminal device may also perform DCI detection in all the agreed DCI formats by using the DCI format configured for the first search space or the search space corresponding to the first CORESET. The DCI format configured for the first search space or the search space corresponding to the first CORESET may completely or partially overlap with the agreed DCI format. The partial coincidence may be that the agreed DCI format is a proper subset of the configured DCI format, or the configured DCI format may be a proper subset of the agreed DCI format, or may also be that the agreed DCI format and the configured DCI format intersect, but include other DCI formats respectively. For example, the configured DCI formats include DCI formats 0_0, 0_1, 1_0, and 1_1, and the agreed DCI formats include DCI formats 0_1 and 1_ 1. For another example, the agreed DCI formats include DCI formats 0_0, 0_1, 1_0, and 1_1, and the configured DCI formats include DCI formats 0_1 and 1_ 1. For another example, the agreed DCI formats include DCI formats 0_0, 0_1, and 1_1, and the configured DCI formats include DCI formats 0_1, 1_0, and 1_ 1.
Typically, the agreed DCI format may be DCI format 0_1 and/or DCI format 1_ 1. Because the two DCI formats are the most frequently used DCI formats for scheduling data transmission, the terminal only detects the two DCI formats in a part of search spaces, and detects the DCI formats for other purposes in other search spaces, thereby reducing the blind detection times to the maximum extent under the condition of ensuring data transmission scheduling.
Optionally, the terminal device also does not expect that the DCI formats configured for the first search space or the search space corresponding to the first CORESET by the network device include DCI formats other than the agreed DCI format. In other words, the terminal device expects that the DCI format configured for the first search space or the search space corresponding to the first CORESET by the network device includes only the DCI format in the agreed DCI formats, and does not include the DCI format other than the agreed DCI format. Then, the DCI format configured by the network device for the first search space or the search space corresponding to the first CORESET may include only the agreed DCI format. If the terminal device receives that the DCI format configured for the first search space or the search space corresponding to the first CORESET includes a DCI format other than the agreed DCI format, the terminal device may consider that the DCI format is configured incorrectly, and thus, DCI detection is not performed in the first search space or the search space corresponding to the first CORESET. At this time, if the first CORESET corresponds to a plurality of search spaces, and only a part of aggregation levels configured in the search spaces includes DCI formats other than the agreed DCI format, the terminal device may not perform DCI detection only in the search spaces including DCI formats other than the agreed DCI format, or may not perform DCI detection in all the search spaces corresponding to the first CORESET.
Optionally, the terminal device may perform DCI detection only in a search space configured as an agreed search space type in the first search space or the search space corresponding to the first CORESET. For example, the terminal device may perform DCI detection only in the first search space or a common search space in the search space corresponding to the first CORESET, and does not need to perform DCI detection in the UE-specific search space therein. For another example, the terminal device may perform DCI detection only in the first search space or the UE-specific search space in the search space corresponding to the first CORESET, and does not need to perform DCI detection in the common search space.
Optionally, the terminal device also does not expect that the search space type configured for the first search space or the search space corresponding to the first CORESET by the network device includes a search space type other than the agreed search space type. In other words, the terminal device expects that the search space type configured by the network device for the first search space or the search space corresponding to the first CORESET only includes the search space type in the agreed search space types, and does not include the search space types other than the agreed search space type. Then, the search space type configured by the network device for the first search space or the search space corresponding to the first CORESET may only include the agreed search space type. If the terminal device receives that the search space type configured for the first search space or the search space corresponding to the first CORESET includes a search space type other than the agreed search space type, the terminal device may consider that the search space type is an incorrect configuration, and may not perform DCI detection in the first search space or the search space corresponding to the first CORESET. For example, the terminal device does not expect that the first search space or the search space corresponding to the first CORESET is configured as the common search space, and if any of the search spaces is configured as the common search space, the terminal device may not perform DCI detection in the search space. For another example, the terminal device does not expect that the first search space or the search space corresponding to the first CORESET is configured as the UE-specific search space, and if any of the search spaces is configured as the UE-specific search space, the terminal device may not perform DCI detection in the search space. At this time, if the first CORESET corresponds to a plurality of search spaces, and only a part of the search spaces are configured as search space types other than the agreed search space type, the terminal device may not perform DCI detection only on the search space types other than the agreed search space types, or may not perform DCI detection in all the search spaces corresponding to the first CORESET.
Optionally, in this embodiment of the present application, a plurality of search spaces or a plurality of CORESET configured by the network device for the terminal device may all be used for scheduling data transmission, or may be partially used for scheduling data transmission. The multiple search spaces or multiple CORESET may not be used to schedule the transmission of the following information: beam recovery Information (i.e., not a recovery Search Space), parameters of the common Search Space 0, a System Information Block (SIB) 1, other System Information, Paging (Paging) Information, random access Information, and the like.
Optionally, in this embodiment of the present application, the first search space or the first CORESET may be used only for scheduling data transmission.
Optionally, the plurality of search spaces or the plurality of CORESET may correspond to different Transmission Configuration Indications (TCIs), that is, configured with different TCIs, that is, the plurality of search spaces or the plurality of CORESET transmit or receive using different beams. At this time, different ones of the plurality of search spaces or different ones of the plurality of CORESET may be respectively used for different TRPs or different panels to perform data scheduling, so as to support simultaneous downlink transmission of a plurality of TRPs or a plurality of panels.
The technical scheme of the present application is described in detail below with reference to examples 1 to 6.
Example 1: the terminal device and the network device may agree to use only aggregation levels 8 and 16 for DCI transmission in the secondary CORESET. The terminal device may receive the configuration of two CORESET through RRC signaling, wherein the second CORESET is an auxiliary CORESET. The first CORESET associates with search space 1, and the auxiliary CORESET associates with 2 search spaces: search space 2 and search space 3. In the search spaces 1 and 2,4 aggregation levels are configured: 2/4/8/16. In the search space 3, 3 aggregation levels are configured: 4/8/16. The terminal devices respectively use the aggregation level 2/4/8/16 for DCI detection in search space 1. The terminal equipment only adopts the agreed aggregation levels 8 and 16 to perform DCI detection in the search space 2 and the search space 3, and does not adopt the configured aggregation level 2 or 4 to perform DCI detection.
Example 2: the terminal device and the network device may agree that only the configured aggregation level 16 is desired to be configured for DCI transmission in the secondary search space. The terminal device may receive the configuration of two search spaces through RRC signaling, where the second search space is an auxiliary search space. In the search space 1,5 aggregation levels are configured: 1/2/4/8/16. In the search space 2, 3 aggregation levels are configured: 4/8/16. The terminal devices respectively use the aggregation level 1/2/4/8/16 for DCI detection in search space 1. Since aggregation levels other than the agreed aggregation level are configured in the search space 2, the terminal device may not perform DCI detection in the search space 2. At this time, if the search space 2 and the search space 3 are associated with the same CORESET, the terminal device may not perform DCI detection in all the search spaces (including the search space 2 and the search space 3) associated with the CORESET.
Example 3: the terminal device and the network device may agree to use only the UE-specific space for DCI transmission in other CORESET except the first CORESET. The terminal device may receive the configuration of three CORESET through RRC signaling. The first CORESET is related to the search space 1 and the search space 2, the second CORESET is related to the search space 3 and the search space 4, and the third CORESET is related to the search space 5. Where search spaces 1 and 3 are common search spaces and search spaces 2,4,5 are UE-specific search spaces. The terminal device may perform DCI detection in the search space 1 by using the DCI format corresponding to the common search space. In the search spaces 2,4, and 5, DCI detection may be performed using DCI formats corresponding to UE-specific search spaces. Since the search space 3 is not the agreed search space type, the terminal device may not perform DCI detection in the search space.
Example 4: the terminal device and the network device may agree that the terminal does not expect other CORESET associated UE-specific spaces outside the first CORESET. The terminal device may receive the configuration of three CORESET through RRC signaling. The first CORESET is related to the search space 1 and the search space 2, the second CORESET is related to the search space 3 and the search space 4, and the third CORESET is related to the search space 5. Wherein the search spaces 1,3,5 are common search spaces and the search spaces 2,4 are UE-specific search spaces. The terminal may perform DCI detection in the search spaces 1 and 5 using DCI formats corresponding to the common search space. In the search space 2, DCI detection may be performed using a DCI format corresponding to the UE-specific search space. Since search space 4 is not the agreed search space type, the terminal considers this to be an incorrect configuration, and DCI detection may not be performed in all search spaces (including search spaces 3 and 4) associated with the second CORESET associated with the search space.
Example 5: the terminal device and the network device may agree to detect only the DCI format 1_1 in other CORESET than the first CORESET. The terminal device may receive the configuration of the two CORESET through RRC signaling. Wherein, the first CORESET is related to the search space 1 and the search space 2, and the second CORESET is related to the search space 3. Wherein, the search space 1 is a common search space including DCI formats 0_0, 1_0, 2_1, 2_2, and 2_3, and the search spaces 2 and 3 are UE-specific search spaces including DCI formats 0_1, 1_0, 0_1, and 1_ 1. The terminal device can blind-detect DCI formats 0_0, 1_0, 2_1, 2_2, 2_3 in search space 1, respectively. DCI formats 0_1, 1_0, 0_1, 1_1 may be blind-detected in search space 2, respectively. In the search space 3, although the DCI formats 0_1, 1_0, 0_1, and 1_1 are included in the configuration, the terminal device blindly detects only the DCI format 1_1 that is agreed, and does not blindly detect DCI formats of other configurations.
Example 6: the terminal device and the network device may agree that the terminal does not desire to be configured with other DCI formats than DCI formats 0_1 and 1_1 in other CORESET than the first CORESET. The terminal device may receive the configuration of the two CORESET through RRC signaling. Wherein, the first CORESET associates the search space 1 and the search space 2, and the second CORESET associates the search space 3 and the search space 4. Search space 1 is a common search space containing DCI formats 0_0, 1_0, 2_1, 2_2, 2_3, search spaces 2 and 3 are UE-specific search spaces containing DCI formats 0_1, 1_0, 0_1, 1_1, and search space 4 is a UE-specific search space containing DCI formats 0_1 and 1_ 1. The terminal device may blind-detect DCI formats 0_0, 1_0, 2_1, 2_2, and 2_3 in search space 1 and DCI formats 0_1, 1_0, and 1_1 in search space 2, respectively. Since DCI formats 0_0 and 1_0 other than the agreed DCI format are configured in the search space 3, the terminal device considers that this is an erroneous configuration, and may not perform DCI detection in all search spaces (3 and 4) associated with the second core set associated with the search space 3.
Fig. 3 is a schematic block diagram of a method 300 for transmitting information according to an embodiment of the present disclosure. As shown in fig. 3, the method 300 includes some or all of the following:
s310, a network device configures a first search space or a search space corresponding to a first control resource set, to a terminal device, where an aggregation level configured for the first search space or the search space corresponding to the first CORESET includes only an agreed aggregation level, or a DCI format of downlink control information configured for the first search space or the search space corresponding to the first CORESET includes only an agreed DCI format, or a search space type configured for the first search space or the search space corresponding to the first CORESET includes only an agreed search space type.
Optionally, the network device may also configure the aggregation level, the DCI format, or the search space type of the search space corresponding to the first search space or the first CORESET to the terminal device, and then indicate the agreed aggregation level, the agreed DCI format, or the agreed search space type to the terminal device.
Optionally, in this embodiment of the present application, the agreed aggregation level is an aggregation level agreed in advance by the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance by the network device and the terminal device.
Optionally, in this embodiment of the present application, the agreed search space type includes a common search space or a UE-specific search space.
Optionally, in an embodiment of the present application, the method further includes: the network device sends configuration information to the terminal device, wherein the configuration information is used for configuring a plurality of search spaces or a plurality of CORESETs, the search spaces comprise a first search space, and the CORESETs comprise a first CORESET.
Optionally, in this embodiment of the present application, the plurality of search spaces or the plurality of CORESET are used for scheduling data transmission.
Optionally, in this embodiment of the present application, the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indicators TCI.
It should be understood that the interaction between the network device and the terminal device described by the network device and the related characteristics, functions, etc. correspond to the related characteristics, functions of the terminal device. That is, what message the network device sends to the terminal device, the terminal device receives the corresponding message from the network device.
It should also be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The method for transmitting information according to the embodiment of the present application is described above in detail, and the apparatus for transmitting information according to the embodiment of the present application will be described below with reference to fig. 4 to 7, and the technical features described in the embodiment of the method are applicable to the following embodiments of the apparatus.
Fig. 4 shows a schematic block diagram of a terminal device 400 of an embodiment of the application. As shown in fig. 4, the terminal apparatus 400 includes:
a processing unit 410, configured to perform DCI detection in downlink control information by using an aggregation level in an agreed aggregation level, or based on a DCI format in an agreed DCI format, or in an agreed search space type in a first search space or a search space corresponding to a first control resource set CORESET.
Optionally, in this embodiment of the present application, the agreed aggregation level is an aggregation level agreed in advance by the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance by the network device and the terminal device.
Optionally, in this embodiment of the present application, the agreed search space type is a common search space or a UE-specific search space.
Optionally, in an embodiment of the present application, the processing unit is specifically configured to: and in the aggregation levels configured for the first search space or the search space corresponding to the first CORESET, only the aggregation level included in the agreed aggregation level is adopted for DCI detection.
Optionally, in an embodiment of the present application, the processing unit is further configured to: it is not desirable that the aggregation levels configured for the first search space or the search space corresponding to the first CORESET include aggregation levels other than the agreed aggregation level.
Optionally, in an embodiment of the present application, the processing unit is specifically configured to: and in the DCI formats configured for the first search space or the search space corresponding to the first CORESET, only performing DCI detection based on the DCI formats included in the agreed DCI formats.
Optionally, in an embodiment of the present application, the processing unit is further configured to: it is not desirable that the DCI formats configured for the first search space or the search space corresponding to the first CORESET include DCI formats other than the agreed DCI format.
Optionally, in an embodiment of the present application, the processing unit is specifically configured to: in the first search space or all search spaces corresponding to the first CORESET, DCI detection is performed only in a search space configured as a common search space, or DCI detection is performed only in a search space configured as a UE-specific search space in the first search space or all search spaces corresponding to the first CORESET.
Optionally, in an embodiment of the present application, the processing unit is further configured to: it is not desirable that the first search space or the search space corresponding to the first CORESET include a search space of a search space type other than the agreed search space type.
Optionally, in this embodiment of the present application, the terminal device further includes: a transceiver unit, configured to receive configuration information, where the configuration information is used to configure multiple search spaces or multiple CORESETs, where the multiple search spaces include the first search space, and the multiple CORESETs include the first CORESET.
Optionally, in this embodiment of the present application, the plurality of search spaces or the plurality of CORESET are used for scheduling data transmission.
Optionally, in this embodiment of the present application, the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indicators TCI.
It should be understood that the terminal device 400 according to the embodiment of the present application may correspond to the terminal device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the terminal device 400 are respectively for implementing the corresponding flow of the terminal device in the method of fig. 2, and are not described herein again for brevity.
Fig. 5 shows a schematic block diagram of a network device 500 of an embodiment of the application. As shown in fig. 5, the network device 500 includes:
a processing unit 510, configured to configure a first search space or a search space corresponding to a first control resource set, to a terminal device, where an aggregation level configured for the first search space or the search space corresponding to the first core set only includes an agreed aggregation level, or a DCI format of downlink control information configured for the first search space or the search space corresponding to the first core set only includes an agreed DCI format, or a search space type configured for the first search space or the search space corresponding to the first core set only includes an agreed search space type.
Optionally, in this embodiment of the present application, the agreed aggregation level is an aggregation level agreed in advance by the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance by the network device and the terminal device.
Optionally, in this embodiment of the present application, the agreed search space type includes a common search space or a UE-specific search space.
Optionally, in this embodiment of the present application, the network device further includes: the terminal device comprises a receiving and sending unit, a processing unit and a processing unit, wherein the receiving and sending unit is used for sending configuration information to the terminal device, the configuration information is used for configuring a plurality of search spaces or a plurality of CORESETs, the plurality of search spaces comprise a first search space, and the plurality of CORESETs comprise the first CORESET.
Optionally, in this embodiment of the present application, the plurality of search spaces or the plurality of CORESET are used for scheduling data transmission.
Optionally, in an embodiment of the present application, optionally, in the embodiment of the present application, the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indicators TCI.
It should be understood that the network device 500 according to the embodiment of the present application may correspond to the network device in the embodiment of the method of the present application, and the above and other operations and/or functions of each unit in the network device 500 are respectively for implementing the corresponding flow of the network device in the method of fig. 3, and are not described herein again for brevity.
As shown in fig. 6, the present embodiment also provides a terminal device 600, where the terminal device 600 may be the terminal device 400 in fig. 4, which can be used to execute the content of the terminal device corresponding to the method 200 in fig. 2. The terminal device 600 shown in fig. 6 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.
Optionally, as shown in fig. 6, the terminal device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.
The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.
Optionally, as shown in fig. 6, the terminal device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.
The transceiver 630 may include a transmitter and a receiver, among others. The transceiver 630 may further include one or more antennas.
Optionally, the terminal device 600 may be the terminal device in the embodiment of the present application, and the terminal device 600 may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
In a specific embodiment, the transceiver unit in the terminal device 400 may be implemented by the transceiver 630 in fig. 6. The processing unit in the terminal device 400 may be implemented by the processor 610 in fig. 6.
As shown in fig. 7, an embodiment of the present application further provides a network device 700, where the network device 700 may be the network device 500 in fig. 5, which can be used to execute the content of the network device corresponding to the method 300 in fig. 3. The network device 700 shown in fig. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 7, network device 700 may also include memory 720. From the memory 720, the processor 710 can call and run a computer program to implement the method in the embodiment of the present application.
The memory 720 may be a separate device from the processor 710, or may be integrated into the processor 710.
Optionally, as shown in fig. 7, the network device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices.
The transceiver 730 may include a transmitter and a receiver, among others. The transceiver 730 may further include an antenna, and the number of antennas may be one or more.
Optionally, the network device 700 may be a network device according to this embodiment, and the network device 700 may implement a corresponding process implemented by the network device in each method according to this embodiment, which is not described herein again for brevity.
In a particular embodiment, the processing unit in the network device 500 may be implemented by the processor 710 in fig. 7. The transceiver unit in the network device 500 may be implemented by the transceiver 730 in fig. 7.
Fig. 8 is a schematic structural diagram of a chip of an embodiment of the present application. The chip 800 shown in fig. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 8, chip 800 may further include a memory 820. From the memory 820, the processor 810 can call and run a computer program to implement the method in the embodiment of the present application.
The memory 820 may be a separate device from the processor 810 or may be integrated into the processor 810.
Optionally, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data transmitted by other devices or chips.
Optionally, the chip 800 may further include an output interface 840. The processor 810 can control the output interface 840 to communicate with other devices or chips, and in particular, can output information or data to other devices or chips.
Optionally, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.
It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.
Fig. 9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in fig. 9, the communication system 900 includes a terminal device 910 and a network device 920.
The terminal device 910 may be configured to implement the corresponding function implemented by the terminal device in the foregoing method, and the network device 920 may be configured to implement the corresponding function implemented by the network device in the foregoing method, for brevity, which is not described herein again.
It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing the computer program.
Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.
Optionally, the computer program product may be applied to the terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the computer program may be applied to the terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (46)
- A method of transmitting information, comprising:the terminal equipment adopts the aggregation level in the appointed aggregation level, or the DCI format based on the appointed DCI format, or carries out the DCI detection in the appointed search space type in the first search space or the search space corresponding to the first control resource set CORESET.
- The method of claim 1, wherein the agreed aggregation level is an agreed aggregation level in advance between the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance between the network device and the terminal device.
- The method of claim 1, wherein the agreed search space type is a common search space or a User Equipment (UE) -specific search space.
- The method according to claim 1 or 2, wherein the DCI detection by the terminal device in the first search space or the search space corresponding to the first control resource set CORESET is performed by using an aggregation level in the agreed aggregation levels, includes:and the terminal equipment only adopts the aggregation grade included in the agreed aggregation grade to perform DCI detection in the aggregation grade configured for the first search space or the search space corresponding to the first CORESET.
- The method according to claim 1 or 2, characterized in that the method further comprises:the terminal device does not expect that the aggregation levels configured for the first search space or the search space corresponding to the first CORESET include other aggregation levels except for the agreed aggregation level.
- The method according to claim 1 or 2, wherein the detecting DCI by the terminal device based on the DCI format in the agreed DCI format in the first search space or the search space corresponding to the first control resource set CORESET includes:and the terminal equipment performs DCI detection only based on the DCI format included in the appointed DCI format in the DCI formats configured for the first search space or the search space corresponding to the first CORESET.
- The method according to claim 1 or 2, characterized in that the method further comprises:the terminal device does not expect that the DCI formats configured for the first search space or the search space corresponding to the first CORESET include other DCI formats other than the agreed DCI format.
- The method of claim 1 or 3, wherein the DCI detection performed by the terminal device in the agreed search space type in the first search space or the search space corresponding to the first control resource set CORESET comprises:the terminal device performs DCI detection only in a search space configured as a common search space in the first search space or all search spaces corresponding to the first CORESET, or,and the terminal equipment only carries out DCI detection in a search space configured as a UE (user equipment) exclusive search space in the first search space or all search spaces corresponding to the first CORESET.
- The method according to claim 1 or 3, characterized in that the method further comprises:the terminal device does not expect that the first search space or the search space corresponding to the first CORESET includes a search space configured as a search space type other than the agreed search space type.
- The method according to any one of claims 1 to 9, further comprising:the terminal device receives configuration information, wherein the configuration information is used for configuring a plurality of search spaces or a plurality of CORESETs, the search spaces comprise the first search space, and the CORESETs comprise the first CORESET.
- The method of claim 10, wherein the plurality of search spaces or the plurality of CORESET are used for scheduling data transmissions.
- The method according to claim 10 or 11, wherein the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indications TCI.
- A method of transmitting information, comprising:the network device configures a first search space or a search space corresponding to a first control resource set (CORESET) to a terminal device, wherein the aggregation level configured for the first search space or the search space corresponding to the first CORESET only includes an agreed aggregation level, or the DCI format of the downlink control information configured for the first search space or the search space corresponding to the first CORESET only includes an agreed DCI format, or the search space type configured for the first search space or the search space corresponding to the first CORESET only includes an agreed search space type.
- The method of claim 13, wherein the agreed aggregation level is an agreed aggregation level in advance between the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance between the network device and the terminal device.
- The method of claim 13, wherein the agreed search space type comprises a common search space or a User Equipment (UE) -specific search space.
- The method according to any one of claims 13 to 15, further comprising:the network device sends configuration information to the terminal device, wherein the configuration information is used for configuring a plurality of search spaces or a plurality of CORESETs, the search spaces comprise a first search space, and the CORESETs comprise a first CORESET.
- The method of claim 16, wherein the plurality of search spaces or the plurality of CORESET are used for scheduling data transmissions.
- The method according to claim 16 or 17, wherein the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indications TCI.
- A terminal device, comprising:and the processing unit is configured to perform DCI detection on downlink control information in a first search space or a search space corresponding to a first control resource set CORESET by using an aggregation level in an agreed aggregation level, or based on a DCI format in an agreed DCI format, or in an agreed search space type.
- The terminal device of claim 19, wherein the agreed aggregation level is an agreed aggregation level in advance between the network device and the terminal device, or the agreed DCI format is a DCI format agreed in advance between the network device and the terminal device.
- The terminal device of claim 19, wherein the agreed search space type is a common search space or a User Equipment (UE) -specific search space.
- The terminal device according to claim 19 or 20, wherein the processing unit is specifically configured to:and in the aggregation levels configured for the first search space or the search space corresponding to the first CORESET, only the aggregation level included in the agreed aggregation level is adopted for DCI detection.
- The terminal device according to claim 19 or 20, wherein the processing unit is further configured to:it is not desirable that the aggregation levels configured for the first search space or the search space corresponding to the first CORESET include aggregation levels other than the agreed aggregation level.
- The terminal device according to claim 19 or 20, wherein the processing unit is specifically configured to:and in the DCI formats configured for the first search space or the search space corresponding to the first CORESET, only performing DCI detection based on the DCI formats included in the agreed DCI formats.
- The terminal device according to claim 19 or 20, wherein the processing unit is further configured to:it is not desirable that the DCI formats configured for the first search space or the search space corresponding to the first CORESET include DCI formats other than the agreed DCI format.
- The terminal device according to claim 19 or 21, wherein the processing unit is specifically configured to:performing DCI detection only in a search space configured as a common search space among the first search space or all search spaces corresponding to the first CORESET, or,and only performing DCI detection in a search space configured as a UE-specific search space in the first search space or all search spaces corresponding to the first CORESET.
- The terminal device according to claim 19 or 21, wherein the processing unit is further configured to:it is not desirable that the first search space or the search space corresponding to the first CORESET include a search space of a search space type other than the agreed search space type.
- The terminal device according to any of claims 19 to 27, wherein the terminal device further comprises:a transceiver unit, configured to receive configuration information, where the configuration information is used to configure multiple search spaces or multiple CORESETs, where the multiple search spaces include the first search space, and the multiple CORESETs include the first CORESET.
- The terminal device of claim 28, wherein the plurality of search spaces or the plurality of CORESET are used for scheduling data transmissions.
- The terminal device according to claim 28 or 29, wherein the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indications TCI.
- A network device, comprising:the processing unit is configured to configure a first search space or a search space corresponding to a first control resource set, where an aggregation level configured for the first search space or the search space corresponding to the first core set only includes an agreed aggregation level, or a DCI format of downlink control information configured for the first search space or the search space corresponding to the first core set only includes an agreed DCI format, or a search space type configured for the first search space or the search space corresponding to the first core set only includes an agreed search space type.
- The network device of claim 31, wherein the agreed aggregation level is an agreed aggregation level in advance between the network device and the terminal device, or wherein the agreed DCI format is a DCI format agreed in advance between the network device and the terminal device.
- The network device of claim 31, wherein the agreed search space type comprises a common search space or a User Equipment (UE) -specific search space.
- The network device of any of claims 31-33, wherein the network device further comprises:the terminal device comprises a receiving and sending unit, a processing unit and a processing unit, wherein the receiving and sending unit is used for sending configuration information to the terminal device, the configuration information is used for configuring a plurality of search spaces or a plurality of CORESETs, the plurality of search spaces comprise a first search space, and the plurality of CORESETs comprise the first CORESET.
- The network device of claim 34, wherein the plurality of search spaces or the plurality of CORESET are used for scheduling data transmissions.
- The network device of claim 34 or 35, wherein the plurality of search spaces or the plurality of CORESET correspond to different transmission configuration indications TCI.
- A terminal device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 1 to 12.
- A network device, comprising: a processor and a memory for storing a computer program, the processor being configured to invoke and execute the computer program stored in the memory to perform the method of any of claims 13 to 18.
- A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 12.
- A chip, comprising: a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 13 to 18.
- A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 12.
- A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 13 to 18.
- A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 12.
- A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 13 to 18.
- A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1 to 12.
- A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 13-18.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/124736 WO2020133176A1 (en) | 2018-12-28 | 2018-12-28 | Information transmission method, terminal device and network device |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111837431A true CN111837431A (en) | 2020-10-27 |
CN111837431B CN111837431B (en) | 2022-01-11 |
Family
ID=71126721
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201880090974.XA Active CN111837431B (en) | 2018-12-28 | 2018-12-28 | Information transmission method, terminal equipment and network equipment |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN111837431B (en) |
WO (1) | WO2020133176A1 (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130077574A1 (en) * | 2010-09-22 | 2013-03-28 | Texas Instruments Incorporated | Resource Allocation and Signaling for Aperiodic Sounding |
CN108811138A (en) * | 2017-05-05 | 2018-11-13 | 北京三星通信技术研究有限公司 | The method and apparatus of transmission control information |
CN109067499A (en) * | 2017-06-13 | 2018-12-21 | 维沃移动通信有限公司 | A kind of sending method of Downlink Control Information, method of reseptance and relevant device |
CN109089316A (en) * | 2017-06-14 | 2018-12-25 | 华为技术有限公司 | Dispatching method and relevant apparatus |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113784451B (en) * | 2018-07-06 | 2024-05-14 | 北京小米移动软件有限公司 | Indication method, device, terminal and base station of control signaling and storage medium |
-
2018
- 2018-12-28 WO PCT/CN2018/124736 patent/WO2020133176A1/en active Application Filing
- 2018-12-28 CN CN201880090974.XA patent/CN111837431B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130077574A1 (en) * | 2010-09-22 | 2013-03-28 | Texas Instruments Incorporated | Resource Allocation and Signaling for Aperiodic Sounding |
CN108811138A (en) * | 2017-05-05 | 2018-11-13 | 北京三星通信技术研究有限公司 | The method and apparatus of transmission control information |
CN109067499A (en) * | 2017-06-13 | 2018-12-21 | 维沃移动通信有限公司 | A kind of sending method of Downlink Control Information, method of reseptance and relevant device |
CN109089316A (en) * | 2017-06-14 | 2018-12-25 | 华为技术有限公司 | Dispatching method and relevant apparatus |
Also Published As
Publication number | Publication date |
---|---|
WO2020133176A1 (en) | 2020-07-02 |
CN111837431B (en) | 2022-01-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12137398B2 (en) | Feedback channel sending method and apparatus, and feedback channel receiving method and apparatus | |
CN112672424B (en) | Wireless communication method, terminal equipment and network equipment | |
CN113316233B (en) | Signal transmission method, network equipment and terminal equipment | |
EP3817474B1 (en) | Method and device for transmitting uplink signal | |
US12089224B2 (en) | Wireless communication method, terminal device and network device | |
CN112369093A (en) | Method and equipment for determining SSB transmission mode of synchronization signal block | |
CN112423370A (en) | Signal transmission method, network equipment and terminal equipment | |
CN113728689A (en) | Wireless communication method, terminal equipment and network equipment | |
CN113170317A (en) | Communication method and device for unlicensed spectrum | |
CN113039842B (en) | Wireless communication method, terminal equipment and network equipment | |
CN111989975A (en) | Method and communication device for signal transmission | |
CN110731116A (en) | Wireless communication method, terminal equipment and network equipment | |
CN112640347A (en) | Wireless communication method, terminal equipment and network equipment | |
CN112655241A (en) | Method for determining transmission mode in sidelink, terminal equipment and network equipment | |
CN113785508A (en) | Wireless communication method, terminal equipment and network equipment | |
CN113557702A (en) | Method and equipment for cell access | |
CN113412649A (en) | Method for monitoring control channel, terminal equipment and network equipment | |
CN113711518A (en) | Method and device for feeding back HARQ information | |
CN113039738A (en) | Transmission method and device of downlink control information | |
CN111837431B (en) | Information transmission method, terminal equipment and network equipment | |
EP3706495B1 (en) | Wireless communication method and device | |
CN114391289A (en) | Wireless communication method and terminal equipment | |
CN113273274A (en) | Method and apparatus for wireless communication | |
CN112703808A (en) | Method and apparatus for BWP handover | |
CN110710276A (en) | Method and equipment for transmitting Physical Random Access Channel (PRACH) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |