Wireless communication method, terminal device and network device
By receiving and analyzing the reserved bits, RNTI and PDCCH time-frequency resources of the target DCI in the terminal device, the terminal device can accurately identify the control information indicated by the network device in the DCI, solving the problem of degradation of communication performance and achieving more efficient communication.
Patent Information
- Application Number
- CN202080105345.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-06
- Publication Date
- 2025-06-06
- Estimated Expiration
- 2040-11-06
AI Technical Summary
In some communication scenarios, the terminal device cannot accurately identify the control information indicated by the network device in the downlink control information (DCI), resulting in a degradation of communication performance.
The target DCI is received through the terminal device, and the control information indicated in the target DCI is determined based on at least one of the information domains in the reserved bits in the target DCI, the RNTI of the scrambled target DCI, and the time-frequency resources occupied by the PDCCH carrying the target DCI.
It realizes that the terminal device can accurately identify the control information in the DCI, thereby correctly receiving the control information, and improving communication performance.
Smart Images

Figure CN116326021B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communications, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art
[0002] In some communication scenarios, network equipment may indicate different types of control information in downlink control information (DCI). In this case, how a terminal device identifies the control information in the DCI is an issue that needs to be addressed urgently. Summary of the invention
[0003] The embodiments of the present application provide a method, terminal device and network device for wireless communication. The terminal device can accurately identify the control information in the DCI, so that the control information in the DCI can be correctly received, thereby improving the communication performance.
[0004] In a first aspect, a wireless communication method is provided, the method comprising:
[0005] The terminal device receives the target DCI;
[0006] The terminal device determines the control information indicated in the target DCI according to at least one of the following:
[0007] At least one information field in the reserved bits in the target DCI;
[0008] Scramble the RNTI of the target DCI;
[0009] The time-frequency resources occupied by the PDCCH carrying the target DCI.
[0010] In a second aspect, a wireless communication method is provided, the method comprising:
[0011] The network device sends the target DCI to the terminal device;
[0012] The control information indicated in the target DCI is determined by at least one of the following:
[0013] At least one information field in the reserved bits in the target DCI;
[0014] Scramble the RNTI of the target DCI;
[0015] The time-frequency resources occupied by the PDCCH carrying the target DCI.
[0016] In a third aspect, a terminal device is provided for executing the method in the first aspect.
[0017] Specifically, the terminal device includes a functional module for executing the method in the above-mentioned first aspect.
[0018] In a fourth aspect, a network device is provided for executing the method in the second aspect.
[0019] Specifically, the network device includes a functional module for executing the method in the above second aspect.
[0020] In a fifth aspect, a terminal device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect.
[0021] In a sixth aspect, a network device is provided, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the second aspect.
[0022] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.
[0023] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.
[0024] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.
[0025] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.
[0026] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.
[0027] Through the above technical solution, the terminal device can determine the control information indicated in the target DCI based on at least one information field in the reserved bits in the target DCI, the RNTI of the encrypted target DCI, and at least one of the time-frequency resources occupied by the PDCCH carrying the target DCI, so that the control information in the DCI can be correctly received and the communication performance can be improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] Figure 1 It is a schematic diagram of a communication system architecture applied in an embodiment of the present application.
[0029] Figure 2 It is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.
[0030] Figure 3 It is a schematic diagram of an identification bit field and a control information field provided according to an embodiment of the present application.
[0031] Figure 4 It is a schematic diagram of a control information field provided according to an embodiment of the present application.
[0032] Figure 5 This is a schematic diagram of an RNTI scrambled DCI provided according to an embodiment of the present application.
[0033] Figure 6 It is a schematic diagram of frequency domain resources occupied by a PDCCH carrying DCI provided according to an embodiment of the present application.
[0034] Figure 7 It is a schematic diagram of time domain resources occupied by a PDCCH carrying DCI provided according to an embodiment of the present application.
[0035] Figure 8 It is a schematic block diagram of a terminal device provided according to an embodiment of the present application.
[0036] Fig. 9 It is a schematic block diagram of a network device provided according to an embodiment of the present application.
[0037] Fig.10 It is a schematic block diagram of a communication device provided according to an embodiment of the present application.
[0038] Fig.11 It is a schematic block diagram of a device provided according to an embodiment of the present application.
[0039] Fig.12 It is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION
[0040] The following will describe the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. For the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0041] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0042] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0043] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0044] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
[0045] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0046] The terminal device can be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, 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 next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0047] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
[0048] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0049] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0050] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device or base station (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0051] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.
[0052] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0053] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographical area and may communicate with terminal devices located in the coverage area.
[0054] Figure 1 One network device and two terminal devices are shown exemplarily. Optionally, the communication system 100 may include multiple network devices and each network device may include another number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0055] Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiments of the present application.
[0056] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1Taking the communication system 100 shown as an example, the communication equipment may include a network device 110 and a terminal device 120 with communication functions. The network device 110 and the terminal device 120 may be the specific devices described above and will not be repeated here. The communication equipment may also include other devices in the communication system 100, such as a network controller, a mobile management entity and other network entities, which is not limited in the embodiments of the present application.
[0057] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0058] The terms used in the implementation mode of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0059] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
[0060] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
[0061] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.
[0062] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0063] In order to facilitate a better understanding of the embodiments of the present application, the reduced capability (RedCap) terminal related to the present application is described.
[0064] The NR system is mainly designed to support Enhanced Mobile Broadband (eMBB) services. Its main technology is to meet the needs of high speed, high spectrum efficiency and large bandwidth. In fact, in addition to eMBB services, there are many different types of services, such as sensor networks, video surveillance, wearables, etc., which have different requirements from eMBB services in terms of speed, bandwidth, power consumption, cost, etc. The capabilities of terminals supporting these services are reduced compared to terminals supporting eMBB, such as reduced supported bandwidth, relaxed processing time, reduced number of antennas, etc. The NR system needs to be optimized for these services and corresponding low-capability terminals. Such a system is called a lightweight NR (NR-light) system. In LTE technology, there are already similar system designs to support terminals with large number of connections, low power consumption and low cost, such as Machine Type Communication (MTC) and Narrow Band Internet of Things (NB-IoT). In the NR system, similar technologies are introduced to use NR technology to better support other types of services besides eMBB services. The terminals that support this type of service are characterized by low complexity, low cost, and low capability, and are called RedCap terminals.
[0065] In order to better understand the embodiments of the present application, a physical broadcast channel (PBCH) related to the present application is described.
[0066] The information carried by the PBCH channel includes A-bit information from the upper layer and additional 8-bit information related to layer 1. The information related to layer 1 includes the system frame number (SFN), half-frame indication, synchronization signal block (SSB) index, etc. The specific definitions are as follows:
[0067] The bits carried by PBCH include the Master Information Block (MIB) from the upper layer, a total of A bits. and 8 bits from layer 1, The definition of A-bit MIB is as described in the following standard, including 6 bits of SFN, 1 bit of subcarrier spacing information, 4 bits of subcarrier offset of SSB, information related to demodulation reference signal (DMRS), resource information of physical downlink control channel (PDCCH) of scheduling system information block (SIB), etc., which also includes 1 idle bit.
[0068] 8 bits for layer 1, middle, The lowest 4 digits of SFN; For half frame indication; when L SSB =64, The highest 3 bits of the SSB index, otherwise, is the parameter k SSB The highest position, is the reserved bit. SSB is the maximum number of SSBs, k SSB Subcarrier offset information of SSB. When the system frequency band is less than 6GHz, that is, L SSB When it is less than 64, 2 bits are reserved for layer 1 related information.
[0069] In the above MIB information, cell restricted (cellBarred) is used to indicate the access control state of the cell. It is used together with the cell reserved for operation use (cellReservedForOperatorUse) and the cell reserved for other use (cellReservedForOtherUse) in SIB1 to determine the access control state of the cell.
[0070] cellBarred="not barred", cellReservedForOperatorUse="not reserved", cellReservedForOtherUse="not true", cell status="not barred", the UE may use the cell as a candidate cell for cell selection or reselection.
[0071] cellBarred="barred", or cellReservedForOtherUse="true", cellstatus="barred".
[0072] cellBarred = "not barred", cellReservedForOperatorUse = "reserved", and cellReservedForOtherUse = not "true", the terminal (UE) assigned to Access Identity 11 or 15 can use the cell as a candidate cell for cell selection or reselection, and the terminal (UE) assigned to Access Identity 1, 2 and 12 to 14 considers the state of the cell to be "barred".
[0073] For a cell, access services can be provided for traditional terminals (UE). When providing services for reduced capability terminals (RedCapUE), there are two ways. One way is that a cell is dedicated to serving RedCap UE. A specific cell can be used to serve RedCap UE. At this time, the access of RedCap UE can be controlled separately, and the existing control method can be used; the other way is that a cell can serve traditional UE and RedCap UE at the same time, that is, the two types of UE coexist in the network. In this way, the access control of traditional UE and RedCap UE needs to be controlled separately, for example, only traditional UE is allowed to access. However, at this stage, the cell status (cell status) is only used for the access control of traditional UE by a cell, and the access control of traditional UE and RedCap UE cannot be performed separately, that is, the access of traditional UE and RedCap UE will be treated equally and cannot be controlled separately.
[0074] It should be noted that the traditional UE may be a non-RedCap UE, or an eMBB UE, or a NR UE. This application does not limit this.
[0075] In some communication scenarios, the network device may indicate different control information in the DCI. In this case, the terminal device cannot recognize the control information in the DCI.
[0076] Based on the above problems, the present application proposes a solution for determining the control information indicated in the DCI, so that the terminal device can accurately identify the control information in the DCI, thereby correctly receiving the control information in the DCI and improving communication performance.
[0077] The technical solution of the present application is described in detail below through specific embodiments.
[0078] Figure 2 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application, such as Figure 2As shown, the method 200 may include at least part of the following contents:
[0079] S210, the network device sends a target DCI to the terminal device;
[0080] S220, the terminal device receives the target DCI;
[0081] S230, the terminal device determines the control information indicated in the target DCI according to at least one of the following:
[0082] At least one information field in the reserved bits in the target DCI; the RNTI for scrambling the target DCI; and the time-frequency resources occupied by the PDCCH carrying the target DCI.
[0083] That is, in the embodiment of the present application, the control information indicated in the target DCI may be determined by at least one of the following:
[0084] At least one information field in the reserved bits in the target DCI; the RNTI for scrambling the target DCI; and the time-frequency resources occupied by the PDCCH carrying the target DCI.
[0085] In the embodiments of the present application, the "reserved bit" may also be referred to as a "reserved bit", which is not limited in the present application.
[0086] Optionally, the target DCI may indicate one or more types of control information, and one or more control information of each type.
[0087] For example, the terminal device can determine the control information indicated in the target DCI based on at least one information field in the reserved bits in the target DCI. By defining at least one information field in the reserved bits in the target DCI to distinguish the values of the reserved bits in the DCI sent by the version 15 (Release 15, Rel-15) or version 16 (Release 16, Rel-16) base station, it is possible to avoid the terminal device not knowing the meaning of the value of the reserved bits in the target DCI and causing a misunderstanding, so that the control information can be correctly received.
[0088] For another example, the terminal device can determine the control information indicated in the target DCI based on the Radio Network Temporary Identity (RNTI) of the scrambled target DCI. By using different scrambled DCI RNTIs corresponding to different control information indicated in the DCI, the terminal device can avoid deviations in understanding the meaning of the bits in the DCI, so that the control information can be correctly received.
[0089] For another example, the terminal device can determine the control information indicated in the target DCI based on the time-frequency resources occupied by the PDCCH carrying the target DCI. By having the time-frequency resources occupied by different PDCCHs carrying DCI correspond to the control information indicated in different DCIs, the terminal device can avoid deviations in its understanding of the meaning of the bits in the DCI, thereby correctly receiving the control information.
[0090] Optionally, in an embodiment of the present application, the control information indicated in the target DCI includes at least control information of the reduced capability terminal.
[0091] Optionally, the control information may be access control information. That is, the control information indicated in the target DCI may at least include access control information of the reduced-capability terminal.
[0092] Of course, the control information in the embodiments of the present application may also be other control information, and the present application is not limited to this.
[0093] Optionally, the format of the target DCI is DCI format 1_0 (DCI format 1_0).
[0094] It should be noted that DCI format 1_0 includes scheduling information of the physical downlink shared channel (PDSCH) carrying SIB1, including frequency domain and time domain resource allocation, modulation and coding scheme, etc. Since DCI format 1_0 is a DCI carried by PDCCH of the common search space, it only contains basic functional domains, the domain size is as fixed as possible, and it is less dependent on the radio resource control (RRC) configuration. In order to reduce the types of DCI sizes, different DCI formats may use the same size, which requires some reserved bits in the DCI. For DCI format 1_0, for the case of authorized spectrum, such as DCI format 1_0 in which the cyclic redundancy check (CRC) is scrambled with the system information RNTI (SI-RNTI), in addition to the useful control information bits, 15 bits are also included as reserved bits that are not used.
[0095] Since the value of the reserved bit is not specified in the standard, the value of the reserved bit is not specified in the implementation of the network equipment, and different manufacturers may set the reserved bit to different values, such as all zero. This poses a problem. When the RedCap UE receives the DCI sent by the Rel-15 or Rel-16 base station, since the RedCap UE does not know the version of the base station, nor does it know the meaning of the value of the reserved bit in the DCI, for example, the Rel-15 or Rel-16 base station sets the reserved bit to 1, and in the Release 17 (Rel-17) standard, the reserved bit is defined as indicating the control access information of the RedCap UE, and the value of 1 indicates that the RedCap UE is allowed to access the cell. When the RedCap UE receives the reserved bit from the Rel-15 or Rel-16 base station, it will mistakenly believe that the cell supports the access of the RedCap UE, and continue to receive the SIB message, causing the RedCap UE to fail in its attempt to access, resulting in additional power consumption.
[0096] Optionally, as Example 1, the terminal device determines the control information indicated in the target DCI based on at least one information field in the reserved bits in the target DCI.
[0097] Optionally, in implementation mode 1 of example 1, the at least one information field includes an identification bit field and a control information field, that is, the reserved bits in the target DCI include an identification bit field and a control information field, such as Figure 3 shown.
[0098] The control information field is used to indicate at least one control information, and the identification bit field is used to indicate the type of control information indicated in the control information field. Alternatively, the identification bit field is used to indicate the meaning of the control information field.
[0099] That is, different values of the bits in the identification bit field may indicate that different types of control information are indicated in the control information field.
[0100] Optionally, in implementation manner 1, the identification bit field is used to indicate that the bits in the control information field are used to indicate RedCap UE access control information.
[0101] Therefore, by defining an identification bit field in the reserved bits in the target DCI to distinguish the reserved values in the DCI sent by the Rel-15 or Rel-16 base station, confusion caused by the RedCap UE not knowing the meaning of the value of the reserved bits in the target DCI can be avoided, so that the access control information for the RedCap UE can be correctly received, avoiding the RedCap UE from blindly attempting to access and causing additional power consumption.
[0102] Optionally, in implementation mode 1, the value of the identification bit field does not include all 0s or all 1s, thereby avoiding confusion caused by the same value as the reserved bit in the base station of Rel-15 or Rel-16.
[0103] Optionally, in implementation 1, the identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold. The first threshold may be pre-configured or agreed upon by a protocol, or the first threshold is configured by a network device.
[0104] Optionally, the number of bits occupied by the identification bit field may also be a fixed value, and the fixed value may be agreed upon by the protocol.
[0105] It should be noted that, the more bits the identification bit field contains, the lower the possibility of confusion due to the same value as the reserved bits in the base station of Rel-15 or Rel-16.
[0106] Optionally, in implementation mode 1, the meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
[0107] For example, the following information can be pre-configured: a bit value of 00 in the identification bit field indicates control information type 1, a bit value of 01 in the identification bit field indicates control information type 2, a bit value of 10 in the identification bit field indicates control information type 3, and a bit value of 11 in the identification bit field indicates control information type 4.
[0108] In implementation mode 1, assuming that the identification bit field contains 5 bits and the control information field contains 2 bits, the meaning of the control information field corresponding to the identification bit field may be shown in the following Table 1, for example.
[0109] Table 1
[0110] Identification bit field (5 bits) Control information type Control information field (e.g. 2 bits) 10101 Control information type 1 Control information 1-4 01010 Control information type 2 Control information 1-4 11100 Control information type 3 Control information 1-4 00011 Control information type 4 Control information 1-4 …… …… ……
[0111] Optionally, in implementation manner 2 of Example 1, the at least one information field includes a control information field, that is, the reserved bits in the target DCI include a control information field, such as Figure 4 shown.
[0112] The control information field is used to indicate at least one control information of the first control information type.
[0113] Optionally, in implementation mode 2, the bits in the control information field are used to indicate RedCap UE access control information.
[0114] Optionally, the control information field includes multiple bits, for example, 3 bits in the reserved bits are defined as the control information field, when the bit value in the control information field is "010", it indicates that the RedCap UE is allowed to access the cell; when the bit value in the control information field is "011", it indicates that the RedCap UE is denied access to the cell. Since the possibility that the specific value of the control information field is the same as the value of the reserved bit in the Rel-15 or Rel-16 base station is low, the RedCap UE can determine that the control information field in the received target DCI carries the access control information of the RedCap UE.
[0115] Therefore, by defining a control information field in the reserved bits in the target DCI to distinguish the reserved values in the DCI sent by the Rel-15 or Rel-16 base station, confusion caused by the RedCap UE not knowing the meaning of the value of the reserved bits in the target DCI can be avoided, so that the access control information for the RedCap UE can be correctly received, avoiding the RedCap UE from blindly attempting to access and causing additional power consumption.
[0116] Optionally, in implementation mode 2, the value of the control information field does not include all 0s or all 1s, thereby avoiding confusion caused by the same value as the reserved bits in the base station of Rel-15 or Rel-16.
[0117] Optionally, in implementation 2, the control information field occupies multiple bits, and the number of bits occupied by the control information field is greater than a second threshold. The second threshold may be pre-configured or agreed upon by a protocol, or the second threshold is configured by a network device.
[0118] Optionally, the number of bits occupied by the control information field may also be a fixed value, and the fixed value may be agreed upon by a protocol.
[0119] It should be noted that the more bits the control information field contains, the lower the possibility of confusion due to the same value as the reserved bits in the Rel-15 or Rel-16 base station.
[0120] Optionally, in implementation mode 2, the meaning indicated by the value of the control information field is pre-configured or agreed upon by the protocol, or the meaning indicated by the value of the control information field is configured by the network device. For example, the following information may be pre-configured: a bit value of 00 in the control information field indicates control information 1, a bit value of 01 in the control information field indicates control information 2, a bit value of 10 in the control information field indicates control information 3, and a bit value of 11 in the control information field indicates control information 4.
[0121] In implementation mode 2, assuming that the control information field contains 5 bits, the meaning of the control information field may be, for example, as shown in Table 2 below.
[0122] Table 2
[0123] Control information field (5 bits) Control Information 10101 Control information 1 01010 Control Information 2 11100 Control Information 3 00011 Control Information 4 …… ……
[0124] Optionally, as Example 2, the terminal device determines the control information indicated in the target DCI according to the RNTI of the scrambled target DCI. That is, different RNTIs of the scrambled DCI correspond to different control information indicated in the DCI.
[0125] Optionally, the target DCI is DCI format 1_0.
[0126] Optionally, the control information may be access control information.
[0127] Optionally, in Example 2, the control information of the reduced capability terminal (RedCap UE) is indicated by the target DCI scrambled by the RNTI corresponding to the reduced capability terminal. For example, the RNTI corresponding to the reduced capability terminal is SI-RNTI-R. That is, SI-RNTI-R is specifically used for RedCap UE to receive DCI format 1_0.
[0128] That is to say, in order to avoid confusion between the traditional UE and the RedCap UE regarding the meaning of the control information in the DCI format 1_0 scrambled by the same SI-RNTI, for the RedCap UE, a new RNTI can be defined to scramble the CRC of the DCI format 1_0. That is, the control information of the RedCap UE is indicated by the DCI format 1_0 scrambled by the SI-RNTI-R corresponding to the RedCap UE.
[0129] Optionally, the SI-RNTI-R scrambled DCI format 1_0 corresponding to the reduced capability terminal and the SI-RNTI scrambled DCI format 1_0 may have the same control information, for example, including:
[0130] Frequency domain resource allocation information, time domain resource allocation information, modulation and coding scheme, redundancy version, mapping method of virtual resource blocks to physical resource blocks, system message indication.
[0131] Optionally, the scheduling information of the SIB in the DCI format 1_0 scrambled by SI-RNTI-R and the DCI format 1_0 scrambled by SI-RNTI is the same, that is, they indicate the same scheduling information of the PDSCH. On this basis, the remaining bits in the DCI can be used to define the access control information indicating the RedCap UE. At this time, due to the difference in RNTI, the RedCap UE will not be confused with the meaning of the bits in the traditional DCI format 1_0. Specifically, Figure 5 shown.
[0132] Optionally, the search space of the PDCCH carrying the DCI format 1_0 scrambled with SI-RNTI-R is the same as the search space of the PDCCH carrying the DCI format 1_0 scrambled with SI-RNTI, and both are indicated by a Master Information Block (MIB).
[0133] Specifically, the format of the DCI scrambled with SI-RNTI-R may not be DCI format 1_0, and the format of the DCI scrambled with SI-RNTI-R may not include the scheduling information of the SIB. The RedCap UE still obtains the scheduling information of the SIB through the DCI format 1_0 scrambled with SI-RNTI.
[0134] Therefore, by using DCI scrambled by different RNTIs, the RedCap UE can avoid being ambiguous about the meaning of the bits in the DCI, can correctly receive the access control information for the RedCap UE, and avoid the RedCap UE blindly trying to access, causing additional power consumption.
[0135] Optionally, as Example 3, the terminal device determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI. That is, the time-frequency resources occupied by different PDCCHs carrying DCI correspond to the control information indicated in different DCIs.
[0136] Optionally, the target DCI is DCI format 1_0. The PDCCH carrying DCI format 1_0 may be a type 0 PDCCH (type0-PDCCH). That is, the PDCCH carrying the target DCI may be a type0-PDCCH.
[0137] Optionally, the control information may be access control information.
[0138] Optionally, the control information of the RedCap UE is indicated by the target DCI received based on a control resource set (Control Resource Set, CORESET) and / or a search space (Search Space) of a PDCCH corresponding to the RedCap UE.
[0139] In one implementation of Example 3, the type0-PDCCH (carrying the target DCI) for RedCap UE and the type0-PDCCH (carrying the target DCI) for traditional UE can be sent on different frequency domain bandwidths. Therefore, there is no confusion about the meaning of the bits caused by DCI sharing, and the access control information of RedCap UE can be indicated in the DCI carried in the type0-PDCCH for RedCap UE. Figure 6 As shown, the type0-PDCCH of the RedCap UE and the type0-PDCCH of the legacy UE are sent on different bandwidth parts (Band Width Part, BWP).
[0140] In another implementation of Example 3, if the type0-PDCCH (carrying target DCI) for RedCap UE and the type0-PDCCH (carrying target DCI) for traditional UE are sent on the same frequency domain resources, that is, their corresponding CORESET 0 is the same, it can also be specified that their monitoring timing is different, that is, Search Space 0 is different, so that the type0-PDCCH for RedCap UE and the type0-PDCCH for traditional UE are sent on different time domain resources. Therefore, there is no confusion about the meaning of the bits caused by DCI sharing, and the access control information of RedCap UE can be indicated in the DCI carried in the type0-PDCCH for RedCap UE. Figure 7 As shown, the type0-PDCCH of the RedCap UE and the type0-PDCCH of the traditional UE have different monitoring opportunities.
[0141] Specifically, after the RedCap UE obtains the SIB1 information through the MIB, it obtains CORESET 0 and Search Space 0, and determines at least one of the CORESET and SearchSpace for the RedCap UE based on the association relationship, which can be called CORESET 0-R and Search Space 0-R. The association relationship can be determined by pre-configuration or protocol agreement rules. Since at least one of the CORESET and Search Space of the type0-PDCCH of the RedCap UE and the traditional UE is different, there is no confusion about the meaning of the bits caused by the sharing of DCI, and the access control information of the RedCap UE can be indicated in the DCI carried in the type0-PDCCH for the RedCap UE.
[0142] Therefore, by using different time domain or frequency domain resources for PDCCH of traditional UE and RedCap UE, the ambiguity of the meaning of the bits in DCI for RedCap UE can be avoided, and the access control information for RedCap UE can be correctly received, which avoids the RedCap UE from blindly trying to access and causing additional power consumption.
[0143] It should be noted that in the embodiment of the present application, the traditional UE may be a non-RedCap UE, or an eMBB UE, or a NR UE. The present application does not limit this.
[0144] Therefore, in an embodiment of the present application, the terminal device can determine the control information indicated in the target DCI based on at least one information field in the reserved bits in the target DCI, the RNTI of the encrypted target DCI, and at least one of the time-frequency resources occupied by the PDCCH carrying the target DCI, so that the control information in the DCI can be correctly received and the communication performance can be improved.
[0145] For example, the terminal device can determine the control information indicated in the target DCI based on at least one information field in the reserved bits in the target DCI. By defining at least one information field in the reserved bits in the target DCI to distinguish the values of the reserved bits in the DCI sent by the Rel-15 or Rel-16 base station, it is possible to avoid the terminal device not knowing the meaning of the values of the reserved bits in the target DCI and causing misunderstandings, so that the control information can be correctly received.
[0146] For another example, the terminal device can determine the control information indicated in the target DCI based on the RNTI of the scrambled target DCI. By having different scrambled DCI RNTIs correspond to different control information indicated in the DCI, the terminal device can avoid deviations in understanding the meaning of the bits in the DCI, so that the control information can be correctly received.
[0147] For another example, the terminal device can determine the control information indicated in the target DCI based on the time-frequency resources occupied by the PDCCH carrying the target DCI. By having the time-frequency resources occupied by different PDCCHs carrying DCI correspond to the control information indicated in different DCIs, the terminal device can avoid deviations in its understanding of the meaning of the bits in the DCI, thereby correctly receiving the control information.
[0148] Combination of the above Figures 2 to 7 , describes in detail the method embodiment of the present application, and the following is combined with Figures 8 to 12 , the device embodiments of the present application are described in detail. It should be understood that the device embodiments and the method embodiments correspond to each other, and similar descriptions can refer to the method embodiments.
[0149] Figure 8 FIG. 3 shows a schematic block diagram of a terminal device 300 according to an embodiment of the present application. Figure 8 As shown, the terminal device 300 includes:
[0150] The communication unit 310 is configured to receive target downlink control information DCI;
[0151] The processing unit 320 is configured to determine the control information indicated in the target DCI according to at least one of the following:
[0152] At least one information field in the reserved bits in the target DCI;
[0153] A radio network temporary identifier RNTI for scrambling the target DCI;
[0154] The time-frequency resources occupied by the physical downlink control channel PDCCH that carries the target DCI.
[0155] Optionally, the at least one information field includes an identification bit field and a control information field;
[0156] The control information field is used to indicate at least one control information, and the identification bit field is used to indicate the type of control information indicated in the control information field.
[0157] Optionally, the value of the identification bit field does not include all 0s or all 1s.
[0158] Optionally, the identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
[0159] Optionally, the meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
[0160] Optionally, the at least one information field includes a control information field;
[0161] The control information field is used to indicate at least one control information of the first control information type.
[0162] Optionally, the value of the control information field does not include all 0s or all 1s.
[0163] Optionally, the control information field occupies multiple bits, and the number of bits occupied by the control information field is greater than a second threshold.
[0164] Optionally, the meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
[0165] Optionally, when the terminal device determines the control information indicated in the target DCI according to the RNTI that scrambles the target DCI,
[0166] The control information of the reduced capability terminal is indicated by the target DCI scrambled by the RNTI corresponding to the reduced capability terminal.
[0167] Optionally, when the terminal device determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI,
[0168] The control information of the reduced capability terminal is indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal.
[0169] Optionally, the control information indicated in the target DCI includes at least control information of the reduced capability terminal.
[0170] Optionally, the control information is access control information.
[0171] Optionally, the format of the target DCI is DCI format 1_0.
[0172] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.
[0173] It should be understood that the terminal device 300 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the terminal device 300 are respectively to implement Figure 2 For the sake of brevity, the corresponding process of the terminal device in the method 200 is not repeated here.
[0174] Fig. 9 FIG. 4 shows a schematic block diagram of a network device 400 according to an embodiment of the present application. Fig. 9 As shown, the network device 400 includes:
[0175] The communication unit 410 is configured to send target downlink control information DCI to the terminal device;
[0176] The control information indicated in the target DCI is determined by at least one of the following:
[0177] At least one information field in the reserved bits in the target DCI;
[0178] A radio network temporary identifier RNTI for scrambling the target DCI;
[0179] The time-frequency resources occupied by the physical downlink control channel PDCCH that carries the target DCI.
[0180] Optionally, the at least one information field includes an identification bit field and a control information field;
[0181] The control information field is used to indicate at least one control information, and the identification bit field is used to indicate the type of control information indicated in the control information field.
[0182] Optionally, the value of the identification bit field does not include all 0s or all 1s.
[0183] Optionally, the identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
[0184] Optionally, the meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
[0185] Optionally, the at least one information field includes a control information field;
[0186] The control information field is used to indicate at least one control information of the first control information type.
[0187] Optionally, the value of the control information field does not include all 0s or all 1s.
[0188] Optionally, the control information field occupies multiple bits, and the number of bits occupied by the control information field is greater than a second threshold.
[0189] Optionally, the meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
[0190] Optionally, when the terminal device determines the control information indicated in the target DCI according to the RNTI that scrambles the target DCI,
[0191] The control information of the reduced capability terminal is indicated by the target DCI scrambled by the RNTI corresponding to the reduced capability terminal.
[0192] Optionally, when the terminal device determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI,
[0193] The control information of the reduced capability terminal is indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal.
[0194] Optionally, the control information indicated in the target DCI includes at least control information of the reduced capability terminal.
[0195] Optionally, the control information is access control information.
[0196] Optionally, the format of the target DCI is DCI format 1_0.
[0197] Optionally, in some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.
[0198] It should be understood that the network device 400 according to the embodiment of the present application may correspond to the network device in the method embodiment of the present application, and the above and other operations and / or functions of each unit in the network device 400 are respectively to implement Figure 2 For the sake of brevity, the corresponding processes of the network device in the method 200 are not described in detail here.
[0199] Fig.10 It is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. Fig.10 The communication device 500 shown includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0200] Alternatively, if Fig.10As shown, the communication device 500 may further include a memory 520. The processor 510 may call and run a computer program from the memory 520 to implement the method in the embodiment of the present application.
[0201] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .
[0202] Alternatively, if Fig.10 As shown, the communication device 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0203] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of the antennas may be one or more.
[0204] Optionally, the communication device 500 may specifically be a network device in an embodiment of the present application, and the communication device 500 may implement corresponding processes implemented by the network device in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0205] Optionally, the communication device 500 may specifically be a mobile terminal / terminal device of an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described again for the sake of brevity.
[0206] Fig.11 It is a schematic structural diagram of the device of an embodiment of the present application. Fig.11 The device 600 shown includes a processor 610, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0207] Alternatively, if Fig.11 As shown, the apparatus 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.
[0208] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .
[0209] Optionally, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0210] Optionally, the apparatus 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0211] Optionally, the device can be applied to the network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the network equipment in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.
[0212] Optionally, the apparatus may be applied to a mobile terminal / terminal device in an embodiment of the present application, and the apparatus may implement corresponding processes implemented by the mobile terminal / terminal device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0213] Optionally, the device mentioned in the embodiment of the present application may also be a chip, for example, a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.
[0214] Fig.12 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. Fig.12 As shown, the communication system 700 includes a terminal device 710 and a network device 720 .
[0215] Among them, the terminal device 710 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 720 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.
[0216] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by the hardware integrated logic circuit or software instructions in the processor. The above processor can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor are combined and performed. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
[0217] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0218] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0219] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.
[0220] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0221] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0222] An embodiment of the present application also provides a computer program product, including computer program instructions.
[0223] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0224] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0225] The embodiment of the present application also provides a computer program.
[0226] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods in the embodiments of the present application. For the sake of brevity, they are not described here.
[0227] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.
[0228] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0229] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0230] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0231] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0232] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0233] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0234] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method of wireless communication, It is characterized in that include: The terminal device receives target downlink control information DCI; wherein the control information indicated in the target DCI at least includes control information of the reduced capability terminal; The terminal device determines the control information indicated in the target DCI according to the following two methods: At least one information field in the reserved bits in the target DCI; The time-frequency resources occupied by the physical downlink control channel PDCCH carrying the target DCI; The at least one information field includes an identification bit field and a control information field, the control information field is used to indicate at least one control information, and the identification bit field is used to indicate a type of control information indicated in the control information field; Wherein, in a case where the terminal device further determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI, the control information of the reduced capability terminal is further indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal, wherein the PDCCH corresponding to the reduced capability terminal is sent on an independent frequency domain bandwidth; Among them, the value of the identification bit field does not include all 0s or all 1s, and the value of the control information field does not include all 0s or all 1s.
2. The method according to claim 1, It is characterized in that The identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
3. The method according to claim 1, It is characterized in that The meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
4. The method according to claim 1, It is characterized in that The control information field occupies a plurality of bits, and the number of bits occupied by the control information field is greater than a second threshold.
5. The method according to claim 1, It is characterized in that The meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
6. The method according to any one of claims 1 to 5, It is characterized in that The control information is access control information.
7. The method according to any one of claims 1 to 5, It is characterized in that The format of the target DCI is DCI format 1_0.
8. A method of wireless communication, It is characterized in that include: The network device sends target downlink control information DCI to the terminal device; wherein the control information indicated in the target DCI at least includes control information of the reduced capability terminal; The control information indicated in the target DCI is determined by the following two methods: At least one information field in the reserved bits in the target DCI; The time-frequency resources occupied by the physical downlink control channel PDCCH carrying the target DCI; The at least one information field includes an identification bit field and a control information field, the control information field is used to indicate at least one control information, and the identification bit field is used to indicate a type of control information indicated in the control information field; Wherein, in a case where the terminal device further determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI, the control information of the reduced capability terminal is further indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal, wherein the PDCCH corresponding to the reduced capability terminal is sent on an independent frequency domain bandwidth; Among them, the value of the identification bit field does not include all 0s or all 1s, and the value of the control information field does not include all 0s or all 1s.
9. The method according to claim 8, It is characterized in that The identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
10. The method according to claim 8, It is characterized in that The meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
11. The method according to claim 8, It is characterized in that The control information field occupies a plurality of bits, and the number of bits occupied by the control information field is greater than a second threshold.
12. The method according to claim 8, It is characterized in that The meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
13. The method according to any one of claims 8 to 12, It is characterized in that The control information is access control information.
14. The method according to any one of claims 8 to 12, It is characterized in that The format of the target DCI is DCI format 1_0.
15. A terminal device, It is characterized in that include: A communication unit, configured to receive target downlink control information DCI; wherein the control information indicated in the target DCI at least includes control information of a reduced capability terminal; A processing unit, configured to determine the control information indicated in the target DCI according to the following two methods: At least one information field in the reserved bits in the target DCI; The time-frequency resources occupied by the physical downlink control channel PDCCH carrying the target DCI; The at least one information field includes an identification bit field and a control information field, the control information field is used to indicate at least one control information, and the identification bit field is used to indicate a type of control information indicated in the control information field; Wherein, in a case where the terminal device further determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI, the control information of the reduced capability terminal is further indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal, wherein the PDCCH corresponding to the reduced capability terminal is sent on an independent frequency domain bandwidth; Among them, the value of the identification bit field does not include all 0s or all 1s, and the value of the control information field does not include all 0s or all 1s.
16. The terminal device according to claim 15, It is characterized in that The identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
17. The terminal device according to claim 15, It is characterized in that The meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
18. The terminal device according to claim 15, It is characterized in that The control information field occupies a plurality of bits, and the number of bits occupied by the control information field is greater than a second threshold.
19. The terminal device according to claim 15, It is characterized in that The meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
20. The terminal device according to any one of claims 15 to 19, It is characterized in that The control information is access control information.
21. The terminal device according to any one of claims 15 to 19, It is characterized in that The format of the target DCI is DCI format 1_0.
22. A network device, It is characterized in that include: A communication unit, configured to send target downlink control information DCI to a terminal device; wherein the control information indicated in the target DCI at least includes control information of a reduced capability terminal; The control information indicated in the target DCI is determined by the following two methods: At least one information field in the reserved bits in the target DCI; The time-frequency resources occupied by the physical downlink control channel PDCCH carrying the target DCI; The at least one information field includes an identification bit field and a control information field, the control information field is used to indicate at least one control information, and the identification bit field is used to indicate a type of control information indicated in the control information field; Wherein, in a case where the terminal device further determines the control information indicated in the target DCI according to the time-frequency resources occupied by the PDCCH carrying the target DCI, the control information of the reduced capability terminal is further indicated by the target DCI received based on the control resource set and / or search space of the PDCCH corresponding to the reduced capability terminal, wherein the PDCCH corresponding to the reduced capability terminal is sent on an independent frequency domain bandwidth; Among them, the value of the identification bit field does not include all 0s or all 1s, and the value of the control information field does not include all 0s or all 1s.
23. The network device according to claim 22, It is characterized in that The identification bit field occupies multiple bits, and the number of bits occupied by the identification bit field is greater than a first threshold.
24. The network device according to claim 22, It is characterized in that The meaning indicated by the value of the identification bit field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the identification bit field is configured by a network device.
25. The network device according to claim 22, It is characterized in that In the case that the at least one information field includes the control information field, the control information field occupies a plurality of bits, and the number of bits occupied by the control information field is greater than a second threshold.
26. The network device according to claim 22, It is characterized in that In the case where the at least one information field includes the control information field, the meaning indicated by the value of the control information field is pre-configured or agreed upon by a protocol, or the meaning indicated by the value of the control information field is configured by a network device.
27. The network device according to any one of claims 22 to 26, It is characterized in that The control information is access control information.
28. The network device according to any one of claims 22 to 26, It is characterized in that The format of the target DCI is DCI format 1_0.
29. A terminal device, It is characterized in that include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 7.
30. A network device, It is characterized in that include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 8 to 14.
31. A chip, It is characterized in that include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 7.
32. A chip, It is characterized in that include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 8 to 14.
33. A computer readable storage medium, It is characterized in that Used to store a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 7.
34. A computer readable storage medium, It is characterized in that Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 8 to 14.