Method performed by a user equipment and user equipment

Abstract

The present application provides a method executed by a user equipment (UE), comprising: receiving bandwidth part (BWP) configuration information of a UE type of a network for the UE, wherein a BWP corresponding to the BWP configuration information is different from an initial downlink BWP of a cell; and determining, by the UE, at least one of a physical downlink control channel (PDCCH) position in a common search space, a width of a frequency domain indication field in downlink control information (DCI) for data scheduling, a value, and a position of scheduled physical downlink shared channel (PDSCH) resources according to the received BWP configuration information.

Description

Technical Field

[0001] This invention relates to the field of wireless communication technology, and more particularly to a method performed by a user equipment and a corresponding user equipment. Background Technology

[0002] In existing 5G / NR networks, three typical service models are defined: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC). In addition to these, there are also time-sensitive communication (TSC) services.

[0003] A key objective of 5G is to enable interconnected industries. 5G connectivity can act as a catalyst for the next wave of industrial transformation and digitalization, enhancing flexibility, increasing productivity and efficiency, reducing maintenance costs, and improving operational safety. Devices in this environment include pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, and actuators. These sensors and actuators need to be connected to the 5G wireless access network and core network. Documents such as TR 22.804 describe large-scale industrial wireless sensor network (IWSN) use cases and requirements, encompassing not only the very high-demand URLLC services but also relatively low-end services requiring smaller size and / or several years of battery life in wireless mode. The requirements for these services are higher than LPWA (Low Power Wide Area Network) but lower than URLCC and eMBB.

[0004] Similar to the internet industry, 5G interconnectivity can be a catalyst for the next wave of smart city innovation. As an example, TSR22.804 describes smart city use cases and requirements. Vertical coverage of data collection and processing in smart cities allows for more effective monitoring and control of urban resources and services for city residents. In particular, the deployment of surveillance cameras is a crucial component of smart cities, as well as in factories and industries.

[0005] Finally, examples of wearable devices include smartwatches / rings, eHealth-related devices, and medical monitoring devices. A key characteristic of this scenario is the requirement for compact device size.

[0006] As a baseline, the requirements for these three use cases are:

[0007] General requirements:

[0008] • Equipment complexity: The primary motivation for this new equipment type is to reduce equipment cost and complexity compared to eMBB and URLLC devices, especially in the case of industrial sensors.

[0009] • Device size: Most use cases require a compact device design.

[0010] • Deployment scenario: The system should support all FR1 / FR2 bands of FDD and TDD.

[0011] Specific requirements for use cases:

[0012] • Industrial Wireless Sensors: Use cases and requirements are described in TR 22.832 and TS 22.104: Communication service availability is 99.99%, and end-to-end latency is less than 100 milliseconds. The reference bit rate is less than 2 Mbps (potentially asymmetric, such as under uplink heavy load), and is smooth for all use cases and devices. Battery life should be at least several years. For safety-related sensors, lower latency requirements are needed, 5-10 ms (TR 22.804).

[0013] • Video surveillance: In TSR 22.804, the reference economic video bitrate is 2-4 Mbps, latency is less than 500 ms, and reliability is 99%-99.9%. High-end video, such as in agriculture, requires 7.5-25 Mbps. The business model is likely to be primarily based on UL transmission.

[0014] • Wearable devices: The reference bit rate for smart wearable applications can be 5-50 Mbps, with a minimum of 2-5 Mbps in DL. Devices can achieve higher peak bit rates, such as up to 150 Mbps downlink and up to 50 Mbps uplink. The device's battery should last 1-2 weeks.

[0015] New demand scenarios place higher demands on network transmission, especially as terminal devices need to achieve reception capabilities that match services under constraints such as smaller size, lower processing complexity, fewer antennas, and smaller bandwidth. These all require improvements to existing air interface resource allocation methods and channel transmission methods. Summary of the Invention

[0016] To address at least some of the aforementioned problems, the present invention provides a method and a user equipment executed by a user equipment, enabling terminals with limited bandwidth capabilities to access the network and perform related service transmissions, thereby enhancing the network's service capabilities, expanding network compatibility, and significantly reducing the cost of communication network deployment.

[0017] According to the present invention, a method executed by a user equipment (UE) is proposed, comprising: receiving bandwidth segment (BWP) configuration information configured by the network for the UE type, wherein the BWP corresponding to the BWP configuration information is different from the cell initial downlink BWP; and determining, based on the received BWP configuration information, at least one of the following: the physical downlink control channel (PDCCH) location in the common search space, the width and value of the frequency domain indication field in the downlink control information (DCI) for data scheduling, and the location of the scheduled physical downlink shared channel (PDSCH) resource.

[0018] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine at least one of the width, value, and location of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resources; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE uses the bandwidth of the BWP and the subcarrier spacing parameters to determine at least one of the width, value, and location of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resources.

[0019] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0, the UE uses the random access search space on the initial BWP of the cell to receive the PDCCH for the random access procedure of the UE; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.

[0020] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine at least one of the width, value, and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resource; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the bandwidth of the BWP and the subcarrier spacing parameter to determine at least one of the width, value, and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resource.

[0021] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the random access search space on the initial BWP of the cell to receive the PDCCH for the random access procedure of the UE; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.

[0022] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine at least one of the width, value, and location of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resource; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0, the subcarrier spacing parameter, and the starting position of the BWP to determine at least one of the width, value, and location of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resource; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the bandwidth of the BWP and the subcarrier spacing parameter to determine at least one of the width, value, and location of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resource.

[0023] Preferably, if the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the random access search space on the initial BWP of the cell to receive the PDCCH for the random access procedure of the UE; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the CORESET on the BWP with the same size as CORESET0 to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH for the random access procedure on the random access search space of the initial BWP of the cell; if the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the CORESET on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH on the random access search space of the initial BWP of the cell.

[0024] Preferably, if the UE receives a BWP configured for the UE by the network, the UE uses the bandwidth of the BWP to determine at least one of the width, value, and location of the scheduled PDSCH resource in the DCI; if the UE does not receive a BWP configured for the UE by the network, the UE uses a cell-related initial BWP or CORESET0 to determine at least one of the width, value, and location of the scheduled PDSCH resource in the DCI.

[0025] Preferably, if the UE receives a BWP configured for the UE by the network, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH on the random access search space of the initial cell BWP; if the UE does not receive a BWP configured for the UE by the network, the UE uses the random access search space on the initial cell BWP to receive the PDCCH for the random access procedure of the UE.

[0026] Furthermore, according to the present invention, a user equipment is provided, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, perform the methods described above.

[0027] According to the present invention, terminals with limited bandwidth capabilities can access the network and perform related service transmissions, thereby improving the network's service capabilities, expanding network compatibility, and significantly reducing the cost of communication network deployment. Attached Figure Description

[0028] The above and other features of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0029] Figure 1 This is a flowchart illustrating a method performed by a user equipment according to Embodiment 1 of the present invention.

[0030] Figure 2 This is a schematic block diagram illustrating the user equipment involved in the present invention. Detailed Implementation

[0031] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the present invention should not be limited to the specific embodiments described below; these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art. Furthermore, for the sake of simplicity, detailed descriptions of well-known technologies not directly related to the present invention have been omitted to prevent confusion in understanding the invention.

[0032] Generally, unless a different meaning is clearly given and / or implied in the context of its use, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless expressly stated otherwise, all references to "a / an / element, device, component, part, step, etc." shall be construed as referring to at least one instance of that element, device, component, part, step, etc. Unless it must be explicitly stated that a step is described as occurring after or before another step and / or implicitly implied that a step must occur after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa.

[0033] The following description uses 5G / NR mobile communication systems and their subsequent evolutions as example application environments to specifically describe several embodiments according to the present invention. However, it should be noted that the present invention is not limited to the following embodiments, but is applicable to many other wireless communication systems, such as communication systems after 5G and 4G mobile communication systems before 5G, 802.11 wireless networks, etc.

[0034] The following describes some of the terms involved in this invention. Unless otherwise specified, the terms used in this invention are as defined herein. The terms given in this invention may be named differently in LTE, LTE-Advanced, LTE-Advanced Pro, NR and later or other communication systems, but a unified terminology is used in this invention. When applied to a specific system, it can be replaced with the terminology used in the corresponding system.

[0035] 3GPP: 3rd Generation Partnership Project

[0036] LTE: Long Term Evolution

[0037] NR: New Radio, New Wireless, New Air Interface

[0038] UE: User Equipment

[0039] eNB: evolved NodeB

[0040] gNB: NR base station

[0041] kssb: SSB subcarrier offset

[0042] TTI: Transmission Time Interval

[0043] OFDM: Orthogonal Frequency Division Multiplexing

[0044] CP-OFDM: Cyclic Prefix Orthogonal Frequency Division Multiplexing

[0045] C-RNTI: Cell Radio Network Temporary Identifier

[0046] CSI: Channel State Information

[0047] HARQ: Hybrid Automatic Repeat Request.

[0048] CSI-RS: Channel State Information Reference Signal

[0049] CRS: Cell Reference Signal

[0050] PBCH: Physical broadcast channel

[0051] PUCCH: Physical Uplink Control Channel

[0052] PUSCH: Physical Uplink Shared Channel

[0053] PRACH: Physical random-access channel

[0054] PDSCH: Physical downlink shared channel

[0055] PDCCH: Physical downlink control channel

[0056] UL-SCH: Uplink Shared Channel

[0057] DL-SCH: Downlink Shared Channel

[0058] RACH: Random-access channel

[0059] DCI: Downlink Control Information

[0060] CG: Configured Grant

[0061] MCS: Modulation and Coding Scheme

[0062] RB: Resource Block

[0063] RE: Resource Element

[0064] CRB: Common Resource Block

[0065] CP: Cyclic Prefix

[0066] PRB: Physical Resource Block

[0067] VRB: Virtual resource block

[0068] FDM: Frequency Division Multiplexing

[0069] TDD: Time Division Duplexing

[0070] FDD: Frequency Division Duplexing

[0071] RRC: Radio Resource Control

[0072] RSRP: Reference Signal Receiving Power

[0073] SRS: Sounding Reference Signal

[0074] DMRS: Demodulation Reference Signal

[0075] CSI-RS: Channel state information reference signal

[0076] CRC: Cyclic Redundancy Check

[0077] SFI: Slot Format Indication

[0078] SIB: System Information Block

[0079] SIB1: System Information Block Type 1

[0080] PSS: Primary Synchronization Signal

[0081] SSS: Secondary Synchronization Signal

[0082] SSB: Synchronization Signal Block

[0083] CRB: Common Resource Block

[0084] BWP: Bandwidth Part

[0085] SFN: System Frame Number

[0086] PCI: Physical Cell ID

[0087] IE: Information Element

[0088] EN-DC: EUTRA-NR Dual Connection, LTE-NR Dual Connectivity

[0089] MCG: Master Cell Group

[0090] SCG: Secondary Cell Group

[0091] PCell: Primary Cell

[0092] SCell: Secondary Cell

[0093] SPS: Semi-Persistant Scheduling

[0094] TA: Timing Advance, uplink timing advance

[0095] PT-RS: Phase-Tracking Reference Signals

[0096] TB: Transport Block

[0097] TBS: Transport Block Size

[0098] CB: Code Block

[0099] QPSK: Quadrature Phase Shift Keying

[0100] 16 / 64 / 256QAM: 16 / 64 / 256 Quadrature Amplitude Modulation.

[0101] AGC: Auto Gain Control

[0102] TDRA (field): Time Domain Resource Assignment.

[0103] FDRA (field): Frequency Domain Resource Assignment.

[0104] ARFCN: Absolute Radio Frequency Channel Number

[0105] RedCap Device: Reduced Capability Device.

[0106] CORESET: Control resource set.

[0107] CORESET0: Control resource set 0, control resource set number 0

[0108] CCE: Control channel element

[0109] REG: Resource Element Group

[0110] MIB: Master Information Block

[0111] DRX: Discontinuous Reception

[0112] AL: Aggregation Level

[0113] UCI: Uplink Control Information

[0114] CSS: Common search space

[0115] USS: User-specific search space

[0116] SCS: Sub-carrier spacing

[0117] SLIV: Start and length indicator value

[0118] RIV: Resource indicator value

[0119] SS-RSRP: Synchronization Signal Reference Signal Received Power

[0120] SS-RSRQ: Synchronization Signal Reference Signal Received Quality.

[0121] FR1: Frequency range 1 as defined in TS 38.104.

[0122] FR2: Frequency range 2 as defined in TS 38.104.

[0123] The following is a description of prior art associated with the present invention. Unless otherwise specified, the same terms in the specific embodiments have the same meaning as in the prior art.

[0124] It is worth noting that the user equipment and terminal equipment mentioned in this specification have the same meaning, and UE can also refer to a terminal. No specific distinction or limitation will be made thereafter. Similarly, network equipment refers to devices that communicate with terminals, including but not limited to base station equipment, gNB, eNB, wireless AP, etc., without specific distinction or limitation.

[0125] The network uses BWP configuration to determine information such as bandwidth required for service transmission with the terminal. BWP configuration includes parameters such as bandwidth, location, subcarrier spacing, and cyclic prefix. Data transmission between the network and the terminal occurs on the BWP. For example, the network can use scheduling information (DCI) in the PDCCH to indicate which symbols are used on which RBs of the BWP for the scheduled resource blocks, as well as other relevant receive or transmit configuration information, to transmit data with the terminal.

[0126] The network configures the CORESET on the BWP for PDCCH reception. The network also configures search space parameters to determine the CORESET that the terminal needs to detect and the corresponding time domain position and other parameters.

[0127] The network can configure an initial uplink BWP and an initial downlink BWP for the cell, which are used by the terminal for random access or data transmission. If the network does not configure the initial downlink BWP through the fields in the SIB1 signaling, the terminal will use the bandwidth determined by CORESET0 as the initial downlink BWP.

[0128] The terminal device can receive the PDCCH based on the received parameters and related protocol procedures. The PDCCH indicates the transmission configuration information of the scheduled PDSCH, including the PDSCH's time-frequency location, resource configuration, and other necessary parameters. The terminal receives the relevant PDSCH according to the PDSCH configuration parameters.

[0129] Network devices periodically send broadcast information containing parameters used to determine various cell configurations. For example, a cell sends MIB information indicating the CORESET and search space configuration information used to receive the PDCCH. Based on the PDCCH indication, the terminal can obtain the time-frequency position, bandwidth, and other relevant configuration parameters of the channel, such as SIB1 and other information, and obtain more relevant information for accessing the cell and transmitting data.

[0130] A concrete example is that the network indicates the relevant parameters for CORESET0 and Search Space 0 in the MIB, and the terminal can receive the PDCCH on the corresponding time-frequency resources. The PDCCH indicates the parameters of the PDSCH used to transmit SIB1. The terminal receives the PDSCH, obtains the SIB1 information, and acquires the configuration, parameters, and other information used for service transmission. The terminal can also receive other SIB information in a similar manner to obtain more service configuration information.

[0131] The SIB1 information can contain parameters for the terminal to perform random access and data transmission, such as downlink initial BWP parameters, uplink initial BWP parameters, random access channel parameters, and random access search space parameters. In a specific example, if the terminal meets the network access conditions, such as the uplink or downlink bandwidth supported by the terminal being greater than the uplink or downlink BWP bandwidth configured by the network, the terminal can access the network by sending a random access signal through the random access channel. Upon receiving the terminal's random access signal, the network responds and indicates relevant information through the PDCCH and scheduled PDSCH signals in the relevant common search space, such as notifying the UE to configure uplink transmission resources. The terminal initiates a relevant request on the indicated uplink resources, such as a radio network connection request signaling. The network can respond to this request and send appropriate response information through the PDCCH and scheduled PDSCH signals in the common search space, thereby establishing a radio link connection between the network and the terminal.

[0132] The network can also indicate configuration parameters for a certain type of terminal through SIB1 or other RRC signaling, enabling that type of terminal to perform random access or data transmission processes in the network.

[0133] A network can define terminal types or categories. For example, it can define a low-complexity terminal based on a specific physical layer capability or a combination of capabilities, such as the number of channels, processing time limits, maximum bandwidth, and duplex capability. A network can also define a terminal type to identify multiple capability sets with different combinations of capabilities. Terminal type information can be used by the network to allow or prohibit that type of terminal from accessing the network, to configure appropriate parameters for that type of terminal for its access or data transmission, or to restrict the use of certain parameters by that type of terminal.

[0134] For some terminal devices, when accessing a network, the received SIB1 information reveals that their maximum supported bandwidth is less than the bandwidth of the uplink initial BWP or downlink initial BWP indicated by the network, but greater than the maximum bandwidth the network uses to send SIB1 information. In this case, the network can configure these devices with an uplink and / or downlink BWP that is different from the uplink or downlink initial BWP. This BWP's bandwidth is less than or equal to the maximum bandwidth supported by the terminal device, allowing these terminal devices to perform random access within the cell, as well as send and receive relevant information. In this scenario, the network configuration enables terminals with limited bandwidth capabilities to access the network and perform related service transmissions even when the initial BWP bandwidth indicated in the network's SIB1 exceeds the terminal's capability. This improves the network's service capabilities, expands network compatibility, and significantly reduces the cost of communication network deployment. Simultaneously, this solution reduces the bandwidth requirements of the terminals, resulting in significant benefits in terms of terminal cost and compatibility.

[0135] The terminal receives network indication information sent by the system. If the maximum uplink or downlink transmission bandwidth supported by the terminal is less than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network, and the uplink or downlink bandwidth supported by the terminal is greater than or equal to the BWP bandwidth configured by the network for this type of terminal, the terminal applies a bandwidth greater than or equal to the BWP bandwidth configured for this type as the terminal's transmission bandwidth; otherwise, the terminal considers that the cell prohibits the terminal's access.

[0136] The terminal receives network indication information sent by the system. If the network indication information does not contain the BWP bandwidth configured for this type of terminal, and if the maximum uplink or downlink transmission bandwidth supported by the terminal is greater than or equal to the carrier bandwidth of the initial uplink or downlink BWP indicated by the network, the terminal applies a bandwidth greater than or equal to the initial uplink or downlink BWP bandwidth indicated by the network as the terminal's transmission bandwidth; otherwise, the terminal considers that the cell prohibits the terminal's access.

[0137] Figure 1 This is a flowchart illustrating a method performed by a user equipment (UE) according to Embodiment 1 of the present invention.

[0138] like Figure 1 As shown, in step 101, the BWP configuration information configured by the network for the UE type of the UE is received, wherein the BWP corresponding to the BWP configuration information is different from the initial downlink BWP of the cell.

[0139] Then, in step 103, based on the received BWP configuration information, at least one of the following is determined: the PDCCH location in the common search space, the width and value of the frequency domain indication field in the DCI used for data scheduling, and the location of the scheduled PDSCH resource.

[0140] Specifically, the terminal can perform a random access procedure or a data transmission procedure in a cell configured with CORESET0, depending on the terminal type and / or capabilities and network instructions. The terminal determines the PDCCH search location in the relevant common search space, the width and value of the frequency domain indication field in the DCI for data scheduling, the location of the scheduled PDSCH resources, and the reference beam of the DMRS, based on the configuration.

[0141] In the public search space, the DCI carried by the PDCCH uses the Type 1 PDSCH frequency domain resource allocation method to schedule PDSCH data transmission. The network can allocate a frequency domain resource of size [missing information - likely a value]. Within the BWP band, a continuous RB is allocated for data transmission. The frequency resource allocation indication field in the DCI uses the RIV (resource indication value) to indicate the specific time-frequency resource location allocated for data transmission. The RIV value determines the bandwidth covered by the scheduled continuous RB within the indication field. The relative starting position RB in the resources start and length L RBs For example, the following method can be used based on RB. start and length L RBs By determining the RIV value transmitted in the DCI, the corresponding RB can also be derived from that RIV value. start and length L RBs This determines the resource locations used for PDSCH transmission.

[0142] if So

[0143]

[0144] otherwise

[0145]

[0146] Here L RBs ≥1 and not greater than The DCI used for downlink data scheduling includes a frequency domain resource allocation indication field, which indicates the bandwidth configuration of the resources used by the scheduled PDSCH. For example, when using the Type 1 PDSCH resource allocation method, the bit length of the indication field is [insert bit length here]. in This refers to the bandwidth of the BWP used.

[0147] The terminal also needs to determine the mapping position of the resource blocks indicated in the DCI in the actual physical channel using an appropriate method. That is, the terminal maps the indicated resources to the actual transmitted PDSCH resource positions based on the relative positions of the resources indicated by the RIV, the relevant physical resource start positions, and other configuration parameters such as interleaving parameters. For example, the terminal may determine the RB resources indicated by the RIV one by one based on the determined resource start positions, or the terminal may start interleaving the number of RBs in the bandwidth associated with the RIV based on the determined resource start positions and map the resources indicated by the RIV according to the interleaving rules.

[0148] As an example, the network configures a Baseband Window (BWP) for a certain type of terminal for random access or data transmission of that type of terminal. The bandwidth supported by the terminal is greater than or equal to the BWP configured for that terminal by the network. In a cell configured with CORESET0, the terminal determines the positional relationship between the BWP and CORESET0 based on the terminal's type and / or capabilities and network instructions. If the BWP contains all the Baseband RBs (RBs) of CORESET0, the terminal uses the bandwidth of CORESET0 and subcarrier spacing parameters to determine information such as the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources. If the BWP does not contain all the Baseband RBs of CORESET0, the terminal uses the bandwidth of the BWP and subcarrier spacing parameters to determine information such as the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources.

[0149] Optionally, the network configures a BWP for a certain type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for the random access procedure of that type of terminal. If the BWP does not contain all RBs of CORESET0, the terminal uses the random access search space on that BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH on the random access search space of the initial BWP.

[0150] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined for the CORESET0 bandwidth and its SCS. If the BWP does not contain all the RBs of CORESET0, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined for the bandwidth of the BWP and its SCS.

[0151] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the minimum RB offset of the scheduled resource relative to CORESET0. RBs This represents the number of RBs in the scheduled resources. If the BWP does not contain all RBs of CORESET0, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameter to determine the value of the relevant DCI intermediate frequency domain indicator field for data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined by the BWP bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located in the BWP. RBs The number of RBs for the scheduled resources.

[0152] Optionally, the network configures a BWP for a certain type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET0. If the BWP does not contain all RBs of CORESET0, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

[0153] As an example, the network configures a Baseband Window (BWP) for a certain type of terminal for random access or data transmission of that type of terminal. The bandwidth supported by the terminal is greater than or equal to the BWP configured for that terminal by the network. In a cell configured with CORESET0, the terminal determines the positional relationship and subcarrier spacing parameter relationship between the BWP and CORESET0 based on the terminal type and / or capabilities and network instructions. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources.

[0154] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for the random access procedure of that type of terminal. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH used for the random access procedure on the random access search space of the initial BWP.

[0155] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined for the bandwidth of the BWP and its SCS.

[0156] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the minimum RB offset of the scheduled resource relative to CORESET0. RBs This refers to the number of RBs in the scheduled resources. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the relevant DCI intermediate frequency domain indicator field for data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined by the BWP bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located in the BWP. RBs The number of RBs for the scheduled resources.

[0157] Optionally, the network configures a BWP for a certain type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET0. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

[0158] As an example, the network configures a Baseband Window (BWP) for a certain type of terminal for random access or data transmission of that type of terminal. The bandwidth supported by the terminal is greater than or equal to the BWP configured for that terminal by the network. In a cell configured with CORESET0, the terminal determines the positional relationship and subcarrier spacing parameter relationship between the BWP and CORESET0 based on the terminal type and / or capabilities and network instructions. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width, value, and location of the scheduled PDSCH resources in the DCI intermediate frequency domain indication field for the relevant data scheduling. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of CORESET0, the bandwidth of the BWP, and the subcarrier spacing parameters to determine the width, value, and location of the scheduled PDSCH resources in the DCI intermediate frequency domain indication field for the relevant data scheduling.

[0159] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for the random access procedure of that type of terminal. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH used for the random access procedure on the random access search space of the initial BWP.

[0160] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width of the DCI intermediate frequency domain indication field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indication field for the common search space is determined by the bandwidth of CORESET0, which is the number of RBs determined by the CORESET0 bandwidth and its SCS. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the number of RBs determined by the CORESET0 bandwidth and its SCS to determine the width of the DCI intermediate frequency domain indication field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indication field for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined for the CORESET0 bandwidth and its SCS.

[0161] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the network uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs is determined by the CORESET0 bandwidth and its SCS, RBstart is the offset of the scheduled resource relative to the minimum RB of CORESET0, and LRBs is the number of RBs of the scheduled resource. If the BWP does not contain all the RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the relevant DCI intermediate frequency domain indicator field for data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0 and the bandwidth of the BWP. The number of RBs determined for the CORESET0 bandwidth and its SCS. The number of RBs determined for the BWP bandwidth and its SCS. The RIV value is used to determine the usage on the BWP. and The mapping location of a certain combination of VRBs.

[0162] if

[0163] Then

[0164] otherwise

[0165] Where L′ RBs =L RBs / K,RB′ start =RB start / K and L′ RBs Not greater than if K is a set {1, 2, 4, 8} that satisfies The maximum value, otherwise K=1.

[0166] Optionally, the network configures a BWP for a certain type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET0. If the BWP does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

[0167] As an example, the network configures a Baseband Window (BWP) for a certain type of terminal for random access or data transmission of that type of terminal. The bandwidth supported by the terminal is greater than or equal to the BWP configured for that terminal by the network. In a cell configured with CORESET0, the terminal determines the positional relationship and subcarrier spacing parameter relationship between the BWP and CORESET0 based on the terminal type and / or capabilities and network instructions. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources. If the BWP does not contain all the RBs of CORESET0 and uses the same subcarrier spacing parameters and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0, the subcarrier spacing parameters, and the starting position of the BWP to determine the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the width and value of the relevant data scheduling DCI intermediate frequency domain indication field and the location of the scheduled PDSCH resources.

[0168] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the random access search space on the initial BWP indicated by the network to receive the PDCCH for the random access procedure of that type of terminal. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the same size CORESET0 on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH used for the random access procedure on CORESET0. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing or different cyclic prefix parameters, the terminal uses the random access search space on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH on the random access search space of the initial BWP.

[0169] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all the RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS. If the BWP does not contain all the RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the CORESET0 bandwidth, subcarrier spacing parameters, and the start position of the BWP to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the CORESET0 bandwidth. The number of RBs determined by the CORESET0 bandwidth and its SCS. If the BWP does not contain all the RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the resource configuration of the data channel. The bit length of the DCI intermediate frequency domain indication field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined for the bandwidth of the BWP and its SCS.

[0170] Optionally, the network configures a BWP for a specific type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the minimum RB offset of the scheduled resource relative to CORESET0. RBs The number of RBs for the scheduled resources. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth of CORESET0, the subcarrier spacing parameters, and the starting position of the BWP to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located. RBs The number of RBs for the scheduled resources.

[0171] If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth of the BWP and the subcarrier spacing parameters to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs determined by the BWP bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located in the BWP. RBs The number of RBs for the scheduled resources.

[0172] Optionally, the network configures a BWP for a certain type of terminal for random access or data transmission of that type of terminal. If the BWP contains all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the resource location of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of CORESET0. If the BWP does not contain all RBs of CORESET0 and uses the same subcarrier spacing and cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET where the DCI that schedules the PDSCH on the BWP is located. If the BWP does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the resource configuration of the data channel, and the scheduled PDSCH resource location is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP.

[0173] As an example, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives a BWP configuration related to that terminal type, and the bandwidth supported by the terminal is greater than or equal to the BWP configured by the network for that terminal type, the terminal uses the BWP bandwidth to determine the width and value of the relevant DCI intermediate frequency domain indication field for data scheduling, as well as the location of the scheduled PDSCH resources. If the terminal does not receive a BWP configuration for that type of terminal, the terminal uses the cell-related initial BWP or CORESET0 to determine the width and value of the relevant DCI intermediate frequency domain indication field for data scheduling, as well as the location of the scheduled PDSCH resources.

[0174] Optionally, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives a BWP configuration related to that terminal type, the terminal uses the random access search space on the BWP on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH on the random access search space of the initial BWP. If the terminal does not receive a BWP configuration for that type of terminal, the terminal uses CORESET0 to receive the PDCCH for the random access procedure of that type of terminal.

[0175] Optionally, the network may configure a BWP for a specific type of terminal, or not configure a BWP for that type of terminal device, for random access or data transmission by that type of terminal. If a terminal receives a BWP configuration related to that terminal type, the terminal uses the BWP bandwidth to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the BWP bandwidth. The number of RBs is determined for the BWP bandwidth and its SCS. If the terminal does not receive a BWP configuration for this type of terminal, the terminal uses the cell's initial BWP to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined for the CORESET0 bandwidth and its SCS.

[0176] Optionally, the network may configure a BWP for a specific type of terminal, or not configure a BWP for that type of terminal device, for random access or data transmission by that type of terminal. If a terminal receives a BWP configuration related to that terminal type, the terminal uses the BWP bandwidth to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the BWP bandwidth. The number of RBs determined by the BWP bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located in the BWP. RBs This refers to the number of RBs for the scheduled resources. If the terminal does not receive a BWP configuration for this type of terminal, the terminal uses the cell-related initial BWP to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the minimum RB offset of the scheduled resource relative to CORESET0. RBS The number of RBs for the scheduled resources.

[0177] Optionally, the network may configure a BWP for a specific type of terminal, or not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives a BWP configuration related to that terminal type, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the resource configuration of the data channel, and the scheduled PDSCH resource position is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP. If the terminal does not receive a BWP configuration for that type of terminal, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the resource position of the data channel, and the scheduled PDSCH resource position is mapped from the smallest RB sequence number of CORESET0.

[0178] As an example, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives a BWP related to that terminal type and a CORESET on that BWP for carrying the random access search space, the terminal uses the BWP bandwidth configuration to determine the width and value of the relevant DCI intermediate frequency domain indication field for data scheduling, as well as the location of the scheduled PDSCH resources. If the terminal does not receive a BWP configuration for that type of terminal or a CORESET configuration on that BWP for carrying the random access search space, the terminal uses the cell-related initial BWP or CORESET0 to determine the width and value of the relevant DCI intermediate frequency domain indication field for data scheduling, as well as the location of the scheduled PDSCH resources.

[0179] Optionally, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives the BWP configuration related to that terminal type and the CORESET on that BWP for the random access search space, the terminal uses the CORESET on the BWP to receive the PDCCH for the random access procedure of that type of terminal, and does not receive the PDCCH for the random access procedure on CORESET0. If the terminal does not receive the BWP configuration for that type of terminal or the CORESET configuration on that BWP for the random access search space, the terminal uses CORESET0 to receive the PDCCH for the random access procedure of that type of terminal.

[0180] Optionally, the network may configure a BWP for a specific type of terminal, or not configure a BWP for that type of terminal device, for random access or data transmission by that type of terminal. If a terminal receives a BWP related to its terminal type and the CORESET or search space configuration on that BWP for carrying type1-PDCCH, the terminal uses the BWP bandwidth configuration to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field used for the common search space is determined by the bandwidth of the BWP. The number of RBs is determined for the BWP bandwidth and its SCS. If the terminal does not receive the BWP configuration for this type of terminal or the CORESET or search space configuration on the BWP for carrying type 1-PDCCH, the terminal uses the cell-related initial BWP to determine the width of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The bit length of the DCI intermediate frequency domain indicator field for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined for the CORESET0 bandwidth and its SCS.

[0181] Optionally, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If a terminal receives a BWP related to that terminal type, along with the CORESET and search space configuration on that BWP for random access search space, the terminal uses the BWP bandwidth configuration to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field for the common search space is determined by the bandwidth of the BWP. The number of RBs determined by the BWP bandwidth and its SCS, RB start L is the offset of the scheduled resource relative to the minimum RB of the CORESET where the DCI is located in the BWP. RBS This refers to the number of RBs for the scheduled resources. If the terminal does not receive a BWP configuration for this type of terminal or a CORESET or search space configuration on that BWP for carrying type 1-PDCCH, the terminal uses the cell-related initial BWP to determine the value of the DCI intermediate frequency domain indicator field for the relevant data scheduling. The RIV value of the DCI intermediate frequency domain indicator field for the common search space is determined by the bandwidth of CORESET0. The number of RBs determined by the CORESET0 bandwidth and its SCS, RB start L is the minimum RB offset of the scheduled resource relative to CORESET0. RBS The number of RBs for the scheduled resources.

[0182] Optionally, the network configures a BWP for a certain type of terminal, or does not configure a BWP for that type of terminal device, for random access or data transmission of that type of terminal. If the terminal receives a BWP configuration related to that terminal type and a CORESET or search space configuration for random access search space on that BWP, the terminal uses the bandwidth and subcarrier spacing parameters of the BWP to determine the resource configuration of the data channel, and the scheduled PDSCH resource position is mapped from the smallest RB sequence number of the CORESET that schedules the PDSCH on the BWP. If the terminal does not receive a BWP configuration for that type of terminal or a CORESET or search space configuration for random access search space on that BWP, the terminal uses the bandwidth and subcarrier spacing parameters of CORESET0 to determine the resource position of the data channel, and the scheduled PDSCH resource position is mapped from the smallest RB sequence number of CORESET0.

[0183] According to one or a combination of the above methods, the terminal can determine the width of the frequency domain indication field of the DCI used for data scheduling in the common search space for that type of terminal, thereby determining the size of the DCI. The network and terminal can also determine the size of the DCI used for the user search space based on the determined size of the common search space DCI. For example, when the size of the DCI used for the user search space is not equal to the size of the DCI in the common search space, and the total number of DCI types exceeds the terminal's receiving capacity, the size of some DCIs is aligned to the determined size of the common search space DCI by padding with zeros or truncating bits. Accordingly, the resource location information of the relevant scheduling PDSCH or PUSCH can be determined based on the values ​​represented by the zero-padding or truncated bits.

[0184] [Variation Example]

[0185] Below, using Figure 2 This describes a user equipment, as a variation, that can execute the method described in detail above for user equipment.

[0186] Figure 2 This is a block diagram representing the user equipment (UE) involved in this invention.

[0187] like Figure 2 As shown, the user equipment UE20 includes a processor 201 and a memory 202. The processor 201 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 202 may include, for example, volatile memory (such as random access memory, RAM), a hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Program instructions are stored on the memory 202. When executed by the processor 201, these instructions can perform the methods described in detail herein, executed by the user equipment.

[0188] The method and related apparatus of the present invention have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are merely exemplary, and the various embodiments described above can be combined with each other without contradiction. The method of the present invention is not limited to the steps and sequence shown above. The network nodes and user equipment shown above may include more modules, such as modules that can be developed or will be developed in the future for use with base stations, MMEs, or UEs, etc. The various identifiers shown above are merely exemplary and not limiting, and the present invention is not limited to the specific information elements exemplified by these identifiers. Those skilled in the art can make many variations and modifications based on the teachings of the illustrated embodiments.

[0189] It should be understood that the above embodiments of the present invention can be implemented by software, hardware, or a combination of both. For example, the various components inside the base station and user equipment in the above embodiments can be implemented by a variety of devices, including but not limited to: analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, programmable processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and so on.

[0190] In this application, "base station" can refer to a mobile communication data and control switching center with high transmission power and wide coverage, including functions such as resource allocation and scheduling, and data reception and transmission. "User equipment" can refer to user mobile terminals, such as mobile phones, laptops, and other terminal devices that can wirelessly communicate with base stations or micro base stations.

[0191] Furthermore, the embodiments of the present invention disclosed herein can be implemented on a computer program product. More specifically, the computer program product is one that has a computer-readable medium on which computer program logic is encoded, which, when executed on a computing device, provides related operations to implement the above-described technical solutions of the present invention. When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention. This configuration of the present invention is typically provided as software, code, and / or other data structures disposed or encoded on a computer-readable medium such as an optical medium (e.g., CD-ROM), floppy disk, or hard disk, or other media such as firmware or microcode on one or more ROM, RAM, or PROM chips, or downloadable software images, shared databases, etc., in one or more modules. The software or firmware or such configuration can be installed on a computing device to cause one or more processors in the computing device to execute the technical solutions described in the embodiments of the present invention.

[0192] Furthermore, each functional module or feature of the base station equipment and terminal equipment used in each of the above embodiments can be implemented or executed by circuitry, which is typically one or more integrated circuits. Circuitry designed to perform the various functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs) or general-purpose integrated circuits, field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, or discrete hardware components, or any combination of the above devices. The general-purpose processor may be a microprocessor, or the processor may be an existing processor, controller, microcontroller, or state machine. The aforementioned general-purpose processor or each circuit may be configured by digital circuitry or by logic circuitry. Furthermore, when advancements in semiconductor technology lead to advanced technologies that can replace current integrated circuits, the present invention may also utilize integrated circuits obtained using such advanced technologies.

[0193] Although the present invention has been illustrated above with reference to preferred embodiments, those skilled in the art will understand that various modifications, substitutions, and alterations can be made to the invention without departing from its spirit and scope. Therefore, the invention should not be limited by the above embodiments, but rather by the appended claims and their equivalents.

Claims

1. A method executed by a user equipment (UE), comprising: The network receives UE type configuration information (BWP) for the UE, which is sent by the system broadcast message (SIB). The BWP corresponding to the BWP configuration information is different from the cell's initial downlink BWP. as well as Based on whether the received BWP contains all resource blocks RB of CORESET0, determine at least one of the following: the location of the Physical Downlink Control Channel (PDCCH) in the common search space for random access or data transmission of the UE type; the width and value of the frequency domain indication field in the downlink control information (DCI) for data scheduling transmitted by the PDCCH; and the location of the Physical Downlink Shared Channel (PDSCH) resource scheduled by the DCI.

2. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameters to determine at least one of the width, value and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resources. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE uses the bandwidth and subcarrier spacing parameters of the BWP to determine at least one of the width, value, and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resources.

3. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks (RBs) of CORESET0, the UE uses the random access search space on the initial BWP of the cell to receive the PDCCH for the random access procedure of the UE. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.

4. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine at least one of the width, value and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resource. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the bandwidth of the BWP and the subcarrier spacing parameters to determine at least one of the following: the width and value of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resources.

5. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the random access search space on the cell initial BWP to receive the PDCCH for the random access procedure of the UE. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 or uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.

6. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0 and the subcarrier spacing parameter to determine at least one of the width, value and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resource. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the bandwidth of CORESET0, the subcarrier spacing parameter and the starting position of the BWP to determine at least one of the width and value of the frequency domain indication field in the DCI and the position of the scheduled PDSCH resource. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses the bandwidth of the BWP and the subcarrier spacing parameters to determine at least one of the width, value, and location of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resources.

7. The method according to claim 1, wherein, If the BWP corresponding to the BWP configuration information contains all resource blocks RB of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the random access search space on the cell initial BWP to receive the PDCCH for the random access procedure of the UE. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses the same subcarrier spacing parameter and cyclic prefix parameter, the UE uses the CORESET on the BWP with the same size as CORESET0 to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH for the random access procedure on the random access search space on the initial BWP of the cell. If the BWP corresponding to the BWP configuration information does not contain all RBs of CORESET0 and uses different subcarrier spacing parameters or different cyclic prefix parameters, the UE uses CORESET on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH of the random access search space on the initial BWP of the cell.

8. The method according to claim 1, wherein, If the UE receives a BWP configured for the UE by the network, the UE uses the bandwidth of the BWP to determine at least one of the width and value of the frequency domain indication field in the DCI and the location of the scheduled PDSCH resources; If the UE does not receive a BWP configured for the UE by the network, the UE uses a cell-related initial BWP or CORESET0 to determine at least one of the following: the width and value of the frequency domain indication field in the DCI, and the location of the scheduled PDSCH resources.

9. The method according to claim 1, wherein, If the UE receives a BWP configured for the UE by the network, the UE uses the random access search space on the BWP to receive the PDCCH for the random access procedure of the UE, and does not receive the PDCCH on the random access search space on the initial BWP of the cell. If the UE does not receive the BWP configured for the UE by the network, the UE uses the random access search space on the initial BWP of the cell to receive the PDCCH for the random access procedure of the UE.

10. A user equipment, comprising: processor; as well as Memory, which stores instructions The instructions, when executed by the processor, perform the method according to any one of claims 1 to 9.

Images